Hi,<br><br>There is also something called OFBiz (Open For Business - <a href="http://ofbiz.apache.org/">http://ofbiz.apache.org/</a>) out there in the java world.<br>I think it may be considered as a very mature product but it needs to be customized and it is the point were it can cost a little because it is not a "dummy" project. There is just a big codebase (you can do everything with it and many things are also implemented) and I think it is well written.
<br><br>Bye,<br>Mimil<br><br><div><span class="gmail_quote">On 9/24/07, <b class="gmail_sendername">Joshua Layne</b> <<a href="mailto:firstname.lastname@example.org">email@example.com</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
On Mon, 24 Sep 2007 13:27:45 -0400, Ian Darwin <<a href="mailto:firstname.lastname@example.org">email@example.com</a>> wrote:<br>><br>>> I've done enough work in django (python) recently that the idea of going<br>>> back to PHP sounds like some kind of really brutal punishment. The
<br>>> code is really much easier to read, because the code and presentation<br>>> are kept in separate files. The original idea with PHP of embedding code<br>>> in HTML was cool in theory, but in practice I think templates are a lot
<br>>> easier to maintain. Django isn't perfect, but I can see why people are<br>>> edging towards it and away from PHP.<br>><br>it's also very possible to code PHP using MVC - it just takes discipline.
<br><br>easier to use a templating engine (like smarty) because it forces the<br>dicspline on you, but also extra overhead - I would argue it is better to<br>do it yourself using strict separation.<br><br>> It's not just PHP - Java EE had the idea (long ago) of embedding code in
<br>> HTML, but now we tell people to "get the Java out of the JavaServer<br>> Pages".<br>><br>> It's funny in a sad sort of way - the original MVC paper was published<br>> in 1979, darn near three decades ago, and way too many developers still
<br>> haven't got the idea. It's bad when they mess up one application, but<br>> when they publish a framework, and zillions of people start using it...<br>><br>we tried teaching basic design patterns to some of our internal developers
<br>(we aren't a software shop, but do write some internal apps) - the<br>feedback: "Why would we ever need this?"<br><br>good development practices are rare IME.<br><br>anyway, somewhat far afield from openmoko. As long as the solution they
<br>build makes the neo orderable and deliverable (without my identity being<br>lifted...), I'm happy :)<br><br><br>_______________________________________________<br>OpenMoko community mailing list<br><a href="mailto:firstname.lastname@example.org">