To Do
=====
Bugs
----
Next
----
Bump version number... Making a new branch for v0.3
Update to the lastest gradle using build.gradle.kts
Minimise icon should be a dash —
Look at how TabPane renders the close icon - is it customisable? Maybe an SVG path.
Consider making floating windows REMAIN as buttons in the Harbour.
Dockable.settingsMenu isn't in the spirit of JavaFX.
Consider allowing a collection of Node which are added to the Dock's ToolBar.
Just expose the toolbar's items?!?
Minimise icon makes it annoying - can't just add items to the end.
Each of my projects has a different way to add css style sheet. Pick ONE! Deprecate the others.
The names are annoying. Everyone else calls it a Dock, not a Dockable.
Harbour -> 4x DockSide -> 2x DockHalfSide -> Wharf/Berth/DockTab/HarbourTab -> Dock
Dockable.dockableContent is just plain weird??
Look at TabPane, it has setContent(node)
If we follow TabPane's lead, then Dock is similar to Tab, in which case it can be a class, not an interface
We can do away with the tricky Dockable/Dock issue.
Dock is the base class for your own docks.
Is it necessary for the "inner" parts such as DockSide to be part of the API, or to be Controls?
Make skins internal
Skins shouldn't be inner classes?
Don't use "skinnable" - e.g. In DockSkin : val dock : Dock get() = skinnable
Later
-----