[14:28] hey all [15:20] hi doctormo! i have one development branch and a packaging branch on lp. for the first rev of the packaging branch, the reference to the devel branch is clear. [15:20] but now, several devel revs later, easiest would be to copy the files i need to the packaging branch. but is there a way to associate the packaging rev with a devel rev, then? [15:28] thorwil: Hey [15:29] thorwil: I don't understand, could you explain some more about what you mean? [15:29] doctormo: oh, and happy new year! :) [15:29] thorwil: Prosit Neujahr [15:30] heh, excellent! [15:30] doctormo: see https://launchpad.net/backtestground [15:30] doctormo: i created a packaging branch and continued development in trunk [15:31] doctormo: for the 2nd release (1st wasn't announced due to an error in it), i want to update the relevant files in packaging [15:32] Interesting, is this similar to my genetic background wallpaper packaging? [15:32] doctormo: now i wonder if there's a way to let LP know that the changes in packaging come from a specfic trunk revision [15:32] doctormo: not at all [15:33] doctormo: just scripts for cropping/resizing images to wallpaper resolutions, for making screenshots with transparent desktop [15:35] and as addition a script that expects a screenshot with transparent desktop to crop/resize it, repeating parts of any panel found to fill gaps [15:36] thorwil: Interesting set of scripts, so, do you need me to review? [15:38] doctormo: thanks, i don't need a review, but wouldn't mind feedback :) [15:38] the bin/__init__.py is redundant, [15:39] The commands are a bit cryptic, and sizes might clobber some other package by mistake. [15:39] ah right, just there for local convenience, shouldn't have checked that in [15:40] doctormo: unique but not cryptic names are hard to come up with [15:40] YHAFK [15:41] huh? [15:41] mm "yhafk" seems both unique and cryptic :) [15:42] So perhaps 'background-crop' 'background-extract' and 'background-sizes' [15:42] It's an old one 'YHAFK' == You have a full keyboard. [15:42] heh [15:42] :) [15:44] You can remove the sodipodi and inkscape namespaces from your svg template, they're not required. [15:44] 'as such' unless you want to take advantage of some editability in inkscape. [15:45] i vaguely recall that layers are not handled right in plain svg [15:46] thorwil: yep, layers are just groups, but you can keep that and not have the metadata, defs or sodipodi window frame guff. [15:49] * thorwil writes todo [15:50] thorwil: In the svg generation, try using printf syntax like so: http://pastebin.ca/2037733 [15:55] but of course! that really was a hack [16:01] Well I could claim printf is too since xml.minidom should be used instead ;-) [16:05] heh, sometimes treating xml as just text does make things simpler. at least if you start out having never messed with a structured xml representation [17:30] * thorwil pushes cleaned up svg_generator.py [18:30] doctormo: oh, and thanks! :) [18:30] np