some of the todos: Add AGA 24 bits color support in copper list - Add AGA 24 bits color support in load IFF / IFF Anim system - Add support to change sprites color palette index. - Update demo to use SCREEN HIDE/SHOW to now display IFF/ILBM loading times. - Add internal checking to avoid loading/writing outside of memory banks (Load Frame, etc.) - (WIP) I plan to add in next update a "Use Screen Palette" to switch AGA Palette between screen own aga palette.
- Screen open resolution up to 4096x4096 pixels (Vampire users)
Yes, I know that. I read the README.MD and even supplied the link to it in my first post and visited github before posting, so the SAGA support being added is more than obvious. What about some assembly experts adding AMMX support? That was the point I was driving at.
Posts 1 13 Nov 2020 10:25
@Olaf : I'm in the place ... I'm about to try to get informations about SAGA chipsets to see what may be possible to insert inside Amos Professional concerning SAGA chipets ;) Nothing official at this time/point...
Nick Fellows (Apollo Team Member) Posts 56 16 Nov 2020 19:00
What im after is the ability to edit AMOS programs using an external editor. Could be something useful there .
Posts 436 17 Nov 2020 02:57
I believe you can export the code to ascii but you have to import it again .. I dont think there is any current mechanic to allow for an external IDE
Nick Fellows (Apollo Team Member) Posts 56 18 Nov 2020 13:41
I think the main issue is that the "source code" is actually tokenised. Figuring out how to implement things so code could be edited externally would require investigating how the AMOS editor translates text into tokens I presume and replicating that somehow.
Even a commandline converter would doe the trick if you could put it into the build script in VSCode . Someone has created language support for AMOS EXTERNAL LINK So we just need the ability to tokenize it for AMOS.