|
Sorry! No users have been active over the past hour. |
|
|||
Hmm, I have an idea of how to slighty improve the chartroom. It's based on that limit=0 thing I suggested on the ListPages module. |
|
|||
Goodnight! [[footnoteblock]] |
|
|||
Goodnight! [[footnoteblock]] |
|
|||
You know that link you sent me? Apple have disabled since a certain version of iOS, so I didn't think it would be worth the energy. Mini-chatroom is not official, but it looks like this at the moment: [[html]] I don't like the idea of having a separate “chatroom-mini” page, so that's why I haven't launched it yet. [[footnoteblock]] |
|
|||
Also, How do I access the mini chatroom? [[footnoteblock]] |
|
|||
Yes! Scrolling works! James, you might want implement a workaround for iOS HTML5 audio autoplay. Alert still not working… [[footnoteblock]] |
|
|||
Wow! He even fixed the scrolling code!!! Now we can scroll using iOS devices!!! [[footnoteblock]] |
|
|||
Awesomeeeee! [[footnoteblock]] |
|
|||
Bryce added a css design for the saving page dialogue!!! [[footnoteblock]] |
|
|||
I'm in the middle of implementing a mini version of the chatroom… [[footnoteblock]] |
|
||
Hmm, I have an idea of how to slighty improve the chartroom. It's based on that limit=0 thing I suggested on the ListPages module. |
|
||
Goodnight! [[footnoteblock]] |
|
||
Goodnight! [[footnoteblock]] |
|
||
You know that link you sent me? Apple have disabled since a certain version of iOS, so I didn't think it would be worth the energy. Mini-chatroom is not official, but it looks like this at the moment: [[html]] I don't like the idea of having a separate “chatroom-mini” page, so that's why I haven't launched it yet. [[footnoteblock]] |
|
||
Also, How do I access the mini chatroom? [[footnoteblock]] |
|
||
Yes! Scrolling works! James, you might want implement a workaround for iOS HTML5 audio autoplay. Alert still not working… [[footnoteblock]] |
|
||
Wow! He even fixed the scrolling code!!! Now we can scroll using iOS devices!!! [[footnoteblock]] |
|
||
Awesomeeeee! [[footnoteblock]] |
|
||
Bryce added a css design for the saving page dialogue!!! [[footnoteblock]] |
|
||
I'm in the middle of implementing a mini version of the chatroom… [[footnoteblock]] |
|
||
I ended up converting to HTML5/Flash via the W3Schools HTML5 standards: <audio> tag [[footnoteblock]] |
|
||
Okay, I'm bringing this live to the actual chatroom. [[footnoteblock]] |
|
||
I implemented a new method of Avatar Grabbing: JavaScript Avatar Grabber. I've found it loads a bit faster than the server method :) [[footnoteblock]] |
|
||
Good luck! [[footnoteblock]] |
|
||
Well, goodnight James. I have a science practical exam tomorrow. Gotta get to bed now… Talk to you soon! [[footnoteblock]] |
|
||
I like it. It's simple and easy to see with the large avatars showing. [[footnoteblock]] |
|
||
And for some strange reason, none of Wikidot's odate spans work on Safari for iOS… [[footnoteblock]] |
|
||
Yeah :) [[footnoteblock]] |
|
||
You mean for the layout of the new chat message box? [[footnoteblock]] |
|
||
http://www.wdeditor.com/thread:159 [[footnoteblock]] |
|
||
What forum posts? [[footnoteblock]] |
|
||
That's a great idea! As you've probably noticed, I was inspired by Shane's forum posts… what do you think? [[footnoteblock]] |
|
||
Okay… BTW, I just switched to my iPod… I turned my PC off… [[footnoteblock]] |
|
||
Thanks for the link Kenneth! Let's try it out aye? [[footnoteblock]] |
|
||
Ahh… but Pieter is MA.
I don't have speakers… I'll go and find some headphones… HTML5 MP3 Audio Detection: https://gist.github.com/253174 [[footnoteblock]] |
|
||
Do you like the new chatroom sound? [[footnoteblock]] |
|
||
Well, that's what I was thinking too. I remember dwelling amongst "browser detection" code in order to manufacture something like that myself. Apparently browser detection is a discouraged technique in web development, however. [[footnoteblock]] |
|
||
This was originally an IronGiant Redirect site (your creation). It redirected you to "chatroom.wikidot.com" [[footnoteblock]] |
|
||
I think there are ready-made scripts to switch between Flash and HTML5 <audio> tag when they are capable :D [[footnoteblock]] |
|
||
And for some strange reason, I was a member of this site "537 days ago"…. [[footnoteblock]] |
|
||
It's all new to me, to be honest. I remember playing with the audio tag several months ago, and there were issues. For example, FireFox wouldn't play .mp3 sounds at the time, but every other browser worked. I don't know how much has changed since then though… [[footnoteblock]] |
|
||
Yes, the installation looks much simplified…
I looked at Chrome's developer tools and it said display:table cell (with the space)… I tried that and realised it didn't work and reverted to adjusting the width :D
Yeah, I haven't tried the new <audio> tag in iOS, does it work like the flash or as a separate player (like the <video> tag? [[footnoteblock]] |
|
||
Oh, something that I've had planned to do was to upgrade the code for the “new message” alert. Currently it uses Flash to play the sound, but I would rather implement a HTML5 solution… this would increase compatibility amongst devices (especially iOS devices). [[footnoteblock]] |
|
||
Mind you, it's not really that much of an upgrade. It's simply a few backend changes to simplify the structure. I didn't like that you needed to create 8 pages on your site to install the application. Now there's only 4 pages to create. And thanks to the advent of CSIs, this framework becomes much much easier to push updates and fixes. Currently the Chat application is not flexible in terms of customisation. But that will come later. [[footnoteblock]] |
|
||
Awesome :D [[footnoteblock]] |
|
||
Yeah, I was. It's fixed now :) Which means this chat upgrade is ready to go live! [[footnoteblock]] |
|
||
It's thinking outside the box! [[footnoteblock]] |
|
||
Impressive workaround! I have reverted the system back to the "display" method, which I like better because some browsers don't know how to handle text-overflow very well. All browsers know how to handle display methods. [[footnoteblock]] |
|
||
Golly! You're right! I (correctly) used the "display: none;" tag to hide the cell, but I incorrectly used the "display: block;" tag to show it. I have since updated it to the correct "display: table-cell;" tag. [[footnoteblock]] |
|
||
Also, are you aware of the bug is the currently active users? [[footnoteblock]] |
|
||
I made some changes. Fixes for Chrome… haven't tested for other browsers. Basically, instead of adjusting display in style, the width is adjusted. If css:2 isn't applied, the width is 0px with overflow set as hidden. When it is, the width is set to 200px with !important. [[footnoteblock]] |
|
||
Actually, solution:
chatarchive
[[footnoteblock]] |
|
||
Another bug? "Currently active users"…
[[footnoteblock]] |
|
||
James, I found the problem. Remove the display:block;… [[footnoteblock]] |
|
||
Works at school :P [[footnoteblock]] |
|
||
Strange… it appears that the first <td> isn't extending to it's full length… [[footnoteblock]] |
|
||
Funny bug, I can't work it out… the “Currently Active Users” section should be 200 pixels wide, and be aligned to the right (adjacent to any visible vertical scroll bars). Can anybody work it out? [[footnoteblock]] |
|
||
Eleven! [[footnoteblock]] |
|
||
Ten [[footnoteblock]] |