dice/impress
1
0
Fork 0
forked from OpenNeo/impress
Code Pull requests Activity
Dress to Impress, a big fancy Neopets customization tool!
160 commits 4 branches 0 tags 248 MiB
JavaScript 45.8%
Ruby 38.2%
Haml 7.6%
Sass 6.1%
HTML 1.9%
Other 0.3%
Find a file
Matchu 8e6a34b69c fix contributions for pet states and items 
dependent contributables would only count as contributed if their parent
was being contributed for the first time, too. the trick was to delay
actually *assigning* them to their parents until the very, very end
2010-11-15 17:56:16 -05:00
app fix contributions for pet states and items 2010-11-15 17:56:16 -05:00
autotest rspec:install 2010-05-14 18:17:10 -04:00
config handle contribution for now-unused swf 2010-11-15 16:44:57 -05:00
db lovely interface for saving outfits. still no reading them yet 2010-11-10 16:59:54 -05:00
doc rails 3 2010-05-14 18:12:31 -04:00
lib remember me on login 2010-11-13 19:42:56 -05:00
public use compass image helpers for cachebuster strings 2010-11-14 20:18:38 -05:00
script rails 3 2010-05-14 18:12:31 -04:00
spec lovely interface for saving outfits. still no reading them yet 2010-11-10 16:59:54 -05:00
test core of pet loading, still needs get image hash, download assets 2010-10-07 10:46:23 -04:00
tmp prepare for deploy 2010-06-30 05:35:50 -04:00
vendor include hoptoad 2010-11-14 16:06:31 -05:00
.gitignore ignore cap files, move auth config to yaml file 2010-11-13 10:37:57 -05:00
config.ru move async behavior to development_async environment 2010-10-11 18:28:39 -04:00
Gemfile include hoptoad 2010-11-14 16:06:31 -05:00
Gemfile.lock include hoptoad 2010-11-14 16:06:31 -05:00
LICENSE copy LICENSE from impress repo 2010-07-07 02:34:17 -04:00
Rakefile upgrade to rails 3, make item tests pass 2010-10-03 19:50:32 -04:00
README replace standard rails readme :P 2010-07-07 02:31:47 -04:00

README 

An extension of Dress to Impress (PHP) that runs on Ruby on Rails.
I wanted to use Rails initially for Impress, but hoped that using
PHP would allow me to attract more developers. Looks like that
wasn't the case, so I just went with what I loved and made the
items database in Rails.

Future Impress sections will likely find themselves in this
project, rather than the PHP project.