Jean-Marc Lasgouttes wrote:
Abdelrazak Younes <[EMAIL PROTECTED]> writes:

Basically, the current FontList will be a specialisation of this
template:

typedef Range<FontInfo> FontList;

And we need the same thing for languages:

typedef Range<Language> LanguageList;

Ideas, comments?

I think I'd prefer to have a AttrList object where attributes are a
struct like

Font * font;
Change * change;
Language * language;

An entry would be NULL if there is no change (you can put smart
pointers or whatever in the mix, it does not change the idea).

This basically means that we rename FontInfo to Font, Font to AttrList and that we integrate Change tracking in there... or am I misunderstanding you?


I think an unified list like that would help understand the
synchronization between the different ranges.

You seem to miss the point that those attributes should be completely independent and thus *unsynchronized*.

Abdel.

Reply via email to