From: Ken O. <ko...@an...> - 2001-02-17 21:30:30
|
Hi Dave, Thanks for the pointer to the tree widgets. I hadn't had a look at those yet. (I only discovered DYN API last Wednesday - and I've been hooked ever since.) Anyway, that interface is more or less what I was trying to achieve. It's doing things in a slightly different way. (I think in a better way - but I'm not sure yet.) So essentially my code example was simply defining a hierarchical menu structure in a similar way to the various tree examples. Some of my goals are: * To be able to build multi-level pull down menus (like Windows applications or the microsoft web site) * Have a standardized (and extendable) interface for a variety of hierarchical selection objects such as pulldown menus, tree selectors, outlook sytle menus, bottom based menus, anything imaginable * Higher level tools (akin to Razor) could use this common interface afford a lot of flexability for skins. For example, one skin chould have pulldown menus. Another skin could have a slide in tree. Another skin could have lamp posts. * As way of quickly wacking out these applications and easily maintaining them something like the XML and XSLT example I posted could be used. Another thought that occurred to me, is that things may be nicely rounded out if popup.js used buttonimage.js as its individual choices. Michael Pemberton had a post very similar to this recently that changed popup.js to use a cell.js. A pulldown menu can be a toolbar that aggregates buttons that spawn popups that aggregates buttons that spawn popups and so on. As a general question, is there any good reason that more widgets aren't part of the 01-25 release? One of the more difficult tasks I'm having ramping up is knowning what widgets are there, what works with what etc. Also, pulling in multiple widgets from multiple people is starting to be confusing. I very much appreciate Richard's ongoing directory standard structure efforts. Are the widgets going to be part of the release in the future (and in CVS)? TTFN Ken |