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

List:       koffice-devel
Subject:    Re: File filters status...
From:       Cyrille Berger <cberger () cberger ! net>
Date:       2009-01-19 16:14:29
Message-ID: 200901191714.29193.cberger () cberger ! net
[Download RAW message or body]

[Attachment #2 (multipart/alternative)]


On Monday 19 January 2009, David Faure wrote:
> Right now it may seem stupid, but if you look at it from a longer
> perspective, relying on the internals of the applications means that any
> refactoring breaks all filters. This has happened MANY times with the
> kspread csv filter for instance.
Except that sometime, the internals of an applications gives convenient way to 
manipulate the XML/Data (I wouldn't want to build by hand, for each krita 
filter, the layer stack ;) ). That said, libkoodf should give a good enough 
high level API for manipulating an odf file and transforming to/from it.

> Also, converting from file to file allows automating the conversion using
> koconverter, and allows chaining. Accessing application internals breaks
> all that.
how so ? if at the end the filter give something that can be saved ? (or 
something that is saved), it should still work right ?

-- 
Cyrille Berger

[Attachment #5 (text/html)]

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN" \
"http://www.w3.org/TR/REC-html40/strict.dtd"><html><head><meta name="qrichtext" \
content="1" /><style type="text/css">p, li { white-space: pre-wrap; \
}</style></head><body style=" font-family:'DejaVu Sans'; font-size:9pt; \
font-weight:400; font-style:normal;">On Monday 19 January 2009, David Faure \
wrote:<br> &gt; Right now it may seem stupid, but if you look at it from a longer<br>
&gt; perspective, relying on the internals of the applications means that any<br>
&gt; refactoring breaks all filters. This has happened MANY times with the<br>
&gt; kspread csv filter for instance.<br>
Except that sometime, the internals of an applications gives convenient way to \
manipulate the XML/Data (I wouldn't want to build by hand, for each krita filter, the \
layer stack ;) ). That said, libkoodf should give a good enough high level API for \
manipulating an odf file and transforming to/from it.<br> <p \
style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; margin-left:0px; \
margin-right:0px; -qt-block-indent:0; text-indent:0px; \
-qt-user-state:0;"><br></p>&gt; Also, converting from file to file allows automating \
the conversion using<br> &gt; koconverter, and allows chaining. Accessing application \
internals breaks<br> &gt; all that.<br>
how so ? if at the end the filter give something that can be saved ? (or something \
that is saved), it should still work right ?<br> <p style="-qt-paragraph-type:empty; \
margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; \
-qt-block-indent:0; text-indent:0px; -qt-user-state:0;"><br></p>-- <br> Cyrille \
Berger</p></body></html>



_______________________________________________
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