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

List:       koffice-devel
Subject:    Re: [PATCH] kword spellchecking trouble
From:       Zack Rusin <zack () kde ! org>
Date:       2004-02-13 16:55:36
Message-ID: 200402131155.36969.zack () kde ! org
[Download RAW message or body]

On Friday 13 February 2004 11:28, David Faure wrote:
> > What would be a lot  
> > more helpful right now to me is having people try kspell2 and let
> > me know how the examples work for them. I'd also like to hear some
> > opinions on where individual files of kspell2 should go to, since
> > so far no one bothered to give it some thought.
>
> Please explain the problem :-)

kspell2 is :

non-gui files (core):
 - kspell_broker.* , kspell_dictionary.*, kspell_filter.*, 
kspell_client.*, kspell_config.*

plugins with a bunch of private files:
 - ispell,
 - aspell,

gui classes:
 - kspell_dialog.*, kspell_highlighter.*, and soon kspell_configwidget.*

Everything is lgpl. Initially I thought about :
- non-gui -> kdecore
- gui -> kdeui
- plugins -> kdelibs/kspell_plugins
But now I'm not sure if it makes sense to keep plugins in kdelibs like 
that, but without them kspell2 doesn't make any sense.
I also thought about having a a seperate kdelibs/kspell dir compiled 
after kdeui, with all those. Which would also allow me to use kconfig 
xt for the config classes.
And finally if we'll decide that kdelibs should stay unchanged then just 
replacing kospell with kspell2 is an option, but I'd prefer to have it 
available for all the apps and not only koffice.
I'm not sure what would be better. 

Zack

-- 
Why do they call it a "building"? It looks like they're finished. Why 
isn't it a "built"?
_______________________________________________
koffice-devel mailing list
koffice-devel@mail.kde.org
https://mail.kde.org/mailman/listinfo/koffice-devel

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