Dress to Impress, a big fancy Neopets customization tool!
Find a file
Matchu 42827362b6 optimize outfit image generation - 4x speed boost on my box
Use the ImageMagick flatten command to generate the output all at
once instead of compositing each layer individually, and download
the layers in parallel. On my box, saving roopal27 five times took
a total of 30 seconds before, whereas now it takes 7 seconds. I
expect it to be even better on the production box, where latency
is even lower.
2012-07-27 23:07:20 -04:00
app optimize outfit image generation - 4x speed boost on my box 2012-07-27 23:07:20 -04:00
autotest rspec:install 2010-05-14 18:17:10 -04:00
config basic image thumbnails 2012-07-16 16:47:28 -04:00
db Sharing now fully supports saved outfits, not just shared ones 2012-07-26 23:47:22 -04:00
doc rails 3 2010-05-14 18:12:31 -04:00
lib rake task to update spotlight pets 2011-12-20 21:00:02 -05:00
public set sidebar height properly on non-fullscreen mode 2012-07-27 03:31:30 -04: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 optimize outfit image generation - 4x speed boost on my box 2012-07-27 23:07:20 -04: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 optimize outfit image generation - 4x speed boost on my box 2012-07-27 23:07:20 -04:00
Gemfile.lock optimize outfit image generation - 4x speed boost on my box 2012-07-27 23:07:20 -04:00
LICENSE copy LICENSE from impress repo 2010-07-07 02:34:17 -04:00
Rakefile use resque-retry to reschedule failed jobs 2011-06-21 11:22:45 -04:00
README replace standard rails readme :P 2010-07-07 02:31:47 -04:00

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.