I have signed up for the course but since it is delayed is there a reference to get started with ebasic.
It appears to me to be a "top-down' type language. Is there a structure or order in which things should be done?
How do you start? Define screen then add functions? That is sort of the way I work in Aurora.
start with the examples like the menu one.
then the control demo.
Larry
Thanks for the starting point - will look there.
In looking at the examples -- I still get the feeling there is no structure to this type language.
Is there one?
Is there a standard programming conventions of any sort?
My code is bad enough without being able to just stick stuff anywhere.
1st I put any required "libs" and "include" files
Then my declarations (external subs, variables, etc)
Then the openwindow command
Then all the controls to add to the window
Then the window message handler routine.
Then my subs.
That's my basic structure for a single source file application.
The message handler is the heart of any windows based program in EBasic.
That's were you respond to user input and call your various subroutines.
Suggest you study the "Windows Programming" section of the help file.
If you are writing a console based program (non windows) you just start with:
1st I put any required "libs" and "include" files
Then my declarations (external subs, variables, etc)
Then the meat of the program
followed by any subs
Larry