OpenNeo/impress
OpenNeo/impress
1
0
Fork 1
Code Pull requests Activity
Dress to Impress, a big fancy Neopets customization tool!
204 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 1e8ec13bfe move to unstable rocketamf so that it builds hashes from registries, not arrays
2011-01-13 17:22:07 -05:00
app move to unstable rocketamf so that it builds hashes from registries, not arrays 2011-01-13 17:22:07 -05:00
autotest rspec:install 2010-05-14 18:17:10 -04:00
config home page caching, reset top contributors only when necessary 2010-12-11 09:37:39 -05:00
db asset spider, yaaay 2010-11-27 18:41:06 -05:00
doc rails 3 2010-05-14 18:12:31 -04:00
lib prep for newid server 2011-01-10 17:52:26 -05:00
public cache item_zone_sets.json too 2010-12-11 10:36:59 -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 move to unstable rocketamf so that it builds hashes from registries, not arrays 2011-01-13 17:22:07 -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 move to unstable rocketamf so that it builds hashes from registries, not arrays 2011-01-13 17:22:07 -05:00
Gemfile.lock move to unstable rocketamf so that it builds hashes from registries, not arrays 2011-01-13 17:22:07 -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.