Okay, that makes sense. And if it doesn't produce a bunch of tickets which distract developers, then great.
I guess I would just include a little more up-front explanation in the book or elsewhere so more experienced developers don't get distracted. Such as <bold>Feel free to use your favorite shell and text editor instead of the admin!</bold> or <bold>The db designer is experimental and will not generate full-featured DAL code</bold> But, maybe I'm a minority - web2py is so new to my PHP/MVC head that I'm almost willing to give up my cherished BASH and VIM if there were a good argument for it. On Feb 12, 9:44 am, mdipierro <[email protected]> wrote: > You do not have to use it. I rarely use it. It is not hard to maintain > (the code is very small). I found it very useful in two occasions: > > 1) access a server remotely when no ssh available. It has happened > that a bug showed up during a presentation using a machine not mine > and I was able to inspect the code in real time, fix in in the browser > and people where impressed. > > 2) I use web2py for teaching. More than 50% of the undergrads and > grads when you say "open a shell" they answer "shell what?". I have > had students in CS asking me questions like "ever you have heard of > this thing called Linux? What is it exactly?" or "which editor is > required for your advanced network programming class?". Mind that this > is a minority of people. Most of the students are bright and learn > fast. Still my intent with web2py is not to serve only the brightest > ones. > > Massimo > > On Feb 12, 11:35 am, snfctech <[email protected]> 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. -- 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.
