The Nsys Platform is trying to achieve several goals and one of them is complete separation of business logic from the presentation layer where applications are accessible on various platforms and devices.
The Nsys Terminal has been designed for visual interpretation of Nsys application on remote device such as mobile phone, smartphone or PC / Mac. The communication is based on client - server approach where XML is used for information exchange between server side (Nsys Platform) and client side (Nsys Terminal). This XML is based on Qube dialect that provides a visual view of various components such as button, text field, media players, etc. This components can be used in application design. Detail information about communication protocol between Nsys Terminal and Nsys Framework are available here.
Figure 1 - Selection of Nsys server to connect
Nsys applications are based on implementation of Nsys Framework object-oriented API helping to do development of applications independent on particular client device and platform. The application code is located and executed on server side and to client device is send a visual interpretation of application defined by a XML document. This helps to develop a single application code when presentation layer of application is transformed into various target platforms such as a web browser, desktop (Windows, Unix/Linux or Mac OS X) or mobile device (phone, smartphone). The framework ensures to do proper transformation of user interface of Nsys application into particular system such as a web browser. In the case of a web browser the user interface is transformed to HTML, for WAP it's to WML etc. On output the Nsys application returns a XML document representing an user interface transformed to particular target platform.
We should understand the concept of user interface as some kind sort of visual application including a set of components such as a button, edit, image and so on. These elements are grouped into single form representing an application.
Figure 2 - Nsys Terminal for MS Windows platform
The user interface is implemented by a simple XML dialect called Qube. Depending on client device the Qube is transformed to HTML, WML or another user-defined XML dialect. This is not necessary in case of communication with Nsys terminal that is processing forms of Nsys application directly in Qube.
Figure 3 - Nsys application viewed in Nsys Terminal
Figure 4 - Nsys Terminal supports to run on client side functions which can be used for validation
Nsys application can be develop in C# for .NET Framework or in Java for any platform supporting JVM. The output of the programming process is an assembly (.NET) or a JAR archive (Java). The Nsys Platform supports its own archive NAR (Nsys Archive) which can be used for deployment of components and/or plugins implemented in .NET or Java. The archive file is a binary file containing application code of one or more Nsys applications runnable on server side and a visual interpretation of the application to view on client device.
Figure 5 - Nsys Terminal settings
The Nsys development team is continuously working on technology development of powerful platform suitable for building information systems in corporate sector. A time ago has started a development of special Linux distribution called Nsys Linux providing Nsys platform for application hosting and accessing applications through built-in Nsys Terminal.
Figure 6 - Nsys Linux - Specialized OS Linux distribution for Nsys