AppFrame CookBook

Application configuration file

AppFrame is supposed to save the current state of the application in the configuration file Options.xml and restore the previous state at startup.
The storage location of the configuration file is the directory bin\<project name>AppData.
AppFrame, as the structure of the future project, saves the following data as the xml structure (the conditional FEBE project is shown ):

<febe_options version="23.08.2019">
<be_options />
<fe_options lastfolder="...\Bin" use-menu="no">
    <group id="fe_AppWindow">
      <language current="eng" last="eng" use-dictionary="yes">
        <support flag="us" id="eng" title="English" />
      </language>
      <ribbon startup="default">
        <loadable script="febeAppData\ribbon_Basic.xml" />
        <embedded />
        <default>
        </default>
        <sourcelayout     changetime="132240248208494519">[]</sourcelayout>
       <lastlayout>[]</lastlayout>
      </ribbon>
    </group>
</fe_options>
</febe_options>

Attribute version specifies the version which corresponds to the configuration file content.
The be_Options node by the AppFrame core is not used. Should, if necessary, be used by the author of a specific project.

The xml-node fe_Options stores the only data:

    lasfolder stores the last directory visited by the User,
    use-menu - defines whether the menu, which corresponds to the content of the ribbon should be created (values "yes" and "no"),
    the group node with the identifier fe_AppWindow contains information
        about the dictionary (language node)
  about the ribbon (ribbon node):
            about how to create a ribbon at startup ( default , embedded , loadable )
            about the configuration of the ribbon at application startup ( sourcelayout node ) and the moment of the last change in the state of the panel
    about the configuration of the ribbon at the end of the application ( lastlayout node )

AppFrame does not contain a tool for runtime-editing the configuration file and essential start parameters must be manually edited with any text editor.

If the configuration file is missing, it is created at application startup, and the default panel mode is used .
Control panel extensions are automatically reflected in the configuration file. They can also be specified manually.