> > On Mar 8, 1:09 am, weheh <[email protected]> wrote: > > > > I've read that this is possible with t2, but how about 1.57? I've > > tried it with 1.57 and it doesn't seem to work. Any suggestions for > > how to do nested multi-level menus with the current version?
On Mar8, 11:38pm, mdipierro <[email protected]> wrote: > The problem is that we do not want to include too many JS libraries > with the base distribution. Everybody has his/her own preferences when > it comes to menus. I would have agree with Massimo about "not to include too many this and that in the base distribution". But, when talking about the menu, I beg a reconsideration. Because menu is such a basic need in almost every web application. I still remember years ago when I just began to develop my first web app based on another "lightweight" web framework, soon I had to pause the app development and dived into many javascript, css things to make my first menu system work. It was painful. So you can understand I am so happy when I start to use web2py and find out that it comes with a decent and easy menu system (although not multi-level). I almost do not need to touch any javascript but I can still finish more and more apps. I call this PRODUCTIVITY. So I do suggest web2py to have a multi-level menu system (while keeping the current response.menu definition for backward compatibility). It can benefit most common developers, and the rest can customize their own menu anyway. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "web2py Web Framework" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/web2py?hl=en -~----------~----~----~----~------~----~------~--~---
