Re: Synopsis - tutorials

Markus Elfring wrote:
> 
>> May be asking more specific questions could lead to a more
>> constructive discussion?
> 
> Which details can or should be differently designed so that the licence
> for the Keystone-"Inspector Clouseau API" will not be violated?

The Keystone parser is distributed under GPL. We had an extensive discussion
about licenses on the OpenC++ list, and people where upset about me distributing
Synopsis under LGPL, because, apparently, it makes it hard to use Synopsis code
with proprietary extensions. LGPL simply requires the covered library to be
exchangable / upgradable in-vito, but GPL requires the entirety of the application
to be freely distributable. The only trick to work around this is not to link
at all, but use other mechanisms for communication among the components, such as,
streaming the representation from one component to a file, and reading it back
in from another, in a separate process.
I don't like the idea at all, because

1) It really defeats the whole idea of the GPL.
2) You chose a bad design to work around a legal problem.

> You published an overview for class relationships in an UML format. Can
> this approach be updated to achieve a model-driven design perhaps?

What is a 'model-driven design' in our context, and why should we strive to
achieve this ? What would you like to be able to do that you presently can't,
without changing the design ?

(Hint: The answer is not a list of references to external resources you want
 me to read. The answer is you engaging into the discussion by trying to
 understand what Synopsis is and does, and then suggesting concrete enhancements,
 based on specific use-cases.)

Thanks,
		Stefan

-- 

      ...ich hab' noch einen Koffer in Berlin...