|
Post by Dashe on Jun 11, 2010 16:25:49 GMT -5
In time for what? No pressure, Chiz.
|
|
|
Post by Pitch on Jun 11, 2010 16:54:05 GMT -5
No pressure indeed. It's 2010; why cross-browser compatibility is still even an issue completely perplexes me... I blame Google/Mozilla/Opera/Microsoft/etc. Any chance you'll be able to do short codes for these? Using the full tag is nice, but it doesn't work great in signatures where character count is a concern.
|
|
|
Post by Chiz on Jun 11, 2010 17:28:08 GMT -5
It's fully working in Chrome (or at least, Chromium for Windows) as of 0.97.5. It's fully working in Opera as of 0.98.1. It's fully working in Safari as of 0.98.5. (and for those keeping track, it's fully working in Firefox as of 0.95.0, but w/e)As for Opera, Proboards function for adding emoticons never worked in the first place, meaning that while they display as of 0.97.5, they cannot be clicked. I'll try to investigate if it's repairable or not. Totally fixable, and as such fixed, as of 0.98.1 Currently investigating whether or not the Chrome solution works in Safari. EDIT: Safari's being finicky. No Safari support for now, although it is compatible with short code use. Finally got it to behave. Working as of 0.98.5 0.97.5 0.98.2 (or any of its successors, if more fixes are found) will be uploaded this weekend. Uploaded and superseded. @green: I'll look into it. Looked into it. Implemented as of 0.98.2. EDIT: Also sometimes the Emotikobun make an appearance in the advertisements bar at the top of the screen in Opera and Chrome. Fixed as of 0.98.0. EDIT2: v0.98.0 - Emotikobun no longer appearing in ad bar in Opera, Chrome; initial tests for emotikobun shortcodes working in FF FX, Opera, Chrome (will probably serve as an effective backdoor for Opera users until I can fix the add function). EDIT3: v0.98.1 - Opera can now add smilies on click (including original 16), fixing Proboards' forum code bug. EDIT4: v0.98.2 - Shortcodes now working in FX, Opera, and Chrome for all new 32; Removed IMG-based codes for the smilies. The new codes will be a colon, followed by a 2-digit number, followed by another colon. The 2 digit number goes from 01 to 32, where 01 to 16 are the first (middle) row, and 17 to 32 are the second (bottom) row. EDIT5: Sent v0.98.2. Hopefully update soon! EDIT6: New bug found...Opera click support seems to fail once you've typed in or erased from the textarea... *sigh* EDIT7: v0.98.3 - Fixed Opera click bug EDIT8: I'm no longer going to update this post; check the first post for updates.
|
|
|
Post by Blues on Jun 12, 2010 22:23:34 GMT -5
These weren't working for me earlier, and I was on Firefox. :06: Odd.
|
|
|
Post by Chiz on Jun 12, 2010 23:10:10 GMT -5
0.97.0 and .1 broke Firefox support. Superseded.
New bugs: Apparently Emotikobun Plus! is breaking the forum's search function! Back to work... :01: Fixed as of 0.98.4.
Important note to everyone: If you don't want to participate in this increasingly apparent open beta, block the emotikobun.js file from loading in your browser. This can be done with any ad-blocking or content-blocking mechanisms. However, it would be appreciated, if it isn't troublesome, to continue to use it, and report any abnormal issues you have.
|
|
Qwertman
Habarool
Work work work...
Posts: 736
|
Post by Qwertman on Jun 13, 2010 9:28:32 GMT -5
Proboards seriously doesn't support the adding of new smileys? It seems rediculous to me that you need to go through all the trouble of creating this script.
|
|
|
Post by in·clover on Jun 13, 2010 15:24:11 GMT -5
That was bothering me for the longest time. I was actually typing in a lot of the [b ] [ /b] kinda stuff manually because of that. :15: Thanks for doing all this.
|
|
|
Post by Mr. Ninja on Jun 13, 2010 19:11:49 GMT -5
Thanks for the new emotikobuns, Chiz! :24: You spin me right round!
|
|
|
Post by Chiz on Jun 14, 2010 0:27:17 GMT -5
@bret, Mr. Ninja: yw
Another announcement to everyone - surely a few of you have noticed a drastic increase in load times on the forums, and I can pretty much confirm that it is due to Emotikobun Plus!. The script is very intensive (you will see a larger-than-usual CPU spike when loading a page on MMLS) and takes a couple seconds for even the swifter browsers to sort through (Firefox 3.6 on Windows takes about 3-4 seconds), and you may get popups saying "script frozen", etc. It hasn't frozen (probably), it's just fighting through large data manipulation procedures. I'm not entirely sure how I'd speed this up, but any optimizations I think of will be included in future revisions. On the plus side, all of the major browsers are fighting amongst themselves of having the shortest javascript execution times, simply because these sorts of abusive scripts are becoming the norm, so even if I can't improve it much, you can still expect faster speeds within the year. As always, if this is too much of a sacrifice, or EKP is somehow breaking something else, you are free to disable the JS file from loading in your browser. Nothing else is required, and the original fast loading times will return immediately.
|
|
|
Post by Dragge on Jun 14, 2010 8:55:02 GMT -5
You know I haven't seen any of the new emotikobuns on my post reply screen. Maybe it's because I'm running off of an internet explorer. From what I've seen though the new ones look pretty sweet!
|
|
|
Post by Chiz on Jun 14, 2010 17:01:07 GMT -5
I'm running off of an internet explorer. Why? MSIE may, in the future, work, but currently Emotikobun Plus! is locked to browsers that I can confirm are working, which are Firefox (and other Netscape-likes), Opera, Chrome, and Safari. Historically, Microsoft has been incredibly deviant in their web standards implementations, so I will not be focusing on any MSIE-related issues should (when) they come up once the script is unlocked for every browser. It may seem unfair and inconsiderate, but not having to deal with a troublemaker of the web design world is incredibly liberating.
To everyone else, 0.98.5 is currently employing the board's censor function to achieve relatively speedy short code swaps. I'm hoping in the near future, I can switch handling back over to EKP, because it allows for greater flexibility and compatibility with their intended usage.
|
|
|
Post by UNIT 0918 on Oct 1, 2010 21:04:21 GMT -5
The only thing I don't like about the Emotikobun Plus is how it deletes everything I wrote while the page was loading. :/
|
|
|
Post by Pitch on Oct 1, 2010 21:05:38 GMT -5
Is that why that happens? I thought it was just a bug in my browser or something. That has been absolutely driving me crazy. :24:
|
|
|
Post by UNIT 0918 on Oct 4, 2010 1:46:45 GMT -5
I'm quite sure it is. This never happened until Emotikobun Plus was released. Maybe it's because it takes longer for the Emotikobuns to load than the page itself. It deletes my new text everytime it finishes loading them.
|
|
|
Post by Chiz on Oct 4, 2010 7:34:03 GMT -5
The reason why the post-page flicker occurs is a side effect of how Emotikobun Plus! has to work.
Semi-technical explanation follows. Do not read if you have a history of mind borks or glossy/blurry vision when confronted with such materials.
EKP is loaded and run at the very end of the page, once everything is rendered. There are 2 reasons for this - first, it's impossible to place JS triggers anywhere other than the beginning (header) or end (footer). Second, for EKP to show up at all, it needs to make a rather large number of code additions and replacements to be compatible with Proboards. Most of these procedures end up being very hackish in nature due to the highly disorganized nature of the forums' code.
The largest and most obvious of these replacements is that I need to go through the entire pages' code and replace all instances of a shortcode ( :00: ) with the appropriate HTML code for displaying an image. The current method of doing so is to load the entire page into memory, make the replacements in memory, and then tell the browser to throw away the original document and rerender what I've altered in memory. This single rerender can't be seen under ideal circumstances, but ideal circumstances are all too often infrequent. Under non-ideal circumstances, the most visible side-effect to this approach is a full-page flash/flicker, as everything is deleted and restored with my modified version. (Please note: This is a vast improvement over pre-98.6 versions, where I modified the browser's copy directly, resulting in almost 50 redraws/'flickers' instead of just 1; it also took about 3-10 seconds for the process and often locked up your browser while doing it.)
There's unfortunately one small flaw in this plan. I replace every shortcode in the page, including the ones in the textbox. This means that, were you ever to use EKP's additional icons, modifying your post would result in a large chunk of HTML code appearing in your text box (due to the shortcode replacement pass done on the modifypost page; this code does not (should not) actually exist in anyone's post). Since Proboards doesn't allow you to post HTML code, it means that everytime you modified your post, you'd have to replace all that HTML with the shortcode again. This would become an incredibly annoying nuisance that I would no doubt receive endless complaints about. Simply put, EKP would be useless because few would go through the hassle of covering for its flaws.
This is my post <img scr="http://www.legends-station.com/forum/emotikobun/emote.png" title="ohgodhowdidthisgethereiamnotgoodwithcomputer" /> ^ - bad.
So, what I decided to do was, during my shortcode replace pass, I saved the contents of the textbox (if there were contents - I don't bother if it's empty), perform my whole-page replace, and then replace the botched textbox contents with my saved copy before the replace. That way, the shortcodes in your message stay shortcodes, but every other instance of them is changed. Unfortunately, like everything else, is only seamless in ideal circumstances. Under non-ideal circumstances, the result is that the page loads, your message is visible, and then the contents of the box get deleted and replaced with the same contents again.
Now, understand, none of this is instantaneous. Never will be. Things take time, and more complex things take more time.
So the end result is that someone goes to modify a post and the original page comes up. They start hammering into a message when my in-memory replace antics finally finish and are ready to be shown. The page gets deleted (along with the person's message), my new page (which was snagged before the user started typing) appears, and then finally the original version of the user's message appears. The user's new message from the last 2-3 seconds has vanished and is unrecoverable. Cue complaints. :01:
Technical explanation ends here.
There are a few solutions I could try (such as delaying the textbox snag as late as possible), but there will always be some brief period where page replacements must be done, flicker can/will occur, and bits of a message will be lost. The easiest solution is to wait a second or two before hammering into a post. The most foolproof solution would be to write all your longer posts in notepad, but that isn't a very good solution and may be a bit too involved for some people.
I do appreciate the feedback, though; if a little bit of flicker and a few seconds of text disappearing is the worst that you guys can find, I think I've done a pretty good job. Hopefully I'll be able to find more room for improvement to eliminate these minor nuisances... The version number for the current Emotikobun Plus! is always listed in your post window; if you notice the number changes, please take the time to test out general usability to make sure everything still works. EKP has interfered with the strangest of things in the past, so please post about them as soon as you notice them.
EDIT: I should also point out...this is a feature a put in a few revisions ago...if EKP ever causes a serious problem which breaks something or other (like it did with polls), go into the title bar and add "&ekp=0" to the end of the URL. This will disable all EKP operations on that page, but it isn't permanent and will reenable once you've browsed away from it. Example: http://mmls.proboards.com/index.cgi?board=comments&action=post&thread=3553 becomeshttp://mmls.proboards.com/index.cgi?board=comments&action=post&thread=3553&ekp=0 .
|
|