I don't know those answers but I hope they have an automated process that reads the C++ headers/source and generates 90% of the bindings. If they don't, it will be really hard to maintain a product this big.
Instead of stopping the development of Qt-jambi all together they should have created an open source project behind it and gradually letting the community to take over it. David. On Sat, Mar 7, 2009 at 8:42 AM, Derek Fountain <[email protected]> wrote: > Switching recent discussion around a bit, can I ask Gunnar and friends > what's actually involved in maintaining Qt Jambi and taking it forwards? > > How much effort do you guys put into the project, say on an > hours-per-week basis? Where, technically, do you concentrate your > efforts? Is the whole thing a fire fight that requires constant work, or > does it basically run itself with just bug reports coming in from time > to time? > > Gregor might be right in thinking my pessimism is ill founded. Can > someone in the know spell out what they think might be required in order > for a FOSS team to maintain and develop Qt Jambi such that it progresses > up to and beyond Qt 5.0? > _______________________________________________ > 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
