OpenNeo/impress
OpenNeo/impress
1
0
Fork 1
Code Pull requests Activity
Dress to Impress, a big fancy Neopets customization tool!
253 commits 4 branches 0 tags 235 MiB
Ruby 43.1%
JavaScript 40.4%
Haml 7.8%
Sass 6.2%
HTML 1.9%
Other 0.5%
Find a file
Matchu 183430adb6 remove non-alphanumeric chars from item pretty urls 
mainly because they were causing the router to freak out when they
contained periods, because that looks like a format, e.g. show.html
2011-05-20 19:50:06 -04:00
app remove non-alphanumeric chars from item pretty urls 2011-05-20 19:50:06 -04:00
autotest rspec:install 2010-05-14 18:17:10 -04:00
config remove deprecated hoptoad js_notifier option 2011-05-13 08:27:57 -04:00
db allow guests to share outfits 2011-02-10 17:50:47 -05:00
doc rails 3 2010-05-14 18:12:31 -04:00
lib handle timeout errors for pet data, swfs, pet images 2011-02-19 22:49:13 -05:00
public remove non-alphanumeric chars from item pretty urls 2011-05-20 19:50:06 -04: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 add production mysql2 dependency 2011-02-09 18:28:50 -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 add production mysql2 dependency 2011-02-09 18:28:50 -05:00
Gemfile.lock add production mysql2 dependency 2011-02-09 18:28:50 -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.