I find this post to be a lot clearer in terms of understanding what Joe is getting after than the posts earlier in the thread.
I'm thinking that SQLFORM already takes a lot of the drudgery out of form design, and so I'm missing what Joe thinks is missing. I haven't used the MS web design tools much (studied Silverlight 1.1 a couple of years ago), so I'm definitely not a power user thereof, so I may not have the perspective to evaluate Joe's request. (I'm also out-of-date in doing Android app dev; that doesn't use Eclipse Galileo anymore, but I think there was some similarity between EG and SL design of the visual side.) /dps On Saturday, January 31, 2015 at 9:01:41 AM UTC-8, JoeCodeswell wrote: > > Dear Leonel, > > I agree that you can and *should* do both. For my web2py projects, I am > BOTH Developer and Administrator, *at* *least initially*, before i hand > it over to my user. > > Regarding *my suggestions to improve* the help web2py gives me with the > *Administration > Tasks for my users*, my suggestion is to help *me, as developer,* > customize the web2py Administrative capabilities for them. Possibly > choosing from an easily understood menu of options of say > registration/login types, etc.. > > Regarding *my suggestions to improve* the help web2py gives me with the > *Website > Creation Tasks* *for me as a developer*, I'd love, for example to have a > Form Designer that would generate easily understandable/tweak-able web2py > MVC code, to take the repeated drudgery out of form generation. I am > thinking here, of the process i used to use in Microsoft Development. I > would > > - first, use the MS form designer to help me flesh out my user > interface View, making sure to get user buy in, > - and then, hook that/those View(s) up with Model/Controller code for > implementation. > > > Thanks to all for a GREAT discussion. > > Love and peace, > > Joe > > On Friday, January 30, 2015 at 2:17:51 PM UTC-8, Leonel Câmara wrote: >> >> I strongly agree with Massimo on this. By making administrative tasks >> easier you take that burden out of many developers. Not every developer is >> part of a big team that has one guy just to take care of administrative >> stuff. This is very true in the startup market where I think web2py has an >> advantage. >> >> There's also another point, if you make web2py easier to admin it will be >> easier for different hosting platforms to support it, this can take even >> more admin tasks out of the developers hands (like pythonanywhere already >> does). >> >> There's no conflict between the two, you can work on features for both >> the developers and the administrators, and specially the poor dudes having >> to wear both hats. In the end it's always good for the developers. >> > -- 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 [email protected]. For more options, visit https://groups.google.com/d/optout.
