Talk:Style Guide - Revision history

Logmanoriginal: /* Entire block diagram should fit on the monitor */

2025-02-19T17:32:11Z

Entire block diagram should fit on the monitor

← Older revision		Revision as of 17:32, 19 February 2025
Line 10:		Line 10:
	In the age of wide screen monitors and zoom capabilities, we probably need a more up-to-date definition of when a block diagram fits on the monitor. For one, the block diagram should fit on the monitor at 100% zoom level. Based on "Code should look good on a 1536 x 824 monitor", using [[Arrange VI Window]], in my opinion the same restrictions should apply to block diagrams. --[[User:Logmanoriginal\|Logmanoriginal]] ([[User talk:Logmanoriginal\|talk]]) 12:46, 25 January 2025 (UTC)<br>		In the age of wide screen monitors and zoom capabilities, we probably need a more up-to-date definition of when a block diagram fits on the monitor. For one, the block diagram should fit on the monitor at 100% zoom level. Based on "Code should look good on a 1536 x 824 monitor", using [[Arrange VI Window]], in my opinion the same restrictions should apply to block diagrams. --[[User:Logmanoriginal\|Logmanoriginal]] ([[User talk:Logmanoriginal\|talk]]) 12:46, 25 January 2025 (UTC)<br>
	:I think a good size ahould be whatever fits on a 1920x1080 monitor. --[[User:MichaelAivaliotis\|MichaelAivaliotis]] ([[User talk:MichaelAivaliotis\|talk]]) 02:14, 15 February 2025 (UTC)		:I think a good size ahould be whatever fits on a 1920x1080 monitor. --[[User:MichaelAivaliotis\|MichaelAivaliotis]] ([[User talk:MichaelAivaliotis\|talk]]) 02:14, 15 February 2025 (UTC)
			::1536 x 824 is the resolution you get for a 1920 x 1080 monitor with 125% scaling (minus 40px for the taskbar on Windows 10). This is the default setting for most laptop screens in the range of 14" to 17". To make it simpler, the recommendation should probably be for a maximized window on a 1920 x 1080 monitor at 100% scaling and 100% zoom level: ''"Code should look good on a 1920 x 1080 monitor with 100% scaling at a zoom level of 100%"'' Does that sound about right? --[[User:Logmanoriginal\|Logmanoriginal]] ([[User talk:Logmanoriginal\|talk]]) 17:32, 19 February 2025 (UTC)

MichaelAivaliotis: /* Entire block diagram should fit on the monitor */

2025-02-15T02:14:42Z

Entire block diagram should fit on the monitor

← Older revision		Revision as of 02:14, 15 February 2025
Line 8:		Line 8:
	== Entire block diagram should fit on the monitor ==		== Entire block diagram should fit on the monitor ==

	In the age of wide screen monitors and zoom capabilities, we probably need a more up-to-date definition of when a block diagram fits on the monitor. For one, the block diagram should fit on the monitor at 100% zoom level. Based on "Code should look good on a 1536 x 824 monitor", using [[Arrange VI Window]], in my opinion the same restrictions should apply to block diagrams. --[[User:Logmanoriginal\|Logmanoriginal]] ([[User talk:Logmanoriginal\|talk]]) 12:46, 25 January 2025 (UTC)		In the age of wide screen monitors and zoom capabilities, we probably need a more up-to-date definition of when a block diagram fits on the monitor. For one, the block diagram should fit on the monitor at 100% zoom level. Based on "Code should look good on a 1536 x 824 monitor", using [[Arrange VI Window]], in my opinion the same restrictions should apply to block diagrams. --[[User:Logmanoriginal\|Logmanoriginal]] ([[User talk:Logmanoriginal\|talk]]) 12:46, 25 January 2025 (UTC)<br>
			:I think a good size ahould be whatever fits on a 1920x1080 monitor. --[[User:MichaelAivaliotis\|MichaelAivaliotis]] ([[User talk:MichaelAivaliotis\|talk]]) 02:14, 15 February 2025 (UTC)

Logmanoriginal: /* Entire block diagram should fit on the monitor */ new section

2025-01-25T12:46:11Z

Entire block diagram should fit on the monitor: new section

