For Pd-extended, I'd much rather keep it as a plugin than make it an internal file. I think it will be much easier for you to work on the search plugin if it stays as a plugin. If its a plugin that's included in Pd-extended, it can be upgraded by the user by just dropping a new version into ~/pd-externals. The dev process will be easier too, since updates won't have to go thru the patch tracker to be accepted into pd-extended.git.
For Vanilla, you'll have to ask Miller. I think this same approach could work for vanilla too with the same advantages. All that Miller would need to do to include it is check in the search-plugin into pd/extra/
.hc
On 11/15/2012 01:45 AM, Jonathan Wilkes wrote:
I already did substantial work on the drop-in replacement for the helpbrowser based on the feedback I got. I had no idea the gui-plugin infrastructure was ready to ship actual plugins running by default in pd-extended.
-Jonathan
----- Original Message -----
From: Hans-Christoph Steiner hans@at.or.at To: "pd-dev@iem.at List" pd-dev@iem.at Cc: Sent: Wednesday, November 14, 2012 11:31 PM Subject: [PD-dev] search plugin in Pd-extended
Hey Jonathan,
I committed your latest search-plugin.tcl into scripts/guiplugins/search-plugin, overwriting my original, simple one. I put it there because I'm adding it to Pd-extended. I think it makes sense to just include your plugin directly rather than as a remixed helpbrowser.tcl. I also just committed a check that makes sure that pd-gui doesn't try to load a plugin that has already been loaded. That way when you make new version of the search plugin, people can just drop it into ~/pd-externals and it'll override the built-in search-plugin.tcl.
As for scripts/guiplugins/search-plugin, feel free to take that over and do whatever you want with it. I can't see a reason to keep the old one around any more, your search plugin is very thorough.
.hc
Pd-dev mailing list Pd-dev@iem.at http://lists.puredata.info/listinfo/pd-dev