AppFrame CookBook

AppFrame. Application

The list of projects that can be built using the AppFrame template set is presented in the introduction .
A complete set of demo projects built using templates is provided in the SpbExamples\Febe directory .

Essentially, an AppFrame is one big template for developing an application that can have one or a combination of properties:

the user interface is being transformed into a new quality, for example, into an interface based on a Web browser.
user interface based on ribbons
user interface ribbons are presented in the form of scripts (xml view)
functionality is expanded and modified in the field.
distributed existence of FrontEnd and BackEnd (according to the scheme of the classic client-server application)
modifiability of user interface text titles and multilingualism as a special case

The following procedure for using AppFrame seems reasonable.

Depending on the assignment task, a project is created with the user interface type MDI or SDI.
The project is developed according to the ideas of the developer, but subject to agreements on the rules for exchanging data between FrontEnd-BackEnd , including:

If you select the MDI style of the user interface, then project templates with SDI style should be deleted immediately. And vice versa.
If it is not intended to run FrontEnd and BackEnd separately, then templates oriented to separate use can be deleted immediately.
If the extension of the control panel is not intended, then the panel can be represented by its code ( default start mode ), or it can be described as XML and embedded mode is used .
If you are planning to expand the control panel, then xml-representations of panel fragments are created and support for these functions is created in the application code.
If it is supposed to be multilingual, or the ability to change the labels of user interface elements under operating conditions, the necessary dictionaries are created .
Classically debugging the application

When the task of changing the user interface based on the GUI of the Visual Prolog system arises, only FrontEnd is modified.
If you are faced with the problem of switching to using a Web browser as a user interface, you should implement the FrontEnd function on the Web browser platform (JavaScript) in compliance with the agreement on the exchange of information with BackEnd.

If such an application may be of interest in the form of PlugIn in the context of an application built, in turn, on the basis of the AppFrame, then the AppFrame set already provides such an opportunity (using xxx_pzlMonoSDI.pzl or xxx_pzlHttpFroneEnd.pzl).