原文:https://www.infinum.co/the-capsized-eight/articles/running-javascript-in-an-ios-application-with-javascriptcore

Although the JavaScriptCore framework has been officially available to iOS and Mac developers for quite some time now, its features are still documented rather poorly. Also, Apple provides no guidelines, save for a great WWDC session named "Integrating JavaScript into Native Apps".

However, while waiting for them to update the documentation, there's no reason not to take advantage of the framework's capabilities - it is, as will be demonstrated in this blog post, fairly easy to use.

Where to begin?

There are three object types we will use to provide a quick example of what you can do with JavaScriptCore. These are:

  • JSVirtualMachine
  • JSContext
  • JSValue


Keep in mind that the number of virtual machines is not limited by the number of ARM cores

JSVirtualMachine represents a JavaScript virtual machine, which manages memory and garbage collection. An arbitrary number of these objects can be instantiated in order to execute JavaScript code in parallel - each of them uses a separate thread.

JSContext sounds a bit trickier to decipher, but rest assured it makes sense. For JavaScript code to be executed, it needs to have a context, a space where it can create new variables and access existing ones. So, a JSContext is a code evaluation context, and you can have multiple contexts in a single virtual machine. You can also exchange information between contexts in the same virtual machine, but not between virtual machines.

JSValue is a class representing any type of data in a JavaScript context. You can have as manyJSValues as you want in a context and you can pass them between different contexts as long as those contexts belong to the same virtual machine.

How to use it?

To execute JavaScript code, we need to have a virtual machine and context. And here's how we can create a JavaScript context:

JSContext *context = [[JSContext alloc] initWithVirtualMachine:[[JSVirtualMachine alloc] init]];

One thing worth mentioning is that the context is empty when we create it. It contains no variables or functions. There's more than one way to create variables in a context or assign values to them. Let's show the simplest one, literal assignment:

context[@"aNumber"] = @;
NSLog(@"%d", [context[@"aNumber"] toInt32]);

The console outputs 22.
Of course, we can also assign JSValues, NSNumbers and so on. But this example reveals an important detail: it's simple to access values within a context using the subscripting operator. We can also access values which were created or set by JavaScript code evaluated in the context. For example:

[context evaluateScript:@"var anotherNumber = aNumber + 20;"];
NSLog(@"%d", [context[@"anotherNumber"] toInt32]);

The console outputs 42.
Here we see how JavaScript code can be executed within the context. The aNumber variable which we created earlier is also available to the JavaScript code. However, if we were to store it in a JSValue, the JSValue would only contain its current value, and not a reference to the variable in the JavaScript context. In other words, it wouldn't change when the variable within the context changes, nor would the JavaScript variable change when the JSValue is changed.

Functions can also be JSValues. We can make use of that to expose an Objective-C block to a JavaScript context. For example, JavaScript's console.log() is not bridged automatically to the Xcode console. Here's how we can enable logging:

[context evaluateScript:@"var console = {};"]; // make console an empty object
context[@"console"][@"log"] = ^(NSString *message) {
NSLog(@"%@", message);
};

If we then write [context evaluateScript:@"console.log(anotherNumber)"];, the console will output42, as expected. This example shows how to use two-level subscripting to create properties that can be accessed from JavaScript via dot notation. It also shows how an Objective-C block can be assigned to a variable in a JavaScript context and how it can be called from within the context. The block can, of course, return a value and have an arbitrary number of arguments.

But it can go the other way around, too! It's possible to call a JavaScript function from Objective-C:

[context evaluateScript:@"var add = function(a, b) {return a + b;}"];
NSLog(@"%@", [context[@"add"] callWithArguments:@[@, @]]);
NSLog(@"%@", [context[@"add"] callWithArguments:@[context[@"aNumber"], context[@"anotherNumber"]]]);

The console will output 50 and 64, as expected. Now let's spice things up a bit with a more complicated function that still serves the same purpose:

[context evaluateScript:@"var addAndPrint = function(a, b) {console.log(add(a, b));}"];
[context[@"addAndPrint"] callWithArguments:@[@, @]];
[context[@"addAndPrint"] callWithArguments:@[context[@"aNumber"], context[@"anotherNumber"]]];

The console output is the same as it was in the previous example. The addAndPrint() function uses the previously declared add() function as well as console.log() which maps to an Objective-C block.

What next?

Thus far we have managed to create variables in the JavaScript context, assign values to them and call JavaScript functions and Objective-C blocks back and forth. While this is powerful by itself, there is more to JavaScriptCore.

A good example of what's possible is the JSExport protocol. If a class implements it, all of its properties and methods can be used in JavaScript contexts. Protocol inheritance makes it possible to exclude unwanted properties or methods from this behavior.

This feature is awesome because it allows you to assign an object to a JSValue and expose all or a part of its properties and methods to JavaScript. It also bypasses the aforementioned limitation of JSValue regarding changes to a JSValue on Objective-C side not propagating to the respective JavaScript variable and vice-versa.

Using the JSExport protocol, it's possible to have a reference to a mutable object both from Objective-C and JavaScript execution environments. The bridge between the two is implemented by JavaScript Core, so that each change to the object made in one execution environment gets copied immediately to the other one.

To explore this and other features and learn more about JavaScriptCore in general, refer to the WWDC session number 615, which targets this topic specifically.

If you decide to use the framework in a project, your JavaScript developers will probably want to know what they're working with. To avoid confusion, here's what JavaScriptCore's developers say about the project:

JavaScriptCore is the built-in JavaScript engine for WebKit. (...) JavaScriptCore is often referred with different names, such as SquirrelFish and SquirrelFish Extreme. Within the context of Safari, Nitro and Nitro Extreme (the marketing terms from Apple) are also commonly used. However, the name of the project and the library is always JavaScriptCore.

