February 20th, 2012 by Aaron N.
Alas, it’s all jQuery stuff, which is fine if you aren’t already using MooTools (really, if you just want Bootstrap and nothing else, use jQuery). But if you’re hooked on MooTools and want to use Bootstrap 2.0, I’m apparently still the only game in town.
So what’s new in MooTools Bootstrap? Mostly just support for all the breaking changes in Bootstrap 2.0. If you’ve already got a project running Bootstrap, you don’t need to upgrade unless you want some of the new features there (like the flexible layouts for mobile and whatnot.
Updating for Bootstrap 2.0
- All the “*.Twipsy” files are now “*.Tooltip” to reflect the change in Bootstrap
- Numerous conventions changed in Bootstrap 2.0. In particular things like tabs, tables, and dropdowns now prefix their component name to all their classes (table-striped instead of zebra-striped, “btn btn-primary” instead of “btn primary”)
- Added support for drop down lists in tabs
October 17th, 2011 by Aaron N.
In my previous release of bootstrap I complained about my inability to test in IE. A few of you were kind enough to hit my specs and let me know that my low expectations of IE were not unfounded. Well, I finally got bootcamp and VMWare installed and went through the super-happy-fun-time that is IE debugging and this release has all my latest stuff working in IE8 at least.
In today’s release:
- Various IE fixes to Autocompleter, Behavior filters for Autocompleter and StickyWin
- Updated specs expectations which were ignored because I can’t remember the names of my own options signatures.
- StickyWin.Fx is nerfed for IE. IE users don’t get fading! Deal with it!
- Various fixes for IE
- Updating docs for inline JSON options – they previously stated that you didn’t have to quote the names in the JSON object; this was never true.
- Updated for MooTools More 126.96.36.199
- Various fixes for IE support
- Dropdowns no longer hide when inputs or labels in the menu are clicked.
- More support for browsers w/o CSS animations (they don’t get any animation at all, but they don’t break either). Old versions of Firefox and IE for example.
- Various IE fixes.
There you has it. Nothing really sexy, but hey, you get what you pay for.
August 9th, 2011 by Aaron N.
I’ve recently been working on and posting about the development application that makes it easier to get started working on and working with MooTools. For those of you who haven’t followed it, the app is a deployable Django app that lets you see docs, demos, benchmarks, and a builder for any combination of MooTools projects.
Today’s release allows you to run more than one configuration at a time:
That means it’s fairly easy to jump between MooTools 1.2, 1.3, etc. What it means here at Clientcide is that users can now browse the docs and download / view multiple past versions (at the moment, only 2.2.0 – the last stable version running on MooTools 1.2 – and the current release).
Support for “Fiddle” demos
MooTools.net recently revamped its demo system and now all the demos you see on mootools.net are in a stand alone git repo.
The demo runner in the dev app now supports these files as well.
Give it a try
As always, the system remains fairly easy to install and play with.
$ git clone git://github.com/anutron/mootools-development.git
$ cd mootools-development
$ ./go install # or just "./go i"
$ ./go depender_check # or just "./go d" - this checks the JS dependency tree
$ ./go run # runs the server on port localhost:9876
The code can be found on github, of course.
May 28th, 2010 by Aaron N.
I know, it’s been a while. A long while. What have I been up to? Oh, a little bit of this and a little bit of that and maybe a pinch of this.
And speaking of what I’ve been up to, I’ve mostly been focused on my job at Cloudera, which is teh awesomes. How awesome? Well, I work in an awesome space with awesome people on awesome projects.
Here’s our sales pitch:
- 3+ years of experience in developing web UI applications.
- Significant experience in developing AJAX-enabled web applications
- Experience in coding standards-compliant semantic markup in XHTML/CSS
- A passion for writing super optimized and clean code
- Some experience designing user experiences; a working knowledge of Photoshop and Illustrator
- Experience with data and information visualization is a strong plus
- Experience building web applications in Django/Python
- Experience developing desktop applications UI (e.g. with Adobe Air)
If you’re interested, ping me and send me your resume.
January 15th, 2009 by Aaron N.
Last fall I gave a talk about MooTools at the Ajax Experience in Boston. Adobe just put it online and I thought I’d share. This talk is first an overview of MooTools and what it has to offer and then delves a little bit into my pattern programming principles that I’ve been blogging about here lately.
I’ll point out that this was at 8am on the last day of the conference and it takes me a few minutes to really get going. If you’re already familiar with MooTools there’s nothing new here for you (probably). The whole thing is about an hour and twenty minutes long…
December 24th, 2008 by Aaron N.
It’s xmas eve and I don’t have time to explain it, but I will later tonight or tomorrow. I’m removing Element.Delegate from my repository for now. Basically, it was premature. It just wasn’t ready for release and I don’t have time to fix it. I’ll revisit it in the next few days.
January 24th, 2008 by Aaron N.
There are three types of error handling that I use:
- Graceful: if possible, just ignore the error and continue with some default state or without a meaningful value
- Debug: throw a warning to the dbug.log method but continue otherwise
- Break: Either explicitly throw an error or (more often) just let the error that is thrown at runtime be thrown
Read the rest of this entry »
June 26th, 2007 by Hamm
There is a new “Facebook” application that utilizes CNETs great API system. This app that was developed is called “My Tech”.
Apart from the great technology use, it is a fun way to show off your latest tech gear to your friends. The best part is you can show your disdain for certain tech products if you absolutely hate it… Good times
“Tag line from app profile”
This application allows you to let everyone know about the latest tech gadgets available using MyTech powered by the CNET API. Facebook users can find it at: http://mytech.cnet.com
CNET Report on CNET MYtech
March 14th, 2007 by Aaron N.
Valerio posted over on the Mootools forums today a list of changes in the upcoming 1.1 version of mootools. We’ve been hard at work on a lot of this stuff and I’m excited to see it come out. After this version, we anticipate working less on the core framework and more on plugins and widgets.
- CUSTOM EVENTS!
- $each also iterates objects
- added Element::getStyles
- added Element::hasChild
- added Array::include
- added Array::merge
- added $merge, to merge objects
- Dom.js uses XPATH in supporting browsers
- the use of +’px’ in setStyle is not required anymore.
- added XHR::cancel
- Object.extend is now $extend, still compatible
- Object.native is now $native, still compatible
- Element has been splitted in Element.Events, Element.Form, Element.Dimensions
- elements creation is easier: new Element accepts second param
- elements creation for elements with name/type is easier, just use second argument.
- setProperty for name/type are is supported anymore.
- dom logic is highly optimized and its blazing fast
- better sortables, no more flickering, removed Drag dependency
- Fx.Slide now accepts borders and margins. Positioning is now possible.
- Element::toQueryString in ajax now works as intended with all Form elements, including multiple selects.
- Element::setStyle supports float
- Element::setProperty and Element::getProperty now supports “for”
- code cleanup and optimization
- bugs and incompatbilities fixed
- mootools is faster, FASTER, FAAASTEEERRR
- some bugs left
- css3 selectors (?)
January 18th, 2007 by Aaron N.
I’ve updated my Mootools Tutorial for the upcoming version 1.0 of the library. It (the library) is still in development, so my tutorial is likely to always be a little behind the svn, but if you’re digging into Mootools for the first time, or you want to see what’s different in version 1.0, here’s the place to start.
I’ve also installed a copy of docuwiki for all my example and tutorial work. The old stuff is still there but I’ll be moving it all over to the wiki. Expect to see more examples of code I’ve written in the coming weeks.