{
"name": "Bender"
, "hind": "Bitable"
, "shiny": true
}
W3C HTML JSON form submission
21–30 of 103 posts
Re: W3C HTML JSON form submission
#22The JSON-based file upload would be nice (AFAIK there's not great way to do this ATM, but I haven't looked in over a year). The rest seems pretty weak-tea though. I can see multiple issues with more defined type (e.g. numeric rather than string values, null rather than blank string), but without dealing with that stuff, this seems of extremely limited utility.
It's nice for small files but base64 really is inefficient. I think it is still used in mails, but really, you should use it only when you control all the usages that will be done with it.
Re: W3C HTML JSON form submission
#23{ "name": "Bender" , "hind": "Bitable" , "shiny": true } Who puts commas at the start of a continuing line? What good could that possibly do?
Send a pull - github for the win! http://darobin.github.io/formic/specs/json/
Re: W3C HTML JSON form submission
#24{ "name": "Bender" , "hind": "Bitable" , "shiny": true } Who puts commas at the start of a continuing line? What good could that possibly do?
It lets you comment out a line without having to remove the trailing comma from the previous line. That'd be useful if JSON had comments.
I've seen people do this in the SELECT portion of SQL queries too.
Personally, I hate this.
Re: W3C HTML JSON form submission
#25They're still working on XForms after 10 years http://www.w3.org/MarkUp/Forms/
Isn't that kind of like saying "They're still working on HTML after 23 years"? Technically you're right, but version 1.1 of XForms was completed and published over 5 years ago. That said, XForms is dead AFAIK, and that's not a bad thing.
Yeah, my point was more along the lines of they've been working for 10 years and gotten near zero adoption. Not saying it will fail again for sure, but if this had value, XForms would have found it. URL-encoded POST data works just fine.
Re: W3C HTML JSON form submission
#26Kind of nice, basically turns form submission into a bare-bones API call.
Which they pretty much already were. The only value I can imagine this adding is a way to encode forms with nested structure.
Re: W3C HTML JSON form submission
#27{ "name": "Bender" , "hind": "Bitable" , "shiny": true } Who puts commas at the start of a continuing line? What good could that possibly do?
It lets you comment out a line without having to remove the trailing comma from the previous line. That'd be useful if JSON had comments. I've seen people do this in the SELECT portion of SQL queries too. Personally, I hate this.
True about the comment. That's why I like the trailing comma style in pep8[1], which enables both commented out array elements and smaller, more meaningful diffs when making additions or deletions. If only trailing commas were valid JSON!
Re: W3C HTML JSON form submission
#28{ "name": "Bender" , "hind": "Bitable" , "shiny": true } Who puts commas at the start of a continuing line? What good could that possibly do?
It lets you comment out a line without having to remove the trailing comma from the previous line. That'd be useful if JSON had comments. I've seen people do this in the SELECT portion of SQL queries too. Personally, I hate this.
> It lets you comment out a line without having to remove the trailing comma from the previous line. That'd be useful if JSON had comments.
It also lets you remove the line (for the same reason that you can comment it out) without modifying other lines. This is somewhat convenient if the file is one that you are going to manually edit (and even more useful if it is going to be the subject of line-oriented diffing tools, since the only changed lines will be the ones with meaningful changes.)
I'd agree that its less readable, though.
Re: W3C HTML JSON form submission
#29{ "name": "Bender" , "hind": "Bitable" , "shiny": true } Who puts commas at the start of a continuing line? What good could that possibly do?
It lets you comment out a line without having to remove the trailing comma from the previous line. That'd be useful if JSON had comments. I've seen people do this in the SELECT portion of SQL queries too. Personally, I hate this.
It also lets you find missing commas more easily.
Re: W3C HTML JSON form submission
#30Earlier quoted context omitted.
It lets you comment out a line without having to remove the trailing comma from the previous line. That'd be useful if JSON had comments. I've seen people do this in the SELECT portion of SQL queries too. Personally, I hate this.
It also lets you find missing commas more easily.
I found it almost a necessity when I started generating larger DOM trees in JavaScript. No more games of hunt-the-missing-comma-on-the-ragged-edge: https://gist.github.com/insin/8e72bed793772d82ca8d (These syntax woes are one of the main problems React's JSX solves)