k, when i first heard about it, i thought its probably whats needed, its a good idea,
and it probably is a good idea
but today i saw a list(probably rather quickly put together) of third party apps that some mug thought should be included
the way to create a standard is to begin by outlineing the general requirements(by a broad range of developers and users)
this type of thing isnt even visible on this site
its hard to see how this is going to be a proper and accepted standard: "ok we need this, this, this, and this..."
second to the generalized requirements(which are not to be specifics of particular software), should be the sort of functions and libraries that are required
e.g.
audio support:
-should have the same function & library names as used in AHI
-should fit in with library abc... etc...
blah blah blah...
2d graphics:
-need for compatability with old 8bit bitplane software, with structures as specified in ARKRM's compatable with graphics.library
-chunky graphics support
-16/24 bit support
...
then the specific libraries can be workout(or worked on later)
if its source level compatability that matters, worry about the functions and structures etc...
so that the libraries and the applications can be made to fit together
so when some new mob comes along to produce an amiga os type os instead of using cybergraphics they might want their own software
but they can still write their own graphics libraries, they can then be made to the same basic standards
but specific software/apps/libraries dont have to be included
the GUI side of it i dont know about... too many people have their own ideas as to which set of libraries to use
IMO it should all be OOP and based on BOOPSI
so that all the classes can be intermixed/ added to
