RE: [SMARTY-DEV] Re: Debug Console

I agree w/ staying w/ open source for Smarty. Whether this should be included w/ smarty shouldn't be decided until a plugin is actually developed. I'm already seeing possible problems w/ the data which, I think, may make this a poor smarty plugin canidate. For insance, to iterate through the multidimentional array I'll need to use a recursive function. Because of this, node names will need to be automaticly generated, but for a user to use the tree inteligently I think they may need to have finer contorl of the node names.....more to come. -----Original Message----- From: Monte Ohrt [mailto:monte@ispi.net] Sent: Wednesday, May 21, 2003 3:53 PM To: Tom Anderson Cc: 'Tom Sommer'; 'Smarty Dev' Subject: RE: [SMARTY-DEV] Re: Debug Console I'm just thinking out loud, currently there is a {popup} function bundled with Smarty which uses overlib. I don't know if we should continue that formality or not. If we use {treemenu}, then respectively we should use {overlib} instead of {popup}. Hindsight 20/20? :-) Should this be bundled in the default distribution? I kind of like the idea of bundling useful things, it makes Smarty more attractive when it makes life easier... especially powerful things like making javascript menus simple to implement. And of course, no penalties for adding more power since it's a plugin. I actually have a plugin that uses a commercial product for creating dropdown menus called CooljsMenu Pro (http://javascript.cooldev.com/scripts/coolmenu/). The only thing stopping me from finishing it and releasing it is that CooljsMenu Pro is not open source. They also make a product called CooljsTree Pro, which is very similar to nanotree. I like the idea of sticking to open source. Monte On Wed, 2003-05-21 at 16:23, Tom Anderson wrote: > {nanotree data=$array showRootNode=false sortNodes=false > dragable=false} was my idea. > > function.nanotree will mostly echo out a lot of javascript. A > {treemenu} type function would need to call another function to process the nanotree. > Options would likely be different for the various tree menues too. I > think, until another tree comes around, we should stick w/ {nanotree}. > A {treemenu} wrapper could be added later... > > -----Original Message----- > From: Monte Ohrt [mailto:monte@ispi.net] > Sent: Wednesday, May 21, 2003 3:24 PM > To: Tom Anderson > Cc: 'Tom Sommer'; 'Smarty Dev' > Subject: RE: [SMARTY-DEV] Re: Debug Console > > > How should it work? Something like: > > {nanotree ...} > > Or something more flexible, like: > > {treemenu type="nanotree" ...} > > where nanotree is the default type? > > Monte > > On Wed, 2003-05-21 at 16:10, Tom Anderson wrote: > > I'll do it....shouldn't take long at all. > > > > -----Original Message----- > > From: Monte Ohrt [mailto:monte@ispi.net] > > Sent: Wednesday, May 21, 2003 3:13 PM > > To: Tom Sommer > > Cc: Smarty Dev > > Subject: Re: [SMARTY-DEV] Re: Debug Console > > > > > > This would be a very useful plugin, FYI. Anyone up for the task? > > > > On Wed, 2003-05-21 at 16:06, Tom Sommer wrote: > > > On Thu, 15 May 2003 12:23:54 +0200, Luca Borrione wrote: > > > > > > > One of these modifications was about the debug console. Now, > > > > after some months since the original idea, I finally found time > > > > enough to reach a > > > > > stable version of it. It's not finished, but I have no time now > > > > to go > > > > further on it. > > > > > > Have a look at http://nanotree.sourceforge.net :) > > > > > > -- > > > Tom Sommer, Denmark > > > www.tsn.dk - www.dreamcoder.dk > > -- > > Monte Ohrt <monte@ispi.net> -- Monte Ohrt <monte@ispi.net>