Shouldn't it say, "an alternative to Qt/Embedded that is also available under GPL terms" ?
Qt/Embedded is dual licensed with the GPL being an avaiable way to license it. IMHO there is no need for an alternative that is an alternative just because it is GPL, Qt/Embedded is good enough.
I have used the winblows version of the Gimp as well AbiWord for Winblows and their respective Linux versions. Something I have noticed is that AbiWord appears to be using the GTK+ widgets under Linux and under Windows it uses what look like native Windows widgets for the windows version. However the Gimp on windows appears as though it is rendering the widgets itself.
Does anyone know what AbiWord does differently? I think I prefer what the windows version of Abiword does to what the Gimp does.
Now what I was thinking was that if GTK+ works by using item factories for the widgets, surely GTK+ could use the native windows button widget, or a GTK+ drawn one, or a KDE/Qt drawn one or someother drawing kits widget sets depending on the item factory used. This would allow KDE widget support from GTK. Themeing of course is an issue when you start to mix things up like that, and it's probably the least important issue, however this would give some added flexability and nicer looking ports of GTK programs to windows.
I really think that a major improvement for the Gimp would be a well done port (using native widgets) to Windows (and probably the Mac too for obvious demographic reasons). This would be leverage to promote GTK+.
Kind of like what Apache has achieved for Linux. People recognise it as one of the predominate web servers that gives you the option to run it on either Windows or Linux (and BSD, etc...). So companies make the choice to use Apache first, then when they have taken that step they then may take the step to using it on Linux.
The Gimp could have an even larger market share with a good Windows and Mac port. I still believe it would be a Linux program. With it's success windows developers may even find their way to GTK+ and Glade and see the light. Even if they only develop GTK based programs from Windows, GTK/GDK and GLib are very well written that portability is not difficult.
This post may be met with scorn at the mere suggestion of using windows to run Linux programs, however don't forget the origins of the GNU project on other UNIX platforms before Linux existed. I see the end goal as being free from the dictates of company interests for all the common tasks performed by developers and users of computer systems in their daily lifes. I don't see Windows ports of Linux programs conflicting with this goal.
Slashdot Mirror
So M$ doesn't like it when the shoe is on the other foot.
I guess Google have been studying and learning from MS.
Is this to imply Qt/Embedded is not GPL?
Shouldn't it say, "an alternative to Qt/Embedded that is also available under GPL terms" ?
Qt/Embedded is dual licensed with the GPL being an avaiable way to license it. IMHO there is no need for an alternative that is an alternative just because it is GPL, Qt/Embedded is good enough.
John
Also try out the cool demo bootable disks here. --- John
I have used the winblows version of the Gimp as well AbiWord for Winblows and their respective Linux versions. Something I have noticed is that AbiWord appears to be using the GTK+ widgets under Linux and under Windows it uses what look like native Windows widgets for the windows version. However the Gimp on windows appears as though it is rendering the widgets itself.
Does anyone know what AbiWord does differently? I think I prefer what the windows version of Abiword does to what the Gimp does.
Now what I was thinking was that if GTK+ works by using item factories for the widgets, surely GTK+ could use the native windows button widget, or a GTK+ drawn one, or a KDE/Qt drawn one or someother drawing kits widget sets depending on the item factory used. This would allow KDE widget support from GTK. Themeing of course is an issue when you start to mix things up like that, and it's probably the least important issue, however this would give some added flexability and nicer looking ports of GTK programs to windows.
I really think that a major improvement for the Gimp would be a well done port (using native widgets) to Windows (and probably the Mac too for obvious demographic reasons). This would be leverage to promote GTK+.
Kind of like what Apache has achieved for Linux. People recognise it as one of the predominate web servers that gives you the option to run it on either Windows or Linux (and BSD, etc...). So companies make the choice to use Apache first, then when they have taken that step they then may take the step to using it on Linux.
The Gimp could have an even larger market share with a good Windows and Mac port. I still believe it would be a Linux program. With it's success windows developers may even find their way to GTK+ and Glade and see the light. Even if they only develop GTK based programs from Windows, GTK/GDK and GLib are very well written that portability is not difficult.
This post may be met with scorn at the mere suggestion of using windows to run Linux programs, however don't forget the origins of the GNU project on other UNIX platforms before Linux existed. I see the end goal as being free from the dictates of company interests for all the common tasks performed by developers and users of computer systems in their daily lifes. I don't see Windows ports of Linux programs conflicting with this goal.