Roadmap

SolidShineUI Library Roadmap

This is the general roadmap for the future of this library.

In general, this roadmap is based upon the year I plan to implement the given items and are not tied to a specific version.

This file will be edited as I make adjustments and changes. Nothing here is set in stone.

Done

• Release version 1.7
  • NuGet support
  • .NET 5.0 support
• Release version 1.8
  • Keyboard shortcut classes
  • Improvements to FontSelectDialog
  • TabControl is now ready!
• Release version 1.8.1
  • Bug fixes
• Release version 1.8.2
  • Tab drag/drop
  • Improvements to KeyRegistry
  • Additional XML comments for code
• Release version 1.8.3
  • Bug fixes
• Release version 1.9
  • Rewrite SelectPanel to not base from UserControl
    • To help with this, SelectableCollection can be used
  • Add "light theme" and "dark theme" to ColorScheme
  • first pass at PropertyGrid control
• Versions 1.9.2 and 1.9.3
  • Further work on PropertyGrid
  • .NET 7.0 support
  • Bulk of online documentation set up

Future

First Half 2024

• Avalonia support
• Ribbon control
• Toolbar control
• Revamp/polish all existing controls
• Redesigned ColorScheme (to be called SsuiTheme)

Second Half 2024

• FileSelect control for Avalonia
• Improve drag-drop visuals of TabControl
• New SelectableControl for SelectPanel
• Multiple TabControl drag-and-drop
• More editors for PropertyList
• More color spaces/profiles support
  • CMYK, CIELAB
• SsuiTheme editor dialog
  • Use editor in PathfinderJson and PropertyBuilder as basis
• Touch/keyboard support for ImageColorPicker
  • May require yet another rewrite

2025

• Ribbon control/tab rearrangment
• Tear off Ribbon groups
• XML support for Ribbon/Toolbar
• Commands library - connect with existing command libraries
  • Integrates with Toolbar, Ribbon, Keyboard shortcuts
• Less dense style / other alternative styles (to fit with Avalonia's Fluent theme, for example)
• Typography support in FontSelectDialog (might be pushed back)
• DataTable, DataInputDialog (might be pushed back)
  • Will rely on core bits of PropertyList
  • Will require a global static list of property editors (rename to data type editors?), rather than a list being stored in a PropertyList instance
• Consider breaking library into separate parts?
  • Non-UI elements in one package (i.e. WildcardMatch, ArithmeticParser)
  • PropertyList and DataTable in its own package
  • Ribbon, Toolbar in their own packages
  • Commands library in its own package?
    • Could have versions that interface with various existing command libraries

Late 2025 / Early 2026

• New major version
  • Drop .NET Framework support, .NET Standard
  • Minimum .NET version: 8.0
• MAUI support
• Maybe Uno support?
• Improvements to DataTable?
• JSON support for Ribbon, Toolbar, SsuiTheme, keyboard shortcuts

Late 2026 / 2027

• Figure out what I wanna even do after that