Sports demo, multiple windows opened. With QuariX you can design your interface anyway you want it, it supports: multiple document interfaces (as shown in the image above), as single document interface, or integrated as part of your web page content.

Login page from the sports demo. With support for SaaS (software as a service) or ASP (application software providers) as one of the base requirement for QuariX you can have multiple applications running in the same namespace each fully customizable and independent.

Simple QuariX maintenance window. Beyond the widget implementations and supporting functions QuariX implements a business layer through specialized business components allowing increasing development speed without sacrificing the quality or functionality of the project. On the top of the window an update followed by a navigation tool group wired to the data object holding the data, data that is being displayed by a data browser followed by the desired fields, fields coordinated by a data view component.

Simple QuariX maintenance window. Same window as the previous one this time in view mode. Smart components means that their state is aware of the state of the related components automatically. The navigation tool group is aware of the current position of the selected row in the data object as is the update tool group and data view driving the fields to the state of the data object (view/update).

More complex QuariX maintenance window. Developing complex windows does not increase the complexity of you code, smart business components can completely take care of the details all you have to do is link them together. Default functionalities and automations can be easily customized, if desired, trough properties and triggers which allows full control over the component behavior.

Extensive keyboard support. Using only the keyboard is essential in a business application, special care was taken that keyboard hotkeys can be attached to any component and that the framework is smart enough to be able to handle contexts allowing an improved user experience (INS will mean insert in each and any data browse). At any point in your application pressing ALT+` will show you what hotkeys are active in the current context you are.

Internationalization, Dutch language, NL localization settings for the current user. Support for internationalization is built into every brick of the QuariX framework, starting with UTF character encoding to be able to handle any language desired, message bundles for every component to allow any interaction with the end user be properly localized and smart components to handle date formats and input masks that can work with the data depending on the user localization.

Sports demo, default theme. Because look and branding are important any component can be customized through standard CSS to look anyway you want it, both globally as in particular down to a specific window or component.

Sports demo, brushed theme. Because look and branding are important any component can be customized through standard CSS to look anyway you want it, both globally as in particular down to a specific window or component.

Sports demo, date field with automatic calendar widget attached. Smart components are smart because you have to work less to provide more. Make a field of type date and it will automatically get a calendar date selector.

Sports demo, input field with modal foreign key browser. Smart components are smart because you have to work less to provide more. Attach a foreign key window to any field and it will be seamlessly integrated with the field, the window can be customized to suit your needs completely and can be reused.

Web Nethrom Office, holiday request window with integrated filter view. On top of the standard widgets there is an extensive array of client side business logic components that makes development proficient. To be noted the integrated filtering of the data object through a filter view (inside the window in this particular case) which automatically handles filter coordination between the data object and the server side data provider. Also the a weekday trigger that automatically calculates the week day depending on the value attached in the input field and displays it in the associated lookup field.

Sports demo, the reports selection and filtering window and the resulting PDF "Sales per region report". As can be seen in the above picture the resulted PDF is generated complete with bookmarks for the main regions, a pie chart and details on the sales and report filters.

Sports demo, the "Sells by item" report as inline HTML complete with chart and sales details

Sports demo, the "Sells by region" report as downloadable PDF file, complete with chart and sales details and bookmarks for the sales regions

The powerful BIRT Report designer showing the "Sales by region" report in design mode.