Code and icon move to kdelibs and kdebase

Olaf Schmidt ojschmidt at kde.org
Wed Dec 15 22:32:26 GMT 2004


[Ismail Donmez, Mittwoch, 15. Dezember 2004 20:08]
> > kdenonbeta/kttsd/app-plugins/katepart-plugin and
> > kdenonbeta/kttsd/app-plugins/khtml-plugin
> > -> kdebase/konqueror/kttsplugin
>
> These should go to kdeaddons/kate and kdeaddons/konq-plugins
> respectively.
>

kdeaddons was also my first idea, but it has some disadvantages. The 
plug-ins are extremely small and don't have any functionality apart from 
doing a DCOP call to kttsd, and it seems strange for me to require people 
to install kdeaddons with all its dependencies only to let two 
applications talk to each other that are both located elsewhere.

The plug-ins don't have any linking dependency on kdeaccessibility, so 
technically, we could move them to kdebase. But I am not familiar with 
the build order in kdebase, so maybe kdeaddons makes more sense.

I don't mind moving them to kdeaddons if there is consensus to do this.

I forgot to mention the kate plug-ins, and of course the katepart-plugin 
has a dependency on kate (not konqueror). Sorry for the confusion. 
Because of a copy-and-paste error, the partpart plug-in still includes a 
khtmlpart header file but it doesn't really need it. 

So it might perhaps be possible to move
kdenonbeta/kttsd/app-plugins/katepart-plugin and 
kdenonbeta/kttsd/app-plugins/kate-plugin
to kdebase/kate/plugins/ktts

kdenonbeta/kttsd/app-plugins/khtml-plugin
to kdebase/konqueror/kttsplugin

(unless the decision is to move all of them to kdeaddons, of course)

Olaf

-- 
KDE Accessibility Project
-------------- 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/kde-core-devel/attachments/20041215/caee6f01/attachment.sig>


More information about the kde-core-devel mailing list