#77267: "Do more actions in the front-end interface instead of the back-end"
Petra a zo c'hoarvezet ? Trugarez evit dibab amañ dindan
Petra a zo c'hoarvezet ? Trugarez evit dibab amañ dindan
Gwiriit mar-plij ma n'eus ket dija un danevell evit an hevelep dodenn
M'oc'h a-du, VOTIT evit an danevell-mañ. An danevelloù gant ar muiañ a vouezhioù a vo studiet DA GENTAÑ !
| # | Status | Votes | Game | Type | Title | Last update |
|---|
Deskrivadur dre ar munud
-
• Mar-plij, eilit/pegit ar gemennadenn fazi a zo war ho skramm, ma zo unan.
For Seasons, there are many cases where it would make sense to do more in the front-end instead of in the back-end. Especially when activating a card, all choices (which effect to use if there are multiple, paying the cost for the effect) should be handled at once in the front-end. Then this combined data could be sent at once to the back-end.
This would allow implementing Undo/Cancel in some cases and would generally make Seasons more user friendly.
A good example where this already partially happens is Amulet of Time: the user can select/unselect multiple cards to discard before confirming. -
• Displegit deomp, mar-plij, ar pezh ho poa c'hoant d'ober, ar pezh ho peus graet hag ar pezh a zo c'hoarvezet 'benn ar fin
• Peseurt merdeer eo hoc'h hini ?
Mozilla v5
-
• Mar-plij, eilit/pegit an destenn e Saozneg ha n'eo ket en ho yezh. M'ho peus un dapadenn skramm eus ar gudenn (ho pezit soñj d'eus se !), gellout a rit implij Imgur.com evit e bellgargañ hag eilañ/pegañ al liamm amañ.
For Seasons, there are many cases where it would make sense to do more in the front-end instead of in the back-end. Especially when activating a card, all choices (which effect to use if there are multiple, paying the cost for the effect) should be handled at once in the front-end. Then this combined data could be sent at once to the back-end.
This would allow implementing Undo/Cancel in some cases and would generally make Seasons more user friendly.
A good example where this already partially happens is Amulet of Time: the user can select/unselect multiple cards to discard before confirming. -
• Ha dibres eo an destenn-mañ er sistem treiñ? Ma ya, daoust ha troet eo bet ouzhpenn 24 eur 'zo ?
• Peseurt merdeer eo hoc'h hini ?
Mozilla v5
-
• Displegit ho kinnig mar-plij, e berrgomzoù met en un doare resis, evit ma vefe an aesañ posupl kompren mat ar pezh ho peus c'hoant lâret.
For Seasons, there are many cases where it would make sense to do more in the front-end instead of in the back-end. Especially when activating a card, all choices (which effect to use if there are multiple, paying the cost for the effect) should be handled at once in the front-end. Then this combined data could be sent at once to the back-end.
This would allow implementing Undo/Cancel in some cases and would generally make Seasons more user friendly.
A good example where this already partially happens is Amulet of Time: the user can select/unselect multiple cards to discard before confirming. • Peseurt merdeer eo hoc'h hini ?
Mozilla v5
-
• Petra oa diskouezet war ar skramm pa 'z oc'h chomet stanket (Skramm goullo ? Ul lodenn eus etrefas ar c'hoari ? Kemennadenn fazi ?)
For Seasons, there are many cases where it would make sense to do more in the front-end instead of in the back-end. Especially when activating a card, all choices (which effect to use if there are multiple, paying the cost for the effect) should be handled at once in the front-end. Then this combined data could be sent at once to the back-end.
This would allow implementing Undo/Cancel in some cases and would generally make Seasons more user friendly.
A good example where this already partially happens is Amulet of Time: the user can select/unselect multiple cards to discard before confirming. • Peseurt merdeer eo hoc'h hini ?
Mozilla v5
-
• Pesseurt reolenn n'eo ket doujet gant azasadenn ar c'hoari-mañ ?
For Seasons, there are many cases where it would make sense to do more in the front-end instead of in the back-end. Especially when activating a card, all choices (which effect to use if there are multiple, paying the cost for the effect) should be handled at once in the front-end. Then this combined data could be sent at once to the back-end.
This would allow implementing Undo/Cancel in some cases and would generally make Seasons more user friendly.
A good example where this already partially happens is Amulet of Time: the user can select/unselect multiple cards to discard before confirming. -
• Ha posupl eo gwelet torridigezh ar reolenn e replay ar bartienn ? Ma 'z eo ya, da be niverenn taol ?
• Peseurt merdeer eo hoc'h hini ?
Mozilla v5
-
• Peseurt taol ho peus c'hoant c'hoari ?
For Seasons, there are many cases where it would make sense to do more in the front-end instead of in the back-end. Especially when activating a card, all choices (which effect to use if there are multiple, paying the cost for the effect) should be handled at once in the front-end. Then this combined data could be sent at once to the back-end.
This would allow implementing Undo/Cancel in some cases and would generally make Seasons more user friendly.
A good example where this already partially happens is Amulet of Time: the user can select/unselect multiple cards to discard before confirming. -
• Petra emaoc'h o klask ober evit delankañ an ober c'hoari-mañ ?
-
• What happened when you try to do this (error message, game status bar message, ...)?
• Peseurt merdeer eo hoc'h hini ?
Mozilla v5
-
• Da be bazenn ar bartienn eo en em gavet ar gudenn (petra oa testenn kemenn ar c'hoari) ?
For Seasons, there are many cases where it would make sense to do more in the front-end instead of in the back-end. Especially when activating a card, all choices (which effect to use if there are multiple, paying the cost for the effect) should be handled at once in the front-end. Then this combined data could be sent at once to the back-end.
This would allow implementing Undo/Cancel in some cases and would generally make Seasons more user friendly.
A good example where this already partially happens is Amulet of Time: the user can select/unselect multiple cards to discard before confirming. -
• What happened when you try to do a game action (error message, game status bar message, ...)?
• Peseurt merdeer eo hoc'h hini ?
Mozilla v5
-
• Mar-plij, diskrivit kudenn an diskwel. M'ho peus un dapadenn skramm eus ar gudenn (ho pezit soñj d'eus se !), gellout a rit implij Imgur.com evit e bellgargañ hag eilañ/pegañ al liamm amañ.
For Seasons, there are many cases where it would make sense to do more in the front-end instead of in the back-end. Especially when activating a card, all choices (which effect to use if there are multiple, paying the cost for the effect) should be handled at once in the front-end. Then this combined data could be sent at once to the back-end.
This would allow implementing Undo/Cancel in some cases and would generally make Seasons more user friendly.
A good example where this already partially happens is Amulet of Time: the user can select/unselect multiple cards to discard before confirming. • Peseurt merdeer eo hoc'h hini ?
Mozilla v5
-
• Mar-plij, eilit/pegit an destenn e Saozneg ha n'eo ket en ho yezh. M'ho peus un dapadenn skramm eus ar gudenn (ho pezit soñj d'eus se !), gellout a rit implij Imgur.com evit e bellgargañ hag eilañ/pegañ al liamm amañ.
For Seasons, there are many cases where it would make sense to do more in the front-end instead of in the back-end. Especially when activating a card, all choices (which effect to use if there are multiple, paying the cost for the effect) should be handled at once in the front-end. Then this combined data could be sent at once to the back-end.
This would allow implementing Undo/Cancel in some cases and would generally make Seasons more user friendly.
A good example where this already partially happens is Amulet of Time: the user can select/unselect multiple cards to discard before confirming. -
• Ha dibres eo an destenn-mañ er sistem treiñ? Ma ya, daoust ha troet eo bet ouzhpenn 24 eur 'zo ?
• Peseurt merdeer eo hoc'h hini ?
Mozilla v5
-
• Displegit ho kinnig mar-plij, e berrgomzoù met en un doare resis, evit ma vefe an aesañ posupl kompren mat ar pezh ho peus c'hoant lâret.
For Seasons, there are many cases where it would make sense to do more in the front-end instead of in the back-end. Especially when activating a card, all choices (which effect to use if there are multiple, paying the cost for the effect) should be handled at once in the front-end. Then this combined data could be sent at once to the back-end.
This would allow implementing Undo/Cancel in some cases and would generally make Seasons more user friendly.
A good example where this already partially happens is Amulet of Time: the user can select/unselect multiple cards to discard before confirming. • Peseurt merdeer eo hoc'h hini ?
Mozilla v5
Roll-istor an danevelloù bog
Ouzhpennañ un dra bennak d'an danevell-mañ
- Niverenn taol all / Niverenn ar fiñv
- Ha renket eo bet ar gudenn gant an douchenn F5 ?
- Ha c'hoarvezet eo ar gudenn meur a wech ? Bewech ? Cheñch-dicheñch ?
- M'ho peus un dapadenn skramm eus ar gudenn (ho pezit soñj d'eus se !), gellout a rit implij Imgur.com evit e bellgargañ hag eilañ/pegañ al liamm amañ.
