Image 01
profile-image

opq

Olivier poyen
Hi, I am opq and I create Various KDE 1.-4. Improvements.

Statistics

1 Products
6 Comments
Plinged 0 Products
Got 0
Has 0 Affiliates
Fan of 0 Products
Got 0 Fan-Likes
Last time active : Jul 28 2003
Joined : May 27 2003
EmbedKicker

Various KDE 1.-4. Improvements by opq 6 comments

It's a superkaramba theme, downloaded around here.

Quit nice. Kirby is moving around, changing form.

But the real reason it's here, is that my embed kicker applet can alos swallow superkaramba thing, so you can have kirby in kicker too. - Jul 28 2003
EmbedKicker

Various KDE 1.-4. Improvements by opq 6 comments

I know, I know. I'm fighting against that, but I don't known how to do it.
But, If you embed other stuff, I know you can click on them, do weird stuff, but I can't figure out, how to do the keyboard focus thing.

And also, I'm planning to add a little feature in order release the swallowed application

Thanks for the comment - Jul 28 2003
ULTIMATE KDE TAB FEATURES

Various KDE 1.-4. Improvements by WinterWolf 18 comments

True, but not in background by default, as you could in Galeon - May 28 2003
Scheduler for Superkaramba

Karamba & Superkaramba by trtmrt 34 comments

locals().update(globals()) create a local variable for each global one, with the same value.
Now, you can play with them.
But it does not have the same effect as:
global foo
which says "now treat foo as a global one".

So, you have to call the locals().update at the beginning of each function where you want to play with a lot of global

And at the end of your function, if you have made any change to the variable and you want to commit those changes into the global namspace, you have to use the other trick: globals().update.
This will create (or replace if they already exists) all the current local variables into the global namspace.

Note that, if you *only* need read access to a variable, you don't event have to say "global foo".
When python looks for a variable, if looks
1) in the local namaspace (ie in the current function)
2) in the global one
3) in the built-in namspace, a special one.


Here is a snippet of working code (pyhon 2.2):

>>>a=1
>>>def printA():
... #Read only. No ned for global
... print a
>>>printA()
-> 1
>>>def upodateA():
... locals().update(globals())
... a=2
... globals().update(locals())

>>>updateA()
>>>print a #at the interpreter prompt
-> 2

Now, if it still doesn't work; do you have any traceback, or just 'it's not working '?

Hope this helps - May 28 2003
Scheduler for Superkaramba

Karamba & Superkaramba by trtmrt 34 comments

For those of you who don't want to have that endless list of global foo at the beginnning of each function, you can do, at the beginning and the end of each karamba function:

def oneKarambaFunction():
#This take *all* globals
#into the local namespace
locals().update(globals())
#Useful stuff involving globals
......
.....

#And at the end
globals().update(locals)

The last step may not be necessary. But it is if you create any *new* variable you want to store.
This is not perfect programming style, but for those who use global scope, this may be a nice shortcut.

Hope this helps

- May 27 2003
ULTIMATE KDE TAB FEATURES

Various KDE 1.-4. Improvements by WinterWolf 18 comments

What about having background tab by default, or possibility to have them by default ? - May 27 2003