@Karlos:
As I told you in a message, that would be a great idea...
I think we should look other GUI libraries from other platforms (like gtk, QT,etc) and then look at our libraries and try to make similar functions... I think that writting similar functions to QT etc would be an added bonus because it would allow programmers to port more easily software...
Firstly it should include the basic components shown as default in VBasic and other IDEs for example: Listers, buttons, textboxes,etc...
"My gut feeling is that a lot of (especially new) programmers are slightly put off by the way these guis are implemented."
Yeah! that's it! A Reaction wrapper for AROS would be really cool, but we need to attract new programmers to our platform. Windows wouldn't have so many programmers if they had to write every GUI like we have to...
And about using MUI for everything... this new Wrapper-API would use similar functions as other toolkits like QT etc, making porting easier...
@Karlos:
I don't know much about reaction, but don't hesitate in sending me a message to talk about the specification, I'm quite interested...
@jaokim:
Using includes or a library wouldn't be similar? After all, it will only be a wrapper that translates the new API calls to Reaction/MUI/Whatever... (even gadtools would be possible)
@Karlos:
It would be possible to make the linkable library first and then once it works correctly turn it into a dynamic library?
@Bloodline:
"Then I think one should be asking oneself, why one would hate MUI...?"
That question may turn this thread into a flame-fest... :-D
Simply accept that not everybody likes MUI.