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

List:       kde-commits
Subject:    Re: koffice/kword
From:       Kalle Dalheimer <kalle () dalheimer ! de>
Date:       1998-10-14 14:24:34
[Download RAW message or body]

Reginald Stadlbauer:
>Am Wed, 14 Oct 1998 schrieb Kalle Dalheimer: 
>>Reginald Stadlbauer: 
>>>I get a mail from somebody with some suggestions I implement that :-) But I'll 
>>>try to add a TODO. 
>>> 
>>>BTW: I'd need a fontdialog where you also can choose the font color and 
>>>subscript/superscript. Also a tab in the paragraph settings dialog would be 
>>>nice, where you can configure the borders of a paragraph. I know these are not 
>>>very interesting things, but I'll not do it in the next time :-) I'll also not 
>>>implement format filters, so everybody can do that :-) 
>> 
>>Count me in for the filter manager (partly done), the MIF import (partly done), 
>>Word 95 and SGML/DocBook. 
> 
>Very good :-))))) How does the filter manager work now? Are there external 
>filters, so that new ones can be easily added? And do the filters create the 
>internal document structure, or do they just create a XML file which is loaded 
>by the app then? 

What I have currently (but not very stable :-)) is that you can register a
filter with KFilterManager::registerFilter(), where you pass the name of the
filter (either a function pointer for built-in filters or the name of a shared
library), the filename extension, a string that names the format (like "MIF")
and whether it's an import or export filter. Currently, you have to register
all filters by hand, but it should also be possible that the filter manager
scans a directory for filters (like with Netscape plugins).

Then, there is KFilterManager::filterList() which returns a filter string to
put into a {Q,K}FileDialog, and KFilterManager::invokeFilter(). The filter then
reads the file and builds up an internal data structure. This internal data
structure is currently accessible via a global variable which is bad and should
(and will) be changed. It's then the task of the application (or rather an
additional filter component) to convert this data structure into the
application's native internal data structure. I have divided this so that you
can use the parser part of a filter for several applications.

Kalle

--
Kalle Dalheimer              Contract programming for Unix
kalle@dalheimer.de           Technical writing
kalle@kde.org                Technical editing
kalle@oreilly.de             KDE Developer (MFCH)
mdalheimer@acm.org           It's open, it's source, it runs - must be KDE!
	

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