I am taking this back , After problems with phonon and trying to understand how to compile and fix things in qtjambi I decidet to rather swith to gstreamer-java and in the future probably to eclipse e4/swt for ui if there will be no good c++ maintainer ho will take qtjambi developement. I would rather code more instead of compile a lot of more. Thanks anyway.
On Tue, Sep 8, 2009 at 10:40 AM, Rene <[email protected]> wrote: > I also think that QTJAMBI have a chance , I personaly dont care much about > designer and special tools for exporting because coding gui in QTJAMBI is > very clean with small amount of code when doing well , thanks to css f.e. > and well designed api . I have used SWING in the past and for me it is > forgotten tehnology , and SWT is also far behind QT in features and > development effort . If I will not stop using QTJAMBI and there will be > need I will learn generator and build new version . > > > On Tue, Sep 8, 2009 at 9:07 AM, Gunnar Sletta <[email protected]>wrote: > >> Helge Fredriksen wrote: >> > Dear Eskil, >> > >> > Just to follow up my previous post, are you able to depict something >> > about coming technology changes in the Qt framework that might inflict >> > on the Jambi support for the upcoming Qt releases? >> >> I see Eskil beat me to it, but I'll post my full answer anyway ;) >> >> This really depends on the feature ;) >> >> Most features in Qt come in the form of a new class, function or enum to >> some existing set of API's, thus extending what is there with a little >> bit more. This kind of funcitonality is usually trivial to add to Qt >> Jambi. New functions you will get by default, like for instance >> QGraphicsView::isTransformed(). >> >> New classes are added by figuring out how its used and then specifying >> it as either a <value-type>, <object-type> or <interface-type> in the >> typesystem. Figuring out which is which requires some insight into what >> the difference between the types are, but it quickly becomes >> self-explanatory. >> >> Enums are similarily added by putting the <enum-type> or <enum-value> >> into the typesystem. >> >> This will cover most of the new features to Qt that will come in the >> future. >> >> - >> >> Then there are the "other things"... For instance kinetic / declarative >> UI / QML. I don't know how the final toolchain for this will behave, but >> say that you want to export your custom widgets into this framework then >> this goes via a C++ plugin, so a C++/java integration plugin would be >> required for this to work. Not to mention if this was ever integrated >> into designer, etc... >> >> These bigger features will be quite a bit of work to support, I think. >> At least, they have been in the past ;) >> >> best regards, >> Gunnar >> _______________________________________________ >> Qt-jambi-interest mailing list >> [email protected] >> http://lists.trolltech.com/mailman/listinfo/qt-jambi-interest >> > > > > -- > S Pozdravom / Best Regards > > Rene Dohan > > http://inno.localnet.sk > http://www.qualityunit.com > -- Best Regards / S Pozdravom Rene Dohan http://inno.localnet.sk http://www.qualityunit.com
_______________________________________________ Qt-jambi-interest mailing list [email protected] http://lists.trolltech.com/mailman/listinfo/qt-jambi-interest
