OpenNeo/impress
OpenNeo/impress
1
0
Fork 1
Code Pull requests Activity
Dress to Impress, a big fancy Neopets customization tool!
524 commits 2 branches 0 tags 230 MiB
JavaScript 43.1%
Ruby 40.3%
Haml 8%
Sass 6.3%
HTML 1.9%
Other 0.3%
Find a file
Matchu 1571a10500 shoot, included in the wrong spot. this is rspec issue hard to test :(
2013-01-02 23:58:25 -05:00
app wardrobe now considers item.species_support_ids when deciding compatibility 2013-01-02 23:15:32 -05:00
autotest rspec:install 2010-05-14 18:17:10 -04:00
config wardrobe now considers item.species_support_ids when deciding compatibility 2013-01-02 23:15:32 -05:00
db finally fix encased in ice - woo! 2012-10-05 20:56:52 -05:00
doc rails 3 2010-05-14 18:12:31 -04:00
lib shoot, included in the wrong spot. this is rspec issue hard to test :( 2013-01-02 23:58:25 -05:00
public wardrobe now considers item.species_support_ids when deciding compatibility 2013-01-02 23:15:32 -05:00
script rails 3 2010-05-14 18:12:31 -04:00
spec report broken images 2011-08-07 18:23:44 -04:00
test core of pet loading, still needs get image hash, download assets 2010-10-07 10:46:23 -04:00
tmp utf-8 support in both ruby 1.9 and 1.8 2011-06-04 18:40:15 -04:00
vendor upgrade to rails 3.0.18 - only patch upgrades, no API changes 2013-01-02 22:44:24 -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 upgrade to rails 3.0.18 - only patch upgrades, no API changes 2013-01-02 22:44:24 -05:00
Gemfile.lock upgrade to rails 3.0.18 - only patch upgrades, no API changes 2013-01-02 22:44:24 -05:00
LICENSE copy LICENSE from impress repo 2010-07-07 02:34:17 -04:00
Rakefile update Rakefile and tasks to match new version of rake 2013-01-02 23:40:37 -05: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.