AMOSPro re-development general speculation

Started by bruceuncle, September 06, 2012, 08:57:41 AM

Previous topic - Next topic

0 Members and 2 Guests are viewing this topic.

bruceuncle

Quotei'll wait the next update!

It may be a while...  ;)

There's a lot of useful stuff there in addition to just the sources.  Every little bit helps.  I especially like the status reports/bug reports/etc.  They help complete the picture.

Now back to browsing.  Where's my French/English dictionary? ...

It's very tempting to extract the comments and their positions, put them through a translator and then put them back in place.  I've learnt a lot of French lately and I think fully translated sources would be a good first step.
Repeat after me ...  "The AMOS Pro architecture is complex but it is not complicated."

MadAngus

#76
Tickityboo, excellent news thank you Pietro and Francois. ;D

More documentation and another digital forest to cut down.

ghizzo, do you have a website you want added to the acknowledgments section.
My shadow says otherwise.

Spellcoder

Quote from: ghizzo on December 01, 2012, 06:10:43 PM
Hi!

I'm Pietro Ghizzoni... as promised i've released the AMOSPro sources. Actually they aren't on Aminet. Here in Italy there is now the Pianeta Amiga 2012 show. I've released the sources during the DevCon conference. Now you can download them from the Pianeta Amiga site http://www.pianetaamiga.it

It's good to see so many brave coders ready to update AMOS like i and the AMOS NG team dreamed to do years ago. But be ready to discover that the AMOS sources are really bad structured, there aren't docs and the sources are not commented  :'( In other words upgrade it means rewrite it 100%.

Good Luck!  ;)

Thanks for the work on getting the distribution finished and released! :).

Funny to see previous unknown information, like information on research for PCos (a version of AMOS for the pc).

Are your patches for AMOSPro in there too? (faster amos/wb switching, limit bob fix, compiled amos progs memory deallocation race condition fix, printer fix etc)

Hungry Horace

Many many thanks Pietro!

Great news for the AMOS collective still out there!!
Quote from: KillerGorillabecause winuae is made of code and your amiga is made of stuff


BooBoo

#79
Yes thanks guys  :)
I assume the Amos compiler outputs/stores ASM before the final compile could this ASM outputed exported

Of course if anyone is able to update Amos - AGA screen modes would be great 16*16, id be happy to stay with 16,32 colours sprites/bobs

I think the guys at Shadow softare used an AGA extention for JetStrike - it might be worth contacting them

MadAngus

#80
Quote from: BooBoo on December 04, 2012, 10:53:31 AM
I think the guys at Shadow softare used an AGA extention for JetStrike - it might be worth contacting them
Cheers for the input.

I recently read something about this. The AGA extention for JetStrike was specific to Jetstrike and for some reason couldn't be used for other things :(. If I find the details of this I'll post them.

QuoteI assume the Amos compiler outputs/stores ASM before the final compile could this ASM outputed exported
Do you mean export the asm instructions.

This sort of thing:
move.l  (T_EcCourant,a5),a4
move.l  (EcWindow,a4),a5
move.w  #0,(WiGraph,a5)

If so bruceuncle may be able to answer that if his current investigations have got that far.
My shadow says otherwise.

bruceuncle

Quote from: BooBoo on December 04, 2012, 10:53:31 AM
I assume the Amos compiler outputs/stores ASM before the final compile could this ASM outputed exported

I'm afraid it doesn't work like that if it's assembler source output you're after.  Don't know the full details yet.  But, with the sources now public, you'll find each and every AMOS instruction is implemented as a relocatable code chunk.  Plus some more code chunks for initialisations and common tasks.  As long as your code references amos.library through the AMOS includes, you can use the functionality of those chunks for your own purposes in an extension or embedded code and an AMOS Basic program.

The compiler is quite buggy.  So it will get a fair bit of attention in the redevelopment.  We'll all know a lot more then. ;)
Repeat after me ...  "The AMOS Pro architecture is complex but it is not complicated."

MadAngus

#82
Although the ClassicAMOS and AMOS 3.x boards are specifically for the actual development, these boards are open to all.

Please post wisely as I do not intend to spend a lot of my time moving posts and topics.
My shadow says otherwise.

MadAngus

#83
Sorry folks I've decide to steal back the AMOS Evolution name for the future of Deimos which will now be named Avolution (AMOS Evolution). The board will be renamed to reflect this and will be specifically for development of Avolution.

I'll create a new board for AMOS Pro 3.x when the time comes to update it past the ClassicAmos development stream.

[Edit]
I've changed all the 'AMOS Evolution' references in previous posts in this thread to 'AMOS Pro 3.x' to avoid confusion.
My shadow says otherwise.

Lonewolf10

Quote from: rayon on January 04, 2013, 04:51:40 PM
@bruceuncle:
I've seen your AMOS overview and it is a great document to get an understanding of the overall architecture of AMOS.
Also the quality is good, I like it, short simple but understandable!

I agree :)


Quote from: rayon on January 04, 2013, 04:51:40 PM
- Is there a known issue / bug list?

Yes. A few bugs are listed on the www.AmigaCoding.com website.

MadAngus

#85
I've locked this topic, interested parties should now create more specific discussion topics.

If you need me to split posts in this topic into a new thread for specific discussion please inform me.

bruceuncle if you think I should unlock this topic please pm me.

[Edit] I've merged the 'AMOS Pro 2: Known Bugs', 'AMOS Editor workbench window', 'TOME Re-Development', 'AMOS Pro Tutor Project' threads from the ClassicAMOS Development Board to the duplicates in the Feature requests and bug reports.

These can be added to the ClassicAMOS Development Board when the actual development/release cycle begins.
My shadow says otherwise.