Login
User Name
Password
Views are the construction parts of pages a solution site is built from. Views are the window into the Holistic Programming system and represent a certain perspective on the knowledge. View are responsible for the technical realization of the communication between user and solution system.
Each page consists of views defined in a page template and those specific to the page. Depending on the access rights the user has the definition of the views can be changed.
Below you can find a list of currently implemented views. As always on this website, displayed data is directly taken from the solutions knowledge base.
Shows multi-language header text. The extended header can show also a selected attributes value of the the object indicated by page parameters. Like this, a context sensitve header text can be shown. Optionally, the header text can be used as page title. This title is shown in the browser's title bar and with most browsers stored along the URL for easy selection in the browsers address bar. Together with the easy readable URL, the browser's navigation capabilities are optimally used.
Rich table template to display object data in a table. For display, columns can be selected and different options are available to make navigation within huge data amounts easy. Depending on the display mode a table is configured, content can be directly edited. If enabled, users can even change the table structure easily - and so the underlying object model. Significant effort has been invested to make this central view as powerful and fast as flexible knowledge management requires. Everything with full multi-language support, of course.
Configurable submit button, allowing to trigger simple page events or even specialized scripts to be executed on server or client (browser) side.
Special view to define scripts to be executed when a page with views based on this template are called. While rarely needed, this view opens the door to "classical" server-side script programming.
A simple view to structrure the page content hierarchically. It's the base of all view templates and provides already the possiblity to special customization of the display - an property inherited by all views. This view (and so all views) represents a DIV tag (division) in the generated HTML code.
The EditForm view is designed to easily create and maintain forms to query data from the user.
Form data can be seen as a view on a specific object instance, so the form view can be used to see and change object attributes, too.
The EditForm provides a wide choice of display variants to create a view on the object data accordingly to the user's perspective.
A typical "design pattern" is to provide a page with a list of object instances using EditTable and define links to a page containing the EditForm view on the same object.
The HTML Text view is provided to view and modify HTML text. It's typically used on text pages.
In EditThisPage-mode, this view provides a full WYSIWYG editor - thanks to the FCKeditor project.
The Special View is designed to allow special server side scripting with non-interactive output to the user.
This view is used when server functionality should be make part of a page and leaves the door open to "classical" server side web application programming.
This view defines a selection menu, based on the menu hierarchy defined at MenuEdit.asp. Creating menus is very flexible and together with different stylesheets it's possible to realize a wide range of menu types.
Since the menu view can be defined on base of the overall menu hierarchy (instead of defining the menu hierarchy by its own) it can be used to create different perspectives on the menu hierarchy at the same time, e.g. realizing a dropdown menu on the same page using a single menu definition. The Holistic Programming site provides an example for this technique.
The Chat View provides an easy to use group chat for registered users. Based on user groups defined by the access right management system, participants can join a chat started by a moderator and can create private (p2p) chats within this session.
A participants list shows who is in the group and who is currently online and actively participating.
The Page Root View is used to define page templates and also page like attributes of all pages. In combiniation with the Body View, the defintion of all pages within a solution is based on Page Root views.
The Set and Check Login View gives the user access to his or her login. It can be used to provide simple login fields (user name and password), login configuration (change password) or even login administration (lock or unlock user accounts).
The password is not stored on the server as it is but instead a hash method is used, so users don't need to fear misuse of their password. Optionally, passwords for login are not transmitted to the server, but will be checked with a challenge-response method.
The body covers the content of pages within page templates. Usually, all pages based on a page template get the "outer" parts of the page (like site menu) from the template, while the content is defined within the body.
The body view is treated special by page templates as it defines the root of the content. Usually, view access rights are given to the body view, while all embedded views inherit these rights from the body.
The Page Loader view allows to dynamically load another page into the main page. The technique can be used to include any content into a given page, even content from other web sites.
Optionally, the loaded content is shown within an IFRAME element (i.e. the loaded content is treated as "foreign") or as dynamically displayed content within the page, inheriting the formatting of it.
The View Container allows to load any view (and its subviews) into the given page. Other than the Page Loader, it does not require complete web pages for displaying them, but any view definition can be used.
Especially, this view is used by page templates to include the body content of pages assigned to this template.
The FlashPlayer view is used to comfortably include Flash content into a page.
The YouTube Player View is used to comfortably include movies stored at YouTube into a page.
The File Editor View offers direct access to files stored on the server.
A special application is to use the file editor for editing low level framework functionality not controlled by the object defnition shell.
The Book View provides a "book" perspective on a sequence of pages. Base of the "book" is a menu root node indicating the associated pages. The header levels are adjusted accordingly, so the pages appeare like being part of a book.
The NewPage Form View is a specialized view to support the copy function of pages best.
The Language Selector View is offers the user the selection of the current text language. It allows to shows the languages enabled for the solution in different modes, i.e. country flags, ISO-2 abbreviations, or dropdown with full language names.
The Object Selector View can be used on pages showing single object content to quickly switch between the instances. This allows comfortable navigation within complex object data.
The Solution Statistics View is a highly specialized view to show key statistics of the solution.
The Chart view has been designed for a project management software to show data in horizontal or vertical bars along a timescale and allow to plan items within this view. It is part of an web solution based on a very early version of Naradana Solutions Framework and is impatiently waiting to be transferred to the actual version.
The WebService Definition View allows the user to define a WebService interface by selecting from the object knowledge base or by creating new object definitions on the fly.
The definied WebService interface then can be used by client systems to accesss the Naradana Solutions Framework system.
Optinally, configuration files will be generated for specialized client systems supporting legacy data transfer protocols like FTP or SMTP. If these client systems are installed together with the generated configuration files, they act as adaptors for bringing data into the NSF system. These can be uploads of image archieves, CSV files, etc.
This view is currently under development.
The Notification View is used to show asynchronous messages like alerts or hints issued by the server to the user. The view is designed to make it very easy for developers to feed users with notifications.
The Search View is used to define the search control, i.e. the input field for the search query and optionally search options.
Executes prepared batch jobs and shows execution progress. Batch execution can be cancelled after each job.
Displays a topic and allows to edit it with a WYSIWYG editor.
Displays a image gallery button that opens a lightbox with a slide show of the specified images including thumbnails for selecting a specific image.