p96 & cgx open standard replacement anyone?

[wawrzon]

That makes no sense, why would you want to keep an API closed?  You'd want more people to use it, right?  Kind of the whole point of having an API....

slaapliedje

unfortunatelly this exactly is the case. we want to talk about strategic solution here.

[itix]

both the aros cybergraphics api and sources are open,and compatible to cgx (de facto primary) standard, p96 is as well compatible to. so, we do have all material to start with actually. no need to open anything else.

While you would also control source code and the future development.

By the way, I took a quick look into AROS and it seems that graphics drivers are implemented separately from CGX (https://en.wikibooks.org/wiki/Aros/Developer/Docs/HIDD/Graphics). CGX part in AROS is just cybergraphics.library (de facto standard for some sweeteners). The driver API is not CGX or P96 so nobody have to debate which one better.

Hardest part is integrating this stuff into the original, OCS bound, graphics.library.

[psxphill]

Hardest part is integrating this stuff into the original, OCS bound, graphics.library.

Ideally you'd just replace graphics.library with the one from aros (or use aros).

But the graphics.library design they came up with for aros was not optimised because pc's have fast cpu's and the ocs/ecs/aga driver is the bare minimum implementation and really slow too. It appears to be one of the major issues with running it on 68k hardware.

Sorting that out would have major benefits all round.

[wawrzon]

Ideally you'd just replace graphics.library with the one from aros (or use aros).

But the graphics.library design they came up with for aros was not optimised because pc's have fast cpu's and the ocs/ecs/aga driver is the bare minimum implementation and really slow too. It appears to be one of the major issues with running it on 68k hardware.

Sorting that out would have major benefits all round.

this has been brought repeatedly. though as someone who tests aros on amiga hardware i dont think the difference is so dramatic, even currently. i could think of some testcase measuring difference between lets say 3.9 and aros on the same config with the same resolution using librarytimer. is there something that stresses all functions of graphics.lib to be simply run from the shell?