Well as a test I got my new designer to try using web2py without any help from me, he was successful so that was one bonus point.
Second if you were to look at the code base from 4 developers which 2 had python background, one PHP, and the other Java, you can imagine how bad the code is running the site. So the primary reason is pyramid gives you to much freedom, and forces you to do way to much manual work yourself. The freedom is good when everyone on the team is VERY strong with python, however it causes more problems when trying to teach someone and launch a product at the same time. Oh and I forgot my main pet pev with pyramid is it has way to many dependences on 3rd party packages, making it very hard to track down bugs. Finally, since the company launched it is been brining in a lot of money and has to many feature requests to continue reinventing the wheel with pyramid (IE: spending to much time developing things web2py already has) We needed more security, a faster development cycle, easier internationalization support, and tools that allow designers to work faster. Don't get my wrong I have projects I have developed running on pyramid (invoicing system), and django (dating site, personal journalling app where daily journal entries are encrypted) that are clean and easy to work with etc... However, my projects are getting bigger and more demanding, so far I am liking web2py more then django and pyramid. I am also developing a fitness application using web2py I will post a link once we get the new brochure up and running. On Fri, Jan 13, 2012 at 8:14 PM, Anthony <[email protected]> wrote: > Glad it worked. Out of curiosity, what prompted you to move from Pyramid > to web2py for this app? > > > On Friday, January 13, 2012 10:59:43 PM UTC-5, Detectedstealth wrote: > >> Thank you Anthony, >> >> That works exactly how I was want. I didn't even think to use >> request.vars. Just trying to see how many different ways this is going to >> save my team development time. >> >> We are moving youadworld.com from pyramid to web2py here is the start so >> far if you are interested in watching the progress: http://176.34.12.39/ >> >> NOTE: There will be LOTS of changes and the database will be deleted and >> rebuilt often over the next few months. youadworld.com however is live >> and free to register to see what the current functionality is, and will be >> in the new version with web2py. >> >> On Fri, Jan 13, 2012 at 2:47 PM, Anthony <[email protected]> wrote: >> >>> db.define_table('user_account'****, >>>> .... >>>> ) >>>> db.define_table('distributors'****, >>>> Field('account_id', db.user_account), >>>> Field('uadpoints_balance_**avail**able', 'integer', default=0), >>>> ) >>>> db.define_table('ads', >>>> Field('member_id', db.user_account), >>>> Field('points', 'integer', default=0), >>>> ) >>>> db.ads.points.requires = IS_INT_IN_RANGE(0, >>>> db(db.distributors.account_id=****=db.ads.member_id).select()[0]**** >>>> .uadpoints_balance_available) >>>> >>> >>> If 'ads' records will be added via form submission, then you might try: >>> >>> db.ads.points.requires = IS_INT_IN_RANGE(0, >>> db(db.distributors.account_id=****=request.vars.member_id).** >>> select().first()**.uadpoints_**balance_available) >>> >>> You might want to set this in the form controller only when request.vars >>> is not empty to avoid unnecessary db hits. >>> >>> Anthony >>> >>> >> >> >> -- >> -- >> Regards, >> Bruce Wade >> http://ca.linkedin.com/in/**brucelwade<http://ca.linkedin.com/in/brucelwade> >> http://www.wadecybertech.com >> http://www.warplydesigned.com >> http://www.**fitnessfriendsfinder.com<http://www.fitnessfriendsfinder.com> >> > -- -- Regards, Bruce Wade http://ca.linkedin.com/in/brucelwade http://www.wadecybertech.com http://www.warplydesigned.com http://www.fitnessfriendsfinder.com
