PixelsCommander
PixelsCommander on Hacker News
Re:Render HTML via WebGL
on Thursday April 02, 2015 @10:09AM (#9310760)
Re:Render HTML via WebGL
on Thursday April 02, 2015 @10:09AM (#9310753)
Browser rasterizes based on it`s assumptions and you cant control it completely which is a bottleneck for performance optimization. Also how would you apply displacement filter on that content?
Re:Render HTML via WebGL
on Thursday April 02, 2015 @10:06AM (#9310734)
Thanks! We are working on improving responsiveness a bit. Will be better.
Re:Render HTML via WebGL
on Thursday April 02, 2015 @10:05AM (#9310724)
Come on! We can do much more together =) Still so many WOW things to implement...
Re:Render HTML via WebGL
on Thursday April 02, 2015 @10:04AM (#9310715)
I would not expect any conflicts there since they are different canvases and textures uploaded just as files. You may ask [email protected] for more details.
Re:Render HTML via WebGL
on Thursday April 02, 2015 @10:02AM (#9310700)
Nice, we may use it as a renderer for HTML GL. Shaders and fast rendering wirth it I believe. Try the demo in the bottom http://htmlgl.com/
Re:Render HTML via WebGL
on Thursday April 02, 2015 @09:48AM (#9310613)
It is already there https://www.chromeexperiments.com/webgl , but it starts to be even more exciting if you think about effects which could be applied to web sites and HTML content... Bumb mapping, reflections, motion blur, elastic elements when dragging. Whole bunch of shaders https://www.shadertoy.com/browse
Re:Render HTML via WebGL
on Thursday April 02, 2015 @09:41AM (#9310591)
It is basicaly not. Just converting HTML to texture with some tricky proxying. The reason is to be able to do that http://pixelscommander.com/polygon/htmlgl/demo/filters.html
Re:Render HTML via WebGL
on Thursday April 02, 2015 @09:36AM (#9310569)
It can be selected at same bounding box DOM node have and the selection will not be highlighted at the moment, but we will fix that.
The state of HTML content rasterization with JavaScript
Re:Applying NASA coding standards to JavaScript
on Thursday January 08, 2015 @10:21AM (#8856728)
Do you mean F-35 project by saying JSF or this is a typo on JPL ?
Re:Applying NASA coding standards to JavaScript
on Thursday January 08, 2015 @10:05AM (#8856645)
Yep, applying this restriction on functions is something I would avoid to suggest as they are a cornerstone of modern JS development.
However another part of rule seems to be something to consider.
Re:Applying NASA coding standards to JavaScript
on Thursday January 08, 2015 @09:57AM (#8856601)
Any help on making text better is appreciated. Blogspam... May be, but consider that PDF were published a long time ago and not that many Web people were interested until there came a way to use it in everyday practice.
Re:Applying NASA coding standards to JavaScript
on Thursday January 08, 2015 @09:49AM (#8856571)
This is the missing thing, will add. Thanks guys!
Re:Applying NASA coding standards to JavaScript
on Thursday January 08, 2015 @09:47AM (#8856554)
"focus on more extensive automated testing, focus on more profiling, and focus on general software engineering principles like single-responsibility and DRY" - this is exactly what was suggested in article. Except may be DRY which is more about design.
Re:Applying NASA coding standards to JavaScript
on Thursday January 08, 2015 @09:43AM (#8856533)
Done, thanks. Please, let me know if there are more typos / stylistic issues.
Applying NASA coding standards to JavaScript
Using React components just as HTML elements
One world – one frontend or first flight instrument built with HTML
Good day colleagues! One more good day which will ends quickly become past and will present one more step forward for us. How will front end development we are all passionate of look like tomorrow?