I use the built in editor heavily. Lots of my web2py coding is done on a chromebook, so it's completely perfect for me.
Be really hard if it worked any other way than this. On Friday, 12 February 2010 17:35:49 UTC, snfctech wrote: > > I'm just getting started with web2py and I must say - I love the > code. Adding validation logic with the DAL and building forms on the > fly with the CRUD helper is awesome. > > That said, I don't understand the point of the admin interface - > especially the online database designer and the editor. The online > database designer doesn't generate 'upload' types (and I imagine other > DAL specific syntax, as well). And the editor is too weak for any > serious coding. > > So why does this extra fluff exist at all, as it will require > resources to maintain and enhance? Not to mention it adds more > unnecessary options for new users wondering about best practices for > web2py development. This doesn't seem in keeping with "there should > be one obvious way to do it." > > The only thing I can think of why things like the editor and designer > exist at all is to promote the "full stack" idea. But is it really > worth the effort to include sub-standard tools in the stack which you > will have to abandon anyway once you start serious development work? > > Thanks in advance for helping me to understand the reasoning here. > > -- 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/d/optout.
