Contents

Examples:
- recreate the rango app AFTER I release Rango 0.3 & bundle it
- ensure all the examples has the same functionality include specs
- ensure all the examples work

=== Version 0.1 ===
- Pupu.framework_root: "."
- Pupu.media_root: "media"
- Pupu.root: "media/pupu"
- @pupu.root: "media/pupu/mootools"

- THERE SHOULD BE A CONVETION TO NAME PUPU WITH PUPU-FRAMEWORK-PLUGIN, FOR EXAMPLE PUPU-MOOTOOLS-FLASH because of search
- install each dependency just once
- how to handle metadata if we have it as submodules? (suggestions: media/pupu/metadata.yml for all) or on the fly from .git/config & config.rb etc
- pupu has a license, but the stuff we want to put into pupu probably has also a license (MooTools is under MIT etc)
- media support (.swf): media helper
- media vs. root vs. custom
- how to handle metadata? Generate metadata.yml from config.rb (dependencies) or generate it through merb-gen and write it by hand?
- what about ruby helpers such as flash :notice, :error for flash <divs>
- add array with loaded plugins, do not load plugin which is already loaded
- hooks for minify etc
- don't touch file system in production mode (don't use File.exist?) -> just load manifest

=== Version 0.2 ===

=== Version 0.3 ===
- bin/pupu

=== Version 0.4 ===
- 100% specs coverage & refactoring
- YARD Code Documentation

Version data entries

10 entries across 10 versions & 1 rubygems

Version	Path
pupu-0.2.1	TODO.txt
pupu-0.2	TODO.txt
pupu-0.1	TODO.txt
pupu-0.0.5.5	TODO.txt
pupu-0.0.5.4	TODO.txt
pupu-0.0.5.3	TODO.txt
pupu-0.0.5.2	TODO.txt
pupu-0.0.5.1	TODO.txt
pupu-0.0.5	TODO.txt
pupu-0.0.4.pre	TODO.txt