<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">
feel free to email the google group if you have questions.<div><br class="webkit-block-placeholder"></div><div>Massimo<br><div><br class="webkit-block-placeholder"></div><div><br><div><div>On Feb 5, 2008, at 10:10 AM, Daniel Griffin wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite">Thanks for elaborating on web2py, I am going to work through some of the tutorials and see for myself.<div><br class="webkit-block-placeholder"></div><div>Martin:</div><div>A few of the frameworks give a little info on legacy data set support. To me a framework should do the following:</div> <div><br class="webkit-block-placeholder"></div><div><div>-Set you up for MVC</div></div><div>-Easy database connectivity and ORM</div><div>-Simple way to expose those models as forms, lists, etc. </div><div>-A template language.</div> <div>-Ideally some helpers to work with AJAX, routes etc.</div><div><br class="webkit-block-placeholder"></div><div>The big problem is the lack of easy forms and lists, it seems that there should be some nice decorator style objects that would let you pop out a variety of forms, from normal HTML forms to Ext style super forms.</div> <div><br class="webkit-block-placeholder"></div><div>But I am still new at web development(I am a C programmer by day), so I might be wrong.</div><div><br class="webkit-block-placeholder"></div><div>Dan</div><div><br><div class="gmail_quote"> On Feb 5, 2008 9:51 AM, Martin Maney <<a href="mailto:maney@two14.net">maney@two14.net</a>> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><div class="Ih2E3d"> On Mon, Feb 04, 2008 at 09:29:33PM -0600, Daniel Griffin wrote:<br>> notes. I would really like Prof. Di Pierro's input on this and why he went<br>> the way he did with web2py.<br><br></div>For pedagogical purposes, it can be very beneficial to pretend that<br> there are only square holes and pegs to match. <wink><br><div class="Ih2E3d"><br>> I have been trying to solve a much larger problem than any of these<br>> frameworks really prepares me for, namely working with creating a web<br> > front-end to a mature piece of enterprise software. Pylons has given me the<br>> most hope so far, but I think I am still going to end up writing a ton of<br>> boilerplate code.<br><br></div>Are there any frameworks that don't pretty much assume you're starting<br> from scratch? I'd say that all of them that I've looked at for more<br>than the briefest glance leverage the assumption that the project is<br>all new (and needn't consider anyone accessing its data except through<br> the app built using the framework) as a hugely simplifying assumption -<br>only one shape of holes and pegs, once again.<br><font color="#888888"><br>--<br>Anyone who says you can have a lot of widely dispersed people hack<br> away on a complicated piece of code and avoid total anarchy has never<br>managed a software project. -- Andy Tanenbaum<br></font><div><div></div><div class="Wj3C7c"><br>_______________________________________________<br> Chicago mailing list<br><a href="mailto:Chicago@python.org">Chicago@python.org</a><br><a href="http://mail.python.org/mailman/listinfo/chicago" target="_blank">http://mail.python.org/mailman/listinfo/chicago</a><br></div> </div></blockquote></div><br><span><ATT00001.txt></span></div></blockquote></div><br></div></div></body></html>