X-Wing List Juggler

By sozin, in X-Wing

- changed the list entry form to autofocus into the YASB, so there is a little blinking cursor that provides a visual hint to the user that they can enter the url there

- added some further protections from non utf-8 data (swedes... : :rolleyes: )

-fixed a bug in the 'add new player' functionality of a tourney

-fergus fixed an xws bug on his side ('slavei' vs 'slave1')

Edited by sozin

Scum is out!

XWS question: the xws spec lists lists the M3-A Scyk Interceptor as ' m3ainterceptor'.

but: voidstate has it as ' m3ascykinterceptor'.

yasb has it as: ' m3ainterceptor'

Who is right? I think that voidstate has it according to the canonical-ization rules:

  1. Take the English-language name as printed on the card
  2. Check for special case exceptions to these rules (see below)
  3. Lowercase the name
  4. Convert non-ASCII characters to closest ASCII equivalent (to remove umlauts, etc.)
  5. Remove non-alphanumeric characters
Edited by sozin

I went with voidstate's xws for the scyk as I think it is correct according to the canonicalization rules.

Card title errors in YASB tend to propagate to the XWS spec, since Geordan's got a decent track record of getting spoilers posted promptly, and had an easy data file that he allowed me to consume to spit out the XWS stuff.

I'll bug him to get it fixed.

If it's the English-language name as printed on the card, the canonicalization should be "m3ainterceptor":

Cartel-spacer-1-.png

I haven't gotten my grubby little hands on the actual card yet, though.

duh! geordan is right. the name should be m3ainterceptor.

sorry guys :-(

EDIT: I let fergus know

Edited by sozin

Ooh, yeah, I forgot to update the cards file on the Heroku app. I'll fix it after work.

Just wondering, if a Store Championship used the iOS "X-Wing TO" app to do all the data, is there a way to get the round by round matchups easily into the List Juggler? It seems like a nightmare to try to type all that in for 23 people, 4 rounds of swiss and the top 8 (I can probably do the top 8 manually). thoughts?

Yeah, I've done the Cryodex JSON file before and it was AMAZING! Thanks in advance Sozin!

no sweat. I posted over on the iOs app's blog page, hopefully he will respond!

The herokuapp link should be fixed now.

verified, ty

Geordan, Eli, Fergus, let's talk Advanced Targetting Computer: ' advancedtargetingcomputer ' or ' advtargetingcomputer '?

adv-targeting-computer.png

Canonicalization rules should be ' advtargetingcomputer '

YASB main has it right, http://geordanr.github.io/xwing/?f=Galactic%20Empire&d=v3!s!20:-1:23:-1:U.124;20:-1:23:-1:U.124;20:-1:23:-1:U.124;20:-1:23:-1:U.124;10::-1:-1:

YASB heroku has it wrong: https://yasb-xws.herokuapp.com/?f=Galactic%20Empire&d=v3!s!20:-1:23:-1:U.124;20:-1:23:-1:U.124;20:-1:23:-1:U.124;20:-1:23:-1:U.124;10::-1:-1:

voidstate has it right: http://xwing-builder.co.uk/xws/196526#view=full

xws spec has it wrong: https://github.com/elistevens/xws-spec/blob/master/README_NAMES.md

All agree?

Edited by sozin

Axel and I hooked up; we're going to create an API that the iOS app can use. here's a google doc where we are stashing the API spec.

All agree?

Yup.

Axel and I hooked up; we're going to create an API that the iOS app can use. here's a google doc where we are stashing the API spec.

Have you considered using REST? It's great for this kind of API.

vs

Updated YASB XWS to fix canonicalization for both Advanced Targeting Computer and Advanced Proton Torpedoes.

ooh, good one, I had the torps wrong as well (as does the xws spec!)

Edited by sozin

Axel and I hooked up; we're going to create an API that the iOS app can use. here's a google doc where we are stashing the API spec.

Thanks Sozin! I assume it's too late for the tournament that already happened and used XWing TO app?

Not sure, depends on how Axel handles it. Hopefully once he implements the functionality your tourney will be available for import.

ooh, good one, I had the torps wrong as well (as does the xws spec!)

I think that I'm going to add both of the "Advanced" -> "adv" names as special cases, just to make it super-explicit what the correct canonical name is.

I think that the only impact ATM would be to the custom .js validation function. Is not having the spec updated blocking development, or can I wait for the rest of the cases to get sorted out and update everything all in one go?