Hi Rick,

    I sent the bare bones of my Tree View I designed for the Uninstall program. 
It works like that, for I make categories and you go down the tree view for 
that category then you expand it and a list of programs are in that category, 
then expand any program and it gives the properties available for it.

    Dave needs to attempt to understand what I have done and use that as he 
wants to. Select an article, gets it main color then get the varieties of that 
color. this is exactly what I do and he should be able to handle it.

    I have not had time to make my program clearer for him to use for it is 
split up into many sections and there is documentation but jumping around is 
the problem. Also the way I use the ID's or data value of the tree element and 
that can be confusing only because I left in there, but commented out, the test 
stuff to see if it works...

    The tree view is a good way to do it, the ID values is the key to know what 
you have selected...

        Sincerely
        Bruce

  Sent: Monday, April 01, 2013 9:14 AM
  Subject: Re: Suggestion needed, is a Treeview the right thing?


  Hi Jamal: So much depends on what the application will be used for and 
exactly what options will be made available.
  If the number of colors and sub-colors are not too many then all the colors 
could be grouped in a list or dropdown list and there is just one color for 
each selection instead of one color and then another sub-color.
  Blue:
  Blue-Light
  Blue-Navy
  Blue-Sky
  Red:Red-Dark
  Red-Light
  etc...
  Then first letter navigation gets you to the base color and a sighted user is 
set and a blind user can just arrow key or mouse down the list of sub-colors to 
pick one. That eliminates the complexity of having a TreeView or a second color 
ListBox.
    I dont recall if he said he is going to allow for a cloth selection or not 
so couldnt do a solid layout.
    But if only an item and a color then only 2 dropdown lists or ListBoxes are 
required, if cloth is included then 3.
    A Review TextBox, Label or even a PopUp with the Review Window is the only 
other control other than the buttons.
    This is pretty straight forward to implement in vb.net and easy to navigate 
for both sighted users, mouse users, and sighted screen reader users, first 
letter navigation - hit the letter b to go to the Blue group then just cursor 
or mouse down and click a sub color.
    This is one layout I would consider in place of a sub-color control.
    Also, he didnt mention but if a production application it is quite likely 
there wont be the same colors available for socks, shirts and pants so the 
lists, the Color List at least, would have to be dynamic
    Then in the SelectedIndexChanged event the color box would be populated 
with the appropriate colors for each item as it is selected in the ClothingItem 
List.
    If Cloth is another selection, again I dont know, when a different 
ClothingItem is selected, or different cloth is selected, the appropriate 
values need to be updated in the child boxes. For a ClothingItem the cloth and 
the colors need to be set and a default cloth and default color for the default 
cloth set as the selected index of those boxes for the selected ClothingItem.
    Two things of note...
    1) This might not be the best layout using VBS since I am not familiar with 
the events of the VBS controls and Dialogs.
    2) If there is going to be a database or xml file or some other way to 
dynamically load contents into the boxes I would design that first and see what 
technicals are available for loading the available cloths for a Selected 
ClothingItem and what colors are available for each type of cloth.
    Then populate the file, db or whatever with a few colors like the ones 
mentioned above for testing my UI which I would then layout and test with the 
limited inputs.
    Rick USA

Reply via email to