What new features would you like to see in G#?

[Mattias_Ericsson]

Hi all,

What kind of support would you like to see in future versions of G#? Please let me know of all kinds of ideas and new features!

[Fox_Mccloud]

Hello Mattias!

I love the G#-Ide so big up!

I would like to be able to pick a "double nested" in placement structure from the G# function tools palette and place it in a block diagram. The first in placement structure should have a DWR and the second a unbundle.

This would further improve my speed as a programmer as I grow tired of building these nested inplacement structures.

Thanks for all your hard work!

[Mattias_Ericsson]

Hi, this is a really good idea.

I just tested and it work just fine. I will include this in the next release in the G# functional palette menu. I will then remove the Memory Control subpalette from the menu, since the only reason it was included was to get the easy access of the In Place Element Structure, since it is quite hidden in the "normal" palettes. This is much better. It actually solved an other issue, I noticed in the LabVIEW 2010 beta that the In Place Element Structure has been moved from Memory Control to the Programming->Structures palette (the same palette where you find case, for loops etc. which is quite logical) and that makes the Memory Control totally obsolete in the G# menu.

See the attached image what it will look like in the next release.

Thanks!

[Fox_Mccloud]

Haha.. Fast response on that one!

Cheers!

[chris.b]

Wow, very fast indeed

[CPAC]

Hi,

I would like som more refactoring features in G#.

The need for refactoring is always present in large SW-projects. Built-in features in G# that encurages refactoring and enables maintaining a nice design would be great!

Example of such features could be:

- A class overview that shows which methods uses which attributes

- "Open all methods using attribute x"

- "Show unused attributes"

- "Split class" (helps you devide a class that has grown to big or has to much responsability)

- "Merge classes" (is this useful?)

- ...

/Skipper Olsson

[Mattias_Ericsson]

Hi,

This is also a very good idea. I have to experiment a bit with scripting to see how I can read out which of the elements inside the In Placement Structure that is selected. If that is possible, the rest isn't hard to do. I will put it on my "to do" list.

I had some thoughts of my own regardning analysis of classes, mostly use of methods and I read a really intrestering blog post a few days ago regarding class feature diagrams. All you do is create a box for every field and a bubble for every method in your class and then draw an arrow from each method to the fields and methods it uses.  Check out the link below (May 24th, 2010). This is basically the same thing but it is nicely visualized.

http://michaelfeathers.typepad.com/michael_feathers_blog/2010/05/class-splitting-and-the-graph-view-...

Thanks,

Mattias

[PatrikC]

Hi,

I like that feature, that would be a good way to show how the classes interact. with methods and attributes.....a thought though, is this not what a sequence diagram does in a sence?

[Mattias_Ericsson]

Well, they are related, but a UML sequence diagram focus more on the flow of operations. The feature diagram is more a check to see if you have high cohesion in your class and not vilolating the SRP (Single Responsible Principle) which is one of the five SOLID priciples.

/Mattias

[mrutm]

Hi,

I would like to see G# will support the conversion from native LVOOP class to G# class and vice versa. By using this features, we can convert the old LVOOP class to G# class without having to re-create it.

Thanks