is the endgame really let response.menu generate a structure than is
converted every time server-side ?
Shouldn't we avoid server-side dom at all costs ?
On Friday, December 13, 2013 3:21:28 PM UTC+1, Paolo Caruccio wrote:
Thank you LightDot.
In the next few days I'll send to your private
Well we could convert the menu on client side but I found several ugly
rendering issues.
And why we should avoid server-side dom? I think that it is an interesting
web2py feature.
However since your opinion is important for me, do you think the following
function might have a bad impact
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
Thank you Niphlod. I see what you mean. I'll try to convert my code in
order to build a custom formstyle. However, I'll share my code with the
web2py users group: maybe it could be useful to someone.
About the menu, I have in my mind a simple change to the MENU helper that
should semplify its
Most of the work already done on bootstrap 3, foundation 5, etc. can be
reused. The DOM manipulating parts are also bound to be useful - as an
example of what can be done, if nothing else.
I'm using the plugin_layout_cssfw functionality to keep bootstrap 2 3,
bootswatch 2 3 and foundation 5
Can you please open a ticket about this so it does not get lost? We need to
port welcome to bootstrap 3 asap.
On Thursday, 12 December 2013 12:08:15 UTC-6, Annet wrote:
Some field definitions in my models have comments, which in a Bootstrap
form are
being displayed in a help-block.
The
6 matches
Mail list logo
