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 if it runs it will show up, if not check the logfile Happy hacking -- Sebastian Hilbert Leipzig / Germany [www.openmed.org] -> PGP welcome, HTML ->/dev/null ICQ: 86 07 67 86 -> No files, no URL's VoIP: callto://[EMAIL PROTECTED] My OS: Suse Linux. Geek by Nature, Linux by Choice
new_plugin.png
Description: PNG image
_______________________________________________ Gnumed-devel mailing list [email protected] http://lists.gnu.org/mailman/listinfo/gnumed-devel
