2003-10-12, 22:11
i'm a real fan of xbmp /xbmc, but skinning for the new xbmc is real hard.
i break my work off for the time since xbmc gets final.
every new added feature needs a change in the skin-xml files.
and every change in the skin-xml files makes a skin useless.
example: cvs 10-10 has no language option.
cvs 10-12 has a language option but skins for the older cvs version didn't know this feature, so there is no language option in the old skin.
result: if there is a new feature added to xbmc you can trash your old skins.
i don't know how, but find another way to do it.
i can change everything in my skin, but there must be changed everything for a new version of xbmc.
possibly make a colors.xml and put the settings-section not in the skin dir, to keep the colors (e.g. 5 default colors) and use the new settings-section with old skins.
i break my work off for the time since xbmc gets final.
every new added feature needs a change in the skin-xml files.
and every change in the skin-xml files makes a skin useless.
example: cvs 10-10 has no language option.
cvs 10-12 has a language option but skins for the older cvs version didn't know this feature, so there is no language option in the old skin.
result: if there is a new feature added to xbmc you can trash your old skins.
i don't know how, but find another way to do it.
i can change everything in my skin, but there must be changed everything for a new version of xbmc.
possibly make a colors.xml and put the settings-section not in the skin dir, to keep the colors (e.g. 5 default colors) and use the new settings-section with old skins.