[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [MiNT] WCOWORK vs WINDOM for components



Joakim Högberg a écrit :
One thing to keep in mind here! Not everyone is:

a) Coding in C
Windom2 will be provided as a shareable library useable in C, C++, GFA, Asm, etc...

So it's not an argument.

b) Using Windom

I don't doubt it is a nice feature of Windom, but Windom ain't the only possible route to
take when creating applications.
Of course but it's currently the easiest way to create a modern ( frames, etc...) new application compatible with all the systems.

Right?

The WCOWORK implementation will IMO be a very nice and clean implementation.
Developers just have to use it.

I have not doubts on that but all the things than the WCOWORK mode will provide exist already in windom.

Please, read again the mail of Arnaud.

I'm very happy that a coder like Odd continues to make XAAES better, I thank him, but imho, you need to make XAAES/MyAES more attractive for the MagiC User before to change the API.

Some ideas:
- True Colors icons/mouse cursor support.
- Themes
- New iconification mode ( maybe in a dock like MacOSX or something else ?).
- Widgets in the menu, etc...

After, you do what you want but keep in mind than almost all the developpers don't want to make an software *only* for XAAES.

Ask to the Highwire ( or Tempus Work, Calamus, Aniplayer, ...) team if they want only make their applications only for XAAES... I know already their answers.

For my part, you have my opinion.


For finish, just one question:

You are the author of aicq, right? The next versions will be only compatible with XAAES?


Ciao,
Zorro