Amount and paypal address please, or IBAN and SWIFT code. Just bear in mind that I have a new MorphOS user at home (2 weeks only).

We recieved 7 donations for the programming toturial unitl now.
I have to add them manuel to the bounty-system, this is the reason
why the amount is zero when you look at the bounty-section...
I will try to add them this evening or tommorow.

Tutorial is a good idea, for me. Tomorrow, i think, donation.

@Krashan

Thanks for a fantastic idea!

It seems that this task is upon you now.

I still have question, not been around for awhile (sold my Mini for financial reasons). Do you plan to include tutorial for Python/PyMui? I do not know what's the stage of yomgui's development but I was close to write some program in Python 9i have 4 years experience in python).

To summarize, because python is easy and very popular, especially in the linux world, it is worth to include it, as a second language I guess, aside C/C++. All the more MorphOS has it - but poorly documented.

What do you think?

I have a strong negative personal opinion about Python language, backed up by some tries to learn it. Sorry, no Python from me.

For french, find some good tutorials :
http://www.gurumed.net/index.php/Accueil

SixK

I've just finished a set of 4 articles fulfilling the first goal of bounty for programmer tutorials.

You can read them there and express your opinion in this thread.

Nice to see this done so quickly! There are a few typos and minor grammar mistakes but they don't effect overall readability. This may the wrong place to ask... Who's allowed to create and edit library articles?

Edit: I think I just found the answer to my question - http://morphos-user.com/

[ Edited by ausPPC on 2010/10/24 11:38 ]

There are a few typos and minor grammar mistakes

Why not list them here or send me a PM? I can fix them then and improve the articles. English is not my native language, so some mistakes are unavoidable...

cool! Thank you Krashan! this is a good start. some questions left:
how to use the autodocs? its possible to use them directly from cubicide?
now we can open muimaster library. how to combine a hello world printout in a simple one button mui gui.
? how to use subproccesses? whats the best way to debug? any log or something?

perhaps its possible to expand the tutorial a bit :) thanks in advance!


[ Edited by manga on 2010/10/24 9:31 ]

@ Krashan : Thanks a lot for this tutorial !

cool! Thank you Krashan! this is a good start. some questions left: [...] perhaps its possible to expand the tutorial a bit :) thanks in advance!

Yes, it is possible. I see it this way: I've stated this first set of articles is worth 25 euro to me. It still applies. The bounty has 185 euro now. Then, when these 25 euro is transferred to me, 160 is still left. We can discuss here what topics should I cover next, for similar bounty sub-amount. I guess it is a fair approach?

I hope you understand that answering most of your questions is impossible in a short forum post. The simplest question is about autodocs. Yes, you can use them from CubicIDE. CubicIDE has an autodoc parser. You specify directories for the parser, then it creates a kind of help database. Then you can set the cursor on a function name and press a hotkey. Then documentation of the function is displayed in a separate window. MorphED, an editor included with the SDK (which is some limited special edition of CubicIDE in fact) does it too.

Hi Krashan,

Nice tutorials.

Some ideas for next tutorials :

- how to debug: kprintf usage, how to interpret debug log (henes did a tutorial on the subject iirc), usage of various debugtool (mungwall like for ex., wipeout etc...)

- custom startup code (already planned i guess, there is a 'dead' link in current tutorial)

- Memory: Everybody needs allocating memory at some point. Alloc*/Free* functions. Some words about local and global symbols and their impact on stack usage. How to track memory leaks.

++

Good first step. Nice to read and pretty informative. I hope with the information provided in part #1 I will be able to update my Cubic IDE installation to the new sdk now.

As for the next step I think a simple and well commented MUI "Hello world" would be most helpful. After that an introduction to debugging.

One other question though regarding calling functions with the same name. Means: When I call printf and include proto/dos.h *and* stdio.h how can I determine which printf will be used? Is there some hierarchy?

[ Editiert durch Zylesea an 2010/10/24 12:33 ]

One other question though regarding calling functions with the same name. Means: When I call printf and include proto/dos.h *and* stdio.h how can I determine which printf will be used? Is there some hierarchy?

Standard C library function is printf(). MorphOS API function is Printf(). Identifiers in C (function name is an identifier) are case sensitive. Then they are just two different functions.

[ Edited by Krashan on 2010/10/24 11:39 ]

Nice starting point for the new developers!

I vote for some kind of debuging howto (shared memory concept, what is a 'hit', getting debuglog, understanding the log, kprintf, wipeout and other usefull tools) and of course a complete, multi-section MUI tutorial. Some basic introduction to exec.library and dos.library woult also be nice-to-have imho.

Really nice tutorials so far.
Please go on describing dos, mui,ahi and cybergraphics.
Please no stanbdard c, because there are so many books about c.
Perhaps some words about amiga specific malloc/free.

EDIT: Also interesting: Threading, Logging Service, ...

[ Edited by eliot on 2010/10/24 13:42 ]

[ Edited by eliot on 2010/10/24 19:34 ]

Quote:
I see. Case sensitivity is always a save trap for me. Be it on a Linux console, Matlab or C++. I always overlook it. Over teh years I should have learned to be a bit more astute in that regard. But I guess will continue to step into that trap aiagn and again...

Ok, so it seems the general reception is positive. AusPPC is sending me a pack of style and grammar fixes. After merging them I will consider the first bounty stage as finished and apply for 25 euro. Then the next stage may be defined. I see most votes go for two topics: debugging and MUI basics. Which one should I take first?


[ Edited by Krashan on 2010/10/24 21:11 ]

Debug from my pov.

I'm curious about how C programmers debug their code too.

please create some sort of debugger, something lowlevel, like monam is on amiga, this is what do i really miss on morphos...

bye, MarK.

Does the MUI chapter include an application and a ChocolateCastle example?

Quote:

Wonderful read. It immediately takes me back to an age when I was learning how to make computers obey humans.

(nowadays, I wonder if that was a good idea anyway )

Your articles are a very rare example of deeply technical writings that, at the same time, can raise genuine emotions. Perhaps you feel them too when you write them.

On a more achademic note, of course, congratulations. I for one would say that these four articles ar exactly what was missing. The problem is, you know... The audience now roars for more!

The problem is, you know... The audience now roars for more!

This is not a problem especially as I've seen the bounty sum has been raised recently. I think the next goal will be "MUIfied Hello World". I want to give it a precedence. Debug tutorial is also important, but debugging plain "Hello world!" is a bit boring IMHO . There is another reason, debugging course should also cover capturing debug via FireWire and I'm just in a process of getting a PowerMac, so I will have some personal experience.

Then the MUI entry level tutorial will cover following topics:

- BOOPSI as an Object Oriented Programming framework, how MUI builds on it.
- Event driven programming and it's implementation in MUI. Notifications.
- Creating basic MUI application.

As an example, i will prepare a minimalistic MUI program having a textfield and a button. I'm not yet sure what amount it will be worth to me, it depends on number of sub-articles needed to cover the above topics. MUI is a very broad topic and I expect more bounty sub-goals will be spent on it in the future.