[sldev] New feature? Clothing Outfit cards

[Stickman]

> suggested format for the card
> **********Outfit Selection Card DN="Display Name" MODE=|Replace,Add to
> outfit|*******
>
> 1 "%Item Display name%" %UUID for item% %item type%
> 2 "%Item Display name%" %UUID for item% %item type%
> ....
> N STOP END OF CARD
>
> and this would also work for folks selling multiple outfits in a
> single box same outfit in blue read and green say "
> Im not sure what all would need to be changed server and or client
> side but does this look like a possible good idea to anybody??
> No jira yet can create one if this idea is "sane"

Sure, I like the idea. The concept is "grouping" multiple attachments
into a single object so we don't need to deal with all the confusion
and inventory bloat.

Unfortunately, I don't see it working. For the following reasons.

1) People live for avatar customization.

Using a head from this avatar, the legs from this avatar, maybe a pair
of prim pants from something else. Having everything divided up allows
that to be done very easily. It also makes it very easy to modify
these individual parts, if they want to change a color, add earrings,
etc.

2) The UUID changes every time an attachment is attached.

There's a current race condition you can easily duplicate. Wear an
item, change it, then detach and reattach it really quickly. Your
change will be lost as it wasn't saved back to the asset server before
it was worn again. What happens after that I haven't tested, but I've
experienced fairly random results about which version finally ends up
in my inventory.

While this "card" would be a nice organizational factor, it adds one
more place where UUIDs need to be updated, introducing one more race
condition that would need to be accounted for.

3) We already have organizational methods for avatars outfits

You can right click on a folder and select one of three options:
replace, add, and remove. You can even mix and match things this way.
SL natively supports this by "saving outfit" when in the appearance
editor.


So -- the concept of "hiding" lesser used inventory items by grouping
them into a single object may be nice, but it's just a front-end
change. According to the backend, you're actually adding at least one
new item (the card) while all of the other items still need to be
accounted for.

Besides, we've basically got the same thing, except with folders. I
don't think the advantage of having less inventory items makes up for
the lack of freedom the current system has.

If I've got things wrong in my head about what you're talking about,
please feel free to clarify for me. New ideas are great and promote
growth -- don't be scared to bring them up. Who knows what this idea
may evolve into when it pairs up with another idea someone else has
down the road.

-Stickman