Skip to content

Conversation

@Luca0208
Copy link
Contributor

@Luca0208 Luca0208 commented Feb 9, 2016

No description provided.

@bauen1
Copy link

bauen1 commented Feb 9, 2016

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

@Luca0208
Copy link
Contributor Author

Luca0208 commented Feb 9, 2016

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

@ghost
Copy link

ghost commented Feb 9, 2016

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

@viluon
Copy link
Collaborator

viluon commented Feb 9, 2016

@Luca0208 a couple of things:

  • Please name your standard
  • What are the benefits of using your standard over serialized Lua tables Lua table format #41?
  • Please use proper highlighting for code samples

@Luca0208
Copy link
Contributor Author

Luca0208 commented Feb 9, 2016

1.I'm not good with name, everyone feel free for suggestions
2. It is more readable than a normal Lua table
3. I will fix it

@oeed
Copy link
Owner

oeed commented Feb 9, 2016

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
Copy link
Contributor Author

Luca0208 commented Feb 9, 2016

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
Copy link
Collaborator

viluon commented Feb 9, 2016

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?

@viluon viluon changed the title Added config.md Configuration File Standard Feb 9, 2016
@lyqyd
Copy link
Collaborator

lyqyd commented Feb 9, 2016

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants