Sebastian Hilbert wrote: > Hi all, > > Ever wondered how to go about testing your freshly coded plugin without > wanting or needing to bother another developer ? > > 1.) hack your plugin > 2a.) if unsure if it ready for our tree keep a local copy in your tree > without > chekcing in > 2.) alternatively develop it in you test-area directory and place a symbolic > link to the place where if should live (e.g. wxpython) > 3.) Start GNUmed and switch to the setup tab > - note your plugin has not been called until now > 4.) In the setup plugin navigate to the tree branch which reads > current user, current workplace > 5.) add name of you plugin > 6.) restart GNUmed I find at this stage of development quite large changesets are required for new features, to both the business layer and backend, as well as the new plugin file. I would add that it would be wise to publish the output of "cvs diff -U" to this list before committing.
Ian _______________________________________________ Gnumed-devel mailing list [email protected] http://lists.gnu.org/mailman/listinfo/gnumed-devel
