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

List:       koffice-devel
Subject:    Re: Merging KWord and KPresenter
From:       "Michael Fair" <michael () daclubhouse ! net>
Date:       2003-10-15 16:42:52
[Download RAW message or body]

Thanks again Nicolas,

That was exactly the kind of thing I was looking for.
It's good to know that I'm at least seeing the same
things you guys are even if I can't quite code them
as proficiently yet.

For the record, I do see KOffice as being the only Open
Source Office suite that is truly poised to offer a totally
integrated experience to the end user.

There are so many innovative, and fundamentally disruptive
things I see KOffice capable of, that truly transform the
end user's experience of what an Office suite can do for
them, that it's hard for me to keep silent.  The epiphanies
and vision I had for what is possible with KOffice go so far
beyond what the other products I've seen are even capable of
that I am absolutely compelled to get involved to help
work on them.

Due to the risk of being portrayed as just another guy
with a bunch of ideas and no code, and that I feel I've
twisted dfaure's ear enough recently, I'm not going to
take up discussion time bringing them up now.  I'm going
to spend my time just fixing bugs till I'm at least
competent at finding and fixing them myself and can begin
the groundwork myself.  However, please, anyone with even
just a passing interest in hearing some of please contact
me privately.  I'd love to share them with you and get
your feedback on architecture and interface design, as
well as get input on how to make the ideas/solutions even
better, stronger, faster, quicker to implement, etc.

Thank you for including me.
Now, back to fixing that bug.

-- Michael --

----- Original Message ----- 
From: "Nicolas Goutte" <nicolasg@snafu.de>
To: "For developer's discussion about KOffice" <koffice-devel@mail.kde.org>
Sent: Wednesday, October 15, 2003 4:19 AM
Subject: Re: Merging KWord and KPresenter


No, you are not smoking.

I too a found that the code and file format was too similiar but used two
different implementations, what I did not find good. I had even thought
about
merging the applications, but I have still not found a good UI (user
inteface) idea for it.

However, as for everything in KOffice, having nice ideas is not enough,
someone must work on it and do the code, which has not happened yet.

Have a nice day!

PS.: it was hard to find again but here it is:
http://lists.kde.org/?l=koffice&m=104566453022965&w=2
http://lists.kde.org/?l=koffice&m=104567317806047&w=2

On Wednesday 15 October 2003 04:18, Michael Fair wrote:
> Has anyone here discussed migrating toward the rendering and editing
> components of KWord and KPresentor into the same KPart?  Not to merge the
> applications since I think the available default toolsets and the UI
> organization of the two programs are very different, but the inherant
> functionality of those two applications seem so similar (each has ideas of
> pages with various frames/backgrounds/headers/parts embedded inside, each
> could use alignment tools, making columns, and font sizes)..
>
> This might already be happening (I know they share the same text
rendering)
> but the more I look at it, the more it seems like they each would benefit
> from having the same underlying capabilities.  KWord might not use the
> "transition" facilities that KPresenter uses, but I can think of a few
> useful cases for it.  KPresenter probably wouldn't have a use for end
> notes...  but I'm sure some bright spark can think of an innovative way to
> use them too.
>
> Anyway, feel free to tell me I'm smoking something and should get my head
> examined, and of course I'm not familar with the underlying interfaces and
> structures so have no clue about how much work is involved, but I wouldn't
> expect this work to being until after 1.4 anyway.  Perhaps something for a
> 2.0 release where not only are the KParts sharable but maybe every
> application is able to actually be the same part and each application
would
> be a predefined set of toolbars/interface UI elements for manipulating
> certain aspects of a document.  (e.g. A "table" in KWord, is implemented
> using the same code that drives a "sheet" in KSpread.)
>
> I would envision that the UI interfaces would remain separate and I'm not
> suggesting merging the applications.  It just seems that the actual
> rendering and manipulation of a Document/Presentation have so many common
> elements that both Documents and Presentations seem like the same
> fundamental underlying object -- not unlike the vision for an SVG
document.
>
> -- Michael --
>
> _______________________________________________
> koffice-devel mailing list
> koffice-devel@mail.kde.org
> http://mail.kde.org/mailman/listinfo/koffice-devel

_______________________________________________
koffice-devel mailing list
koffice-devel@mail.kde.org
http://mail.kde.org/mailman/listinfo/koffice-devel

_______________________________________________
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]