Create a Joomla Extension

Module / Plugin Specification --------------------------------- 1. The plugin needs to add two remotely hosted scripts into the head tag on the page. The script tags need to appear last (after all other scripts) in the head section of the webpage. The script should be referenced so that it will use the same protocol as the webpage connection (either http:// or https://). They should never be cached and served locally as the script is dynamic in nature and will change. Script 1: "//[login to view URL]" Script 2: "//[login to view URL]{AppID}" 2. The plugin needs to have a configuration form that can be used to easily save the users AppID to the system. The AppID will be used to construct the url to the second script in part 1 of this spec. 3. The plugin should have a configuration form which allows the user to choose which pages on the website where the scripts will be loaded, as they may not want the overhead on every page. It should however default to load on every page. 4. The plugin needs to add a shortcode / input filter to the system which allows the user to easily add our proprietary markup to their webpage. In other words, the user would write a shortcode while creating content that would be translated into a custom html element. This html is very simple. In fact, the short code will create a single <div> tag with any specified options being written into a "data-bbflex" attribute of that div tag. The options that the user can specify should be flexible to include unlimited definitions. An example of the rendered html element would be: <div data-bbflex="{ widget: 'fwplayer', width: 620, height: 150, cart: 'off' }"></div> Notice that the data-bbflex attribute is written in JSON notation and is interpreted as such by our scripts. But the shortcode should allow defining the attribute options in whichever method is considered "best-practice" or conventional to the CMS. An example of our preferred shortcode format would be as follows for the example mentioned above, unless another format is considered more suitable for the CMS: [bbflex:widget=fwplayer,width=620,height=150,cart=off] As mentioned, the shortcode should support any number of configurations, so the shortcode could also be any of the following: [bbflex:widget=fwplayer] or [bbflex:widget=fwplayer,opt1=val1,opt2=val2] or [bbflex:widget=fwdock] That's It!