edit-cfg-json-tk

There are 3 related packages for editing a config-as-json configuration:

• edit-cfg-json-tk a desktop editor based on Tkinter. It is a thin backend on top of the core.

• edit-cfg-json-textual a terminal editor based on Textual. It is a thin backend on top of the core.

• edit-cfg-json the user interface agnostic core. It discovers the editable structure of a config_as_json.Config object by introspection, and owns all editing, validation and file handling. It is also the package a third party writes a new user interface backend against. The only backend it ships itself is a very limited non-interactive one that prints the model once and returns, for a script, a test or a continuous integration job.

The application supplies its own Config object and gets a folding editor for it, without writing any user interface code and without describing its configuration schema a second time.

The three packages share a version number and are released together. The first two are the editors: pick the one that matches how your application is used, and it pulls in the core itself.

Project status

Alpha. No API stability and no backward compatibility is offered while this package is in Alpha. That applies to the core and to both backends. Public names may change without a major version bump.

Semantic versioning starts when the Alpha period ends. Until then, pin an exact version if your build needs to be reproducible.

Stable exception: Descriptions

A library or a program that only does

from edit_cfg_json import Descriptions

and then uses the Descriptions type definition can safely use the latest version of edit_cfg_json in its declared dependencies with install_requires = [ 'edit_cfg_json >=... That type definition will be kept stable (or at least backward compatible).

What this package does

edit-cfg-json-tk is the Tkinter desktop editor. It is a thin backend on top of edit-cfg-json, which it installs as a dependency. All the editing, validation and file handling logic lives in the core; this package only draws it and forwards the user's actions.

Tkinter itself is not installable from PyPI. It comes with most Python distributions, but on some Linux distributions it is a separate system package, such as python3-tk.

Main entry points

Everything a user of this package needs is re-exported from the top-level edit_cfg_json_tk package:

from edit_cfg_json_tk import TkEditor, TkEditorPanel, edit

edit is the short way in for an application that has already chosen Tkinter. It is edit_cfg_json.edit with this package's backend filled in, and it gives back the configuration object that was saved, or None when nothing was:

from edit_cfg_json_tk import edit

saved = edit(config=config, in_file='my_config.json')

Every keyword of edit_cfg_json.edit except the backend is taken here too: descriptions says what the members are for, settings says what the application has already decided about keys and files, and loader is for a class this library cannot construct on its own.

TkEditorPanel is the same editor for an application that already runs Tk. edit and TkEditor cannot serve one of those: each of them creates a tkinter.Tk, a second one in a process is a second Tcl interpreter, and no widget, variable, font or image crosses between two of them. So this is a separate entry point, it reads the configuration itself in exactly the way edit does, and it does not block:

from edit_cfg_json_tk import TkEditorPanel

# a window of its own, over the application's, holding the application
panel = TkEditorPanel(config, parent=self.window, in_file='my_config.json',
                      on_close=self.editor_gone)

# or filling a frame of a window the application also uses for other things
panel = TkEditorPanel(config, area=self.frame, modal=False,
                      in_file='my_config.json', on_close=self.editor_gone)

parent or area, and never both, is the one decision this entry point asks of the application. parent is a widget the editor opens a window over: it creates that tkinter.Toplevel itself, names it after the configuration class, makes it transient and destroys it again when the session ends. area is a widget the editor fills instead, building one frame inside it and touching nothing else. modal says whether the editor holds the application for the session, and is True by default.

What the application learns is on_close, which says that the session has ended, and panel.saved_config, which says what came of it — an editor that returns at once has no moment at which it could return anything. panel.close(ask_about_unsaved=True) is how the application closes the editor itself, from a button or a menu of its own.

TkEditor is the Tkinter implementation of the EditorBackend protocol of edit-cfg-json, for an application that builds the model itself. Every public name of this package, that one included, is described in the api document.

The edit-cfg-json-tk program

Installing this package also installs a program of the same name, so an application author gets a Tk editor for their own configuration class without writing a line of code. The window it opens is the one this page describes, on the class that was named. It is edit_cfg_json.run_cli with this package's backend filled in, so the command line below is the same one that edit-cfg-json-textual has; what differs is which of the two shows the configuration.

Telling it which class to edit

The class is told and never guessed. Exactly one of these says where it comes from, and --version is the one of them that edits nothing:

Option	Meaning
--module MODULE	Importable module that holds the class. This is the ordinary import path, so PYTHONPATH reaches a package that is not installed.
--file PATH	Python file that is not importable as a module. Its own folder goes to the front of the path, so a file that imports its neighbours works; a file that belongs to a package and uses a relative import is refused, with a message saying to use --module instead.
--edit-settings	The class is this editor's own settings, so a settings file is edited in this editor like any other configuration.
--version	Report the version of this program and of every package it is built on, and which of them PyPI has a newer release of.

edit-cfg-json-tk --module myapp.config --class AppConfig -i /etc/myapp.json
edit-cfg-json-tk --file ./somewhere/cfg.py --class AppConfig
edit-cfg-json-tk --edit-settings -o ~/.edit-cfg-json-tk.cfg
edit-cfg-json-tk --version

Importing a module runs it. That is the same exposure as running the file with python, and it is not guarded against, because a configuration class is Python and reaching it means importing the module it is in.

The rest of the command line

Option	Meaning
--class CLASS	Name of the config_as_json.Config class in that module or file.
--loader NAME	Name of an edit_cfg_json.ConfigLoader there, for a class this editor cannot construct on its own. At least one of --class and --loader is needed and both are allowed: a loader that chooses its class by looking at the file is held to the one --class names.
--descriptions NAME	Name of an edit_cfg_json.Descriptions mapping there, saying what the members are for. Without it the members are shown with whatever their own types say about them.
-i, --input	Configuration file to read. Without it the editor starts from the values the class declares.
-o, --output	Configuration file to write. Without it the input file is written, which is what an editor is normally asked to do.
--policy	What to do about a declared value the file does not hold: strict-then-defaults, which is the default, strict or defaults.
-c, --cfg	Settings file that this run itself behaves according to, instead of the one the program would look for.

A member has no docstring at runtime, so what a member is for is either in a mapping like the one --descriptions names or nowhere at all. The docstring of the configuration class needs no option, because the class carries it.

Whatever a loader needs beyond the four keyword arguments of ConfigLoader is bound where the loader is written, for instance with functools.partial, because a command line cannot supply an argument this library knows nothing about. edit_cfg_json.derived_loader is one line for the ordinary case:

make_config = derived_loader(partial(AppConfig, known_teams=TEAMS))

The settings this program itself runs with

The command line says what to edit and which files, and never how the editor behaves. The extension a configuration uses, the key combinations of the actions and what becomes of a file that a save writes over are settings, and edit_cfg_json.SettingsConfig is what lets them be written in a file. This program uses the first of five that answers: the file -c names, the file $CFG_EDIT_CFG_JSON names, ~/.edit-cfg-json-tk.cfg, ~/.edit-cfg-json.cfg, or the values the editor would have chosen anyway. A file that was named must be there; the two in the home folder are the lookup itself, so a step that finds nothing is simply the next step.

Such a file need name only what it changes, and -c is what makes it per run rather than only per user — an extension is a fact about the class being edited, so an application whose files are called .cfg gets one of its own:

{"actions": {"save": ["ctrl+w"]},
 "file_extension": ".cfg", "extension_enforced": true,
 "backup_suffix": ".old", "backup_count": 3}

--edit-settings is how one is edited in this editor itself: with -i it reads the file that is there, and with no -i it starts from the values the class declares, which is how a file that does not exist yet is made.

How the run ends, and two smaller things

Each way of refusing has an exit code of its own, so this program is usable from a script and from a continuous integration job: 0 when everything it was asked to do was done, 2 for a command line that is wrong, and a number of its own for each way a module, a file, a class, a loader or a settings file can refuse to be read. They are edit_cfg_json.ExitCode, where each is named. Closing an editor is not a failure, so a session the user closed ends with 0 whatever is left in the fields.

The program is also reachable through the package it belongs to, for a machine whose script folder is not on PATH, and it completes its own options and file names with argcomplete:

python3 -m edit_cfg_json_tk --module myapp.config --class AppConfig
eval "$(register-python-argcomplete edit-cfg-json-tk)"

What the window shows

The window holds the label of the configuration, what the class says about itself, what reading the input file did, and then one row per node of the configuration. Below those, in a part of the window that does not scroll, are the validation verdict, the saving line, and the buttons: Validate, Save, Save as..., a tick-box for Explain, a button that folds or opens every container, and Close. Every one of them has a key as well:

Key	What it does
ctrl+r, or f5	Validate
ctrl+s	Save
ctrl+shift+s or f12	Save as
f1, or ctrl+g	Explain
f2, or ctrl+t	Fold all, or unfold all
ctrl+q	Close

Those are the defaults of edit_cfg_json.ActionSettings, and an application that needs one of these combinations for itself moves it, or empties it, in the actions of its own edit_cfg_json.Settings. Every action has a button as well, so an action with no key at all stays reachable. The bindings are made on a bind tag of the editor's own, which the widget the editor was built below and every widget inside it carry, so an editor that owns its window gets the keys of all of it and an embedded one never claims a key of the application.

Every change of a field goes straight into the model, and the label above the rows is marked while the model holds a change worth saving.

A container is a row and not a field. The rows of what it holds are indented below it, there is a field at every value, and the container row says how many things it holds — or which class the object at it is — where a value would be. A control at the left of the row folds it away, Fold all below the rows does the same to all of them at once, and its text says what the next press will do. A configuration with nothing to fold gets neither the button nor the column that the controls sit in, so the values keep that width.

At the end of the line of a node are its element controls: Add, Del, Up and Down, and only the ones that node really offers. Adding an entry to a dict opens a small dialog for the key, because nothing but the person configuring the application knows what a new entry is called. A container that can be given nothing gets no Add at all and says why below itself instead.

Beside the class on the row of a nested object is what that object is on its own: valid on its own, or refused on its own with the member it was about saying why below itself. A list or a dict of such objects says what the objects in it amount to, because its row is the only one that folding leaves on the screen. The qualifying words are the whole point — a rule of the class above may refuse a configuration in which every object is valid on its own — so the verdict line below the rows is the only thing that answers whether the file can be saved.

Validate shows what the application's own configuration class would say about the values that are in the fields, below the node each remark is about. Leaving a field asks the smaller question of whether what was typed into it means a value of that member at all, which is what an enum member name answers only once it is fully typed. Save writes the output file and refuses to write values the application would not accept, leaving the file on disk exactly as it was; it asks first before writing over a file this session has not written, and says where the previous content was kept. Save as asks with the ordinary system dialog, offering the extension the application named in its Settings. Close writes nothing, and asks whether unsaved changes may be dropped, with the answer that keeps them as the one the dialog opens on.

Explain shows or hides what the application says about these values: the class docstring, the docstring of each nested object, the description of each described member below its own field, what kind of value each member holds, and why a container cannot be given an element. The editor opens with them shown, and what is left when they are hidden is the first paragraph of the class docstring. It is a tick-box rather than a button, because a button saying Explain beside explanations that are already there would be offering something that has been done.

A configuration bigger than the window is scrolled through rather than cut off: the rows are on a canvas that scrolls while the verdict, the saving line and the buttons stay where they are, and every paragraph wraps to the width there is. The window opens at the size the configuration asks for, up to the size of a window.

Each kind of text has a colour, so that the explanations do not read as loudly as the values and a refused validation does not read like an accepted one. Which kind each piece of text is comes from edit_cfg_json.Emphasis, so it is the same here as in the Textual backend; the colours are this package's own and are chosen for the light window that Tk gives this editor.

Installing edit-cfg-json-tk

On macOS and Linux

To install edit-cfg-json-tk on macOS and Linux, run the following command:

pip3 install --upgrade edit-cfg-json-tk

On Microsoft Windows

To install edit-cfg-json-tk on Microsoft Windows, run the following command:

pip install --upgrade edit-cfg-json-tk

Documentation

• Design and decisions: doc/design.md

• Public API: edit-cfg-json, edit-cfg-json-tk, edit-cfg-json-textual

• Protected API: edit-cfg-json, edit-cfg-json-tk, edit-cfg-json-textual

• Worked examples: examples/src/example

License

edit-cfg-json-tk is released under the MIT License. See the LICENSE.txt file included in the distribution.

Test summary

• Test result: 1627 passed, 3 deselected in 46s
• No flake8 warnings.
• No mypy errors found.
• No pylint warnings.
• No python layout warnings.
• Built version(s): 0.0.4
• Build and test using Python 3.14.7