drneau.com Forum Index drneau.com
A discussion board for drneau.com
 
 FAQFAQ   SearchSearch   MemberlistMemberlist   UsergroupsUsergroups   RegisterRegister 
 ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 

Video - Console Dashboard Designer (v3Beta2)

 
Post new topic   Reply to topic    drneau.com Forum Index -> Consoles
View previous topic :: View next topic  
Author Message
drneau
Site Admin


Joined: 13 Feb 2005
Posts: 2385
Location: Woodbury, MN

PostPosted: Wed May 28, 2008 9:52 pm    Post subject: Video - Console Dashboard Designer (v3Beta2) Reply with quote

A video I created demonstrating the dashboard designer for v3. Created around April, 2008:

http://drneau.com/v3Preview/dashboardDesigner/consoleDashboardDesigner.html
_________________
--
Dr. Neau (not a real doctor)
http://drneau.com
http://home.comcast.net/~jneau


Last edited by drneau on Sun Jun 01, 2008 3:08 pm; edited 3 times in total
Back to top
View user's profile Send private message Send e-mail Visit poster's website
rastapete
Founding Father
Founding Father


Joined: 13 Feb 2005
Posts: 401
Location: 'Ipsa' this, you pissy little bitch!

PostPosted: Thu May 29, 2008 6:47 am    Post subject: Reply with quote

Very nice, doc.

I like the way editing the properties of multiple components only brings up the common properties. You're right, it is slick!

An interface question though, would it be possible, and desirable, to show all the properties in that dialog, but only have the common properties be active?

There would have to be a visual cue of course, maybe have the inactive properties greyed out and the active ones normal.

Which brings up another question, why require users to check a box for the property that they are going to edit? Is it like that also when editing a single component?
Back to top
View user's profile Send private message
drneau
Site Admin


Joined: 13 Feb 2005
Posts: 2385
Location: Woodbury, MN

PostPosted: Thu May 29, 2008 7:39 am    Post subject: Reply with quote

rastapete wrote:
Which brings up another question, why require users to check a box for the property that they are going to edit? Is it like that also when editing a single component?


Let's say you try to edit 5 components and each one has a different foreground color. You may want to change the foreground for each, or you may want to leave it alone. The checkbox is your way of specifying which way you want to go. The checkbox is your way of saying "I want to change the value for this attribute" vs. "leave this attribute as is".

It isn't like that when editing one component. With one component, all widgets reflect the values of the component you are editing.
_________________
--
Dr. Neau (not a real doctor)
http://drneau.com
http://home.comcast.net/~jneau
Back to top
View user's profile Send private message Send e-mail Visit poster's website
rastapete
Founding Father
Founding Father


Joined: 13 Feb 2005
Posts: 401
Location: 'Ipsa' this, you pissy little bitch!

PostPosted: Thu May 29, 2008 11:25 am    Post subject: Reply with quote

drneau wrote:
rastapete wrote:
Which brings up another question, why require users to check a box for the property that they are going to edit? Is it like that also when editing a single component?


Let's say you try to edit 5 components and each one has a different foreground color. You may want to change the foreground for each, or you may want to leave it alone. The checkbox is your way of specifying which way you want to go. The checkbox is your way of saying "I want to change the value for this attribute" vs. "leave this attribute as is".

It isn't like that when editing one component. With one component, all widgets reflect the values of the component you are editing.


Thanks. I see the last point. With respect to the first, I understand that the checkbox is telling the app. these things. I am wondering whether the act of changing the value does not accomplish the same thing in one step. Having to speak entirely hypothetically may be hindering me.
Back to top
View user's profile Send private message
drneau
Site Admin


Joined: 13 Feb 2005
Posts: 2385
Location: Woodbury, MN

PostPosted: Thu May 29, 2008 1:29 pm    Post subject: Reply with quote

rastapete wrote:
drneau wrote:
rastapete wrote:
Which brings up another question, why require users to check a box for the property that they are going to edit? Is it like that also when editing a single component?


Let's say you try to edit 5 components and each one has a different foreground color. You may want to change the foreground for each, or you may want to leave it alone. The checkbox is your way of specifying which way you want to go. The checkbox is your way of saying "I want to change the value for this attribute" vs. "leave this attribute as is".

It isn't like that when editing one component. With one component, all widgets reflect the values of the component you are editing.


Thanks. I see the last point. With respect to the first, I understand that the checkbox is telling the app. these things. I am wondering whether the act of changing the value does not accomplish the same thing in one step. Having to speak entirely hypothetically may be hindering me.


Believe me, I thought about that.

But keeping track of which ones you've changed could be daunting.

AND...what if you change one and then change your mind? Do you cancel the whole dialog?
_________________
--
Dr. Neau (not a real doctor)
http://drneau.com
http://home.comcast.net/~jneau
Back to top
View user's profile Send private message Send e-mail Visit poster's website
Display posts from previous:   
Post new topic   Reply to topic    drneau.com Forum Index -> Consoles All times are GMT - 6 Hours
Page 1 of 1

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum


Powered by phpBB © 2001, 2005 phpBB Group