-
-
Notifications
You must be signed in to change notification settings - Fork 229
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Plan the expansion of the options #32
Comments
more info here: https://gitlab.kitware.com/f3d/f3d/-/issues/204 |
With the introduction of named options, we can loop back on this. I suggest to internally name options like this:
(the idea is to categorize, we also could have multiples levels: This will open to any number of options. Regarding hotkeys, I think that modifiers are a bad idea. I'd keep the current number of hotkeys and add only very very important one to it (even remove some not important one). Instead, a very simple command line wich will be used like this:
Of course, the actual naming of each options and categories will have to be discussed. |
I agree with the vim-like commands, but I'm not sure about the category, I'd rather keep the option name short... Or at least, provide short aliases ( |
That would work. I we do not introduce categories, how do you plan to support more options ?
and more later |
So here is the current listing of options and how they should be modified
|
Here is the new list of libf3d options
|
In the context of f3d-app#52 , Introduce a first element, f3d::options and start using it when possible without refactoring the whole of F3D for now. TODO in other PRs: - doc - F3DLoader refacto - options names f3d-app#32
We are running out of short options and hotkeys, Let's plan how to tackle that.
A few possibilities:
:comp=2
The text was updated successfully, but these errors were encountered: