This is what I like TODO

If you have any good ideas, let me know:
goran_schwarz@hotmail.com
gorans@sybase.com

• Move CountersModel into asemon.cm package this also implicates splitting GetCounters all "sub classes" and make them into "proper" java classes. Why: the GetCounters starts to get BIG
• More "save props" for graphs and TabCntrPanels
• The OFF-LINE MODE. Meaning view persisted counters... - Add Off-Line Connect dialogue
• Work more on the Spinlock panel... set descriptions for known spinlocks, fix the renderer so it indicates high values with RED color or similar.
• Configuration now has getProps() and getSaveProps() why not put them together for "read" so it reads: system->props->saveProps and when we saveProps we only save them into the saveProps because we do not want to write in the "config" file... Meaning different level of config read...
• Cleanup all the classes that are not used today...
• Save more GUI stuff in the saveProps. have a "tab" been "un-docked" into its own window, what was the x,y position. Should the graph(s) be active or disabled.
• Menu->view->"Configure" What tabs should be visible and some configurations for each tab in a "list" form. Example: Show on Tab[x], Persist To Off-line (abs[x] diff[x] rate[x])
• Persister: if table destination table exists: check if all the desired columns are in the table (if not, alter table add column...)
• Try to get HOST CPU usage in it's own Tab (and if possible disk IO statistics)
• New Properties/Preferences Dialog which looks like the Eclipse one...
• SQL Capture: Right click menu on tables, redo the GUI and code
• Make copy to clipboard a bit better
• Validate that the OFF Line works as it should after this major re-code
• CounterModel redo the code, it's pritty uggly for the moment
• Options panel: make all CM properties editable (a good overview) of all the CM's that are configured.
• Implement the lock tool
• Integrate 'dbisql' into various places... dbisql has good perf & tuning output.
  Right now it's in SQL Window, but it needs to be in more places.
• OFF-Line: Store only the specified capture set (ABS, DIFF or RATE)
• WIZARD: create a wizard that creates a new UserDefined CM...
• A new permanent CM that checks mon"CurrentExecutingSQL and statements... this is a complement to capture SQL
• OFF-Line: make a "Capture SQL" that works for off-line as well