← Older revision		Revision as of 12:46, 25 January 2025
Line 5:		Line 5:

	Some of the "good" examples appear to be in conflict with its definition. For example, <code>GenericRealTimeControl.lvproj</code> uses Pascal-case for separation of adjacent words. Were these supposed to be examples of how to rename them, like <code>GenericRealTimeControl.lvproj</code> → <code>Generic Real-Time Control.lvproj</code>? --[[User:Logmanoriginal\|Logmanoriginal]] ([[User talk:Logmanoriginal\|talk]]) 12:25, 25 January 2025 (UTC)		Some of the "good" examples appear to be in conflict with its definition. For example, <code>GenericRealTimeControl.lvproj</code> uses Pascal-case for separation of adjacent words. Were these supposed to be examples of how to rename them, like <code>GenericRealTimeControl.lvproj</code> → <code>Generic Real-Time Control.lvproj</code>? --[[User:Logmanoriginal\|Logmanoriginal]] ([[User talk:Logmanoriginal\|talk]]) 12:25, 25 January 2025 (UTC)

			== Entire block diagram should fit on the monitor ==

			In the age of wide screen monitors and zoom capabilities, we probably need a more up-to-date definition of when a block diagram fits on the monitor. For one, the block diagram should fit on the monitor at 100% zoom level. Based on "Code should look good on a 1536 x 824 monitor", using [[Arrange VI Window]], in my opinion the same restrictions should apply to block diagrams. --[[User:Logmanoriginal\|Logmanoriginal]] ([[User talk:Logmanoriginal\|talk]]) 12:46, 25 January 2025 (UTC)

Logmanoriginal: /* Inconsistent examples for "Do not use camel-case, Pascal-case, or underscore characters for separation of adjacent words" */ new section

2025-01-25T12:25:35Z

Inconsistent examples for "Do not use camel-case, Pascal-case, or underscore characters for separation of adjacent words": new section

← Older revision		Revision as of 12:25, 25 January 2025
Line 1:		Line 1:
	== VI Connector Pane ==		== VI Connector Pane ==
	There seems to be some debate in regard to the "correct" connector pane to use based on recent edits. I think presenting the pros and cons of the 2 popular patterns helps. However, in general, I would prefer that any style guideline recommendations or objections be hashed out in this discussion page. There are exceptions to the rule and they should be pointed out. For example if you are creating utility VIs or converters. Then the connector pane can be adjusted so the VI can be smaller in size, for example. --[[User:MichaelAivaliotis\|MichaelAivaliotis]] ([[User talk:MichaelAivaliotis\|talk]]) 08:53, 15 January 2025 (UTC)		There seems to be some debate in regard to the "correct" connector pane to use based on recent edits. I think presenting the pros and cons of the 2 popular patterns helps. However, in general, I would prefer that any style guideline recommendations or objections be hashed out in this discussion page. There are exceptions to the rule and they should be pointed out. For example if you are creating utility VIs or converters. Then the connector pane can be adjusted so the VI can be smaller in size, for example. --[[User:MichaelAivaliotis\|MichaelAivaliotis]] ([[User talk:MichaelAivaliotis\|talk]]) 08:53, 15 January 2025 (UTC)

			== Inconsistent examples for "Do not use camel-case, Pascal-case, or underscore characters for separation of adjacent words" ==

			Some of the "good" examples appear to be in conflict with its definition. For example, <code>GenericRealTimeControl.lvproj</code> uses Pascal-case for separation of adjacent words. Were these supposed to be examples of how to rename them, like <code>GenericRealTimeControl.lvproj</code> → <code>Generic Real-Time Control.lvproj</code>? --[[User:Logmanoriginal\|Logmanoriginal]] ([[User talk:Logmanoriginal\|talk]]) 12:25, 25 January 2025 (UTC)

MichaelAivaliotis at 08:57, 15 January 2025

2025-01-15T08:57:08Z

