Sha256: 6b728a31e2d67314a42f0001a1d1c8efa540e60966f554e0b1bed0c77e1ea819

Contents?: true

Size: 1.08 KB

Versions: 5

Compression:

Stored size: 1.08 KB

Contents

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

- rango & merb apps: both with same functionality include specs

- 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

=== Version 0.2 ===

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

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

Version data entries

5 entries across 5 versions & 1 rubygems

Version Path
pupu-0.0.3 TODO.txt
pupu-0.0.3.pre TODO.txt
pupu-0.0.2.pre TODO.txt
pupu-0.0.2 TODO.txt
pupu-0.1.pre TODO.txt