[daisy] [JIRA] Commented: (DSY-542) Making the skinning layout.xsl more 'modular'

[Grzegorz Kossakowski (JIRA)]

    [ http://issues.cocoondev.org//browse/DSY-542?page=comments#action_13348 ] 

Grzegorz Kossakowski commented on DSY-542:
------------------------------------------

Hello,

I'm aware that Daisy uses Cocoon 2.1.x but have you considered migrating to 2.2? I'm asking because I think Cocoon 2.2 could help you to make skinning more modular.

The idea is to use capabilities of Servlet Service Framework that drives real blocks implementation. SSF allows Cocoon blocks to take advantage of Object Oriented concepts in URI space In other words, you can let one block extend another one (called super block) by inheriting from super every single pipeline and override only needed ones. This way custom skin could become a block extending default implementation of skin and could override some pipelines.

Marc's idea of XSLT stylesheets being more ready for extension is still valid. It's a question how to inject customized XSLT into existing pipeline, I believe that blocks inheritance is the best option.

Does it make sense?

> Making the skinning layout.xsl more 'modular'
> ---------------------------------------------
>
>          Key: DSY-542
>          URL: http://issues.cocoondev.org//browse/DSY-542
>      Project: Daisy
>         Type: Improvement
>     Reporter: Marc Portier
>     Priority: Minor

>
> The current skinning system is already quite 'modular' when it comes down to be split over multiple separate files.
> However, each of these files is holding a number of templates that each in their own right need to be completely overridden when a new skin is to be made.
> A general effort should be taken to split down the templates in smaller pieces, as well as to provide some clear documentation for each of them.
> This issue acts as a focal point in this effort
> - please list suggestions and or modularity-itches as comments to this issue
> Work on this should result in a new 'default' skin, and can thus even be performed as a completely new replacement skin rather then as patches on the current one.
> (Which should lower the bar for the lesser-svn-skilled and read an as open invitation to anyone around to share their expertise in this area by providing some 'baseskin' to be included...)

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.cocoondev.org//secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira