Re: Status of project, and where to next

On Apr 22, 2005 at 07:48:05PM +0200, nico wrote:
> If you have suggestions to improve flexibility, or even some hack, please
> tell it on the list. You can send all your wishes, at least to see the
> amount of work to do.

Some other items:

- I've looked into the mappings - it seems that this is just a simplified
  way of mass-defining templates. I think to ensure flexibility each
  element should get a separate template in XSL.

- There should be some general considerations on naming the templates. The
  current system seems rather chaotic to me, especially with all the
  "generate.*" templates.

- Connected to the item above: we might need some generic XSL function
  library. For example, I needed to build up some kind of array structure
  to be able to implement morerows. There will certainly be a whole lot of
  other helping functions, which we'll need all over the code especially
  for the complex things. Maybe something like this exists already?
  (http://sourceforge.net/projects/xsltsl/ and
  http://fxsl.sourceforge.net/ have some material)

- We'll also need some prototyping language for XSLT - all the <xsl:if>s
  are just nasty. I've seen something like that on the internet, but I do
  not have a link right now. It plainly lets you write if a=b {} and
  converts it to <xsl:if test="a=b"></xsl:if>. Maybe, if we find something
  really working and useful, we might switch to that format and generate
  XSLT only automatically?

- General file structure. How about an xsl-file for each Docbook element
  or something like it?

  

-- 
Nikolai Prokoschenko 
[email protected] / Jabber: [email protected]


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click