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
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
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,
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.
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+
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.
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
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
