This repository is private.
All pages are served over SSL and all pushing and pulling is done over SSH.
No one may fork, clone, or view it unless they are added as a member.
Every repository with this icon (
) is private.
Every repository with this icon (
This repository is public.
Anyone may fork, clone, or view it.
Every repository with this icon (
) is public.
Every repository with this icon (
No gems have been built for this project yet.
commit 6db3ffe21b792fccd70f02ff1a1d881dc0d6de9a
tree 1fdead5a134f526b9b5c8d3c4c78a8ff41856e2d
parent 8d432c6e847db710b2774f2837e56cd2cb7cada3
tree 1fdead5a134f526b9b5c8d3c4c78a8ff41856e2d
parent 8d432c6e847db710b2774f2837e56cd2cb7cada3
- README
- README.textile
- Rakefile
- dm-observer/LICENSE
- dm-observer/README
- dm-observer/Rakefile
- dm-observer/TODO
- dm-observer/lib/dm-observer.rb
- dm-observer/spec/integration/dm-observer_spec.rb
- dm-observer/spec/spec.opts
- dm-observer/spec/spec_helper.rb
- dm-voyeur/LICENSE
- dm-voyeur/README
- dm-voyeur/Rakefile
- dm-voyeur/TODO
- dm-voyeur/lib/dm-voyeur.rb
- dm-voyeur/spec/integration/dm-voyeur_spec.rb
- dm-voyeur/spec/spec.opts
- dm-voyeur/spec/spec_helper.rb
... |
... |
|





Comments
In my local repo, git did a better job of showing the file renames. Sorry that they don’t appear very well here.
What’s the reasoning behind changing the name? There’s another dm-observers gem out there which does actually follow the Observers pattern. DM-Voyeurs uses the Hook architecture to inject callbacks. It’s not an Observer in the strictest sense.
I’m open to another name, provided that it reflects well on the DM community. I thought using “voyeur” was not the best choice.