← Older revision		Revision as of 08:57, 15 January 2025
Line 1:		Line 1:
	== VI Connector Pane ==		== VI Connector Pane ==
	There seems to be some debate in regard to the "correct" connector pane to use based on recent edits. I think presenting the pros and cons of the 2 popular patterns helps. However, in general, I would prefer that any style guideline recommendations or objections be hashed out in this discussion page. --[[User:MichaelAivaliotis\|MichaelAivaliotis]] ([[User talk:MichaelAivaliotis\|talk]]) 08:53, 15 January 2025 (UTC)		There seems to be some debate in regard to the "correct" connector pane to use based on recent edits. I think presenting the pros and cons of the 2 popular patterns helps. However, in general, I would prefer that any style guideline recommendations or objections be hashed out in this discussion page. There are exceptions to the rule and they should be pointed out. For example if you are creating utility VIs or converters. Then the connector pane can be adjusted so the VI can be smaller in size, for example. --[[User:MichaelAivaliotis\|MichaelAivaliotis]] ([[User talk:MichaelAivaliotis\|talk]]) 08:53, 15 January 2025 (UTC)

MichaelAivaliotis: Created page with "== VI Connector Pane == There seems to be some debate in regard to the "correct" connector pane to use based on recent edits. I think presenting the pros and cons of the 2 popular patterns helps. However, in general, I would prefer that any style guideline recommendations or objections be hashed out in this discussion page. --~~~~"

2025-01-15T08:53:55Z

Created page with "== VI Connector Pane == There seems to be some debate in regard to the "correct" connector pane to use based on recent edits. I think presenting the pros and cons of the 2 popular patterns helps. However, in general, I would prefer that any style guideline recommendations or objections be hashed out in this discussion page. --~~~~"

New page

== VI Connector Pane ==
There seems to be some debate in regard to the "correct" connector pane to use based on recent edits. I think presenting the pros and cons of the 2 popular patterns helps. However, in general, I would prefer that any style guideline recommendations or objections be hashed out in this discussion page. --[[User:MichaelAivaliotis|MichaelAivaliotis]] ([[User talk:MichaelAivaliotis|talk]]) 08:53, 15 January 2025 (UTC)

← Older revision		Revision as of 17:32, 19 February 2025
Line 10:		Line 10:
	In the age of wide screen monitors and zoom capabilities, we probably need a more up-to-date definition of when a block diagram fits on the monitor. For one, the block diagram should fit on the monitor at 100% zoom level. Based on "Code should look good on a 1536 x 824 monitor", using [[Arrange VI Window]], in my opinion the same restrictions should apply to block diagrams. --[[User:Logmanoriginal\|Logmanoriginal]] ([[User talk:Logmanoriginal\|talk]]) 12:46, 25 January 2025 (UTC)<br>		In the age of wide screen monitors and zoom capabilities, we probably need a more up-to-date definition of when a block diagram fits on the monitor. For one, the block diagram should fit on the monitor at 100% zoom level. Based on "Code should look good on a 1536 x 824 monitor", using [[Arrange VI Window]], in my opinion the same restrictions should apply to block diagrams. --[[User:Logmanoriginal\|Logmanoriginal]] ([[User talk:Logmanoriginal\|talk]]) 12:46, 25 January 2025 (UTC)<br>
	:I think a good size ahould be whatever fits on a 1920x1080 monitor. --[[User:MichaelAivaliotis\|MichaelAivaliotis]] ([[User talk:MichaelAivaliotis\|talk]]) 02:14, 15 February 2025 (UTC)		:I think a good size ahould be whatever fits on a 1920x1080 monitor. --[[User:MichaelAivaliotis\|MichaelAivaliotis]] ([[User talk:MichaelAivaliotis\|talk]]) 02:14, 15 February 2025 (UTC)
			::1536 x 824 is the resolution you get for a 1920 x 1080 monitor with 125% scaling (minus 40px for the taskbar on Windows 10). This is the default setting for most laptop screens in the range of 14" to 17". To make it simpler, the recommendation should probably be for a maximized window on a 1920 x 1080 monitor at 100% scaling and 100% zoom level: ''"Code should look good on a 1920 x 1080 monitor with 100% scaling at a zoom level of 100%"'' Does that sound about right? --[[User:Logmanoriginal\|Logmanoriginal]] ([[User talk:Logmanoriginal\|talk]]) 17:32, 19 February 2025 (UTC)