Skip to content
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

Closed
opnsenseuser opened this issue Nov 5, 2018 · 15 comments
Closed

routing: standard menu item #2878

opnsenseuser opened this issue Nov 5, 2018 · 15 comments
Assignees
Labels
feature Adding new functionality
Milestone

Comments

@opnsenseuser
Copy link
Member

opnsenseuser commented Nov 5, 2018

@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é

@mimugmail
Copy link
Member

Perhaps we could move:

Telegraf
Colldectd
Vnstat
Zabbix Agent
Zabbix Proxy
LLDPd
ntopng

to Reporting?

@fichtner
Copy link
Member

fichtner commented Nov 5, 2018

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.

@opnsenseuser
Copy link
Member Author

opnsenseuser commented Nov 5, 2018

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)).

@fichtner fichtner self-assigned this Dec 28, 2018
@fichtner fichtner changed the title Is it really useful to put almost every plugin in the "service" menu? routing: standard menu item Dec 28, 2018
@fichtner fichtner added the feature Adding new functionality label Dec 28, 2018
@fichtner fichtner added this to the 19.1 milestone Dec 28, 2018
@fichtner
Copy link
Member

Also see #1647

@opnsenseuser
Copy link
Member Author

@fichtner really great! 👍

fichtner added a commit that referenced this issue Jan 20, 2019
@fichtner
Copy link
Member

screenshot 2019-01-20 at 11 57 07 am

@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.

@AdSchellevis
Copy link
Member

@fichtner development branch is fine, I’ll get back to you about production release

@AdSchellevis
Copy link
Member

@fichtner I've pulled your change into master, let's do this for 19.1.

AdSchellevis added a commit to opnsense/docs that referenced this issue Jan 25, 2019
@fichtner
Copy link
Member

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

@AdSchellevis
Copy link
Member

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

AdSchellevis added a commit to opnsense/docs that referenced this issue Jan 25, 2019
@fichtner
Copy link
Member

Yes, thanks and sorry for the trouble.

@AdSchellevis
Copy link
Member

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.

@fichtner
Copy link
Member

hyperv might be fixed... reports are inconclusive or incomplete at this point

@AdSchellevis
Copy link
Member

we'll see, can always close when it appears to be solved

@fichtner
Copy link
Member

ok 👍

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature Adding new functionality
Development

No branches or pull requests

4 participants