[prev in list] [next in list] [prev in thread] [next in thread] 

List:       koffice-devel
Subject:    Re: new KWord
From:       John Califf <jcaliff () compuzone ! net>
Date:       2000-11-06 14:57:31
[Download RAW message or body]

Reginald Stadlbauer wrote:
> 
> On Sunday 05 November 2000 22:55, Shaheed Haque wrote:
> > Hi Reggie,
> >
> > Like Thomas, I see no real alternative to storing some exceptions with the
> > text. It is very common to have just a word in a paragraph italicised for
> > example. And once we have that, the mechanism works quite well for special
> > objects too. Do you have an alternative in mind?
> >
> > On the other hand, I think that styles should behave like this:
> >
> > 1. On writing XML, the attributes of a paragrpah should be compared to the
> > style sheet entry for that paragraph, and only the exception stored (along
> > with the style name).
> >
> > 2. On reading, the style sheet entry named in the paragraph should set the
> > baseline attributes for the paragraph, being overridden by the expcetions.
> >
> > I think this is what you were saying too, right?
> 
> Yes, that sounds good. That is also how styles internally work now. Each
> format "inherits" from a style and stores differences.
> 
> > I also agree that there is cruft that we could tidy up (e.g. I'm thinking
> > of making FORMATs more consistent). Whatever we do, we must make sure that
> > syntaxVersion=1 is still supported too.
> 
> Yes, true.
> 
> --
> Reggie (reggie@trolltech.com)
> _______________________________________________

Regarding all these changes, this seems like very good news. 
Particularly regarding some criticisms I had before becoming involved in
KOffice about the lack of efficiency in loading large documents because
of excessive detail in the document structure at every level, rather
than having styles to be applied for whole documents and sections and
changes from these styles within each frame, paragraph, etc.  I am glad
that you are actually doing that.  I guess you read those posts a few
months ago and also have your own reasons for making major changes in
the basics.

I'm a little confused about where these changes are being made.  In the
main cvs branch version, or another branch?  Do they require a
prerelease of Qt 3 or do they work with the current Qt 2.2.1 ?  I guess
an easy way to find out is to update again from the main branch.  If
they aren't in the main branch, when will these changes be merged into
it?

Slightly off topic, but I was very surprised to discover when looking at
the export filters that the one for kwd -> html is empty - it just
generates an empty html document.  The import filter html -> kwd works
fine.  This export filter is very important because html really should
be the standard document format across all the different word
processors,  even though it lacks what's needed for printing and dtp. 
But is more widely used.  The page divisions have to be handled
differently or ignored, though, for html unless using the dtp style in
which each kwd page should be a separate html document.  I consider html
filters more important than the MS/Ole filters.

I cannot work on kword much anymore right now but will be glad to help
again after I get Krayon (KImageShop) in better shape and more complete
and I haven't forgotten about that committment at all.  There have also
been a number of usuability problems, for me at least, involving the
core libs which I just had to fix to make kde from current cvs usable,
and I have not had very good luck getting any feedback, good or bad, to
the patches I've submitted.  Very frustrating but I don't give up
easily.

John
_______________________________________________
Koffice-devel mailing list
Koffice-devel@master.kde.org
http://master.kde.org/mailman/listinfo/koffice-devel

[prev in list] [next in list] [prev in thread] [next in thread]