1. add new directive to parser
2. add new sort function
3. add new option to ifsort directive
4. support new option in side menu generation code
5. update the documentation (and the book!) as this changes the section on ordering
Lots of little bits to do throughout the code, but none of them in themselves difficult. Will add this to the wishlist as I expect to be doing some development on Routers2 between now and Xmas.
Statistics: Posted by stevesh — Wed Oct 10, 2012 7:51 am
]]>
Anyway, I still think it should be more flexible
Couldn't you add an enhanced option that takes a number for the ordering? Like:
routers.cgi*Order[asdf]: 1
routers.cgi*Order[qwertz]: 2
which can be parsed by your scripts?
Statistics: Posted by gerch_winnheuer — Wed Oct 10, 2012 6:37 am
]]>
What you can do, though, is to use the ifsort option in the routers2.conf; also, if you use routers.cgi*ShortDesc[] to set a short description for targets, then you can prefix this with a zero-padded number to force a sort order - eg, ShortDesc[foo]: 01. foo
I know this is not as flexible as you might like, but it has been used by several other people to approximate what you're after.
Statistics: Posted by stevesh — Tue Oct 02, 2012 10:08 am
]]>
I am not always happy with the automated order of the targets.
Could you add an option in the routers.conf that allows the order of the targets JUST LIKE in the order they are specified in the *.cfg files with the Target[] lines?
Additional, the user defined graphs and summary pages could be reference in a similar way in order to create the ordering of the targets just like someone wants.
(Example: I am monitoring several VPN graphs such as RemoteAccess, WebVPN, Site-to-Site, etc. Now I have a single summary graph but I don't want it to be in the end of the target list, because all the other VPN graphs are somewhere else.)
Statistics: Posted by gerch_winnheuer — Mon Oct 01, 2012 10:30 pm
]]>