[opensource-dev] Open Development project: extendingavatarwearables
Dzonatas Sol
dzonatas at gmail.com
Fri Mar 26 08:26:20 PDT 2010
+1 A 'change type' feature isn't needed for this project.
Nyx's proposed category layout can override the type as old types are
just hints. Possible with an ability to just drag-n-drop a wearable
between categories.
The proposed outfit list would allow more for arbitrary lists that
wouldn't depend on type hints or any new ordinals for layer priority,
yet a complete UI for such feature is not expected this cycle in the
main viewer as noted. The solution is here, however, with further
development. Instead of any need to convert a type into a new type, the
category list can be converted to an outfit list that make sense. One
can just wear the outfit list instead of wear the specific type.
For example, the outfit list could be a notecard with a specific
description to denote it as a wearable, which the viewer reads to fill
in the category list when worn. Maybe you want superman underwear worn
underneath blue pants, so your create a werable notecard called 'Kent'.
You also can create a notecard called 'Superman' that then lists the
superman underwear over the blue pants. To change layer order is now
simply an action to either wear 'Kent' outfit or wear 'Superman' outfit,
even though both lists contain specific wearables. With such outfit
lists, there is never a need to 'change type' on a specific wearable.
Carlo Wood wrote:
> If the goal is to be able to change the type, then
> I don't feel it should be part of this particular
> project.
>
More information about the opensource-dev
mailing list