Honestly, folks, I was just having so much fun with web2py last night that I had to share. And it was late enough that my wicked side came out. If it caused some people some consternation, I guess that's what I designed it to do. ;^)
As for sites I've done with web2py, only one is in production, so far. The guts of the proprietary http://www.spinyc.com reservations systems are done with web2py. This has nearly equivalent (and in at least one case more) functionality to google calendar, so it had some elements in it that are acknowledged by the Google team as requiring heavy lifting, such as multiple-interlocking recurring events used for resource allocation. As I stated in a previous post, it took a grand total of 200 hours to complete the entire system single-handedly (including time spent talking with the client, writing specs and doc ... not just code), which is about 3X what I think it should have taken. 3X because (1) it was my first real web2py app, so I was playing around a lot with different stuff to get a feel for it, (2) it was my first calendar app, so I had to get familiar with datetimes and other such python functionality, and (3) because I had to do a complete rewrite mid-stream because the client completely changed the spec and continued to change the spec up until the final delivery date. I'm afraid that if you want to play with the app, you'll have to become a paying member of SPiN New York (if you like ping pong, it's worth it). For my work, I was paid handsomely. I host the reservations from my dedicated server. I almost never check on the app. I figure if it breaks, the client will call me. The client has *never* called me. (I wish they would, 'cause my ego still needs stroking. Darn, no wonder I flunked that enlightenment course I took last year.) The app has made over a thousand paid-for reservations and many more resource assignments since going live in June, and has been responsible for well over $10K in revenue to my client. The rest of the SPiN website (mostly auth and some CMS stuff) is done by 2-3 very competent guys using Ruby. Frankly, witnessing how painfully slow the Ruby stuff came together, I think it's possible I could have been able to do it single- handedly with web2py more quickly, but that's just my opinion. Who knows, the Ruby guys have day jobs and may have been really busy. I'm currently working on replacing a website that I developed by myself a couple of years ago (pre-web2py) using all my own proprietary software. I'm self-taught when it comes to the web, so this other website was heavy lifting for me when I built it, since I hadn't written a program or a website in over 15 years. I'm doing version 2 with web2py and I just got done in a few hours what would have taken me many days to do previously. I have no idea how long it would take with another framework since I've never used another framework, 'cause none of them appealed to me (at the time, they lacked the 3-Cs (and python) that I was looking for and ultimately found in web2py: consistency, conciseness, and completeness). I estimate I could have my entire site redesign from scratch finished in another week, if I wanted to. But I'm dreaming up new functionality and designing the details in a very loving way since it's rev 2 of my baby, so I'm going to take my sweet time. Also, since I work on it only a few hours a week, it'll still take a little calendar time to finish. I'll let this group know about the app once it's ready to go live. I can say, so far, that most of my effort has been in designing css styles and using photoshop to polish my buttons ... not in coding web2py. Which is awesome since that's the part that most people complained about in the older version of my app and web2py makes it easy to design sites top- down (or front to back). Anyway, it seems like my code base is at least a few X smaller than it used to be, but I haven't measured, yet. I'll take a measurement when I'm done and report back. Cheers. And I stick by my earlier statement, web2py is a bad, bad thing. And us native English speakers know that bad is good, and badder is better. In my book, web2py is the baddest. On Sep 1, 1:16 pm, Alex Fanjul <[email protected]> wrote: > Do you have any one o such astounded new websites made in web2py to > check them out? :-D > > El 01/09/2009 4:00, weheh escribió: > > > > > > > I've been using web2py for around 6 months now and I thought I'd share > > a bunch of reasons why I think web2py is a bad thing all around. > > > I used to be an expert at all sorts of things in order to build my > > websites. I developed a whole python infrastructure over a couple of > > years that mostly enforced a MVC development structure. With it, I > > could get a new website, like a photo gallery website, roughed-in in > > under a week. I had a bunch of tricks up my sleeve, written in > > javascript, css, cookies, AJAX, Apache, MySQL, html, XML, and other > > arcane stuff. It was a steep learning curve and frustrating having to > > learn all those different languages, but it gave me big mental muscles > > and a big ego to go along with them. My websites were reasonbly > > consistent looking and did a few nifty grpahics tricks to boot. They > > stood up pretty well to lots of page hits. > > > Now, I only use what comes in the web2py package and my sites look way > > more consistent, do more graphics tricks, and use a ton less code. My > > websites never break and I rarely check in on them to see if they're > > working. They just work. I can develop the look and feel of the site > > before writing the database and controller code. The photo-gallery > > site that took a week to develop ... I can now do in an afternoon. > > Another site that took me months to develop ... I'm on the way to > > implementing it in a couple of weeks. I have so much extra time on my > > hand that I find myself worrying about really dumb stuff, like > > implementing rounded corners on my boxes or getting just the right > > shade of eggshell blue in my background. I thought I still had a valid > > complaint that the web2py doc was thin and incomplete, but now that > > Massimo has come out with the fantastic rev 2.0 of the doc, even that > > gripe has been taken away from me. > > > Now my mental muscles are going flabby and my ego has been deflated. > > Practically any shmoe can now make an excellent dynamic website with > > web2py. Web2py is a bad, bad thing. > > -- > Alejandro Fanjul Fdez. > [email protected] Hide quoted text - > > - Show quoted text - --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "web2py-users" 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 -~----------~----~----~----~------~----~------~--~---
