[prev in list] [next in list] [prev in thread] [next in thread]
List: koffice-devel
Subject: Re: koffice-devel Digest, Vol 19, Issue 39
From: Muhammad Atif <atif.muhammad () gmail ! com>
Date: 2004-10-27 11:29:51
Message-ID: 407338f304102704291a35031b () mail ! gmail ! com
[Download RAW message or body]
having a KPresenter>>KWord filter is impractical. its not worth it.
On 27 Oct 2004 10:01:04 -0000, koffice-devel-request@kde.org
<koffice-devel-request@kde.org> wrote:
> Send koffice-devel mailing list submissions to
> koffice-devel@kde.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
> https://mail.kde.org/mailman/listinfo/koffice-devel
> or, via email, send a message with subject or body 'help' to
> koffice-devel-request@kde.org
>
> You can reach the person managing the list at
> koffice-devel-owner@kde.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of koffice-devel digest..."
>
> Today's Topics:
>
> 1. Re: save a kword file as a spread sheet (Nicolas Goutte)
> 2. Re: save a kword file as a spread sheet (zander@kde.org)
> 3. Re: save a kword file as a spread sheet (Nicolas Goutte)
> 4. Re: save a kword file as a spread sheet (Tomas Mecir)
> 5. Re: save a kword file as a spread sheet (zander@kde.org)
> 6. Re: save a kword file as a spread sheet (David Faure)
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Wed, 27 Oct 2004 10:54:28 +0200
> From: Nicolas Goutte <nicolasg@snafu.de>
> Subject: Re: save a kword file as a spread sheet
> To: For developer's discussion about KOffice <koffice-devel@kde.org>
> Message-ID: <200410271054.28873.nicolasg@snafu.de>
> Content-Type: text/plain; charset="iso-8859-1"
>
> On Wednesday 27 October 2004 10:49, David Faure wrote:
> > On Wednesday 27 October 2004 10:41, Werner Trobin wrote:
> > > Merging the code is not really possible, IMHO. The two problems we \
> > > have to solve are:
> > > - Which mimetypes of the graph have a path to the target mimetype? \
> > > (for the filter dialog box)
> >
> > Yes, so how do you suggest we exclude some paths from that graph?
> > I like Tomas' idea, I think it's simple enough; but maybe a very high
> > weight could mean the same thing? If it doesn't prevent using this \
> > filter (as the final filter when exporting to text/plain), that is.
>
> Tomas' idea has the same problem. If we do not know the exact path before
> showing the dialog, we can still have absurd paths.
>
> (You must still allow KPresenter to KWord, even if there would be a \
> filter chain like: KPresenter => Plain Text => KWord .)
>
> Have a nice day!
>
> ------------------------------
>
> Message: 2
> Date: Wed, 27 Oct 2004 10:54:56 +0200
> From: zander@kde.org
> Subject: Re: save a kword file as a spread sheet
> To: For developer's discussion about KOffice <koffice-devel@kde.org>
> Message-ID: <20041027085456.GB5118@factotummedia.nl>
> Content-Type: text/plain; charset="us-ascii"
>
> On Wed, Oct 27, 2004 at 10:41:56AM +0200, Werner Trobin wrote:
> > On Wednesday 27 October 2004 10:20, Nicolas Goutte wrote:
> > > On Wednesday 27 October 2004 09:11, Tomas Mecir wrote:
> > > > On Tue, 26 Oct 2004 18:53:38 +0200, Nicolas Goutte \
> > > > <nicolasg@snafu.de>
> > >
> > > wrote:
> > > > > > This is the known "going via text/plain in the filter chain" \
> > > > > > problem. Nicolas Goutte was looking into it afaik.
> > > > >
> > > > > Yes, but as fixing it exceed the time that I can guarantee to \
> > > > > work on it, I have done nothing for now. However I can try to \
> > > > > explain to anybody wanting to try to fix it.
> > > >
> > > > Hm, wouldn't it be sufficient to simply add a flag for each
> > > > import/export filter, that would state whether output of this
> > > > particular filter can be used as a source for another filter? Then \
> > > > set that flag for filters that output to HTML and text/plain... \
> > > > Maybe not perfect, but it should work.
> > >
> > > No, we have decide to do it by filter weights. However that means \
> > > that new code must be added. (The filter weights are only user when \
> > > creating the filter chain to process the document and not before \
> > > showing the file dialog. So we need to transform the code for the \
> > > file dialog to use filter weights too. I suppose that both codes \
> > > could perhaps be merged as one but that is to be seen in details.)
> >
> > Merging the code is not really possible, IMHO. The two problems we have \
> > to solve are:
> > - Which mimetypes of the graph have a path to the target mimetype? (for \
> > the filter dialog box)
>
> But I proposed to do exactly this using the filter-weights as Nicolas \
> points out. Theoretically speaking; solving the this problem will still \
> lead to having paths between illogical nodes if you don't limit the \
> amount of hops it can take.
>
> > The two algorithms I implemented are a BFS on the graph with edges \
> > reversed (we are searching from the target mimetype towards the \
> > sources, i.e. in the "wrong" direction) and Dijkstra's shortest path \
> > algorithm (to determine the shortest path from S to T).
>
> The merging of code that Nicolas proposed seems to be about some \
> different parts then this though; but I don't know the code that well to \
> talk about it.
> --
> Thomas Zander
> -------------- next part --------------
> A non-text attachment was scrubbed...
> Name: not available
> Type: application/pgp-signature
> Size: 189 bytes
> Desc: not available
> Url : http://mail.kde.org/pipermail/koffice-devel/attachments/20041027/493db6f9/attachment-0001.pgp
>
> ------------------------------
>
> Message: 3
> Date: Wed, 27 Oct 2004 10:58:44 +0200
> From: Nicolas Goutte <nicolasg@snafu.de>
> Subject: Re: save a kword file as a spread sheet
> To: For developer's discussion about KOffice <koffice-devel@kde.org>
> Message-ID: <200410271058.44347.nicolasg@snafu.de>
> Content-Type: text/plain; charset="iso-8859-1"
>
> On Wednesday 27 October 2004 10:54, zander@kde.org wrote:
> > On Wed, Oct 27, 2004 at 10:41:56AM +0200, Werner Trobin wrote:
> > > On Wednesday 27 October 2004 10:20, Nicolas Goutte wrote:
> > > > On Wednesday 27 October 2004 09:11, Tomas Mecir wrote:
> > > > > On Tue, 26 Oct 2004 18:53:38 +0200, Nicolas Goutte
> > > > > <nicolasg@snafu.de>
> > > >
> > > > wrote:
> (...)
> > > The two algorithms I implemented are a BFS on the graph with edges
> > > reversed (we are searching from the target mimetype towards the \
> > > sources, i.e. in the "wrong" direction) and Dijkstra's shortest path \
> > > algorithm (to determine the shortest path from S to T).
> >
> > The merging of code that Nicolas proposed seems to be about some \
> > different parts then this though; but I don't know the code that well \
> > to talk about it.
>
> No, I meant these two code parts.
>
> Have a nice day!
>
> ------------------------------
>
> Message: 4
> Date: Wed, 27 Oct 2004 11:41:12 +0200
> From: Tomas Mecir <mecirt@gmail.com>
> Subject: Re: save a kword file as a spread sheet
> To: For developer's discussion about KOffice <koffice-devel@kde.org>
> Message-ID: <492258b1041027024121d6f448@mail.gmail.com>
> Content-Type: text/plain; charset=US-ASCII
>
> On Wed, 27 Oct 2004 10:54:28 +0200, Nicolas Goutte <nicolasg@snafu.de> \
> wrote:
> > Tomas' idea has the same problem. If we do not know the exact path \
> > before showing the dialog, we can still have absurd paths.
> >
> > (You must still allow KPresenter to KWord, even if there would be a \
> > filter chain like: KPresenter => Plain Text => KWord .)
>
> Okay, another variation of the same idea... Have a list of
> "problematic" mimetypes (either as an attribute of the filter that
> outputs to that mimetype, or even hard-coded somewhere - it's probably
> just text/plain and text/html so this shouldn't be an issue). Then,
> discard all filter chains such that they go through any of the
> problematic mimetypes, and there is some other way to go. For
> conversions such that there is no other way, append some warning text
> to the text shown in the fileformat combobox (e.g., in KWord, you'd
> see KSpread listed amongst the possible output formats, but it would
> show as "KSpread (using plain-text)", or something like that...
>
> Not perfect, I know, but if you want KPresenter => plaintext => KWord,
> but not KSpread => plaintext => KWord, then weights probably won't
> help you much either, as they would either discard both or none ...
>
> / Tomas
>
> ------------------------------
>
> Message: 5
> Date: Wed, 27 Oct 2004 11:46:56 +0200
> From: zander@kde.org
> Subject: Re: save a kword file as a spread sheet
> To: Tomas Mecir <mecirt@gmail.com>, For developer's discussion about
> KOffice <koffice-devel@kde.org>
> Message-ID: <20041027094656.GD5118@factotummedia.nl>
> Content-Type: text/plain; charset="us-ascii"
>
> On Wed, Oct 27, 2004 at 11:41:12AM +0200, Tomas Mecir wrote:
> > On Wed, 27 Oct 2004 10:54:28 +0200, Nicolas Goutte <nicolasg@snafu.de> \
> > wrote:
> > > Tomas' idea has the same problem. If we do not know the exact path \
> > > before showing the dialog, we can still have absurd paths.
> > >
> > > (You must still allow KPresenter to KWord, even if there would be a \
> > > filter chain like: KPresenter => Plain Text => KWord .)
> >
> > Okay, another variation of the same idea... Have a list of
> > "problematic" mimetypes (either as an attribute of the filter that
> > outputs to that mimetype, or even hard-coded somewhere - it's probably
> > just text/plain and text/html so this shouldn't be an issue). Then,
> > discard all filter chains such that they go through any of the
> > problematic mimetypes, and there is some other way to go. For
> > conversions such that there is no other way, append some warning text
> > to the text shown in the fileformat combobox (e.g., in KWord, you'd
> > see KSpread listed amongst the possible output formats, but it would
> > show as "KSpread (using plain-text)", or something like that...
>
> Adding a flag to one or two is just a subset of the proposal I already \
> gave with each conversion step taking a weight and your solution probably \
> needs about the same logic as my proposal making me vote for the full \
> solution.
> --
> Thomas Zander
> -------------- next part --------------
> A non-text attachment was scrubbed...
> Name: not available
> Type: application/pgp-signature
> Size: 189 bytes
> Desc: not available
> Url : http://mail.kde.org/pipermail/koffice-devel/attachments/20041027/e3c2c046/attachment-0001.pgp
>
> ------------------------------
>
> Message: 6
> Date: Wed, 27 Oct 2004 11:50:21 +0200
> From: David Faure <faure@kde.org>
> Subject: Re: save a kword file as a spread sheet
> To: For developer's discussion about KOffice <koffice-devel@kde.org>
> Message-ID: <200410271150.22150.faure@kde.org>
> Content-Type: text/plain; charset="iso-8859-1"
>
> On Wednesday 27 October 2004 11:41, Tomas Mecir wrote:
> > Not perfect, I know, but if you want KPresenter => plaintext => KWord,
> > but not KSpread => plaintext => KWord, then weights probably won't
> > help you much either, as they would either discard both or none ...
>
> Actually we don't want KPresenter -> plaintext -> kword, I wrote a real \
> kpr-to-kword converter...
> --
> David Faure, faure@kde.org, sponsored by Trolltech to work on KDE,
> Konqueror (http://www.konqueror.org), and KOffice \
> (http://www.koffice.org).
> ------------------------------
>
> _______________________________________________
> koffice-devel mailing list
> koffice-devel@kde.org
> https://mail.kde.org/mailman/listinfo/koffice-devel
>
> End of koffice-devel Digest, Vol 19, Issue 39
> *********************************************
>
_______________________________________________
koffice-devel mailing list
koffice-devel@kde.org
https://mail.kde.org/mailman/listinfo/koffice-devel
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic