Anyway as a way of getting to know Mootools, I decided to rewrite it to take advantage of the framework. I took the opportunity to clean up the code a bit and make it easier to style the output.

You can find a zip file for MooTools version 1.2 here (included is another zip file with the old, MooTools v1.1 compatible code) with the full annotated source code, also a compressed version (it weighs in at just 2.5K), some simple CSS, an example HTML file and a readme (which is basically identical to the extended comments at the top of the source code).

Demo: http://the-stickman.com/files/mootools/multiupload/

Download: http://the-stickman.com/files/mootools/multiupload/Stickman.MultiUpload.zip

Source: http://the-stickman.com/web-development/javascript/multiple-file-uploader-mootools-version/

Related Listings:

1. uploadify – A file upload plugin using jQuery This plugin allows you to change any element with an...
2. TimeSpinner : Moo Tools Welcome to this temporary/permanent page. Temporary because is really ugly,...
3. Featured articles plugin for Wordpress with Moo Tools Featured articles gives the wordpress blog admin the possibility to...

This pattern splits the view (also called the presentation) into “dumb” templates
that are primarily responsible for inserting pre-built data in between HTML tags.
The model contains the “smart” domain objects (such as Account, Product, Person,
Post) that holds all the business logic and knows how to persist themselves to
a database. The controller handles the incoming requests (such as Save New Account,
Update Product, Show Post) by manipulating the model and directing data to the view.

In Rails, the model is handled by what’s called an object-relational mapping
layer entitled Active Record. This layer allows you to present the data from
database rows as objects and embellish these data objects with business logic
methods. You can read more about Active Record in
link:files/vendor/rails/activerecord/README.html.

The controller and view are handled by the Action Pack, which handles both
layers by its two parts: Action View and Action Controller. These two layers
are bundled in a single package due to their heavy interdependence. This is
unlike the relationship between the Active Record and Action Pack that is much
more separate. Each of these packages can be used independently outside of
Rails. You can read more about Action Pack in
link:files/vendor/rails/actionpack/README.html.

== Getting Started

1. At the command prompt, start a new Rails application using the rails command
and your application name. Ex: rails myapp
2. Change directory into myapp and start the web server: script/server (run with –help for options)
3. Go to http://localhost:3000/ and get “Welcome aboard: You’re riding the Rails!”
4. Follow the guidelines to start developing your application

== Web Servers

By default, Rails will try to use Mongrel and lighttpd if they are installed, otherwise
Rails will use WEBrick, the webserver that ships with Ruby. When you run script/server,
Rails will check if Mongrel exists, then lighttpd and finally fall back to WEBrick. This ensures
that you can always get up and running quickly.

Mongrel is a Ruby-based webserver with a C component (which requires compilation) that is
suitable for development and deployment of Rails applications. If you have Ruby Gems installed,
getting up and running with mongrel is as easy as: gem install mongrel.
More info at: http://mongrel.rubyforge.org

If Mongrel is not installed, Rails will look for lighttpd. It’s considerably faster than
Mongrel and WEBrick and also suited for production use, but requires additional
installation and currently only works well on OS X/Unix (Windows users are encouraged
to start with Mongrel). We recommend version 1.4.11 and higher. You can download it from

http://www.lighttpd.net.

And finally, if neither Mongrel or lighttpd are installed, Rails will use the built-in Ruby
web server, WEBrick. WEBrick is a small Ruby web server suitable for development, but not
for production.

But of course its also possible to run Rails on any platform that supports FCGI.
Apache, LiteSpeed, IIS are just a few. For more information on FCGI,
please visit: http://wiki.rubyonrails.com/rails/pages/FastCGI

== Debugger

Debugger support is available through the debugger command when you start your Mongrel or
Webrick server with –debugger. This means that you can break out of execution at any point
in the code, investigate and change the model, AND then resume execution!
You need to install ruby-debug to run the server in debugging mode. With gems, use ‘gem install ruby-debug’
Example:

  class WeblogController < ActionController::Base
    def index
      @posts = Post.find(:all)
      debugger
    end
  end

So the controller will accept the action, run the first line, then present you
with a IRB prompt in the server window. Here you can do things like:

[/code]

  >> @posts.inspect
  => "[#<post :0x14a6be8 @attributes={\"title\"=>nil, \"body\"=>nil, \"id\"=>\"1\"}>,
       #</post><post :0x14a6620 @attributes={\"title\"=>\"Rails you know!\", \"body\"=>\"Only ten..\", \"id\"=>\"2\"}>]"
  >> @posts.first.title = "hello from a debugger"
  => "hello from a debugger"
</post>

...and even better is that you can examine how your runtime objects actually work:

  >> f = @posts.first
  => #<post :0x13630c4 @attributes={"title"=>nil, "body"=>nil, "id"=>"1"}>
  >> f.</post>

Display all 152 possibilities? (y or n)

Finally, when you're ready to resume execution, you enter "cont"

Demo: http://github.com/syntacticx/sauce/zipball/master

Download: http://download.github.com/syntacticx-sauce-9ea3843e17a336f508816e88f12826b4fc5b7761.zip

Source: http://github.com/syntacticx/sauce/zipball/master

Related Listings:

1. Pikachoose – lightweight Jquery Image Gallery plugin Pikachoose is a lightweight Jquery plugin that allows easy presentation...
2. Dynamic Image Gallery with Slideshow This extremely lightweight JavaScript image gallery and slideshow script clocks...