Thanks Yarko, we make similar points. I am curious to learn more about how PyPubSub concepts could be applied to help the front-end/back-end development balance in web2py. Could you explain?
More specifically, I am curious how web2py users are rapidly prototyping in web2py now? >From a newish web2py user perspective, I can write that an example where my team would like a decoupling of front (Views) and back-end (Models/Controllers), would be the positioning of forms within apps. Though we would rarely go back to developing in PHP, often it was possible to quickly throw forms around without generating errors, but at the same time get enough functionality to test the user experience of the placement of that form, if not the general layout of the app. No doubt, this shouldnt be possible for a production app, but for rapid prototyping/development, it was very very useful. I Iike the tight MVC paradigm, security, and other good practices built into web2py, but sometimes I wish there was a way to more quickly prototype the front-end, eg test the functionality of SQLFORMS in different views from a user experience perspective, without worrying about this matching the controller side so much at that early development stage. If anyone knows a way of doing this that I have overlooked, and doesnt involve simply copy n pasting html forms, please write. But if this is a bad idea in web2py - even at prototyping phase - please offer a constructive alternative. Though my teams first web2py app is nearly fully prototyped, with about a third of the backend done, I would like to hear how others are rapidly prototyping in web2py while retaining a good balance at allowing for the development of the backend controllers etc as their apps near production standard. Perhaps if it were possible in web2py to switch between a security lenient development phase and secure production phase, a quicker front end development may be possible? Ok, this is probably a stupid idea, but I was thinking back to my php.ini days. ;-) This isnt a rant - just some questions that may help myself, team, and others here - including Dunsun - find ways to find a balance between front and back-end development. I use forms as an example - but I am keen to read of solutions to the quick placement of all other common web app components in web2py. I am guessing that T3 may handle a component layout of on top of web2py, but I am also guessing that eveyone here has some good workflow ideas they can pass on here and now. Perhaps the solution is just to wait for T3 or spend more time planning out the MC side? I hope people have some tricks/tips they can offer as alternatives to this. thanks, Noob --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "web2py Web Framework" group. To post to this group, send email to web2py@googlegroups.com 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 -~----------~----~----~----~------~----~------~--~---
