From time to time there pops up a thread where people complain that learning the Amiga-API would be so hard and that no good resources would be available.
Now, there is the the Amiga-C-Manual, but thats quite outdated, and there is the Yahoo-maillist amiga_bcg but here you will find all sorts of skill-levels and question mixed up.
And then you have the occasional tutorial in print-magazines, but I allways found they were trying to do to much at a time overwhelming the reader, and making it hard to figure out where the tutorial ends, and where the pseudo-functionallity starts.
I therefore decided *fanzy fanfare* to do my own !!
It's very basic
It's targeted a users with basic C-skills
It's examples won't try to be usefull in any kind
It's a one proble at a time approach
It expects the reader to look up further options and arguments himself
Preparing yourself for the ride:
http://home.arcor.de/dietmar_eilert/site/cubic/download.htmDownload atleast the Demo-versoin (should suffice), buying the full package is offcourse an even better idea (and no I'm not getting paid for writing this :pissed: ), you may also wish to download the C/C++ Add-On Package, unless you know how to setup and use a bare compiler&documentation.
After installing, set Compiler to gcc (press blue box in toolbar), and target to amigaos3 (gcc 2.95.3). Useing other compilers and targets should be possible, but for the moment we should keep the possible problems to a minimum.
Now create a new project (the tilted white paper)and make it an Amiga project. After doing that open the created file main.c and paste the tutorial-source into it (yes, I'm sure there are more elegant ways of doing it, but for the moment this will do).
You should now be able to call "make all" (the 4 connected blue boxes) and "run" (white on green arrow).
O.k. here are the 1st chapters:
Intuition1Intuition2Once you got them working you should right-click some of the coloured keyword, selcect "look up word" (or something similar) to see other related functions, structures and tags.
I will not explain all of them, only those that aren't self-explaining and/or important.
As noted above these were written for OS3.x, no change is needed to adapt them for MorphOS-native (and same should go for AROS), adapting them to OS4-native would either need a pre-processor statement switching of the use of interfaces, or actully adding the code for interfaces. As none of this changes the way the API and it's functions work, this isn't neccasary until you have grown out of tutorials.
