Yes, you can, as long as you make sure to use a similar naming scheme so it's easy to find stuff (though I'm sure you know that already!) . By that, I mean, don't use anything like Transmogrified's naming scheme, which doesn't *quite* match core2 *g* (to be fair, that layout was done while we were hammering out the naming conventions).
One note, though, if you have one where the color property name is close enough, but the description isn't, I believe you can do something like:
property Color existing_property_name { des = "this description will be the one that shows up in the wizard"; }
Which helps us avoid having unused properties in the wizard, and may help in some cases to keep the number of properties down.
(From feedback, having more color options just means people are more likely to give up halfway through creating a new color theme).
![[community profile]](https://www.dreamwidth.org/img/silk/identity/community.png){kind=small}
![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png)
onlyembers
no subject
Date: 2009-09-09 09:08 am (UTC)One note, though, if you have one where the color property name is close enough, but the description isn't, I believe you can do something like:
property Color existing_property_name { des = "this description will be the one that shows up in the wizard"; }
Which helps us avoid having unused properties in the wizard, and may help in some cases to keep the number of properties down.
(From feedback, having more color options just means people are more likely to give up halfway through creating a new color theme).