1
0
Fork 0
forked from OpenNeo/impress
Dress to Impress, a big fancy Neopets customization tool!
Find a file
Matchu 4dd2bc9549 fix some outfits list bugs
I think I got the 0-width bug where the outfit never expands beyond
0px width, and there were also some issues with the fact that
image subscriptions pointed to the current outfit object, even
after that object had changed identity, so now we re-fetch from
the cache by ID.
2012-07-31 11:14:32 -04:00
app new outfit image filename: preview instead of thumb, one more partition level 2012-07-31 10:41:13 -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 retroactively enqueue outfit images 2012-07-31 10:20:37 -04:00
public fix some outfits list bugs 2012-07-31 11:14:32 -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.