Tag Archives: mootools
How it works
A regular expression looks for text outside HTML tags. It uses a callback function to perform replacements to simulate native lookahead support.
When is this sort of replacement suitable ?
- Remote HTML responses (ajax) highlighting
- Autocompleters suggestion highlighting
- User-typed HTML, WYSIWIGs, etc.
Generally speaking, the only downside of this method, since it deals with the innerHTML, is that all attached events and properties are lost when the replacement is performed.
You wanted more, we give you More. Today the new MooTools More RC1 is being released, with an outstanding number of new plugins. More functionality, but with the quality you come to expect from the MooTools framework.
Most of the new components come from the excellent Aaron’s Clientcide library. I contributed to the improvement, refining and testing of some of his vast code, which brings More to its present state.
The goal here is to provide more great, simple and extensible tools to make developers’ lives easier. I suggest you head to the Docs or Builder page right away to start trying out the new stuff. As always, head to Lighthouse to report the bugs you encounter, or even to suggest new additions or features.
Given the Object-Oriented nature of the MooTools framework, code repetition is something that is long forgotten (or should be) in the scripts your write. With the avoidance of code repetition comes code reusability, which results in your website being easier to read, extend and maintain, and your scripts smaller in size.
At this point there’s no doubt in anyone’s mind that DRY is a principle we should stick to. However, let’s examine how to achieve this in the right way.
These two widely used scripts have been updated. BarackSlideshow now supports transition effects and can autoplay (requested by the community many times).
MorphList is now even more flexible, supporting custom markup for the dynamic background.
