[01:19] <h31> Hello. How to use Ayatana mailing list?
[09:15] <dbarth> bye #ayatana, welcome #ubuntu-unity
[09:16] <thumper> all... general Unity discussions moving to #ubuntu-unity
[09:17]  * thumper heading for a flight
[09:17] <thumper> can someone update the topic?
[11:28] <mhr3> davidcalle, hope you dont mind if we co-host the lenses session :)
[11:29] <davidcalle> mhr3, of course I don't. I would enjoy it :)
[11:29] <mhr3> davidcalle, cool i just mentioned if to dholback
[11:30] <mhr3> s/if/it/
[13:25] <kamstrup> bilal: awesome work on the USC integration. Can't wait to land it :-)
[14:15] <mhall119> oh, he changed his nick did he?  no wonder I couldn't ever find him
[15:01] <mhall119> kamstrup: ping
[15:01] <kamstrup> mhall119: pong
[15:01] <mhall119> kamstrup: do you know if this warning on the Launcher API is still valid? https://wiki.ubuntu.com/Unity/LauncherAPI#Using_the_Launcher_API
[15:02] <kamstrup> mhall119: the API and ABI is for all practical purposes frozen by now. Only divine (read: sabdfl) intervention can change that
[15:02] <kamstrup> mhall119: so I guess the answer is "no" :-)
[15:03] <kamstrup> although the disclaimer on the dbus protocol is still valid I guess
[15:03] <kamstrup> that is not part of the public api
[15:04] <mhall119> is everything here on the wiki duplicated on the developer portal?
[15:05] <mhall119> or parts of it that we can replace with a link to the dev portal docs?
[15:22] <mhall119> kamstrup: ^^ ?  I'd like to clean that up, since it was pointed out on a comment in my blog that we're giving developers the wrong information
[15:22] <kamstrup> oh
[15:22] <kamstrup> i don't know much about the stuff on the dev portal, that is updated by dpm afaik
[15:37] <mhall119> kamstrup: ok, for now is it okay if I remove the warning on the Launcher API (but leave the one on DBus)?
[15:51] <kenvandine> kamstrup, any ideas why row-added is broken with pygi?  it has never worked
[15:51] <kenvandine> TypeError: Expected Dee.ModelIter, but got StructMeta
[15:57] <mhall119> didrocks: ping
[15:57] <didrocks> hey mhall119
[15:58] <mhall119> hey didrocks, jcastro was telling me that you had a community contributor make a significant patch to Unity that sped things up for Unity 5.0, and he asked me to blog about that
[15:58] <mhall119> would you be able to shoot me an email with the contributor's name, link to the rev/mp, and a description of what it did?
[15:59] <mhall119> also his email, so I can contact him for a photo and bio
[16:02] <didrocks> mhall119: oh sure, doing that in 10 minutes :)
[16:02] <didrocks> (just need to finish testing file-roller first)
[16:05] <mhall119> thanks didrocks
[16:07] <didrocks> yw :)
[17:10] <kamstrup> mhall119: ok
[17:10] <kamstrup> kenvandine: i think i had it working once... can you file a bug?
[17:12] <kenvandine> sure
[17:12] <kenvandine> kamstrup, thx
[17:16] <kenvandine> kamstrup, bug 917761
[17:43] <mick0> davidcalle: You there? :)
[17:57] <davidcalle> mick0, yup
[17:58] <davidcalle> mick0, I'm pushing the packaging branch tonight. :)
[17:58] <mick0> davidcalle: I've updated the spotify scope as you did with the piratebay scope.
[17:58] <mick0> davidcalle: Can I find documantation on the 5.0 api anywhere?
[18:00] <mick0> I don't have precise installed yet (downloading it to install it on my laptop right now) so I havent tested it yet.
[18:00] <davidcalle> There is https://wiki.ubuntu.com/mhr3/Lenses which is in progress I believe. And http://developer.ubuntu.com/api/ubuntu-12.04/python/Unity-5.0.html
[18:00] <mick0> davidcalle: Did you get the new packaging standard working?
[18:01] <mick0> Ahh nice. Thanks :)
[18:01] <davidcalle> mick0, the packaging is now a bit more complicated. I will push the branch tonight.
[18:02] <mick0> Ok.
[18:03] <davidcalle> mick0, there will be a blog post from kamstrup about the new API, it should be helpful too (with sample code, I believe).
[18:03] <mick0> Nice
[18:12] <BerndSch_> davidcalle: why is the new packaging more compicated? I thought the only difference is the path /opt instead of /usr/lib?
[18:13] <BerndSch_> davidcalle: I also started a branch for precise yesterday and pushed it to launchpad. But I hadn't enough time to test it. I think there are still some problems
[18:14] <davidcalle> BerndSch_, because it also needs an AppArmor profile. I haven't really looked at it since I got it yesterday, it has been done by a member of the Application Review Board.
[18:17]  * davidcalle is afk for a few hours.
[18:18] <BerndSch_> davidcalle: ok, if I have tested my precise branch I will try to submit my lens
[18:21] <davidcalle> BerndSch_, I don't know if the submissions for Precise are open yet. You might want to check with stgraber, he is the one who has guided me through the process (and done the packaging).
[21:47] <bschaefer> andyrock, hey are you still up?
[21:48] <andyrock> bschaefer, sure
[21:48] <bschaefer> andyrock, do you ibus installed?
[21:48] <andyrock> yep
[21:49] <bschaefer> andyrock, well it comes with ubuntu but umm with ibus-hangul version?
[21:49] <bschaefer> andyrock, I just found out something even weirder with the ibus bug...
[21:50] <bschaefer> andyrock, and I wanted to see if that was happing for you. Do you also have the num pad? or are you using a laptop?
[21:50] <andyrock> i enabled ibus when i tested a Trevino's branch
[21:50] <andyrock> laptop
[21:50] <andyrock> without num pad
[21:50] <andyrock> let me check the first question
[21:50] <bschaefer> andyrock, shit. well so ALL the num pad keys get commited before the preedit...
[21:51] <bschaefer> so - on the left side commits fine and the - on num pad commits before the preedit!
[21:51] <bschaefer> andyrock,
[21:51] <bschaefer> https://bugs.launchpad.net/ubuntu/+source/unity/+bug/880876
[21:51] <bschaefer> for refrence
[21:52] <bschaefer> andyrock, if you done have it just sudo apt-get install ibus-hangul for the Koren input...but you dont have the num pad
[21:53] <andyrock> bschaefer, can i fake the numpad with an osk?
[21:53] <bschaefer> andyrock, hmm I haven't tried
[21:53] <bschaefer> andyrock, i need to check the keyval of the keys too
[21:53] <bschaefer> andyrock, cause now I am thinking they are different (for some reason)
[21:56] <bschaefer> andyrock, yeah using the keyboard in the universal access causes the same thing
[21:57] <bschaefer> andyrock, hmm interesting...I have been digging though the source of ibus and ibus-hangul for last couple days for a fix. I really want ibus to be happy with unity!
[21:57] <andyrock> bschaefer, so help me to enable ibus :)
[21:57] <bschaefer> andyrock, alright, so go to system settings
[21:57] <bschaefer> then language support
[21:58] <bschaefer> andyrock, and under keyboard input method system select ibus
[21:58] <bschaefer> andyrock, and Apply system-wide
[21:58] <bschaefer> andyrock, then at the command line: sudo apt-get install ibus-hangul ibus-table
[21:59] <bschaefer> then reboot (yeaah annoy sorry!)
[21:59] <bschaefer> annoying*
[21:59] <bschaefer> or logout
[22:00] <andyrock> brb
[22:00] <bschaefer> alright
[22:02] <bschaefer> andyrock, ok, then on the command line: ibus-setup&
[22:02] <bschaefer> and add the Koren input method
[22:02] <andyrock> 아럼낭ㄹ
[22:02] <bschaefer> sweet
[22:03] <andyrock> awesome
[22:03] <bschaefer> ok now type in Koren then when the char still is in preedit
[22:03] <bschaefer> press space
[22:03] <bschaefer> and that is the bug
[22:03] <bschaefer> ㄹㅁㄴㅇ ㄹ
[22:03] <bschaefer> ㅁㄴ리ㅏ8ㅓ
[22:03] <bschaefer> along with num pad keys and return which is a problem too
[22:04] <andyrock> ok i press
[22:04] <andyrock> a
[22:04] <andyrock> n
[22:04] <andyrock> d
[22:04] <andyrock> then space
[22:04] <andyrock> and i got this
[22:05] <andyrock> 뭉
[22:05] <andyrock> 뭉
[22:05] <bschaefer> right click and make sure under input method it is ibus
[22:05] <bschaefer> because I patch went through to fix the ibus if you use xim and the main input method
[22:05] <bschaefer> right click where you are typing text
[22:06] <bschaefer> or do it in the Dash
[22:06] <bschaefer> cause xim doesn't work there...
[22:06] <andyrock> ok i've it in the dash i'm no longer able to get the ibus menu
[22:06] <andyrock> ant this's weid
[22:06] <andyrock> *weird
[22:06] <andyrock> mmm
[22:07] <bschaefer> shit
[22:07] <bschaefer> I have a patch for that
[22:07] <bschaefer> haha, the focus was removed
[22:07] <bschaefer> in IMTextEntry.cpp
[22:07] <bschaefer> (signal was removed)
[22:07] <bschaefer> umm will try the gnome-terminal then haha
[22:08] <andyrock> in the gnome-terminal
[22:08] <andyrock> i get the space before
[22:08] <andyrock> the symbol
[22:08] <bschaefer> yeah
[22:08] <bschaefer> ok now get that virtual keyboard thing up
[22:08] <andyrock> 뭉
[22:08] <andyrock> 무요개차
[22:09] <bschaefer> your chat program is prob using XIM as its IM
[22:09] <bschaefer> which uses different code in ibus
[22:10] <andyrock> ok i've the osk
[22:10] <bschaefer> no back in gnome-terminal try the same thing with a normal 1 and a num pad 1
[22:11] <bschaefer> when I type "asd1" I get these two versions: ㅁㄴㅇ1 and ㅁㄴ1ㅇ and I just want to make sure that is happening for someone else
[22:12] <bschaefer> the second one being from numpad
[22:13] <andyrock> with a normal 1 i don't get the problem
[22:14] <bschaefer> yeah
[22:14] <andyrock> 뭉1
[22:14] <bschaefer> a numpad 1 or anything on the numpad should mess is up
[22:15] <andyrock> indeed
[22:15] <andyrock> i've tested it withoud the osk
[22:15] <andyrock> fn + numlk
[22:16] <andyrock> does its job
[22:16] <andyrock> i get 1 and the symbol
[22:16] <bschaefer> sweet, that is good to know though
[22:16] <bschaefer> man this bug is very interesting...
[22:17] <bschaefer> cause I am thinking the problem now is ibus-hangul when forced to handle space or num pad nums it doesn't know how to handle them
[22:17] <andyrock> bschaefer, then theach it
[22:17] <andyrock> ;)
[22:17] <bschaefer> which forces how it process the keyval it just commits it right away instead of checking else where
[22:18] <bschaefer> theach?
[22:19] <bschaefer> andyrock, I am have been trying to make unity and ibus friends for months now! They just don't like each other...
[22:20] <andyrock> teach
[22:20] <andyrock> sorry
[22:20] <andyrock> ;)
[22:20] <andyrock> maybe compiz's fault?
[22:20] <bschaefer> haha no problem. I haven't even been able to get gdb working with the ibus sooo all the out I am using is fprintf to a log file I set up
[22:21] <bschaefer> no you can get this bug on any enviorment. Gnome, Unity 2d
[22:21] <andyrock> Cimi loves printf ;)
[22:21] <bschaefer> it is an ibus problem!
[22:21] <andyrock> ah ok
[22:21] <bschaefer> I love it too, so no complaints, it is just some of this ustring that fwprintf cant handle or printf haha
[22:21] <andyrock> and why we have the bug opened against unity? o.o
[22:22] <bschaefer> andyrock, no sure!
[22:22] <bschaefer> not*
[22:22] <andyrock> use g_debug btw
[22:22]  * bschaefer looks up function
[22:22] <bschaefer> thanks!
[22:23] <andyrock> i don't know if it can handle wchar
[22:23] <andyrock> but use (f)printf for debug is evil
[22:23] <bschaefer> yeah, i the buffer
[22:23] <bschaefer> using stderr helps
[22:24] <bschaefer> when using fprintf it doesn't get commited to files, but using stderr forces it to print right away!
[22:24] <gang65> hi
[22:24] <bschaefer> doesn't get commited to files right away*
[22:24] <gang65> I need some advice about Unity design
[22:25] <mgedmin> fflush()?
[22:25] <bschaefer> that would work too
[22:25] <mgedmin> stderr is not buffered by default, iirc
[22:26] <bschaefer> mgedmin, thanks, the fflush() is something I should be using anyway
[22:28] <bschaefer> andyrock, and thanks for confirming that! Always help talking to some else about bugs...
[22:28] <andyrock> your welcome
[22:28] <andyrock> i'm not an ibus-expert :)
[22:29] <andyrock> btw remove all the ibus code from unity
[22:29] <andyrock> and put them directly in nux
[22:29] <bschaefer> andyrock, jaytaoko is working on that
[22:30] <bschaefer> andyrock, and if he can get that working with out using IBUS_ENABLE_SYNC_MODE
[22:30] <bschaefer> then this wont be a problem, but im not sure how much progress he has made on it
[22:31] <bschaefer> andyrock, I wish I was an ibus expert, I just keep getting assigned the ibus bugs haha
[22:32] <andyrock> we have all the time to learn ;)
[22:33] <bschaefer> very true! I would have to admit I do know a lot about the ibus now
[22:34] <bschaefer> jaytaoko, ping if you are around! Curious on your TextEntry progress!
[22:34] <andyrock> bschaefer, in budapest I told me that he want you to review iirc
[22:34] <andyrock> *wants
[22:35] <andyrock> *to review his code
[22:35] <bschaefer> yeah, does he have a branch out?
[22:35] <bschaefer> that I missed
[22:37] <andyrock> bschaefer, i think not
[22:38] <bschaefer> andyrock, well he +3 hours from my time zone so i should be able to catch him sometime today
[22:39] <bschaefer> andyrock, now I need to make some more coffee and then back to trying to fix this ibus bug! Good luck with your work :)
[22:40] <andyrock> bschaefer, struts work and keyboard navigation :(
[22:40] <andyrock> *struts work = _NET_WM_STRUT_PARTIAL
[22:53] <bschaefer> andyrock, haha
[23:31] <AlanBell> in precise I am finding gnome-terminal and terminator windows are translucent when the unity compiz plugin is activated
[23:31] <AlanBell> is this intentional behaviour? my terminal settings are set to solid colour
[23:34] <mhr3> bschaefer, you wanted to work on the hint for no-results, right?
[23:35] <mhr3> there are merge requests lined up for review which would finally allow you do it :)
[23:37] <AlanBell> ah, looks like the panel opacity slider is controlling terminal window opacity as well as the panel