[00:08] <bschaefer> jaytaoko, hey, ping
[00:33] <jaytaoko> bschaefer: hello
[00:36] <bschaefer> jaytaoko, so it turns out there isn't a g_utf8 that checks if the string is utf8 only
[00:37] <jaytaoko> bschaefer: yep, I saw
[00:37] <bschaefer> jaytaoko, but if you check against array[i][0]
[00:37] <bschaefer> all unicode strings will be less then 0
[00:37] <jaytaoko> bschaefer: I managed to get around. I have a working test now!
[00:37] <bschaefer> if you take the first char and turn it into an int
[00:37] <bschaefer> nice! I just finsihed a working version also!
[00:37] <jaytaoko> cool!
[00:38] <bschaefer> Im not as sure about mine though, I don't like doing this to find unicode
[00:38] <bschaefer> if (match) { while (nux_compose_string[i][0] > 0) {i++;}}
[00:38] <jaytaoko> bschaefer: I added a special string that marks the start of the character we want
[00:38] <bschaefer> yeah
[00:39] <bschaefer> that sounds like a better way :)
[00:39] <jaytaoko> bschaefer: works fine!
[00:39] <bschaefer> awesome! Have you noticed a lag when it EnterText() is called?
[00:39] <jaytaoko> bschaefer: let me finish something here and i will push
[00:39] <bschaefer> sweet
[00:39] <jaytaoko> bschaefer: the lag is resolved!
[00:39] <bschaefer> jaytaoko, awesome! What was causing it?
[00:40] <bschaefer> and event gone missing?
[00:40] <bschaefer> an*
[00:40] <bschaefer> jaytaoko, ill talk with you about when you finish up the branch! Hopefully my work last night was helpful!
[00:40] <jaytaoko> bschaefer: when there is a match, we have to call QueueRefresh the the text entry will redraw. Otherwise, it will redraw only the next time the cursor blinks
[00:41] <bschaefer> dam that makes sense!
[00:41] <jaytaoko> bschaefer: it was very helpful!
[00:41] <bschaefer> sweet!
[00:42] <jaytaoko> bschaefer: so give me a few minutes and I will push a branch... you will also notice that it works in Unity's dash (the previous work as been reverted)
[00:42] <bschaefer> jaytaoko, awesome! Yeah take your time :)
[00:53] <jaytaoko> bschaefer: I pushed to the branch https://code.launchpad.net/~unity-team/nux/nux.compose-key
[00:54] <bschaefer> jaytaoko, cool, I just compiled unitys new changes
[00:54] <jaytaoko> bschaefer: compile and run the test xtest-text-entry-deadkeys
[00:54] <bschaefer> jaytaoko, cool, and i wasn't sure if putting the list in a header like that was correct
[00:54] <jaytaoko> bschaefer: with unity trunk and this nux branch, the composition characters works
[00:55] <jaytaoko> bschaefer: it is ok!
[00:55] <bschaefer> cool, I also didn't think I needed to add it to the make file
[00:56] <bschaefer> jaytaoko, awesome work!!
[00:56] <jaytaoko> bschaefer: I wasn't able to do all the test that I wanted because I have to guess how to automated some of the characters with X11...
[00:56] <bschaefer> jaytaoko, working well here
[00:56] <jaytaoko> bschaefer: cool! thank you for making that python script! it was very helpful!
[00:57] <bschaefer> jaytaoko, yeah I was thinking it could be used to make the test!
[00:57] <bschaefer> jaytaoko, though it isn't the best python code there is, it work haha
[00:57] <jaytaoko> bschaefer: it is fine!
[00:57] <jaytaoko> bschaefer: you can add a few tests of your own if you want
[00:57] <bschaefer> jaytaoko, wait so whats wrong with entering some of the text?
[00:57]  * bschaefer looks at the current test
[00:58] <jaytaoko> bschaefer: well I still can't simulate "´" with X11
[00:58] <jaytaoko> bschaefer: so I wasn't able to do ś
[00:58] <bschaefer> test.ViewSendCompositionKeys("`o");
[00:58] <bschaefer> so that doesn't work?
[00:58] <bschaefer> opps that is the wrong way
[00:58] <jaytaoko> bschaefer: yes that one works
[00:59] <bschaefer> jaytaoko, wait im not sure where that key even is..
[00:59] <bschaefer> jaytaoko, well what im thinking I can do!
[01:00] <jaytaoko> bschaefer: it is not on my keyboard either but if you press: Right Alt + ' + '  then you get ´
[01:00] <bschaefer> jaytaoko, with the python script I can make it output these C++ code for nux, for ALL of them
[01:00] <bschaefer> jaytaoko, in theory
[01:00] <bschaefer> or more or less in my head haha
[01:01] <bschaefer> jaytaoko, but ill update these test!
[01:01] <bschaefer> with more
[01:01] <bschaefer> jaytaoko, o one problem I found was the delete key!
[01:01] <jaytaoko> bschaefer: cool, feel free to do "control + a" and erase the text entry and then continue with your own serie
[01:02] <jaytaoko> bschaefer: otherwise the string becomes too long for the text entry
[01:02] <bschaefer> jaytaoko, alright, will do, yeah
[01:02] <bschaefer> jaytaoko, Im thinking the test will go:
[01:02] <bschaefer> test.ViewSendCompKey...
[01:02] <bschaefer> then check for equal
[01:02] <bschaefer> then delete all
[01:02] <bschaefer> then next test
[01:03] <bschaefer> repeat for all possible combos
[01:03] <jaytaoko> bschaefer: sure, you can do that as well! fell free!
[01:03] <jaytaoko> bschaefer: I am going to propose the branch for review also
[01:03] <bschaefer> jaytaoko, do you think we should fix the delete key?
[01:03] <bschaefer> jaytaoko, if you press Multi_key
[01:03] <bschaefer> jaytaoko, and just hit delete you get stuck
[01:04] <jaytaoko> bschaefer: oh!
[01:04] <bschaefer> jaytaoko, I feel like out of any combo that one might be used
[01:04] <bschaefer> in gnome-terminal it quits if 2 deletes are pressed
[01:04] <bschaefer> quits multi_key mode that is
[01:05] <jaytaoko> bschaefer: yes, we should fix that
[01:05] <bschaefer> jaytaoko, also pressing multi_key should toggle comp mode off and on
[01:07] <bschaefer> jaytaoko, the delete key doesn't add anything to the string
[01:07] <bschaefer> jaytaoko, so what we could do is!
[01:07] <bschaefer> jaytaoko, if (composition_string_ == character) { quick comp mode)
[01:08] <bschaefer> hm
[01:08] <bschaefer> jaytaoko, I don't know though, as im not sure if there are combos that are the same key twice
[01:08] <jaytaoko> bschaefer: not sure either...
[01:09] <jaytaoko> bschaefer: I am going to take a break, but I will be back later
[01:09] <bschaefer> jaytaoko, sounds good, Ill see if I can find an easy fix for both those problems!
[01:09] <jaytaoko> bschaefer: thank you!
[01:09] <bschaefer> jaytaoko, thanks for finishing that up! Awesome work
[01:10] <bschaefer> no problem, this is fun :)
[01:10] <jaytaoko> bschaefer: ;-)
[01:14] <bschaefer> jaytaoko, found a good solution, just check in LookForMatch if comp string is empty, if it is then there cant be a match; return NO_MATCH
[01:14] <bschaefer> (for when you get back)
[03:11] <bschaefer> :q
[03:11] <bschaefer> opps
[03:30] <jaytaoko> bschaefer: ping
[03:31] <bschaefer> jaytaoko, hey, so turns out that delete fix wont work
[03:32] <bschaefer> and I also found some more errors in the list
[03:32] <bschaefer> just because of "">"
[03:32] <bschaefer> stuff like that were missing \
[03:32] <jaytaoko> bschaefer: right I have had issue with < and >
[03:32] <bschaefer> jaytaoko, yeah and a few lines were missing "::"
[03:33] <bschaefer> because the python script had some issues with spaces and stuff
[03:33] <jaytaoko> bschaefer: ok
[03:33] <bschaefer> easy fixes though
[03:33] <bschaefer> http://paste.ubuntu.com/873973/
[03:33] <jaytaoko> bschaefer: I just pulled the code
[03:33] <bschaefer> jaytaoko, im just pushing some new changes to the list
[03:34] <jaytaoko> bschaefer: yeah, I still don't know how to simulate some of the characters with the Xtest
[03:35] <jaytaoko> bschaefer: skype?
[03:35] <bschaefer> jaytaoko, hmm well im getting this so I cant push:
[03:35] <bschaefer> bzr: ERROR: Connection error: Couldn't resolve host 'bazaar.launchpad.net' [Errno -2] Name or service not known
[03:35] <bschaefer> jaytaoko, yeah lets get on skype
[03:36] <bschaefer> jaytaoko, never figured it out, pushing changes now
[10:40] <didrocks> JohnLea: about the MM changes
[10:40] <didrocks> JohnLea: you know that changing that in that dialog won't work for nvidia users, right?
[10:41] <didrocks> JohnLea: as on nvidia, the dialog just shows one screen
 JohnLea: about the MM changes
