All times are UTC.
01:07:04 <-- clokep has quit (Ping timeout) 01:07:15 --> clokep has joined #instantbird 01:12:49 <clokep> There really needs to be a way to find arbitrary logs. :( 02:39:08 --> skeledrew has joined #instantbird 02:42:36 --> Amfi has joined #instantbird 02:50:40 <-- Amfi has left #instantbird () 02:58:00 <-- skeledrew has quit (Ping timeout) 02:59:35 --> skeledrew has joined #instantbird 03:38:23 <-- skeledrew has quit (Ping timeout) 03:42:47 --> skeledrew has joined #instantbird 03:57:14 <-- clokep has quit (Ping timeout) 03:57:18 * Gizmokid2005 is now known as Gizmokid2005|AFK 04:05:25 <-- Even has quit (Quit: Instantbird 0.2pre) 04:19:12 <-- skeledrew has quit (Ping timeout) 04:19:22 --> skeledrew has joined #instantbird 04:30:03 <-- skeledrew has quit (Ping timeout) 04:34:06 --> skeledrew has joined #instantbird 04:51:43 <-- skeledrew has quit (Ping timeout) 05:03:04 --> skeledrew has joined #instantbird 05:13:51 <-- skeledrew has quit (Ping timeout) 05:34:44 --> skeledrew has joined #instantbird 05:59:08 <-- skeledrew has quit (Ping timeout) 06:03:04 --> skeledrew has joined #instantbird 06:18:25 <-- skeledrew has quit (Ping timeout) 06:19:06 --> skeledrew has joined #instantbird 06:27:18 <-- skeledrew has quit (Ping timeout) 08:04:41 --> GeekShadow has joined #instantbird 08:52:16 <-- GeekShadow has quit (Quit: The cake is a lie !) 09:20:54 --> Mic has joined #instantbird 09:21:14 <Mic> hello 09:22:47 --> skeledrew has joined #instantbird 09:25:53 <-- skeledrew has quit (Ping timeout) 10:07:43 --> skeledrew has joined #instantbird 10:24:47 <-- skeledrew has quit (Ping timeout) 10:25:54 --> skeledrew has joined #instantbird 10:28:54 <-- skeledrew has quit (Ping timeout) 10:30:31 --> skeledrew has joined #instantbird 10:37:47 <-- skeledrew has quit (Ping timeout) 12:19:34 --> skeledrew has joined #instantbird 12:27:03 <-- skeledrew has quit (Ping timeout) 13:06:02 --> clokep has joined #instantbird 13:23:03 --> skeledrew has joined #instantbird 13:23:27 <-- clokep has quit (Quit: Instantbird 0.2pre) 13:24:13 --> clokep has joined #instantbird 13:24:16 <-- clokep has quit (Quit: clokep) 13:24:48 --> clokep has joined #instantbird 13:59:38 <-- skeledrew has quit (Ping timeout) 15:01:04 --> skeledrew has joined #instantbird 15:16:07 <-- skeledrew has quit (Ping timeout) 15:33:57 --> skeledrew has joined #instantbird 15:45:55 <-- skeledrew has quit (Quit: Instantbird 0.2b2) 15:47:54 --> skeledrew has joined #instantbird 15:49:00 <-- skeledrew has quit (Connection reset by peer) 15:49:50 --> skeledrew has joined #instantbird 15:59:09 <-- skeledrew has quit (Ping timeout) 16:14:00 --> tymerkaev has joined #instantbird 16:16:05 --> skeledrew has joined #instantbird 16:19:08 <-- skeledrew has quit (Ping timeout) 16:20:36 --> skeledrew has joined #instantbird 16:45:53 --> Amfi has joined #instantbird 16:47:12 <-- Amfi has left #instantbird () 17:11:53 <-- skeledrew has quit (Ping timeout) 18:17:02 --> GeekShadow has joined #instantbird 19:06:57 --> skeledrew has joined #instantbird 19:53:33 * tymerkaev is now known as tymerkaev-afk 19:54:20 <-- tymerkaev-afk has quit (Quit: I must go. Good bye!) 19:54:30 --> tymerkaev-afk has joined #instantbird 20:10:57 <skeledrew> where in the JS can i find the ev can be handled? and where can i find a good intermediate tutorial on JS specific to XUL? 20:11:28 <flo> ev ? 20:11:34 <skeledrew> *events that 20:12:40 <skeledrew> my internet collection is malfunctioning badly, so i have to download the info i need elsewhere... 20:12:49 <skeledrew> *connection 20:13:42 <flo> I'm not sure about the tutorial, but there's a lot of interesting resources for add-on developers on http://developer.mozilla.org/ 20:14:55 <flo> and which event are you talking about? 20:15:05 <skeledrew> those are a bit out of my depth at this time. i'm more focusing on the JS side, and the general setup 20:15:38 <skeledrew> buddy-sign-on/off, message-sent/received, etc 20:15:51 <flo> https://wiki.instantbird.org/Instantbird:Notifications 20:16:21 <skeledrew> k 20:18:00 <skeledrew> flo: and the various actions that can actually be performed? 20:20:31 <Mic> What you can do depends on "what you have" 20:20:54 <Mic> If you have an object representing a buddy you can do things like 20:21:25 <flo> http://lxr.instantbird.org/instantbird/source/purple/purplexpcom/public/ look there for the interfaces of the XPCOM components you get as parameter of the notifications 20:22:12 <Mic> ok, or just that .. :) 20:22:40 <Mic> I just was looking up purpleIBuddy as example 20:22:40 <flo> :) 20:43:17 <skeledrew> k 20:47:57 <-- tymerkaev-afk has quit (Client exited) 20:53:10 <Mic> skeledrew: the article on the wiki has links to the mentioned interfaces on lxr 20:53:21 <Mic> *now 20:53:44 <skeledrew> k 20:56:43 <Mic> The wiki could need some cleaning :S 20:58:27 <flo> Mic: this is great! I was thinking too that these should be links :) 20:59:11 <flo> thanks :) 21:00:03 <Mic> no worries 21:00:27 <Mic> What happened to the video link addon that one of your students was creating by the way? 21:02:37 <flo> hmm 21:02:43 <flo> the code wasn't pretty 21:02:56 <flo> neither was the UI 21:03:01 <flo> but it worked 21:03:17 <flo> the .xpi is somewhere in my email inbox 21:03:39 <Mic> Would you mind letting me have a look? 21:04:25 <Mic> I think you should have my email if you don't want to upload it somewhere 21:05:05 * flo tries to find the email containing the xpi file first :-P 21:08:25 <flo> Mic: email sent! :) 21:08:33 <Mic> thanks 21:08:37 <flo> np 21:09:36 <Mic> Maybe the "Brainstorm:prefwindow" and "Brainstorm:tabs-improvements" articles would be better named "Bugtracking: ..." or so, "Brainstorm" is definitely a misnomer 21:10:20 <Mic> We could create a bug in Bugzilla pointing to the respective article next time, so there's no way to miss that there is a list with more bugs somewhere else than in Bugzilla 21:10:51 <flo> what's the next big feature that will need such a tracking? 21:11:48 <flo> I'm not sure of how soon we can hope to have JS protocols 21:11:49 <Mic> The FF4 style "in content"-pref window maybe? ;) 21:12:18 <flo> but we will probably have "... can be done only for protocols implemented in libpurple" bugs 21:12:39 <Mic> The thing with the articles is that they can't be found at all if you don't know exactly what you are looking for 21:12:41 <flo> there's so much to rewrite 21:13:16 <Mic> And it's not just an article but bugtracking 21:13:47 <flo> yes 21:14:14 <flo> somehow, I'm reluctant to file bugs with an empty or one-line description, but that may be better than the wikipage 21:14:31 <Mic> I meant a tracking bug pointing to the wiki article 21:15:22 <flo> it seems we have discussed most of these things here, and it's completely messy in the IRC logs 21:15:46 <flo> having had that discussion in each bug would provide a better history 21:15:47 <-- skeledrew has quit (Ping timeout) 21:18:19 --> skeledrew has joined #instantbird 21:21:10 <-- Mic has quit (Quit: Instantbird 0.2pre) 21:22:35 --> Mic has joined #instantbird 21:26:57 <Mic> flo: is your student still working on it? 21:27:04 <flo> no 21:27:10 <flo> all students are in vacations :-D 21:27:37 <flo> the final evaluation for the 2 students who were "playing" with canvas was last week. 21:27:42 <flo> s/last/this/ 21:27:48 <flo> it wasn't great :-/. 21:28:16 <Mic> Honestly I wasn't sure were this thing was supposed to be going 21:29:07 <Mic> I saw a canvas thing once (i think it's in the addons repository) and it was drawing lines which looked like a random walk to me? (or was that somewhere else?) 21:33:18 <-- skeledrew has quit (Quit: Instantbird 0.2b2) 21:37:10 <clokep> flo: Reply-to-Nick is pretty convenient. :) 21:37:27 <flo> clokep: thanks for the good feedback :) 21:37:52 <clokep> And I might have taken a look at the new style you're working on by mistake in the HG logs. :P 21:37:55 <flo> Mic: there's a separate hg repository 21:38:13 <flo> this way, I'll be able to quietely rm -rf it in a few months without anybody noticing :) 21:38:20 <clokep> flo: Interesting idea at least. 21:38:54 <flo> clokep: it's not a secret ;) 21:39:12 <clokep> Haha, well you said you didn't want us to try it until it works cause the bug will take our attention away. 21:39:30 <flo> it's just that I got the same feedback from all the testers who tested the current version, and I feel that it's wasting good possible feedback to provide a version with the same obvious defect to more people 21:39:47 <clokep> Fair enough. Well when you have a new version, let me know. 21:39:54 <flo> :) 21:40:09 <flo> (the annoying bug doesn't exist on Mac, so if you have a mac, don't wait :-P) 21:40:21 <flo> (that's also the reason why I haven't noticed it in the first place) 21:41:06 <clokep> I run only Windows, occasionally I'll have access to Linux, but not installed ATM. 21:47:25 <Mic> http://gdata.youtube.com/feeds/api/videos/<video-id> gives information concerning the video 21:47:45 <Mic> Might be a nice addition 21:48:26 <Mic> Is the author continuing to work on the addon or is his part on this done on? 21:57:06 <Mic> flo: ping 21:57:33 <flo> Mic: I think we will rewrite that add-on ;) 21:57:48 <flo> could be a great idea for an "add-on day" 21:57:52 <Mic> I was looking up other related greasemonkey scripts 21:57:56 <flo> I'm not sure if I've already talked about this here 21:58:10 <Mic> We could need a bugzilla and wiki day as well? ;) 21:58:33 <Mic> Not to me, btw 21:58:35 <flo> we plan to do "add-on days" sometimes on sundays. The idea would be that at least idechix and me would be together in the same place, working all the day on creating interesting add-ons to demonstrate the extensibility 21:59:09 <flo> we would encourage others on IRC to create add-ons too, and I'd be available to answer add-on development questions all the day long, and helping people start 22:02:55 <Mic> Sounds good :) 22:03:13 <flo> I'm not sure how many participants we could have 22:03:38 <flo> we tried only once, but without announcing it on IRC for the first time to see how it would work just with the 2 of us 22:04:13 <flo> it failed miserably that day because idechix needed to do things on the website, and I had a headache that prevented me from focusing on code :( 22:04:33 <Mic> Do you see any difficulties with loading a Youtube flash player into a conversation? 22:04:58 <flo> it should be done in an iframe 22:05:48 <flo> the external flash object should not be loaded directly into the html file of the conversation (it has chrome privileges, there would be a security risk) 22:06:17 <Mic> Oh, the conversation has chrome priviledges? I didn't know that 22:06:29 <Mic> Wel, I guess it should to be able to eg load smilies from chrome urls 22:07:25 <flo> it can execute javascript 22:07:48 <flo> the smilies are from smile:// urls, we could make these accessible from "content" I guess 22:08:10 <flo> hmm, wait. Thinking more about it, I think it's having content privileges. 22:08:29 <flo> oh well, I'm confused this evening :) 22:08:31 <Mic> Even though having it in an iframe would be better 22:08:57 <Mic> in the sense that it couldn't possibly read conversation content, am I right on this? 22:09:06 <flo> yeah, having it in the same document would "feel bad" anyway. 22:09:11 <flo> yep! :) 22:10:02 <Mic> A problem that I see with the UI is that you don't know what the messagestyle looks like 22:10:43 <flo> hmm 22:10:51 <Mic> Would be nice to have something like on Facebook, where you've got a preview image and maybe some extra data (available from the YT API) 22:11:06 <Mic> in the content, not as tooltip 22:11:08 <flo> if you want to play the video I don't know, but to only display a preview picture, I think it should just use a tooltip 22:11:36 <flo> ah well, maybe :) 22:11:43 <flo> not having to move the mouse is even better! 22:12:09 <Mic> I was thinking about an extra box after the message, "blabla sent you (a|some) video link(s): + preview(s)" 22:13:34 <Mic> but that's difficult to do with messagestyles as I see it 22:13:54 <flo> maybe do it as a system message? 22:14:33 <flo> an exception will probably have to be added to filter that strips unwanted HTML markup 22:15:12 <clokep> Why can't it just pop up a new Window? (or add an extra box to the side the message window)? 22:16:17 <clokep> It could make like a "content bin" on the side which shows all the things linked to and then pulls in certain ones (youtube videos, pictures, etc.) and if its collapsible it would fit in to the UI pretty well. 22:17:22 <flo> hmm 22:17:40 <flo> not sure. I guess doing a mockup/experimenting would tell if it's a good idea or not 22:19:05 <clokep> Is it OK if I just draw ghetto boxes? :) 22:19:59 <flo> why not? 22:20:57 <clokep> Either of you ever use mockery or pencil to do mockups? 22:21:33 <Mic> Sometimes I do sketches on paper 22:21:45 <Mic> Or freehand with a graphics tablet 22:22:16 <clokep> Mic: I don't have a scanner around. :( Nor own a table.t 22:22:30 <Mic> A camera? 22:22:41 <clokep> Mic: Don't own one. My webcam is in a different state. :) 22:22:56 <Mic> oh, ok. 22:23:18 <clokep> Just gimme a sec, it'll be OK. ;) 22:23:58 <flo> that reminds me I should scan my paper/pencil buddy list mockup! 22:26:41 <Mic> I'm curious what this might be 22:26:49 <clokep> A note, Mockery is pretty sweet. But its not free. :( Oops. 22:28:27 <Mic> I like the way Skype does it: selecting a buddy will display more information, including the buddy picture and some buttons to do the most frequent things 22:29:29 <clokep> Mic: kind of a cross between Instantbird and Pidgin? It shows the more info, but only when you click on them? 22:29:38 <Mic> yes 22:29:45 <Mic> unfortunately it would lead to jumping items on the buddylist when clicking on a group (that does not have such a view) 22:29:58 <clokep> :-\ I agree. 22:30:11 <clokep> Dinner time. I'll finish this mock up sometime tonight...is there some place I can post it? 22:30:14 <Mic> They're of equal height, so the total height of the list doesn't change when selecting another buddy 22:30:21 <Mic> You could put it on the wiki maybe 22:30:21 <clokep> If not I can put it on some webspace I have and leave a link in here. 22:30:27 <clokep> Oh, OK. 22:34:49 <Mic> hmm, a "content bin" 22:34:55 <Mic> Sounds interesting 22:36:13 <Mic> I imagine a window with a richlist containing images and videos that have been posted, maybe with some extra information (who posted it, when was it posted; click could just to the place in the conversation) 22:36:46 <Mic> *jump 22:37:06 <Mic> A play/open button would go to the place on the web maybe 22:38:33 <Mic> flo: an image preview would maybe suffer from privacy problems, as someone could upload an image to own webspace and check the logs for access to it :S 22:39:02 <flo> and image is not different from a video 22:39:14 <flo> there would need to be known/trusted domains 22:39:22 <flo> imgshark for example 22:39:54 <Mic> ok, I was thinking about previews for any url that looks like an image 22:40:08 <Mic> You're right 22:43:41 <Mic> Good night 22:47:22 <flo> good night :) 22:54:06 <clokep> This is definitely one of those things that would be easier w/ a mouse. :( 23:01:47 <-- Mic has quit (Quit: Instantbird 0.2pre) 23:06:11 <clokep> flo: You still here? 23:06:20 <flo> no :) 23:06:33 <flo> ;) 23:07:00 <clokep> Any particular place I should upload this? 23:07:15 <clokep> wiki? 23:08:16 <clokep> Now I need to create an account. 23:10:42 <clokep> flo: https://wiki.instantbird.org/File:Content_bin_mockup.png 23:12:15 <flo> why not "just" a list of thumbnail previews? 23:15:51 <clokep> Instead of a listbox of the URLs? 23:16:50 <clokep> Could do that if you're handling only images and youtube videos I guess, I was thinking of also pulling in other links, but a scrollable grid of thumbnails could be nice...but would they automatically load? Is that a security issue? 23:19:39 <clokep> Limiting it to people in the buddy list might be good hahah. 23:23:51 <flo> hmm 23:23:56 <flo> so no youtube video in IRC channels? 23:24:18 <clokep> Well...if you could add IRC chatrooms to the buddy list...;) 23:27:20 <clokep> The implementation wasn't really my point, just the UI. Thumbnails might be a bit nicer though... 23:56:00 <flo> ok 23:56:03 <flo> good night! :) 23:56:06 <flo> or evening