kpanelextension

[Aaron J. Seigo]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On May 23, 2002 12:06 pm, Aaron J. Seigo wrote:
> attached is the patch again KPanelExtension. thoughts? ideas? magic wand
> waving that will make this unecessary?

after thinking about it over an over-caffienated drink last night (20oz coffee 
with 8 shots of espresso .. mmmmmmmm), i figured out a way to do this w/out 
breaking BC or forcing extensions to support user-controlled resizing. all is 
happy in happy land again.

KPanelExtension does keep track of size settings in case they are there in the 
config file, but the extension can choose to pay attention to or ignore them. 
this way extensions that do support resizing can do so in a standardized way, 
without forcing it upon all extensions.

at the end of the day, it still relies on sizeHint() to get the size.

as for the kicker kcm, it knows which extensions support resizing and which 
don't (which is the default) by looking in their .desktop file (which it had 
to do to get their names anyway). and this is where i have some questions...

i've added the following to the kicker extension .desktop files as optional 
entries:

X-KDE-PanelExt-Resizeable=true
X-KDE-PanelExt-StdSizes=true
X-KDE-PanelExt-CustomMin=24
X-KDE-PanelExt-CustomMax=128

i'm not sure if the names i chose were appropriate since i've never had to add 
anything like this to .desktop files before. basically, they tell whether or 
not the extension is user resizeable, whether or not it accepts the 
"standard" sizes of Tiny / Small / Normal / Large and what (if any) custom 
size range it supports.

if CustomMin == CustomMax (or they are left out altogether) then the extension 
does support custom sizing.

this allows intelligent outside (read: from kcontrol) management of sizing..

is this OK, or should the .desktop file entries be changed to something else, 
or?

- -- 
Aaron J. Seigo
GPG Fingerprint: 8B8B 2209 0C6F 7C47 B1EA  EE75 D6B7 2EB1 A7F1 DB43
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (GNU/Linux)

iD8DBQE87uJP1rcusafx20MRAosnAKCih23J/10A1+Vp4SR6b/gAwlOIngCgh0ey
7i4B4V+yiOYcZbA6Hlfwth8=
=2uDo
-----END PGP SIGNATURE-----