search

DrewNaylor / UXL-Launcher

An app launcher meant to launch Microsoft Office 2010, 2013, 2016, 2019 desktop software/apps, including ones from Office 365. Not associated with Microsoft.
Apache License 2.0
7 stars 1 forks source link

Allow a "small mode" that's kinda like the Office Shortcut Bar. #201

Open DrewNaylor opened 3 years ago

DrewNaylor commented 3 years ago

This can be a form that has just the main buttons along with buttons for New and Open, besides duplicating relevant menubar entries. The buttons should probably be in a FlowLayoutPanel. See also Office Shortcut Bar screenshots in #153.

When the user switches to this view, hide the main window and show this one. The setting to use this will persist across app restarts in case the user prefers it. If the user interacts with the Quickmenu while the small view is active, be sure to redirect stuff to it instead of the main window.

DrewNaylor commented 1 year ago

Try to figure out a way to have the "small mode" be a plugin that can be loaded at runtime if it's present in the installation folder, that way it can both be not installed if the user doesn't want it as well as allowing other, alternative UIs to be easily integrated into the View dropdown. There needs to be an option to select the default UI that loads on startup, as well. Not sure exactly how this can all be integrated to easily allow different licenses, perhaps there would have to be just multiple EXE files and they each have a file describing how they would be displayed in the main window and they'd all import the main library DLL? But there would probably have to also be easy ways to do settings, not sure.

Edit: maybe it would be ok if third-party alternative UIs are, say, licensed under the GPL, as long as the resulting combination isn't distributed (there will need to be a note somewhere stating that any alternative UI plugins that would be licensed in a way that would make them incompatible with UXL Launcher if they were to be directly bundled with it in an installer [such as by packaging it with a GPL plugin] is not allowed for licensing and probably legal reasons and these license-incompatible plugins must be distributed separately, in separate installers/packages). There's a discussion on Apache Airflow's Issues page that discusses this, and their conclusion appears to me to be that it's fine if the plugin is optional and not distributed with the program: https://github.com/apache/airflow/issues/9898 I really hope this is fine, because I don't want to restrict allowed licenses.