True. But surely better organised or prettier prototypes are preferable when prototyping, as they gives a more realistic idea of a final desired layout before the prettifiers get called in!
You can see the effect using just BEAUTIFY at http://www.zgus.com/zgus/products/category_item/1 I don't have the skills or time to make the site pretty. If I start to make money using the site then I will be happy to pay someone to give my drab functional site a really pretty look! What I would really prefer in web2py is a hook in BEAUTIFY and other helpers so I could bypass them and not have my changes overridden every time I do an upgrade. Even a hook in a low level inherited base class would be enough, if using the hook would enable the name of the helper to be determined and to override the helper. However I reckon this is too much to ask! John Heenan On Feb 17, 11:57 am, villas <[email protected]> wrote: > On Feb 17, 12:07 am, John Heenan <[email protected]> wrote: > > > No reaction to including a four line big productivity booster into > > web2py! > > Hi John, > Sorry no one commented! At least I looked at it, and liked it. But > Beautify is only a prototyping & testing thing for most so it's making > something prettier that no one will see. But it's still better, so why > not? +1 > David -- You received this message because you are subscribed to the Google Groups "web2py-users" 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.
