On Thu, Mar 31, 2011 at 9:08 AM, Pouyan Zachar <pouyanster at gmail.com> wrote:
> [Excerpts from Ian's message] > > I'll all for moving to a standard web framework, rather than our current > > home-grown solution. However there are a lot of options to choose from. > > Why Struts, and not another option (like, for example, Apache Wicket)? > > Ian. > > Well, that's a good point indeed. I suggested Struts because I already > had experience working with Struts in WebApp development. The bottom > line is to decouple Java code from web interface (as much as possible) > so designing web interface would be a little bit easier (even for > those who are not familiar with Java language). The question is which > framework to choose? > Well, there is nothing wrong with choosing a tool on the basis that its what you are most familiar with provided that you are willing to commit to seeing it through to completion :-) It doesn't make sense to choose a tool on that basis if other people will then need to do the actual implementation. Ian. -- Ian Clarke Personal blog: http://blog.locut.us/ -------------- next part -------------- An HTML attachment was scrubbed... URL: <https://emu.freenetproject.org/pipermail/devl/attachments/20110331/b0cbb4da/attachment.html>
