[00:01] buss daemon: http://paste.ubuntu.com/845168/ and buss.lens http://paste.ubuntu.com/845171/ [00:06] "NÃ¥r gÃ¥r bussen.." (I have an utf-8 bug in my term) [00:08] malin, there is a problem in your .lens file : Name and Icon need to be capitalized. [00:08] Name=Buss [00:08] Icon=/usr/share/unity/5/buss.svg [00:08] davidcalle: ah, but it works for me, but i could remove the norwegian letters [00:09] malin, it was working when I tried it the first time. It's just now, a crash that has messed up my utf8 :) [00:09] hey [00:09] unity [00:10] oh [00:10] how wonderus it is [00:10] im so glad i stuck around [00:10] i knew it would pay off [00:10] davidcalle: so net.buss.lens.buss should be: Net.Buss.Lens.Buss ? and in the icon-file should change from buss.svg to Buss.svg ? [00:10] or is it icon to ICon [00:10] ah, that what it is. I see [00:11] malin, nope, just "name" to "Name" and "icon" to Icon" [00:12] davidcalle: okey [00:12] and the daemon-file is okey as it is? I get the norwegian letters in my terminal [00:14] malin, looks fine, you can remove the "_m = dir(Dee.SequenceModel)" [00:14] holy sh....t it it it.. I can't belive it.. I see an icon in the dash [00:15] I dreamd of it last night [00:15] :) [00:15] so that line is just to be removed :) okey [00:15] yeah [00:16] it just dosen't print anything to the dash [00:16] but this was a huge step forward [00:16] malin, indeed [00:17] it prints to the terminal [00:17] but not in the dash :) hehe [00:18] malin, I got to go, ping me tomorrow if you need some more help. Good night ;) [00:18] thank you so much for helping me out the evening [00:19] I think I need more help and maybe tomorro :) [00:19] have a good night :) [00:19] No problem! [00:19] :) [01:16] is there any standard or convention that should be followed when choosing a dbus name/path for a Lens or Scope? [01:27] bschaefer: ping? [01:36] hey thomi [01:37] hi - there's a new version of by ibus testing branch, with several more tests.. I wonder if you're willing to try them out at some point? [01:37] yes i can! [01:37] ill pull the changes and let you know [01:37] sweet - we're missing a bit of introspection inside unity to complete the tests (ideally we'd verify that the correct apps show up in the results)... [01:38] for e.g.- when you search 'photo' (but in chinese) you should see shotwell [01:38] also, apparently this should work no matter what locale you have set locally. [01:38] o yes, testing the CJK parsing through xapian [01:38] yup :) [01:38] coolio [01:39] that is also something I worked on haha [01:39] keep me posted if anything interesting happens OK? :) [01:39] will do! Should be able to do in a couple min [01:45] thomi, everything worked except cipan guanli [01:45] it was in english [01:45] though my compiz freaked out [01:45] hmmm [01:45] try it again maybe? [01:46] compiz freaking out isn't a good sign ; [01:46] ) [01:46] im doing it, and yeah the only one not in chinese is "cipan guanli" [01:46] but im using a different TextEntry [01:47] like im moving the ibus support form unity to nux and these changes should be coming in by the end of the week [01:47] though im not sure how that would effect the test... [01:47] thomi, nevermind it worked :) [01:47] sweet [01:48] a big thing we will need to add test for is ibus-hangul [01:48] hangul? [01:48] and making sure the space gets committed correctly, but Ill talk to you about it when the code langs [01:48] hangul = korean [01:51] bschaefer: ahh, ok [01:51] well, if we have good test data the tests should be trivial to write [01:52] thomi, but awesome work! The test will be very to easy to write now! [01:52] thomi, also for pinyin we can test tab, the arrow keys [01:52] I'm not very happy about the way we initialise the engine, it seems a bit cludgy, but it seems to work anyway [01:52] they change pages on the popup box [01:53] thomi, yeah, I need to take a better look into it! [01:53] ahhh, ok [01:53] well, it's probably not worth spending much time on right now [01:53] yeah, soon though! [01:54] thomi, as I have to dig through ibus's source files for the python apo [01:54] and the online version isn't very helpful with set_value and get_value (which I think we will need to use more of) [01:54] bschaefer: ahhh.. what are you looking for? [01:55] thomi, well right now I want to be able to get inactive engines and set them as active, so we dont ever have to open up "ibus-setup" [01:55] bschaefer: I do that in my code [01:55] check out autopilot/emulators/ibus.py [01:55] thomi, well I need to dig through your code! [01:56] well, I can return both a list of active and inactive engines [01:56] yeah [01:56] I *think* I know how to make an engine active.... with a bit of digging [01:56] but when I tried setting the inactive ones using set_gloabl_engines I was getting a runtime error === Jens is now known as Guest41607 [01:56] hmm, [01:56] OK, I'll look into that [01:56] saying it wasn't active [01:57] but! A good place to look is [01:57] ibus/setup [01:57] if you download the source [01:57] as it has that entire "ibus-setup" source code which is doing that when you hit the add key [01:57] Im just not as good as reading python code ;) [01:59] thomi, DBusException: org.freedesktop.DBus.Error.Failed: Can not find engine pinyin. [01:59] is what that test does when you remove pinyin from "ibus-setup" [01:59] under the active list [01:59] thomi, thats why I just used the active list cause I couldn't find how to add them :( [02:00] ahh, ok [02:00] Yeah, I was trying to read the src for ibus-setup yesterday. [02:00] sorry I should have said that [02:01] it's not that python code's hard to read, it's that *that* python code is hard to read ;) [02:01] haha that is what I was thinking [02:01] so I need to figure out how the add is working [02:02] what ill do is start tinkering with the add code and start commenting stuff out until I break it haha [02:02] ill try to do that this weekend or next week :) [02:02] thomi, we also have some test from nux coming in to cover a lot of this too! [02:03] cool [02:13] whoever came up with the pressure reveal [02:14] is a friggin genius [02:16] seriously [02:50] thumper, hey, do you have a sec? An update on ibus stuff [02:50] bschaefer: I'm just about to head into town to buy a new toaster :) [02:50] bschaefer: whazzup? [02:50] thumper, awesome! I need to get one...haha [02:50] so right now [02:50] the ibus works 100% in the Hud [02:51] but for some reason in the dash it seems to lose the popup box sometimes [02:51] hmm [02:51] when you have multiple windows, and the cursor is not correct [02:51] there is a bit of code somewhere that is stealing focus [02:51] which the hud is being super careful of [02:51] so that may be the difference there [02:52] yeah, I was also look at this over OverlayRenderer [02:52] which the Hud uses and not Dash [02:53] but thats good to know; but what is nice is everything is working correctly for ibus ;) [02:53] nux wise [02:53] and copy/cut/paste still works until we get that into nux [02:54] so all I have to do is figure out who is stealing focus, and or why the dash isn't rendering the box correctly [02:54] cool [02:54] awesome to hear [02:54] * thumper away for a bit [02:54] and we will have a solid release :) [02:54] good luck getting the right toaster! [05:23] I'm not very clear on HUD's development. Will the code be merged with Unity? If so, does anybody know when? [05:28] Won't it be merged with Trunk? [07:48] mhall119: morning :-)! [07:49] mhall119: please help with my lens: ./cooking-lens File "./cooking-lens", line 41 filters = [] ^ IndentationError: unexpected indent [07:49] mhall119: what do I have to import, and how? === philipballew is now known as philipballew_ === philipballew_ is now known as philipballew [08:00] Aha! with HUD one cannot do Alt+PrintScreen [08:00] because this combination only works (for some reason) when alt is depressed === david is now known as davidcalle [08:15] gotwig, re: IndentationError - it means that the code is not indented properly, i.e. not enough or more than needed spaces at the line indicated [08:20] didrocks, hello. Just so you know, MIR accepted on the video lens and scope. [08:20] davidcalle: woow! I'll make unity recommends it [08:21] rye: what you mean [08:21] gotwig, your message to mhall119 [08:22] didrocks, thanks :) [08:23] rye: yes, but I still dont understand it... [08:24] gotwig, in python, there are no block delimiters, could you please pastebin the code so that I could tell what's wrong? [08:24] rye: yes [08:26] gotwig, have you programmed earlier in any other language? [08:27] rye: I am still programming in other languages [08:27] rye: Java [08:27] rye: I am still a student :X [08:27] gotwig, ah, then the habit of indentation vs blocks will kick in... It took a while for me - i migrated from Perl :) [08:28] http://paste.ubuntu.com/845480/ [08:28] rye: hm, I just wanna do this lens/scope I've been working for it so long [08:28] rye: I have to cancel developing it today I think [08:29] rye: for longer time, becouse I won't have the time in future.. [08:29] gotwig, ah, the whole code is not indented correctly [08:29] rye: so how may I do it ^^? [08:29] rye: I tried to merge something from original Python code for lenses with code from singlet library [08:29] gotwig, give me a minute [08:29] rye: wanna see the scope for it? [08:30] rye: I think I will commit it to my bzr branch... wait [08:32] gotwig, quick hint - it's recipes, not recips [08:32] gotwig, and another question - where did you get the boilerplate code from? [08:33] rye: from the python example for lens and scopes ( that simple lens, and wikipedia scope) , and from a singlet example [08:34] rye: I dont realy know how to do it it with singlet [08:35] gotwig, do you have the link to that wikipedia scope? [08:35] rye: wait [08:35] rye, https://code.launchpad.net/~unity-team/unity-lens-sample/python-5.0 [08:36] rye: and why for the scope? === alan_g is now known as alan_g|afk [08:38] rye: thats the code for my scope : http://paste.ubuntu.com/845492/ [08:39] rye: the bus names are different, right? [08:40] gotwig, hm, I think you have mixed singlet and sample which are not directly compatible in the lens, the scope you pasted is ok [08:40] davidcalle, thanks! [08:40] rye: :D juhu , I worked long on the scope [08:41] rye: just began to work on a lens [08:41] rye: can you help me? [08:41] rye: I dont know if I should choose singlet or the normal python gobject code [08:42] gotwig, let me try to run the example lens first (i always wanted to see how it works :) [08:44] erm, is unity supposed to crash when i run setsid [08:48] rye: could be, just restart all, than run the lens, than run the scope [08:50] tsdgeos, you said you can have VBox with multiple screens, anywhere I can read on that? [08:50] Saviq: Gerry said it, i tried, failed miserably [08:50] oh [08:50] Saviq: basically in the settings of the VM there is a "Screens" setting [08:50] you can set it to two there [08:50] but the inner VM never detected 2 [08:51] even if i had "two" virtualBox screens [08:51] tsdgeos, ah :/ [08:51] Saviq: but give it a try, it's like 5 sec to try :D [08:51] doing that now [08:51] so it requires to go fullscreen then [08:52] does it? [08:52] it didn't here [08:52] maybe that is what broke :D [08:53] stoopid [08:53] it complained about only one screen being connected [08:53] just to open two windows on one screen when I connected the second one [08:55] Saviq: lol [08:56] tsdgeos, well, seems to work, kind of [08:56] Saviq: did you have to disconnect the second real screen? [08:57] tsdgeos, no [08:57] did you have to go fullscreen? [08:57] no [08:58] tsdgeos, but it helps a lot with the perception of it [08:58] tsdgeos, I could have two small windows next to each other that worked fine [08:59] :-/ [08:59] tsdgeos, when I switched to fullscreen [08:59] i mean :-/ it doesn't work for me :D [08:59] morning [08:59] tsdgeos, each of them fullscreened on two separate screens [08:59] tsdgeos, and then I had to tweak the displays _inside_ the vm [08:59] i.e. xrandr [08:59] 'cause they cloned instead of being left/right [09:00] xrandr does not recognize two displays here [09:00] Saviq: which driver are you using inside the VM ? [09:01] tsdgeos, vboxvideo [09:01] tsdgeos, although I might be using the non-OSE version [09:02] let me check [09:02] yeah virtualbox-4.1-4.1.8-75467~Ubuntu~oneiric [09:02] aaaah [09:02] i'm usign the vesa_Drv [09:02] well [09:02] no vboxvideo driver here [09:03] that explains stuff [09:03] tsdgeos, you need to install the additions [09:03] i tried [09:03] something failed [09:03] let me check again [09:03] well, jockey should tell you to do so === alan_g|afk is now known as alan_g [09:03] rye: ok, I changed many things [09:03] rye: now I only have problems with dbus [09:04] rye: http://paste.ubuntu.com/845514/ [09:04] rye: afk for 20 min's :-) [09:05] erm, Am i correct that the wikipedia.scope and sample.lens are completely unrelated? [09:05] gotwig, you still have the dbus bus name from the example [09:05] installing the guest additions fails to compile utils.c [09:06] rye: so where do I have to change it [09:06] rye, the sample lens can host any kind of scope. The wikipedia scope is to be considered also as a sample scope. They are here for learning purposes. [09:06] rye: should I commit it to my bzr, so you can see all files? [09:08] otoh using jockie seems to have worked [09:09] cool [09:15] dont know why [09:15] but bzr sucks [09:15] why do I have merge problems, if this is my 2.th commit o.0? an my first commit is totaly empty? [09:15] tsdgeos, looking at the mm stuff... have you considered the HUD at all? [09:15] tsdgeos, it's the exact same case as with the Dash [09:16] not yet [09:16] is the hud merged already? [09:16] no, but just wanted to know whether you guys have in mind that we might have more than just one component to be moved around [09:16] probably the same for the shortcuts overlay? [09:16] yeah [09:16] or shortcut overlay has to show on all screens? [09:16] no, I don't think so [09:17] hud should be merged soon, as in maybe even today [09:17] added to the todo list [09:17] so we don't forget about it [09:20] tsdgeos, I tested out your move-dash branch quickly, seems to work nicely :) [09:20] cool [09:20] except for the second shell being positioned wrong [09:20] lots of headaches not to lose focus and stuff [09:20] Saviq: hide-mode 0 ? [09:21] yes [09:21] try hide-mode 1 :D [09:21] ;) [09:21] working on that as we speak [09:22] oh forrgot bzr remove [09:22] tsdgeos, yeah I saw yesterday that you had an idea on what's happening [09:22] tsdgeos, yup, better in hide-mode 1 [09:22] rye: https://code.launchpad.net/~gotwig/lens-cooking/lens-cooking [09:22] rye: afk [09:23] greyback, hmm, is the lack of highlight _inside_ a focused launcher tile some new design? [09:23] I'm only getting a glow [09:23] around the tile [09:24] can someone help? I have problems with dbus, why does the lens not work/communite with that scope? :/ https://code.launchpad.net/~gotwig/lens-cooking/lens-cooking [09:24] Cimi: hi! can you tell me if the thunderbird toolbar will stay light colored for 12.04? i modified the icons of two extensions and i don't want to change those again for nothing. ;-) [09:25] by the way, bug #934055 :( [09:25] Launchpad bug 934055 in unity "Alt+PrintScreen is impossible with HUD" [Undecided,New] https://launchpad.net/bugs/934055 [09:25] htorque, light colored? [09:25] screenshot? [09:26] gotwig, your .scope file is wrong [09:26] Saviq: no new design [09:26] greyback, ok, checking with trunk [09:26] Cimi: http://i.imgur.com/ExpK6.png [09:26] htorque, http://ubuntuone.com/2InpyFE2dUNV11zWijd7Ie - that's what you are referring to? [09:26] Saviq: I'm gonna propose hud2 for merge [09:27] tsdgeos, can I see the TODO for MM so I don't bother you with known issues I find? [09:27] ah, you guys have labels... [09:27] sure [09:28] tsdgeos, panels positioning doesn't seem to be there [09:28] gotwig, here is what a scope looks like. http://bazaar.launchpad.net/~davidc3/unity-lens-videos/remote-videos/view/head:/video-remote.scope [09:28] Saviq: waht do you mean by panel positioning? [09:28] tsdgeos, currently multiple panels only work with screens lined up to their top edge [09:29] but that should be easy now that panels now which screen they belong to [09:29] Saviq: still don't get what is the problem [09:29] rye: yes, it was light-on-dark before, now it's the other way round. :-) [09:29] i.e. they always align to y=0 [09:29] but note i have one screen "physically" behing the other :D [09:29] so... [09:29] tsdgeos, try having one above the other [09:30] what would you expect? [09:30] the down one having no panel? [09:30] I would expect it to have a panel (I think) [09:30] and it doesn't? [09:30] no, both get stuck to top edge [09:30] tsdgeos, both of your screens are the same res, right? [09:31] they would be if the intel driver worked [09:31] so not really [09:31] tsdgeos, then align them by their bottom edge [09:31] i.e. a left of b [09:31] but not "common" top edge [09:31] just move the smaller one down a bit [09:31] i see [09:32] all panels get stuck to the top edge of the desktop [09:32] not screen [09:32] Saviq: write that there [09:32] I will [09:34] tsdgeos, done [09:35] greyback, is the last "in progress" item for HUD done? [09:45] tsdgeos, can you alt+f1 [09:45] do you have the whole launcher item highlighted? [09:46] davidcalle: does it work for you? [09:47] Saviq: yeah [09:47] doesn't work for you? [09:47] gotwig, I don't have the time to test it right now, sorry. [09:47] tsdgeos, nope, just a glow around it [09:48] ah true [09:48] :D [09:48] tsdgeos, must be something on my side then, ignore [09:48] well, actually [09:48] no no [09:48] i can repro [09:48] sorry [09:48] ok then, bug [09:49] Saviq: is that a pure unity-2d-shell bug? [09:49] Saviq: i.e. does it work with 1 screen only? [09:49] seems not [09:50] good morning [09:50] Saviq: just noticed background MR comments, need to deal with them first [09:50] davidcalle: is my .lens file also wrong? it has the same format [09:51] gotwig, your .lens file looks right. [09:51] tsdgeos, no, it's a trunk issue [09:52] davidcalle: no [09:52] davidcalle: it has an other namespace [09:54] davidcalle: do I need a .service fileß [09:54] greyback, tsdgeos confirmed - in trunk launcher tiles don't get highlighted properly on focus [09:55] gotwig, only if you want your lens to start when the session does. But you don't need it at that point for things to work. [09:55] Saviq: damnation. And good catch [09:58] anyone else seeing unity appindicator menus as only the shadow frame for the first use? [09:58] bug #934072 [09:58] Launchpad bug 934072 in unity (Ubuntu) "drop-down menus only partially drawn and sometimes displaced" [Undecided,Confirmed] https://launchpad.net/bugs/934072 [09:59] smb, ^^ i am seeing the same as you with different h/w, so i suspect its generic [09:59] apw, True. So at least "good" it seems indipendant [10:00] yep, handy you have radeon in this case [10:00] The Internet is coming! [10:00] bbiab === dyams is now known as dyams|lunch [10:08] * tsdgeos is having more problems than expected with the _NET_WM_STRUT_PARTIAL thing [10:09] davidcalle: it works partialy [10:14] davidcalle: I can acess the lens, even the scope does not work, and there's no content http://paste.ubuntu.com/845514/ [10:14] davidcalle: is the error when i run the lens, is that even an error? [10:18] Saviq: there? [10:20] unity launcher super+ shortcuts are now completely broken for already running applications [10:20] bug #934084 [10:20] Launchpad bug 934084 in unity (Ubuntu) "super+ keys now cause launch to wedge with the key hints shown and retains focus instead of selecting the requested window" [Undecided,New] https://launchpad.net/bugs/934084 [10:20] please tell me, if this is an error or not http://paste.ubuntu.com/845514/ [10:21] gotwig, is the dbus path in your scope daemon /net/launchpad/scope/information/wikipedia ? [10:22] davidcalle: you can see that in the bzr branch [10:22] davidcalle: its not [10:23] gotwig, the dbus path in your scope daemon should match the one in your .scope [10:23] davidcalle: it does? [10:24] davidcalle: is the /net important? [10:26] davidcalle: if I use the / I get another error [10:27] davidcalle: NameError: name 'sys' is not defined === dyams|lunch is now known as dyams [10:29] davidcalle: solved. so now I get Failed to own name net.launchpad.lens.cooking. Bailing out. [10:34] gotwig, the Failed to own name means that the daemon is already running. So check if you have it running in an other terminal. [10:34] davidcalle: :-) [10:35] http://paste.ubuntu.com/845514/ [10:38] http://paste.ubuntu.com/845589/ , after I restart unity [10:38] gotwig, what's in your /usr/share/unity/lenses/ cooking.lens cooking.svg recipefy.scope [10:39] davidcalle: I binNEWed the videdo lens btw [10:39] it wasn't [10:39] I need to push it to main now if you have the MIR ack bug # hadny [10:39] handy* [10:40] https://bugs.launchpad.net/ubuntu/+source/unity-scope-video-remote/+bug/933610 [10:40] Ubuntu bug 933610 in unity-scope-video-remote (Ubuntu) "[MIR] unity-scope-video-remote" [Undecided,Fix committed] [10:40] davidcalle: but thats not a problem I think. The lens does start up, and works, but without the scope [10:40] https://bugs.launchpad.net/ubuntu/+source/unity-lens-video/+bug/933609 [10:40] Ubuntu bug 933609 in unity-lens-video (Ubuntu) "[MIR] unity-lens-video" [Undecided,Fix committed] [10:40] didrocks, ^^ [10:40] thanks :) [10:41] didrocks, about the binNEWed, I don't know what it means :) [10:41] meaning that the video lens wasn't available in ubuntu [10:41] didrocks, ok [10:42]