Config overhaul, tbg's http server with logging, and more!

New

1. tbg
   • new http server to listen to POST requests that trigger certain actions (change to a random image, set a specific image, quit server) (#36)
   • json logs are in $env:LOCALAPPDATA/tbg/tbg.log (#51)
2. Config
   • new port field to specify which port tbg server uses (#44)
   • default config path is now in $env:LOCALAPPDATA/tbg/config.yml
3. Command/Flag
   • can select profile through name: tbg run --profile pwsh (#32)
   • server commands (next-image set-image and quit) for convenience instead of manually making a POST request to tbg server's endpoints (#36, #45, #46)
   • -c --config flag to specify a command to use a custom config (#53)

Main Changes

1. tbg
   • default behavior is now randomly choosing an image from a random path under paths field in the config (#34)
     • -r --random flag is removed
   • removed interactive keystrokes (#49)
     • only way to interact with a tbg process is through server commands/making a request to its POST endpoints
2. Config
   • removed default alignment, opacity, and stretch fields (#31)
     • default values are now a constant center, 1.0 and uniformToFill respectively
   • all config fields except paths are optional. Here are the default values

     config field	default value
     alignment	center
     interval	1800
     port	9545
     profile	default
     opacity	1.0
     stretch	uniformToFill

   • when manually adding a path to the config, tilde (~), and %windows_style%/$unix_style ${environment_variables} are not expanded (#50)
   • interval now means in seconds instead of minutes (#53)
3. Command/Flag
   • can select profile through name: tbg run --profile pwsh (#32)
   • when adding a path through add command, tilde (~) is not expanded (#50)
   • config is always validated before executing run, add, remove, and config commands

Other Changes

• profile no longer needs list- prefix to identify the profile by index (#30)
• removed flag help messages (#47)
  • commands now must specify what each flag does for that command
• images are now identified through mime types, not extensions (#50)
• --alignment and --stretch errors now list all valid values (#50)
• video demos in README (#53)

Full Changelog: v0.3.0...v1.0.0

What's Changed

• v0.3.0 Release by @saltkid in #24

Breaking

1. new config format (see .tbg.yml.md)
2. new config name (.tbg.yml)
3. config command is no longer a valid sub command for any other command
   • this means the only valid config is the created .tbg.yml file
   • the only command left that accepts sub commands is help to print out help information for that command
4. removed edit as sub command for config
   • now, when any flag is set, it will edit the field specified by that flag without needing to specify the edit subcommand
   • this is because edit was not even a "main" command in the first place

Other Changes

1. codebase which was separated into modules is now just in the top level main module for simplicity (hence the line added/removed count)
   • old modules all depended on each other anyway
2. changing background is now more event driven, allowing extensibility
   • possible assigning shortcuts in tbg's config to map to events in the future?
3. updated docs to reflect the config changes

Full Changelog: v0.2.0...v0.3.0

tbg.exe checksums

• SHA-256

51469411b485e01a011e0fd0e1e40e7fb3478b4987295530d7fa1f2787aa0185

• MD5

818ab6f8512d92e92fbf46fe3931a4dd

edit and tbg_profile deprecated, blank _ flags, and more!

changelog

breaking

• edit command gone
  • editing per path flags functionality is now in add
• add can add paths, add flags to an existing path, change flags of an existing path.
• when removing a flag of a path through remove, it will no longer inherit its respective default flag field but instead leave a blank _
  • this just means during tbg run it will either inherit its respective default flag field or the user specified value via run flags (if any provided)
  • this blank _ behavior also applies to add. When not adding all flags, the unspecified flags will be blank _
• tbg_profile and the concept of default and user configs GONE
  • there can only be one config now, the config.yaml auto created in the same path as the tbg executable

etc

• doc changes to accommodate above changes

tbg.exe checksums

• SHA-256

3544AE13D78C0138A6732555824A2422BFBA0551155F4BC7D687565ACB3A7EDB

• MD5

97094c21ed2270998630590cd6238f5c

leftover bugs from v0.1.0 release:

• adding paths with no flags left a | after the path, fixed that
• paths separators are now standardized to always be backslashes, regardless of whatever inputted
  • this fixed remove and edit bugs since path names were not equal due to differing path separators

First release!

Features:

1. change background image of targeted windows terminal profile at a set interval
2. allow to set target profile, interval, image alignment, image stretch, and image opacity on the config
3. able to specify image collection dirs in the config
   • allow per path flags (alignment, stretch, and opacity) to override the default alignment, stretch, and opacity set in no. 2
4. can add and remove paths using tbg commands
   • can also edit path flags too
5. can print the current config using a command
6. can have multiple configs
   • you can set which config to use using the config command

More information on the docs