Sounds great! Decentralised is better, like, same basic structure ("protocol", but more like directory structure and perhaps GET query, at most, something simple) and so you pass a base path or domain to a tool and it can browse or download from any car repository.
So car IDs, I guess, we keep using the four letter system that's default in Stunts. In other words, same four letters, same car, except version in any case. Right? To follow DOS, it should be case-insensitive and most ASCII wouldn't be allowed. Safest is letters, numbers, and underscore. Daniël recently introduced the number sign. In DOS, extended ASCII was allowed, but this brings problems for new Unicode based systems. What do you think?
Also, would a repository be able to have several subdirectories, like several "garages"?
Your config file example is interesting. It allows for multi-line values and is multi-dimensional. Just checking on this idea to make sure we understand it the same way:
* Pipe as the first significant (non-space) in the value side of the colon means multi-line
* Lines containing no colon are ignored except as part of a previously defined multi-line value
* A line with a colon provides a key:value pair and breaks any previously open multi-line value
* Identations allow for nested key:value pairs
Am I right?
Here my only doubt is how to handle when you need to enter a colon as part of a text. In my older configuration format (with equal signs), an equal sign is allowed in the value because only the first one separates key from value, so not allowed in the key. I was also just ignoring indentations.
I imagine these two could be internally seen as identical:
Just some thoughts
EDIT: Another thing to consider... how about lines that begin with spaces? I would like a simple format that looks good to the human eye, doesn't need escaping, is easy to parse, yet powerful. I can think of some opitmisations
So car IDs, I guess, we keep using the four letter system that's default in Stunts. In other words, same four letters, same car, except version in any case. Right? To follow DOS, it should be case-insensitive and most ASCII wouldn't be allowed. Safest is letters, numbers, and underscore. Daniël recently introduced the number sign. In DOS, extended ASCII was allowed, but this brings problems for new Unicode based systems. What do you think?
Also, would a repository be able to have several subdirectories, like several "garages"?
Your config file example is interesting. It allows for multi-line values and is multi-dimensional. Just checking on this idea to make sure we understand it the same way:
* Pipe as the first significant (non-space) in the value side of the colon means multi-line
* Lines containing no colon are ignored except as part of a previously defined multi-line value
* A line with a colon provides a key:value pair and breaks any previously open multi-line value
* Identations allow for nested key:value pairs
Am I right?
Here my only doubt is how to handle when you need to enter a colon as part of a text. In my older configuration format (with equal signs), an equal sign is allowed in the value because only the first one separates key from value, so not allowed in the key. I was also just ignoring indentations.
I imagine these two could be internally seen as identical:
Code Select
default_color: blue
urls:
wiki: https://wikiaddress
author_site: https://authorsite
author: Overdrijf
Code Select
default_color: blue
urls.wiki: https://wikiaddress
urls.author_site: https://authorsite
author: Overdrijf
Just some thoughts
EDIT: Another thing to consider... how about lines that begin with spaces? I would like a simple format that looks good to the human eye, doesn't need escaping, is easy to parse, yet powerful. I can think of some opitmisations