Saved searches
Use saved searches to filter your results more quickly
You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session. You switched accounts on another tab or window. Reload to refresh your session.
Framework for creating desktop C# applications with HTML user interface.
License
Samotorcan/HtmlUi
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Name already in use
A tag already exists with the provided branch name. Many Git commands accept both tag and branch names, so creating this branch may cause unexpected behavior. Are you sure you want to create this branch?
Sign In Required
Please sign in to use Codespaces.
Launching GitHub Desktop
If nothing happens, download GitHub Desktop and try again.
Launching GitHub Desktop
If nothing happens, download GitHub Desktop and try again.
Launching Xcode
If nothing happens, download Xcode and try again.
Launching Visual Studio Code
Your codespace will open once ready.
There was a problem preparing your codespace, please try again.
Latest commit
Git stats
Files
Failed to load latest commit information.
README.md
HtmlUi is a framework for creating desktop C# applications with HTML user interface.
The framework uses CEF library to render the UI and C# to connect controllers with the UI. For client side on the UI the framework curently only support AngularJS. Every AngularJS controller is linked with the C# controller and so every property changed in the C# controller gets updated to the AngularJS controller and vice versa. Methods on the C# controller are also linked to to the AngularJS side so they can be called from the UI.
CEF binaries can be compiled from the CEF sources or downloaded from the CEF Builds. HtmlUi currently uses CEF version 3.2357.1281. The required files for CEF to run are listed here. The repository also includes the Windows x86 and Linux x64 binaries to run examples without the need to search and download the right CEF.
To use CEF in C# the framework uses a library called CefGlue to P/Invoke calls to CEF. Which CEF version the framework uses is conditional with the CefGlue library. When the CefGlue library gets updated so will the framework be upadated to use the newest CEF version.
The framework was only tested with Visual Studio 2015.
To create a new application first create a new Console Application in Visual Studio. The minimum C# supported version by the framework is 4.5.
To debug the application with CEF Enable the Visual Studio hosting process must be unchecked in the project properties. If this is enabled you will only get a white screen when running the application in debug mode.
Next the output type in project options must be changed to Windows Application so the console window is not started.
The Platform Target must also be set to either x86 or x64 and the correct bit version of CEF must be copied next to the application. Windows x86 and Linux x64 CEF binaries can be found in the repository.
The framework will start multiple processes where the first started process will be the main application process. To correctly run child processes the main method of the application should look like something like this.
static void Main(string[] args) if (HtmlUiRuntime.ApplicationType == ApplicationType.ChildApplication) OSChildApplication.Run(); return; > OSApplication.Run(); >
At this part the HtmlUi must be added in references to correctly find HtmlUi classes.
The framework currently supports only one main window. To add the view for the main window create a folder named Views and add Index.html file. This file will contain the html for the UI part. Next you have to mark the Index.html file as Embedded Resource or Copy always in the file properties.
From here on now you can start the application and you should get an empty white window. To edit the UI simply add all your html in the Index.html and rerun the application. If you selected that Index.html is Copy always you can edit the file and refresh (F5) the window without restarting the application. The Developer Tools can be accessed by pressing F12 or clicking the top left corner of the application and selecting Developer Tools.
To connect a C# controller with the AngularJS controller create an angular module and include the htmlUi module. Next in the AngularJS controller request a service htmlUi.controller and create the C# controller with htmlUiController.createObservableController(‘controllerName’, $scope); . Now the $scope will contain all the properties and methods that are defined in the C# controller.
var app = angular.module('myApp', ['htmlUi']); app.controller('exampleController', ['$scope', 'htmlUi.controller', function ($scope, htmlUiController) htmlUiController.createObservableController('exampleController', $scope); // controller code . > );
To create a C# controller simply create a class that extends either Controller or ObservableController. The controllers that are extended from Controller will only have methods linked to the AngularJS controller and properties will be ignored. Controllers created this way are used where the AngularJS scope is not created like services.
public class ExampleController : Controller public void DoSomething() // this method can be called from JavaScript > >
Controllers that extend ObservableController are used where the AngularJS scope is created like the AngularJS controller. The scope will contain all the methods and the properties that are defined in the C# controller. The properties are also linked and every property changed in scope or C# controller will be sync back. In AngularJS the framework adds watches to all the controller properties to watch for changes and sync them back to C# controller. In C# controller the framework must be notified of property changes by calling the INotifyPropertyChanged.PropertyChanged event or SetField in controller.
public class ExampleController : ObservableController public string SomeProperty get; set; > // only changes from JavaScript to C# are synced private string _someOtherProperty; public string SomeOtherProperty // changes are synced both ways get return _someOtherProperty; > set SetField(ref _someOtherProperty, value); > > >
The create an application for Windows only the CEF binaries must be copied next to the application tu run properly. No additional steps are needed.
The run the application on Linux Mono is required. After Mono is installed on Linux the application must be packed into a bundle with mkbundle. The CEF library must be linked before libc.so . To achieve this you can run the application with LD_PRELOAD like this LD_PRELOAD=LD_PRELOAD=/path/to/libcef.so /path/to/your/app or by modifying the link part in mkbundle process. An example of how to modify the mkbundle process to include the libcef.so before libc.so .
mkbundle -c -o host.c -oo bundles.o yourApp.exe cc -ggdb -o yourApp -Wall host.c -Wl,-rpath=. libcef.so `pkg-config --cflags --libs mono-2` bundles.o rm host.c bundles.o The CEF bit version is dependent on the bit version of Mono. If you have a x86 version of Mono you will need a x86 version of CEF and if you have a x64 version of Mono you will need a x64 version of CEF.
The sources contain one example application TodoList. The application shows how to use the HtmlUi framework to sync todo items from UI to C# and load and save todo items in a JSON file.
To run the example application the required CEF version must be copied next to the example application and for Linux the example application must also be packed with mkbundle.
About
Framework for creating desktop C# applications with HTML user interface.