☰

Scrying Workshop Reworked

UX Improvements for Flight Rising's Scrying Workshop and Search

Tác giả
UXRising
Cài đặt hàng ngày
0
Số lần cài đặt
491
Đánh giá
3 0 0
Phiên bản
1.16
Đã tạo
14-04-2014
Đã cập nhật
18-11-2015
Giấy phép
N/A
Áp dụng cho

Dragon pages:
* Adds 'Scry' button to open Morphology page with that dragon loaded.

Bloodlines page:
* Adds images of the dragons being checked.
* Replaces dialog pop-up with text beneath button and large, clear icon between dragons (green check for yes, red X for no).
* Adds button to go directly to the progeny page with those two dragons, whether they can actually breed or not (you might just want to see 'what if').

Progeny page:
* Adds images of the dragons being checked.
* Adds button to check the bloodlines of dragons being checked.
* Adds small popup on hover to tell you what that potential offspring's details are.
* If you click a possible offspring, takes you to the morphology page to show you that potential as an adult.

Morphology page:
* Switches dropdowns into Color - Gene order, like everything else on the site.
* Makes image generation automatic when all dropdowns have been selected.
* Removes 'Predict' button.
* Adds 'Reset' button.
* Adds 'Random' button.
* Adds 'Search?' button which opens the search page and runs a search to see if a dragon with those attributes already exists.

Search page:
* Adds 'Reset' button.
* Shows search results on same page, beneath the buttons.
* Adds arrows to page through said results at top and bottom.
* Displays information about and larger image of found dragon on hover.
* Clicking a dragon opens that dragon's page in a new tab.
* Adds checkbox to show/hide exalted results in search -- doesn't remove them, but does let you choose whether they're visible.

I know everyone wants an indicator in search of whether a dragon is for sale, but unfortunately I haven't yet thought of a way to get that information without either being able to check the database directly, which I can't, or checking every dragon's page individually, which would be an unreasonable load on the server. If I think of a reasonable way to do it, I will.