English
  • About BSPK component
  • ATL
  • BWEB
  • Version history
  • FAQ

    • The JSON object editor

    A tree-view JSON editor shipped with the component. It has two uses: editing the project's JSON configuration files, and editing the content of an object field of a record.

    Opening it

    • From the launcher (_BSPK_LAUNCH method): the Open JSON object editor button. The editor then works on files.
    • From an ATL list, on an object column: the editor opens on the object field of the selected record. File commands are hidden, and saving saves the record directly.

    Working on a file

    • The list offers the files of the project's Resources/json folder.
    • These files are encrypted on disk: the editor shows them decrypted and encrypts them again on save. That is why you go through it rather than a text editor.
    • When a file with the same name exists both in the component and in the project, what you see is their merge, the project taking precedence over the component.
    • Save (also Cmd/Ctrl + S), copy the content to the clipboard, paste the clipboard into the editor, or delete the file after confirmation.

    Good to know

    • Saving a file that the component also ships freezes its values in your project. The editor shows the merge, and saving writes that whole merge into your project's file. The component's values are now copied there and win: a later component version that changes one of them will not be taken into account. Modul_menus is such a file; the parameter files (APP_PARAMETERS…) are not concerned.
    • Saving reloads nothing: a parameter changed here only applies at the next startup. See Parameter files.
    • The button that selects a file outside the Resources/json folder does not load its content in this version: use the list.

    These files drive the application's behaviour. Save invalid or incomplete JSON, and the screen that depends on it will stop working. Copy the content before you change it.

    See also