From the screenshot on the frontpage it looks like GTK2+, but I can't really make it out.
Doesn anyone know if it is GTK2+ or perhaps a Gnome application?
Printable View
From the screenshot on the frontpage it looks like GTK2+, but I can't really make it out.
Doesn anyone know if it is GTK2+ or perhaps a Gnome application?
The FAQ clearly states that Xtreme is been ported to wxWidgets, which on Linux adequates to Gtk toolkit.Quote:
Originally Posted by amadeus
Greetings from Sweden!Quote:
Originally Posted by prokoudine
I have been using Xara Products for years and love them!
Not reflecting anything on the product, However, I would
hope that you to be a little more understanding when it comes
to technical questions concerning Linux. I myself having just
moved over to Linux, so I would not have known that
wxWidgets = GTK toolkit. :(
I love both my new Linux and I am in Love with this program...
Looking forward to Beta-testing it. The demo works great on
Xandros 3.01 OCE ... :)
Dennis
No, wxWidgets != gtk (at least not quite), see:
http://www.wxwidgets.org/faqgtk.htm
Does that mean the compiled applications actually use native GUI instead of some emulated libraries? When I tried to run Inkscape on Windows, it requires GTK+ runtime, loading Inkscape alone is terribly slow and crashes quickly. In addition, each the floating toolbar is treated like an application under Windows, making the interface a pain to use. If Xara developers decided to do multiplatform, it should use something like Cairo to render canvas, which supports native OS backends.Quote:
Originally Posted by prokoudine
emulated libraries? huh? GTK isn't an emulated library, it's just a set of GUI widgets, wxWidgets (formerly wxWindows) uses it on Linux or BSDs.
What kind of PC do you have? Inkscape loads after a second or two on my PC, is pretty stable, but really really slow.
Got any proof that the toolbars are treated as separate apps? Because my Windows install doesn't see them as such.
They won't use cairo, as their own renderer is much faster. And Cairo only recently got to version 1.0, it's a slowcoach. There's no reason to use Cairo yet and if it doesn't get much faster, I doubt Xara guys will ever use it.
I am running Pentium II 400, on Windows, which runs GTK+ app in emulated mode in Windows.Quote:
Originally Posted by Slapo
I asked Tor Lillqvist about this emulation thingy, here's what he said (used with permission):
"Who would be emulating what? Especially now with cairo, most of the low-level code has been designed cross-platform from the start.
Initially indeed much work in the GTK+ porting effort was caused by the need to "emulate" low-level X11 behaviour, as GDK at first was mostly a thin layer on top of Xlib.
A GTK+ application that behaves pathologically might be much slower on Windows than on X11, because some of the GDK API is trivially implemented on top of X11, but requires lots of work on top of GDI.
GTK+ isn't any more "emulated" than the "native" widgets (the Microsoft "Common Controls", I think they are called) are. Both are built on top of the Win32 GDI.
As to wxWidgets, it uses GTK+ on X11 (Unix), but not on Windows. On Windows it presumably uses the Common Controls.
Well, there certainly are bugs and misfeatures in GTK+ on Windows, for instance related to the concepts of transient windows, window groups etc. This can be irritating indeed in applications that use lots of top-level windows, like GIMP (and presumably Inkscape, I haven't used that). I wouldn't say that "treated like an application" is correct, though. These problems will be fixed eventually.
--tml"
Pretty much says it all, doesn't it :)
Sorry, what do you mean with that? The lower levels of GTK+ on Win32, to a minor extent, can be said to "emulate" some X11 semantics, but I don't know what you mean with "runs in emulated mode"?Quote:
I am running Pentium II 400, on Windows, which runs GTK+ app in emulated mode in Windows.
That said, a PII 400 is certainly not the kind of machine one can expect snappy GTK+ application behaviour on, if the application is much complex at all, or does things in a way which is painful to handle on Win32. On the other hand, my previous machine was a PIII 450, and GIMP was quite usable on it.
I hope not. The GTK2.6 file dialogs are HORRIBLE. If XaraLX uses them it will alienate a lot of users.Quote:
Originally Posted by amadeus
It doesn't have to use GTK2.6 native file dialogs, but I think it's likely, would give it a more consistent look when compared to the rest of gtk apps.Quote:
Originally Posted by hpv
What's so bad about those dialogs anyway? The only thing I miss in there is the actual path, but they're nice (although I use gtk+2.8, can't remember whether it's any different from gtk+2.6 ones).
Use of gtk doesn't mean it has to be dependent on gnome libs.
The current path is right there on the top of the dialog as a series of buttons. You cen get an editable version with Ctrl+L, also don't forget that the file list has type-ahead search.Quote:
Originally Posted by Slapo
That's only your opinion, I find them wonderful as do many other GNOME users.Quote:
Originally Posted by hpv
That's it. Thanks :)Quote:
Originally Posted by Artis
Which acconts for what? Maybe 10% of Linux users and 0% of users who might at some point migrate to Linux?Quote:
Originally Posted by Artis
Switching to gtk2 dialogs is mistake far too many other applications have made and it's an unnecessary barrier to adaption even among users currently using Linux. Xara would be making a huge mistake to adopt it, which they seem to be doing.
You can see what file dialogs it uses, by downloading and trying. Select the Open button or menu. We go via WxWidgets which I would presume uses whatever is the OS standard file dialogs for the appropriate platform. To my untrained eyes it looks as if it uses standard Gnome file dialogs on Gnome and standard KDE ones on KDE (and of course Windows and Mac ones on those platforms).
It's gnome dialogs in KDE.Quote:
Originally Posted by Charles Moir
It's GNOME (or more accurately GTK) dialogs when compiling against wxWidgets WXGTK, MSW dialogs when compiling against wxWidgets WXMSW, Mac dialogs when compiling against wxWidgets WXMAC. You get the idea. If there was a WXQT (which there isn't, due to QT licensing problems) and we compiled against that, you'd get a KDE (or more accurately QT) file-open dialog. If you run the GTK app under KDE, the dialogs look like any other GTK app does running under KDE.Quote:
Originally Posted by hpv
I'm sure the wxWidgets folks would be interested in patches to improve KDE friendliness provided there are no licensing issue involved.
Alex
Which licensing problems are those? Is wxWidgets LGPL or something? That still wouldn't stop them from releasing a WXQT under GPL. gnome file dialogs are a huge turn off for any app though, and the whole gnome philosophy is kind of hurting the Linux desktop across the board. And I really hate to see more applications, especially ones with graphics apps that are almost universally gtk on Linux.Quote:
Originally Posted by abligh
wxWindows license version 3. LGPL with 3 exceptions, mainly for allowing binaries to be distributed without the demand to provide wx with it if it's unchanged, iirc. The other exceptions are backing that up. The license can be consulted directly.Quote:
Originally Posted by hpv
One thing that this means is that we can't put LGPL code in - it would violate their license due to wxWidgets having that exception.
No, it wouldn't. Lack of manpower does. The license concerns can be alleviated through using a different source repository, or strict separation in directories.Quote:
Originally Posted by hpv
That is a matter of opinion. For example I believe the same negative things to be true for KDE, and completely wrong for GNOME and GTK+. This is not the place to express such opinions.Quote:
Originally Posted by hpv
The file dialog concerns are nonsense. They are fixed in GTK+-2.10, and the new dialog was introduced in 2.4. You really don't want to see what it was looking like pre-2.4. That's why wxGTK uses its own generic file dialog if gtk runtime version is not 2.4 or newer - it's considered so much more worse. GTK+-2.8 has it nice, 2.10 will have the location entry in the dialog, not behind a popup box, and will save settings, and not block on networked bookmarks, and other nice things.