IMHO there's no point on having web2py serializing by default a structure (response.menu) to a string (the html markup) and then reparse it back to a structure (elements) to move a few pieces back and forth and then reserializing those pieces back to html markup. It's just a waste of cpu.
The way to go NEEDS to be modules with overrides, not server-side DOM manipulations... I agree that right now you can only act on the MENU() function, but a way must be figured out to avoid serverside DOM parsing or we'll soon face an untouchable MENU() that can't accomodate for new features 'cause there are lots of code expecting a fixed html markup. Same goes for forms and widgets: fortunately we have already a formstyle that takes a callback, but I don't see why noone is coming up with a new set of widgets that override the default one composing the html elements the way they are supposed to be in the first place -- Resources: - http://web2py.com - http://web2py.com/book (Documentation) - http://github.com/web2py/web2py (Source code) - https://code.google.com/p/web2py/issues/list (Report Issues) --- You received this message because you are subscribed to the Google Groups "web2py-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to web2py+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
