guycook

Whoops. goto fail indeed

I'm still working on getting QML [0] running in the browser because I think it should be the write-once run-everywhere language of modern UIs. https://github.com/guycook/HQML

[0] http://qt-project.org/doc/qt-5.0/qtquick/qtquick-application...

Working on a QML runtime for browsers. It's cool for all the reasons QML on the desktop is for describing UIs. Still early days but there's a prototype at http://ivorydungeon.net/HQML and code at https://github.com/guycook/HQML

Just a heads up, I went to fetchnotes.com in Firefox (23) and got nothing but a blank blue page with the following errors: http://i.imgur.com/zjBXqSx.png

Nevertheless, I checked out your site in Chrome and I'll send my application later today :)

This is really neat - already knew everything here but if it ramps up I'll be coming back.

For those who want to dig into pixel shaders, I recently wrote a tutorial going from no-knowledge to intermediate on this very topic:

http://ivorydungeon.net/2013/zero-to-glsl-spectrum-analyser-... HN - https://news.ycombinator.com/item?id=6159240

This is brilliant. I've been working lately on something very similar (using d3 + gonville) so I know how much work must have gone into this.

I'm sure you're aware of how much is left to do, but if I had to offer one criticism for right now it's that getting around is a bit slow. Ctrl+left/right for moving between measures and home/end for each line would be quite helpful.

It's quite heavy for me (too much for my liking as well) - Chrome 27 on OSX. The culprit is http://shkspr.mobi/blog/?custom-css=1&csblog=1&cscache=6&csr... giving a font-weight of 500. Probably affecting OSX people only

whilst I'm usually loathe to see comments such as this, I was interested in reading this and must say:

The post is completely unreadable on opera mobile, whether I send through desktop or mobile UA, and on default 2.3 browser. Guess I'll give it a read at work tomorrow.

I would hardly call this 'the norm', may as well say the all C software inevitably segfaults and is thus unreliable since that happens at least once to everyone who's ever learnt the language. PHP newbies just have the unfortunate side effect of being a bit more exposed to the 'outside elements' while learning.

And if your prior employment recruited based on connections rather than competence that speaks to a management issue that couldn't possibly be solved by switching languages.

(this isn't really to single out your comment meaty, could be attached to anyone else in this thread)

I'm surprised at so many people taking a hard line at 80 characters. I guess you never wanted to

    automaticallyForwardAppearanceAndRotationMethodsToChildViewControllers

I'm not seeing any on the website as a guest but

    wget http://thenounproject.com/download/zipped/svg_{1..10000}.zip && unzip '*.zip' && zip nouns *.svg

should do the trick

Yes, quite right. I probably wasn't clear enough there, but I was referring to this from the article:

  <input type="text" required><label>Social Security Number</label></input>

Should be marked up as

  <label>Social Security Number<input type="text" required /></label>

if you want to omit the 'for' attribute.

Doing it the wrong way around will still render as you expect, but defeats the purpose as you won't get the click-to-activate behaviour.

Number 1 (and throughout the article) isn't right, the input should go inside the label.

See https://developer.mozilla.org/en-US/docs/HTML/Element/input Permitted content: None, this is a void element.

And https://developer.mozilla.org/en-US/docs/HTML/Element/label for an example of doing it correctly