Noob - I think iterative / rapid is good for layout, look / feel - and forms fall into that.
How to decouple? - My instinct says (for web2py) to make a separate, quick dummy db, and t2 level controllers to serve forms. I know at one time Massimo was working on a simple text layout of data which could also help. I think key is not decoupling controllers, rather decoupling basic form generation from application data development and structure somewhat (have a facade data). But really, what are the form parameters you are wanting to control from a display perspective - those are what can be put up quickly any way you want (non-functioning image boxes could do that?), but being able to control those aspects of the forms in the "real code" is what needs to be easy - then how you prototype layout is irrelevant. For example, if I take the fundamental approach of laying out a page in Photoshop (or Paint.NET is you're using a PC?), and "automatically" converting it to HTML / CSS with a plugin like Sitegrinder.... I should be able to take that, and wrap web2py around that. My thought here is that graphic layout and design is a special skill, often outsourced, and even if not - should be running in parallel --- not necessarily by web2py coders! I am starting from scraping existing sites (converting an existing site, or an empty blogger blog is little different from getting a site layout from a designer / site planner), and seeing what processes this calls for... Regards, Yarko On Wed, Oct 29, 2008 at 11:32 PM, noobpythoncoder <[EMAIL PROTECTED]>wrote: > > 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 [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 -~----------~----~----~----~------~----~------~--~---
