• Post Reply Bookmark Topic Watch Topic
  • New Topic

UXP Advice  RSS feed

 
Gregg Bolinger
Ranch Hand
Posts: 15304
6
Chrome IntelliJ IDE Mac OS X
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
On a particular form I have two tables that are a parent-child relationship. The parent table contains Parameters which consist of the following columns:

Name, Required, Description

The child table contains Values for each Parameter and has the following columns:

Value, Description



So what happens is as you select a Parameter Row the Values table updates to show the values for that particular parameter. It works but I don't really care for the UXP. It's not very self explanatory and prone to user errors. I'm looking for advice on a better way to handle this.
 
Ilja Preuss
author
Sheriff
Posts: 14112
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Tricky. Perhaps a TreeTable that shows all the data in one widget?
 
Gregg Bolinger
Ranch Hand
Posts: 15304
6
Chrome IntelliJ IDE Mac OS X
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Originally posted by Ilja Preuss:
Tricky. Perhaps a TreeTable that shows all the data in one widget?


I thought about that but this table is also editable and the Tree Table implementations I've seen seem overly complex.
 
Maneesh Godbole
Bartender
Posts: 11445
18
Android Eclipse IDE Google Web Toolkit Java Mac Ubuntu
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Use a panel instead of the second table. This will have a textfield for name and a text area for description.
 
Gregg Bolinger
Ranch Hand
Posts: 15304
6
Chrome IntelliJ IDE Mac OS X
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Originally posted by Maneesh Godbole:
Use a panel instead of the second table. This will have a textfield for name and a text area for description.


But I need to be able to enter more than 1 at a time. The thing is the two tables work great. It's just not very intuitive. And all this data needs to be able to be entered very quickly and I have to be able to see all the data all the time (give or take some scrolling).
 
Maneesh Godbole
Bartender
Posts: 11445
18
Android Eclipse IDE Google Web Toolkit Java Mac Ubuntu
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Originally posted by Gregg Bolinger:


But I need to be able to enter more than 1 at a time. The thing is the two tables work great. It's just not very intuitive. ... I have to be able to see all the data all the time (give or take some scrolling).


I dont get this. From what I understood, the top table displays the parent attributes and the bottom table displays the child attributes for the selected parent element in the top table. So it is a one to one relationship isnt it? If yes, can you please explain what you meant by "But I need to be able to enter more than 1 at a time".

Or is it that the child/bottom can have multiple values for one particular parent?
 
Gregg Bolinger
Ranch Hand
Posts: 15304
6
Chrome IntelliJ IDE Mac OS X
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Originally posted by Maneesh Godbole:
Or is it that the child/bottom can have multiple values for one particular parent?


Yes.
 
Ilja Preuss
author
Sheriff
Posts: 14112
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I don't have a revolutionary idea, but perhaps an evolutionary approach will bring you somewhere:

First, would it feel better if you put the two tables side by side instead of on top of each other?

Alternatively, what about putting the buttons on the side of the tables? That would make it more obvious which table they belong to, and put the table contents closer together. (I would also think about using icons + tooltips instead of the text.)

Last but not least, do you really need *two* save buttons?
 
Maneesh Godbole
Bartender
Posts: 11445
18
Android Eclipse IDE Google Web Toolkit Java Mac Ubuntu
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Originally posted by Gregg Bolinger:


Yes.


Ok.
My 2 cents.
Add a fourth column called values. Provide a custom renderer which will display a JButton("\u2026"). When the user clicks on that button, you pop up the second table just like the JDateChooser does (I presume you are aware of this component.

From the usability perspective, the user has clicked the button so he is aware that whatever dialog/popup is now presented, is pertaining to the row he clicked on.

This way, you still get to present the data in a tabular format, and the user is very clear regarding the parent child relationship between the values.

Does this make sense?
 
Gregg Bolinger
Ranch Hand
Posts: 15304
6
Chrome IntelliJ IDE Mac OS X
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Originally posted by Maneesh Godbole:


Ok.
My 2 cents.
Add a fourth column called values. Provide a custom renderer which will display a JButton("\u2026"). When the user clicks on that button, you pop up the second table just like the JDateChooser does (I presume you are aware of this component.

From the usability perspective, the user has clicked the button so he is aware that whatever dialog/popup is now presented, is pertaining to the row he clicked on.

This way, you still get to present the data in a tabular format, and the user is very clear regarding the parent child relationship between the values.

Does this make sense?


That was the original approach however the client didn't like it. The reason being this limits the values that can be displayed and you can't see the description for each value all at the same time.
 
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!