[00:32] <hamax> hi, anyone still here?
[00:36] <thumper> yes
[00:37] <hamax> I'm trying to change the behaviour of 'ShowCurrentWorkspace' but I can't find the code :)
[00:38] <hamax> I greped the whole unity 2D project and I still can't find it
[00:39] <thumper> what triggers ShowCurrentWorkspace?
[00:40] <hamax> libunity-2d-private/src/launcherapplication.cpp
[00:40] <hamax> calls
[00:40] <hamax> spread.asyncCall("ShowAllWorkspaces", m_application->desktop_file());
[00:41] <hamax> hm, I copied the wrong line, but it's the same call
[00:41] <popey> isnt that a qt thing?
[00:41] <popey> i.e. not a unity thing
[00:42] <hamax> spread is: QDBusInterface spread("com.canonical.Unity2d.Spread", "/Spread", "com.canonical.Unity2d.Spread");
[00:42] <hamax> I don't know
[00:42] <hamax> I played with qt once before, so...
[00:42] <hamax> I'm lost
[00:43] <hamax> spreadcontroll.cpp calls: Q_EMIT showCurrentWorkspace(applicationDesktopFile);
[00:46] <hamax> the result seems to be very specific
[00:46] <hamax> but it's possible that it's qt thing
[00:47]  * thumper doesn't know Qt
[00:48] <hamax> i don't even know what the q_emit thing is :)
[01:12] <FloatingGoat> mhall119: hey can you help me out
[01:13] <mhall119> FloatingGoat: maybe, what's your trouble?
[01:13] <FloatingGoat> you're michael hall right?
[01:13] <mhall119> yes sir
[01:14] <FloatingGoat> well i'm on your blog here and it says you made a unity dictionary lens. And ive been tinkering around for like 30 mins here trying to install it.
[01:15] <FloatingGoat> Is there something more to installing it than what is in the readme?
[01:15] <FloatingGoat> it's okay if you cant help
[01:22] <mhall119> FloatingGoat: well for starters, are you on oneiric or precise?
[01:23] <FloatingGoat> im on oneric
[01:23] <FloatingGoat> :o
[01:23] <FloatingGoat> oneiric*
[01:24] <mhall119> ok
[01:24] <mhall119> so my Dictionary lens uses my experimental Singlet library, so it's a little more difficult to install currently
[01:25] <mhall119> since singlet isn't packaged
[01:25] <mhall119> are you familiar with Python?
[01:25] <FloatingGoat> hmm interesting. did you make it yourself?
[01:25] <FloatingGoat> somewhat, I wrote a simple script once.
[01:25] <mhall119> yes
[01:26] <mhall119> ok, since I don't have singlet properly packaged, you'd have to do some ugly stuff to manually install it
[01:26] <mhall119> I would generally recommend not doing it
[01:27] <FloatingGoat> hmmm what kind of ugly stuff?
[01:27] <mhall119> sudo copying files into python system directories
[01:27] <FloatingGoat> is it risky or just difficult?
[01:28] <mhall119> a little bit of both
[01:29] <mhall119> FloatingGoat: hang on a minute and let me see if I can get a quick and dirty package made for you
[01:29] <FloatingGoat> because I am somewhat familiar with command line
[01:29] <FloatingGoat> file management
[01:29] <FloatingGoat> alright
[01:30] <FloatingGoat> I have 32 bit architexture
[01:30] <FloatingGoat> if you needed to know
[01:31] <mhall119> nope, it's all python, so it's architecture independent
[01:31] <FloatingGoat> hey and I have an idea for another lens/scope
[01:31] <mhall119> FloatingGoat: try installing the .deb here http://people.ubuntu.com/~mhall119/singlet/
[01:31] <FloatingGoat> not that you should make it but its an idea
[01:32] <mhall119> well if this package works for you, you can make it :)
[01:33] <FloatingGoat> alright
[01:33] <FloatingGoat> here goes nuthin
[01:34] <FloatingGoat> okay it installed
[01:35] <FloatingGoat> mhall119: now how do I see if it worked?
[01:35] <mhall119> FloatingGoat: ok, no in the directory with the dictionary-lens file
[01:36] <mhall119> run: python ./dictionary-lens make
[01:36] <mhall119> then: python ./dictionary-lens install
[01:36] <mhall119> after that you will need to restart Unity for it to find the new lens
[01:36] <FloatingGoat> oh should I put all the files in one folder, does it matter which?
[01:36] <mhall119> all which files?
[01:37] <FloatingGoat> the ones i got from your launchpad
[01:38] <mhall119> the install command will put them where they need to be
[01:38] <FloatingGoat> alright cool
[01:38] <FloatingGoat> that's what I had thought
[01:39] <mhall119> the make command generates the necessary files
[01:39] <mhall119> theinstall command puts them in the right system directories
[01:39] <mhall119> the install command needs to be run in sudo, I didn't mention that
[01:39] <FloatingGoat> permission denied.
[01:39] <FloatingGoat> so I
[01:39] <FloatingGoat> used sudo
[01:39] <mhall119> ^^
[01:41] <FloatingGoat> alright I restarted unity but it doesnt seem to be there
[01:41] <FloatingGoat> is there something that needs to be ran?
[01:42] <FloatingGoat> I have enchant and dictlient
[01:45] <FloatingGoat> when I run it in terminal, it says that it is searching for scopes.
[01:46] <mhall119> the install command ran okay
[01:46] <mhall119> ?
[01:46] <FloatingGoat> lemme check
[01:47] <FloatingGoat> well when I ran it, no errors were displayed. nothing was it jumped to a new line.
[01:48] <mhall119> hmmm....
[01:49] <FloatingGoat> "(process:20774): libunity-DEBUG: unity-scope-factory.vala:57: Searching for Scopes in /usr/share/unity/lenses/dictionary"
[01:49] <FloatingGoat> if that helps
[01:49] <mhall119> I think that's standard, it checks for 3rd party scopes that extend the lens
[01:50] <mhall119> is the icon showing in the dash?
[01:51] <FloatingGoat> no
[01:52] <mhall119> alright, then it's not finding the lens file
[01:52] <mhall119> ls -lha /usr/share/unity/lenses/dictionary/
[01:55] <mhall119> FloatingGoat: unfortunately I just upgraded to Precise yesterday....
[01:55] <FloatingGoat> drwxr-xr-x 2 root root 4.0K 2012-01-24 19:54 .
[01:55] <FloatingGoat> drwxr-xr-x 9 root root 4.0K 2012-01-24 19:39 ..
[01:55] <FloatingGoat> -rw-rw-r-- 1 root root  291 2012-01-24 19:54 dictionary.lens
[01:55] <FloatingGoat> -rw-rw-r-- 1 root root  291 2012-01-24 19:53 dictionary.lens~
[01:55] <FloatingGoat> -rw-rw-r-- 1 root root  11K 2012-01-24 19:39 dictionary-lens.svg
[01:55] <mhall119> well, it's there
[01:56] <FloatingGoat> oh no, should I do it too? maybe I will try it on my experiment partition.
[01:56] <mhall119> try running 'setsid unity' (that'll restart unity)
[01:57] <FloatingGoat> hmm I tried that before and just now but still it is not there.
[01:58] <mhall119> :/
[01:58] <mhall119> I'm worry dude, I'm not sure where to go from here
[01:58] <mhall119> all I can tell you is that I'll be getting Singlet finished up and easily installable for Precise, and I'll try and make the dictionary lens installable from the software center
[01:59] <mhall119> s/worry/sorry/
[01:59] <FloatingGoat> hmm okay it is cool. I'll try to tinker some more I guess and maybe ill get somewhere.
[02:00] <mhall119> let me know if you make any progress
[02:03] <FloatingGoat> okay.
[02:03] <FloatingGoat> also I have a cool idea for a scope or lense.
[02:03] <FloatingGoat> you wouldnt see it though.
[02:04] <FloatingGoat> its for when you get a chat notification. When the notification pops up you press super and you can type a reply and send it from the dash.
[02:05] <FloatingGoat> would that be difficult?
[02:14] <thumper> I think that is confusing the dash search for a generic entry field
[02:14] <thumper> which it isn't
[02:21] <bschaefer> thumper, hey, I have some more questions about valgrind. So I there are a lot of these but im not sure how to read them
[02:22] <bschaefer> ==2253== Conditional jump or move depends on uninitialised value(s)
[02:22] <bschaefer> ==2253==    at 0x508E79B: ??? (in /usr/lib/i386-linux-gnu/libpixman-1.so.0.24.2)
[02:22] <thumper> bschaefer: hi
[02:22] <bschaefer> ==2253==    by 0x7CC686B: ???
[02:22] <thumper> bschaefer: don't post heaps in here
[02:22] <bschaefer> ==2253==  Uninitialised value was created by a stack allocation
[02:22] <bschaefer> ==2253==    at 0x50798D4: ??? (in /usr/lib/i386-linux-gnu/libpixman-1.so.0.24.2)
[02:22] <thumper> bschaefer: use a pastebin
[02:22] <bschaefer> its small
[02:22] <bschaefer> that is all
[02:22] <thumper> bschaefer: that looks like a bug in libpixman :)
[02:22] <bschaefer> so I installed that libpixman from source but it still seemed to not get the debugging info
[02:23] <bschaefer> i know :), but there seems to be a lot of ?????? everywhere through the logs
[02:23]  * thumper looks at something
[02:24] <bschaefer> thumper, I figured that installing from source would install it with the correct debugging info which should get rid of the ??? for that spot
[02:24] <bschaefer> but some look just like this
[02:24] <bschaefer> ==2253==    by 0xBE8CC3FB: ???
[02:24] <bschaefer> and just a mem address isn't very helpful
[02:25] <FloatingGoat> mhall119: i GOT IT TO WORK
[02:25] <FloatingGoat> oops caps
[02:25] <FloatingGoat> ..
[02:27] <thumper> bschaefer: obviously it isn't running your version from shource
[02:28] <thumper> bschaefer: or you didn't compile with debug info
[02:28] <bschaefer> thumper, yeah, but that is the cause of the question marks?
[02:31] <thumper> bschaefer: valgrind can't find the debug info
[02:31] <bschaefer> thumper, alright, just want to make sure there wasn't a different cause. There is a lot of info that it puts out :)
[02:31] <thumper> bschaefer: yes there is :)
[02:32] <FloatingGoat> mhall119: is there any way to make the definitions open externally?
[02:32] <bschaefer> thumper, also have you taken a look at the update from the branch yesterday? I fixed a few loops in that file to use range based for loops
[02:34] <bschaefer> thumper, it really isn't a priority but curious if I was doing the range base for loops correctly; and that is such a better way to iterate through STL containers then the previous way!
[02:36] <thumper> bschaefer: for (auto it : _inner_main)
[02:36] <thumper> bschaefer: it isn't really an iterator any more
[02:36] <thumper> bschaefer: it is a reference to the item in the iterator
[02:36] <bschaefer> yeah...I should use a different name
[02:36] <thumper> bschaefer: so... for (auto icon : _inter_main)
[02:37] <thumper> bschaefer: a bit more of an issue when there is a param called icon
[02:37] <thumper> bschaefer: so you need a meaningful name
[02:38] <bschaefer> thumper, can you turn an arbitrary reference back into an iterator? One function was return an iterator so I didn't change that
[02:38] <thumper> bschaefer: no you can't
[02:38] <thumper> bschaefer: which one?
[02:38] <mhall119> FloatingGoat: \o/
[02:38] <mhall119> FloatingGoat: what do yu mean open externally?
[02:38] <mhall119> in something other than gnome-dictionary?
[02:39] <bschaefer> thumper, LauncherModel::at
[02:39] <FloatingGoat> mhall119: hmm
[02:39] <FloatingGoat> I dont think I have gnome-dictionaary
[02:39] <thumper> bschaefer: sure, leave that one alone
[02:39] <bschaefer> thumper, alright. Ill make those changes
[02:40] <mhall119> FloatingGoat: really?  It should be part of the base install
[02:41] <FloatingGoat> idk why it wasnt there
[02:41] <FloatingGoat> I just installed it
[02:41] <FloatingGoat> now this is aweeessommee
[02:41] <mhall119> huh, maybe it wasn't part of the default in 11.10...
[02:46] <bschaefer> thumper, hopefully icon_it sounds good. Though it isn't an actually iterator it is still iterating through all the icons.
[02:47] <FloatingGoat> mhall119: thanks for this, should I show other people?
[02:48] <bschaefer> thumper, and if I really wanted to return an iterator from the list I could keep an int i around and return (_inner.begin() + i); I believe. If it support bi directional it. (wont do it but just a thought)
[02:48] <mhall119> FloatingGoat: sure, just make sure they all know it's still pretty early stage
[02:48] <FloatingGoat> hmm okay
[02:49] <mhall119> as indicated by the 0.1 version number on that .deb
[02:49] <FloatingGoat> lol
[02:50] <FloatingGoat> btw why do you have the shortcut disabled by default?
[02:53] <mhall119> I couldn't think of a good one
[02:53] <mhall119> super+d is "show desktop" already
[02:55] <FloatingGoat> hmm i think c is fine.
[02:55] <FloatingGoat> btw im pretty sure all I had to do was mark the dictionary.lens file as an executable.
[02:56] <FloatingGoat> and it worked out
[03:03] <mhall119> hmmm, that could be, I'mnot sure what the permissions on .lens files shoudl be
[03:28] <FloatingGoat> mhall119: judging by what that one guy said, my idea wouldnt be that easy, would it?
[03:41] <FloatingGoat> because a lot of people find that feature in gnome shell useful, and while it is useful I find it too intrusive.
[03:44] <mhall119> FloatingGoat: what was your idea?
[03:45] <FloatingGoat> being able to press super and type a response in the event of a chat notification.
[03:45] <mhall119> ah, no, that's not what the dash/lenses are form
[03:45] <FloatingGoat> are for?
[03:46] <mhall119> having a lense that searches empathy and pidgen chat logs, now that would be very useful
[03:46] <mhall119> lenses are a way to let a user find something and access it
[03:46] <mhall119> not a way for them to respond to messages
[03:46] <FloatingGoat> I wish there was though, I find myself switchiing windows too often to get to mah chats.
[03:48] <mhall119> FloatingGoat: the message indicator lets you know when you have some
[03:48] <mhall119> I have empathy on my launcher in position #6, so I can get to it any time by pressing super+6
[03:50] <FloatingGoat> oh wow you are right I should have thought about that
[03:50] <FloatingGoat> but I half dont want empathy to be permanent but I guess ill try it.
[03:54] <FloatingGoat> hmm i've never really tried controlling unity from the keyboard til now
[03:54] <FloatingGoat> this is real nice
[03:58] <mhall119> FloatingGoat: if you make a generic lens (not using singlet) for searching chat history, people can add independend scopes to feed it with results from empathy, pidgin, whatever else
[03:59] <FloatingGoat> hmm I could try.
[03:59] <FloatingGoat> What about a graphing calculator lense?
[04:01] <mhall119> to return graphs?
[04:01] <mhall119> again, not really what they're for
[04:01] <FloatingGoat> hmm well I got a regular calculator goin here
[04:02] <mhall119> FloatingGoat: read https://wiki.ubuntu.com/Unity/Lenses#Responsibilities_of_a_Lens
[04:02] <mhall119> we're working on a better document about what lenses are/should be
[04:02] <mhall119> but that should give you a basic idea
[04:02] <mhall119> so really, they're a content-specific search interface
[04:03] <FloatingGoat> hmm so you dont like it when they are anything else?
[04:03] <mhall119> it breaks the user experience that we're trying to create
[04:03] <mhall119> the dash is a place to find things, not do things
[04:04] <FloatingGoat> when it lets me do things it makes my life easier.
[04:06] <mhall119> but it makes the dash more complex and slower to try and allow that
[04:08] <FloatingGoat> hmm. Well if you look at it technically. If an equation is graphable then its graph does exist in the real world. So you would technically be trying to find something.
[04:10] <mhall119> we don't have a letter of the law here, so if you break the intent you've pretty much broken the all there is
[04:10] <mhall119> nobody is going to say you can't
[04:10] <mhall119> just that it's not the kind of thing we wanted the Dash to do
[04:16] <FloatingGoat> alright
[04:17] <FloatingGoat> does unity have a function for doing?
[04:17] <mhall119> it has hooks for searcing and handling an item that's been  clicked on
[04:18] <mhall119> any "doing" should happen in one of those
[04:18] <mhall119> if you want to generate results based on a search, it will be in the search handler
[04:19] <mhall119> if you want to do something with just one of the results of the search, it would be in the activation handler
[04:24] <FloatingGoat> alright
[04:25] <FloatingGoat> do you know anything about that HIG that canonical was talking about?
[04:30] <FloatingGoat> nvm
[04:34] <FloatingGoat> im pretty sure that this dictionary lens is the best thing ever
[07:59] <Saviq> morning
[07:59] <dyams> saviq: morning
[08:00] <Saviq> hey tsdgeos
[08:01] <tsdgeos> hi
[08:01] <FloatingGoat> mhall119: I made a vid on how to install your lens
[08:02] <FloatingGoat> mhall119: im going to post it on le youtube
[08:19] <dyams> saviq: one issue with launcher and alt-f1
[08:20] <Saviq> dyams, wassup?
[08:20] <dyams> saviq: toggle the dash with super (show and hide)
[08:20] <dyams> saviq: now press alt-f1 fails to reveal launcher..
[08:21] <dyams> saviq: but second time pressing aft-f1 will work
[08:22] <Saviq> dyams, indeed, it seems to be thinking the launcher has focus, /methinks
[08:24] <dyams> saviq: ok
[08:24] <mhr3> Saviq, how fast does 2d dispatch search to lenses after you type something to the search entry?
[08:24] <mhr3> Saviq, and btw good morning :)
[08:25] <Saviq> mhr3, hey
[08:27] <Saviq> mhr3, trying to find out
[08:30] <Saviq> mhr3, no timeout that I can see
[08:30] <mhr3> oh... interesting
[08:32] <Saviq> mhr3, every change in the search entry results in a search being performed
[08:34] <mhr3> somehow my 2d is crashing all the time :/
[08:35] <dyams> mhr3: unity-2d-places?
[08:35] <mhr3> dyams, no, panel
[08:37] <mhr3> dyams, oh, nevermind it is places actually
[08:37] <dyams> mhr3: ah..
[08:38] <dyams> mhr3: update from daily ppa.
[08:58] <tsdgeos> dyams: answered your comments at https://code.launchpad.net/~aacid/unity-2d/unity-2d_test_alt_f2_pops_dash/+merge/89873 not sure if they make you happy
[08:59] <elvisd> Hello
[08:59] <elvisd> I'm testing HUD in eclipse in my daily work and recorded some strange behaviors
[09:00] <elvisd> where can i save the video and report them
[09:00] <elvisd> ?
[09:03] <dyams> tsdgeos: I see...one sec...in meeeting
[09:04] <tsdgeos> dyams: sure, no hurries
[09:09] <Saviq> tsdgeos, "./launcher/autohide_show_tests.rb:33: warning: already initialized constant WIDTH" - ideas?
[09:10] <tsdgeos> nope
[09:10]  * tsdgeos checks
[09:10] <tsdgeos> ah yes
[09:10] <tsdgeos> i think gerry moved that to run_tests.rb ?
[09:10] <tsdgeos> Saviq: is that on -shell ?
[09:10] <Saviq> tsdgeos, yes, merging into -shell
[09:11] <tsdgeos> ok, no he did not move anything :D
[09:11] <Saviq> ;)
[09:12] <tsdgeos> does that happen in non-shell too?
[09:12] <tsdgeos> maybe ./always_visible_tests.rb:33 "overlaps" with ./autohide_show_tests.rb:33 ?
[09:12] <Saviq> yeah might be
[09:13] <tsdgeos> find it weird though
[09:13] <Saviq> yeah that would make sense
[09:13] <Saviq> we need LAUNCHER_WIDTH abstracted anyway
[09:13] <Saviq> hey greyback
[09:14] <greyback> Saviq: morning.
[09:15] <tsdgeos> nerochiaro: ping
[09:15] <Saviq> greyback, I'm merging trunk into shell, getting http://pastebin.ubuntu.com/816242/ - doesn't look like a "proper" failure?
[09:16] <nerochiaro> tsdgeos: yes ?
[09:16] <htorque> hi all! what's the expected behavior when i press the super key with an application menu opened?
[09:16] <htorque> right now it does nothing, maybe it's supposed to close the menu and open the dash?
[09:17] <tsdgeos> nerochiaro: you have "When dash is active, pressing 'Super+S' to invoke spread is getting 's' character being entered in Dash search box" assigned to you in the kanban, want me to have a look? Or you started already?
[09:17] <nerochiaro> tsdgeos: didn't start, if you're not busy with anything else feel free to have a look
[09:17] <nerochiaro> Saviq: why the nested verifys ?
[09:18] <tsdgeos> nerochiaro: you verify that something will not happen in 2 seconds
[09:18] <tsdgeos> Saviq: object expected? that test works in non-shell afair
[09:19] <greyback> Saviq: yep, looks like a proper fail. launcher must hide after clicking bfb twice
[09:19] <Saviq> greyback, the failure message is cryptic, though?
[09:20] <tsdgeos> wait
[09:20] <tsdgeos> no launcher should not hide when clicking the bfb twice
[09:20] <tsdgeos> the mouse is still over the launcher
[09:20] <tsdgeos> why should it hide?
[09:20] <greyback> Saviq: agreed. Which is why it took me 4 minutes, in my semi-woken & head-ached state :)
[09:20] <Saviq> greyback, :)
[09:20] <greyback> tsdgeos: it shouldn't
[09:21] <tsdgeos> greyback: you said " launcher must hide after clicking bfb twice"
[09:21] <greyback> tsdgeos: yep, that is what I suspect is happening (badly phrased, sorry)
[09:21] <tsdgeos> ah
[09:21] <Saviq> and now the test passed
[09:22] <dyams> nerochiaro: tsdgoes: toggle the dash with super (show and hide)
 saviq: now press alt-f1 fails to reveal launcher..
 saviq: but second time pressing aft-f1 will work
