NXKit

NXKit forms the basis of an XML processing engine that can be used to implement other XML based models, such as XForms, or theoritically a full web browser user agent.

NXKit is simple to use. Just create a project, ensure extension assemblies are referenced, and load some XML into the Document class.

public static void Main(string[] args)
{
    var nx = Document.Load(@"<root />");
}

The Document instance loads your document into an internal XLinq instance and provides extensions on elements. These extensions can come from various plugin assemblies, such as NXKit.XForms. Extensions implement various interfaces. For example, Input from the NXKit.XForms namespace.

NXKit Document instances fully support serializing and deserializing a running instance through the usage of the Save method. The output of the serialization process is a copy of the current running Document instance with all the included runtime state.

var host = Document.Load(new Uri("nx-example:///form.xml"));
var save = new MemoryStream();
host.Save(save);

NXKit.DOMEvents

Implements W3C DOM Events. Elements can have events dispatched to them using the IEventTarget interface.

http://www.w3.org/TR/2013/WD-DOM-Level-3-Events-20131105/

For instance to synthesize a UI click or activate (defined as emitting a DOMActivate event):

document.Xml
    .Element("my-element")
    .Interface<IEventTarget>()
    .DispatchEvent(UIEvents.DOMActivate);

NXKit.XMLEvents

Implements W3C XML Events. This provides a number of elements and attributes for listening to DOM Events.

http://www.w3.org/TR/xml-events2/

NXKit.XForms

NXKit.XForms is an implementation of XForms in the NXKit processing model.

http://www.w3.org/TR/xforms/ http://www.w3.org/TR/xforms20/

The implementation currently covers most features from XForms 1.1, and some features from XForms 2.0.

<f:form 
    xmlns:xsd="http://www.w3.org/2001/XMLSchema"
    xmlns:f="http://schemas.nxkit.org/2014/xforms-layout"
    xmlns:xf="http://www.w3.org/2002/xforms"
    xmlns:ev="http://www.w3.org/2001/xml-events">
    <xf:model>
        <xf:instance>
            <data xmlns="">
                <value>text</value>
            </data>
        </xf:instance>
    </xf:model>
    <f:section>
        <xf:label>Section 1</xf:label>
        <xf:group>
            <xf:label>Section 1</xf:label>
            <xf:input ref="value">
                <xf:label>Label</xf:label>
            </xf:input>
        </xf:group>
    </f:section>
</f:form>

NXKit.XForms.Layout

NXKit.XForms.Layout contains a basic layout module supporting sections, tables, and a number of text formatting elements. Can serve as a semantic-only approach to building a form without getting involed with HTML.

<table>
    <table-row>
        <table-cell><strong>Header 1</strong></table-cell>
        <table-cell><strong>Header 2</strong></table-cell>
        <table-cell><strong>Header 3</strong></table-cell>
    </table-row>
    <table-row>
        <table-cell>Header 1</table-cell>
        <table-cell>Header 2</table-cell>
        <table-cell>Header 3</table-cell>
    </table-row>
</table>

NXKit.View.Server

Provides a server side object model for assisting in running a NXKit Document on a server that communicates with a remote (client-based) user interface.

For example, the ViewServer class is used by the Web UI library to host a Document instance on the server to which the HTML interface can connect to.

NXKit.View.Js

Core implementation of the NXKit View in JavaScript using Knockout.

Provides a set of client side objects and scripts for implementing a browser based interface for NXKit documents. The NXKit.View.Web.UI library makes use of these during rendering.

NXKit.View.Web.UI

ASP.Net WebForms interface for NXKit. Contains a View control that you can add to the page, which imports all the neccessary client side objects and script. Communication with the server is handled using async postbacks, serializing the running document instance into the ViewState. Just drop the View control on your page, ensure UI extension packages are referenced (such as NXKit.XForms.View.Web.UI) and open a document.

<xforms:View ID="View" runat="server"
    CssClass="FormView"
    OnLoad="View_Load" />


protected void View_Load(object sender, EventArgs args)
{
    if (!IsPostBack)
    {
        View.Open(new Uri(Request.Url, "nx-example:///aship-form.xml"));
    }
}

NXKit.XForms.View.Js

XForms client-side components. Extends NXKit.View.Js for the client-side interface for XForms.

NXKit.Scripting.EcmaScript

Support for ECMAScript using the Jurassic JavaScript implementation.

This means you can insert script elements into your XForms documents which are invoked in response to XForms events:

<xf:trigger>
    <xf:label>Do Thing</xf:label>
    <xf:script type="text/javascript" ev:event="DOMActivate">
        console.log(i = 0);
    </xf:script>
</xf:trigger>