Okay, let's break this down.
Quote:
Originally Posted by Super-six
The response I received at vBulletin.com:
"I wouldn't recommend allowing users to use HTML in posts..."
I understand there are security issues with this.
|
That has nothing to do with AME. vBulletin.com is talking about the option in your Admin CP that let's users post raw HTML code in posts. You don't need that for AME and is kinda the point of the modification to begin with. AME takes a link and converts it into a predefined embed code. All the JW Player definitions would do is convert a link into the embed code defined for it. No security risk or posting of raw HTML involved.
Quote:
There is a real need for an alternative to the 2 or 3 MODS that are
currently in circulation. I dont really need 250 definitions. Just
the standard YouTube and a handful of most common works for me.
Im just after something a bit nicer. More sleek and refined.
|
That's why I provide every definition separately. You don't have to import all 250+ if you don't want them. But I provide a Master XML file in case people do. They're still available seperately in the ZIP file provided. You should really read over The Geek's thread and my Add-On thread more closely, as you'll see that by default, AME only comes with 2 supported sites, and then you can import more as needed from my thread.
Quote:
If you have a way to facilitate the use of JW Player Im all ears. :erm:
|
As I said, they're definitions I'm working on for AME. No, you don't need to import all 250 definitions. You can just import the ones I release (if I release them) for the JW Player. (Though that would be in a separate release thread, as you need some additional files for the JW Player to work.) Though, it won't matter. AME works just as well with all 250 sites installed as it does for two. You don't even have to tell your users you've installed it, if you don't want to, as the videos will auto-convert as soon as they post a link. No BBCode involved.