You make some good points in this. I wonder if I might add some observations?
1. Your problems with SQLObject - could you go in to a little more depth with this? As a long-term PHP programmer I think we had a similar experience. I too was angered by SO when I was treating it as an SQL layer, however when I stopped doing that and took a more Pythonic approach, things became a lot easier, although I'm unconvinced as to whether my queries are being executed efficiently. However I would always use SO when I'm not 100% concerned by efficiency. I recently re-wrote an in-house application that I was revisiting to use SO. 2. I think your problems with Kid stem from not having much experience in HTML markup. Believe it or not, HTML is well-defined standard that not a lot of people understand. About a year ago in my office I began enforcing a policy of valid xHTML as much as possible. We installed HTMLTidy on everyone's firefoxes, and encouraged people to constantly check that pages produced no errors. Since we only do xHTML, this means we're extremely used to writing well-formed XML. Because of this I have absolutely zero problems with Kid, as it appears to me to be standard xHTML + a couple of extra attributes in the py: namespace. I think if you spend more time working on "websites" you will develop a greater appreciation for xHTML, the benefits of actually writing real HTML (as opposed to the trash that most people spew out), and in turn, a greater appreciation for Kid. After recently doing another project with Smarty (which I used to worship), I really prefer Kid. As a matter of interest, did TG succeed in getting you from A to B in time C? -Rob Ville Vainio wrote: > We are almost done with our school project that uses TG, and I wrote a > small "lessons learned"/retrospective analysis of what went right and > what went wrong: > > http://www.writely.com/View.aspx?docid=bdfmvvthd98nc > > Of course it may be overly critical and subjective, but there wasn't > really enough time to go to great depths in various issues during the > implementation and frustration came about more easily than it typically > does with completely "voluntary" open source projects. :-) > > I copy pasted it here, for those that care: > > TurboGears, lessons learned > > Author: Ville Vainio, [EMAIL PROTECTED] --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears" 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/turbogears -~----------~----~----~----~------~----~------~--~---
