Well for me it is in this order QtJambi , Swt , Swing . Yes Qtjambi is abandoned and Swing in my eyes also .Try to create tray icon or something special in swing and you will be burden in problems . Also api of Qt Jambi is very clean for me and you can write far less code and more readable code. Qt 4.5.2 is pretty stable and maintained , and look at ages old bugs on Sun site, that will never be resolved . Well Sun did not put much effort to their desktop library for years.
I have created few desktop applications in swing some time ago , now I am using QtJambi and I am ready to switch to swt if there will not be person who will be able to understand that C++ part of QtJambi. On Tue, Jan 5, 2010 at 5:18 PM, Bruno Wouters <[email protected]>wrote: > Hi all, > > > > Thanks for the responses! > > It helps a lot but is it still a difficult choice. > > > > This is my current idea about the frameworks, please correct me if I’m > wrong.: > > Swing seems to be the safest with the same rendering on each OS but may not > have the look & feel of a native application. And it has the most libraries > for things like charts etc because it exists longer that other gui > frameworks. > > SWT is faster than swing but could give some problems as new operating > systems appear. (has/had problems with Mac OSX 64bit) And it also could > render certain gui elements differently on different operating systems. > > Qt Jambi is probably the least safe choice because Nokia stopped > development and the community still needs to grow. > > > > Is it correct to assume that I will have the least amount of maintenance > with swing? (with new operating systems etc) > > Does swing work well for multilingual gui’s? (also right-to-left) > > Are there any must have libraries/frameworks to use with swing/swt? > > > > Thanks again! > > > > Kind regards, > > Bruno Wouters > > > > PS.: Happy new year! > > > > *From:* Helge Fredriksen [mailto:[email protected]] > *Sent:* vrijdag 1 januari 2010 21:50 > > *To:* Bruno Wouters > *Cc:* [email protected] > *Subject:* Re: [Qt-jambi-interest] Some questions about Qt Jambi > > > > Hello, > > And a happy new year, all Qt Jambi interests! > > Just some more additions to the discussion about the difference about > Qt Jambi vs. Swing (don't have so much experience with SWT) > > * Although Swing is getting better "under the hood" as you say, there > aren't that many additions to the API itself, although you may of course > take > advantage of Swing based third party Open Source APIs like JFreeChart > etc. > * Qt Jambi has the big advantage of getting for "free" all the new > advances in > Qt. Especially, this is something you really should acknowledge for the > QGraphics* classes which allows you to build highly complex 2D graphic > system. > And now, with the new Animation and Gesture APIs, things are looking > quite > awsome for creating advanced graphics applications. > * Since QtJambi is a fairly thin layer between Qt and Java, you get a very > high > performance on your app. Especially on the latest versions of Qt, they > have > been focusing on performance a lot due to the adoption to mobile > devices. > If you were to build a framework like QGraphics* on top of Swing for > example > I think you would see problems getting the kind of performance see in > Qt Jambi. > * Qt Jambi has the possibility to build bridges between existing Qt C++ > apps/APIs > and Java. For example, one could imagine that the effort wouldn't be > that > hard to build a Marble Jambi widget and a QWT for Jambi component. > There > really are a lot of nice components to port. > * The community is still very small, and we haven't come very far in > setting up > a community site, setting up releases for download etc. One still has > to > either use the last binaries that Nokia built for 4.5, or to build your > own > stuff on 4.6 using the build descriptions found on gitorious.org. > However, > I think this will change shortly. The best thing, however, would of > course > be if someone saw this as a business opportunity. That is, one could > agree > to pay a support fee to such a company and in return get help on Qt > Jambi > if your application development ran into some kind of trouble. To get > an > official commercial maintainer for Qt Jambi would really mean a lot of > security for the framework audience. Just think about it; Qt Jambi is > really > a worthy challenger to Swing, and could be the next big thing for > building > cross-platform graphical desktop applications in a high-level language. > That > demands for quite a bit more attention to the marketing side, > especially in the open > source community. > > Looking in the crystal ball: > > The community will support the Qt Jambi framework more or less as is, > enhancing it > with new features (which will not be many towards 4.7 as was stated in the > DevDays) until at least 5.0 arrives (probably in 2-3 years). After that, > there is > an open question what will happen to Qt, if the Qt people will invent > something > what breaks the way Qt 4 is build up. This was the case when they moved > from > Qt 3 to Qt 4, but that stirred so much frustration that they had to commit > to > "We will never break your code again". Thus there is a legitimate hope that > > Qt Jambi will have a happy life supporting the new Qt features for many > many > years to come! > > PS: To prepare some release activity on Qt Jambi 4.6, I have been playing > around > with some project creation on SourceForge. Not much there yet, please > comment > if you like. We are also looking into the oppertunity of using Atlassian > Jira, but > we're struggeling a bit with the hosting side here. > > PS2: Please join in on the on #qtjambi on the Freenode IRC server for those > of > you who want to chat! > > Best regards, > Helge Fredriksen > > > Bruno Wouters wrote: > > Hi Tom, > > > > Thanks for the fast response! > > > > Which UI framework do you think has the most secure future in terms of > > compatibility with new operating systems and fixing bugs? While searching > > the net I found that there were a lot of people saying that Swing isn't > > updated for about 10 years or so. Is this true? > > > > I think it will be a choice between SWT or Qt Jambi... Not sure which one to > > pick... > > > > The UFaceKit you pointed out also looks interesting but then I still need to > > choose a UI framework to start with :-). Will UFaceKit work with things like > > charts? Or more advanced stuff like drag & drop? > > > > Kind regards, > > Bruno Wouters > > > > > > -----Original Message----- > > From: Tom Schindl [mailto:[email protected] <[email protected]>] > > Sent: dinsdag 29 december 2009 10:45 > > To: Bruno Wouters > > Cc: [email protected] > > Subject: Re: [Qt-jambi-interest] Some questions about Qt Jambi > > > > Hi, > > > > Not sure what to suggest when it comes to whether using Qt-Jambi in > > commercial product but there are alternatives naturally: > > > > * Swing > > * SWT integrates nicely on Win32 and MacOS-X as well as on Linux-Gnome > > > > I can point you also to a project I started some time ago named UFaceKit > > [1,2] which is hiding the real toolkit behind a facade and so allows you > > to defers the choice of the UI-ToolKit. > > > > LGPL is a quite commerical friendly license and even if you modify > > LGPL-Code you only have to contribute back the modified code and NOT > > publish your own (but I'm not a lawyer). > > > > It's really a bitty that Nokia took this step and on the other hand > > invested into a Qt-eSWT-Port on the other side. Please note eSWT != SWT. > > > > Tom > > > > [1]http://wiki.eclipse.org/UFaceKit > > [2]http://tomsondev.files.wordpress.com/2009/10/slides1.pdf > > > > Am 29.12.09 10:20, schrieb Bruno Wouters: > > > > Hi all, > > > > > > I'm considering to use Qt Jambi for a new project. Is this a good choice > > knowing that Nokia decided to discontinue development of it? Is the open > > source community large enough to keep it alive/up to date? > > > > Are there other, better choices then Qt Jambi for a java application > > that is going to be deployed on Windows and Mac OS X? It will be a > > multilingual (also right-to-left languages) application taking care of > > some administrative tasks (quite simple gui). > > > > And can I use Qt Jambi under the LGPL license (without changing the Qt > > Jambi code) in a commercial application without providing the source > > code of it? > > > > > > Thanks for your time! > > > > > > Kind regards, > > > > Bruno Wouters > > > > > > > > _______________________________________________ > > Qt-jambi-interest mailing list > > [email protected] > > http://lists.trolltech.com/mailman/listinfo/qt-jambi-interest > > > > > > _______________________________________________ > > Qt-jambi-interest mailing list > > [email protected] > > http://lists.trolltech.com/mailman/listinfo/qt-jambi-interest > > > > > > _______________________________________________ > Qt-jambi-interest mailing list > [email protected] > http://lists.trolltech.com/mailman/listinfo/qt-jambi-interest > > -- Best Regards / S Pozdravom Rene Dohan http://inno-a-dev.blogspot.com http://inno.localnet.sk http://www.qualityunit.com
_______________________________________________ Qt-jambi-interest mailing list [email protected] http://lists.trolltech.com/mailman/listinfo/qt-jambi-interest