[10:41] <JohnLea>  JohnLea: you know that changing that in that dialog won't work for nvidia users, right?
[10:41] <JohnLea>  JohnLea: as on nvidia, the dialog just shows one screen
[10:41] <JohnLea> swilson ^
[10:42] <didrocks> the second option will work, but not the first one as we won't have the monitors listed
[10:43] <didrocks> the All displays can be presented, it will just not be able to select on which screen the launcher will be placed for nvidia
[10:43] <didrocks> DBO: greyback: that is of some interests for you ^
[10:44] <greyback> didrocks: noted
[10:47] <Saviq> didrocks, you can select your primary screen in nvidia-settings (that you have to use to set up screens on nvidia anyway)
[10:47] <Saviq> didrocks, maybe we should detect nvidia and give additional info next to the selection or something?
[10:49] <didrocks> Saviq: well, it won't match the design as well, I'm not sure how easy it can be to get the info like nvidia-settings
[10:49] <didrocks> Saviq: and it won't be the same "monitor name" than the dialog above
[10:49] <swilson> didrocks, Saviq: hi, would anyone be able to send me a quick screenshot of what you see in the nvidia config screen please?
[10:51] <Saviq> didrocks, what I mean is just select "All screens" vs. "Main screen" and direct the users to nvidia-settings to select which is the main screen
[10:51] <Saviq> swilson, sure, sec
[10:52] <didrocks> swilson: http://people.canonical.com/~didrocks/nvidia.png
[10:52] <didrocks> Saviq: no need
[10:52] <didrocks> swilson: I have multiple monitors
[10:53] <didrocks> and "Inconnu" is "unknown"
[10:53] <swilson> didrocks: thanks!
[10:53] <didrocks> Saviq: yeah, Main screen can be the way to go
[10:54] <didrocks> Saviq: I'm not sure we make something more elegant to detect nvidia than looking at the loaded kernel module
[10:55] <Andy80> 'morning :)
[10:56] <didrocks> morning Andy80 :)
[11:00] <Saviq> swilson, http://ubuntuone.com/11DlGCkW3x5N6AMek5sdsL and http://ubuntuone.com/4opyBrMXwLy2x0GXrng9M7
[11:00] <Saviq> swilson, http://ubuntuone.com/11DlGCkW3x5N6AMek5sdsL and http://ubuntuone.com/4opyBrMXwLy2x0GXrng9M7
[11:00] <Saviq> swilson, network troubles?
[11:01] <Saviq> you're difficult to catch...
[11:02] <swilson> Saviq: yep, back online now...
[11:03] <swilson> thanks for the screenshots
[11:04] <Saviq> swilson, people with nvidia have to be friendly with the tool anyway, 'cause there's no other way to set up your screens
[11:05] <Saviq> let me try something, brb
[11:05] <swilson> sure, so this dialog refers to the primary display
[11:06] <swilson> maybe we just hook to this for Nvidia
[11:06] <swilson> Saviq: I am in a sprint at the moment and have to get back into it, will try to stay in touch as much as I can...
[11:17] <Saviq> swilson, yeah and that's how it looks in "Displays" http://ubuntuone.com/0nbRrX5CopsZH1tRYo3BEN
[11:23] <swilson> Saviq: thanks. how straightforward/reliable do you think it would be to determine that the single large display reported in Display Settings is actually multiple displays?
[11:23] <swilson> maybe we could just provide the options Primary display and All dislpays for this case
[11:23] <Saviq> swilson, tbh no idea, but if it would be "easy" I think it'd have already been done
[11:24] <Saviq> didrocks, maybe you have insights ^?
[11:24] <swilson> i just mean to find out that this is the case, not necessarily to correct it by splitting the individual displays out at this stage
[11:26] <didrocks> (on a call, will look later)
[11:30] <didrocks> swilson: it's not trivial, but we can have a look if the nvidia module is loaded maybe and in this case proposing the "primary display" option
[11:36] <swilson> didrocks: cool. it would be ideal not to expose the Primary display concept to the user unless they are already aware of it because of using the nvidia settings options
[11:37] <didrocks> swilson: hum, what do you want to do in the nvidia case then? you are forced to have a primary display, that doesn't mean the user is aware of it unfotunatly
[11:41] <swilson> yes, this is not an ideal case
[11:41] <swilson> nvidia users have to use the nvidia settings panel if they want to manage their multiple displays
[11:41] <swilson> they are exposed to the concept of the primary display there
[11:42] <swilson> ideally, they should only have to use the Display Settings panel
[11:43] <swilson> we will ideally improve this going forwards
[11:46] <didrocks> yeah, but it's not really possible because of closed sourced software
[11:47] <DBO> why not put all the options in one place?
[11:54] <didrocks> swilson: so, I would go with this "primary" option if possible
[11:55] <swilson> didrocks: you mean in all cases (nvidia, ati, etc...)
[11:58] <didrocks> hum
[11:58] <didrocks> ok, let me recap
[11:58] <didrocks> in non nvidia case
[11:58] <didrocks> we have monitor names
[11:58] <didrocks> and "on all screens"
[11:59] <didrocks> in the nvidia case
[11:59] <didrocks> we don't have the monitor names
[11:59] <didrocks> so we can tell "in primary monitor"
[11:59] <didrocks> and "on all screens"
[12:05] <swilson> yes
[12:07] <didrocks> ok, I guess we can put that in case there is one sceen with "unknown" label
[12:16] <didrocks> swilson: can you update the spec with that case, please?
[12:17] <swilson> didrocks: yes, will do. i am in a sprint at the moment, so i will update the spec when i get a chance. john also wants for us to finalise details and get these modifications into the system as bugs before we start implementation
[12:17] <didrocks> swilson: right, thanks!
[12:18] <swilson> didrocks: thanks v much for pointing out this case by the way!
[12:18] <didrocks> swilson: no worry (and yes, I agree the situation is suboptimal for that) :-)
[13:00] <mhall119> somehow lost unity last night
[13:00]  * mhall119 should pay more attention to the dist-upgrade
[13:26] <zyga> hi, there is a color mismatch in the sound indicator
[13:26] <zyga> shall I report that?
[13:29] <Andy80> zyga: can you make a screenshot so we can see the problem better?
[13:29] <seb128> zyga, the slider background you mean?
[13:29] <zyga> sure
[13:29] <zyga> yes
[13:29] <zyga> seb128, exactly that
[13:29] <seb128> zyga, known issue
[13:29] <zyga> seb128, I've spotted it on my efika mx which has 16bit color screen
[13:29] <zyga> the issue is very visible there
[13:29] <seb128> not only there
[13:29] <zyga> right, I can see it on my desktop as well
[14:19] <angeloc> mhr3: hi Michal!
[14:20] <angeloc> mhr3: for merge proposal of bug 770126
[14:20] <ubot5`> Launchpad bug 770126 in unity-place-applications (Ubuntu) "Alt+F2 - ssh:// and smb:// access doesn't work in Unity (should open Nautilus)" [Wishlist,Confirmed] https://launchpad.net/bugs/770126
[14:20] <mhr3> angeloc, hey there
[14:20] <angeloc> mhr3: orig never starts with \\\\
[14:21] <mhr3> angeloc, how come?
[14:21] <angeloc> mhr3: sorry, i'm wrong!
[14:23] <angeloc> mhr3: I'm really wrong! I suffer a little of sleep deprivation since i had my second son!
[14:23] <mhr3> angeloc, hehe, no problem, get some rest
[14:26] <angeloc> mh3r: I had :)!
[14:40] <mhall119> angeloc: kids will do that
[14:42] <angeloc> mhall199: yes, but they are beautifull!
[14:44] <mhall119> angeloc: true
[14:46] <angeloc> mhall119: my little one starts to crawl and he's very exhilarant!
[14:47] <mhall119> once they're mobile you're in trouble
[14:48] <angeloc> mhr3: can you suggest another bug to solve? I'm intrested in bug 925021, but i'm not experienced sufficiently with codebase
[14:48] <ubot5`> Launchpad bug 925021 in unity (Ubuntu) "Launcher - Inserting items into launcher makes unnecessary animations on other monitors" [High,Confirmed] https://launchpad.net/bugs/925021
[14:49] <mhr3> angeloc, just go over the bugs and pick something
[14:50] <angeloc> mhr3: let's go!
[14:50] <mhr3> angeloc, also, you won't be familiar with many of them, you'll have to take a deep breath and dig into them ;)
[14:51] <angeloc> mhr3, i'm really intrested, i'll be really proud if you can mentor me woth bug 925021
[14:51] <ubot5`> Launchpad bug 925021 in unity (Ubuntu) "Launcher - Inserting items into launcher makes unnecessary animations on other monitors" [High,Confirmed] https://launchpad.net/bugs/925021
[14:53] <mhr3> angeloc, not even my knowledge isn't enough here ;) but MacSlow might be able to help
[14:54] <mhr3> eeh, no double negatives in english...
[14:54]  * mhr3 slaps himself
[14:54] <MacSlow> angeloc, hey... taking a loko at #925021
[14:55] <angeloc> MacSlow: greeat!
[14:56] <MacSlow> angeloc, oh.. hm... I can't say off the top of my head what could be going on there... would have to dig in myself... and I'm busy with other stuff still
[14:57] <angeloc> MacSlow, solving a bug means diggin into, I'm trying by myself!
[14:57] <MacSlow> angeloc, but what I suggest... just take a look and collect any kind of questions you come across... put them in an email and send them over to me... I'll look into answering them later this evening (or tomorrow)... deal?
[14:57] <angeloc> MacSlow, there is a sort of documentation of what's going on somewhere?
[14:58] <MacSlow> angeloc, ehm... the soucecode :)
[14:58] <angeloc> MacSlow, really great!
[14:58] <angeloc> MacSlow, code is self explaining!
[14:58] <MacSlow> angeloc, of jason if you're lucky... but he's as busy as everybody else :)
[14:59] <angeloc> MacSlow, i don't want to be a pain in the ass
[15:00] <MacSlow> angeloc, email is fine... don't worry
[15:00] <angeloc> MacSlow, ok
[16:09] <didrocks> greyback: when you get a chance: https://code.launchpad.net/~didrocks/unity-2d/common-and-package-cleaning/+merge/96610
[16:09] <greyback> didrocks: wonderful, will get to it, thanks
[16:11] <didrocks> yw ;)
[16:29] <VlAleVas> Hi! I'm writing an article for russian Wikipedia and I have a question: is there any differnce between Lenses and Places&
[16:35] <davidcalle> VlAleVas, no real difference. "Places" is the old name of "Lenses".
[16:37] <davidcalle> VlAleVas, the technical difference : Places were both the containers and the search engines. Now, lenses are the container and scopes are the search engines inside lenses.
[16:37] <VlAleVas> Thanks davidcalle!
[16:38] <davidcalle> VlAleVas, yw
[16:55] <angeloc> mhr3: bugs i slved works also in unity2d? lenses are shared? Have to take a look also at 2d version of the bug?
[17:44] <mhall119> does anybody know where I can find mark tully?
[18:00] <angeloc> MacSlow: i think i found the root of the problem!
[18:01] <angeloc> MacSlow: on row 2695 in Launcher.cpp this will be called unrespectively of where launcher mouse is on
[18:01] <angeloc> MacSlow: _dnd_hovered_icon = new SpacerLauncherIcon();
[18:02] <angeloc> MacSlow: how choose a launcher instead of another? Involves it mouse x,y?
[18:22] <jalcine> Is the meeting at 19:00 still happening?
[18:44] <mhall119> ronoc: ping
[18:49] <ronoc> mhall119, just running out the door
[18:49] <ronoc> mhall119, back online MOnda
[18:49] <ronoc> y
[18:50]  * ronoc needs to catch a flight
[18:50] <mhall119> ronoc: am I going to get a blog about the Sound Menu API?
[18:53] <thomi> morning everyone
[18:54] <mhall119> is there anybody who can help me put together some quick documentation about integrating with the sound menu using libunity?
[18:55] <mhall119> thumper: ^^ I need help, I'm under the gun to get something for dpm this week
[19:18] <mhall119> dbarth: ping
 does anybody know where I can find mark tully?
[19:47] <Teester> mhall119: Were you looking for me earlier? ^
[19:48] <mhall119> Teester: I was, yes
[19:48] <mhall119> wanted to chat about your lenses and scopes, got a few minutes?
[19:49] <Teester> Sure. What's up?
[19:49] <mhall119> can you still access https://docs.google.com/spreadsheet/ccc?key=0AhORzygg00JldFZtOVgzVHllekMzR1VMOXZYMk54c0E ?
[19:49] <Teester> Yes
[19:50] <mhall119> cool
[19:50] <mhall119> so, backstory, to allow separate lenses and scopes to be installable via the software center, and to let them go through the developer portal, the ARB has agreed to maintain the packaging for them
[19:51] <mhall119> so all we need to do is submit them as branches or tarballs or something, no need to build packages from them
[19:51] <Teester> Ok.
[19:51] <mhall119> right now they're only looking at submissions for Oneiric, so if you have any lenses or scopes ready for that release you can go ahead and start submitting them
[19:52] <Teester> I've submitted the music lens scopes already - rhythmbox, guayadeque, clementine & gmusicbrowser.
[19:52] <Teester> But I've packaged them by copying the askubuntu lens.
[19:53] <mhall119> that's okay
[19:54] <mhall119> the reason is so they can keep related lenses and scopes in the same source package archive, without requiring the lens and scopes developers to coordinate on packaging
[19:55] <mhall119> for the music lens, since it's in the main repo, this doesn't apply
[19:55] <mhall119> but for any lens that in the extras repo, they'll handle packaging everything together
[19:56] <mhall119> so, for example, davidcalle's graphic design lens, they're going to maintain the packaging for that and any scopes that get submitted for it
[19:56] <mhall119> make sense?
[19:57] <Teester> Does that mean that the user will only see one package in the software centre for a lens and its scopes?
[19:59] <thumper> mhall119: integrating with menus would be ted I think, and ronoc knows about sound, but not sure how much about the menu itself
[19:59] <mhall119> thumper: right, unfortunately ronoc is done until Monday
[20:00] <mhall119> tedg: do you have anything for me to use as documentation for integrating with the message menu?
[20:00] <tedg> mhall119, I don't have anything other than what you have.
[20:00] <mhall119> it doesn't have to be ready-to-post, I can edit and even expand somewhat, I just need something to start with
[20:00] <mhall119> tedg: I  don't have anything atm
[20:01] <tedg> mhall119, I believe we did an developer week or one of those talks on it.
[20:01] <tedg> mhall119, https://wiki.ubuntu.com/MessagingMenu#How_applications_should_integrate_with_the_messaging_menu
[20:01] <tedg> mhall119, https://wiki.ubuntu.com/MessagingMenu#API
[20:01] <mhall119> tedg: there's no code there
[20:02] <mhall119> nothing about adding a message source and counter
[20:03] <tedg> mhall119, http://bazaar.launchpad.net/~indicator-applet-developers/libindicate/trunk.0.7/files/head:/examples/
[20:08] <mhall119> tedg: do you know if those examples are still valid?  Some seem pretty old
[20:09] <tedg> mhall119, I believe so, but I haven't checked for a bit.
[20:09] <tedg> mhall119, The messaging menu is old as well ;-)
[20:10] <mhall119> ok
[20:10] <mhall119> thanks tedg
[20:11]  * tedg bitches a bit about kids these days "back when I was a kid we wished for examples from 2009!"
[20:13] <mhall119> well that would have made them examples from the future, so that would be pretty cool, yeah
[20:13] <mhall119> heck, when I was a kid, I'd have loves a *laptop* from 2009
[20:26] <bschaefer> thumper, ping
[21:08] <mokush> hey. does anybody know any usability reason/details why the dock is placed on the left side of the screen?
[21:17] <mhall119> thumper: do you know if there's a good description of the global menu somewhere I can copy/paste into these docs?
[21:21] <mhall119> gord: ^^ or maybe you know of something?
[21:43] <mhall119> anybody?