• Allow toolbox to use separate home folder (script exists)
• Make seperate homefolder user configurable (#6 )
• Allow users to create symbolic links between directories of seprate home and actual home directory (moved to seperate issue #33)

Vendoring dependencies and uploading them in releases makes publishing on Flathub easier.

When the application is run in a toolbox podman-host needs to be used to communicated with podman

• BlackBox
• Console (org.gnome.Console)
• Konsole

Inspiration could be taken by: https://gitlab.gnome.org/World/amberol

The goal is to have one toolbx owner thread that manages the toolboxes. This means it:

• Runs commands for toolboxes
• Gives update notifications to UI components
• Recieves commands from UI

This might be more work than it seems and needs some exploration on how to do it best.

A user might want to run an application like gparted inside a toolbox as root.

This was suggested on reddit.

A user might want to mount volumes to access for example the home folder as root.

This was suggested on reddit.

• Allow toolbox creation

• podman
• toolbox
• gnome-terminal (later support other terminal applications)

Expected behaviour is to only allow a single window to be open at a time. This is due to the app expecting only one instance running at a time. Otherwise settings could be overwritten.

• Default Update Settings (nothing/notify/autoupdate)
• Default home folder base location ~/.toolbox/homedir/
• Use separate home by default (yes/no)
• Handle overrides in local toolbox settings

• Allow modification of base image
• Allow other "base images" images to use for toolbox creation
• Allow toolbox creation based on different base images
• Update function should have an option to update an image instead of its contents (https://www.reddit.com/r/Fedora/comments/u6kdet/comment/i5c7xgo/?utm_source=share&utm_medium=web2x&context=3)

If the list command of a toolbox misses toolboxes that settings exist for inform the user and prompt about what to do. This can be done as an info banner or with a dialogue. The options to the user should be:

• Delete Settings
• Keep Settings (settings will be applied to a toolbox with the same name if it ever gets created again)

• Display toolbox status (running/stopped)
• Refresh toolbox status continiously (every 10 sec, or after interaction)
• Stop toolbox
• Start Toolbox

• Docker Image to build Flatpak (#29)
• Proper Description for Software Center
• Add screenshot to app manifest

Dialogue on first start to set certain preferences e.g:

• Homefolder (default seperate or shared)
• Terminal program (gnome-terminal, Console, BlackBox)

Upon pressing a button to open terminal inside toolbox a terminal window should pop up and the command toolbox enter <name> should be run.

• Start containers
• Stop containers
• Initialize container struct from name
• Write tests that use toolbox (moved to seperate issue #23 )
• Setup docker/podman test image
• Fix podman test image not working with toolbox (moved to seperate issue #24)

Write tests that are not run on samle strings but that run against the actual toolbox cli and podman

• Allow applications inside the toolbox to be updated
• Check for application updates inside of the toolbox (if enabled)
• add configuration options to toolbox settings
• add configuration options to global settings
• Automatic updates (no, notification, auto apply)

Modify code to also allow running the tool as appimage + automatic buid.

• Individual Settings (relates to #6)
• General Settings (relates to #9)

The migration guide can be found here.

Have a toolbox settings window that stores individual settings per toolbox.

• Create struct for settings
• Connect individual settings to model
• On settings change (individual) update model and save them

https://relm4.org/docs/stable/relm4/factory/collections/struct.FactoryVec.html#method.from_vec

• Add applications from toolbox to application menu
• Remove applications from toolbox from application menu

• Docker image to build Flatpak
• Build flatpak in CI