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