[09:22] <Saviq> tsdgeos, and indeed the WIDTH must be conflicting from always_visible
[09:22] <tsdgeos> Saviq: weird
[09:22] <tsdgeos> Saviq: what happened for it to pass, nothing?
[09:23] <Saviq> and now it failed again
[09:23] <dyams> saviq: nerochiaro: greyback: tsdgoes: Gentle Reminder - we should discuss about multi monitor - shell today.
[09:23] <greyback> Saviq: you're watching it, is the UI acting the same?
[09:24] <Saviq> dyams, yeah, we need Kaleo for that, too
[09:24] <Saviq> greyback, trying a manual test
[09:24] <dyams> kaleo: pls let us know when you are available
[09:24] <dyams> saviq: true
[09:25] <nerochiaro> dyams: include Kaleo too. can you please organize a time that's good for everyone involved ?
[09:26] <dyams> nerochiaro: yes, lets do it immediately after the shell stand up.
[09:26] <nerochiaro> dyams: works for me. hope it's not too late
[09:26] <dyams> kaleo: saviq: nerochiaro: greyback: tsdgoes: Is that good for you all
[09:26] <greyback> good for me
[09:26] <tsdgeos> me too
[09:27] <Saviq> dyams, yup, fine for me
[09:27] <dyams> kaleo: (?) ping
[09:27] <Kaleo> yes
[09:27] <Kaleo> good for me
[09:28] <dyams> kaleo: saviq: nerochiaro: greyback: tsdgoes: Ok, we will extend the today's 'shell - start up' little bit more then.
[09:28] <Saviq> dyams, re tests file naming - we can always move them around later
[09:29] <Saviq> as we only have two tests now, they might just as well sit in places-tests
[09:30] <dyams> saviq: no prob
[09:31] <tsdgeos> Saviq: can you note that in the MR so it shows we "solved" all the issues dyams? Or want me to do it?
[09:31] <Saviq> tsdgeos, just do it
[09:31] <tsdgeos> ok
[09:32] <tsdgeos> done
[09:32] <tsdgeos> Saviq: any progress with that random failing test?
[09:32] <Saviq> tsdgeos, still failing randomly
[09:32] <Saviq> depends what you call progress
[09:32] <Saviq> it didn't fail when I only run this one
[09:32] <tsdgeos> :-/
[09:32] <Saviq> in, like, 20 tries
[09:32] <tsdgeos> aha
[09:33] <Saviq> but if I run the autohide_show suite
[09:33] <Saviq> then one out of 2-3 times it will fail
[09:33] <Saviq> the behavior when trying manually is correct, though
[09:33] <tsdgeos> seems we carry on some weird state?
[09:36] <Saviq> yeah trying some more things, too
[09:36] <dyams> greyback: https://code.launchpad.net/~unity-2d-team/unity-2d/filter-option-compact-shell/+merge/89874
[09:36] <dyams> saviq: https://code.launchpad.net/~unity-2d-team/unity-2d/update-launcher-pips-shell/+merge/89679
[09:37] <Saviq> dyams, thanks
[09:37] <dyams> saviq: greyback: i have updated them again. check it once pls
[09:40] <Kaleo> dyams: can you do a write up of what the status and questions are around the multi monitor work?
[09:42] <dyams> Kaleo: I just started it yesterday, do segregate the shell stuff
[09:43] <greyback> dyams: will do
[09:44] <dyams> kaleo: Earlier when launcher and shell were separate applications
[09:44] <dyams> kaleo: i worked on multi monitor stuff already
[09:44] <Kaleo> dyams: I meant, not an IRC write up
[09:44] <Kaleo> dyams: :)
[09:45] <dyams> kaleo: :) Ok
[09:45] <tsdgeos> greyback: can I get https://code.launchpad.net/~aacid/unity-2d/unity-2d_test_alt_f2_pops_dash/+merge/89873 merged? I'd like to do more places tests and put them in that very same file
[09:46] <Saviq> dyams, please also describe the target for 12.04
[09:46] <dyams> saviq: lemme check
[09:46] <greyback> tsdgeos: ok
[09:46] <Saviq> target as in: what needs to be done
[09:47] <dyams> saviq: ah..I'll
[09:47] <dyams> saviq: did you check this gdoc already?
[09:47] <Saviq> nope, no gdoc I saw
[09:48] <dyams> saviq: UX spec i mean
[09:48] <dyams> saviq: http://design.canonical.com/the-toolkit/unity-multi-monitor-interactions/
[09:48] <tsdgeos> greyback: nice, thanks
[09:48] <greyback> tsdgeos: np
[09:48] <nerochiaro> greyback: to change dconf settings from a test do you have any special way or do i just use the cmd line tool ?
[09:49] <Saviq> dyams, I _think_ I saw it, not that I analyzed it enough to know what needs to be done
[09:49] <greyback> dyams:
[09:49] <greyback> oops, ignore that ^^
[09:49] <Saviq> nerochiaro, `gsettings get/set` is what's used now
[09:49] <greyback> nerochiaro: no special way
[09:50] <Saviq> dyams, I assume you read that already, so you can distill for us what we need to support?
[09:50] <greyback> dyams: please make up a GDoc with a bullet point summary of the tasks that need to be done, based on the UX spec. That way we'll have an item-by-item discussion on what do to
[09:50] <greyback> dyams: and also save us digesting that whole spec
[09:51] <dyams> greyback: OK
[09:52] <dyams> greyback: lets take it piece by piece...
[09:52] <greyback> dyams: share it so we can all edit it. We'll be adding notes as the discussion progresses
[09:53] <greyback> dyams: and when we're done, it'll be a guide to follow to completion of the task
[09:53] <dyams> greyback: ok
[09:53] <dyams> greyback: agreed
[10:03] <nerochiaro> greyback: so the final work on tests that require changing something like the screen resolution is that we run them only with the current resolution and check we do the right thing for that resolution, right ?
[10:03] <nerochiaro> s/work/word
[10:04] <greyback> nerochiaro: yes
[10:04] <greyback> nerochiaro: I see no easy elegant solution to that problem right now
[10:04] <nerochiaro> greyback: ok
[10:27] <ideaguy> hi, I'm looking for someone from unity development team. thanks
[10:29] <Saviq> ideaguy, see the channel name? I'd say you're in the right place :)
[10:30] <ideaguy> but probably not every1 is actually involved in unity, e.g. I'm just a user and want to ask a question
[10:31] <ideaguy> there's one feature that I extremely lack in unity (and lots of my collegues) and I was worndering if such feature shall be developed
[10:33] <ideaguy> more precisely - switching between windows of the same application using alt-"~" is very unconfortable. It's very hard to get to the right window. While other UI's have simple switching option with moving mouse on the icon of the application and then it shows a (small or medium) list of open instances (windows) of that application. My question: shall such feature appear in unityt, 12.04 maybe ?
[10:37] <tsdgeos> nerochiaro: ping
[10:37] <nerochiaro> tsdgeos: yes ?
[10:37] <tsdgeos> nerochiaro: are you aware -shell kills dragging?
[10:38] <nerochiaro> tsdgeos: dragging of what to where ? but yes, now that you mention it i wouldn't be surprised
[10:38] <tsdgeos> nerochiaro: at least inside kmail, might be a kmail "bug", can't repro it in any other program
[10:38] <nerochiaro> tsdgeos: can you drag icons from desktop to launcher ?
[10:38] <nerochiaro> tsdgeos: and stuff from dash to launcher
[10:39] <tsdgeos> i don't have "a desktop"
[10:39] <nerochiaro> tsdgeos: you don't ?
[10:39] <tsdgeos> i mean, i have but it's empty
[10:39] <tsdgeos> i can drag from dash to launcher yes
[10:40] <nerochiaro> tsdgeos: try putting a .desktop file on the desktop and dragging that too
[10:40] <nerochiaro> tsdgeos: if it shows the + icon over the launcher then all the dragging functionality that i know was available in trunk is still there
[10:40] <nerochiaro> tsdgeos: what do you expect to happen when you drag something from kmail ?
[10:40] <tsdgeos> nerochiaro: well, i can drag mails in kontact in trunk and i can't in shell
[10:41] <tsdgeos> nerochiaro: dragging from kontact to itself is what fails
[10:41] <nerochiaro> tsdgeos: oh, i see
[10:41] <tsdgeos> which is weird
[10:41] <tsdgeos> and can't repro in any other program
[10:41] <tsdgeos> be it Qt or kde or gtk
[10:42] <tsdgeos> probably they are doing something weird that gets triggered by the shell being "over everything"
[10:42] <nerochiaro> tsdgeos: most likely, but i'm not sure how to verify
[10:43] <tsdgeos> yeah :/
[10:43] <tsdgeos> way to verify its not our bug would be proving its their bug :D
[10:44] <nerochiaro> tsdgeos: yeah, always the smart way ;)
[10:44] <greyback> nerochiaro: you're removing DashSettings in shell, yes?
[10:44] <nerochiaro> greyback: in trunk
[10:44] <greyback> nerochiaro: ah good, ok
[10:45] <Saviq> ideaguy, such a question would probably fit better in #ubuntu-design
[10:45] <Saviq> ideaguy, did you try to click on the icon when you have multiple windows?
[10:46] <tsdgeos> Saviq: what do i do with the "Intellihide Alt+F1+Esc fix" kanban card, put it on "Ready to test" or on "Tested" ?
[10:47] <Saviq> tsdgeos, didn't I merge it already?
[10:47] <tsdgeos> Saviq: yes you did, so "Tested" ?
[10:47] <Saviq> tsdgeos, packaging, as all the rest
[10:47] <tsdgeos> Saviq: well on the "bugs" part there is no packaging
[10:47] <Saviq> tsdgeos, hrmpf
[10:47] <Saviq> tsdgeos, Tested, then
[10:48] <tsdgeos> ok
[10:52] <nerochiaro> tsdgeos: what was the way to get multiple objects out of a testability query ? like @app.AppNameApplet().AbstractButton => 3 of them ?
[10:52] <tsdgeos> nerochiaro: children
[10:52] <ideaguy> Saviq: thanks, I'll try at ubuntu-design. And I know for sure that such feature does not exist atm.
[10:53] <Saviq> ideaguy, no, but something similar does
[10:53] <tsdgeos> nerochiaro: @app.AppNameApplet().children( filter )
[10:53] <Saviq> ideaguy, if you click on an item in the launcher that has multiple windows
[10:53] <Saviq> it will invoke the spread with just that application
[10:53] <nerochiaro> tsdgeos: ok thanks
[10:53] <ideaguy> Saviq: it does not display any ifnromation about multiple windos
[10:53] <Saviq> ideaguy, if you click on it, yes it does
[10:53] <Saviq> it will show the spread with the windows filtered
[10:54] <Saviq> ideaguy, it will only spread one workspace if all windows of this application are on current workspace
[10:54] <Saviq> otherwise it will just spread all of them
[10:54] <ideaguy> Saviq: well yes, If I click on it again I get all the windows in the workspace
[10:55] <ideaguy> but in such way I cant distinguish wich is which - e.g. they all look the same
[10:55] <Saviq> ideaguy, how else would you distinguish them?
[10:55] <Saviq> ideaguy, you can also go dblclick to go straight to the spread without first switching to the app's last window
[10:55] <ideaguy> Saviq: e.g. clicking on icon would give me small menu with the names of each window
[10:56] <greyback> Saviq: he's asking for a list of window titles
[10:57] <greyback> ideaguy: I agree, when I've many terminals open, I cannot easily distinguish them in the Spread
[10:57] <Saviq> greyback, that's why you should only have one terminal with byobu in it ;)
[10:57] <Saviq> tbh I rarely have many windows of just one app open
[10:57] <ideaguy> Saviq: I mainly work with text and the window name usually includes filename - then the list of winow names would help me to switch between the windows I want, e.g. I would want to see a small window with:  editor: file1.txt,  editor file2.txt,  editor: file3.txt (in a column)
[10:58] <Saviq> ideaguy, I get what you're saying, was just trying to show you the feature that's closest to what you're asking for
[10:58] <ideaguy> greyback: indeed! I believe you understand me very well
[10:58] <greyback> Saviq: on come on, this is the 21st century! 'screen' can't the pinnacle of terminal management
[10:58] <Saviq> ideaguy, either way, it's best to pick that up in #ubuntu-design or file a feature request bug with your ideas
[10:58] <Saviq> greyback, screen - no, byobu - yes
[10:59] <ideaguy> Saviq: thanks, but I find that feature (tilting windows) very unuseful
[10:59] <greyback> ideaguy: yep, what Saviq said. Designers do read them
[10:59] <ideaguy> because now I always have dockbarx running on top of unity
[11:00] <Saviq> ideaguy, also, make sure you try out <super>+number shortcuts
[11:00] <Saviq> that doesn't solve your issue, that I get, but might help nevertheless
[11:00] <ideaguy> Saviq: thanks, but again - give one number for *all* instances of the same application
[11:01] <Saviq> ideaguy, yes, that's why I said it doesn't solve your issue
[11:01] <ideaguy> many thanks guys, I'll try at ubuntu-design
[11:02] <ideaguy> I really don't want to drop using ubuntu
[11:07] <Saviq> nerochiaro, Kaleo you there
[11:07] <Saviq> ?
[11:08] <nerochiaro> Saviq: i am
[11:08] <nerochiaro> in the mumble chat i mean
[11:29] <tsdgeos> Saviq: going to create a new card for the "always visible launcher pushes itself to the right" bug
[11:29] <Saviq> tsdgeos, please do
[12:16] <Saviq> tsdgeos, nerochiaro, dyams I just merged trunk into shell - make sure to pull / merge
[12:16] <tsdgeos> nice
[12:33] <tsdgeos> nerochiaro: Saviq: just realized "Fix shell struts / resize going awry" card is the same as my "Always visible launcher pushes itself" card, right?
[12:34] <nerochiaro> tsdgeos: checking
[12:34] <Saviq> tsdgeos, ah yeah I think so
[12:34] <Saviq> tsdgeos, sorry
[12:34] <Saviq> I forgot I added that yesterday
[12:34] <tsdgeos> Saviq: so i kill the one assigned to nerochiaro then?
[12:35] <Saviq> tsdgeos, if you're working on it - yea
[12:35] <nerochiaro> as Saviq said
[12:35] <tsdgeos> i'm not working on it anymore as i've finished already
[12:35]  * tsdgeos runs :D
[12:36] <Saviq> tsdgeos, cool, you'll be able to start tackling one of the bigger issues then ;P
[12:36] <tsdgeos> tsdgeos: sure, which one you want me to start next?
[12:38] <Saviq> tsdgeos, talkin' to yourself already, eh?
[12:38] <tsdgeos> yes
[12:38] <tsdgeos> craaaaaaaaaaazy
[12:38] <tsdgeos> :D
[12:38] <Saviq> tsdgeos, do you have a second screen handy?
[12:38] <tsdgeos> almost lunch time thinking with my stomach
[12:39] <Saviq> actually, since you touched that already
[12:39] <Saviq> take on the Alt+F1 / Super thing
[12:39] <tsdgeos> Saviq: i do have one, last time i tried my display port did not give me the correct resolution, i had to patch the kernel to fix it, not sure if the patch i was given made it to proper ubuntu already
[12:39] <tsdgeos> Saviq: ok, that'd be easier :D
[12:40] <Saviq> tsdgeos, there're two broken usecases in there
[12:40] <tsdgeos> Saviq: is there a card for that
[12:40] <tsdgeos> ?
[12:40] <Saviq> tsdgeos, they are there in the description
[12:40] <Saviq> the card is the last one in backlog
[12:40] <Saviq> last red one
[12:41] <Saviq> "Fix Alt+F1 / Super..."
[12:41] <tsdgeos> oki
[12:42] <tsdgeos> moved to coding and assigned to me
[12:51] <Saviq> tsdgeos, your super+s test needs fixin'
[12:51] <Saviq> tsdgeos, just commented on the MR
[12:51] <Saviq> I wasn't able to fail it, but it might be related
[13:06] <Saviq> tsdgeos, with unity-2d-spread from -shell I can see the "s" appearing in the search entry
[13:06] <Saviq> but the test doesn't fail, but I might have adapted the test wrong
[13:07] <Saviq> I put the adapted diff in LP
[13:08] <nerochiaro> Kaleo: Saviq: good and bad news at the same time. there's a way to reparent a QDeclarativeItem by calling setParentItem on it. However when i do that with items from different views the application crashes
[13:09] <Saviq> nerochiaro, did you do some simple test app or did you try to do it with the shell?
[13:10] <nerochiaro> Saviq: test app (based on a gutted out unity-2d-places just to make things quicker)
[13:10] <Saviq> mhm, so where's the good news? ;)
[13:10] <nerochiaro> Saviq: that there's a way to do it. I didn't even think that there was an API allowing it
[13:11] <Saviq> nerochiaro, it's probably there to use within one viewport :/
[13:11] <Saviq> we're actually abusing it somewhere
[13:11] <nerochiaro> Saviq: yeah, i'm checking but that's how it looks like
[13:11] <nerochiaro> the thing is
[13:12] <nerochiaro> a declarative _view_ is just a view, one should be able to have two views on the same scene
[13:12] <nerochiaro> Saviq: ^
[13:12] <nerochiaro> but i guess when declarativeview loads a qml file it creates a new scene
[13:12] <nerochiaro> implicitly
[13:13] <Saviq> mhm
[13:13] <nerochiaro> Saviq: QDeclarativeItem objects can be placed on a standard QGraphicsScene and displayed with QGraphicsView. QDeclarativeView is a QGraphicsView subclass provided as a convenience for displaying QML files, and connecting between QML and C++ Qt objects.
[13:14] <nerochiaro> and
[13:14] <nerochiaro> The QGraphicsView class provides a widget for displaying the contents of a QGraphicsScene.
[13:14] <nerochiaro> so if we could just have one graphics scene and multiple views...
[13:14] <Saviq> nerochiaro, but the scene would have to span all the displays
[13:14] <Saviq> and hence we could have a single view
[13:14] <Saviq> or am I mixing things up?
[13:15] <nerochiaro> Saviq: no, the scene is an abstract concept. it's an infinite plane where all your objects live. a view is like a viewport, a window, on a part of the scene (or the entire scene if you want, which is the default)
[13:15] <Saviq> oh
[13:15] <Saviq> that would be awesome
[13:15] <nerochiaro> but probably a lot of work
[13:15] <Saviq> we could move the dash within the scene
[13:16] <Saviq> and the viewports would just show part of the scene
[13:16] <nerochiaro> something like that, yes
[13:16] <Saviq> that would be the best of both worlds, if you ask me
[13:16] <Saviq> Kaleo, &
[13:16] <Saviq> Kaleo, ^
[13:17] <nerochiaro> Saviq: my guess is: it's possible, but you have to manually provide all the connective stuff that QDeclarativeView provides on top of QGraphicsView manually
[13:18] <Saviq> I wonder how many there are
[13:18] <nerochiaro> Saviq: all the stuff to handle declarative engines and contexts
[13:18] <Saviq> the QGraphicsView doc explicitly says: "Several views can observe a single scene"
[13:19] <nerochiaro> Saviq: yes, that what i'm saying. the problem is how declarativeview sets things up. i bet when you call setSource it will create a new scene
[13:20] <nerochiaro> Saviq: and i'm sure it can be done manually, but it's probably quite a lot of work if Qt provides you a convenience class for it
[13:20] <nerochiaro> that said, sounds lots of fun to try :)
[13:21] <nerochiaro> Saviq: however it might also be worth a shot to check why QT crashes when we "abuse" the setParentItem. maybe it's actually meant to be possible to but it crash for some bug
[13:22] <Saviq> yup
[13:33] <Saviq> hey greyback, any idea why the recent tests would launch unity-2d-launcher when finished?
[13:33] <Saviq> has something like that been added?
[13:34] <greyback> Saviq: not that I'm aware of. Checking
[13:34] <Saviq> greyback, don't, it's probably related to the spread being run from installed
[13:38] <greyback> hmmm, nevertheless we need better way to ensure apps are restarted cleanly & killed properly in tests. kills are inelegant & not reliable
[13:38] <Saviq> nerochiaro, http://qt.gitorious.org/qt/qt/blobs/4.8/src/declarative/util/qdeclarativeview.cpp
[13:39] <Saviq> nerochiaro, QDeclarativeScene is simple enough
[13:39] <nerochiaro> Saviq: but the problem is QDeclarativeView, not scene
[13:40] <Saviq> nerochiaro, I know it is
[13:40]  * Saviq is reading further down
[13:40] <nerochiaro> :)
[13:41] <Saviq> nerochiaro, http://qt.gitorious.org/qt/qt/blobs/4.8/src/declarative/util/qdeclarativeview.cpp#line282
[13:42] <Saviq> so yeah, each QDeclarativeView is handling its own Scene
[13:42] <nerochiaro> Saviq: which is not accessible from the outside either
[13:42] <Saviq> yup, it's private
[13:43] <Saviq> I wonder if that's per design or just something they omitted for now
[13:45] <Saviq> damn, that would be exactly what we need
[13:46] <nerochiaro> Saviq: i think it's by design, the same way all QDeclarativeItem subclasses aren't even exposed in the public API.
[13:46] <nerochiaro> the declarative API is high level, if you want to use the graphics view you have to do so explicitly
[13:46] <nerochiaro> (my opinion only, of course)
[13:47] <tsdgeos> Saviq: test doesn't fail for you in -shell?
[13:47] <tsdgeos> weird
[13:47] <Saviq> tsdgeos, nope
[13:47] <tsdgeos> i tried and it failed, let me check again
[13:49] <Saviq> tsdgeos, be sure to run the spread from -shell
[13:50] <tsdgeos> Saviq: why would that make a difference ?
[13:51] <Saviq> tsdgeos, well, it launched unity-2d-launcher here, for example
[13:51] <Saviq> it's done that over dbus probably
[13:51] <tsdgeos> the spread you mean?
[13:51] <tsdgeos> i see
[13:51] <Saviq> yes
[13:52] <Saviq> tsdgeos, that's why I said in the test that you should kill / run the current spread, too
[13:52] <tsdgeos> yep read that
[13:53] <tsdgeos> Saviq: fails here
[13:53]  * tsdgeos scratches head
[13:55] <tsdgeos> hmm
[13:55] <Saviq> tsdgeos, with the diff I posted in the commenT?
[13:56] <Saviq> maybe I failed to port the test to -shell?
[13:56] <tsdgeos> Saviq: can you try commenting the rest of the tests in the file?
[13:56] <Saviq> tsdgeos, sure, sec
[13:56] <tsdgeos> Saviq: seems we have again the case in which that test alone works but together with the others not
[13:56] <tsdgeos> Saviq: yes, with your diff + killing/starting spread
[13:56] <tsdgeos> but worked withoug killing/starting spread too
[14:00] <Saviq> tsdgeos, nope, doesn't fail regardless
[14:00] <tsdgeos> really?
[14:00]  * tsdgeos sad
[14:00] <nerochiaro> Saviq: https://pastebin.canonical.com/58746/ << it seems we were not abusing anything, it's meant to be possible to move items between scenes it seems
[14:01] <tsdgeos> Saviq: ok, leave it with me, i'll try to make the full test pass here at least and then come back to you
[14:01] <Saviq> nerochiaro, at least for qgraphicsitem
[14:02] <nerochiaro> Saviq: all QDeclarativeItems are QGraphicsItems
[14:02] <nerochiaro> Saviq: and the crash happens in that function from what i can see
[14:02] <Saviq> oh ok
[14:04] <Saviq> tsdgeos, isn't there a verify_notequal?
[14:04] <Saviq> the verify_true() { x != y } looks convoluted
[14:04] <tsdgeos> Saviq: nope
[14:04] <Saviq> :/
[14:05] <Saviq> bbiab
[14:05] <burli> hi
[14:05] <burli> I have add a Bug report https://bugs.launchpad.net/unity/+bug/921577
[14:06] <burli> but I can't add a tag for HUD. Can someone add this tag, if possible?
[14:08] <nerochiaro> Saviq: https://bugreports.qt.nokia.com/browse/QTBUG-23070 and https://bugreports.qt.nokia.com/browse/QTBUG-6932 looks like we're not the only ones with this issue. even though they get asserts which i can't find in the code
[14:09] <nerochiaro> Saviq|afk: oh, actually i can, but my crash is different
[14:09] <burli> Oh, there are some duplicates. Oops
[14:10] <nerochiaro> Saviq|afk: in any case, we're supposed to be able to do that, but it's broken in QT. Let's mumble with Kaleo when he comes back to figure out what to do now that we know what our options are
[14:15] <tsdgeos> Saviq|afk: this works for me (i.e. last test gives a failure in unity-2d-shell) http://paste.kde.org/~tsdgeos/192638/
[14:20] <tsdgeos> back in a sec
[14:46] <didrocks> greyback: hey hey :)
[14:46] <greyback> didrocks: hello
[14:46] <didrocks> greyback: so, I implemented the options in control-center for 3D, I think there is only one that can be applied to 2D (which is the autohide mode, isn't it?
[14:47] <greyback> didrocks: oh yes, I was to mail you about that
[14:47] <greyback> didrocks: so right now, auto-hide is only one, yeah
[14:47] <greyback> didrocks: we need to re-introduce the corner-reveal-launcher thing
[14:47] <didrocks> do you think it will hard for you to implement the other 2 that are in 3D right now?
[14:47] <didrocks> yeah, corner-reveal
[14:48] <didrocks> (which is just "reveal if x=y=0)
[14:48] <greyback> didrocks: corner reveal is just digging up old code, should not be much work
[14:48] <didrocks> not the proximity effect
[14:48] <didrocks> and launcher size
[14:48] <greyback> didrocks: the resizable launcher is more work. Kaleo did work on it, but we're hesitating over it
[14:49] <didrocks> greyback: hum, I need to know that quite early so that I hide or not the option depending on the session :)
[14:49] <greyback> didrocks: ok, let me call ppl together and we'll chat about it. Then I'll let you know
[14:49] <greyback> Kaleo: Saviq|afk ping
[14:50] <didrocks> greyback: excellent, thanks!
[14:50] <greyback> didrocks: I'll get back to you asap
[14:50] <didrocks> no worry ;)
[14:50] <greyback> well I'd like this decided quickly too :)
[14:55] <jml> how can I reorder icons on the launcher?
[14:56] <seb128> jml, click on them and stay clicked for a second
[14:56] <seb128> or dnd to the right
[14:56] <jml> seb128, thanks!
[14:56] <seb128> jml, yw
[14:56] <seb128> jml, still not obvious enough it seems ;-)
[15:01] <balloons> is HUD unity2d compatible? Any consideration for unity2d in the design?
[15:01] <greyback> didrocks: disable the resizable launcher in 2d please
[15:02] <greyback> balloons: it's being worked on for Unity2D right now
[15:02] <balloons> awesome, so unity2d will be supported in the final release?
[15:04] <didrocks> greyback: ok then
[15:04] <greyback> balloons: yes, it's on the roadmap
[15:31] <mhall119> what's the long-term goal for unity/unity2d, do we want to eventually use just one, or continue to develope them separate?
[15:32] <Saviq> greyback, wassup?
[15:35] <Saviq> greyback, ok, so "proximity" I don't know, resizable launcher we can do, but it will be like 1-2 days work, corner reveal - no digging up old code, but very simple to do with current qml-based behaviors
[15:51] <jml> is there a way to discover the default unity keybindings in the unity that's in precise?
[15:51] <jml> I thought it was long-press super
[15:51] <jml> but that doesn't do much for me.
[15:54] <mhall119> jml: that's it, it was working for me this morning
[15:55] <jml> mhall119, that shows me the shortcuts on the launcher but not things like Super+w
[15:59] <mhall119> jml: I geet an overlay in the middle of the screen, check ccsm to see if it's disabled for you
[16:01] <jml> mhall119, it's a clean install, I don't have CCSM installed
[16:01] <jml> (although I'll install & check
[16:01] <jml> )
[16:02] <mhall119> I know you can disable it, but I thought it was on b y default
[16:15] <greyback> Saviq: got a few minutes, would like your opinion/advice?
[16:15] <Saviq> greyback, sure
[16:15] <Saviq> mumble?
[16:15] <greyback> Saviq: lemme share a quick doc with you first
[16:16] <greyback> Saviq: yep, mumble 1-1 roo, when you're ready
[16:18] <Saviq> greyback, just one thing - what's supposed to happen when the launcher is on screen? the HUD shows up next to it?
[16:25] <greyback> Saviq: I believe launcher hides & HUD appears
[16:25] <Saviq> greyback, oof
[16:25] <Saviq> greyback, either way
[16:25] <Saviq> you'll be fine
[16:25] <mhall119> tedg: gord: We still have a few sections of https://wiki.ubuntu.com/Unity/HUD that need to be filled in
[16:26] <greyback> Saviq: yeah, I'm not too worried
[16:26] <greyback> just need to get the little things right
[16:27] <gord> greyback, do you have the hud showing on alt yet?
[16:27] <greyback> gord: I've bindings made up, now working on UI
[16:28] <gord> greyback, put a video in totem and watch your bindings activate like crazy ;) they send alt every 30 seconds to inhibit the screensaver
[16:28] <gord> i'm going to distropatch that out, but its funny so i'm telling everyone
[16:28] <greyback> gord: that's hilarious
[16:28] <greyback> lol
[16:28] <mhall119> gord: isn't there an actually API for disabling the screensaver?
[16:29] <gord> mhall119, not sure what i can fill out there
[16:29] <gord> mhall119, yeah there is, they do that too, but yeah. i don't know what on earth they are thinking
[16:29] <mhall119> gord: something to help people get setup for hackong on the code
[16:29] <gord> mhall119, hrm okay, i'll see if i can do something there tomorrow
[16:30] <mhall119> gord: anything under "Developing for the HUD" too, for app authors to create hint files, etc
[16:30] <mhall119> and how they can check their apps's menus against the HUD's matching algorithm
[16:33] <tsdgeos> greyback: don't merge the test about Meta_s yet, might be not correct
[16:34] <jml> mhall119: have just checked in ccsm... where exactly is the option for showing the keyboard shortcut display on long-press Super?
[16:35] <tsdgeos> Saviq:         onActiveChanged: if (!dash.active) search_input.text = ""
[16:36] <tsdgeos> Saviq: the other option is clearing the text on show instead of on hide...
[16:36] <mhall119> jml: I don't recall exactly
[16:36] <mhall119> and I'm currently on my netbook, which is still 11.10
[16:36] <tsdgeos> Saviq: but that'd be modifying the code to help the test, which is cheating :D
[16:36] <Saviq> tsdgeos, we will actually have to defer that clearing, too, when we enable fade in / out
[16:36] <jml> mhall119: oh well.
[16:38] <Saviq> tsdgeos, but yeah, I've no good idea on how to solve that at this point
[16:38] <tsdgeos> greyback: have a sec?
[16:40] <Saviq> jml, Unity plugin / Experimental / Enable shortcut hints overlay
[16:41] <Saviq> tsdgeos, he's HUDing now ;)
[16:41] <tsdgeos> :D
[16:42] <jml> Saviq: thanks. that doesn't seem to be in ccsm for me on precise.
[16:42] <Saviq> jml, I'm on precise + HUD
[16:42] <Saviq> jml, so I might have a newer Unity
[16:42] <jml> Saviq: ah.
[16:42] <jml> there's only so much adventure I can take in one day
[16:45] <Saviq> jml, I'd say it should be there in latest unity in precise, though :/
[16:47] <greyback> tsdgeos: yep
[16:48] <tsdgeos> greyback: so in https://code.launchpad.net/~aacid/unity-2d/unity-2d_test_super_s_does_not_type_s/+merge/90068 Saviq is facing the problem that his spread triggers too fast and this clears the line and thus when we want to read the search_line there is no "s" there anymore, we can't think of anything  to fix it in testabiltiy, would an entry in "manual" tests be enough?
[16:48] <greyback> tsdgeos: Super+S MR not merged yet :)
[16:49] <greyback> tsdgeos: Could you try tpying in an application other than dash?
[16:49] <greyback> *typing
[16:49] <tsdgeos> greyback: no, has to be the dash, since it's about a bugfix in the dash
[16:51] <greyback> tsdgeos: hmm, ok. I see the problem. Yeah I can't think of an automatic way to test it, manual will do
[16:51] <tsdgeos> Saviq: agree going with manual test?
[16:52] <greyback> Causing problems with that SSD of his
[16:54] <Saviq> tsdgeos, yeah
[16:54] <Saviq> tsdgeos, maybe disable the test (say xtest instead of test)
[16:54] <tsdgeos> Saviq: ok
[16:55] <Saviq> tsdgeos, and we'll revisit once we have to postpone clearing the entry
[16:57] <Saviq> tsdgeos, and add a FIXME... or a FIXTHEM, rather
[17:02] <Saviq> greyback, you know that with input shaping we can now get the dash extensions easily?
[17:02] <Saviq> I mean the horizontal / vertical thin lines that go out from the dash
[17:02] <Saviq> and to the edge of the screen
[17:02] <greyback> Saviq: yes I'm aware of that
[17:03] <Saviq> oh and btw you know that our lower right corner of the dash differs a lot from unity's one?
[17:05] <greyback> Saviq: yep. Ours looks bad
[17:06] <Saviq> EOD for me, peeps
[17:06] <Saviq> see you tomorrow
[17:07] <tsdgeos> same here
[17:07] <tsdgeos> tomorrow more
[18:52] <jono> tedg, hey
[18:52] <jono> which package displays the indicators on my panel?
[18:53] <jono> I am seeing no indicators in Precise, apart from the app menus
[18:53] <seb128> jono, did you update unity?
[18:53] <jono> seb128, I did a dist-upgrade today
[18:53] <seb128> jono, dpkg -l | grep unity
[18:53] <jono> and I am running the HUD PPA
[18:53] <seb128> jono, the hud ppa rebuilds might be behind
[18:53] <seb128> the ppas tend to have extra delay in their build queues compared to the archive
[18:53] <seb128> kenvandine, ^
[18:53] <jono> gotcha
[18:54] <seb128> yeah, the ppa is waiting to build
[18:56] <jono> sorry
[18:56] <jono> my wireless keeps dropping
[18:56] <jono> a bug in the kernel
[18:56] <jono> seb128, not sure if you responded, but can I remove the PPA and delete a package and dist-upgrade to fix this?
[18:56] <seb128> jono, infinity is bumping the scores of the builds cf #ubuntu-devel
[18:56] <seb128> update from the ppa when it will have built
[18:56] <seb128> like in half an hour
[18:56] <seb128> will be easier than downgrading
[18:56] <jono> seb128, ok sounds good
[18:56] <jono> I will just wait
[18:57] <jono> thanks, seb128
[18:57] <seb128> yw
[18:58] <mhall119> tedg: ping
[18:58] <tedg> mhall119, Howdy
[18:59] <kenvandine> seb128, thx!
[18:59] <mhall119> tedg: hey,  I have a couple of bugs I'd like you to update for me
[18:59] <mhall119> tedg: https://bugs.launchpad.net/indicator-appmenu/+bug/721491
[19:00] <tedg> mhall119, heh, I just sent those to jcastro, he's a traitor!
[19:00] <mhall119> that one is almost a year old now
[19:00] <mhall119> heh
[19:00] <mhall119> then I guess you know about https://bugs.launchpad.net/indicator-appmenu/+bug/887843 too
[19:02] <mhall119> tedg: can we get those patches either accepted/rejected, or ask for an update
[19:02] <mhall119> sometime today if possible
[19:20] <tedg> mhall119, done
[19:33] <mhall119> thanks tedg
[20:07] <mhall119> _thumper_: would you be available at 21:00 utc today?
[20:10] <thumper> mhall119: that is the time of the US standup
[20:11] <thumper> after that I should be
[20:20] <mhall119> ok, I'll be around until about 22:30, so ping me when you are free
[20:25] <micahg> hi, I had unity-2d lose its panel, I tried restarting it and got this http://paste.ubuntu.com/816878/, I have no panel at present
[20:25] <micahg> I'm running 11.10 with proposed enabled on this machine
[20:53] <micahg> are there certain hours that are better for this channel?
[20:59] <micahg> ooh, even better, my panel is there, but invisible
[21:02] <asdfoiu3> Hello world!
[21:16] <asdfoiu3>  Hello, i have a question, i was messing around with touchegg drivers on ubuntu unity and i had to configure some x11 files.. and from that day on i havent been able to use my unity desktop, i have been looking online for solutions but nobody else seems to have this problem.. it is like i have no "explorer.exe".... Sorry for my english
[21:35] <FloatingGoat> mhall119: btw
[21:35] <FloatingGoat> mhall119: if unity dash isnt for doing stuff then why is there a lens for running commands?
[21:36] <mhall119> FloatingGoat: where?
[21:36] <FloatingGoat> alt F2 I thought
[21:36] <FloatingGoat> im just asking because
[21:36] <mhall119> oh, that's not technically the dash
[21:36] <mhall119> it's a part of Unity, but not the dash
[21:36] <FloatingGoat> oh
[21:36] <mhall119> like the new HUD
[21:36] <FloatingGoat> I can access my other lense from it though
[21:37] <FloatingGoat> that new hud looks cool
[21:37] <mhall119> oh, so you can, that's changed
[21:37] <mhall119> it wasn't like that in 11.10
[21:37] <FloatingGoat> mhall119: I made a video on how to install the dictionary, should I put it on youtube or do you not want me to?
[21:39] <mhall119> I'd love that
[21:39] <mhall119> I'll even link to it from my blog once it's up
[21:39] <FloatingGoat> okay I am going to make a revised version though
[21:40] <FloatingGoat> err of the video, because I didn't do the first one very well. So tonight I'll make it again.
[21:42] <mhall119> ok
[21:43] <FloatingGoat> But yeah i'll do that. Thanks. :D
[21:44] <FloatingGoat> I'm just curious, what do you do exactly? do you work on unity?
[22:12] <mhall119> thumper: can we maybe do a call this afternoon (your time)?
[22:13] <mhall119> FloatingGoat: my job is to promote Unity and Unity technology among community developers
[22:13] <FloatingGoat> oh wow cool
[22:13] <mhall119> well, any Ubuntu technology really, not just Unity
[22:13] <FloatingGoat> I love unity
[22:13] <mhall119> \o/
[22:13] <FloatingGoat> lol is that a celebrating guy?
[22:13] <mhall119> they don't hear that enough, so it's always good to see
[22:13] <mhall119> yea
[22:14] <FloatingGoat> hmm well I realize it has its downfalls but I stuck with it and i've always generally liked it from the start.
[22:15] <FloatingGoat> and I know it will get better
[22:15] <mhall119> kam/layout save
[22:33] <thumper> mhall119: sorry, been on a call talking with DBO