@HenryCase

Btw, did AROS have lamp/textinput/listview and string classes ? If no, then, to the bounty #1 need to add also them, because they all also need for fab's owb.

Related to bounty#2 and fixes in zune "there and there": i think there we can mixing bounty 2 with bounty 3. And so, it will be called:

Bounty2: making zune works the same as mui3.x , and as prove-of make LunaPaint works on mui (os3/os4/mos) (because as it now, LunaPaint compiles just buggy and on aos4 and on mos (and bugs are the same, which point on the same problems related to current differences beetwen mui and zune in some areas ).

(I of course will help to test aos4/mos versions, with no problems, and for free).

So, no more bounty3 then as it was, and new version of Bounty3.

Bounty3: Implement as much as possible mui4 features in zune, but, for compile the bounty, need only necessary ones which need for making fab's OWB works. The features are: some methods of List should works as methods, not as hooks (but maybe in aros its already done like this, dunno), some wellknown bugs should be fixes (show_mui (if not already) ) , some functions should return TRUE/FALSE when the braked around of IF, i.e. like:

Quote:

Fix negative arrays (or add normal support of them, or just make the code not crashes on it). As example:

Quote:

And some more, which for now i do not remember, but when someone will really assign this bounty, i will describe everything normally.

Also examples which prove that all new features works fine and as should should be added to finalize the bounty as well.

Bounty4: Port a Fab's OWB. Ther is also will be a lot of work, but, with all available classes, with normal working zune which reacts as mui3-4 1:1 - its will be more or less easy. Just will need rewrite hooks and macroses. All the other code we already do for aos4 (like tabs and other small workorounds).

When any of aros developers will assign any of these bounty and will start to works on it: he can expect that i will help him with everything related to it , and as we already pass that way for aos4, then it will be for that developers twice easy.

Hi amigan,

Thank you for taking the initiative with this. You proposals seem reasonable. However, I'd like to see more detail. There needs to be clearly defined goals so that you judge when the goal is met.

For example, on sub-bounty 2, 'fixes zune here and here', it should list what should be demonstrated to be working without obvious bugs.

Similarly, on sub-bounty 4, what are the names of the new API calls that need to be implemented?

Thanks,
Tom

Smaller sub-bounties should be easier to do:

Bounty No. 1: make an AboutBox and Process classes.

Bounty No. 2: fixes zune here and here (all those datatypes, showmui and whatever bugs is zune have for now).

Bounty No. 3: making zune react the same as mui3.x by testing of the LunaPaint.

Bounty No. 4: implemented new API calls (family,area,group,menu)

Final Bounty: port fab's OWB


This is a *rough* draft; it can be improved.
Let's get this thing roll.