MooTools

Twice a mon­th, we re­vis­it some of our read­ers’ fa­vorite posts from through­out the his­to­ry of Nettuts+. Implementing AJAX tech­nol­o­gy can be a hit or miss thing. Do it well and you’ll have users rav­ing over the slick­ness it pro­vides to the gen­er­al user ex­pe­ri­ence, while, if you mess it up, you’ll be at the re­ceiv­ing end of their wrath. Here are 24 tips to guide through the pro­cess of im­ple­ment­ing AJAX tech­nol­o­gy with­in your web ap­pli­ca­tion. 1. Understand What it All Means First up, you (...)

Mooplay is a set of con­trols, built on top of MooTools, that en­ables us to cre­ate and cus­tomize a HTML5 video play­er. It doesn't force you to use the video ele­ment with on­ly its con­trols. They can be con­trolled by other scripts and Mooplay will adapt it­self ac­cord­ing­ly. The con­trols in­clude: play/pause rewind/for­ward in­ter­ac­tive play pro­gress slid­er load pro­gress bar vol­ume slid­er and mute but­ton full-page dis­play cur­rrent and re­main­ing time. Another great fea­ture is the abil­i­ty (...)

The youth is pow­er­ing our dig­i­tal age and they will con­trol the fu­ture of our web. The po­si­tion of free­lance web­site de­sign­er seems lu­cra­tive and very en­tic­ing from the get-go. Set your own hours, work on what­ev­er you want, get paid to work from home and learn as you go. What could be bet­ter? Problems be­gin to arise when free­lancers si­t­u­ate them­selves in all mar­kets and spread their tech­niques too thin. There is a sub­set of jobs in dig­i­tal de­sign and de­vel­op­ment which free­lancers should (...)

The com­mu­ni­ty and the MooTools users are very im­por­tant for MooTools and its de­vel­op­ment. Therefore we would love to hear who you are and how you are us­ing MooTools. You could do this by this sur­vey. It will take about five min­utes and none of the ques­tions are re­quired. The pur­pose of this sur­vey is to help us pri­or­i­tize what the de­vel­op­ment team spends its time on. We want to make MooTools as use­ful for you as we can. Some ques­tions are more ex­plic­it than others, re­lat­ing to where we put (...)

When re­leas­ing a web pro­duct, there is noth­ing more ben­e­fi­cial than re­ceiv­ing ear­ly feed­back from your users. Unfortunately, many web­sites make it un­nec­es­sar­i­ly dif­fi­cult to send your feed­back or lack this func­tion­al­i­ty al­to­geth­er Tutorialzine taught us how to solve this prob­lem with a Quick Feedback Form. Powered by jQuery, PHP and the PHPMailer class, the form sends the users’ sug­ges­tions di­rect­ly to your mail­box. Requirements: jQuery Framework Demo: (...)

In this post, I have col­lect­ed 26 use­ful jQuery nav­i­ga­tion menu tu­to­ri­als. Enjoy! Mega Drop Down Menus w/ CSS & jQuery Animated Navigation with CSS & jQuery Create Simple Dropdown Menu Using jQuery Collapsing Site Navigation with jQuery Use Sprites to Create an Awesomeness-Filled Navigation Menu Thumbnails Navigation Gallery with jQuery Sexy Drop Down Menu w/ jQuery & CSS How to Create a Drop-down Nav Menu with HTML5, CSS3 and jQuery Slide Down Box Menu (...)

Content Security Policy is a way for site own­ers to de­fine how con­tent in their web site or web ap­pli­ca­tion is meant to be­have, and have this en­forced by the web browser. Content Security Policy is not a mag­i­cal so­lu­tion to ev­ery se­cu­ri­ty is­sue, but it ad­dress­es one aspect in par­tic­u­lar. The pri­ma­ry goal of Content Security Policy is to mit­i­gate Cross Site Scripting (XSS) by pro­vid­ing a way for site own­ers to spec­i­fy which do­mains the browser should treat as valid sources of script. (...)

Every web de­vel­op­er should have in their tool­box a col­lec­tion of CSS tools and re­sources like the ones out­lined in this ar­ti­cle. A set of tech­niques that you re­ly on and that are al­ways at the ready to cov­er any pos­si­ble even­tu­al­i­ty. You will find not a se­lec­tion of the lat­est in­no­va­tive CSS tech­niques (there are some) in this ar­ti­cle, mere­ly a col­lec­tion of tools, re­sources and down­loads that can be used by web de­sign­ers for so­lu­tions to ev­ery­day CSS de­sign and cod­ing so­lu­tions. The (...)

Today, JavaScript take a lead­ing place when it comes to client side pro­gram­ming and is used by pro­fes­sion­als and web de­vel­op­ers all over the world. JavaScript is a pow­er­ful lan­guage with many ad­vanced fea­tures and frame­works like jQuery, YUI, SproutCore and Cappuccino. But it has cer­tain dis­ad­van­tages that JavaScript is not the same in all browsers and it lim­its and ac­ces­si­bil­i­ty of a web­site. But the­se fac­tors should not lim­it the ca­pa­bil­i­ties of this won­der­ful lan­guage. Working with (...)

We here­by an­nounce the im­me­di­ate avail­abil­i­ty of MooTools More 1.3.0.1. We have up­dat­ed all of MooTools More’s code to work with the re­cent­ly re­leased Core 1.3 with­out 1.2 com­pat­i­bil­i­ty. Besides the API up­date, 1.3 im­proves sta­bil­i­ty and in­tro­duces some awe­some new fea­tures. Awesome new fea­tures? What awe­some new fea­tures? Events.Pseudos, wait, this isn’t hap­pen­ing! MooTools Core 1.3 in­cludes our new se­lec­tor engine Slick. One of Slick’s com­po­nents is Slick.Parser. Slick.Parser pars­es a (...)

