John Friend
John Friend
You can't write native bindings that will run in node unless you're going to require your app run at root level access. The whole reason for doing an exec on...
What do you think could be improved in that regard? There's one exec() call for .open(), one for .close() and everything else is just node.js file I/O.
More native bindings and thus more things to compile per platform is a significant complication and place for things to go wrong. Thus, it should be justified with a proven...
Then I would think some performance tests with native bindings for read and write are in order to see how much of a difference it makes compared to the file...
One possible work-around to issue #1 is to just call gpio.close(pin) before I call gpio.open(pin) and just ignore any error that happens on the .close(). So, if the pin happens...
This issue is currently wrecking the formatting on a bunch of code I wrote awhile ago, but am now just trying to use in an environment that uses js-beautify. Has...
> That is unfortunate but unavoidable. Why is it unavoidable? Nobody believes there's any algorithm that could do better?
Why did you remove so much code from docreadytest.html?
That's perfectly fine to include docready.js into the test page instead of the copy of the code that it had, but you removed a lot of test code too so...
The tests were designed to log when various events happened relative to one another so one could see that docReady is firing at the right time relative to other things...