The sounds of a beautiful woman walking towards me

Many people are around but no one else is there

Her lovely eyes, her beautiful smile, the enchanting smell of her hair

I smile to draw attention, a smile I get in return

As she nears anticipation grows, my heart starts to yearn

I wonder what her thoughts are as I prepare my words

I am deeply enthralled in another world filled with flowers and birds

My fantasies are aroused but reality does not comply

For returning from this dreaming state finds her only passing by

I continue eating; focused, I am focused.

by Kevin A.

when I close my eyes?

when I embrace the nocturnal likeness of myself,

this thing called night,

I dream

when I am amidst the atmosphere which makes all things visible,

I think it is called the light of day,

I dream

when I break from continuously adding to the great lore of my mind,

. . . infinity,

. . . education,

I dream

when I am drowned in the sounds of that which makes my heart

pause from its rhythmic flow,

the music of life and love,

I dream

when I can find no activity which will accept

my willingness to participate,

I dream

I dream about how wonderful it is to be loved by you.

by Kevin Andre Armstrong

DirtyForm Class

The class is located on here on github.

Examples

All form fields in a single form with two fields excluded.

It is now possible and recommended to generate MooTools (and its plugins) yourself using MooTools Packager or MooTools Depender. These libraries combine multiple javascript files into one for single file deployment. Once you understand the convention these libraries use, building a single production file is a breeze. This article focuses on setting up your javascript files for use primarily with Packager. Once created though, the files can be used with Packager or Depender.

Packager

Structure

Start by creating a folder for your project. Inside that folder you should have a Source folder and the file package.yml.
- PeopleProject/
    - package.yml
    - Source/
        - Employee.js
        - Person.js

Package.yml
Below is a sample package.yml file.

name: People
sources:
- "Source/Person.js"
- "Source/Employee.js"

• The name property specifies the name of your project. It is the name that will be registered with the project manifest.
• The sources property specifies the location of your javascript source files.

Source Files
Source files consists of whatever javascript code you choose. The header of these javascript files is what is important. The header syntax should be in YAML as follows:

/*
---
name: Person
requires:
- Core/Class
provides: Person
...
*/

The --- and ... are very important. They are required by YAML and specify the start and end of a YAML block.

• The name property specifies the name of the source file and is used by Packager to reference the source file.
• The requires property specifies the dependencies of the source file. This can be written using a YAML collection block sequence with each entry on its own line and preceded by a dash and a space or by using a flow sequence with entry separated by a comma within square brackets [].
• The provides property specifies the code that is provided by the source file. A source file can provide several blocks of code. When any one of those blocks is required by another source file, the entire file is included.

As with the manifest file, this YAML block can contain other useful properties such as author, description, license, etc.

Command line usage

With the manifest and the source files properly configured, using Packager from the command line is simple.

First you must register the manifest by issuing the register command:

./packager register <path-to-manifest>

After the manifest has been registered, you can issue several build commands depending on your needs.

./packager build +components People/Person People/Employee

Which builds the passed in components (and their dependancies) using your registered packages. You can get the same results with the command:

./packager build People/Person People/Employee

You can build every component from your project with the command:

./packager build People/*

To write the results of the commands to a file, use the following:

./packager build People/* > people.js

More commands and explanations can be found on the packager project page.

The XML that I had to parse required querying for node with text of a certain value. The native :contains pseudo shipped with dojo didn’t work because it uses the innerHTML property which isn’t available for XML nodes. I could have rewritten that pseudo but that would potentially break other code. I decided to create my own pseudo with the logic used in jQuery’s :contains pseudo:

1
2
3
4
5
6
7
8
9

dojo.query.pseudos.text = function(name, condition){
    var cz = condition.charAt(0);
    if( cz == '"' || cz == "'" ){ //remove quote
        condition = condition.slice(1, -1);
    }
    return function(elem){
        return ((elem.textContent || elem.innerText || "").indexOf(condition) >= 0);
    }
};

Using the following XML:

<?xml version="1.0"?>
<catalog>
    <book id="bk101">
        <author>Grisham, John</author>
        <title>The Confession: A Novel</title>
    </book>
    <book id="bk102">
        <author>Morrison, Matthew</author>
        <title>One Day More</title>
    </book>
    <book id="bk103">
        <author>Grisham, John</author>
        <title>The Partner</title>
    </book>
    <book id="bk104">
        <author>Grisham, John</author>
        <title>Theodore Boone: Kid Lawyer</title>
    </book>
    <book id="bk105">
        <author>Morrison, Matthew</author>
        <title>It Takes Two</title>
    </book>
</catalog>

I could find all books by John Grisham using the following:

1
2
3

dojo.query('book', xml).filter(function(book){
    return dojo.query('author:text(Grisham, John)', book).length > 0;
});