2 points before review
-
Hey Jeff, looks like a cool plugin!
two quick points before I rate it (one also posted as a comment to your reply but it seems you can’t see those):
1) changing the sound file (there’s only one) like you explained is damn easy, yes. “Look in the /resources/ file for the sound files. You should recognize them by their extensions. Replace any that you would like, it’s designed to work that way so it’s easy.”
But we did, and have no caching plugin running, and still, magically you play that VERY odd standard file still. Any idea why?(Tip, use a different standard file, that one you used sounds SO WEIRD… like aliens trying to speak sth??)
2) And an improvement suggestion (or else I can’t give 5 stars):
“By default, the plugin includes its JavaScript on every page. To prevent this, and to include its JavaScript only on the chat page, enter the URL where it’s displayed.”
The possibility to limit extra server/browser load is smart foresight, thank you, but for a page URL?
No. Obviously users will want to limit loading to where they actually display the chat. Most will display it in a widget (and if for logged-in users only, then obviously in a widget-logic controlled widget for logged-in users only. ??
Thus I suggest to load its Javascript only on pages where the chat is used (eg in a widget on certain pages). Can you not code it with a hook checking if the chat is displayed on the page? Would be easy. And then loading its Javascript in the footer (at the end).
Hope you have a minute to reply to both points. Thank you.
- The topic ‘2 points before review’ is closed to new replies.