1.1.0

Added

• another type of code linting, provided by Joker
• a --debug flag that will run strongbox with lots of output and write a log file.
  • the name of the log file is shown after the application has exited
• ticket templates with instructions on using the new --debug flag

Changed

• 'wowman' was renamed 'strongbox' in the list
• split 'tukui' into 'tukui' and 'tukui-classic' in the 'source' column
  • this should make it clearer which game track a tukui addon can be installed to
• the number of addons displayed in the search results is now tuned according to number of addons in catalogue
• 'WoW Directory' has moved to the other side of the addon directory drop down and has been renamed 'Addon directory'

Fixed

• browser not opening addon URL
• very slow searches. Typing has now been decoupled from showing search results so it feels faster.
• added a caveat against the screenshots in the README. The dark-mode version only works on particular desktops.
• fixed bug that crashes GUI when the next upgrade is available.
• support for Java 11 (the next Java LTS)
  • some date time parsing was behaving strangely between versions 8 and 11
• a very old bug where the app would continue to run when 'Quit' was selected from the menu
  • rather than closing the window or doing ctrl-c
• useragent was still stuck on 'wowman'
• tukui/elvui support was not properly distinguishing the game track leading some tukui addons to not install
• search results would highlight anything matching an installed addon's 'label'
  • this explains why the same addon from different hosts would both be highlighted despite only being installed once

0.12.5

Fixed

• fixed bug that crashes GUI when the next upgrade is available.

1.0.0

This has mostly been a large clean up and code analysis/refactor exercise.

Added

• users can now specify their own catalogues
• strongbox can now operate without catalogues
  • it won't do much, but it won't crash and burn
• last selected addon directory is now remembered between application restarts
• migration tasks of wowman config and catalogue and nfo files to strongbox
  • should be seamless
  • wowman configuration is left untouched but .wowman.json files can be removed from the gui
• a 'delete .strongbox.json' action in the gui
  • behaves the same as the 'delete .wowman.json' action
• code profiling to key sections of the application I can turn on during development
  • used in optimising performance
  • disabled by default
• a log file that is written when '--debug' is used to start the application
  • intended to help hunt down user problems

Changed

• 'wowman' changed to 'strongbox'
• all usage of 'uri' changed to 'url'
• all usage of 'catalog' changes to 'catalogue'
• user-catalogue moved to the 'config' directory from the 'data' directory
  • prevents user-catalogue being deleted with the 'clear catalogues' action
• categories are now 'tags' with common categories unified across addon hosts
• function speccing has been greatly cleaned up and is coherent and sane now
• catalogues are now on specification version 2 (see ogri-la/strongbox-catalogue)
  • version 1 catalogues (ogri-la/wowman-data) are still supported

Fixed

• some performance problems, especially around loading catalogues

Removed

• the relational database
  • it has been replaced with a simple (albeit large) list of addons
• last traces of a 'donation url' and 'author name' removed
• 'alt-name' from catalogue items
• 'updated date' from catalogue
• support for nfo v1
  • invalid nfo files are now deleted.
• speccing from final build
  • it is enabled during development and testing but otherwise disabled
  • key inputs like catalogues and user config are still validated against their specs

1.0.0 pre-release

This is a pre-release of strongbox 1.0.0, previously wowman.

It's meant for those brave souls who would like to try it and report any bugs.

There are no sexy new features except a slight performance improvement.

The purpose of the new name and major version bump was for me to revisit a lot of decisions I had made while wowman was growing quickly and help me untangle them, clean them up and make them clearer for me going forwards.

A proper release will be made in the next day or two.

0.12.4

Changed

• clicking a link will now try the Java way of opening a URL, then look for xdg-open, gnome-open and kde-open to open URL
  • if nothing is found at all you will get an error in the console

Fixed

• fixes an exception that is raised by clicking a link when Java cannot detect your 'desktop' or a means to open URLs

0.12.3

Fixed

• fixes a bug where catalog entries whose 'description' is greater than 255 characters causes a crash while loading the database
  • thanks to https://github.com/rainecheck for reporting this bug

0.12.2

• release 0.12.1 was badly formed and missing the commit with the actual fix.

0.12.1

Fixed

• addons with no nfo file were attempting to upgrade it and failing
  • these addons are now skipped
• fixed a bug where addons with a nfo file that is still invalid even after upgrading have the nfo file deleted

0.12.0

Added

• 'source-id' column to gui (hidden by default)
• 'game-track' column to gui (hidden by default) that is either 'retail' or 'classic'
• support for reconciling addons by 'x-curse', 'x-wowi' and 'x-tukui' ids found in the .toc file
• gui tabs can now be switched using mouse scroll
• basic support to ignore addons that appear to be under version control
  • this can be manually disabled on a per-addon basis by adding the key ignore? and the value false to that addon's .wowman.json file
• user catalogue (github addons) can now be exported just like a directory full of addons can.

Changed

• renamed the 'go' column in the gui to 'source'
• export now captures game track so the correct game track is re-installed
• importing addons exported using this version of wowman should be much quicker
  • unfortunately old exports will still have an inexplicable long pause while importing. re-export your addons!
• nfo files (.wowman.json) are now specced out and will receive an upgrade on first start of 0.12.0
  • previously the file was only ever updated when an addon was installed or upgraded, and some bundled addons were still using very old formatted nfo files

Fixed

• selected directory was incorrect after restarting gui by switching themes
• 'refresh user catalog' gave no indication it was doing anything until it finally re-wrote the user catalogue
• clearing catalogues and clicking refresh didn't see the database rebuilt
• importing addons that don't match the currently selected game track are still imported correctly
  • if a game track (retail or classic) could not be found, a sensible guess is made

Removed

• dependency data.codec. My usage could be done with plain old java
• dependency cheshire. Functionality satisfied by clojure.data.json
• 'debugging' mode. I never used it and it wasn't doing any special

0.11.0

Added

• added www.tukui.org as an addon host
• added github.com as an addon host, using the 'releases' mechanism
  • some examples of supported addons
• 'user' catalogues of addons. This is a catalog controlled by the user with addons from hosts like github.com
  • this catalogue can be refreshed from Catalog -> Refresh user catalog
• source attributes are now present in the curseforge and wowinterface catalogues
• mac support
• a 'dark' theme for those Linux users who are using a dark widget set
  • this is just the inverse colours of the current 'light' theme

Changed

• new addon directories will have their game track set to classic by default if _classic_ is present in the path

Fixed

• exporting addons using the Import/Export -> Export addon list now uses the currently selected addon directory
• duplicate categories in the curseforge catalogue generation
• .part files are now removed if an error would cause a download to fail
• if an addon directory went missing between two calls to save settings, all addon directory settings would be removed
• a regression introduced in 0.10.0 where missing catalogue fields, like description, would become description=nil after pulling it out of the database.
  • this would cause masking of .toc file data that could be used in it's stead

Removed

• special handling for curseforge.com HTTP redirect behaviour
  • wowman now uses the curseforge API
• dependency metosin/spec-tools. It's a sophisticated tool but I just wasn't taking advantage of it