File system implementation

Conlang-Software-Dream-Team / Langscaper

constructed language development application

MIT License

0 stars 0 forks source link

File system implementation #7

Open KrankerApfel opened 2 months ago

KrankerApfel commented 2 months ago

The way we store data must be approved by both @terahlunah and @c-m-green before starting the implementation.

Features

[ ] Save a language

[ ] Define what data we need to store ( ID, name, nb speakers, etc...)

[ ] Define the how the data are organized ( is there an header ? are section nested as in phonology : { phonem : {...}})

[x] Define serialization method (Json ? yml ? )

[x] Define file extension (.ls for langscaper? .lang ? .conlang ?)

[ ] Must be easy to import/export only a subsection (ex: phonological system, inventory, etc..)

[ ] Load a language
[ ] Autosave system (each 10 min ? at exit ?)

terahlunah commented 2 months ago

nb speakers

What's that?

serialization method

JSON

is there an header?

Yes, at least for a version field that would help evolving this file without breaking stuff

file extension

I like .lang

how the data are organized

Too early to tell, it will reflect the C# structure representing a language's data

c-m-green commented 2 months ago

Define serialization method (Json ? yml ? )

I'm more familiar with JSON, and I think it'll suit our needs.

Define file extension (.ls for langscaper? .lang ? .conlang ?)

Subjectively, I like .conlang.

KrankerApfel commented 1 month ago

summary of our discussions

Together, we validated :

Serialization : JSON, and must have an header with versionning
File extension : .conlang
A description field in the json
A user custom metadata list (key:value). Things like number of speaker could be put inside by the user.

To be discussed later :

Define what data we need to store
Define the how the data are organized