floof: usable, kinda
After some mad hacking over the weekend and a couple afternoons, I think floof is actually sorta reliable enough to be using. Look, there's even some sample art: http://floof.veekun.com/users/purplekecleon
AND LOOK COMMISSION SUPPORT, I guess http://floof.veekun.com/users/eevee
Specifically changed:
- Use of OpenID is explained a little more better, and OpenID errors are caught instead of just crashing spectacularly.
- Thumbnails. There weren't any before. This was a problem!
- Workflow is less.. garbage.
- Art page has less clutter on it.
- I discovered text-shadow and may have gone a little overboard.
Seeing a bright orange default error 500 page, by the way, means I just got an email with gratuitous detail about why it crashed.
I have this whole giant stupid massive list of todo items argh. User demands take priority, though.
I suppose one of the first things I ought to do is move this off of sqlite and onto a Real Database™.
AND LOOK COMMISSION SUPPORT, I guess http://floof.veekun.com/users/eevee
Specifically changed:
- Use of OpenID is explained a little more better, and OpenID errors are caught instead of just crashing spectacularly.
- Thumbnails. There weren't any before. This was a problem!
- Workflow is less.. garbage.
- Art page has less clutter on it.
- I discovered text-shadow and may have gone a little overboard.
Seeing a bright orange default error 500 page, by the way, means I just got an email with gratuitous detail about why it crashed.
I have this whole giant stupid massive list of todo items argh. User demands take priority, though.
I suppose one of the first things I ought to do is move this off of sqlite and onto a Real Database™.