Hi mike and bert With cyrille we have a bunch of question about rome. Here is a list of affirmations/questions that we would like to get some answers: - RomePluginCanvas is the class to call the Cairo primitives. - What is RomeReferenceCanvas? Is it an abstract class? This is strange because RomeReferenceCanvas refers to its subclass Is this class that should be subclassed to create an SVG Canvas? or it is too dedicated to the romepluging - We imagine that RomePlug - Is there a romeCanvas that delegates to the current Canvas - What is a RomePluginTargetFile? We see two scenarios Sc1 Current clients used the current canvas Now we could have a newCanvas that wrap romeCanvas with the same API as currentCanvas => clients do not have to be changed but the system benefit from cairo or other romecanvas. - Was this integration done in the RomeTweakCanvas which wraps a RomeCanvas? Sc2 Can/Could Rome be used in place of the actual canvas (modulo client changes)? May be the actual Canvas should be offered as a subclass of RomeCanvas. Was it the idea? Could Rome be pushed in the core so that the current canvas can be a subclass of Rome? here current clients have to be fixed and currentCanvasAsRome is a subclass of RomeCanvas or CurrentCanvasAsRome wraps the currentCanvas to offer a rome interface on top of the current canvas API Stef