XML option browser
-
@Mahks I don't think having an inlined all-in-one page fits the structure of our website.
Of course we could just upload the file and leave everything as-is, but if we want to align the design with a website we'd want to use the existing css that's being kept seperate in its own css file.
So if we want to drop offline support I have a pretty good strategy that'll make everything pretty easy to read.
I'd actually prefer seperate files per entry, the opposite of @redrum's idea.
This way everything is way more structured and easier accessible.
Also when creating a new entry one would just create a new file which is pretty straightforward IMO.
Also we could give "context" a special treatment so that the xml can just get pasted at the end of the file without having to to any escaping. -
Thanks for feedback.
To build on how yaml knows about the double colon, it knows based on the first letter after the first colon. There are three choices, 'string', 'list', or 'map', if it sees a
[
, it's a list,{
for a map, and any letter is a string value. You can also do lists in a different syntax, multi-line as:list_name: - a - b - c same_list_values: [ 'a' , 'b', c' ]
And for a map:
map_name: - property_a: 1 - property_b: 2 map_name { 'a': 1, 'b': 2 }
And you can nest these, so hence why we have a superset of JSON.
YAML provides block values with native HTML without any escaping, so it's just a nicer format to work with and avoids the error prone syntax requirements of JSON.
The idea is that we basically structure a YAML to match the needed JSON, work with the YAML by hand, and use software to do the relatively simple conversion to JSON and upload to website (we have an existing pattern for doing that).
All that aside, simply hosting the HTML directly on the triplea website is a good first option! : )
That would be just plopping the file in: https://github.com/triplea-game/triplea-game.github.io; Then it'll be available from
http://triplea-game.org/theFileName.html
-
Sounded to me like offline support was in-lieu of online support. The most brute-force option here is to just host on website as an html.
Overall it seems we are weighing three options:
- maintain the data as an html file (post-render) hosted directly on website repo.
- create dynamic html page that is hosted on website repo, feed the page a JSON payload that is rendered from a YML file
- create dynamic html page that is hosted on website repo, feed the page a JSON payload that is rendered from a set of input files (eg: all files in a given folder)
Let me know @RoiEX if I mischaracterized the recommendation.
-
@LaFayette Seems right.
However I'd like to point out option 2 and 3 do not work well offline. -
-
-
@mahks Nice job.
-
@mahks Glad to see this is still alive. Well done fine sir!
-
The hierarchical index is great tool for anyone trying to understand what is possible with triplea game scenario .xml. POS2 can be a bit hard to read and take in.
-
@butterw POS2 is out of date in places as well : |
-
is this still getting updated? it looks like @Mahks hasn't posted in several years...
wondering if anyone can fix the entry for "carrierCapacity" as it's example is for "carrierCost".
actually, while on the subject of corrections, can we get all the examples to use " (double quotes) instead of ' (single quotes)? such a pain having to edit when copy/pasting and missing one...
-
@Myrd was doing some work to move the XOB to the official TripleA website.
It is kinda available here, but does not yet render nicely:
https://triplea-game.org/xob/XOB.html -
good to know it's not been abandoned.
although that link just displayed the code for me...
-
@cameron Indeed; not sure what is more needed to get it to actually "render". I was happy to see it be picked back up as well.
-
i copypasted the text into notepad and deleted the
"Line wrap
<!DOCTYPE HTML>"
bit at the front and saved it as an .html file and now it works in my browser (firefox). -
It is interesting that works. Seemingly it is the web browser auto-attaching the 'doctype' part.
Here is the raw contents of the file, notice it is missing that doctype line:
https://github.com/triplea-game/triplea-game.github.io/blob/master/xob/XOB.htmlFor comparison: https://triplea-game.org/xob/XOB.html
What else, I'm not able to apply the same trick as you. If I save the file & open it - I see similar results as 'https://triplea-game.org/xob/XOB.html'
-
huh. so what's adding the weird prefix?
maybe try commenting out line 9 & 10?
-
I think the XOB file format is escaped. We may need to take another stab at exporting the data.