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

List:       kde-core-devel
Subject:    KPropsPage, KPropsDlg, KPropsDlgPlugin and friends
From:       Alex Zepeda <jazepeda () pacbell ! net>
Date:       2001-11-27 9:19:07
[Download RAW message or body]

Here's the thing.  I'm working a bit on fixing up the acl plugin for
kfile/konqy.  I'd like to have it only enabled where the object supports
ACLs (very easy to test for with a libc call).  Unfortunately property
page *plugins* can at best be bound merely to a mimetype.  Built in
property pages have a static function (class::Supports(Kfileitemlist))  
that can check what's appropiate.  I'd like to see this implemented in
KFile.  Probably some non name mangled function would work just fine.  
But the problem with this is that it requires a new API for the plugins
(does anyone actually use this interface?)... and would not make it a
candidate for 3.0.

Any thoughts?

As I'm about ready to send this message, it hits me.  Maybe tweaking the
desktop entry to have a new field (ExtendedConfiguration), that if set to
the string "true" the KFile classes would then pull the proper function,
give it the fileitems list and go from there.  If this option wasn't there
(the key), the classes would operate as they always have.

I'd really like to see something worked out for 3.0, as it would be nice
to stuff a few plugins throughout CVS.  Maybe a CVS (kdetoys), file flags
(kdebase, kdeutils), id3/ogg tag editor (kdemultimedia), NetWare/SMB
attribute (kdebase?  kdenetwork?) tweaker would be useful.  I miss these
things from Windows.

- alex

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