One thing I didn't note yesterday is that currently Behavior is written against MooTools 1.2.5. I'm working on a 1.3 version of it currently.
> Yeah, I'll send instructions tomorrow. If you can't wait, check out the > "behavior" branch of my mootools-development repo on github. > My "mootools-development" repo is designed to make portable environments that pull together numerous repositories that work in a specific state (i.e. a bunch of submodules that represent a working state). https://github.com/anutron/mootools-development If you want to use it, just follow the instructions in the readme. One thing about that environment: once you run the installer, it's best not to switch branches as you'll get a bunch of artifacts. So, if you wanted to check out the behaviors branch, clone the repo to our computer, check out the behavior branch, THEN run the installer. Note the prerequisites (python, crepo, virtual-env). > 2. I would like to see how extensions of behavior look like - and how the > assigned methods variable is used or interaction (I really really like this > pattern - very cool use of dependency injection). > > Check out my more-behaviors repo. > http://github.com/anutron/more-behaviors You can find example filters and html tests for these there. > 3. I've noticed that Behavior uses ART, so 2 questions about that: a) What > parts of ART does it use? I failed to find any. b) Depending on the previous > q - how hard will it be to port it to normal apps? > > It doesn't depend on ART. Where did you see that? > I've updated it. It now requires only content from Core and Table, which will soon be part of More (but isn't yet). You can get table from http://github.com/anutron/mootools-table in the mean time (or use the branch of More that has it, which you'll get if you use the mootools-development environment).
