1,958 karma · joined April 19, 2011
- WebCore - the rendering engine
- JavaScriptCore (aka SquirrelFish or Nitro) - JavaScript engine
- WebKit - synchronous API
- WebKit2 - asynchronous API
All WebKit-based browsers are using the same rendering engine (that is WebCore). Only some of them are using other WebKit components.Google did not fork WebKit to implement Gamepad API and WebGL, those features are implemented in upstream WebKit project (check http://goo.gl/5M9gN). Safari does not support them probably because of its longer release cycle.
It's true that there is no single version of WebKit though. Browser vendors are free to take any SVN snapshot, replace any component, toggle on/off any feature and brand it with any version number they prefer.
Files that break cross-origin policy or use non-standard tags are poorly authored by my standards.
I have a lot of experience with SVG under WebKit-based browsers and so far everything renders just fine for me except for advanced features mentioned earlier.
Inkscape is doing layer compositing by applying filters on groups. This is not SVG 1.2 feature. It was present in SVG 1.1 for years and it's still not properly implemented by all browsers and authoring tools: http://www.w3.org/TR/SVG/filters.html#feBlendElement
def set_clock():
ctx.beginPath()
ctx.fillStyle = "#FFF"
ctx.arc(width/2,height/2,ray*0.89,0,2*math.pi)
ctx.fill()
show_hours()
This is not the case with some other languages that compile to JavaScript, e.g. LiveScript allows dash-case almost everywhere.You don't need to sanitize SVGs to host them safely - you just put them inside <img> tag and browsers will do sandboxing for you.
What features do you actually miss in SVG 1.1? Gradient meshes? 3d transforms? multiple fills? I can think of only advanced stuff that is rarely used and tricky to do with other web technologies anyway.
Also, why would you want to strip browser-incompatible SVG elements? Browsers will simply ignore such elements.
1. If you do something that is not moving you towards your goal then it's moving you away from your goal.
2. What you DO NOT include in your product is as important as what you DO include.
Sample usage:
button =
toggleOn: ->
@trigger 'toggled', 'on'
window =
init: ->
button.listen 'toggled', (buttonState) =>
@showWindow if buttonState is 'on'I'm also using delegate and prototype patterns a lot, though those are rather dangerous when misused. Deep inheritance chains or excessive method overrides can easly make the code unmaintainable.
What I fail to see is how legalizing file sharing on massive scale (akin to MegaUpload) and banning DRM technologies would improve consumer rights. The natural response from the market would be to move to the cloud which means even more restrictions and privacy concerns than in the current model.
I agree that there are some reforms needed, but I'm against revolution that this document proposes.
Legalized file sharing, shorter protection times for the commercial
copyright monopoly, free sampling and a ban on DRM.
Sorry, I didn't read the document. Do those lunatics also want to ban SaaS? Because if software is in the cloud you can't easily pirate it.I strongly believe that such legislation would only complicate my life. With high-speed networks and new protocols it's not that hard to imagine companies like Adobe or Autodesk moving their products almost completely to cloud. You would no longer "own" professional software, you would only rent access to it.
[1] http://javascript.spec.whatwg.org/#object.prototype.__proto_...
I have seen various definitions of the term "clone", e.g. Io language documentation says that "a clone is an empty object that has the parent in its list of protos", this article defines clone as an exact shallow copy of another object.
Screenshot: http://i.imgur.com/oUL5U.png
[1] http://www.youtube.com/user/mohammedabshaun/videos?view=0
I'm selling the same app on both Ubuntu Software Center [1] and Mac App Store [2]. Between June and December I have sold 29 licenses on Ubuntu store and ~2000 licenses on Mac App Store.
Chrome Web Store [3] seems to be a much more promising distribution channel for Linux apps. With the new APIs it will be possible to access native window manager, USB ports, filesystem or webcam. Besides, you don't have to deal with incompatibilities between distros.
[1] https://apps.ubuntu.com/cat/applications/type-fu/
[2] https://itunes.apple.com/us/app/type-fu/id509818877?ls=1&...
Still, I'm afraid that such Newspeak-like language could be implemented only in some totalitarian dictatorship, so I hope that it won't happen any time soon...
You can launch it without installation (just unzip the archive). I think there were daily builds of Chrome as well, but I can't recall the link.
The real blocker for SVG is the lack of good authoring tools. Illustrator (used by the author of this article) apparently generates SVG files by rasterising many vector effects.
I suspect that there is a bug in WebKit that breaks bitmap rendering in certain circumstances, this would explain why some Illustrator-generated effects failed on Chrome.