Re: [Guidolib-devel] Code Changes

[J. S. A. <js...@sh...>]

Hi Jerome,

On Tue, 2004-02-03 at 03:09, Jerome Berthet wrote:
> Do you want us to commit our changes first (about _getTagArgxxx
> functions., naguido.cpp...) ?

Sure, it shouldn't make too much difference - I have removed the files
from the build list, but not actually physically altered them.  However,
it might be good for me to make sure everything is ok with the latest
changes.

> Ok, we were thinking about doing something like this. This is a good
> Idea. Next step is probably to have separate settings attached to each
> GuidoHandle, so two different Guido documents could have different
> settings ( including page format...), i.e by adding a "settings" field to
> the PairArMusic struct.

Interesting.  I'll have a look at this and see about extended my
alterations to include this, if you prefer.

> We would like to keep GDeviceDefs.h as Guido-independent as possible,
> It there any other place where gFontDefs could be put ?

Sure, I could just add it to GUIDOEngine.h as a similar settings struct,
and perhaps place it in the PairGR?

> You can remove the internal GGS functions. We do not use it at all,
> but we are interested in it. What are your plans for GGS ? do you have
> specifications, drafts or something ?

I believe the initial reason for the GGS was to provide a platform
independent means of graphic output from the score engine.  However,
since you have achieved that already with the VGDevice class, it's role
will be a bit different! :-)  My thoughts are that it provides a means
to modularize the engine and an interface.  A developer could build a
graphic front-end for Java, say, or some other currently unsupported
graphic device without having to extend the engine (although that would
also be possible).  I'm waiting for Holger to get back to me about
approaching the GGS through a VGDevice, as that will affect the
specification.  Once something is solidified, I will certainly pass it
on to the list.

Cheers,

Scott