-
Notifications
You must be signed in to change notification settings - Fork 710
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
routing: standard menu item #2878
Comments
Perhaps we could move: Telegraf to |
There's little we can do to avoid long menus long term, 4th level is not great for overview. I like @mimugmail's suggestion about the reporting, and we should eventually go for a standard routing menu. |
I fully agree with you and @mimugmail. Other plugins should really be assigned more specific. and the routing is extra (can not be wrong with a firewall anyway) -> This provides more overview! @fichtner as soon as the routing is available as a separate main menu item, I would adapt all the themes (@media/css) and the opnsense_theme.js for the (.on (resize)). |
Also see #1647 |
@fichtner really great! 👍 |
@AdSchellevis 19.1 or 19.7 ... this is something that has been put off for too long. In any case with your OK I would like to add this to development branch now. |
@fichtner development branch is fine, I’ll get back to you about production release |
@fichtner I've pulled your change into master, let's do this for 19.1. |
I already reverted it... discussing other ways with @mimugmail currently... none of the ways forward are great so it's best to stick with what we always had |
ok, I'll revert the cherry-pick and doc then, let's keep this issue closed if it doesn't reflect the actual state anymore then |
This reverts commit 20874be.
Yes, thanks and sorry for the trouble. |
no problem, going to move the other discussions (pppoe, hyperv) to 19.7 as well, it's not very likely they will be sorted out in a day. |
hyperv might be fixed... reports are inconclusive or incomplete at this point |
we'll see, can always close when it appears to be solved |
ok 👍 |
@fichtner
@AdSchellevis
Only as food for thought! and no negative review!
Is it really useful to put almost every plugin in the "service" menu? if I install more than 20 plugins on my test environment, sometimes, it depends on the plugin, even the new "dropup" function of the sidebar is no long enough to display the full menu.
It would still have so much space in the main menu and could for the sake of clarity, some plugins in another or new category record.
Opnsense gets more and more new plugins, but stuffing almost everything in the category "services" seems to me to be over-thinking.
19.1 will be another milestone and should, in my opinion, take another step in this regard.
thx,
best regards,
rené
The text was updated successfully, but these errors were encountered: