 |
iif_id.patch (976 bytes) |
 |
Perhaps a mouse hover hint would do? |
|
|
I have reached the conclusion that you have some secret love for mouseovers. :-) I'm rather for the explicit visuals especially when I have to figure out what's what and an overview (when everything is visible at once) helps much better than a mouseover (have to view them one by one). As far as I know there is no way to get the list of IIF id's, so this table may be The One. Btw I quite dislike the database-kind of stuff hidden in the intrface config. It would be much nicer to have a similar config table for: * List source: object, for which asset tag should be set * List of object with Cacti graphs * List of devices running CDP * List source: IPv4 NAT performers * List source: IPv4-enabled objects * List source: object, for which common name should be set * List source: objects without ports as well as * Default port outer interface IDs * List source: virtual objects |
|
|
The "list source" series of options accept arbitrary text in RackCode syntax, they are not database-like. The default OIF map can indeed be backed with a table, but in this case it won't be overridable by each user any more. If this idea makes it through the users mailing list, I won't mind the change. If you consider explicit table columns better than mouseovers, please make this consistent (THs and column ordering) with other similar tables and I will commit it. |
|
|
I will create the patch but please bear with me, I'm doing at least five different things at once. :-P |
|
|
Sure, take your time. |
|
|
So... I looked around. First, a bit prettier is this: --- a/inc/interface.php Mon Feb 25 22:31:57 2013 +0100 +++ b/inc/interface.php Thu Mar 07 13:21:01 2013 +0100 @@ -6507,7 +6507,7 @@ { global $nextorder; echo ' <table class=cooltable align=center border=0 cellpadding=5 cellspacing=0>'; - echo '<tr><th class=tdleft>inner interface</th><th></th><th class=tdleft>outer interface</th><th></th></tr>'; + echo '<tr><th class=tdleft>inner interface</th><th>iif key</th><th class=tdleft>index.php?page=chapter&chapter_no=2</th><th>oif key</th></tr>'; $last_iif_id = 0; $order = 'even'; foreach (getPortInterfaceCompat() as $record) But that's basically the same as before. I have checked most of the config tables an apart from Dictionary (which shows 'key' for me, I believe it's already in the upstream) I see no other tables which may benefit from showing the keys. The purpose to show the keys is to be able to reference them in the aforementioned "Interface config", and basically the iif and iof keys are used. Th other thing you mentioned that the entries are RackCode. Yes, I am aware of that however I observed that I almost exclusively use a form "{$typeid_4} or {$typeid_7} or {$typeid_8} or {$typeid_798}...". I don't know the usual usage patterns but my guess is that most people don't use fancy features of RackCode here. It could be a solution to be able to use an auitomatic config to generate the rackcode and the possibiliy to override the result manually, if someone wants it. This may be true for the "iif=oif, ..." and similar lists, too. And in fact I would have not looked for them in "USER INTERFACE" section: for me enabling ports is not really the part of the UI. :-) But these are just feedback, its quite okay for me like it is now. |
|
|
Commit dc7a926 stands for the patch originally submitted, which seems to be cleaner than the second. Thank you! |
- Anonymous
