LabVIEW Idea Exchange

cancel
Showing results for 
Search instead for 
Did you mean: 
David S.

Better Indication of Access Scope

Status: New

There are lots of ways to convey information graphically to your users. For example, you can use size, shape, pattern, and saturation/transparency. The differentiation between any two pieces of information becomes even more apparent when you use multiple approaches.

 

One of the things we are commonly taught not to lean on for differentiation is color. To differentiate the color of two objects, the eye needs a sizeable area of the colors to be able to view them. (Figuring out the color of small or thin objects can be very hard.) And then there's the ever-present threat of colorblindness in the user.

 

Why are the access scope icons used in classes and libraries small and identially shaped, differing only in their colors? I find myself leaning in to the monitor any time I want to figure out whether a class method is private or protected. It shouldn't have to be this way.

 

unhelpful.PNG

 

I'd like to see access scope glyphs that are:

  1. Slightly larger. So much detail is put into the project item icons, and so little of it is useful for determining what kind of project item that is. Why not dedicate more of that space to the differentiating information, like the object's access scope glyph? That would keep me from squinting so often.
  2. Uniquely shaped. UML uses a plus sign (+) for public scope, a minus sign (-) for private scope, a hashmark (#) for protected scope, and a tilde (~) for package scope. I'd like to see the glyphs shaped like this, so at a glance I can know a project item's scope without needing to figure out its color.

(Since LV doesn't have a "package" item, I would suggest that we overload the tilde (~) for Community-scoped items.)

 

helpful.png

 

I am not an artist, nor a graphic designer. If you like my idea but hate my glyphs, I'm open to replacing them with prettier ones. 🙂 In case you do like my glyphs, I've attached them for anyone to use.

David Staab, CLA
Staff Systems Engineer
National Instruments
1 Comment
alsoACS
Member

I like the idea of using UML notation.  I'd like to see those symbols as graphics, along the lines of what is usually done in windows with check marks and x marks.