oeed / CraftOS-Standards

Community standard file formats, communication systems, etc. for ComputerCraft and CraftOS 2.0
Other
20 stars 14 forks source link

Configuration File Standard #50

Closed Luca0208 closed 8 years ago

bauen1 commented 8 years ago

From what i can see your using Key: Value But some people may also use Key = Value

Luca0208 commented 8 years ago

Hmm, that's true, let's see what other people thing.

ghost commented 8 years ago

ComputerCraft Introduced an Standard itself, using your Standard is like using something else instead of Rednet (but with modems too)

viluon commented 8 years ago

@Luca0208 a couple of things:

Luca0208 commented 8 years ago

1.I'm not good with name, everyone feel free for suggestions

  1. It is more readable than a normal Lua table
  2. I will fix it
oeed commented 8 years ago

To be honest I think config files should just use textutils.serialise. I just don't think people are going to bother using the format when there's very little difference and one has built in support.

Luca0208 commented 8 years ago

My point is, if someone who is new to CC sees these two files(can't use codenlocks currently, sorry):

Name:"Player1"
Difficulty:1

and

{
  Name="Player1",
  Difficulty=1,
}

The potential to screw up the bottom version is higher.

meta: Added code blocks for you ~ @viluon

viluon commented 8 years ago

In that case, you are better off making a GUI settings screen. Nice people make those even for experienced users, so that they don't have to dig through the config files.

I feel like closing this because #41 is superior. Any objections?

lyqyd commented 8 years ago

Yes, this should be closed in favor of #41. Intentionally not supporting line breaks isn't fantastic, and valid-lua configuration files are easier to handle than plain text, within the context of ComputerCraft.