Go to file
Frank A. Krueger edb2296a21
Reconnect web sockets when closed
2020-03-08 20:03:36 -07:00
.vscode Don't show test build status 2017-06-19 00:15:48 -07:00
Documentation Add HD icon 2019-07-17 16:13:53 -07:00
Ooui Reconnect web sockets when closed 2020-03-08 20:03:36 -07:00
Ooui.AspNetCore Bump AspNetCoreMvc to (ASP) .Net Core 2.2 2019-03-23 23:47:35 +01:00
Ooui.Forms Update to Forms 4.5.0.356 2020-03-08 18:01:51 -07:00
Ooui.Wasm Fix build dist paths 2018-03-13 15:58:18 -07:00
Ooui.Wasm.Build.Tasks Backoff linker update 2019-01-05 11:52:47 -08:00
PlatformSamples/AspNetCoreMvc Update to Forms 4.5.0.356 2020-03-08 18:01:51 -07:00
PlatformTests Add Android presentation to a web view 2017-07-07 18:04:09 -07:00
Samples Update to Forms 4.5.0.356 2020-03-08 18:01:51 -07:00
Tests Fix connecting to web sockets with regex urls 2020-03-08 18:45:21 -07:00
.editorconfig Update styling 2017-11-09 12:34:08 -08:00
.gitignore Add Ooui.Wasm package 2018-03-13 14:44:35 -07:00
.gitmodules Use https path for mono submodule 2018-07-20 09:09:33 +02:00
LICENSE Add MIT license 2017-06-13 18:12:27 -07:00
Ooui.sln Remove out of date templates 2020-03-08 18:04:45 -07:00
README.md Simplify Samples execution 2019-01-05 10:35:16 -08:00
ooui.service Update the service to always restart 2017-12-09 15:50:59 -08:00

README.md

Ooui Web Framework Build Status

Version Package Description
NuGet Package Ooui Core library with HTML elements and a server
NuGet Package Ooui.AspNetCore Integration with ASP.NET Core
NuGet Package Ooui.Forms Xamarin.Forms backend using Ooui (Status)
NuGet Package Ooui.Wasm Package your app into a web assembly

Ooui (pronounced weee!) is a small cross-platform UI library for .NET that uses web technologies.

It presents a classic object-oriented UI API that controls a dumb browser. With Ooui, you get the full power of your favorite .NET programming language plus the ability to interact with your app using any device.

Try it Online

Head on over to http://ooui.mecha.parts to tryout the samples.

You can also load https://s3.amazonaws.com/praeclarum.org/wasm/index.html to try the WebAssembly mode of Ooui running Xamarin.Forms. (That's Xamarin.Forms running right in your browser!)

Try the Samples Locally

git clone git@github.com:praeclarum/Ooui.git
cd Ooui

dotnet run --project Samples/Samples.csproj

This will open the default starting page for the Samples. Now point your browser at http://localhost:8080/shared-button

You should see a button that tracks the number of times it was clicked. The source code for that button is shown in the example below.

Example App

Here is the complete source code to a fully collaborative button clicking app.

using System;
using Ooui;

class Program
{
    static void Main(string[] args)
    {
        // Create the UI
        var button = new Button("Click me!");

        // Add some logic to it
        var count = 0;
        button.Click += (s, e) => {
            count++;
            button.Text = $"Clicked {count} times";
        };

        // Publishing makes an object available at a given URL
        // The user should be directed to http://localhost:8080/shared-button
        UI.Publish ("/shared-button", button);

        // Don't exit the app until someone hits return
        Console.ReadLine ();
    }
}

Make sure to add a reference to Ooui before you start running!

dotnet add package Ooui
dotnet run

With just that code, a web server that serves the HTML and web socket logic necessary for an interactive button will start.

The Many Ways to Ooui

Ooui has been broken up into several packages to increase the variety of ways that it can be used. Here are some combinations to help you decide which way is best for you.

OouiOoui.AspNetCoreOoui.FormsOoui.Wasm
Web DOM with the Built-in Web Server
Web DOM with ASP.NET Core
Xamarin.Forms with ASP.NET Core
Xamarin.Forms with the built-in web server
Web DOM with Web Assembly
Xamarin.Forms with Web Assembly

How it works

When the user requests a page, the page will connect to the server using a web socket. This socket is used to keep the server's in-memory model of the UI (the one you work with as a programmer) in sync with the actual UI shown to the user in their browser. This is done using a simple messaging protocol with JSON packets.

When the user clicks or otherwise interacts with the UI, those events are sent back over the web socket so that your code can deal with them.

In the case of web assembly, this same dataflow takes place. However, sockets are not used as all communication is done locally in the browser process.

Contributing

Ooui is open source and I love merging PRs. Please fork away, and please obey the .editorconfig file. :-) Try to file issues for things that you want to work on before you start the work so that there's no duplicated effort. If you just want to help out, check out the issues and dive in!