Winbox and CLI inconsistencies

[jarda]

Hi all,
I am sure everyone already realised that, but I have not seen any discussion about this topic, therefore I would like to try to open it. Maybe none cares…

Does anyone know why the winbox menu structure does not corresponds to CLI structure?

Why some functions are allowed only from CLI and not from winbox?

Is there any work on aligning both together in order to make both user interfaces behave the same? It would be much more better to have it consistent and everything accessible in the same way from both interfaces.

[rextended]

@jarda

Hi all,

1. I am sure everyone already realised that,

2. but I have not seen any discussion about this topic, therefore I would like to try to open it.

3. Maybe none cares…

4. Does anyone know why the winbox menu structure does not corresponds to CLI structure?

5. Why some functions are allowed only from CLI and not from winbox?

6. Is there any work on aligning both together in order to make both user interfaces behave the same?
   4 again)It would be much more better to have it consistent and everything accessible in the same way from both interfaces.

1. Obviously

3. And I?

4. Because Winbox is “mouse” oriented, and the CLI are keyboard oriented, and are good how are both structurated…

5. Because usually are hazardous function, and for security you must activate manually…
   like enable the “disable running check” on x86, if the ethernet are not fully supported, you lost the connection, or you lock the x86 machine…

6. Why align the CLI and Winbox? Are made for two different purposes,
   like DOS and Windows,
   like shell and GUI,
   like a PC and a smartphone,
   like Windows XP and Windows 8,
   like Mac OS X and (i)OS X…

[Rudios]

I think we have to refer them as differences rather than inconsistencies.

[rextended]

@Rudios

I think we have to refer them as differences rather than inconsistencies.

+1