I doubt it would be that hard to establish a way to ensure that the config
could be exported to an easy to read table that can have the option to save to
either a file on the computer (for easy reference) or as a single notecard
within the ao folder that other viewers can read and allow you to import either
manually or individually. An additional hot tip when you mouse over the folder
could tell you what AO is associated with the outfit.
As someone that has to constantly pack and unpack things on my two oldest
accounts in order to even be able to get my inventory to fully load, the idea
of having to add another item to each outfit folder I make pretty much destroys
any advantage to having a system that could associate the ao with the outfit.
I use in client ao systems to reduce attachments, lag, and inventory clutter.
A system that relied on objects in each outfit folder would be a huge step
backward for me.
> CC: opensource-dev@lists.secondlife.com
> From: secret.arg...@gmail.com
> Subject: Re: [opensource-dev] allowing client side AO's to swtich with outfits
> Date: Mon, 16 Apr 2012 03:46:43 -0500
> To: angel_of_crim...@hotmail.com
>
> On 2012-04-16, at 00:50, Erin Mallory wrote:
> > Why would it need to be in the inventory taking up space when it would ONLY
> > do the same thing that either of these options do?
>
> I have over 300 outfits, each with their own set of AO choices... maybe 15 or
> 20 different sets of AOs depending on the shape of the base avatar in the
> outfit, attachments, and general style of the avatar. I change avatars
> radically, maybe a couple of times a minute when it makes sense. I already
> have an appropriate AO item in the inventory for each avatar... changing them
> gradually over to calling the item #AO or moving its attachment point and
> turning the scripts off or changing the script to one that chats the Notecard
> to the viewer on attach, that I am willing to do.
>
> Under your scheme I will first have to manually configure the AO into the
> viewer, then associate it with the inventory. Then I will no longer have any
> record in the inventory of what AOs are associated with each outfit. If I'm
> using SL from another computer, or I lose the profile directory on my
> computer, all of that's gone, forever. There's no way I'd ever be able to
> reconstruct it.
>
> And for what benefit? A barely measurable drop in my script time (which is
> already very low), a savings of 16k of script memory (and people are
> routinely walking around with megabytes of scripts), and possibly better
> behavior in laggy areas. It's simply not worth the effort and risk.
_______________________________________________
Policies and (un)subscribe information available here:
http://wiki.secondlife.com/wiki/OpenSource-Dev
Please read the policies before posting to keep unmoderated posting privileges
