forked from tryphotino/photino.Documentation
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
1 parent
89c5bd1
commit 4486b60
Showing
18 changed files
with
183 additions
and
32 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,141 @@ | ||
| # What's New in V2 | ||
|
|
||
| ## What’s New | ||
| * Improved .NET Intelli-sense documentation | ||
| * Improved organization of the source code | ||
| * Improved ability to add new startup parameters and features in the future | ||
| * Improved development experience for configuration for Photino.NET users | ||
| * Multi-window support | ||
| * Programmatically close native windows | ||
| * Most properties can be set before and/or after native window initialization | ||
| * Extended fluent methods for initialization and ability to call them after initialization as well | ||
| * Handlers can now be established prior to initializing the native window | ||
| * Native browser control’s context menu and developer tools access can now be set in code | ||
| * New setting to automatically enable permissions for browser control access to local hardware such as camera and microphone without prompting the user | ||
| * New settings to use OS default window position and size for native window | ||
| * Programmatically set the native browser control’s Zoom level | ||
| * Minimize and maximize native windows programmatically | ||
| * Center native windows before and/or after initialization | ||
| * Chrome-less native windows allows developers to create custom title bars, footers and menus | ||
| * Improved support for Full Screen (Kiosk) mode | ||
| * Improved support for Topmost (Always on Top) native windows | ||
| * Improved logging | ||
| * Ability to retrieve values from native windows as well as set them via expanded set of properties | ||
|
|
||
| ### New Properties | ||
| * Centered (bool) | ||
| * Chromeless (bool) | ||
| * ContextMenuEnabled (bool) | ||
| * DevToolsEnabled (bool) | ||
| * FullScreen (kiosk mode) (bool) | ||
| * GrantBrowserPermissions (bool) | ||
| * IconFile (string) | ||
| * Maximized (bool) | ||
| * Minimized (bool) | ||
| * StartupString (string) | ||
| * StartupUrl (string) | ||
| * TemporaryFilesPath (string) | ||
| * Topmost (bool) | ||
| * UseOSDefaultLocation (bool) | ||
| * UseOSDefaultSize (bool) | ||
| * WebMessageReceivedHandler (EventHandler<string>) | ||
| * WindowClosingHandler (NetClosingDelegate) | ||
| * WindowCreatingHandler (EventHandler) | ||
| * WindowCreatedHandler (EventHandler) | ||
| * WindowLocationChangedHandler (EventHandler<Point>) | ||
| * WindowSizeChangedHandler (EnventHandler<Size>) | ||
| * Zoom (int) | ||
|
|
||
| ### New Methods | ||
| * RegisterWindowCreatingHandler() | ||
| * RegisterWindowCreatedHandler() | ||
| * RegisterWindowClosedHandler() | ||
| * SetChromeless() | ||
| * SetContextMenuEnabled() | ||
| * SetDevToolsEnabled() | ||
| * SetGrantBrowserPermissions() | ||
| * SetHeight() | ||
| * SetLeft() | ||
| * SetSize() | ||
| * SetLocation() | ||
| * SetLogVerbosity() | ||
| * SetTemporaryFilesPath() | ||
| * SetTitle() | ||
| * SetTopMost() | ||
| * SetWidth() | ||
| * SetZoom() | ||
| * SetUseOsDefaultLocation() | ||
| * SetUseOsDefaultSize() | ||
|
|
||
| ### Windows | ||
| * The Edge browser control’s temporary files are created in AppData\Local by default and the location can now be set in code. | ||
| ### Linux | ||
| * n/a | ||
| ### Mac | ||
| * n/a | ||
|
|
||
|
|
||
| ## Bugs Fixed | ||
| * WindowClosing event now works properly | ||
| * Fixed several issues related to custom schemes (xxx://) | ||
|
|
||
| ### Windows | ||
| * Memory leak injecting JavaScript code | ||
| * Now supports multiple windows | ||
| * Fixed pixelated window and taskbar icons | ||
| ### Linux | ||
| * Fixed crash when creating multiple windows | ||
| ### Mac | ||
| * Fixed crash when calling SetIconfile() | ||
| * Fixed crash on closing | ||
|
|
||
| ## Breaking Changes | ||
| In order to solve some technical issues, we had to make a few breaking changes in V2. The biggest change has been how PhotinoWindow is initialized. The constructor now takes a single parameter; an instance of the parent window if one exists. Properties and/or fluent methods are used configure nearly every setting prior to initialization of the native window and browser control. The only property the developer is required to set is either StartUrl or StartString allowing the native browse control to immediately render the UI. This requirement is necessary to enable multiple window support in Windows as well as provide a better experience for developers. The native window and browser control are automatically initialized and displayed when WaitForClose() is called. Nearly all properties and fluent methods can also be called after initialization of the native window and browser control to change settings at runtime, providing a consistent developer experience. | ||
|
|
||
| ### Renamed Properties | ||
| * IsOnTop --> Topmost | ||
|
|
||
| ### Renamed Methods | ||
| * FullScreen() --> SetFullScreen() (or use FullScreen property) | ||
| * Hide() --> Minimize() (or use Minimized property) | ||
| * UserCanResize() --> SetResizable() (or use Resizeable property) | ||
|
|
||
| ### Deprecated Properties | ||
| * Children | ||
| * WasShown | ||
|
|
||
| ### Deprecated Methods | ||
| * AddChild() | ||
| * Dispose() | ||
| * RemoveChild() | ||
| * Show() | ||
|
|
||
| ### Other Changes | ||
| * PhotinoWindow no longer implements IDsposable | ||
| * PhotinoWindowOptions initialization parameter has been removed. Use XXXHandler properties and/or ResgieterXXHandler() fluent methods and/or Events directly instead. Use of RegisterXXHandler() methods is preferred. | ||
|
|
||
|
|
||
| ### Known Issues | ||
| * ShowState() doesn’t pop up in Alert window. | ||
|
|
||
| ### Windows | ||
| * n/a | ||
| ### Linux | ||
| * Access to local hardware from native browser control is not yet supported by the browser control (out of our control) | ||
| * Reading the minimized (iconified) state of a native window doesn’t work in GTK 3 (out of our control) | ||
| * Calling GetSize() and SetSize() in rapid succession does not work properly. E.g. :<br> | ||
| .Height = .Height + 5;<br> | ||
| .Width = .Width + 5;<br> | ||
| ### Mac | ||
| * SendWebMessage() is not working (root cause of custom schemes issue as well?) | ||
| * .NET Application doesn’t exit when all native windows are closed | ||
| * Closing the main window does not close child windows | ||
| * Center property and method make window ‘prominent’ per macOS / Cocoa standards and don’t exactly center the window (not a bug) | ||
| * Access to local hardware from native browser control is not yet supported by the browser control (out of our control) | ||
| * Visual error messages from .Native app not implemented as they are in Windows and Linux | ||
| * UseOsDefaultLocation sets location to 0,0 as macOS has no default window location (not a bug) | ||
| * UseOsDefaultSize is 800x600 as macOS has no default window size (not a bug) | ||
| * ContextMenuEnabled cannot be toggled after initialization as it’s not supported in WKWebKit (out of our control) | ||
| * DevToolsEnabled cannot be toggled after initialization as it’s not supported in WKWebKit (out of our control) | ||
| * GetScreenDpi always return 72 as it’s not supported on macOS (out of our control) | ||
|
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -6,7 +6,7 @@ This document is for .NET developers using Visual Studio 2019 or later who would | |
| ## Overview | ||
| The Visual Studio Extension installs project templates for creating the Photino.NET and Photino.Blazor sample projects. | ||
|
|
||
| Photino project templates create bare-bones sample applications for various Photino project flavors such as .NET (plain html), Angular, React, Vue, and Blazor. Installing the project templates for Visual Studio 2019, the dotnet CLI and/or VS Code is the easiest way to get up and running creating Photino apps for .NET 5. | ||
| Photino project templates create bare-bones sample applications for various Photino project flavors such as .NET (plain HTML), Angular, React, Vue, etc. Installing the project templates for Visual Studio 2019, the dotnet CLI and/or VS Code is the easiest way to get up and running creating Photino apps for .NET 5. | ||
|
|
||
| The Visual Studio solution source code can be found in the [GitHub repository]( https://github.com/tryphotino/PhotinoSamples.VSExtension ) | ||
|
|
||
|
|
@@ -18,10 +18,11 @@ Open the solution in Visual Studio 2019 or later with the **ASP.NET and web deve | |
|
|
||
| 1. Open the Photino.Samples solution [GitHub]( https://github.com/tryphotino/photino.Samples ). | ||
| 2. Update the samples as required and ensure they build and run correctly. | ||
| 3. From the Project menu, select Export Template…. | ||
| 4. Select *Project Template*. | ||
| 5. For each project, enter description as: “Photino.XXX Sample application with XXX UI”. | ||
| 6. Set icon and preview images if you have them. | ||
| 3. Make sure to delete any node_modules folders!!!! | ||
| 4. From the Project menu, select Export Template…. | ||
| 5. Select *Project Template*. | ||
| 6. For each project, enter description as the description listed in the Samples documentation. | ||
| 7. Set icon and preview images if you have them. | ||
|
|
||
| Zip files are written to: | ||
| * C:\Users\xxxx\Documents\Visual Studio 2019\Templates\ProjectTemplates | ||
|
|
@@ -40,6 +41,7 @@ Project templates will now be available on your dev machine and you can copy the | |
|
|
||
| ## Upload VSIX Extension to Visual Studio Gallery | ||
| * A Photino contributor with account information can sign in to https://marketplace.visualstudio.com with [email protected] Microsoft ID | ||
| * Click the “Publish Extensions” link | ||
| * Find the extension. Click “manage” link. Click the “…” menu, choose Edit. Click pencil icon next to step 1, Upload new version of the VSIX (created in the bin folder). | ||
|
|
||
|
|
||
|
|
||
Oops, something went wrong.