Add new attachment

Only authorized users are allowed to upload new attachments.

This page (revision-11) was last changed on 27-Jan-2008 20:31 by HarryMetske  

This page was created on 29-Jan-2007 06:35 by 76.19.8.139

Only authorized users are allowed to rename pages.

Only authorized users are allowed to delete pages.

Difference between version and

At line 1 removed 2 lines
Greetings. This post was originally created by Andrew Jaquith, ace fighter pilot and Scrabble player extraordinaire.
At line 5 changed one line
I concluded a while ago that the minute Janne signaled intent to move to Java 5, I'd take a serious look at an MVC framework I have long admired: [Stripes|http://stripes.mc4j.org/confluence/display/stripes/Home]. Janne previously stated that he wasn't interested in looking into MVC frameworks because they impose a learning curve. I suspect his reticence is also because some of the most popular ones (for example, Struts) all suck in various ways. Struts, for example, is very configuration-heavy and requires lots of seemingly-redundant classes to do just even little things. Creating that kind of overhead isn't something I think he wanted, and of course, I agree. But the current system JSPWiki uses — which does not use a framework — has some significant limitations, too.
I concluded a while ago that the minute Janne signaled intent to move to Java 5, I'd take a serious look at an MVC framework I have long admired: [Stripes|http://www.stripesframework.org/display/stripes/Home]. Janne previously stated that he wasn't interested in looking into MVC frameworks because they impose a learning curve. I suspect his reticence is also because some of the most popular ones (for example, Struts) all suck in various ways. Struts, for example, is very configuration-heavy and requires lots of seemingly-redundant classes to do just even little things. Creating that kind of overhead isn't something I think he wanted, and of course, I agree. But the current system JSPWiki uses — which does not use a framework — has some significant limitations, too.
At line 7 changed one line
!Critique of Current JSPWiki MVC Model
!Critique of Current JSPWiki MVC Model...
At line 43 changed one line
If you want a ''very fast'' introduction to how Stripes works, see the ["Quick Start" guide|http://stripes.mc4j.org/confluence/display/stripes/Quick+Start+Guide], and start with "My First Stripe":
If you want a ''very fast'' introduction to how Stripes works, see the ["Quick Start" guide|http://www.stripesframework.org/display/stripes/Quick+Start+Guide], and start with "My First Stripe":
At line 86 changed one line
{{{<stripes:useActionBean binding="/View.action"}}}
{{{<stripes:useActionBean binding="/View.action">}}}
At line 91 changed one line
The result of all this is that top-level JSPs become ''super simple'': maybe 4 lines long. In fact, If you wanted to you could simply over-write the top-level JSPs with the default template {{*Content.jsp}} files. In other words, templates would go away because you could merge them with the top-level files. Our JSPs would become very, very stupid but stay pretty. If someone wanted to hack JSPWiki's look and feel, they could simply hack the top-level files — because that's all there would be. (Janne — I'm not advocating we go that far, just suggesting how far one could push the envelope if inclined.)
The result of all this is that top-level JSPs become ''super simple'': maybe 4 lines long. In the test branch that I'm working on now, here is the ''entire'' contents of {{Wiki.jsp}}:
{{{<%@ taglib uri="/WEB-INF/jspwiki.tld" prefix="wiki" %>
<%@ taglib uri="http://stripes.sourceforge.net/stripes.tld" prefix="stripes" %>
<stripes:useActionBean binding="/View.action" />
<wiki:Include page="ViewTemplate.jsp" />}}}
At line 95 added 2 lines
In fact, If you wanted to you could simply over-write the top-level JSPs with the default template {{*Content.jsp}} files. In other words, templates would go away because you could merge them with the top-level files. Our JSPs would become very, very stupid but stay pretty. If someone wanted to hack JSPWiki's look and feel, they could simply hack the top-level files — because that's all there would be. (Janne — I'm not advocating we go that far, just suggesting how far one could push the envelope if inclined.)
At line 127 changed one line
Please post your critiques, suggestions and thoughts on this. I am trying very hard not to disrupt existing APIs (other than the few instances I've mentioned), while trying to move things forward with this. If Stripes makes you nervous, check out the [Quick Start guide|http://stripes.mc4j.org/confluence/display/stripes/Quick+Start+Guide] first, and I think you'll agree that it will really accelerate our ability to add functionality, once we get it integrated.
Please post your critiques, suggestions and thoughts on this. I am trying very hard not to disrupt existing APIs (other than the few instances I've mentioned), while trying to move things forward with this. If Stripes makes you nervous, check out the [Quick Start guide|http://www.stripesframework.org/display/stripes/Quick+Start+Guide] first, and I think you'll agree that it will really accelerate our ability to add functionality, once we get it integrated.
At line 134 added 22 lines
----
I'm going to stick my project management hat on, and say that we should stabilize 2.6 first before starting serious work on 3.0. I don't particularly want to import *two* sets of bug fixes into the main branch every single time we make a fix, and I fear the development will totally get out of hand so that we will end up with ''two'' half-functional releases of code: 2.6 (which nobody cares about because it's so much cooler to work on 3.0), and 3.0, which will become the host of all the nice improvements people have been drooling at for the past year.
3.0 will also include a full redesign of the provider interface, based on JSR-170, so we will almost certainly have to rewrite quite a lot of the internals. And that means that we won't have the time to work on 2.6.
-- JanneJalkanen
----
And, actually, to add... Stripes certainly looks like a good MVC framework which embodies many of the design principles also behind JSPWiki: simplicity, clarity, no extra libraries, etc. I'll have to delve into it a bit deeper to get a coherent image, but it certainly looks like it could simplify our existing structure as opposed to making it more complicated (which is what Struts would do).
--JanneJalkanen, 29-Jan-2007
----
Janne -- let me know what the most pressing issues are that you'd like me to work on for 2.6. Happy to help, as you know. :)
--Andrew Jaquith, 29-Jan-2007
Version Date Modified Size Author Changes ... Change note
11 27-Jan-2008 20:31 21.67 kB HarryMetske to previous adjusted links to stripes site
10 07-Jun-2007 13:51 21.681 kB 196.12.53.9 to previous | to last
9 07-Jun-2007 11:18 21.799 kB 196.12.53.9 to previous | to last
8 29-Jan-2007 16:11 21.796 kB Andrew Jaquith to previous | to last Comment by Andrew Jaquith
7 29-Jan-2007 15:12 21.625 kB JanneJalkanen to previous | to last Comment by JanneJalkanen
6 29-Jan-2007 14:16 21.184 kB JanneJalkanen to previous | to last
5 29-Jan-2007 06:40 20.375 kB Andrew Jaquith to previous | to last
4 29-Jan-2007 06:38 20.043 kB Andrew Jaquith to previous | to last
3 29-Jan-2007 06:37 20.031 kB Andrew Jaquith to previous | to last
2 29-Jan-2007 06:36 20.029 kB 76.19.8.139 to previous | to last
1 29-Jan-2007 06:35 20.025 kB 76.19.8.139 to last
« This page (revision-11) was last changed on 27-Jan-2008 20:31 by HarryMetske