This is an interesting discussion. The theme was also talked about in the thread about the Amy editor.
I am really interested in the concept of collaborative programming. Using a local machine only for development doesn't really work well for this concept. I think segregating the code and databases into a setup of PRODUCTION, TRAINING and TESTING could allow various options in the Admin interface to be turned on or off. For example in PRODUCTION the table editing could be usefull if you simply need to fix a data issue for a user. However making a change to a controller in a production env is NOT a good idea at all. No matter how good your programming skills bugs still get in. And caching is normally in full swing on a production setup. I am really a newbie to web2py but i would find it immensely helpful if I could share a controller I am working with with Yarko or Massimo and they could simply type in the fixes and show me as they type how I should be coding a section. (this is what amy intends doing) I have rambled here a lot but I think Massimo needs feedback on the development env direction. PS. The ability to create autocompletions or shortcodes (ie SF changes to SQLFIELD) in your code and the ability for the editor to show calltips (with syntax) and options for parameters would immensely speed up development and usage of powerful features we don't know about initially. On Thu, Oct 9, 2008 at 5:33 AM, Timothy Farrell <[EMAIL PROTECTED]> wrote: > I understand the inconsistent behavior of not being able to edit modules > via admin. Making changes to module that won't be reflected until something > outside of the admin interface happens encourages bad programming practice. > > I can see the web2py newbies screaming now..."I hit submit, why aren't you > changing!?!?" > > ...meanwhile on the mailing list... > > From: Joe Newbie > To: [email protected] > Subject: Module editing broken > > Whenever I submit changes to a module, it doesn't take effect. Why? > > ...by the 16th of such emails a conflict ensued that engulfed the web2py > community... > > Nah, let's just stay away from that one. > > -tim > > Flamer Disclaimer: By "newbie" I mean someone who does not understand or is > not familiar with web2py. By no means am I implying that anyone would be > incapable of understanding such concepts. > > > mdipierro wrote: > > The problem is that I do not want to clutter the admin interface > moreover even if you could edit modules via admin you should still > restart web2py from the shell to reload the modules. If you are so > advanced to edit modules I think you should use a shell editor. > > Anyway, I am not saying no. Just waiting for more opinions on this > matter. > > On Oct 8, 10:36 am, seeker <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> wrote: > > > Disregarding the location from which Admin is accessed, it still seems > strange to me that I am able to conveniently edit virtually my entire > Web2Py app via admin, but then have to open my modules in an external > editor. > > > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "web2py Web Framework" 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 -~----------~----~----~----~------~----~------~--~---
