renaming a template and applying changes

[tamlyn]

Sorry to be reporting bugs just before a release! This may already have been fixed in svn but I found this in beta2: If you change the name of a template and click 'apply' it all works fine but the next time you try to apply or submit the changes it tells you the template already exists. If you go back to the template list and click edit again then it's fine. I guess it's something to do with templates being treated as 'new' or not.

EDIT: I get the same behaviour with stylesheets.

Also I'm not sure I approve of the stylesheet being split into so many sections... but that's another matter.

[Ted]

I'll look at it today.  Thanks.

You mean the number of default stylesheets?  Too confusing?

[tamlyn]

Not confusing but a bit unnecessary. I can't really see what advantage there is to putting the colours, layout etc. in different stylesheets when they will be used together. It just makes editing them more complicated. I dunno though maybe that's just me. Also even though it makes logical sense to keep stylesheet and template editing separate I quite enjoyed being able to edit both from the same page. But actually having the template and stylesheet open in different tabs is just as easy so forget that.

Can't wait for 0.12 proper - discovering a new cmsms release is like unwrapping a christmas present for me! Actually it's better than that: it's more like discovering a whole room of presents... 

[Greg]

Inexperienced users really find the number of style sheets very confusing. We know there are to many when code has to be developed to ensure load order, which will again add frustration for inexperienced users. Maybe condensing them down to 2 or 3 would help.

[Ted]

This is fixed in svn.  Thanks!

[jelle]

I agree that it looks daunting for inexperienced users, but the contents of them are even more daunting. There is not 'solution' to that anytime soon. I guess the idea with the snippets was/is that each extra module brings it's own css. If you include the new module in your template, all you have to do next is add the module's css snippet. That does not expose the user to scary code.
Lumping all css together will remove some/all of this granularity, and mean that the user will have to dive into css code sooner, and do it in bigger stretches of css code.
In the end the user will have to face the code whichever way you turn it and a certain design requires a certain amount of css code. I think the inexperienced (and expercieced!) user would be better served with granular code and maybe the first few lines of the snippet in a tooltip, or a separate field for a helptext/description.

[Greg]

Very good points jelle.

[tamlyn]

Yeah I can see the advantage of separating module css into separate stylesheets but the layout, colours, forms, tools etc stylesheets are all used on all pages (i think) so why separate them? It just makes them more tedious to edit.