On June 19, 2011 10:32:22 AM kfj wrote: > On 19 Jun., 15:55, Yuval Levy <[email protected]> wrote: > > > I've added two skeleton plugins which do nothing > > > > skeleton or ghosts? I did not find any trace of them in the patch. > > sorry, I forgot to issue 'hg add' before 'hg commit'. Here's a new > patch with the three plugins - one of them, shooting_pattern.py, is > the one which was called demo_plugin.py previously. I noticed that the > installation routine only adds new stuff but doesn't seem to remove > old stuff, so you may have to get rid of demo_plugin.py manually. > > http://bazaar.launchpad.net/~kfj/+junk/script/view/head:/main/patch5327
sorry I did not add them to the first beta release - was in a way too advanced state when I saw your message. indeed there are no provision in the CMake build system to remove old stuff. I don't think it is critical. The set plugins that will be distributed with Hugin will be determined once per release (so roughly 2-3 times per year), ideally before starting a release cycle. In between releases there will be other mechanisms to add/remove plugins. This time it is just too new so we will do what we do and learn from the experience. I think dual_use.py and plugin_skeleton.py belong in a different place than where your other plugins are stored and installed. Your other plugins are productive, get installed into the system-wide plugin directory and are accessible through the Actions menu. These two have a different purpose. For now I put them in "plugins-dev", and I commited them only to default. We need to think were to put them. In my opinion they are templates, so maybe we should install them in a subdirectory of the user's home directory. But what will happen when a new user account is created? Another possibility is to have a system-wide plugin-templates directory and a function for the user to copy one into his local plugins directory and start editing. For now I just entered something in the CMakeFiles.txt as a place holder. Thoughts / ideas? Yuv
signature.asc
Description: This is a digitally signed message part.
