Home Community User Groups Partner Groups GCentral G Idea Exchange

G Idea Exchange

Community Browser
Top Authors
View All
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
Guidelines for posting ideas

On behalf of the G Idea Exchange and GCentral, thanks for considering posting an idea for discussion. Here are a few guidelines to think about before posting the idea. 

Does the idea already exist in the community or on VIPM?

The effort of creating two competing ideas is usually not worth the time but is better spent to improve the existing idea with the functionality. If your idea differs significantly from the existing solution then write that in the idea post.

Is the Idea a request for a new LabVIEW primitive?

If the idea requires new LabVIEW primitives, the idea belongs on the LabVIEW idea exchange instead of here. 

Will your idea improve the productivity of everyone in the community?

It is important that other developers can see that the idea is something that they would vote for. Sometimes an idea is specific to a particular problem in your current project, which would be great if there was a solution, but it is hard to see the reusability of the idea.

Would you be willing to release the result of your idea under a permissive open-source software license?

In order for your idea to be used by others it would have to be released under a permissive open-source license, defining the rights of usage. The G Idea exchange can only support and possibly fund ideas that will be released as open-source. 

Discussions about an idea.

When you post an idea on this board it is open to discussion, and improvement by the community, and other developers can join in and ask questions about the idea. Consider these questions as sources for expansion and improvement of the idea rather than critique. When commenting on or discussing an idea please keep a respectful tone.

Best regards

The GCentral Idea Exchange

Post an idea
wiebe@CARYA

Search utility for LabVIEW

Status: Development Started Submitted on ‎11-08-2023 09:56 AM Submitted by Knight of NI Knight of NI on ‎11-08-2023 09:56 AM 3 Comments (3 New)

Description
By treading VIs and LV projects as graphs, we can use graph database queries to search\find things.
Submitter
Wiebe.
LabVIEW Compatibility
20 and up.
How would the user interact with this tool?
At first by typing a query, eventually drag and drop, autocompletion, etc.
Distribution Method
T.B.D.
Development Target Cost
A lot up to now. More needed. Amount depends on scope...
Other Notes
This might help:

antsundq

Refactoring Suite for LabVIEW

Status: New Submitted on ‎11-23-2023 01:33 PM Submitted by Active Participant Active Participant on ‎11-23-2023 01:33 PM 6 Comments (6 New)

Description
To cite Sam Taggart: "A good refactoring suite for LabVIEW is desperately needed. IMO the worst offenders are classes/interfaces", taking the words out of my mouth. 
 
Good tooling for automated refactoring can speed up development and reduce risk of making mistakes. By automating tedious tasks the developer may focus on design over housekeeping. Most other languages have good tools for refactoring through various IDE:s, and there is not really any reason we could not have that as well.
 
I'm sure there are a lot of tools out there I am not aware of, which could be leveraged. I think the right tools should be collected or developed, to be put into a suite of high quality refactoring tools.

Submitter
Anton Sundqvist
 
LabVIEW Compatibility
LabVIEW 2020 (first version supporting interfaces)
 
How would the user interact with this tool?
Through suitable LabVIEW project integration.

Distribution Method
VI Package (.vip)

Development Target Cost
$?

Other Notes
I'm happy to work on this myself together with whomever wants to contribute. I think we need some community guidance and suggestions for what tools are needed and how they should be implemented in LabVIEW. The purpose of this post is to gauge the interest within the community and gather ideas. 
I'll start with a few tools I would like to see, let's see if we can get it rolling:
- Extract interface from class
- Override and save all must override VI:s
- Generate constructors/destructors (not that they are strictly needed, but they are useful for communicating intent. Using them by convention makes it easier to locate each place a class is instantiated, compared to block-dropping)

View All (1)
Neil.Pate

Some kind of hotkey to run a top-level VI

Status: Released Submitted on ‎08-30-2023 03:09 PM Submitted by Active Participant Active Participant on ‎08-30-2023 03:09 PM 9 Comments (9 New)

Description
In Visual Studio or similar environments it is common to have a shortcut key (F5 for example in VS) build and run some preconfigured project. It would be really cool if we could have the same thing in the LabVIEW IDE. Pressing F5 (or whatever key was configured) from anywhere "inside" LabVIEW would then start a VI.  
Submitter
Neil Pate
LabVIEW Compatibility
The older the better
How would the user interact with this tool?
A (configurable) key. Default would be F5 to mimi what is done in Visual Studio
Distribution Method
VI Package (.vip)
Development Target Cost
$?

Other Notes
As a first attempt this could probably be implemented using Quick Drop, but I think it deserves to be baked into the actual IDE itself.

Schliepe

Proper attribution of deployed open source tookits.

Status: New Submitted on ‎01-08-2024 01:50 PM Submitted by Member Member on ‎01-08-2024 01:50 PM Comment

Description
This would be a tool that is used to gather information about the licensing of dependencies in a project, specifically the open source attributions. The output would be a file with all of the dependencies and licenses and attribution statements that could be included as a readme or other appropriate file to comply with the requirements of the licenses.  In particular for deployed executables where some licenses require the inclusion of the open source license or attribution in deployed code. 
 
Really the idea is to make it easier to roll these up.  So I would see this being a developer tool that would create a text file that could be added to the build spec. 

Submitter
Erich Schlieper
 
LabVIEW Compatibility
The earlier the better.
 
How would the user interact with this tool?
Through suitable LabVIEW project integration.

Distribution Method
VI Package (.vip)

Development Target Cost
$?

Other Notes
 

JKSoerensen

Enhanced LabVIEW Inheritance Dialog

Status: New Submitted on ‎05-10-2023 03:57 PM Submitted by Member Member on ‎05-10-2023 03:57 PM Comment

Description
With hundreds or thousands of classes loaded, the LabVIEW class inheritance dialog can be very cumbersome to navigate. This utility would provide an alternate dialog for modifying a class' inheritance. The main enhancement would be the ability to filter classes by name (e.g. entering "hardware" would only show classes who have "Hardware" in the name) so that navigating to the class you intend would be easier.
Submitter
Thomas Robertson
LabVIEW Compatibility
The older the better
How would the user interact with this tool?
Right-click menu on class in project that opens a new inheritance dialog.
Distribution Method
VI Package (.vip)
Development Target Cost
$?

Other Notes

CaseyM

Quick VIAN (VI Analyzer)

Status: Released Submitted on ‎03-29-2023 05:36 PM Submitted by Active Participant Active Participant on ‎03-29-2023 05:36 PM 3 Comments (3 New)

Description

This tool would provide a way to quickly run VI Analyzer on the subset of files that have changed since the last commit/push (Git is a prerequisite), present the user with a way to select a subset of those files, and then run user-specified VI Analyzer tests on them.
 
Developer
Sam Taggart
 
LabVIEW Compatibility
LabVIEW 2020+, 32 and 64-bit. Might be possible to develop in earlier versions, but would take some investigation.
 
How would the user interact with this tool?
The tool would be launched through QuickDrop.

 

Distribution Method

VI Package (.vip file)

 

Other Notes

Future enhancements could include:

  • Automated testing of the tool (for easier community development)
  • GCLI API

JKSoerensen

Bowzer Enhancement: View "Fundamental" Actor Methods

Status: New Submitted on ‎05-10-2023 04:11 PM Submitted by Member Member on ‎05-10-2023 04:11 PM Comment

Description

Bowzer already allows you to view the payload methods associated with an actor's supported Messages. This update would also allow developers to browse the dynamic dispatch methods included with EVERY Actor:

  • Actor Core

  • Handle Error

  • Handle Last Ack Core

  • Receive Message

  • Pre Launch Init

  • Stop Core

  • Substitute Actor

  • Uninit (new in LV2022)

Developer

CaseyM

 

LabVIEW Compatibility
Should be compatible with LV2020

 

How would the user interact with this tool?

This would be an extension to Bowzer the Browser from Zyah Solutions

Distribution Method

VI Package

Development Target Cost
$400

 

Other Notes
Essential Features
This is an enhancement to an already existing utility, so everything listed in the description would need to be implemented.