You should also note that the framework comes with a caveat: JIT compilation is not supported, although it isn't ruled out for future releases, either.

Why do it?

Apart from executing JavaScript code in native iOS applications being interesting and cool, I think it can be useful as well. Apple's example from the WWDC session suggests extending the application's functionality by using "modules" or "plug-ins" written in JavaScript.

To demonstrate the idea, they developed a simple syntax highlighting tool and a set of JS plug-ins that implemented the actual syntax highlighting logic for each programming language. Using this approach, they were able to support new languages just by loading additional plug-ins.

I believe a similar model could also be used to provide extensibility in applications that accomplish tasks using the same basic function set. Who knows, soon we may even see a simple JavaScript IDE as an iOS application.

[转]Running JavaScript in an iOS application with JavaScriptCore的更多相关文章

  1. iOS Application Security

    文章分A,B,C,D 4个部分. A) iOS Application Security 下面介绍iOS应用安全,如何分析和动态修改app. 1)iOS Application security Pa ...

  2. IOS Application Security Testing Cheat Sheet

    IOS Application Security Testing Cheat Sheet    [hide]  1 DRAFT CHEAT SHEET - WORK IN PROGRESS 2 Int ...

  3. JSPatch 可以让你用 JavaScript 书写原生 iOS APP

    简介   JSPatch 可以让你用 JavaScript 书写原生 iOS APP.只需在项目引入极小的引擎,就可以使用 JavaScript 调用任何 Objective-C 的原生接口,获得脚本 ...

  4. iOS Application Project与OS X Application Project对于plist使用的区别

    前几天因为在开源中国看到一个求源代码的问题: 模拟一个动物园系统MyZoo 1.动物园里面有三种动物:Panda,Elephant,Kangaroo 2.三种动物都有一定的数量(不止一只) 3.动物有 ...

  5. Persisting iOS Application Data in SQLite Database Using FMDB

    In previous articles we have utilized NSUserDefaults and .NET web services to persist iPhone data. N ...

  6. Attacking JavaScript Engines: A case study of JavaScriptCore and CVE-2016-4622(转)

    转:http://phrack.org/papers/attacking_javascript_engines.html Title : Attacking JavaScript Engines: A ...

  7. iOS Application Life Cycle 应用程序生命周期

    应用程序的状态 IOS的应用程序一共有5种状态. Not running(未运行):程序未启动 Inactive(未激活):其他两个状态切换时出现的短暂状态.唯一在此状态停留时间比较长的情况是:当用户 ...

  8. Demystifying iOS Application Crash Logs

    http://www.raywenderlich.com/23704/demystifying-ios-application-crash-logs This is a blog post by So ...

  9. iOS application/json上传文件等

    在和sever后台交互的过程中.有时候.他们需要我们iOS开发者以“application/json”形式上传. NSString *accessUrl = [NSString stringWithF ...

随机推荐

  1. web 安全的前期准备哦

    学习web安全  需要的软件  和 基础 基础会在以后发出来  软件  在网上都可以下 首先   你要有一款虚拟机软件 虚拟系统通过生成现有操作系统的全新虚拟镜像,它具有真实windows系统完全一样 ...

  2. Ubuntu下很给力的下载工具

    Windows下的下载工具--迅雷,之所下面载速度快,乃是它能搜索资源.为己所用,而不是只从原始地址这单一资源处下载. Ubuntu下也有类似的工具,那就是aira2. aira2是一个命令行下载工具 ...

  3. Java Tomcat Glassfish Weblogic远程debug(remote debug)

    tomcat ./catalina.sh jpda start 这条命令启动tomcat,它就会监听8000端口,等待调试器的连接. 默认监听8000端口,通过设置环境变量JPDA_ADDRESS指定 ...

  4. Nginx 之六: Nginx服务器的反向代理功能

    一:Nginx作为正向代理服务器: 1.正向代理:代理(proxy)服务也可以称为是正向代理,指的是将服务器部署在公司的网关,代理公司内部员工上外网的请求,可以起到一定的安全作用和管理限制作用,正向代 ...

  5. HTTP必知必会(转)

    HTTP协议作为网络传输的基本协议,有着广泛的应用.HTTP协议的完整内容很多,但是其核心知识却又简单精炼.学习者应该掌握其基本结构,并且能够举一反三.这篇文章所列的,就是在实际开发中必须知道必须掌握 ...

  6. 织梦CMS提示DedeTag Engine Create File False错误的解决办法总结

    今天帮客户升级站点,遇到了一个老问题,生成栏目的时候提示"DedeTag Engine Create File False",突然发觉这个问题竟然在以前做站的时候困扰过我多次,于是 ...

  7. hibernate框架学习笔记2:配置文件详解

    实体类: package domain; public class Customer { private Long cust_id; private String cust_name; private ...

  8. AngularJs 服务 广播

    1, angularJs的服务有provider,Service, Factory. Factory是对Service的封装,Service是对Provider的封装. Provide的源码如下: f ...

  9. import导入模块,==和is,浅拷贝和深拷贝,进制转换,位运算,私有化,property装饰器

    '''import导入模块'''import sysprint(sys.path) sys.path.append('D://ASoft/Python/PycharmProjects')import ...

  10. Hibernate(9)_双向n对n

    1.概述 ①双向 n-n 关联需要两端都使用集合属性 ②双向n-n关联必须使用连接表 ③集合属性应增加 key 子元素用以映射外键列, 集合元素里还应增加many-to-many子元素关联实体类 ④在 ...