Well, one thing which occurs to me is that <dri:field type='button'/> should instead be something like <dri:action/> and let the Theme figure out whether it wants to lay out a button (or anything else) which links to the action. These "button" fields are really just abstract handles for things the user can ask to have done. If they weren't *called* buttons, they wouldn't look like presentation.
If we do away with DRI we will have to invent something almost like
it. We still need some way to build a bag of structured, labeled data
and action handles, so that when a Theme reaches into the bag it can
know what to grab and make good use of XSL facilities to do so.
What's going on here, it seems to me, is that the current design
strives for separation of concerns between data and presentation
across the Aspect/Theme boundary but perhaps has not quite achieved
it, compounded with the use of terms in DRI which we are conditioned
to think of as presentational.
--
Mark H. Wood, Lead System Programmer mw...@iupui.edu
Balance your desire for bells and whistles with the reality that only a
little more than 2 percent of world population has broadband.
-- Ledford and Tyler, _Google Analytics 2.0_
pgpngMSDxtC9l.pgp
Description: PGP signature
------------------------------------------------------------------------------ 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
_______________________________________________ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech
