I believe the only reason for putting something like this in the db is so the user can configure it.
I can see where that might be useful, but have you considered what the user interface will look like? Following the principle of least surprise, it should look like a generic file manager tree such as you would see in Nautilus or Dolphin or Windows Explorer. You'll need some Javascript code for that and I believe these functions won't be provided by Web2py's normal js libraries. On Tuesday, July 10, 2012 4:05:42 PM UTC-4, Alan wrote: > > thank you for the code villas, will have a play. > > i didn't think my attempt was for anything complicated personally, i just > wanted to output an array in the same syntax as response.menu but with all > results coming from a single 'page' table in a database. > I was trying to think of the best way round multiple database lookups for > child elements and hitting any snags with menu levels, which led me to the > link in my first post. > > i wanted to really make something unique from any plugins that can just > use the in-built MENU(), so that it is a small app with few dependencies. i > also had an issue referencing part of the markmin stuff inside the plugin > (can't remember what now) which is what led me down the diy route. > also had delusions of grandeur on making this a simple (to end user > anyway) cms app that uses as much of the core as possible. >
