Drawing Graphics using PowerShell 1.0 and GDI+ - Revision history

Neil: Text replacement - "" to "
"
2016-10-27T19:55:26Z
Text replacement - "<table border="0" cellspacing="0">" to "<table border="0" cellspacing="0" width="100%">"

← Older revision Revision as of 19:55, 27 October 2016
Line 1: Line 1:

−
<table border="0" cellspacing="0">
+
<table border="0" cellspacing="0" width="100%">

<tr>

<tr>

<td width="20%">[[Creating GUIs in Windows PowerShell 1.0 with WinForms|Previous]]<td align="center">[[Windows PowerShell 1.0 Essentials|Table of Contents]]<td width="20%" align="right">[[Using COM with Windows PowerShell|Next]]</td>

<td width="20%">[[Creating GUIs in Windows PowerShell 1.0 with WinForms|Previous]]<td align="center">[[Windows PowerShell 1.0 Essentials|Table of Contents]]<td width="20%" align="right">[[Using COM with Windows PowerShell|Next]]</td>

Neil: Text replacement - "" to "
"
2016-05-05T14:37:49Z
Text replacement - "<table border="0" cellspacing="0" width="100%">" to "<table border="0" cellspacing="0">"

← Older revision Revision as of 14:37, 5 May 2016
Line 1: Line 1:

−
<table border="0" cellspacing="0" width="100%">
+
<table border="0" cellspacing="0">

<tr>

<tr>

<td width="20%">[[Creating GUIs in Windows PowerShell 1.0 with WinForms|Previous]]<td align="center">[[Windows PowerShell 1.0 Essentials|Table of Contents]]<td width="20%" align="right">[[Using COM with Windows PowerShell|Next]]</td>

<td width="20%">[[Creating GUIs in Windows PowerShell 1.0 with WinForms|Previous]]<td align="center">[[Windows PowerShell 1.0 Essentials|Table of Contents]]<td width="20%" align="right">[[Using COM with Windows PowerShell|Next]]</td>

Neil: Text replacement - "BUY_WPS" to "powershell"

2016-02-01T21:12:12Z

Text replacement - "<google>BUY_WPS</google>" to "<htmlet>powershell</htmlet>"

Neil: Text replacement - "ADSDAQBOX_FLOW" to "adsdaqbox_flow"

2016-02-01T18:04:53Z

Text replacement - "<google>ADSDAQBOX_FLOW</google>" to "<htmlet>adsdaqbox_flow</htmlet>"

Neil at 17:39, 15 May 2009

2009-05-15T17:39:10Z

Neil at 14:19, 14 May 2009

2009-05-14T14:19:08Z

Neil: /* An Overview of GDI+ */

2009-03-18T18:54:03Z

‎An Overview of GDI+

Neil: /* Creating the WinForms Form and Graphics Object */

2008-12-18T20:10:06Z

‎Creating the WinForms Form and Graphics Object

Neil: /* Creating the WinForms Form */

2008-12-18T20:09:45Z

‎Creating the WinForms Form

← Older revision		Revision as of 21:12, 1 February 2016
Line 8:		Line 8:


−	<~~google~~>~~BUY_WPS~~</~~google~~>	+	<htmlet>powershell</htmlet>

@@ Line 14: / Line 14: @@
 == An Overview of GDI+ ==
-<google>ADSDAQBOX_FLOW</google>
+<htmlet>adsdaqbox_flow</htmlet>
 GDI+ is part of the .NET framwork and is the standard Windows API for working with display hardware to draw graphics on Windows XP, Windows Server 2003 and later Microsoft operating systems. The ''GDI'' in ''GDI+'' is an abbreviation for ''Graphics Display Interface''. In terms of using GDI+ within Windows PowerShell it is used in conjunction with WinForms, whereby WinForms provides dialogs, controls and the Form canvas on which the drawing takes place. For more information in WinForms in the context of Windows PowerShell, refer to the chapter entitled [[Creating GUIs in Windows PowerShell 1.0 with WinForms]].

@@ Line 19: / Line 19: @@
 == Loading the GDI+ and WinForms .NET Assemblies ==
-As previously mention, Windows PowerShell GDI+ development is typically performed in conjunction with WinForms. Neither the GDI+, nor the WinForms .NET assemblies are loaded into the Windows PowerShell environment by default. It is necessary, therefore, to load these assemblies before beginning the development process. GDI+ and Winforms reside in the [Windows.Drawing] and [Windows.Windows.Forms] assemblies respectively. These can be loaded using the following commands:
+As previously mentioned, Windows PowerShell GDI+ development is typically performed in conjunction with WinForms. Neither the GDI+, nor the WinForms .NET assemblies are loaded into the Windows PowerShell environment by default. It is necessary, therefore, to load these assemblies before beginning the development process. GDI+ and Winforms reside in the [Windows.Drawing] and [Windows.Windows.Forms] assemblies respectively. These can be loaded using the following commands:
 <pre>
