| 1 | <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> |
| 2 | <html> |
| 3 | <head> |
| 4 | <title>Roadmap</title> |
| 5 | </head> |
| 6 | <body> |
| 7 | |
| 8 | <h1>Roadmap</h1> |
| 9 | |
| 10 | <p> |
| 11 | As of january 28 2004, the short term development plans include the following |
| 12 | items. |
| 13 | |
| 14 | <UL> |
| 15 | <LI> Add the copyright notices in each program file. |
| 16 | <LI> Insure that the coding practices are being implemented. |
| 17 | <LI> Polish the visual appearance: icons for the tabs and buttons, |
| 18 | background, lines and labels in the control flow viewer... |
| 19 | <LI> When a trace is opened, start a background thread to precompute |
| 20 | the system state and memorize it after each ~100 000 events. |
| 21 | Have the option to save the precomputed state when a trace is closed. |
| 22 | Use the precomputed state if available when opening a trace or |
| 23 | seeking in a trace. Use the same thread for computing statistics. |
| 24 | <LI> Update module.c to ease changing a module into a builtin feature. |
| 25 | <LI> Split processTrace into tracecontext and processtrace. |
| 26 | <LI> Insure that g_info logging is generally available but off by default. |
| 27 | <LI> Document each header file such that developer documentation can |
| 28 | be extracted automatically using |
| 29 | <A href="http://www.doxygen.org">Doxygen</A>. |
| 30 | <LI> Complete the user and developer documentation. |
| 31 | <LI> Test the viewer on large SMP traces. Insure that 2GB files do not cause |
| 32 | crashes. Note and fix unduly long delays. |
| 33 | <LI> Add C99 test (declaration of variable inside a function) to configure.in |
| 34 | |
| 35 | |
| 36 | </body> |
| 37 | </html> |
| 38 | |
| 39 | |
| 40 | |