Hi, I just came across this post by Adam on implementing a new API as - what he calls - a "Blink Module":
https://groups.google.com/a/chromium.org/d/msg/blink-dev/R5yYtHEPiw4/-eVaKo6unq4J "[...] Currently we use two different technology stacks to implement JavaScript API, one in for web-facing APIs in Blink and another for Apps/Extensions facing APIs in Chromium. In the past, this division has made it more difficult to standardize Apps APIs because switching from from an Apps API to a Web API involves rewriting the API using a different technology rather than that simply evolving the implementation. For example, Apps APIs cannot contain any EventTargets because the technology we use to implement Extension APIs can't subclass EventTarget. For NetInfo, I thought we might try a bit of an experiment and try implementing an Apps-facing API in as a Blink module. That would let us implement the API using the same technology we use to implement Web-facing APIs, which will hopefully smooth the transition to the standards track. [...]" Did anyone else see this? Does this approach affect how we implement extensions in the future? Could it be useful for us the use the "Blink module" approach - without having looked into it in detail myself. Dominik _______________________________________________ Crosswalk-dev mailing list Crosswalk-dev@lists.crosswalk-project.org https://lists.crosswalk-project.org/mailman/listinfo/crosswalk-dev
