Skip to main content

Timeline for ThirdPlace JavaScript chat library

Current License: CC BY-SA 3.0

23 events
when toggle format what by license comment
Aug 29, 2012 at 15:57 comment added Josh Since work has been keeping em so busy, I have created a GitHub project for ThirdPlace. I will fix the bugs as soon as I can, but in the meantime, anyone else can feel free to hack away!
Jul 16, 2012 at 15:28 comment added Raphael @Josh No worries! I know how it is to want to work on some pet project but to not get around to it. Best of luck at work, looking forward to your updates!
Jul 16, 2012 at 14:32 comment added Josh my apologies for the delay. Chat hacking takes a backseat to real work, sadly! I expect I may have some time this week, we'll see. I'll post updates as I have them!
Jun 28, 2012 at 17:20 comment added Raphael @Josh Looks like you are still busy? Do you have a (reliable) estimate on when you can continue working on ThirdPlace?
Apr 11, 2012 at 12:13 comment added Josh Thanks @Raphael. My business is keeping me extremely busy right now and I haven't had a chance to work on ThirdPlace much at all, unfortunately. I do very much want to fix these bugs, but it may be a week or more before I can get to them, unfortunately. I also intend to set up a GitHub site.
Apr 11, 2012 at 10:57 comment added Raphael @Josh: How are things going? Just letting you know someone still cares. ;)
Mar 30, 2012 at 2:50 comment added Josh there's definitely bugs with double messages. I think it's related to multiple tabs, but I am unsure. Still working on it!
Mar 29, 2012 at 18:47 history edited Raphael CC BY-SA 3.0
added 74 characters in body
Mar 29, 2012 at 18:37 comment added Josh I'm working on these questions now @Raphael
Mar 25, 2012 at 17:02 comment added Josh I'll check in to these items and get back to you. Also, a GitHub site may be in order :-)
Mar 24, 2012 at 19:45 comment added Raphael Two more things: newMessge is fired for the latest message when entering a room. Is this intended? And all newMessage events seem to come through twice (not so editMessage).
Mar 24, 2012 at 19:39 comment added Raphael I tried injecting a script tag with src pointing to your file but that causes the $-issue again (I guess; at least nothing happens.)
Mar 24, 2012 at 19:29 comment added Raphael An alternative to passing the DOM object of messages would be their ID; with that, one can retrieve the required elements oneself.
Mar 24, 2012 at 19:20 comment added Raphael @Josh when I inject your code it works. O.o I am a userscript novice, but does such behaviour not defeat the purpose of @require? Regarding DOM and old messages: that would be cool! I want to tell MathJax to work on the message text so I need a handle, and of course you would want math in old messages to be parsed, too (in particular also when even older messages are explicitly loaded). Thanks for your help!
Mar 24, 2012 at 18:39 comment added Josh To answer your other questions: right now Message objects do not know their DOM object, but I can add such a feature. At the moment, newMessage events only fire as new messages are loaded, they won't fire for older messages in the room when you join. Again, I can add that.
Mar 24, 2012 at 18:37 comment added Josh I didn't try your specific example, I tried part of it in the Firebug console. Let me play with this a bit longer and see if I can reproduce. I think the issue may be the @require http://josh.gitlin.name/userscripts/ThirdPlace.js. Try wrapping the entire ThirdPlace.js script in an inject(function($) { call?
Mar 24, 2012 at 17:36 comment added Raphael @Josh No luck. It does not throw any errors but no dialogs pop up. Does the example work for you? Maybe ThirdPlace is not the problem; in this case I would appreciate hints as towards what I am doing wrong.
Mar 23, 2012 at 16:11 comment added Josh Okay Raphael, I just released v0.6 of ThirdPlace. Please update to the new code and try your test again. Thanks!
Mar 23, 2012 at 14:54 comment added Josh window.addEventListener('storage',...) is not firing in FireFox, so that's why ThirdPlace.observe is having no effect. Looking for a solution.
Mar 23, 2012 at 14:41 comment added Josh Found the problem. ThirdPlace.observe seems to be broken. ThirdPlace is working, and the console.log.apply messages are just a tangential issue. For some reason ThirdPlace is unable to detect events. Working on that, will post back when it's resolved!
Mar 23, 2012 at 12:07 comment added Josh Hey sorry, somehow I missed this answer until just now! I'll take a look at this and get back to you shortly.
Mar 19, 2012 at 11:32 history edited Raphael CC BY-SA 3.0
added 295 characters in body
Mar 19, 2012 at 11:22 history answered Raphael CC BY-SA 3.0