RFC001 : Consider adding a function to export HTML documents and create a PSHTML object.

[Stephanevg]

Currently each HTML document is exported via the following code on the user's side:

$PSHTMLContent > "Example6.html"

As this works fine, I would like to offer the ability to the end users to use a more 'standard' way of creating such a a document.

I would like to discuss the introduction of an export function, that would allow the following things:

• Have a uniformly way to export HTML documents back to the parser (just returning the HTML content)
• Save the HTML page to a specific location on disk

I would imagine something along these lines:

Out-PSHTMLDocument -Path [String/FileInfo] 

Options

Optionally, I would like to discuss the following:

• Have an overall PSHTML Object that contains the HTML stucture tree
• Have the classes, ID's and attributes

I would imagine a structure along these lines:

PSHTML.Document

Postion	Type	Id	Class	Attributes
[int]	[String]Div,Body, etc..	[String]html id	[String[]] html class	[HashTable] Attributes

Perhaps also think of adding a content on the object, which would contain the content of each HTML tab part. It could potentially, also contain another PSHTML.Document, for nested elements.

Postion	Type	Id	Class	Attributes	Content
[int]	[String]Div,Body, etc..	[String]html id	[String[]] html class	[HashTable] Attributes	[PSHTML.Document] or [String]

Some sources for inspiration for the exports:

• Przemysław's Save-HTMLReport from PSWriteHTML --> https://github.com/Stephanevg/PSWriteHTML/blob/master/Public/Get-HTMLReport.ps1
• Ian's PSScribo's OutHTML.ps1 (from PSSCribo) --> https://github.com/iainbrighton/PScribo/blob/dev/Src/Plugins/Public/OutHtml.ps1
• Any other interesting ones?

[Stephanevg]

As I will shortly introduce a depency on PowerShell 5 (Using classes), we have the possibility to use classes, and potentially implement design patterns. For the PSHTML.Document we could perhaps use the composite pattern ? I think it will handle the problematic of the nested HTML elements pretty well, and we will be able to add functionality to every component centrally.

[Stephanevg]

For reference -> https://docs.microsoft.com/fr-fr/dotnet/api/system.web.ui.htmltextwriter?view=netframework-4.7.2

[Stephanevg]

First version of Out-PSHTMLDocument has been added in this commit -> https://github.com/Stephanevg/PSHTML/commit/0e4382ca490a58c18c104168063a73f602915a27

[Stephanevg]

This was actually two points, exporting the HTML content via a cmdlet, and desining the PSHTML.Document object.

I consider the first point done in the commit above. The second point will be tracked here --> https://github.com/Stephanevg/PSHTML/issues/218