1
0

ISSUES 3.3 KB

12345678910111213141516171819202122232425262728293031323334353637383940414243444546474849505152535455565758596061626364656667686970717273747576777879808182838485868788899091
  1. /**
  2. \page _issues_page Issues
  3. \todo
  4. - placing a "?" character in a text file doesn't display help text when
  5. passed into clish.
  6. - ACTIONS which are meant to handle signals like CTRL-C
  7. don't seem to work properly, either the sub-script fails and the
  8. shell breaks, or the sub-script never handles the signal (depending on
  9. platform).
  10. - the heap unittest current has 10 failures
  11. - no unittests for the dblockpool component yet...
  12. - lub_heap_destroy() method should be provided which will de-register any allocated blocks from the
  13. leak detection trees.
  14. - update leak detection to scan non-monitored allocated memory blocks, for references. This requires
  15. the ability to iterate all the heaps in the system.
  16. - auto-completion currently doesn't handle optional parameters (defined using the "prefix" attribute).
  17. - If a multi-word command is defined in global and local views then
  18. auto-completion currently works for both, but resolving doesn't seem to.
  19. \verbatim
  20. e.g. "mode" - local view
  21. "mode qos" - global view
  22. Will auto-complete "mode qos" but won't run it...
  23. \endverbatim
  24. - Doesn't handle wrapping of long lines properly; get multiple lines scrolling
  25. down the screen.
  26. - Not all files have been split out into one file per function...
  27. - need to complete the Doxygen documentation for clish, tinyrl and lub/argv
  28. \section _nice Nice to have
  29. - when importing from a namespace, allow the specification of the following:
  30. no-help - defaults to false but may be set true to prevent display in the help menu.
  31. no-completion - defaults to false but may be set true to prevent auto-completion.
  32. no-context-help - defaults to false but may be set true to prevent context sensitive help for
  33. commands.
  34. - place an access level on namespaces; saves worrying about defining access for
  35. every single command. e.g. device_show namespace could have different access
  36. to device_config namespace. device view simply imports both namespaces.
  37. - When defining a default attribute if you could include a variable in the
  38. definition, default could be given meaningful values.
  39. - Augment the XML schema for support of dynamic variables.
  40. e.g.
  41. \verbatim
  42. <VARIABLE name="fred"><ACTION>puts "hello world"</ACTION></VARIABLE>
  43. \endverbatim
  44. will get the value of "hello world" when expanded as ${fred}...
  45. This is simple for TCL as the result is returned... what about for clish ,
  46. how do we get a return value into the execitable?
  47. - Currently handles commands in one view or all views. Better model is to be able
  48. to specify a namespace for commands and then assign a view to a namespace.
  49. e.g.
  50. \verbatim
  51. <NAMESPACE name="fred">
  52. <COMMAND>
  53. </NAMESPACE>
  54. <VIEW name=" kdjkdj"...>
  55. <IMPORT namespace="fred">
  56. <COMMAND ...>
  57. </VIEW>
  58. \endverbatim
  59. by default a view imports commands from the global namespace.
  60. NB. need to be able to resolve commands from all included namespaces.
  61. - In addition a command could become an alias for an entire namespace's worth
  62. of sub-commands.
  63. e.g.
  64. \verbatim
  65. <NAMESPACE name="config">
  66. <COMMAND name="show"...>
  67. <COMMAND name="show ip"...>
  68. ...
  69. </NAMESPACE>
  70. <VIEW name="foobar"...>
  71. <COMMAND name="do"
  72. help="perform a configuration command"
  73. namespace="config"/>
  74. </VIEW>
  75. \endverbatim
  76. */