MArcomage

Creating a deck is annoying, because each time you choose a card the page reloads and the scroll bar resets to the start of the list.
It could be fixed by adding checkboxes under each card and confirm when you are ready

This does sound useful indeed.

Or by bringing the site forward a decade and using javascript.

*runs*

moullas is studying computer and electrical engineering. he might be able to help hehe

[Branched off a discussion on the site's program languag]

[Mojko said on topic here:
Suggested functionality can be implemented and I think it's a good idea to have something like "mass take" and "mass remove" button in the deck building section.]
[The rest of his post is moved to start a new topic about the Site Program Language]

I've been working on a new deck building engine by using AJAX. This allows to modify your deck without the need of reloading the whole page. This allows faster manipulation and also doesn't reset the card pool. I have a working prototype, but are some design decisions I want to discuss.

There are two options how to connect the new AJAX functionality to the interface:

1 - the new functionality will be attached to "take" and "return" buttons located near the cards. When user pushes these buttons the application will check if the Javscript is enabled. If enabled, then it will continue in the AJAX mode (no page reloading), if disabled, the buttons will work the same way as before (with page reloading).

2 - User with enabled Javascript will not have "take" and "return" buttons displayed, but he will move the cards (in and out of his deck) by clicking or double clicking (which one would you prefer?) on the card itself. This will move the cards using AJAX without reloading the page. Users with disabled Javascript will have the "take" and "return" buttons displayed and will have to move the cards the standard way (with page reload).

I'm in favor of 2, but the 1 preserves the old interface. Is it intuitive enough to click on the cards to move them?

In my opinion regarding #2, it would depend on the execution. If clicking it causes the card to "vanish" with the card after it instantly appearing in its position, this could prove confusing and cause people to accidentally click more than once and pull out multiple cards. However, if it could be done in such a way that there's an animation of sorts, such as the selected card "moving" downward and the cards after it "sliding" in to the newly vacant place, it would be both less confusing and more fun to use. Maybe clicking on the card triggers a quick animation where a swath of light travels downward from where the card was, the animation itself just occupying that space. (I'm not suggesting that the card can be seen flying to its new spot entirely, though if that were possible, it would be equally neat.)

I think double clicking would be more safe to avoid issues that DPsycho noted. Another way is to use an 'Undo' feature which could be quite tricky to implement though...

With Ajax enhancements we could also get rid of the horizontal scrollbar in the selecting cards section, as new cards could be loaded transparently when the user e.g scrolls inside a box or when the mouse reaches the edge of the screen. :-)

I'm in favour of number 2, and I would vote for single-clicking rather than double-clicking. Having to double-click in a web app seems very unnatural to me, and I can't think of any instances where it's used.

New deck editor engine implemented in https://netvor.sk/trac/arcomage/changeset/899

Changes will be applied in the upcoming update.