OpenNeo/impress
OpenNeo/impress
1
0
Fork 1
Code Pull requests Activity
Dress to Impress, a big fancy Neopets customization tool!
814 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 e62d52bbd4 use body zone (15) instead of static so that most items look good
2014-03-27 22:28:48 -05:00
.sass-cache phew. rails 3.2.12, including some asset pipeline. still buggy. 2013-03-05 20:08:57 -06:00
app create colors from rake 2014-03-27 22:28:48 -05:00
autotest rspec:install 2010-05-14 18:17:10 -04:00
config ugh, add react.js manually :( 2014-01-20 14:35:28 -06:00
db prank color migration 2014-03-27 22:28:48 -05:00
doc rails 3 2010-05-14 18:12:31 -04:00
lib use body zone (15) instead of static so that most items look good 2014-03-27 22:28:48 -05:00
public monocle favicon 2013-12-26 12:44:03 -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 basic modeling buttons 2014-01-10 16:25:03 -05:00
.gitignore ignore cap files, move auth config to yaml file 2010-11-13 10:37:57 -05:00
bundle rails 3.1 upgrade - still buggy 2013-03-05 15:10:25 -06:00
config.ru move async behavior to development_async environment 2010-10-11 18:28:39 -04:00
Gemfile basic modeling buttons 2014-01-10 16:25:03 -05:00
Gemfile.lock basic modeling buttons 2014-01-10 16:25:03 -05:00
isntall rails 3.1 upgrade - still buggy 2013-03-05 15:10:25 -06: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.