MageBridge patch for RocketTheme Mynxx
Wednesday, 17 March 2010We are happy to announce the release of a MageBridge patch for the popular template RocketTheme Mynxx. The Mynxx template is sold on the RocketTheme website and gives a nice look to your Joomla! site. Also, the Mynxx template ships with some nice add-ons for VirtueMart, which we have rewritten to MageBridge.
Our patches for the RocketTheme templates
As new templates are released regularly by RocketTheme, we will come up with extra CSS and images to integrate those RocketTheme templates nicely with the Magento Default Theme brought to Joomla! through MageBridge. This makes it possible to setup a Magento shop within Joomla!, with no knowledge of HTML or CSS.
VirtueMart to MageBridge
The Mynxx template ships with some nice modules for VirtueMart, among which a product-scroller and a nice login-panel. Those modules are now ported to MageBridge and shipped to all customers who purchase the Mynx template at the RocketTheme site plus our Mynxx template-patch at the Yireo Shop.
Due to copyright issues we can not ship the modules apart from the Mynxx template-patch. If you want to use the product-scroller and/or login-module apart from the Mynxx-template, you probably need to contact RocketTheme to get their permission.
Dynamic switch of MooTools to ProtoType
A technical note is that there is always the struggle between different JavaScript frameworks, as Magento uses ProtoType by default while Joomla! prefers MooTools. If ProtoType or MooTools are combined on one single page, the JavaScript functions on that page will be broken. There for MageBridge offers a set of configuration options (plus an awfull lot of documentation) to guide you in the process of setting up a clean JavaScript environment.
One of the tricks is to disable MooTools on MageBridge pages, but to disable ProtoType on other Joomla! pages. The VirtueMart login-module developed by RocketTheme is based on MooTools, so disabling MooTools on MageBridge pages also disables this module.
We have fixed this by adding some extra logic to the login-module, which makes it possible to use the original MooTools-scripts as long as MooTools is loaded. But as soon as ProtoType is loaded and MooTools is disabled, the module loads a little piece of ProtoType scripting which accomplished the same task.
This kind of auto-sensing the loaded JavaScript framework, and using different pieces of JavaScript-scripts for the same purpose, is part of an ongoing effort at our side (Yireo) to ease the use of both JavaScript frameworks and - more importantly - the conflict that exists between them.