Patch for Fluido 1.1
Hello folks, finally I would like to commit a patch for the site to use fluido 1.1. Currently it looks like: http://code.grobmeier.de/struts-draft-v4 There is some stuff left to do, but now, since I am able to commit myself, I would like to add this new layout now and modify it step by step. If the urgent case of a security bugfix comes up, the website will do the trick, even when there is some minor stuff to be done. If you agree, I will commit then. If you find urgent things to be changed now, please let me know. What I have made different the latest commit is: I have removed the 2.3.1/2.3.1.1 notification as I think only the most recent downloads should appear on top. Also I have corrected the release date of 2.3.1.2 which is wrong at the moment :-) Cheers Christian -- http://www.grobmeier.de https://www.timeandbill.de - To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org
Plugins Recap
Hello, I find it pretty complex to get an overview of plugins on the current struts site. There are many listed, but its state is sometimes unclear. For example: http://struts.apache.org/2.3.1.2/struts2-plugins/struts2-javatemplates-plugin/apidocs/index.html leads to 404. I tried the DWR plugin I before a good while and finally gave up, because it was somehow broken. Another colleg told me he tried the S1-plugin last year and gave up on that one too. Question: which plugins named here: http://struts.apache.org/2.3.1.2/index.html are really supported and are really working? Cheers, Christian -- http://www.grobmeier.de https://www.timeandbill.de - To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org
Struts 2 Components
Last mail for today :-)
Today there is a discussion on going, Tapestry vs Struts (on
tapestry-users list). Of course people are convinced of Tapestry, and
actually it is a great framework with huge benefits. And it is pretty
modern. People now say (and not only there) Struts is a dinosaur.
Well, what I really liked on Wicket was the idea on components. I
think Wicket failed with it. But Tapestry did something similar, and
there it is working. Then there is Vaading, another great framework
supporting components.
I look at Struts. I see, we can use different presentation layers here
too. I am just not sure what other than jsp is really working. Are we
sure JavaTemplates work? We support Sitemesh2, which is pretty
outdated too.
These days people go to Components. I have thought a while about it...
shouldn't it be possible to use components in STruts too? We have DI
in place, which is a good backbone for that.
For example, look at this:
class MyAction {
@Inject
MyComponent blub; // Implements StrutsComponent
}
body
s2:component id=blub /
/body
Components might be able to return html. They can calculate. They can
be used with JSP. Looking at this:
http://tapestry.apache.org/component-reference.html
We can learn a bit from Tapestry here. Probably we are able to reuse
some of the components from them.
I begin to think a good frontend layer would bring benefits. Otherwise
it might happen S2 is more and more going into the direction service
layer, and for that it might not fit very well.
What do you think?
Cheers
Christian
--
http://www.grobmeier.de
https://www.timeandbill.de
--
http://www.grobmeier.de
https://www.timeandbill.de
-
To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org
For additional commands, e-mail: dev-h...@struts.apache.org
Re: Plugins Recap
Hi Christian, Question: which plugins named here: http://struts.apache.org/2.3.1.2/index.html are really supported and are really working? The answer should be *all of them*. My guess is that due to some configuration errors, the apidocs folder for the javatemplate plugin is not generated. The only plugin which is going to be deprecated is dojo plugin AFAIK. Twitter :http://www.twitter.com/m_cucchiara G+ :https://plus.google.com/107903711540963855921 Linkedin:http://www.linkedin.com/in/mauriziocucchiara Maurizio Cucchiara
Re: Patch for Fluido 1.1
Although as far as I remember last time we didn't reach the general consensus, again I'm for the new layout. But what about to create a new branch and after, when the site will be in a consistent state, start a vote? Twitter :http://www.twitter.com/m_cucchiara G+ :https://plus.google.com/107903711540963855921 Linkedin:http://www.linkedin.com/in/mauriziocucchiara Maurizio Cucchiara On 26 January 2012 11:50, Christian Grobmeier grobme...@gmail.com wrote: Hello folks, finally I would like to commit a patch for the site to use fluido 1.1. Currently it looks like: http://code.grobmeier.de/struts-draft-v4 There is some stuff left to do, but now, since I am able to commit myself, I would like to add this new layout now and modify it step by step. If the urgent case of a security bugfix comes up, the website will do the trick, even when there is some minor stuff to be done. If you agree, I will commit then. If you find urgent things to be changed now, please let me know. What I have made different the latest commit is: I have removed the 2.3.1/2.3.1.1 notification as I think only the most recent downloads should appear on top. Also I have corrected the release date of 2.3.1.2 which is wrong at the moment :-) Cheers Christian -- http://www.grobmeier.de https://www.timeandbill.de - To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org
Re: Patch for Fluido 1.1
This design seems to incorporate many good points of the first fluido draft discussion thread (I could not actively participate due to insane RL task load), and I like it very much. I think in general it's both more modern and cleaner in terms of information presentation than the current site. Maurizio's approach sound very good - why not branch current site, and look if we get more feedback and a formal consensus on it? BTW, I'm still unsure whether the right announcement wouldn't be good to re-add for our one or two most recent / prominent announcements - especially regarding our latest critical security issues - nothing mentioned on the frontpage, and I doubt people take time to visit the Announcements section as regularly as the frontpage. And of course - thanks for your efforts, Christian. Good to see this pushed forward. - René On 26.01.12 16:21, Maurizio Cucchiara wrote: Although as far as I remember last time we didn't reach the general consensus, again I'm for the new layout. But what about to create a new branch and after, when the site will be in a consistent state, start a vote? Twitter :http://www.twitter.com/m_cucchiara G+ :https://plus.google.com/107903711540963855921 Linkedin:http://www.linkedin.com/in/mauriziocucchiara Maurizio Cucchiara On 26 January 2012 11:50, Christian Grobmeier grobme...@gmail.com wrote: Hello folks, finally I would like to commit a patch for the site to use fluido 1.1. Currently it looks like: http://code.grobmeier.de/struts-draft-v4 There is some stuff left to do, but now, since I am able to commit myself, I would like to add this new layout now and modify it step by step. If the urgent case of a security bugfix comes up, the website will do the trick, even when there is some minor stuff to be done. If you agree, I will commit then. If you find urgent things to be changed now, please let me know. What I have made different the latest commit is: I have removed the 2.3.1/2.3.1.1 notification as I think only the most recent downloads should appear on top. Also I have corrected the release date of 2.3.1.2 which is wrong at the moment :-) Cheers Christian -- http://www.grobmeier.de https://www.timeandbill.de - To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org -- René Gielen http://twitter.com/rgielen -- René Gielen IT-Neering.net Saarstrasse 100, 52062 Aachen, Germany Tel: +49-(0)241-4010770 Fax: +49-(0)241-4010771 Cel: +49-(0)163-2844164 http://twitter.com/rgielen - To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org
Re: Struts 2 Components
On Thu, Jan 26, 2012 at 3:34 AM, Christian Grobmeier
grobme...@gmail.com wrote:
Last mail for today :-)
Today there is a discussion on going, Tapestry vs Struts (on
tapestry-users list). Of course people are convinced of Tapestry, and
actually it is a great framework with huge benefits. And it is pretty
modern. People now say (and not only there) Struts is a dinosaur.
Well, what I really liked on Wicket was the idea on components. I
think Wicket failed with it. But Tapestry did something similar, and
there it is working. Then there is Vaading, another great framework
supporting components.
I look at Struts. I see, we can use different presentation layers here
too. I am just not sure what other than jsp is really working. Are we
sure JavaTemplates work? We support Sitemesh2, which is pretty
outdated too.
These days people go to Components. I have thought a while about it...
shouldn't it be possible to use components in STruts too?
The classical distinction between styles of web frameworks is
action-oriented versus component-oriented. The two take different
approaches to the problem of building web apps, and each has its
place, depending on the goals and constraints of the app. Some people
pick one and try to use it for everything; others will pick the
appropriate tool for each job.
Since its very beginnings, Struts has been an action-oriented
framework. Over time, people have attempted to morph it into something
more component-oriented, or tried to build a component layer on top of
it. To me, that's a bit like trying to improve upon a screwdriver by
turning it into a hammer.
If you look back at the early history of JSF, you'll find the
beginnings of Apache Shale, which started out as a Struts subproject
to explore some component-oriented ideas in a Struts world. Shale was
split off from Struts because of the divergent perspectives of
action-oriented versus component-oriented developers. The project was
retired about 2 years ago, in part because many of the good ideas from
Shale were being adopted into JSF, and in part because of the
realisation that trying to morph an action-oriented framework into a
component-oriented one was an unnatural act. It made (and makes) more
sense, if you wanted a component-oriented framework, to focus on just
that, rather than bending another tool to needs for which it wasn't
designed.
Now, of course, that's not to say that there aren't ideas that might
be interesting for some people to explore, as a kind of Shale2 on top
of Struts2 (conceptually speaking). I'd just encourage you to think
carefully about why you would want to do that, rather than use an
existing component-oriented framework in a situation that warrants
that style. I'd also encourage you to think about why tens of
thousands of developers have chosen Struts as an action-oriented
framework when they too could have chosen a component-oriented
alternative if it fit their needs.
--
Martin Cooper
We have DI
in place, which is a good backbone for that.
For example, look at this:
class MyAction {
@Inject
MyComponent blub; // Implements StrutsComponent
}
body
s2:component id=blub /
/body
Components might be able to return html. They can calculate. They can
be used with JSP. Looking at this:
http://tapestry.apache.org/component-reference.html
We can learn a bit from Tapestry here. Probably we are able to reuse
some of the components from them.
I begin to think a good frontend layer would bring benefits. Otherwise
it might happen S2 is more and more going into the direction service
layer, and for that it might not fit very well.
What do you think?
Cheers
Christian
--
http://www.grobmeier.de
https://www.timeandbill.de
--
http://www.grobmeier.de
https://www.timeandbill.de
-
To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org
For additional commands, e-mail: dev-h...@struts.apache.org
-
To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org
For additional commands, e-mail: dev-h...@struts.apache.org
Re: Struts 2 Components
Hi, After Martin's words, there is nothing to say. Adding components to S2 isn't a good option, S2 should remain as action base framework. If you want components you have a lot of options - Wicket, JSF, Tapestry, etc. Kind regards -- Łukasz - To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org
