Share Your Input: The Next LabVIEW Feature to Go Open Source

[crossrulz]

---

@thomas-allibe wrote:

And NXG would be "fun"

---

Nope. I have no desire to figure out the C# involved, which, to my knowledge, the entire project is written in (no G code).

[Jacobson]

Q has a presentation which I think covers this although it's just about adding pages. I'm not sure if it's also relevant to editing existing pages.

https://youtu.be/Sn8ZCYqMoA4?t=3658

[IlluminatedG]

• All of the free features of VIPM
• Class creation / properties. I've implemented my own search features for selecting parents and was told flat out that NI wasn't interested.
• Tim already said it so second on GSW. Making it more extensible and plugin based so projects like CTI can streamline new user onboarding and internal company usage could surface custom tooling and other project management stuff. I've been told it's already plugin based and not sure if they meant more than the XML configuration which id just call configurable launching but not customizing layout/implementation of GSW.
• Palette tooling. Plz plz plz

  ---

[Les__Bartel]

Config file (.ini) read/write.

[Mads]

The Edit Events dialog...

Then I would redesign it to be optimized for event creation. Edits come second...As discussed here:

https://forums.ni.com/t5/LabVIEW-Idea-Exchange/Make-it-possible-to-select-multiple-event-sources-whe...

[SlippinJimmy85]

The Quick-Drop dialog/engine.

[Intaris]

Give us the information needed to implement a community tool to manage the Compile Cache better:

https://forums.ni.com/t5/LabVIEW-Idea-Exchange/More-control-over-deleting-compile-cache/idi-p/321472...

[ShockHouse]

- NI LabVIEW Command Line Interface

- LabVIEW Unit Test Framework

[Jay14159265]

---

@billko wrote:

Let's make NXG open source.  Couldn't hurt.

---

Yes, please. I was excited to switch to NXG and got to do a few projects in it. It would be a perfect candidate for open source. There was so much effort already put into it, let the community pick it up and go from there. 

[sergiovelderrain]

---

@Quiztus2 wrote:

Make the documentation of VI's open source. Periodically I think that some information is missing in the VI's documentation.

I would like to see a repo, where one could create a pull request for VI documentation.

E.g.

To more specific class:

VI Doc: 

Typecasts a reference, such as a control or a type definition, to a more specific class or interface in the inheritance hierarchy.

Returns the input's default value when an invalid type cast occurs.

Html Doc:

... 

For example, if Class A inherits from Class B, a variable of type B can hold a value of type A. You can use the function to downcast from type B to type A. If the typecast is invalid, this function returns an error at run time and an instance of the input's default value.

...

The pull request could then be peer reviewed for mistakes or different optimizations.

---

Just so you know, that my potential list includes this as #1. Thank you for your recommendation.