i really think we shoudl have a port of WxWidgets......it would make it really really easy for a lot of software to be ported to MorphOS....
LINK

it also looks rather portable

FLTK would be my first choice since it's much more light-weight. It's probably a good idea to port this before it becomes too bloated as well :)
A portable widget kit that works on MorphOS as well as X would be really nice to have.

i think WxWidgets would be good simply because MANY pieces of software use it and many of the ones i want use it lol....plus it is more platform independant...(though there is more code).....though i think both of those would be very good to have......but i would poersonaly like WxWidgets first......here are 2 examples of a great piece of software that uses WxWidgets Here and here

I have used (and compiled) wxWindows for both windows and Mac OS X, and must say it´s great.

What´s really great, is that you can strip down what´s going to be compiled so only the things needed is made. So for a port for MUI, one could strip it down just to port the GUI-part only, for starters, then proceed with the other classes as time permits. That is a good structure methinks.

Unfortunately i suck when it comes to configure-files, and makefiles, so i cannot create a new platform tree in wxwindows, but i could make the GUI-code if someone made the initial structure.

I think there is a problem for the moment. The C++ support had been improved recently but I don't know if it's enough to compile big projects.
And these API (wxWindows and FLTK) seem to only use C++.

what would be the bigest problem with the port? and why?

Forget "porting other toolkits". Name me some useful software which would be ported that YOU would use.

And in any event, what's stopping people porting said software, but just using MUI instead of WxWidgets?

If an application is well written to use a specific GUI toolkit, it is usually not very hard to rip out that toolkit and put in another one.

Excuse my irritation, but I wish people would quit posting to forums whining "someone should port xyz GUI toolkit, it would enable many softwares to be ported to MorphOS!!"

Look: if it is that easy, you do it, poundsmack!

If you can't do it, then stop asking for it, you aren't qualifying your requests with any specific applications you wish for support, and I can bet you £5 that there is already a version of some application which is just as capable on Aminet anyway.

We already have too many GUI toolkits. Try writing original software, guys.

I'm jsut throwing things out there for discussion nothing more......i would love to see everything written using MUI......but i am jsut throwing htings out there to see what other people think.......as to the comment of me porting it....i stick to games......and plus i don't htihnk i have the skil for this one...... ....mabey with more practice....(i am not good with C++, i am a python person and an SDL person particularly)

Neko, Poundsmack is not whining. He's just kind of thread creator. He straightly types in what comes to his mind. He just says 'Hey cool, would like to it' but he is not complaining that it's not present.
I actually know that there are some individuals who are complaining a lot but - hey - don't care too much.
Poundsmack's threads are just communication, talk. This is what morphzone was created for. Hang in the bar, grab a drink and have a little talk. Everything's fine as long as noone leaves the ways of civilized communication.

well thank you for the kind words Zylesea

:D
I agree, but it's sure a problem actually. Mui need much more c++ support to easly "remap" othe widgets on its ones.
Bye

Btw, when i compiled it, i noticed the support for IFF compressed images.

Perhaps some of the original developers are pre-amigans?

And just as someone wrote earlier, it is heavily c++ , massive use of classes and templates.

Personally I'm not interested in a port because it would make it easier to port application X. I would like a portable widget kit to use in my own applications to save some development time.

Quote:

I´m not sure i understand you here?

You mean, you are not interested in a port of wxWindows because your own apps doesn´t use it?

It´s really quite simple to convert a Windows application to wxWindows, and make as much as possible ansi-compliant. And you also get possibility to port to Mac and Linux without alot of hassle.

I used this great tool for dialogmaking: Dialogblocks


I converted my own app, consisting of approx 240 sourcecode files, and about 30 dialogues, during 1-2 months of work. (and made a MUI version too, but couldn´t finish it completely as the Mac version had more priority)

As someone wrote earlier, perhaps a parser tool that converts wxWindows GUI-code to MUI-equivalents is simpler.

like this:

wx2mui mydialog.cpp mydialog.h mymuidestinationdlg.cpp

And it would transcribe the code to MUI.

anyway, this is just ideas..

I don't care which widget kit is ported to use MUI as long as it's available on X and OSX. Spending 1-2 months rewriting GUI code in an application for MUI is a large investment. I just want a kit that supports MUI, X and OSX from the start. If it is wxWidgets, FLTK, GTK+ or any other doesn't matter as much.

Isn't MUI available on Linux ?

I found some old unmaintained code that I couldn't get to work. It was also missing a lot of components. I think Zune was based on the code I found.
Anyway, porting MUI to X is not the answer. A widget kit made to be portable should be ported to MorphOS instead. Otherwise you would also have to adapt MUI to OSX and other platforms as well.

Clarification, i spent 1-2 month on porting the whole software, not only the GUI, it was only a part of it.

Expected porting time from the company i work at was 6-12 months for a early beta, and my final release was finished after 1-2 months.

The point being, wxWindows really is a smart toolkit, as it is native GUI objects for every os, it´s not looking like X or like Windows on other platforms.

Also the mailinglist is great, and the ppl are helpful to say the least.

Afaik you can also port your software to cellphones through wxWindows..

Quote:
No

yes through WxWidgets you can do increadible things......i would love to see morphos added to the platforms they suport.....i wonder what would happen if we emailed them asking nicely if they would suport MorphOS.....hmmmmm....(runs off to hotmail)

I am pretty sure they don´t have the time. As their time has always been limited.

However what could be an idea is that they create a clean tree for morphos / amigaos, with empty classes, or how it works when supporting a new platform.

That way, anyone with some spare time could add some classes functions whenever time permits.

Just happened on this thread and it raised some questions for me.
1) I read that the gcc version on MOS does not support templates and other C++ functions properly, is that true? Some code I use is very heavily templated Was there any communication from the MOS team telling this support will be integrated?
2) Sounds like a lot of people are willing to help make the wrapper, I doubt the wxwidgets team itself will have time for it. But it is an open source effort, I have no doubt they would welcome an effort.
And finally a remark. Yes of course it is nicer if apps are written in MUI, but for many cross platform developers having to do that just means there will be no MOS port at all. If it would just be a matter of putting the crosscompiler to a MOS target they might be much more inclined to do ports for MOS and the platforms viability would rise enormously.

Templates are buggy in GCC 2.95. GNU's STL seems to work properly, but forget about Boost or STLPort. We require GCC 3.x in order to have proper template handling but according to what I've heard there are some issues with GCC 3.x on MOS. I hope this will be addressed together with MOS 1.5.
Hopefully your templates will work with 2.95.