1) JNI = pain 2) Command line - means it will be easier for you to test and reproduce. 3) Using an external command also means the build dependencies of QtCreator will be smaller.
I am no QtCreator dev... but I would recommend using an external "3rd party" app. On Wed, Oct 1, 2014 at 8:14 PM, <[email protected]> wrote: > I've started (sometime ago) to develop a plugin to QtCreator to work > with Tfs. > > My initial idea was using TEE (Team Foundation team Everywhere - which is > java based) command line. But when I've started to code a "CloneWizard", > I've realized that Tfs command line (tf.exe/tf.bat) doesn't list Tfs > collections (user's can choose an project in a list?). > > Team Foundation Everywhere 2013 has a Java SDK similar to .Net classes. So > I can write some java code to use Tfs capabilities (like list collections). > > But I wanted the opinion of you. > > Do I Write a java command like to list the information that I need? (this > option makes the plugin like others plugins - like mercurial, subversion - > that relies on external programs) > > or > > Do I Load a Java VM in memory (via JNI) and use the Tfs classes directly? > (this option will speed the use of Tfs - java command line has slow startup > times on some machines. But QtCreator will load a JavaVM in your memory > space.) > > > > > > > > > > > > > > > _______________________________________________ > Qt-creator mailing list > [email protected] > http://lists.qt-project.org/mailman/listinfo/qt-creator > >
_______________________________________________ Qt-creator mailing list [email protected] http://lists.qt-project.org/mailman/listinfo/qt-creator
