|
Connexion
News Rss |
Blog » MooTools - Home
jpdery | 2012-04-24T19:22:09+02:00
Moobile is a mobile web application framework built on MooTools. It focuses on building mobile apps that behave as close as possible to their native counterparts, either on a mobile browser or on a webview wrapper such as Phonegap.Moobile is also meant to be extended. I believe one of the strengths of a mobile web app is the ease of creating something entirely different. Moobile helps in this area by providing a structure as well as controls, view and controllers that can be easily extended to suit your needs.Moobile relies on external stylesheets for presentation and animations which makes it easy to customize. Rules that should not be changed are marked with an /* Important */ comment. ...
Arian | 2012-02-27T03:00:45+01:00
| 2 reads
MooTools Core 1.4.5 is a maintenance release for the 1.4 branch.1.4.5 brings a critical bugfix for Fx.CSS which caused many troubles for tweening and morphing your element styles. The bug was caused by a fix in 1.4.4 which should improve animating other length units like % or em (see #2160. Many of you noticed the bug and filled bugreports and also helped us testing this new release.We have improved our tests and are planning to freeze the code for a new release for a longer period so we can gather more feedback to prevent potential regressions. If you’re interested in testing a new release in your application, you can ping us on IRC (#mootools on freenode.net), Twitter (@mootools /...
ibolmo | 2012-02-07T17:30:11+01:00
| 2 reads
Today we release MooTools Core 1.4.4 which is a critical maintenance release. 1.4.3 release introduced a bug as a result of fixing another bug. Specifically, 1.4.3 did not allow custom attributes (e.g. data- or non-standard attributes). See this issue for a full explanation and solution.We recommend that all users upgrade to 1.4.4 as soon as possible.Fixes#2160: Fx.Tween/Fx.Morph problem with ‘%’ unit#2175: IE Leak: Array.flatten#2178: IE doesn’t set value when creating element if css attributes are used#2241: Slick.finder index selector#2247: Element.get not reading custom attributes in IE7/8#2248: contains causes “Out of Stack Space” in IE#2252: Element.get...
ibolmo | 2012-01-21T18:59:21+01:00
| 1 reads
Today we release MooTools Core 1.4.3 which is a small maintenance release. Upgrading from 1.4.2 should not cause any backward incompatibilities. We recommend that all users upgrade to 1.4.3 as soon as possible.Fixes#2109: IE7/8 getProperty returns functions#2110: Documentation: Request.JSON’s behaviour of onFailure#2117: Document conflicts between Array and Elements methods#2121: Missing Fx.options.frameSkip documentation.#2126: Re-add undocumented from argument to Element.fade#2127: Element.js memory leaks#2146: Add Element.NativeEvents to docs#2150: Add Fx.isPaused() method#2152: Packaging issue. Build header and Core.js yml header collide#2155: Add special note to Element.empty#2...
aaron | 2011-12-26T21:02:37+01:00
| 1 reads
Jon Bomgardner is a contributor to the jxlib.org project. After recently joining the MooTools Developer mailing list and sharing his experience in upgrading jxlib to MooTools 1.4.2 we asked him to share his work here on the blog.What is JxLibJxLib is a JavaScript UI framework built on MooTools. It allows web developers and designers to quickly build user interfaces for their applications. JxLib is based on some sweet HMTL markup and strives to be fully CSS compliant. It is also a modular library allowing you to pick and choose from the available components as well as giving you the ability to override default behaviors and extend core classes.All of this flexibility is, in large part, du...
aaron | 2011-12-21T01:51:54+01:00
Those of you who follow my work over on Clientcide may already be familiar with it, but for the rest of you I wanted to write a blog posts here on MooTools.net about the work I’ve been doing on a library called Behavior - a throwback to the behavior.js library released way back in 2005 which one might consider to be philosophically an ancestor of sorts.PurposeAll well-written web sites / apps that are interactive have the same basic pattern:Each page of a site or app you build is esoteric. It may have any combination of interactive elements, some of which interact with each other (for example, a form validation controller might interact with an ajax controller to prevent it sending ...
ibolmo | 2011-12-02T22:03:31+01:00
Today we release MooTools Core 1.4.2 which is a small maintenance release. Upgrading from 1.4.1 should not cause any backward incompatibilities. We recommend all users upgrade to 1.4.2 as soon as possible.Fixes#2073: Reduced redundant call to onTimeout if async option is true.#2083: Fixes Element.clone in IE. #2085: All specs are green across.#2110: Element.erase('class') did not clear the class.#2113: button.set('type', 'button') is now fixed for webkit bug.#2116: Fixes Element.fade chain.#2118: $uid method is no longer exposedImprovements#2089: Added support for native mouseenter and mouseleave. #2134: Deprecates the MooTools Core Specs repository in favor of including the specs in the ...
fakedarren | 2011-10-19T00:55:47+02:00
Just a quick update to let you know we’ve added comments through Disqus to all Forge plugins.If you’re a plugin owner, you can subscribe by going to your plugin page and clicking ‘subscribe by email’ at the bottom.Remember, if you find a bug in a plugin, you should always report it in that repository’s Github Issues.As it stands, all comments will need to be moderated before they appear, just to make sure we don’t get trolled / spammed and we’re really looking forward to adding the ability to comment to the other parts of the website - particularly in documentation.Thanks to Aaron for making this happen!
cpojer | 2011-10-06T21:01:19+02:00
| 1 reads
Today we release MooTools Core 1.4.1 which is a small maintenance release and as such only fixes bugs that were introduced in previous releases. We have fixed the mousewheel event in Firefox, Element.fade sets the visibility CSS-property again, Event.Delegation now behaves properly if you use fireEvent and we have fixed a couple of issues with Element.setProperty and Element.removeProperty.Upgrading from 1.4.0 should not cause any backward incompatibilities. We recommend all users to update to 1.4.1 as soon as possible.Get it!Download MooTools Core 1.4.1; Build MooTools Core 1.4.1Fork / clone MooTools Core 1.4.1 from GitHub, and build it yourself with Packager.Google CDN (will be updated ...
Arian | 2011-09-10T16:16:16+02:00
| 3 reads
As of today a new version of MooTools is available. This includes MooTools Core and MooTools More. We’ve communicated a lot about changes for 2.0 but we also felt we had some good stuff that would benefit you directly which we wanted to add to the 1.x releases. This good stuff contains of course numerous bugfixes but mostly one important new feature for MooTools Core: Delegation. This 1.4 release should be fully backward compatible with the 1.3 series.So all changes for 1.4.0:Move Delegation into Core.ECMAScript 5 compatibility fixes. Among them are Function.bind, Array.map and String.trimDeprecate Element.setOpacity() and Element.set('opacity'). Element.setStyle('opacity') is the o... |