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

List:       koffice-devel
Subject:    Re: Explanation on WP vs DTP modes in KWord (Re: Kde-cvs-digest request for information)
From:       Dirk_Schönberger <dirk.schoenberger () sz-online ! de>
Date:       2002-11-30 21:37:56
[Download RAW message or body]

> Well, I could be wrong as well. But I'm under the impression that KWord's
page
> layout mode tends to better suppport work on a page-by-page basis. Of
course
> it allows "chaining" frames together on separate pages but since it does
eg
> "not  know what a header, a footer and a column" is (as Nicholas put it) I
> think it's certainly working under another paradigm than it does in its
text
> oriented mode and that this "paradigm" (approach, way of thinking) is more
of
> the sort "creating individual pages that look graphically interesting"
than
> "make a bigger document as uniform as possible".

I think I understand this "page layout" mode. I haven't worked with the
"bigger" applications, like Ventura, or FrameMaker, but with some smaller
application suite, which allows for a similar model.
But I don't quite understand the differences (e.g. in User Interface) for
the "large block of text" mode. Care to explain?

> That's how I arrive at the conclusion that the things that are unique to
the
> "page layout mode" (as re-arranging separate pages) should be either
> integrated in the rest of KWord (eg by changing the document structure
view
> to something like the Ventura Navigator) or moved to another app which
> follows another approach, eg Scribus. Main thing, IMHO, would be to avoid
> having "two different ways of thinking" in the same program to a degree
that
> makes KWord to some people two different programs under the same name.

Again, I don't know Ventura Navigator, so please be patient :)
I have some trouble visualizing a document structure view which mixes
logical structure (chapters, headings and the like) with layout / visually
oriented items, like the frames on a page.
For two multiple applications, this is fine, as long as these applications
share the same text layout algorithm and probably other features like
embedding of graphics.
One of the things I absolutely don't like about the "professional" DTP
applications is their non-sharing attitude and their non-interchangeability,
i.e. all applications are specialist tools, but the general useability, like
common file formats, common clipboard exchange, common clipart/graphics
support, common GUI ..., is non-existant.
Somehow I don't have the impression that the Scribus authors are interested
much in this direction. This make it rather difficult as a KOffice
component, at least IMHO.

Regards
Dirk





_______________________________________________
koffice-devel mailing list
koffice-devel@mail.kde.org
http://mail.kde.org/mailman/listinfo/koffice-devel
[prev in list] [next in list] [prev in thread] [next in thread]