[03:18] <mac_v> DanRabbit1: pong
[03:19] <mac_v> DanRabbit1: http://dl.getdropbox.com/u/1325768/Humanity.tar
[12:28]  * MacSlow -> lunch
[13:36] <mac_v> MacSlow: hi... have the classes sync/async been merged again? :(
[13:36] <MacSlow> no
[13:37] <MacSlow> mac_v, what makes you think that?
[13:37] <mac_v> hmm... both appear in the first row
[13:37] <mac_v> for me , 
[13:37] <mac_v> or is it a bug?
[13:37] <MacSlow> mac_v, do you use notify-osd 0.9.20?
[13:38] <MacSlow> mac_v, and do you use the NorthEast gravity (gconf-key /apps/notify-osd/gravity == 1)?
[13:39] <mac_v> MacSlow: notify-osd 0.9.20 (0ubuntu1) , but didnt  set any gravity , the bubbles just moved back up ad now both appear in the first row
[13:39] <mac_v> and*
[13:39] <MacSlow> mac_v, if only one comes up at a time that's currently ok
[13:41] <mac_v> MacSlow: aw, :( , the fixed location of the async to second row would have been better , now its almost the same old behavior :(
[13:43] <MacSlow> mac_v, we're considering such layout options too
[13:43] <mac_v>  \o/ that would be great
[14:29] <DanRabbit> mac_v: that link is a 404 :(
[14:30] <mac_v> DanRabbit: oh! i thought you already grabbed it and moved it ;) , just a sec
[14:30] <mac_v> *i moved
[14:31] <mac_v> DanRabbit: http://dl.getdropbox.com/u/1325768/Humanity.tar
[14:31] <DanRabbit> cool
[14:33] <DanRabbit> mac_v: which icons (freedesktop.org names) do these correspond to?
[14:34] <mac_v> DanRabbit: hehe , the names are wrong , i thought you knew , was just lazy to look them up ;p
[14:34] <DanRabbit> oh
[14:34] <DanRabbit> well
[14:34] <DanRabbit> I'm looking at the netstatus icons, and there is many more than these
[14:34] <DanRabbit>  :D
[14:35] <mac_v> DanRabbit: they are 22 and 24px icons for the wired and the disconnected icons
[14:35] <mac_v> let me check
[14:38] <DanRabbit> It's okay, I can take care of it
[14:38] <mac_v> DanRabbit: /usr/share/icons/Human/22x22/status/network-transmit-receive.png , /usr/share/icons/gnome/22x22/status/network-offline.png 
[14:38] <mac_v> oops! /usr/share/icons/gnome/22x22/status/network-transmit.png
[14:38] <DanRabbit> yea, those are the ones I assigned 
[14:38] <mac_v> hehe ;)
[14:38] <DanRabbit> we need network-error
[14:38] <mac_v> the rest are all symlinks to these
[14:38] <DanRabbit> network idel
[14:38] <DanRabbit> idle*
[14:39] <mac_v> DanRabbit: yeah just noticed
[14:39] <DanRabbit> network receive
[14:39] <DanRabbit> and network transmit
[14:39] <DanRabbit> shouldn't be too hard to do from the current icons
[14:40] <mac_v> network-receive.png network-transmit.png , would either need different shades or could use colors 
[14:40] <DanRabbit> I'm thinking just fading out one of the plugs
[14:40] <DanRabbit> use the connected plugs, but with their respective transparency
[14:40] <mac_v> yeah that works too :)
[14:41] <mac_v> for error? 
[14:41] <mac_v> is color not allowed even for error?
[14:42] <DanRabbit> Well, we use red on the battery
[14:42] <DanRabbit> so I would think the disconnect icon, but in red
[14:43] <mac_v> the disconnect can stay similar to the wireless where we dont use color for the no signal , i think only error can have the red , this makes it more easy to differentiate
[14:43] <DanRabbit> that's what I meant :D
[14:43] <mac_v> hehe i think you just said the same ;p
[14:45] <mac_v> DanRabbit: why are the battery icons blurry? , 
[14:45] <DanRabbit> I don't know
[14:45] <mac_v> :(
[14:45] <DanRabbit> I'm thinking it's an issue with the applet
[14:45] <mac_v> stupid panel applets!
[14:46] <DanRabbit> mac_v: you should apply to join elementary icons team on launchpad and then you can just upload your icons straight to bzr
[14:46] <DanRabbit> :D
[14:47] <mac_v> DanRabbit: hehe , i wouldnt go so far as to upload them directly ;) but i guess i can show and upload 
[14:50] <mac_v> DanRabbit: done 
[14:50] <DanRabbit> cool :D
[14:52] <DanRabbit> brb
[14:53] <mac_v> DanRabbit: for the inactive panel icons , at 50% transparency , for the dark panels its a bit tough to notice the difference , i think the level can be lowered ,so that it is easy to see the levels
[14:54] <mac_v> *see the difference in the signal/volume levels
[15:02] <DanRabbit> okay sounds good
[15:02] <DanRabbit> I have to go to school :(
[15:02] <DanRabbit> be back later
[15:03] <mac_v> sure bye ;)
[15:55] <SiDi> MacSlow: heya.
[15:55] <SiDi> Just wanted to ask you.. With that gravity setting, you now have 2 code paths for the bubble placement, right ?
[15:57] <MacSlow> SiDi, yes... but those will get shifted (actually are atm) around
[15:57] <SiDi> i see :)
[15:57] <SiDi> With that code written up, it would actually be trivial to add north west / west gravities, right ? :D
[16:35] <sintack> please help... i can't get a notify-osd to last shorter than 10 seconds.  and i've tried to set the urgency to less than critical.  thanks
[16:40] <mac_v> SiDi , ^ any thoughts? 
[16:41] <SiDi> I dont think the default time is configurable yet :p
[16:41] <SiDi> ask MacSlow :p
[16:43] <SiDi> Does anyone know the IRC nick of Scott James Remnant and which channels i may find him, please ?
[16:43] <sintack> oh.. so a confirmation bubble, like volume change, stays there for 10 seconds?  at this point in time?
[16:43] <SiDi> volume change goes after 1/2 seconds
[16:43] <SiDi> what version do you use, sintack ?
[16:44] <SiDi> (/me found the nick, sorry for the noise)
[16:44] <sintack> i'm using 0.9.18-1, the one in debian testing
[16:44] <SiDi> sintack: may you try with 0.9.19/20 or with the bzr trunk (bzr co lp:notify-osd) ?
[16:45] <SiDi> Confirmation bubbles do last 3 seconds, apparently
[16:45] <sintack> yes, i could try.
[16:45] <SiDi> as for normal bubbles, i'm not sure of the current status but they're meant to last more if there is a lot of text, but i think the default is about 10 secs
[16:46] <sintack> ah, i see.  well i read in the specs that a low-urgency normal bubble can last 5, or shorter, i think
[16:46] <sintack> and besides, doesn't the tool like "notify-send" allow you to set the expiration time?
[16:47] <SiDi> You're right
[16:47] <SiDi> 5s + 250ms / line of body text
[16:47] <SiDi> it looks like this is not fully implemented
[16:47] <SiDi> and, notify-osd will ignore timeout parameters from applications
[16:47] <sintack> i understand
[16:47] <SiDi> because this was heavily abused by some apps
[17:00] <sintack> i've come across a site that confirms this problem for debian official repo. users.
[17:02] <sintack> anyhoo, thanks for the replies SiDi.  perhaps i'll try or wait for later versions.
[17:03] <SiDi> sintack: could you please file a bug, though ?
[17:03] <SiDi> specifying that the problem occurs with the debian package ?
[17:03] <SiDi> i didnt see any such bug in launchpad
[17:03] <sintack> so, i'll file it in launchpad?
[17:03] <SiDi> Yes, and link it to debian's bugzilla please
[17:03] <SiDi> https://bugs.launchpad.net/notify-osd/+filebug
[17:04] <sintack> ok, i've never filed a bug before :P;  i'll try
[17:04] <SiDi> do you have the link to the debian bug report ? :)
[17:04] <sintack> yeah, i guess
[20:17] <chrisccoulson> MacSlow - has the interface for volume notifications changed in notify-osd at all recently? (as in, the last 3 weeks or so)
[20:23] <SiDi> chrisccoulson: what do you mean ?
[20:23] <SiDi> Regarding over/undershoot volume notifications ?
[20:23] <chrisccoulson> SiDi - yes
[20:24] <SiDi> Well, you have to use -1 for under / 101 for over
[20:24] <chrisccoulson> SiDi, thanks. it seems gnome-settings-daemon is already doing that
[20:24] <SiDi> but i think trunk notify-osd is broken in that regard :P
[20:24] <chrisccoulson> the only reason i ask, is because i got assigned to bug 419645, and was wondering what needed updating
[20:24] <ubot4> Launchpad bug 419645 in gnome-settings-daemon "Update to 2.27.91" [Wishlist,New] https://launchpad.net/bugs/419645
[20:25] <chrisccoulson> but it seems like nothing needs changing on the g-s-d side at the moment
[20:25] <SiDi> may i see that patch file please ? :P
[20:25] <SiDi> apparently its ok. under/overshoot is disabled in notify-osd for now, i dont know when it'll be put back
[20:25] <SiDi> but if you use -1 for under and 101 for over then it's ok, it should work
[20:26] <chrisccoulson> SiDi - cool. i've got to go for dinner now, i'll get you the patch afterwards if that's ok (if you haven't already found it)
[20:26] <chrisccoulson> but yeah, g-s-d already uses -1,+101
[20:27] <SiDi> it should be fine then
[20:27] <SiDi> i'm leaving to a party right now though
[20:27] <SiDi> have a nice dinner :p
[20:33] <MacSlow> chrisccoulson, SiDi: no... it's a regression in notify-osd (from the blur-/tile-cache work) I still need to fix
[20:33] <SiDi> MacSlow: but once it'll be fixed, itll be -1 & 101 right ? :P
[20:34] <MacSlow> SiDi, sure -1 and 101 are still the "trigger"-values
[20:34] <SiDi> okies
[20:34] <SiDi>  i needa go
[20:34] <SiDi> have a nice evening :)
[20:34] <MacSlow> I should call it a day too
[20:34] <MacSlow> SiDi, see you later
[22:07] <mac_v> tedg: hi! , i'v been waiting for you ;)
[22:07] <mac_v> a few doubts regarding the mail notifications
[22:07] <mac_v> in the i-a
[22:08] <tedg> mac_v: Waiting?
[22:08] <mac_v> hehe , yeah ;p , i wanted to write a mail to ayatana , but wanted to confirm a few things first :)
[22:09] <mac_v> you said that selecting the app when a new mail arrives , will change the icon back to "no new mail", right?
[22:09] <mac_v> this is irrespective of the mail being read or not , 
[22:11] <mac_v> tedg: what happens if the user has new mail in evolution and new chat in empathy? selecting evolution will change the icon back to "no new mail" ?
[22:11] <mac_v> or will the apps be considered separately?
[22:11] <tedg> mac_v: The apps are considered separately.
[22:12] <mac_v> if new mail is in evolution and new chat in empathy , so if user selects evolution , the icon is changed to "no new" instantly or only after empathy is also selected?
[22:13] <tedg> After Empathy is also selected.
[22:14] <tedg> Basically each indicator can or can not set the notification to the user.  When all the indicators that set the green dot are removed, then it goes away.
[22:15] <mac_v> tedg: but the dot depends on the app being selected or not...... and not the mails being read or not
[22:15] <mac_v> is it difficult to keep the dot on until all the mail are read?
[22:16] <tedg> That is based on the implementation of the application.  The messaging menu does not control that directly.
[22:16] <tedg> We think that applications should only use it for "new information" so if I have 1000 unread mail in my mailbox, it shouldn't remain lit.
[22:17] <tedg> But if I get 10 more since I last checked, then light it up.  When I look at the app I've chosen whether to ignore those or not.
[22:18] <tedg> Likewise if someone IMs you it should go away when you look, not when you respond.
[22:19] <mac_v> tedg: hmm... what i find from using it is ,... i read mail in certain folders when they arrive , since i want to read them now , but certain folders i read later , so the lack of "no new" is kinda misleading :(
[22:19] <mac_v> its like i have to remember i havent read those mails
[22:19] <tedg> mac_v: Well, the idea would be that you could select the folders that it responds to.  Hopefully, we can get that implemented for Karmic, but that is harder.
[22:20] <tedg> mac_v: Evolution has a pretty difficult layout for mail folders.
[22:20] <mac_v> yeah
[22:22] <mac_v> tedg: just an idea ... maybe the icon on the panel turns to "no new" but when the user selects the drop down , the folders still show as "5new" , is that possible... or is that what you are trying to implement?
[22:22] <tedg> mac_v: That's not impossible.  That wasn't the original idea, but I think that's definitely interesting.
[22:23] <mac_v> or does such an implementation need plugins in the apps?
[22:23] <tedg> mac_v: I'm curious about the number of entries then, the idea was that they'd cycle... then they'd become more permanent.
[22:24] <tedg> Everything needs a plugin in the apps :)  That's what evolution-indicator is for Evolution.
[22:24] <tedg> I believe that the KMail support is a patch though.  That would be a question for agateau as he did that work.
[22:24] <mac_v> hehe ;) , i meant in other apps too
[22:26] <mac_v> tedg: when is the applet expected , to be complete ? i know stupid question...! or is it possible to use upstream version and test it?
[22:27] <tedg> mac_v: You can grab it, but it's not entirely complete yet.  I have the library changes in code review now, then I'm getting cracking on the applet.  I'll be in trouble if it's not by the end of the week :)
[22:27] <mac_v>  great, \o/
[22:28] <mac_v> not that you'll be in trouble , but the applet will be done by this week ;p
[22:29] <mac_v> i'm planning on looking into xchat and messaging menu , so if it lands soon enough , i'd start looking into it ;)
[22:45] <tedg> You're welcome to grab my version of the lib.
[22:45] <tedg> Everything else will be just the props in the spec.
[22:45] <tedg> http://wiki.ubuntu.com/MessagingMenu
[22:47] <mccann> hey guys
[22:48] <mccann> just wondering - what is the state of the wallpaper contest thing?
[22:51] <DanRabbit> mac_v: did you do those wired network icons, or do I need to do them?
[22:52] <mac_v> DanRabbit: which icons...huh? the error?
[22:52] <DanRabbit> yea and the transmit and receive and all that
[22:53] <mac_v> oh , just  a few mins :)
[22:53] <DanRabbit> :D
[23:15] <DanRabbit> mac_v: I have to leave for work in just a few short minutes. Can you add those icons to lp:humanity? I've approaved your membership.
[23:16] <mac_v> ok , no probs :)
[23:20] <DanRabbit> cool ty
[23:20] <DanRabbit> bye
[23:54] <mac_v> DanRabbit: push to branch , the icons are labeled according to gnome , and the network-offline was a symlink to a wireless no signal  , but the gnome is for a wired , so changed it accordingly
[23:55] <mac_v> mccann: regarding the wallpaper contest you need to ask in #ubuntu-artwork