Re: Pango change, first^Wsecond baby step !

[Hans Breuer <hans breuer org>]

At 18:25 22.06.02 +0200, Cyrille Chepelov wrote:
> Le Sat, Jun 22, 2002, à 04:40:53PM +0200, Hans Breuer a écrit:
> [...]
>
> What I wanted to do was to carry on the bulk of the new DiaFont change, and
> commit with something more than two hands can tinker with (there will be
> lots of run-time breakage to fix about everywhere). 
What I tried to suggest was take a few objects/plug-ins and take them
for prototyping - while at first ignore all the others. At least a 
simple approach with my msvc build setup.

> The next potential transformations:
>       * DiaFont also includes height 
>       * DiaString is a chunk of text with visual attributes and a position
> on a diagram 
>
> need to be more discussed before they can take place; besides, the first one
> is basically a mechanical change over the whole tree (can happen while
> others do modifications), and the second one can happen gradually, on an
> object-by-object basis (and should be well planned, to avoid loosing old
> diagrams).
Agreed.

> > Again, do you first plan to change all the objects before letting 
> > someone else take a look?  To me it appears to be much simpler
> > to let the new API evolve at a restricted set of objects (say
> > Standard, UML, ...) and plug-ins (I'd take wmf, python, ...)
> > and get better ideas at that instead of converting all and
> > then restructuring all again ;-)
>
> I can't make the GdkFont -> Pango transition (first stage) happen in a
> gradual way (well, maybe I could have, but it would have meant more work).
> However, the next changes should happen gradually, in short
> change-compile-test-commit cycles.
Fine with me. It'll probably take me an hour to compile and crash the
current version. Will go online than again.

> Can you point me to a quick, comprehensive and well-written primer on
> GObject ?
I wished I could, would have to read it myself. IIRC there where some
enligthning mails about GObject at creation time, written by the 
authors of GObject, Tim Janik.
But at least I'm not aware of a GObject HowTo :(

        Hans
-------- Hans "at" Breuer "dot" Org -----------
Tell me what you need, and I'll tell you how to 
get along without it.                -- Dilbert