dice/impress
1
0
Fork 0
forked from OpenNeo/impress
Code Pull requests Activity
Dress to Impress, a big fancy Neopets customization tool!
178 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 6b5b978cb1 different ajax loader for current outfit, quick bug fix
2010-11-24 21:10:29 -05:00
app different ajax loader for current outfit, quick bug fix 2010-11-24 21:10:29 -05:00
autotest rspec:install 2010-05-14 18:17:10 -04:00
config remove old routes to not throw off will_paginate 2010-11-17 00:19:02 -05:00
db add join index on swf_assets.type, swf_assets.id 2010-11-20 10:35:34 -05:00
doc rails 3 2010-05-14 18:12:31 -04:00
lib rake task to, hopefully, repair duplicate pet state ids cleanly 2010-11-15 21:15:33 -05:00
public different ajax loader for current outfit, quick bug fix 2010-11-24 21:10:29 -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 rails 3.0.3, negating arel condition is not(c) instead of c.not now 2010-11-16 17:26:06 -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 rails 3.0.3, negating arel condition is not(c) instead of c.not now 2010-11-16 17:26:06 -05:00
Gemfile.lock rails 3.0.3, negating arel condition is not(c) instead of c.not now 2010-11-16 17:26:06 -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.