- Move method for creation of all buttons from NavigationButton to swing
util
- Correctly update InfoPanel when plugin is started or needs title bar
refresh
- Correctly update ClientUI title bar when custom one is visible
Signed-off-by: Tomas Slusny <slusnucky@gmail.com>
- Change info panel to support new hooks
- Change plugins to use NavigationButton for adding buttons to
titleToolbar
Signed-off-by: Tomas Slusny <slusnucky@gmail.com>
- Extract title toolbar layout to separate component
- Create new events for adding and removing title toolbar buttons
- Create TitleToolbar through Guice
Signed-off-by: Tomas Slusny <slusnucky@gmail.com>
- Use updated construction for NavigationButton
- Replace ClientUI injections with PluginToolbar injections
Signed-off-by: Tomas Slusny <slusnucky@gmail.com>
- Create PluginToolbar through Guice
- Create separate component class for toolbar layout
- Create custom navigation button component to not depend on swing
- Create new events that are fired on new toolbar button addition and
removal
Signed-off-by: Tomas Slusny <slusnucky@gmail.com>
- Change LinkBrowser to not use ClientUI as parent for message box (not
required at all) and change it from Guice service to static utility
class
- Set screenshot plugin offsets statically without recalculating them
based on swing component
Signed-off-by: Tomas Slusny <slusnucky@gmail.com>
- Make ClientUI wrap JFrame inside
- Do not make RuneLite class depend on Swing API at all
- Create ClientUI through Guice
- Simplify initialization and showing of UI
Signed-off-by: Tomas Slusny <slusnucky@gmail.com>
- Extract common utlity methods from ClientUI to SwingUtil utlity class.
- Make OSXUtil accept JFrame instead of ClientUI
Signed-off-by: Tomas Slusny <slusnucky@gmail.com>
Automatically append 300 to every world that is lower than 300 to
support both f.e. 22 and 322 formats for specifying the world.
Signed-off-by: Tomas Slusny <slusnucky@gmail.com>