@@ Line 101: / Line 101: @@
 Applications with graphical user interfaces are primarily ''event driven''. This means that event handlers must be written to define what actions are to be performed when certain activities occur with regard to the user interface. When a user clicks a button, for example, an event handler performs the necessary tasks associated with that button being pressed (if the button was a Close button, the event handler would be responsible for exiting the application).
-In terms of graphics drawing, when a form is displayed a ''paint'' event is triggered. Similarly, when a form needs to be repainted (for example because all or part of the form was obscured and then uncovered by another window), the paint event is also triggered. it is, therefore, the job of the ''paint handler'' to perform the graphics drawing tasks. A paint event handler is declared in Windows PowerShell via a call to ''add_paint()'':
+In terms of graphics drawing, when a form is displayed a ''paint'' event is triggered. Similarly, when a form needs to be repainted (for example because all or part of the form was obscured and then uncovered by another window), the paint event is also triggered. It is, therefore, the job of the ''paint handler'' to perform the graphics drawing tasks. A paint event handler is declared in Windows PowerShell via a call to ''add_paint()'':
 <pre>
@@ Line 206: / Line 206: @@
 [[Image:windows_powershell_gdi_example.jpg|A Windows PowerShell/GDI+ Example]]

@@ Line 2: / Line 2: @@
 == An Overview of GDI+ ==
+<google>ADSDAQBOX_FLOW</google>
 GDI+ is part of the .NET framwork and is the standard Windows API for working with display hardware to draw graphics on Windows XP, Windows Server 2003 and later Microsoft operating systems. The ''GDI'' in ''GDI+'' is an abbreviation for ''Graphics Display Interface''. In terms of using GDI+ within Windows PowerShell it is used in conjunction with WinForms, whereby WinForms provides dialogs, controls and the Form canvas on which the drawing takes place. For more information in WinForms in the context of Windows PowerShell, refer to the chapter entitled [[Creating GUIs in Windows PowerShell 1.0 with WinForms]].

@@ Line 71: / Line 71: @@
 </pre>
-== Creating the WinForms Form and Graphics Object ==
+== Creating the WinForms Form and the Graphics Object ==
 Having defined the GDI+ drawing objects, the next step is to create a canvas on which to draw. For the purposes of this example, a Winforms ''Form'' will act as the drawing canvas. To create this form it is necessary to make use of the WinForms API:

@@ Line 1: / Line 1: @@
-<table border="0" cellspacing="0">
+<table border="0" cellspacing="0" width="100%">
 <tr>
 <td width="20%">[[Creating GUIs in Windows PowerShell 1.0 with WinForms|Previous]]<td align="center">[[Windows PowerShell 1.0 Essentials|Table of Contents]]<td width="20%" align="right">[[Using COM with Windows PowerShell|Next]]</td>

← Older revision		Revision as of 14:19, 14 May 2009
Line 1:		Line 1:
		+	<table border="0" cellspacing="0" width="100%">
		+	<tr>
		+	<td width="20%">[[Creating GUIs in Windows PowerShell 1.0 with WinForms\|Previous]]<td align="center">[[Windows PowerShell 1.0 Essentials\|Table of Contents]]<td width="20%" align="right">[[Using COM with Windows PowerShell\|Next]]</td>
		+	<tr>
		+	<td width="20%">Creating GUIs in Windows PowerShell 1.0 with WinForms<td align="center"><td width="20%" align="right">Using COM with Windows PowerShell</td>
		+	</table>
		+	<hr>
		+
		+
		+	<google>BUY_WPS</google>
		+
		+
	Windows PowerShell leverages the GDI+ library to provide graphics drawing capabilities. In fact, PowerShell provides the same level of drawing capabilities through GDI+ as those available in other programming languages such as C# and Visual Basic. In fact, those familiar with GDI+ in the context of other programming languages will find the learning curve to be extremely shallow. Those with no previous experience of GDI+ graphics drawing will quickly find that it is both intuitive and easy to learn.		Windows PowerShell leverages the GDI+ library to provide graphics drawing capabilities. In fact, PowerShell provides the same level of drawing capabilities through GDI+ as those available in other programming languages such as C# and Visual Basic. In fact, those familiar with GDI+ in the context of other programming languages will find the learning curve to be extremely shallow. Those with no previous experience of GDI+ graphics drawing will quickly find that it is both intuitive and easy to learn.