Better terms organization, easier to learn and use

[Sea226354]

I have something to say with LabVIEW programming.
As we all know, LabVIEW is widely used around the world in the field of instrument operation. The most prominent feature of LabVIEW is the graphic language editing, which covers a large quanity of function terms.
However,as it was said that negative and positive always go together,a large quanity of function terms cover almost every details of daily operation while it could cause large confuse to freshmen.
The initial step into the LabVIEW world is easy to take while it is rather difficult to become adept at LabVIEW programming.
I think this phenomenon was caused by the fact that most people cannot understand the organization method of the function panel exactly, which can be solve by reconstruct the function panel in a more logical way.Here are the details of my suggestions:
First of all, all the function can be divided into four following group:
1. The convertion between the same types and scales of data ,which can be realize by property node in dropdown list;
2. The convertion between the same types but different scale of data;
3. The convertion between differnet types of data;
4. Something about the outside data.(The "data" in the three points above refers to inside data, which can be used and processed by the programme directly. )

Point One can be reserved in the old way.
Function terms in Point Two and Three can be reorganized in the 2D form.
Funtion terms in Point Four can be reorganized by another 2D form.

In this way, user can find the very terms much more easily . So LabVIEW using can spread to much.

[RavensFan]

I'm sorry, but I don't understand what you are proposing here.  It seems more like an essay than a new idea to improve LabVIEW.

Can you give us some sort of example as to what you are looking for?

(What is with all the jscript code at thet bottom of your message?)

[altenbach]

The current palette organization is actually very logical and hierarchical. Rearranging everything into a different hierarchy would be a major problem for longtime users.

Remember that you have several choices on how the palettes are organized. Look in the options dialog.

There is also quickdrop that allows you to get any function by (partial) name almost instantly.

If you are confused by the general programming environment, start out with a few basic tutorials.

All that said, I really don't understand what you mean. "Convertion" is not a word. Do you mean convention or conversion?

1. What can be realized "by property node in dropdown list". How is this supposed to work?
2. What is the meaning of "different scales"? Different how? Different to what?
3. Data "outside" of where? You never defined the terms "inside" and "outside". Where is the demarcation?

Maybe you can do a graphical mockup of how your idea would look like and attach a picture.

[Darren]

Any idea that has not received any kudos within a year after posting will be automatically declined.