first please excuseme for my poor english
theese days i'm reflecting about the inkscape engine. it can produce, move, rotate vectorial shapes. it can use different measurement units and put texts inside any shape, use grids and rulers, use different layers and so on. theese features could be a common base for any cad or flowcharter software. using inkscape capabilities a cad project or a workflow could display a very good eyecandy.

going on, my idea is to separate the engine and the front-end to different packages and starting from the engine, programming a different frontend (a sort of "fork") specialized for 2D cad and another one for flowcharting.

architecture could be like this:

-a common 2D vectorial engine.
-a common base frontend (delivering the client area and open/save copy/paste toolbars and menus, layer sidebar or window, color manager)
-separate "plugins" bars to manage specific tasks (i.e like a shapes and connectors tool for the flowcharter)

the interface assett (in the sense of the number and position of tools to load) could be stored in separate xml files.

suppose the name of the software becomes "vectorscape". you should launch the three sw in this way

vectorscape --inkscape.xml
vectorscape --cadskape.xml
vectorscape --flowchart.xml

or something similar.

what do you all think about?

I don't think SVG is a suitable format for CAD, strictly speaking. There are numerous properties of a drafting package that differentiate itself from software like Inkscape, Illustrator or Corel Draw.

Also, Inkscape already has a single flow-charting tool - I'm not sure it needs a different front end to take advantage of flow-charting.

That's just my 2-cents. Perhaps if you feel there are certain elements of the current Inkscape interface that is inhibiting your goals you could provide examples.