The problems I've run into in comprehending the Theme layer:

o  The "library" files are too big and contain too many ideas.  A
   single river of templates makes it hard for me to grasp their
   relationships.  I'd like to see them broken down into a larger set
   of smaller, more focused files, much as the Java code is.

   Not necessarily, however, by the type of page produced.  That would
   entail a lot of duplication of the implementations of cross-cutting
   concerns and common requirements.

o  Documentation, documentation, documentation.  I'd like to go
   through the templates and work over the comments on each one, but I
   don't yet feel that I understand them well enough to do that.

o  No data dictionary.  There is a rich set of "hints" that the Aspect
   chain can use to tell the Theme engine what its intent is
   w.r.t. some element, but I haven't found any comprehensive list of
   them.  To know how to proceed, the method seems to be "read the
   entire library and every Theme you use, until you find something
   that seems to fit."

o  Too much copying.  Some of the templates might be further broken
   down into "subroutines", so there is less copying of a large template
   just to make a small change.  This will require compiling and
   analyzing a lot of input from the community about what UI features
   they usually want to change, and how.  (This might also allow us to
   group many of the callouts for those "hot spots" into a single file
   without a lot of distractions, if the common customizations are
   conceptually closely enough related.)

-- 
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_

Attachment: pgpLXcs7QJYmU.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

Reply via email to