So, you have a couple of formats to write a config, but if user wants to use UI, it will be converted to JSON removing all formatting, right?
Just checking, I got that kind of a problem several times with different applications, when you can't automatically update config and preserve formatting at the same time. I have some ideas, but sadly no universally working solution yet.
14.01.2014, 23:50, "mgutz" <mario.l.gutier...@gmail.com>:
--I like the simplicity of JSON, I endured years of XML and XSLT :)The reason for the JSON format, which is actually any of JSON, CSON, YAML, is for the project script to survive round trips between the drag 'n drop GUI and editing the script manually. Functions are supported through simple declarations so yeah a JavasScript jock like yourself has all the power at his disposal, while front-end folks who just want to compile, watch, minify, image sprie by simple clicks don't have to deal with JSON or JS at all.
On Tuesday, January 14, 2014 4:13:54 AM UTC-8, Alex Kocharin wrote:Mark,One maintains an npm fork - https://github.com/rlidwka/yapm - and happily uses package.yaml forgetting that package.json ever existed. It was an experiment a year ago, but right now I can't even imagine how I would use package.json without an ability to comment anything. :)As for any other config file, it's a fair point. A lot of packages use json as a configuration file just because it's simple, but when they grow they usually change to something more appropriate. Sadly, it's usually cjson (commented json), but I really like to see something more advanced instead.Most packages use _javascript_ object as a config, take node-http-proxy for example. You require() it and pass a custom-made object defined somewhere of your choice. All my production servers use executable _javascript_ for writing configuration as well, because it allows greater flexibility.I'm trying to remember config formats for standalone tools... Grunt and similar tools use _javascript_ (or coffeescript in case of cake), JSHint - cjson, Sinopia - yaml, npm - ini (I wonder, did someone thought about why npm uses ini instead of json for a config?). Meteor uses package.js, that's where I envy them sometimes, you can do awesome things on install. Maybe bower still uses json in bowerrc? I don't use it though. pm2 uses json as well, but it's managed automatically and don't cause trouble.So yes, I read a lot of JSON files in mongodb interface or in traffic dumps from REST services, but I don't remember writing them, there are always more convenient tools.Regards,alex14.01.2014, 12:38, "Mark Hahn" <ma...@reevuit.com>:> If you're updating JSON by hand, you're doing it wrong. No exceptions.
I don't understand. How does one maintain a file like package.json or any other config file?
On Mon, Jan 13, 2014 at 10:07 PM, Alex Kocharin <al...@kocharin.ru> wrote:> JSON scripts are for GUIs so they can be updated by hand or a GUI.If you're updating JSON by hand, you're doing it wrong. No exceptions.14.01.2014, 03:03, "mgutz" <mario.l....@gmail.com>:gee - simpler builds using gulp filters* gulp filters (node streams)* autowatch (-w flag)* display errors and continue when watching* build modes* imperative or declaractive (JSON) project scriptsJSON scripts are for GUIs so they can be updated by hand or a GUI. Undecided whetherto create a standalone app like CodeKit or custom build of Adobe Brackets?Any feedback appreciated--
--
Job Board: http://jobs.nodejs.org/
Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
You received this message because you are subscribed to the Google
Groups "nodejs" group.
To post to this group, send email to nod...@googlegroups.com
To unsubscribe from this group, send email to
nodejs+un...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/nodejs?hl=en?hl=en
---
You received this message because you are subscribed to the Google Groups "nodejs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to nodejs+un...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.--
--
Job Board: http://jobs.nodejs.org/
Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
You received this message because you are subscribed to the Google
Groups "nodejs" group.
To post to this group, send email to nod...@googlegroups.com
To unsubscribe from this group, send email to
nodejs+un...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/nodejs?hl=en?hl=en
---
You received this message because you are subscribed to the Google Groups "nodejs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to nodejs+un...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.--
--
Job Board: http://jobs.nodejs.org/
Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
You received this message because you are subscribed to the Google
Groups "nodejs" group.
To post to this group, send email to nod...@googlegroups.com
To unsubscribe from this group, send email to
nodejs+un...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/nodejs?hl=en?hl=en
---
You received this message because you are subscribed to the Google Groups "nodejs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to nodejs+un...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
--
Job Board: http://jobs.nodejs.org/
Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
You received this message because you are subscribed to the Google
Groups "nodejs" group.
To post to this group, send email to nodejs@googlegroups.com
To unsubscribe from this group, send email to
nodejs+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/nodejs?hl=en?hl=en
---
You received this message because you are subscribed to the Google Groups "nodejs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to nodejs+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
