LabVIEW style guide - Revision history

Logmanoriginal: LabVIEW Style guide was moved to LabVIEW Wiki, redirect to Style Guide

2025-01-25T12:19:42Z

LabVIEW Style guide was moved to LabVIEW Wiki, redirect to Style Guide

← Older revision		Revision as of 12:19, 25 January 2025
Line 1:		Line 1:
	LabVIEW is a graphical programming language, and as a result emphasis is often put on how the code looks, as well as how it performs. Developers may have preferences on one style or another, but one good starting point is the following NI White Papers on Rules to Wire by:		#REDIRECT [[Style Guide]]

	*[~~http://www.ni.com/white-paper/5560/en/ Rules to Wire By Part 1]~~
	*[~~http://www.ni.com/white-paper/4822/en/ Rules to Wire By Part 2]~~

	~~Additionally, there are checklists and style guides that contain more detail when ensuring consistency of style in LabVIEW program code.~~

	*[https://www.ni.com/docs/en-US/bundle/labview/page/labview-style-checklist.html LabVIEW Style Checklist]
	*[https://wiki.dqmh.org/dqmh/styleguide DQMH Queued Message Handler Style Guide]

	~~These guidelines in programming style are important and can be check through automated inspection using the [[VI_analyzer\|VI Analyzer]] toolkit.~~

	~~[[Category:LabVIEW fundamentals~~]]

Austinman: Added links to style guides.

2024-06-14T15:17:26Z

Added links to style guides.

← Older revision		Revision as of 15:17, 14 June 2024
Line 1:		Line 1:
	LabVIEW is a graphical programming language, and as a result emphasis is often put on how the code looks, as well as how it performs. Developers may have preferences on one style or another, but one good starting point is the following NI White Papers on Rules to Wire by:		LabVIEW is a graphical programming language, and as a result emphasis is often put on how the code looks, as well as how it performs. Developers may have preferences on one style or another, but one good starting point is the following NI White Papers on Rules to Wire by:

	*[https://www.ni.com/docs/en-US/bundle/labview/page/labview-style-checklist.html LabVIEW Style Checklist]
	*[http://www.ni.com/white-paper/5560/en/ Rules to Wire By Part 1]		*[http://www.ni.com/white-paper/5560/en/ Rules to Wire By Part 1]
	*[http://www.ni.com/white-paper/4822/en/ Rules to Wire By Part 2]		*[http://www.ni.com/white-paper/4822/en/ Rules to Wire By Part 2]

			Additionally, there are checklists and style guides that contain more detail when ensuring consistency of style in LabVIEW program code.

			*[https://www.ni.com/docs/en-US/bundle/labview/page/labview-style-checklist.html LabVIEW Style Checklist]
			*[https://wiki.dqmh.org/dqmh/styleguide DQMH Queued Message Handler Style Guide]

	These guidelines in programming style are important and can be check through automated inspection using the [[VI_analyzer\|VI Analyzer]] toolkit.		These guidelines in programming style are important and can be check through automated inspection using the [[VI_analyzer\|VI Analyzer]] toolkit.

	[[Category:LabVIEW fundamentals]]		[[Category:LabVIEW fundamentals]]

Austinman at 15:12, 14 June 2024

2024-06-14T15:12:12Z

← Older revision		Revision as of 15:12, 14 June 2024
Line 1:		Line 1:
	LabVIEW is a graphical programming language, and as a result emphasis is often put on how the code looks, as well as how it performs. Developers may have preferences on one style or another, but one good starting point is the following NI White Papers on Rules to Wire by:		LabVIEW is a graphical programming language, and as a result emphasis is often put on how the code looks, as well as how it performs. Developers may have preferences on one style or another, but one good starting point is the following NI White Papers on Rules to Wire by:

	*[https://www.ni.com/docs/en-US/bundle/labview/page/labview-style-checklist.html]		*[https://www.ni.com/docs/en-US/bundle/labview/page/labview-style-checklist.html LabVIEW Style Checklist]
	*[http://www.ni.com/white-paper/5560/en/ Rules to Wire By Part 1]		*[http://www.ni.com/white-paper/5560/en/ Rules to Wire By Part 1]
	*[http://www.ni.com/white-paper/4822/en/ Rules to Wire By Part 2]		*[http://www.ni.com/white-paper/4822/en/ Rules to Wire By Part 2]

Austinman: Added link to NI LV style checklist.

2024-06-14T15:10:14Z

Added link to NI LV style checklist.

← Older revision		Revision as of 15:10, 14 June 2024
Line 1:		Line 1:
	LabVIEW is a graphical programming language, and as a result emphasis is often put on how the code looks, as well as how it performs. Developers may have preferences on one style or another, but one good starting point is the following NI White Papers on Rules to Wire by:		LabVIEW is a graphical programming language, and as a result emphasis is often put on how the code looks, as well as how it performs. Developers may have preferences on one style or another, but one good starting point is the following NI White Papers on Rules to Wire by:

			*[https://www.ni.com/docs/en-US/bundle/labview/page/labview-style-checklist.html]
	*[http://www.ni.com/white-paper/5560/en/ Rules to Wire By Part 1]		*[http://www.ni.com/white-paper/5560/en/ Rules to Wire By Part 1]
	*[http://www.ni.com/white-paper/4822/en/ Rules to Wire By Part 2]		*[http://www.ni.com/white-paper/4822/en/ Rules to Wire By Part 2]

Q: Category reorg

2020-06-17T21:14:01Z

Category reorg

← Older revision		Revision as of 21:14, 17 June 2020
Line 5:		Line 5:

	These guidelines in programming style are important and can be check through automated inspection using the [[VI_analyzer\|VI Analyzer]] toolkit.		These guidelines in programming style are important and can be check through automated inspection using the [[VI_analyzer\|VI Analyzer]] toolkit.

			[[Category:LabVIEW fundamentals]]

Hooovahh at 15:45, 15 November 2018

2018-11-15T15:45:54Z

← Older revision		Revision as of 15:45, 15 November 2018
Line 4:		Line 4:
	*[http://www.ni.com/white-paper/4822/en/ Rules to Wire By Part 2]		*[http://www.ni.com/white-paper/4822/en/ Rules to Wire By Part 2]

	These guidelines in programming style are important and can be check through automated inspection using the [[VI_analyzer VI Analyzer]] toolkit.		These guidelines in programming style are important and can be check through automated inspection using the [[VI_analyzer\|VI Analyzer]] toolkit.

Hooovahh: Created page with links to Rules to Wire by and VI Analyzer

2018-11-15T15:45:16Z

Created page with links to Rules to Wire by and VI Analyzer

New page

LabVIEW is a graphical programming language, and as a result emphasis is often put on how the code looks, as well as how it performs. Developers may have preferences on one style or another, but one good starting point is the following NI White Papers on Rules to Wire by:

*[http://www.ni.com/white-paper/5560/en/ Rules to Wire By Part 1]
*[http://www.ni.com/white-paper/4822/en/ Rules to Wire By Part 2]

These guidelines in programming style are important and can be check through automated inspection using the [[VI_analyzer VI Analyzer]] toolkit.