From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me X-Spam-Level: X-Spam-Status: No, score=-1.1 required=5.0 tests=BAYES_00, PP_MIME_FAKE_ASCII_TEXT autolearn=no autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII X-Google-Thread: 103376,88ed72d98e6b3457 X-Google-Attributes: gid103376,public X-Google-ArrivalTime: 2003-10-12 04:14:54 PST Path: archiver1.google.com!news2.google.com!news.maxwell.syr.edu!newsfeed-west.nntpserver.com!hub1.meganetnews.com!newsfeed-east.nntpserver.com!nntpserver.com!chi1.webusenet.com!news.webusenet.com!cyclone1.gnilink.net!spamkiller2.gnilink.net!nwrdny03.gnilink.net.POSTED!53ab2750!not-for-mail From: "Stephane Richard" Newsgroups: comp.lang.ada References: <3F7F760E.2020901@comcast.net> <3F8035B0.7080902@noplace.com> <3F816A35.4030108@noplace.com> <3F81FBEC.9010103@noplace.com> <6Ingb.30667$541.13861@nwrdny02.gnilink.net> <3F82B4A4.5060301@noplace.com> <3F82F527.3020101@noplace.com> <3F846B5E.9080502@comcast.net> <3F855460.6020804@noplace.com> <3F86211B.103@comcast.net> <3F8640CA.6090306@noplace.com> <3F86FE09.3050302@comcast.net> <3F8816EB.1010009@noplace.com> <3F88A577.5000803@noplace.com> <3F88BD31.6050906@noplace.com> Subject: Re: Standard Library Interest? X-Priority: 3 X-MSMail-Priority: Normal X-Newsreader: Microsoft Outlook Express 6.00.2800.1158 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 Message-ID: Date: Sun, 12 Oct 2003 11:14:54 GMT NNTP-Posting-Host: 141.149.81.17 X-Complaints-To: abuse@verizon.net X-Trace: nwrdny03.gnilink.net 1065957294 141.149.81.17 (Sun, 12 Oct 2003 07:14:54 EDT) NNTP-Posting-Date: Sun, 12 Oct 2003 07:14:54 EDT Xref: archiver1.google.com comp.lang.ada:727 Date: 2003-10-12T11:14:54+00:00 List-Id: "Marin David Condic" wrote in message news:3F88BD31.6050906@noplace.com... > I put a list of things I thought might make good topics for a library > into the Ada Letters article I wrote. You might want to look at that. > > At this stage, I'd say that the only important thing is to start > capturing ideas about what kinds of things *might* be good fodder for > the CAL. Your list got a little too specific and as I have said > elsewhere, I don't think much of bindings and I like less the idea of > grabbing existing things from the Internet and trying to cobble them > into a "Library". (Think about "why": If you had a dozen different > existing libraries, what are the odds that they are using a dozen > different container libraries? If the CAL has a container library, you > would like everything else in the CAL to use *that* library - especially > as it relates to interfaces the end user has to program to.) > > You're simply brainstorming here - that should be the goal. Think about > packages or objects or subsystems you'd like to see. Don't worry about > structure or trees or names - just get down concepts. (e.g. "I think it > would be cool if in some way, some how, the CAL had a package or > subsystem that let me parse XML files and build/maintain an XML DOM.") > Don't worry about specifics and especially don't worry about > incorporating specific existing libraries. Just get down "Requirements" > and "Good Ideas" in a very general way. > > The reason is this: To do this right, you're not going to rush off and > start hacking out code. You're going to ask the vendors and some > potential customers what it is that *THEY* want to see in a library. You > want to get *THEIR* lists of stuff. You might then hand them your list > and say, "Is there anything in there that blows your skirt up? If so, > what would *YOUR* priorities be?" Let the *customer* tell you what they > want built. > > You've got limited resources and you want to build the things that the > end users really want rather than waste your time putting things in that > nobody wants to use. The best source for finding that out is to ask the > vendors and their customers. Do some market research. It will pay in the > end. After that, write some *requirements*. That will pay off too. By > the time you've got some requirements, you'll be able to evaluate your > ideas and existing libraries to see if they meet them. It will keep you > from wasting lots of time in the end. > > MDC > Indeed, In most ways, can't really disagree with that. Although I create a whole hierarchy, it's exactly what I did really. Stated a list of things I'd like to see in the library I just happened to "visualize' they're position in the hierarchy. For my list of things I want to see, look around, my list starts with what's missing in ada that's present in other languages (whether compilable like Delphi/Lylix, or scripting languages like Ruby and Python) as far as containers, data structures, libraries, seems GtkAda has taken the lead for a GUI library, how about a choice?, what else, there's so many. abd that just in categories that I have in the hierarchy. More at a language level, well yes, any containers are always welcome for one thing :-). Stacks, queues, dequeues, lists, collections (sorted or not), data dictionaries and the list goes on and on as far as data structures go. Also, perhaps a librarie that allows better control over a DOS or windows Console screen would be more than welcome :-). I have a binding to C's conio standard library that does things like you can do in any other DOS languages :-) Clear the screen, pick a color, position the cursor, turn the cursor on and off, etc etc...I'd like that in a standard way as in CAL.Screen_IO. kinda fashion. If that can't be accomplished in a multiplatform fashion then perhaps based on each OS but with the same function names so that the code can be compiled and execute on every platform would be nice. Graphic wise there's Ada3D, AdaOpenGL, AdaSDL which seem to cover alot of grounds. I'm thinking a library similar to Allegro (which offers extreme 3D graphics rendering and animation) would be a big plus for Ada in the Gaming industry for example. With AdaSDL it should give you access to MIDI input / output (no?) perhaps a thick binding to MIDI and Digital Audio (direct and Streaming). woudl be good again for the game industry but the music industry as well. I could detail them in a list, sure, but to me, the first two thing that woudl give Ada a competitive edge are like I said, what's missing as compared to other languages (for that I could draw up a list of key features that are sought by developers when looking for a language for the job) I'll start on that right away, and for vendors (yes) but also other companies to start developing third party stuff for Ada like they would say for VB and Delphi, it would be nice since VB adn Delphi are ActiveX languages that they could add at least specification files for Ada for example :-). GNATCOM should be pushed further for one idea :-). Database Bindings are getting better and better Add SQL, SAMeDL, have you looked at APQ? Not sure hwo many generics and definitions they are, but to me APQ is somewhat on the right track to say the least :-).... With databases comes (almost hand in hand) reporting technology too. Someone mentionned CORBA and having all library elements come with an IDL, not a bad idea either, but since we're talking about Ada, I'd first integrate GLADE and develop for it. As a second phase to that I'd see about giving it CORBA support. Add to my list any possible trick and tip to make Ada programming even more faster. Gode generators for repetitive tasks for example. Perhaps a Windows API based Form designer that generates Ada Code based on perhaps Win32Ada or some other thin binding to the Windows API. -- St�phane Richard "Ada World" Webmaster http://www.adaworld.com