I've cre­at­ed HeatMap: a MooTools class that al­lows you to de­tect, load, save, and dis­play spots on a given area where a user has clicked.

After al­most a year in de­vel­op­ment, the MooTools team an­nounced the re­lease of ver­sion 1.3 with ma­jor no­table en­hance­ments. Slick Selector Engine The biggest up­date is the in­clu­sion of the new Slick stan­dalone se­lec­tor engine. The engine was de­vel­oped by Thomas Aylott, Fabio Costa and Valerio Proietti with ac­cu­ra­cy and porta­bil­i­ty in mind, al­low­ing the engine to not on­ly provide MooTools de­vel­op­ers with ex­cel­lent se­lec­tor sup­port but al­so the abil­i­ty for it to be in­clud­ed in other pro­jects (...)

Pretty am­bigu­ous ti­tle isn’t it? That’s en­tire­ly in­ten­tion­al, be­cause the topic of this par­tic­u­lar ar­ti­cle is some­thing that a lot of web de­sign­ers seem to hate talk­ing about. But, now that I’ve got you here hope­ful­ly you’ll stick around, so I’ll let the cat out of the bag (so to speak). In this ar­ti­cle we’re go­ing to be talk­ing about Web 2.0. Wait! Don’t run away! This isn’t the sort of ar­ti­cle that’s go­ing to round up eight bazil­lion awe­some ex­am­ples of Web 2.0 de­signs, or a tu­to­ri­al that’s go­ing (...)

Good news, ev­ery­one! We are ex­treme­ly hap­py to an­nounce the of­fi­cial re­lease of MooTools Core 1.3 after al­most a year of de­vel­op­ment. You might call us per­fec­tion­ists, but we’re now ready to call the 1.3 re­lease com­plete and stable. For those of you who have been wait­ing to make the switch, now would be the per­fect time. In ad­di­tion, MooTools Core 1.3 is ful­ly back­wards com­pat­i­ble with all doc­u­ment­ed func­tion­al­i­ty of MooTools Core 1.2, but more on that later. MooTools Core 1.3 brings the (...)

MooTools has al­ways prid­ed it­self with the qual­i­ty of its de­vel­op­er com­mu­ni­ty, and the MooTools de­vel­op­ment team has al­ways high­ly val­ued the opin­ion and in­put of the thou­sands of users who con­tin­u­al­ly sup­port the frame­work. With this in mind, we’ve de­cid­ed to provide ev­ery­one with a quick up­date on the re­cent work that the More team has been do­ing. Specifically, the meta things about More; the things we do to make work­ing on MooTools More bet­ter and bet­ter. MooTools More Team Has Grown and (...)

Today we’re re­leas­ing MooTools Core 1.2.5, which can be con­sid­ered the last ver­sion of the 1.2 series. 1.2.5 is a main­te­nance re­lease, and con­tains fix­es for the lat­est be­ta browsers, such as Firefox 4 be­ta, Chrome 6 and IE9 be­ta. Below, a quick changel­og: Fix for fireEvent un­der IE9 be­ta. Forcing MooTools bind im­ple­men­ta­tion to work with the lat­est gecko / we­bkit be­ta browsers. Fixes HTML Elements cre­ation in IE9 be­ta. Fixed Elements garbage col­lec­tion in IE. Or, if you prefer, you can (...)

We are cur­rent­ly seek­ing a mo­ti­vat­ed, hands-on web de­vel­op­er to join our team. Developers are in­volved through­out our pro­cess and are en­cour­aged to work through ideas and so­lu­tions with the en­tire de­sign team. Required ex­pe­ri­ence: 5+ years de­vel­op­ment ex­pe­ri­ence Experience with JavaScript li­braries such as MooTools & jQuery Expert hands-on knowl­edge of HTML, XHTML,CSS, JavaScript, AJAX, XML Experience trans­lat­ing comps and wire­frames in­to flex­i­ble and us­able code tem­plates Excellent (...)

Once you know how much easier it is to get ele­ments all around, you should take the time to learn how MooTools has pro­vid­ed a sim­ple ac­cess API around the browser quirks for Elements. And on top of it, we’ve ex­tend­ed this API to things that you don’t nor­mal­ly find on Elements. And as cool as it is, you can easi­ly add your own bits with ease. Get Who? Set What? On Elements, theres on­ly 3 get­ters/set­ters that you need to wor­ry your­self with: get/set, get­Style/set­Style, and store/re­trieve (...)

Over the past cou­ple of weeks we have got a lot of great re­spons­es over the ini­tial be­ta of MooTools Core 1.3. We have since im­proved both the code and the doc­u­men­ta­tion in order to re­lease a sec­ond be­ta. Most no­tably we have re­moved the de­pen­den­cy on Hash. If you build 1.3 with­out com­pat­i­bil­i­ty you won’t get the Hash ob­ject no more. But fear not, we have added Object.js which brings you all the Hash meth­ods as gener­ics. Everything else is re­al­ly mi­nor, has to do with sta­bil­i­ty or was meant (...)

If you’ve been pay­ing at­ten­tion for the past few years, you’ve prob­a­bly no­ticed the growth of MooTools, both as a pro­ject and as a thriv­ing com­mu­ni­ty. Unfortunately, it has come to light that many so called “mem­bers” of the JavaScript com­mu­ni­ty may, in fact, be au­tomata. To pro­tect our­selves and the MooTools com­mu­ni­ty, we’ve start­ed two phys­i­cal screen­ing pro­grams (or “mee­tups”), one in London and the other in the heart of Silicon Valley. In a sur­pris­ing turn of events, both groups have had (...)