Priest of the Order of the Butterfly
Posts: 525 from 2003/2/25
From: France
Quote:Papiosaur wrote:
Hello,
after Easy2Install, i start a new project named Easy2Compile with Hollywood.
Like i'm a newbie, i need your needs (if you have) to improve my GUI.
This is a first snapshot:
Easy2Compile.pngCompile button has this syntaxe: gg:bin/gcc -noixemul -Wall -o ram:outputexe sourcefile
Execute button launch ram:outputexe
If you edit the script with FlowStudio, you can refresh the source code showed in the window by a double click on the source file on the lister.
I can of course add a pref for destination, options, multiselection, etc...
What do you think about that?
I wait your returns.
The best way to learn programming is simply to write a very simple program to learn things. The target of the program must be easy enough to implement for not being stuck with some totally out of reach goal.
The usual first program anyone write is the famous 'hello world' followed by the 'guess my number' that introduces conditional logic.
Before diving into the intrinsics of MorphOS, I would first take a serious course with ANSI C. There is a lot of paper books available on the subject and preferably in french, your native language.
Those books are perfect to take a tour deep enough in the C language without focusing too much on the platform API (ie: the specific libraries of the operating system).
You can also get some book named like 'Exercices en C'. Those are valuable as well. They don't cover the language itself but provides directed playground to ... exercice. :)
Once you're fluent enough with the language, you can now dive into more serious things because the language isn't anymore your main problem: you read and understand it without decyphering. It is exactly the same thing as learning a foreign language.
Being fluent with the language frees a bit of your brain to learn new things like how the MorphOS system is working. You can hardly do both at the same time: the learning curve is extremly steep imo.
You never drive a 200hp motorbike straight. You first drive a 125cc for a time and then get to a 400cc and finally ride a 1600cc monster. Programming is like mastering motorbike: it is progressive.
Once you're on a 400cc motorbike (ie: you know enough of the C language, you did many exercice book, you know how to tweak a makefile too), then you're ready to dive into the intrinsics of MorphOS (or AmigaOS for instance, the API is mostly 1:1).
Find a simple program to implement like for example:
- a color wheel that produce html hex representation of the color #AARRGGBB
- a simple RPN calculator doing the basic math operations
Ha. We have a new problem. Algorithmics.
If words like linked list, graph, stack, FIFO, LIFO, tree, binary tree, whatever tree, hash, array sound alien, then you also need to learn algorithmics.
Algorithmics isn't specific to a programming language. They are just way of doing things efficiently.
You also need to learn algorithmics because this can help you solve *problems* whatever the language you're using.
The first book in french that comes to my mind is 'Initiation à l'algorithmique'. About 800 pages in small characters. Hopefully, there is some graphics here and there to make it a bit more enjoyable.
While learning algorithmics isn't a stricly necessary step to get into programming, it is in my opinion still a good idea to get into early because this knowledge will help you write better program right from the start (because, you'll have a better idea on how to store/handle data structures to reach your programming goal).
You will probably not use the most advanced data structures like trees or graph for example for your first projects but for the RPN calculator for example, you'll need to master the 'stack' concept first for implementing it efficiently (and most importantly! - successfully too).
Nobody climbs the everest in thong sandals. Practice with generic book first.
ISBN:
2212118252
2212111053
2100492977
2100034383
Then, read RKRM (Rom Kernel Reference Manual) to get a somewhat serious ground in AmigaOS API. You'll need that knowledge at some point to make things.
And finish with mastering MUI. User interface is the tip of the iceberg.