Re: gSoC ideas?

Robert Knight wrote:
> Actually, come to think of it, I believe OpenOffice has
command-line
> tools to do Microsoft Office -> ODF ( and vice versa
) conversion.
> Providing access to this from within KOffice would be
useful.

While I wrote before some dirty words about the only partly

working "Open"XML=>_Open_Document hack, I
deleted it to prevent to much bad 
impressions and try to extract the essential question out of
it;

Is it a KOffice-project? I mean, I see there the case to get
mono started from 
within a filter + pass the "Open"XML-filter to it
+ fetch the result and pass 
it on to KWord, but I really fail to see how this could fit
into a 2 month 
project and how it actualy could work / be useful for users
without starting 
to actualy hack on the C#-code to get the import (imho the
most if not only 
interesting part) working. If the result are hacks on the
C#-code, then I 
really fail to see how this could be related to KOffice.

Sorry for that hard personal view, but from following the
last few months of 
developing on those codebase I am lost with a "ah, some
code to let OOo 
depend on mono" and "let's finally push our own
OOo-with-mono fork" feeling 
here :-(

-- 
Sebastian Sauer aka dipesh[sebsauer]
http://www.dipe.or
g/public_key.asc
Fingerprint: 8F1E 219B 16E6 4EC7 29CC F408 E193 65E2 9134
2221
Coder in http://www.koffice.org
&& http://www.kmldonkey.org

_______________________________________________
koffice-devel mailing list
koffice-develkde.org
h
ttps://mail.kde.org/mailman/listinfo/koffice-devel

Sebastian, I think I may have missed some earlier
discussion.  What
does OO.org have to do with mono?
What I had in mind was somewhat simpler:

1.  User selects file in unsupported format.
2.  KOffice offers to use a 3rd party tool to produce an ODF
document
3.  KOffice runs that tool in the background and loads the
ODF
document when finished.

Where "3rd party tool" is a simple command-line
program with syntax such as:

ooconvert -i input.docx -o output.odf

All KOffice needs to know is:
1.  Name of the 3rd party tool
2.  What formats the tool is expected to be able to handle
3.  Syntax for running the tool ( probably a string in the
format
"%NAME% -i %INPUTFILE% -o %OUTPUTFILE%" for
example )
4.  Name of the generated ODF file given the input
filename.

The process for saving the document would be similar.  Save
as ODF by
default and provide easy access to 3rd party tool to do the
conversion
to a different format.

No linking with additional external libraries, no code
dependencies on
anything outside of KOffice.  Quite do-able in a couple of
months I
should think, IF (and this is a big IF) the 3rd party tools
exist or
are simple to create.

Regards,
Robert.

On 08/03/07, Sebastian Sauer <maildipe.org> wrote:
> Robert Knight wrote:
> > Actually, come to think of it, I believe
OpenOffice has command-line
> > tools to do Microsoft Office -> ODF ( and vice
versa ) conversion.
> > Providing access to this from within KOffice would
be useful.
>
> While I wrote before some dirty words about the only
partly
> working "Open"XML=>_Open_Document hack, I
deleted it to prevent to much bad
> impressions and try to extract the essential question
out of it;
>
> Is it a KOffice-project? I mean, I see there the case
to get mono started from
> within a filter + pass the "Open"XML-filter
to it + fetch the result and pass
> it on to KWord, but I really fail to see how this could
fit into a 2 month
> project and how it actualy could work / be useful for
users without starting
> to actualy hack on the C#-code to get the import (imho
the most if not only
> interesting part) working. If the result are hacks on
the C#-code, then I
> really fail to see how this could be related to
KOffice.
>
> Sorry for that hard personal view, but from following
the last few months of
> developing on those codebase I am lost with a "ah,
some code to let OOo
> depend on mono" and "let's finally push our
own OOo-with-mono fork" feeling
> here :-(
>
> --
> Sebastian Sauer aka dipesh[sebsauer]
> http://www.dipe.or
g/public_key.asc
> Fingerprint: 8F1E 219B 16E6 4EC7 29CC F408 E193 65E2
9134 2221
> Coder in http://www.koffice.org
&& http://www.kmldonkey.org

> _______________________________________________
> koffice-devel mailing list
> koffice-develkde.org
> h
ttps://mail.kde.org/mailman/listinfo/koffice-devel
>
_______________________________________________
koffice-devel mailing list
koffice-develkde.org
h
ttps://mail.kde.org/mailman/listinfo/koffice-devel