Themes

[GeorgeV]

In the new version of muCommander the previous settings don't worrking. Like this:

<editor>
<font size="12" family="Verdana"/>
<normal>
<background color="ffffff"/>
<text color="333333"/>
</normal>
<selection>
<background color="b8cfe5"/>
<text color="333333"/>
</selection>
</editor>
<location_bar>
<font size="12" family="Verdana"/>
<normal>
<background color="ffffff"/>
<text color="333333"/>
</normal>
<selection>
<background color="b8cfe5"/>
<text color="333333"/>
</selection>
</editor>
<volume_label>
<font size="12" family="Verdana"/>
<background color="cccccc"/>
<text color="000000"/>
<border color="cccccc"/>
<ok color="cccccc"/>
<warning color="cccccc"/>
<critical color="cccccc"/>
</volume_label>

[Nicolas]

Absolutely correct. We're reworking the whole theme API - it was step in the right direction, but we didn't feel it was a big enough step, so we've added a lot of possible states for the file table.

The upside: you can now tweak the way muCommander looks a lot further than before.

The downside: older theme xml files are almost entirely incompatible with the new API.

I know it's a hassle, but there really was no way of avoinding that short of writing two XML parsers, one for older versions and one for newer versions. Since the 'old' version has never made it to an official release, we decided against that.

My suggestion would be to trash your user_theme.xml file (~/.mucommander/user_theme.xml) and start over. The way things are working now, we shouldn't need to completely change the format anymore.

Nicolas

[GeorgeV]

And how can I customize the <editor>, <location_bar> and <volume_label> section now?

[Nicolas]

Those haven't been changed, only the file table.
For an example file, just browse the mucommander jar file and go in themes/, you'll find ClassicCommander.xml.

[GeorgeV]

I copy the editor section from classiccommander to the user theme and now the user theme is unusable.

I copy this from classiccommander theme:

<editor>
<font family="Lucida Grande,Arial,Lucida Sans" size ="12"/>
<normal>
<text color="000000"/>
<background color="ffffff"/>
</normal>
<selection>
<text color="ffffff"/>
<background color="3875d7"/>
</selection>
</editor>

I changed the <selection> to <selected> (because in user theme I find <selected> section instead of <selection>) but in this case as well the user theme unusable.

If I copy classiccommander xml to user theme xml, the user theme xml also unusable.

[Nicolas]

Woops, you're right. Two other things you need to change:
- selection -> selected
- text -> foreground

That ought to fix your problems.

[GeorgeV]

And <status_bar> usable instead of <volume_label> in user theme.

[Nicolas]

Woops, forgot that one as well, sorry mate :)

In theory this sort of things shouldn't happen anymore - we decided it was acceptable in the nightly build, but since we're aiming to release the official beta 3 within, well, the next few days / weeks depending on how much life gets in the way, we won't do that anymore. At the very worst, if we have to update xml file formats, we'll make sure that muCommander knows how to import older versions - the way it works for the configuration file, for example.

Again, sorry about the hassle.

Nicolas