Re: [oll-user] Call for initial feedback

[Urs L. <ul...@op...>]

Am 28.03.2013 18:50, schrieb Joseph Rushton Wakeling:
> On 03/28/2013 05:59 PM, Urs Liska wrote:
> ...
>> Not really problems, its rather the complexity of the amount of repos.
>> An example: If I work on, say, the manual for 'musicexamples' I may run
>> into updating the stylesheet package. If everything is in one repository
>> I will surely notice the need for committing this change, at least if I
>> want to power down the computer and see that git status isn't clean.
> Wouldn't that kind of issue suggest that your repos are improperly modularized?
>
> For example, if an individual tutorial needs a stylesheet change, it might make
> sense to allow tutorials to have custom local stylesheets that are used
> alongside the global one.  And if, reviewing the merge of a tutorial patch,
> there is a stylesheet change, it could be consciously decided to make that
> change to the global stylesheet instead.
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'.
>
> Put it another way -- if you have to make changes to the global stylesheet
> often, then your global stylesheet needs rethinking anyway.  Preventing you from
> habitually making stylesheet changes along with tutorial changes is probably a
> good way to enforce good discipline of 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.

Urs