rev 3009 - trunk/packages/kdeutils/debian/patches
Christopher Martin
chrsmrtn at costa.debian.org
Fri Jan 27 20:46:13 UTC 2006
Author: chrsmrtn
Date: 2006-01-27 20:46:07 +0000 (Fri, 27 Jan 2006)
New Revision: 3009
Added:
trunk/packages/kdeutils/debian/patches/01_kdeutils_branch_r502961.diff
Removed:
trunk/packages/kdeutils/debian/patches/01_kdeutils_branch_r484357.diff
trunk/packages/kdeutils/debian/patches/01_kdeutils_branch_r489522.diff
trunk/packages/kdeutils/debian/patches/01_kdeutils_branch_r495372.diff
Log:
New buildprep and remove old.
Deleted: trunk/packages/kdeutils/debian/patches/01_kdeutils_branch_r484357.diff
Deleted: trunk/packages/kdeutils/debian/patches/01_kdeutils_branch_r489522.diff
Deleted: trunk/packages/kdeutils/debian/patches/01_kdeutils_branch_r495372.diff
Added: trunk/packages/kdeutils/debian/patches/01_kdeutils_branch_r502961.diff
===================================================================
--- trunk/packages/kdeutils/debian/patches/01_kdeutils_branch_r502961.diff 2006-01-27 19:30:04 UTC (rev 3008)
+++ trunk/packages/kdeutils/debian/patches/01_kdeutils_branch_r502961.diff 2006-01-27 20:46:07 UTC (rev 3009)
@@ -0,0 +1,492 @@
+#DPATCHLEVEL=0
+--- superkaramba/examples/change_interval/interval.theme (.../tags/KDE/3.5.1/kdeutils) (revision 0)
++++ superkaramba/examples/change_interval/interval.theme (.../branches/KDE/3.5/kdeutils) (revision 502961)
+@@ -0,0 +1,2 @@
++KARAMBA x=200 y=100 w=300 h=40 INTERVAL=200 LOCKED=true
++TEXT x=0 y=0 w=300 h=20 value="wiggle the mouse over me" color=200,252,200
+--- superkaramba/examples/change_interval/interval.py (.../tags/KDE/3.5.1/kdeutils) (revision 0)
++++ superkaramba/examples/change_interval/interval.py (.../branches/KDE/3.5/kdeutils) (revision 502961)
+@@ -0,0 +1,60 @@
++#
++# Written by Luke Kenneth Casson Leighton <lkcl at lkcl.net>
++
++# This theme is demonstrates the interval timer changing.
++
++#this import statement allows access to the karamba functions
++import karamba
++
++seq = 0
++text = None
++
++#this is called when you widget is initialized
++def initWidget(widget):
++
++ karamba.redrawWidget(widget)
++
++# sequence drops down to zero and changes the time interval to 1 second.
++# keeps counting down thereafter...
++
++def widgetUpdated(widget):
++ global seq
++ global text
++
++ seq -= 1
++
++ if seq <= 0:
++ karamba.changeInterval(widget, 1000)
++
++ if seq <= 0:
++ message = "biding-time seq:%d" % -seq
++ else:
++ message = "wiggle seq:%d" % seq
++
++ # delete previous text if exists.
++ if text is not None:
++ karamba.deleteText(widget, text)
++
++ # display new message
++ text = karamba.createText(widget, 0, 20, 300, 20, message)
++ karamba.changeTextColor(widget, text, 252,252,252)
++
++ karamba.redrawWidget(widget)
++
++# wiggle the mouse over the widget to get the sequence number increased more.
++# also set the refresh rate to 50ms so that the theme has to fight against
++# the wiggling.
++
++def widgetMouseMoved(widget, x, y, button):
++ global seq
++
++ if seq <= 0:
++ seq = 0
++ karamba.changeInterval(widget, 50)
++
++ seq += 1
++
++
++# This will be printed when the widget loads.
++print "Loaded my python extension!"
++
+--- superkaramba/examples/setIncomingData/1.theme (.../tags/KDE/3.5.1/kdeutils) (revision 0)
++++ superkaramba/examples/setIncomingData/1.theme (.../branches/KDE/3.5/kdeutils) (revision 502961)
+@@ -0,0 +1,2 @@
++KARAMBA x=200 y=50 w=100 h=20 INTERVAL=1000 LOCKED=true
++TEXT x=0 Y=0 w=300 h=20 value="Click me!"
+--- superkaramba/examples/setIncomingData/2.theme (.../tags/KDE/3.5.1/kdeutils) (revision 0)
++++ superkaramba/examples/setIncomingData/2.theme (.../branches/KDE/3.5/kdeutils) (revision 502961)
+@@ -0,0 +1,2 @@
++KARAMBA x=200 y=100 w=300 h=40 INTERVAL=200 LOCKED=true
++TEXT x=0 y=0 w=300 h=20 value="you clicked on theme 1:"
+--- superkaramba/examples/setIncomingData/1.py (.../tags/KDE/3.5.1/kdeutils) (revision 0)
++++ superkaramba/examples/setIncomingData/1.py (.../branches/KDE/3.5/kdeutils) (revision 502961)
+@@ -0,0 +1,27 @@
++import karamba
++
++sequence_num = 0
++
++def initWidget(widget):
++ karamba.openTheme('2.theme')
++
++# pass over a sequence number as well - the reason is to
++# make it possible to identify the clicks uniquely.
++#
++# unfortunately, the recipient has to do "polling"
++# by calling getIncomingData - see 2.py for more info
++
++def widgetClicked(widget, x, y, button):
++
++ # do as you wish, but this is a good way:
++ # compact your stuff with repr() it can cope
++ # with pretty much any basic types - dictionaries, lists -
++ # and then use eval() at the other end.
++
++ global sequence_num
++ sequence_num += 1
++
++ vars = (sequence_num, x, y, button)
++ message = repr(vars)
++ karamba.setIncomingData(widget, "2", message)
++
+--- superkaramba/examples/setIncomingData/2.py (.../tags/KDE/3.5.1/kdeutils) (revision 0)
++++ superkaramba/examples/setIncomingData/2.py (.../branches/KDE/3.5/kdeutils) (revision 502961)
+@@ -0,0 +1,78 @@
++#
++# Written by Luke Kenneth Casson Leighton <lkcl at lkcl.net>
++
++# This theme is demonstrates how to
++
++#this import statement allows access to the karamba functions
++import karamba
++
++drop_txt = None
++
++#this is called when you widget is initialized
++def initWidget(widget):
++
++ # this resets the text to "" so we know we've never
++ # received anything yet from the other theme
++ name = karamba.getPrettyThemeName(widget)
++ print "2.py name: ", name
++ karamba.setIncomingData(widget, name, "")
++
++ karamba.redrawWidget(widget)
++
++# this is a pain. in order to avoid memory-related threading problems,
++# and also locking, with the communication between themes, the
++# communication is done asynchronously. so you have to POLL for the
++# information, by reading getIncomingData().
++#
++# therefore, you must set an interval=time_in_ms in your receiving .theme
++# file (see 2.theme) and then call getIncomingData() in here.
++#
++# it's not ideal - but it works.
++#
++# NOTE: the data received - by getIncomingData - is NOT, i repeat NOT
++# deleted when you call getIncomingData.
++# so, obviously, you need to take care to not activate repeatedly.
++# you could do this in several ways. one of them is to send, in
++# the calling theme (the one that calls setIncomingData) a sequential
++# number as part of the message.
++#
++# alternatively, you could reset the text to "" (see above)
++
++
++expected_seq = 0
++
++def widgetUpdated(widget):
++
++ global expected_seq # i hate globals. please write better code than this example.
++
++ # get the "message"...
++ disp = karamba.getIncomingData(widget)
++ if disp == "":
++ return
++
++ # decode it...
++ (seq, x, y, button) = eval(disp)
++
++ # if it's been seen before, skip it...
++ if seq <= expected_seq:
++ pass
++
++ expected_seq += 1
++
++ message = "seq:%d x:%d y:%d btn:%d" % (seq, x, y, button)
++ # delete previous text if exists.
++ global drop_txt
++ if drop_txt is not None:
++ karamba.deleteText(widget, drop_txt)
++
++ # display it...
++ drop_txt = karamba.createText(widget, 0, 20, 300, 20, message)
++ karamba.changeTextColor(widget, drop_txt, 252,252,252)
++
++ karamba.redrawWidget(widget)
++
++ pass
++
++# This will be printed when the widget loads.
++print "Loaded my python 2.py extension!"
++
+--- superkaramba/examples/service_group/service_group.py (.../tags/KDE/3.5.1/kdeutils) (revision 0)
++++ superkaramba/examples/service_group/service_group.py (.../branches/KDE/3.5/kdeutils) (revision 502961)
+@@ -0,0 +1,143 @@
++# Service Groups demo
++# Written by Luke Kenneth Casson Leighton <lkcl at lkcl.net>
++
++# This theme is demonstrates how to parse service groups.
++# it's done recursively to give a complete dump of your menu
++# that you will also be able to double-check against kmenuedit
++# and also the KDE Start button.
++#
++# for a real-live usage, see kroller.sez (try searching kde-look.org),
++# which fires off a sub-theme with the service-group menu options when
++# you click on a service group on the "main" bar.
++
++#this import statement allows access to the karamba functions
++import karamba
++
++# simple function to display
++
++def create_text(widget, line, depth, disp, name=None, command=None, icon=None):
++
++ x = depth*30
++ y = line*7
++ width = 400
++ height = 8
++ drop_txt = karamba.createText(widget, x, y, width, height, disp)
++ karamba.changeTextSize(widget, drop_txt, 7)
++ karamba.changeTextColor(widget, drop_txt, 252,252,252)
++
++ # create a (very narrow! only an 8-pixel-high area!)
++ # service click area to demonstrate that commands get
++ # executed correctly.
++
++ if name:
++ karamba.createServiceClickArea( widget,
++ x,y,width,height,
++ name, command, icon)
++
++
++# okay. you really should be looking up the KDE Developer documentation
++# on service groups. here is a _brief_ explanation of what they contain.
++#
++# getServiceGroups returns a list of menu options.
++# you can either have a subgroup, or you can have an executable program.
++# if a list item is a subgroup, then (0, dict) is returned, where
++# dict is a dictionary containing information describing the subgroup.
++# if a list item is an executable menu option, then (1, dict) is returned,
++# where dict is a dictionary containing information describing the menu option.
++#
++# the information (keys in the dictionary) returned about a subgroup comprises:
++# relpath - the fully qualified path of that subgroup, and
++# calling getServiceGroups (again) with that path will get
++# you all of the menu options in that subgroup, hurrah.
++# icon - the name of an icon (a png, usually) which you can, if you
++# so wish, use as the filename argument to createImage().
++# caption - i get confused as to which is which, but
++# and you can always run this program in combination
++# comment with kmenuedit to find out!
++#
++# the information (keys in the dictionary) returned about an
++# executable option comprises:
++# exec - obviously the most important bit: the name of the command
++# to be executed.
++# icon - the filename of the icon (usually a png) which should be
++# displayed for this command.
++# name - not to be confused with genericname, neither of which i
++# am sure about, and if you really want to know, run
++# kmenuedit and experiment, or look at the KDE Developer source
++# code.
++# menuid - don't know what it is for. it's just... there.
++#
++# how to use the service group info:
++#
++# the simplest way to get commands actually executed is to hand
++# over the name, the command and the icon filename to a
++# ServiceClickArea (karamba.createServiceClickArea()).
++#
++# other than making sure that you put the service click area in
++# the right place, you don't have to worry about much else.
++#
++# or, you could always run it manually, yourself, by using
++# karamba.Run(name, command, icon). personally, i prefer
++# the service click areas. no, karamba.Run() is not like
++# karamba.execute() - if you use karamba.Run() you get to say which
++# bouncing icon is used, whereas if you use karamba.execute() you
++# always get a superkaramba bouncing icon...
++#
++# do look out for kroller.sez on http://kde-look.org or other locations
++# for a more complex and comprehensive usage of service groups.
++
++def display_svc_group(widget, rel_path, line, depth):
++
++ grps = karamba.getServiceGroups(rel_path)
++
++ for (type, d) in grps:
++
++ if type is 0:
++
++ # it's a
++
++ sub_relpath = d['relpath']
++ icon = d.get('icon', 'unknown')
++ caption = d.get('caption', None)
++ comment = d.get('comment', None)
++ cmt = ''
++
++ # get at least something to display
++ if comment:
++ cmt = comment
++ elif caption:
++ cmt = caption
++
++ msg = "SVCGRP: %s %s" % (icon, cmt)
++ create_text(widget, line, depth, msg)
++ line += 1
++ line = display_svc_group(widget, sub_relpath,
++ line, depth+1)
++
++ elif type is 1 and d.has_key('menuid'):
++
++ relpath = d.get('relpath', '')
++ cmd = d['exec']
++ icon = d.get('icon', 'unknown')
++ name = d.get('name', None)
++ genericname = d.get('genericname', None)
++ cmt = ''
++
++ # get at least something to display
++ if genericname:
++ cmt = genericname
++ elif name:
++ cmt = name
++
++ msg = "%s %s %s" % (cmd, icon, cmt)
++ create_text(widget, line, depth, msg, name, cmd, icon)
++ line += 1
++
++ return line
++
++#this is called when you widget is initialized
++def initWidget(widget):
++
++ display_svc_group(widget, "", 0, 0)
++ karamba.redrawWidget(widget)
++
+--- superkaramba/examples/service_group/service_group.theme (.../tags/KDE/3.5.1/kdeutils) (revision 0)
++++ superkaramba/examples/service_group/service_group.theme (.../branches/KDE/3.5/kdeutils) (revision 502961)
+@@ -0,0 +1,4 @@
++# simple test of service group stuff. displays your kde menu.
++
++karamba x=0 y=0 w=600 h=800 locked=true
++
+--- superkaramba/examples/mouseDrop/mousedrop.py (.../tags/KDE/3.5.1/kdeutils) (revision 0)
++++ superkaramba/examples/mouseDrop/mousedrop.py (.../branches/KDE/3.5/kdeutils) (revision 502961)
+@@ -0,0 +1,138 @@
++# Drop Detect
++# Written by Luke Kenneth Casson Leighton <lkcl at lkcl.net>
++
++# This theme is demonstrates how to
++
++#this import statement allows access to the karamba functions
++import karamba
++
++drop_txt = None
++
++#this is called when you widget is initialized
++def initWidget(widget):
++
++ karamba.acceptDrops(widget)
++ karamba.redrawWidget(widget)
++
++#this is called everytime your widget is updated
++#the update inverval is specified in the .theme file
++def widgetUpdated(widget):
++ pass
++
++#This gets called everytime our widget is clicked.
++#Notes:
++# widget = reference to our widget
++# x = x position (relative to our widget)
++# y = y position (relative to our widget)
++# botton = button clicked:
++# 1 = Left Mouse Button
++# 2 = Middle Mouse Button
++# 3 = Right Mouse Button, but this will never happen
++# because the right mouse button brings up the
++# Karamba menu.
++# 4,5 = Scroll wheel up and down
++def widgetClicked(widget, x, y, button):
++ pass
++
++#This gets called everytime our widget is clicked.
++#Notes
++# widget = reference to our widget
++# x = x position (relative to our widget)
++# y = y position (relative to our widget)
++# botton = button being held:
++# 0 = No Mouse Button
++# 1 = Left Mouse Button
++# 2 = Middle Mouse Button
++# 3 = Right Mouse Button, but this will never happen
++# because the right mouse button brings up the
++# Karamba menu.
++def widgetMouseMoved(widget, x, y, button):
++ pass
++
++#This gets called when an item is clicked in a popup menu you have created.
++# menu = a reference to the menu
++# id = the number of the item that was clicked.
++def menuItemClicked(widget, menu, id):
++ pass
++
++#This gets called when an item is clicked in the theme CONFIGURATION menu,
++#not the popup menus that you create.
++# key = the reference to the configuration key that was changed
++# value = the new value (true or false) that was selected
++def menuOptionChanged(widget, key, value):
++ pass
++
++#This gets called when a meter (image, text, etc) is clicked.
++# NOTE you must use attachClickArea() to make a meter
++# clickable.
++# widget = reference to your theme
++# meter = the meter clicked
++# button = the button clicked (see widgetClicked for button numbers)
++def meterClicked(widget, meter, button):
++ pass
++
++#This gets called when a command you have executed with executeInteractive() outputs something
++#to stdout. This way you can get the output of for example kdialog without freezing up the widget
++#waiting for kdialog to end.
++# widget = reference to your theme
++# pid = process number of the program outputting (use this if you execute more than out process)
++# output = the text the program outputted to stdout
++def commandOutput(widget, pid, output):
++ pass
++
++#This gets called when an item is dropped on this widget.
++# NOTE you have to call acceptDrops() before your widget will accept drops.
++# widget = reference to your theme
++# dropText = the text of the dropped item (probably a URL to it's location in KDE)
++# x and y are coordinates of mouse where the drop occurred.
++# this you can use to e.g. detect which icon or object in your
++# theme that someone wants to "receive" the icon you were dragging
++def itemDropped(widget, dropText, x, y):
++ global drop_txt
++ # delete previous text if exists.
++ if drop_txt is not None:
++ karamba.deleteText(widget, drop_txt)
++
++ disp = "x:%d y:%d command: %s" % (x, y, dropText)
++ drop_txt = karamba.createText(widget, 10, 40, 500, 20, disp)
++ karamba.changeTextColor(widget, drop_txt, 252,252,252)
++
++ karamba.redrawWidget(widget)
++
++#This gets called when a new program is LOADING in KDE. When it is done
++#loading, startupRemoved() is called, followed by taskAdded().
++# widget = reference to your widget
++# task = A refence to the task that is starting.
++def startupAdded(widget, startup):
++ pass
++
++#This gets called when a new program is done LOADING in KDE.
++# widget = reference to your widget
++# task = A refence to the task that just finished loading.
++def startupRemoved(widget, startup):
++ pass
++
++#This is called every time a new task (program) is started in KDE.
++# widget = reference to your widget
++# task = A refence to the new task. Call getTaskInfo() with this reference
++# to get the name, etc of this new task.
++def taskAdded(widget, task):
++ pass
++
++#This is called everytime a task (program) is closed in KDE.
++# widget = reference to your widget
++# task = A refence to the task.
++def taskRemoved(widget, task):
++ pass
++
++#This is called everytime a different task gains focus (IE, the user clicks
++#on a different window).
++# widget = reference to your widget
++# task = A refence to the task. Call getTaskInfo() with this reference
++# to get the name, etc of this new task.
++def activeTaskChanged(widget, task):
++ pass
++
++# This will be printed when the widget loads.
++print "Loaded my python extension!"
++
+--- superkaramba/examples/mouseDrop/mousedrop.theme (.../tags/KDE/3.5.1/kdeutils) (revision 0)
++++ superkaramba/examples/mouseDrop/mousedrop.theme (.../branches/KDE/3.5/kdeutils) (revision 502961)
+@@ -0,0 +1,5 @@
++# simple test of drop receipt, including location.
++
++karamba x=0 y=0 w=600 h=140 locked=true color=0,50,0
++text x=10 y=10 value="Drag a desktop icon on me and i will tell you where" color=252,252,252 fontsize=12 font="sans"
++
More information about the pkg-kde-commits
mailing list