Re: [oll-user] Call for initial feedback

[Joseph R. W. <jos...@we...>]

On 04/06/2013 01:39 PM, Urs Liska wrote:
> This is a very good idea. It is completely practical to have an 
> individual style sheet for use in an individual tutorial.
> Or a tutorial author could write his additions directly in the preamble 
> of his 'subfile'.

That said, you want to avoid this as much as possible, because it means that
changes to the global stylesheet may break individual tutorials if there are
clashes with their customizations.

I know that probably sounds like a contradiction with what I said before, but
not really.  Priority should be something like: if you need a new stylesheet
feature, try and design something general-purpose and useful to everyone that
can go in the global stylesheet.  If your need is really, really specific, then
put it in a local stylesheet, but try and design it so that it's very unlikely
to suffer from global stylesheet tweaks.

What shouldn't be acceptable is someone making a custom stylesheet just as a
lazy way of having to avoid thinking about how to tweak the global stylesheet.
Of course, if you really like someone's tutorial, you could accept it as a short
term measure to get the tutorial included and then the core OLLib people take
responsibility for correcting the design ... :-)

> I see your point, but that's not really the case here.
> I have to change the style sheets often because they are developed along 
> the way. So I'll add an environment for a specific kind of table when I 
> first need it. So the number of this kind of updates will fastly 
> decrease. And it can be made simpler with your previous suggestion.

As you say it's a short-term pain.  So, in the long term it's irrelevant from
the point of view of modularizing the documentation.