On Tue, Jun 15, 2010 at 8:32 PM, Mathieu Bouchard matju@artengine.cawrote:
[...]
As far as I know, the pd gui rewrite adds the ability for custom tcl/tk
snippets through the command menu. This could be just a tcl call to svn diff.
Ok, so, you have to hunt all over the internet for pieces of tcl code that take 1k each ? Pd has this concept of externals, that are rather plug-and-play (or at least: can be), and then Pd-extended changed the deal and made it no-plug-just-play, and then Pd-devel ("gui-rewrite") would have those snippets of tcl floating around so that you can download your menu-items one by one ? A little bundling would help...
Exactly, please no tcl plugins for pd floating around the net. I see these reasons why having plugins is good for us:
- itsy-bitsy code that was not made up on a declared requirement can (and
shall) make it into the main codebase if it proves sense. A question may be how is it decided - for me it's still better to write up a plugin sometimes than huff'n'puff trying to push something into the svn that no one needed.
- externals, libs have a chance to modify the Pd GUI in the easiest way.
Andras
On Jun 15, 2010, at 10:20 PM, András Murányi wrote:
On Tue, Jun 15, 2010 at 8:32 PM, Mathieu Bouchard matju@artengine.ca wrote: [...]
As far as I know, the pd gui rewrite adds the ability for custom tcl/tk snippets through the command menu. This could be just a tcl call to svn diff.
Ok, so, you have to hunt all over the internet for pieces of tcl code that take 1k each ? Pd has this concept of externals, that are rather plug-and-play (or at least: can be), and then Pd-extended changed the deal and made it no-plug-just-play, and then Pd-devel ("gui-rewrite") would have those snippets of tcl floating around so that you can download your menu-items one by one ? A little bundling would help...
Exactly, please no tcl plugins for pd floating around the net. I see these reasons why having plugins is good for us:
- itsy-bitsy code that was not made up on a declared requirement can (and shall) make it into the main codebase if it proves sense. A question may be how is it decided - for me it's still better to write up a plugin sometimes than huff'n'puff trying to push something into the svn that no one needed.
- externals, libs have a chance to modify the Pd GUI in the easiest way.
Well if this is the case, then why are their no externals to add features that have been asked for before like snap to grid, auto alignment, etc. As far as I can tell, the gui settings people want are as varied as the externals they use. This would provide an easy means to customize the gui without having to load an actual external object into a canvas. BTW I'm talking about the main gui, not just canvas windows with objects. I don't understand how you can have any problem with that as it allows them more freedom to extend the gui to their liking and share the code which could then be included back into pd-extended. Of course you can just turn off all the extra plugins and not change the gui, so what's the difference?
If you don't want the tcl plugin idea, then what should replace it? Special externals? Where are they? Do I need to keep a canvas window open all the time to have my snap-to-grid working?
Then again, I haven't used the gui rewrite build much more then to check it out, so I don't know the details and shouldn't speak for Hans.
Dan Wilcox danomatika.com robotcowboy.com
Woops, sorry. I realize now you already made the points that I was trying to make, albeit more elegantly then I :D I mis read you first sentence ...
On Jun 16, 2010, at 10:28 AM, Dan Wilcox wrote:
On Jun 15, 2010, at 10:20 PM, András Murányi wrote:
On Tue, Jun 15, 2010 at 8:32 PM, Mathieu Bouchard matju@artengine.ca wrote: [...]
As far as I know, the pd gui rewrite adds the ability for custom tcl/tk snippets through the command menu. This could be just a tcl call to svn diff.
Ok, so, you have to hunt all over the internet for pieces of tcl code that take 1k each ? Pd has this concept of externals, that are rather plug-and-play (or at least: can be), and then Pd-extended changed the deal and made it no-plug-just-play, and then Pd-devel ("gui-rewrite") would have those snippets of tcl floating around so that you can download your menu-items one by one ? A little bundling would help...
Exactly, please no tcl plugins for pd floating around the net. I see these reasons why having plugins is good for us:
- itsy-bitsy code that was not made up on a declared requirement can (and shall) make it into the main codebase if it proves sense. A question may be how is it decided - for me it's still better to write up a plugin sometimes than huff'n'puff trying to push something into the svn that no one needed.
- externals, libs have a chance to modify the Pd GUI in the easiest way.
Well if this is the case, then why are their no externals to add features that have been asked for before like snap to grid, auto alignment, etc. As far as I can tell, the gui settings people want are as varied as the externals they use. This would provide an easy means to customize the gui without having to load an actual external object into a canvas. BTW I'm talking about the main gui, not just canvas windows with objects. I don't understand how you can have any problem with that as it allows them more freedom to extend the gui to their liking and share the code which could then be included back into pd-extended. Of course you can just turn off all the extra plugins and not change the gui, so what's the difference?
If you don't want the tcl plugin idea, then what should replace it? Special externals? Where are they? Do I need to keep a canvas window open all the time to have my snap-to-grid working?
Then again, I haven't used the gui rewrite build much more then to check it out, so I don't know the details and shouldn't speak for Hans.
Dan Wilcox danomatika.com robotcowboy.com
-
András Murányi -
Dan Wilcox