search

PiRSquared17 / synoptic

Automatically exported from code.google.com/p/synoptic
0 stars 0 forks source link

Synoptic library API #56

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
Why is this enhancement useful?

With the Swing and GWT GUIs we are moving towards a model in which there is a 
core Synoptic library and then there is other code that uses this library as a 
blackbox.

To maximize code re-use and to simplify future blackbox uses of Synoptic we 
need to design a Synoptic library API. It will have the following two 
requirements at its core:
- Expose flexibility, so that the client code can selectively turn on\off 
features
- Hide implementation details, so that we can easily evolve the library 

A good way to start on this is to refactor the Swing uses of Synoptic into a 
library that can be reused from GWT.

Original issue reported on code.google.com by bestchai on 5 May 2011 at 12:11

GoogleCodeExporter commented 9 years ago 
An important concrete issue that is relevant to this is to encapsulate 
refinement and coarsening state in the Synoptic core, instead of having the 
library clients maintain it.

Original comment by bestchai on 17 Dec 2011 at 3:42