HTML::PopupTreeSelect 1.0 is out. There's certainly room for improvement, but so far it seems to be working well as an xTree replacement in my current project. I've got a live demo of the code running here.
Very slick, but it needs to be movable/ scrollable. Otherwise, when a tree is larger than the browser window, the OK/ Cancel buttons aren't readily accesible. I tried tabbing to the OK buttong, but I wasn't sure of how many things were in the tree, and thus unsure of how many times I'd need to hit tab.
Patches welcome. I know how to make it movable, but I think scrolling might require an iframe. I've had some bad iframe/CSS-positioning experiences in the past...
in your CSS for some outer-level div or something. (I haven't looked at the module's output, just read the discussion in the journal.)
See the third example at http://hotwired.lycos.com/webmonkey/98/15/stuff4a/overflow.html
This will work in css-compliant browsers, but probably have no effect in browsers which don't grok auto overflow. If you want to appease some of those older browsers, you'd have to do iframe, but if you go far enough back, iframe won't be understood
I have to ask, did you look at DynAPI [sourceforge.net] ? Probably the most the most powerful cross-browser implementation of object-orientated javascript.
I currently use it do explorer style navigation trees, pop-up boxes, drag and drop among a whole host of other features.
I simply write one javascript file to create the layers and build functions, which neatly tie into DynAPI. Then I use Template Toolkit to loop through my hashes and sundry variables, which creates simple javascript calls in the HTML page, to those buil
It would be *very* nice to have a single JSPAN rather than the many javascript code sites that there are.
Did you think that's why I wrote it?
No, I kinda figured you might had a need for it, but just hadn't found the right tool for the job. Personally I'm always a bit wary of putting JS code within Perl, as it can be too easy to mess quoting up, let alone confuse another reader. Plus it can be a pain to debug sometimes.
My suggestion for splitting things up, was simply to point out that if you did want
Impressed (Score:1)
Nice work (Score:2, Interesting)
Re:Nice work (Score:3, Interesting)
-sam
Re:Nice work (Score:3, Informative)
in your CSS for some outer-level div or something. (I haven't looked at the module's output, just read the discussion in the journal.)
See the third example at
http://hotwired.lycos.com/webmonkey/98/15/stuff4a/overflow.html
This will work in css-compliant browsers, but probably have no effect in browsers which don't grok auto overflow. If you want to appease some of those older browsers, you'd have to do iframe, but if you go far enough back, iframe won't be understood
Re:Nice work (Score:2)
Thanks,
-sam
DynAPI (Score:1)
I simply write one javascript file to create the layers and build functions, which neatly tie into DynAPI. Then I use Template Toolkit to loop through my hashes and sundry variables, which creates simple javascript calls in the HTML page, to those buil
Re:DynAPI (Score:2)
Did you think that's why I wrote it? Nope. I needed it and I couldn't find anything that would do the trick.
Now who's trying to do
Re:DynAPI (Score:1)
No, I kinda figured you might had a need for it, but just hadn't found the right tool for the job. Personally I'm always a bit wary of putting JS code within Perl, as it can be too easy to mess quoting up, let alone confuse another reader. Plus it can be a pain to debug sometimes.
My suggestion for splitting things up, was simply to point out that if you did want