It bothers me a bit that we (you) would choose to go
for an implementation that is not the best or the
ideal one, ONLY because you want to push out a new
feature "in time".
Personally, I'd first design how I'd want it to look
from the user point of view (what most of the discussion
from the community is about) without taking into account
coding arguments. And once we have that, I'd just
implement it, no matter the costs or time needed.
That is what coders do: they implement what is requested.
Thus, since for almost everything we said so far your
argument is: we can't do that within the given timeframe;
can you defend, or at least make acceptable and understandable
that "a" new feature has to be added in 3 months, even if
that new feauture is a bit inferior compared to what
that UI could have looked like?
Changing it AGAIN in the near future (ie, 6 months later)
is probably not going to happen for several reasons :/
So, not doing it right now has almost the same implications
as deciding to never do it. I'd really like to understand
why that is the best thing to do.
Thanks for discussing this with us,
Carlo Wood <ca...@alinoe.com>
PS With regards to the UI design.
I like the concept of "click wear" inserts the wearable
in a default place, after which you can reorder it.
And where this inserting means "at the top of a folder
that one of the currently existing wearable categories".
It just makes sense.
But, in the end the goal should be that wearer can
determine the order of every texture layer, or at
least to a great extend, including:
- Tucking in jackets or not (jacket <-> pants ordering)
(my proposal was to add a pseudo jacket, below or
above which other jackets are below or above the pants).
- Wearing shirts over jackets (jacket <-> shirt ordering)
(proposal was to be able to dump a jacket in the 'shirt'
folder if one wishes).
_______________________________________________
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
