Image Designer Archive
Thread: Let's Talk About: The ID UI and Client's Peace of Mind
Neige
Fri Sep 10, 2004 7:40 am
#14
the simpliest way to avoid grief would be to have the customer rendered in hotpants in the UI, whatever he is wearing. (this would also solve the "persisitence of armor" bug)
Juny
Fri Sep 10, 2004 12:02 pm
#15
Sorry to not so along this subject, but I have an idea about UI.
Add to 'Clothing' tab for ID window. On the preview window, you can choose any clothes what tailor can make. After commint to customer, they recevies a mail what clothes and color code (need to be display on crafting window too...) selected on it.
Customers are simply forward the mail to his/her favorite tailor.
Almost of customer need to get new clothes after change the hair/fur color...
It's just brows, but this is not fair for tailor, so,make it touse the skill to need a item call 'holo-catalog' what made by tailor.
Rrowann
Fri Sep 10, 2004 12:59 pm
#16
I saw an idea for a changing room for a tailor, where the room would be linked to what boxes a tailor had, so a customer could go in, pick his or her own outfit, and then the Tailor would get a sort of order for it. I thought it was cool. But in the end, I think picking clothes is for people to do with Tailors, not ID's.
The last thing I want to be approached for is to stand around and be a hypothetical changing room while someone tries to decide what shade of brown his leather coat should be when he has it custom-made.
Maisland
Fri Sep 10, 2004 2:46 pm
#17
Heh... I've had such requests myself... to match eyes, hair, tattoos etc to clothing worn... and even matched one of my characters eyes to her gown myself.
Vorpaks wrote:
Some people (okay, me) try to match their looks to what they are wearing though so it is useful to be able to see the clothes.
"Can you even dye my eyes to match my gown? Jolly old town!"
Kwee
Fri Sep 10, 2004 3:17 pm
#18
Maisland wrote:
Heh... I've had such requests myself... to match eyes, hair, tattoos etc to clothing worn... and even matched one of my characters eyes to her gown myself.
Vorpaks wrote:
Some people (okay, me) try to match their looks to what they are wearing though so it is useful to be able to see the clothes.
"Can you even dye my eyes to match my gown? Jolly old town!"
Same here, especially given I do my Tailoring and ID in the samelocation
And I change my own colors to match outfits. Anyone can accuse me of playing Barbie Beauty Boutique and be absolutely correct 
I'll pass this thread along once it grows a bit more Lots of good brainstorming so far
TechnoCan
Sat Sep 11, 2004 7:41 am
#19
I think there are several possible things to use as a saveguard for the client.
1.) A list of changes as stated before. This list could even be used to cancel a selected change and not only the complete session. which is something I would have liked to have several times during my ID-work.
2.) A checkbock system them gives the client the ability to allow us to change a given part/aspect of their body. This would be pretty annoying since we would have to tell alot of customers how this works again...
3.) a Checkbox system that shows the areas/aspects of the body changed... which is basically a downgrade of #1.
4.) It could help if the 'after' avatar in the client window behaves like the one we see in our interface so the client actually can see what we do... like zooming in on the head while changing the eyecolor or face-features... maybe combined with a message that tells the client which part is currently changed. this could be combined with one of the above ideas.
And yes, I would welcome the ability to match a skin/eye/marking-color with the color of another object... not that easy to code but it would be awsome
May the Force be with you all!
TechnoCan
SakeO
Sat Sep 11, 2004 9:20 am
#20
What I think we need is a UI that clearly allows the customer to know what has been changed without requiring them to know what they are doing to complete the changes.
Many of our customers rarely use our skills and it could be very frustating for IDs if the process got bogged down by a necessity to spend the majority of our time training them how to use their side of the UI.I don't think most customers would want the bother of it either. I do not mind justifying why I changed something they did not expect to get the effect they wanted but, having to continually ask them for specific permissions could get very annoying.
-customer side indicators for each tab thata change was made in is whatI favor
-a modifcation report, with or without exact values, that pops up with the cancel/accept buttons could be useful
-system messages could be a good way ("Chasing Amy has proposed an increase to your nose protrusion")
Chasing Amy - Bria
Syzygy-Gorath
Sat Sep 11, 2004 11:20 am
#21
I think the report on accept would be the best way to do it. Great idea there. Client clicks accept and gets a secondary popup that states "Soandso is proposing the following changes: [changes here]. Are you sure you want to accept?" Declining at that point would NOT cancel the ID session, instead it would return the client to their UI and deactivate the ID's 'accept' button to allow for explanations/further changes. (And for the love of god, can we PLEASE get the ID-side to stay open after accept has been clicked?)
SakeO wrote:
What I think we need is a UI that clearly allows the customer to know what has been changed without requiring them to know what they are doing to complete the changes.
Many of our customers rarely use our skills and it could be very frustating for IDs if the process got bogged down by a necessity to spend the majority of our time training them how to use their side of the UI.I don't think most customers would want the bother of it either. I do not mind justifying why I changed something they did not expect to get the effect they wanted but, having to continually ask them for specific permissions could get very annoying.
-customer side indicators for each tab thata change was made in is whatI favor
-a modifcation report, with or without exact values, that pops up with the cancel/accept buttons could be useful
-system messages could be a good way ("Chasing Amy has proposed an increase to your nose protrusion")
Chasing Amy - Bria
ToppDog
Sat Sep 11, 2004 1:16 pm
#22
My proposal for a "Universal Numbered Color Palette" would have worked better for this & would have been equally usable for ANY profession where color selection is an option.
ToppDog
Sat Sep 11, 2004 1:25 pm
#23
As far as the main post goes, one solution may be to divide the session into parts, meaning that we couldcombine the part ofthe old system where the player had to okay every change individually by clicking a button called "accept this change" or something, but keep theaspect of the new part where they could click a separate button to "Finalize All Changes & End ThisID Session" or something along those lines.
Syzygy-Gorath
Sat Sep 11, 2004 1:34 pm
#24
ToppDog wrote:
As far as the main post goes, one solution may be to divide the session into parts, meaning that we couldcombine the part ofthe old system where the player had to okay every change individually by clicking a button called "accept this change" or something, but keep theaspect of the new part where they could click a separate button to "Finalize All Changes & End ThisID Session" or something along those lines.
In that we don't technically commit anything until the very end, that would be somewhat annoying. I mean, how would it know when to okay a change? With every tick of the slider? Every color we try? Ugh.
Semi-unrelated, in reference to my earlier complaint about the UI closing the second we hit accept, why doesn't the UI mimic the secure trade window with an accept checkbox and an ok clickie? It would seem to make a lot more sense; I don't know about you guys and gals, but I've had many instances of "Ready?" "Sure." *click* "Oh wait!" "Too late." and it seems to me the checkbox/button scheme would prevent a lot of this from happening.
Gyopi
Sat Sep 11, 2004 3:10 pm
#25
Vorpaks wrote:
I agree with no click-boxes. The biggest pain about ID for me is making sure the customer, every customer, is properly trained before we do the migration or whatever. Adding more things to explain leaves more room for frustration and error.
Well, they *shouldn't* be necessary, but the point of this thread is that some IDs are changing people's looks without permission when clients come in for a stat migration. In the old days this was never a problem because you did one thing at a time. Changing things without permission or notification is something that should *never* happen and we are beginning to get a bad reputation because of it. My suggestion (even though I really hate giving up creative control)is basically *uncheck* boxes where by default all changes are made, but the client has the decision to skip some changes. I know that if I were a client and waited on line for stat migration I would be pretty mad if I got the list of changes that I did not ask for along with my migration and my only choice was to refuse the migration and start all over again.
ToppDog
Sat Sep 11, 2004 4:13 pm
#26
Na, I meant to incorporate how we used to do it before this whole new UI came to be. Lets say we agreed to do some ID for a customer...we would click on the radial to initiate a session & the customer would do the same to accept the session. We would be able to chat during the whole process like before to figure out what the customer wants. Ifthey only want Migration thenthey dotheir thing & we wait for the timer to run out, but ifthey want a "real" ID change, thenthey can tell you want they want or you can make suggestions, etc. Once you actually make a change forthem to see, you press commit (just like the old way) & they will decide ifthey like it or not & can press "accept this change" or "deny this change" for each option you offer, such as weight, height, hairstyle, etc. Only at the end of the timer (or even later if you are doing along makeover) will you both agree that you are finished with the session & each click on a totally different button that wll make all the agreed to changes final & transfer the agreed to price & completely end the session.
Syzygy-Gorath wrote:
ToppDog wrote:
As far as the main post goes, one solution may be to divide the session into parts, meaning that we couldcombine the part ofthe old system where the player had to okay every change individually by clicking a button called "accept this change" or something, but keep theaspect of the new part where they could click a separate button to "Finalize All Changes & End ThisID Session" or something along those lines.
In that we don't technically commit anything until the very end, that would be somewhat annoying. I mean, how would it know when to okay a change? With every tick of the slider? Every color we try? Ugh.