I’m starting work on a canvas based graphics package and I have a question 
about organization.

We currently have:

Graphics.swc has a graphics package which has mostly generic interfaces.
Graphics.swc has an svg package which has SVG filters, gradients, transforms 
and the like.
Graphics.swc has a display package which has some definitions which are a 
complement to ones in the graphics package as well as a Graphics API 
implementation which is specific to SVG.

Basic.swc has an svg package which implements IGraphicShape using various SVG 
elements.

Some issues I have is:

1. The current arrangement is confusing. Finding what is where is not easy.
2. The display and graphics packages should probably be combined into a single 
package.
3. The display package has implementation which is specific to SVG. That does 
not leave a good place to implement the canvas implementation.


Thoughts?

Rolling the Basic SVG package into Graphics (as things stand) is not an option 
because they use UIBase.

Reply via email to