Drop Down Menu
Menu Module Example
Grouped Child Menu
S5 Vertex Framework
Template Specific Features
Vertex Template Features
J! Stuff
Joomla and Vertex Tutorials
Continued Vertex Features
Drop Down MenuUnlimited Level OptionsMenu Module ExamplePublish Any Module to Any Menu
Grouped Child MenuGroup Children TogetherS5 Vertex FrameworkLearn More About VertexTemplate Specific FeaturesOptions For This TemplateVertex Template FeaturesPowerful Template SettingsJ! StuffDefault Joomla ItemsJoomla and Vertex TutorialsVertex and Joomla TutorialsContinued Vertex FeaturesMore Great S5 Vertex OptionsJoomla and Vertex TutorialsVertex and Joomla TutorialsToday marks the release of MooTools Core and More versions 1.6.0. This is a minor revision that delivers a number of bug fixes as well as the introduction of new features.
The main new adition is Class.Thenable which is a new Class mixin that can be used in Promise style flows by using its then method. When implemented in a Class, it makes the class "thenable" in the Promises/A+ sense of the word, meaning it can be used in Promise style flows by using its then method.
The implementation, however, is more than just a "then" method. Any instance of a Class implementing Class.Thenable is a Promises/A+ compliant object (generally referred to as "a Promise") with only one exception: it is possible to reset the Class's value resolution state fully (rejecting pending reactions, and starting empty) to support a Class instance living for longer than just the lifetime of one value resolution.
Example using Request:
var request = new Request();
request.send().then(function(response){ console.log(response.text); });Example hooking into a native Promise:
var request = new Request();
var promise = Promise.resolve(request);
request.send();
promise.then(function(response){ console.log(response.text); });You can find this new version 1.6.0 in the website or within the dist folder of the 1.6.0 tag (Core).
IE warning: This will be the last version to support old IE browsers. Next minor and/or major versions should be only IE11+ compatible. We might still release some patch in the 1.6.x version if needed.
Array.from deprecated, now called Array.convert: Following the conclusion of the ES6 specs we know now that Array.from will have a different implementation than the one MooTools uses.
Because of this we renamed Array.from to Array.convert to not overwrite the Native implementation.
We kept it as it was though in the compat layer for compatibility reasons if you really to use it still.
To keep the API consistency we changed also the name of the method in Function, Number and String Types.
The main changes in this release are:
.from method in Array, Function, String and Number (#2758)(#2760)$pick gets exported to global (#2735)Event Class gets exported to global (#2733)keepOpen to Accordion (#1333)onSort function arguments (#1332)validate-match "matchName" when containing spaces(#1186)unDraggableTags in Drag (#1159)validate-reqchk-byname (#1329)Today we release MooTools Core versions 1.5.2. In this new version there are some fixes for raised issues and also some new stuff!
You can find the new version in the dist/ folder of the Github repo or on the website.
The main things in this release are:
input[type="email"] (#2705)+ into spaces (#1313)Today we release MooTools Core and More versions 1.5.1. This continues our improvement work for both Core and More and introduces also some features that were in the queue for being added. This release fixes also a regression related to the mousewheel event.
When preparing the 1.5 release we decided that Core 1.5.x will work with More 1.5.x. This means that, inside the 1.5 space, versions should be compatible and you might be seeing Core or More releases that are not simultaneous.
In 1.5.1 we added a new dist/ folder in Core, present at the tagged commit, for those who want the Core source, as well as a needed update so you can get MooTools via Bower.
Worth a notice is also the new MooTools Packager. MooTools has always been about modularity, and for those of you that want to choose which modules to use you can now use the new MooTools Packager (for Node.js/Grunt), as well as the website builder. The new Packager allows to compile source files from the dependencies in the YAML header. You can find it on GitHub and NPM.
The main things in this release are:
1.5 is a HUGE bug fix release with roughly 240 commits addressing new browsers that have entered the market as well as new features in the JavaScript language. The team spent a ton of time instrumenting the tests to run against Travis CI and Sauce Labs so that the source code would be easier to test. This will help to make new contributions, fixes and features to the framework and release much more rapidly.
It's easy to underestimate the value of all the work that went into the project over the past two months.
On our road to Version 1.5, we're trying to eliminate some bad practices from our code. One of the things we've just gotten rid of, is that a few last pieces of our libraries still depended on Browser UA detection. This has all been eliminated in favour of feature detection. To help us reach a decision on where to go with the Browser module, here's a quick survey. Reply via @mootools or leave a comment here.
S5 Vertex FrameworkTemplate Specific FeaturesVertex Template Features
J! Stuff
Joomla and Vertex TutorialsContinued Vertex Features