Today have been plagued by my VNC client "evaporating".
Probably because my VNC window is pretty large, 1200 high by circa 6000 wide, to span all of my displays.
Disclaimer
The content of this blog is my personal opinion only. Although I am an employee - currently of Nvidia, in the past of other companies such as Iagination Technologies, MIPS, Intellectual Ventures, Intel, AMD, Motorola, and Gould - I reveal this only so that the reader may account for any possible bias I may have towards my employer's products. The statements I make here in no way represent my employer's position, nor am I authorized to speak on behalf of my employer. In fact, this posting may not even represent my personal opinion, since occasionally I play devil's advocate.
See http://docs.google.com/View?id=dcxddbtr_23cg5thdfj for photo credits.
See http://docs.google.com/View?id=dcxddbtr_23cg5thdfj for photo credits.
Thursday, February 09, 2012
Nested structure without parentheses
In my thoughts about PSON (Pseudo Object Notation), descended from Pseudo-XML and earlier Perl-SQL notation:
Stipulate the usual: nice parens and quotes. I'm just looking to strip out visual clutter ad create a more human readable subset - e.g. so that muy debug lines can be parseable.
Earlier I blogged about letting = be a tighter binding strength than :. so that
Delineating the end of the struct is an issue. Hinted at above by s= a=1 b:2, t=7
We can use whitespace separated elements, comma-separated, semi-colon separated, period separated as a hierarchy of nesting:
a b, c, d, e; f g h, i j k
(((a b), c, d, e); ((f g h), (i j k)))
Not general, because only three levels. But human friendly, similar to what I do naturally in real life.
Q: intermixing : and = binding, and the blank/comma/semicolon separated lists? Who binds first?
Stipulate the usual: nice parens and quotes. I'm just looking to strip out visual clutter ad create a more human readable subset - e.g. so that muy debug lines can be parseable.
Earlier I blogged about letting = be a tighter binding strength than :. so that
s: a=1, b=2, t: 7becomes
s: { a=1, b=2 }, t: 7There's no need for binding strength. Can just have any name = or name : without an atom\
s= a=1 b:2, t=7yielding
s= {a=1 b:2}, t=7---
Delineating the end of the struct is an issue. Hinted at above by s= a=1 b:2, t=7
We can use whitespace separated elements, comma-separated, semi-colon separated, period separated as a hierarchy of nesting:
a b, c, d, e; f g h, i j k
(((a b), c, d, e); ((f g h), (i j k)))
Not general, because only three levels. But human friendly, similar to what I do naturally in real life.
Q: intermixing : and = binding, and the blank/comma/semicolon separated lists? Who binds first?
<angle brackets in titles confuses blogger>
If you put angle brackets in the title of a blogger post, like this:
Not clear that this is a bug, but certainly a feature of questionable merit.
Yet another quotification issue.
<angle brackets in titles confuses blogger>blogger gets confused and decides that it is an untitled post - whereas if there is truly bno title, blogger guesses from the first line.
Not clear that this is a bug, but certainly a feature of questionable merit.
Yet another quotification issue.
Monday, February 06, 2012
< tags with words breaking XML rules >
<tag some attributes>
...
...
</tag>
e.g.
<test expected-time="10min" start="">
</test elapsed-time=5min>
--
<tags that occupy a line by themselves are fairly clear/>
and, if so restricted, allowing < and > inside text is simple.
<tag>on same line</tag> and <more/>
no so bad. But tyhe morte allowed, the more possibilities for confusion.
...
...
</tag>
e.g.
<test expected-time="10min" start="">
</test elapsed-time=5min>
--
<tags that occupy a line by themselves are fairly clear/>
and, if so restricted, allowing < and > inside text is simple.
<tag>on same line</tag> and <more/>
no so bad. But tyhe morte allowed, the more possibilities for confusion.
Serialization Formats
There are so many: http://en.wikipedia.org/wiki/Comparison_of_data_serialization_formats
And yet, I want some more, with my pseudo-XML (or pseudo-JSON, or whatever)
-
ASN/1: an XML subset, that defines how values are represented (as text, not attributes).
- Netstring: length:strings,
- JSON: hashes ansd arrays; keys are strings, just like values.
- OGDL: trees, indentation based, with commas and parenrtheses for when you don't want new lines. #comments and references. Guaranteed round tripping, except for comments.
- Property lists; NeXT to Apple.
- YAML: outline indentation, name:, little quoting, {hash: value}, [arrays, ...]; &id anchors and *id references, name: value, name: !!type value, !!binary
- XML: <tag>barewords</tag>, <>tag/>, attribute metadata. Basically simple, and then a whole lot of crap descended from SGML. Schemas and DTDs :-( Namespaces, references, XQuery, XSLT. An occasionally uncomfortable distinction between metadata (atributes) and data (text).
Why I dislike XML
I want to be abkle to write
<matching-brackert>
text, maybe some math, like a <b and c> d </matching-brackert>
withiout having to write ugly \&\l\t\; Heck, this WYSIWYG blog ceditor is an example - I can;t figure out how to type thye escape code for & lt ;
text, maybe some math, like a <b and c> d </matching-brackert>
withiout having to write ugly \&\l\t\; Heck, this WYSIWYG blog ceditor is an example - I can;t figure out how to type thye escape code for & lt ;
Subscribe to:
Posts (Atom)