Ben, et. al,
The good news is I¹ve been buried in a ³Powered by Stripes 1.5.3² project.
The bad news is, besides being a champion for a more flexible configuration
of the HTML output of Stripes, I haven¹t been able to complete what I
started.
My patch doesn¹t throw a NPE, but it doesn¹t work in nested Layout
Definitions and Renderers.
I recently proposed a Stripes configuration setting that would be much wider
in scope than page, request, or session (session is not the right place
anyway). Application level seem more apropos. A context-param has started
making more sense in recent weeks. Follow my logic:
An application is going to have HTML 4, 5, or XHTML output across the
application as a whole. Developers should not be developing an application
intentionally, or unintentionally, with varied response types... Well,
mobile being an exception, but we (meaning myself and my employer) are
finding that HTML 4 and 5 are the expected standards on advanced, even 3
years recent, mobile platforms (WAP transforms are another matter
altogether).
Having a page level <s:options ... > or other Layout attribute requires
pages/views to be aware of its response to the client, or puts encumbrance
on the page developer to remember the output is of variety x for view y.
Setting the response output in the deployment descriptor make it a much
simpler branching in the FormTag and HtmlTagSupport classes: just check the
ServletContext for the response type.
I really need to visit this again, but yours truly is in the push to
release... Maybe in our next iteration I¹ll press the matter internally
more.
Regards,
Tim
On 10/12/10 9:14 PM, "Ben Gunter" <gunter...@gmail.com> wrote:
>> Thanks for the answer. I've seen recent posts to the group about Stripes'
>> future. Well, this is one direction. The library is very well matured at this
>> point, there's no immediate need to do anything (except for streaming layout
>> - works on our platform btw). Maybe one direction to go is introduce HTML5
>> and some XHTML configuration for picky governments and etc...
--
Timothy Stone | Director, Application Developer Technical Lead
Barclaycard | Business Technology Group, Solutions Delivery
125 S. West Street | Wilmington, DE | 19801
USA | www.barclaycardus.com
+1 302 255 8044 direct | +1 410 441 9450 cell
COMPANY CONFIDENTIAL
P Before printing this e-mail, or any other document, ask yourself whether
you need a hard copy
Barclays www.barclaycardus.com
This e-mail and any files transmitted with it may contain confidential and/or
proprietary information. It is intended solely for the use of the individual or
entity who is the intended recipient. Unauthorized use of this information is
prohibited. If you have received this in error, please contact the sender by
replying to this message and delete this material from any system it may be on.
------------------------------------------------------------------------------
Beautiful is writing same markup. Internet Explorer 9 supports
standards for HTML5, CSS3, SVG 1.1, ECMAScript5, and DOM L2 & L3.
Spend less time writing and rewriting code and more time creating great
experiences on the web. Be a part of the beta today.
http://p.sf.net/sfu/beautyoftheweb
_______________________________________________
Stripes-users mailing list
Stripes-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/stripes-users
