-
Notifications
You must be signed in to change notification settings - Fork 129
README iOS (0.5.0)
LiquidCore provides an environment for developers to create native mobile micro apps in Javascript that can in turn be embedded into other apps. Think: native <iframe>
for mobile apps. A LiquidCore micro app is simply a Node.js module that can be served from the cloud, and therefore, like in a webpage, it can be modified server-side and instantly updated on all mobile devices.
The framework is distributed through Carthage.
-
Install Carthage as described here.
-
Create a Cartfile that includes the
LiquidCore
framework:git "git@github.com:LiquidPlayer/LiquidCore.git" ~> 0.5.0
-
Run
carthage update
. This will fetch dependencies into a Carthage/Checkouts folder, then build each one or download a pre-compiled framework. -
On your application targets’ General settings tab, in the “Linked Frameworks and Libraries” section, drag and drop
LiquidCore.framework
from the Carthage/Build folder on disk. -
On your application targets’ Build Phases settings tab, click the + icon and choose New Run Script Phase. Create a Run Script in which you specify your shell (ex:
/bin/sh
), add the following contents to the script area below the shell:/usr/local/bin/carthage copy-frameworks
-
Add the paths to the framework under “Input Files":
$(SRCROOT)/Carthage/Build/iOS/LiquidCore.framework
-
Add the paths to the copied framework to the “Output Files”:
$(BUILT_PRODUCTS_DIR)/$(FRAMEWORKS_FOLDER_PATH)/LiquidCore.framework
This section covers the two major intended use cases of LiquidCore, complete with Hello, World! step-by-step examples.
A micro app is built on a micro service. A micro service is nothing more than an independent Node.js instance whose startup code is referenced by a URI. For example:
import LiquidCore
...
let url = URL(string: "http://my.server.com/path/to/code.js")
let service = LCMicroService(url: url!)
service?.start()
#import <LiquidCore/LiquidCore.h>
...
NSURL *url = [NSURL URLWithString:@"http://my.server.com/path/to/code.js"];
LCMicroService *service = [[LCMicroService alloc] initWithURL:url];
[service start];
The service URI can either refer to a server URL or a local resource (NSURL *url = [[NSBundle mainBundle] URLForResource: @"somefile" withExtension:@"js"];
). LiquidCore is designed to primarily use remote URLs, as dynamic updates are an important value proposition, but local resources are supported for both debugging and/or backup (e.g. as a factory preset if the network is not available).
A micro service can communicate with the host app once the Node.js environment is set up. This can be determined by specifying an LCMicroServiceDelegate
in the LCMicroService
constructor:
let url = URL(string: "http://my.server.com/path/to/code.js")
let service = LCMicroService(url: url!, delegate:self)
service?.start()
...
func onStart(_ service: LCMicroService!, synchronizer: LCSynchronizer?) {
// .. The environment is live, but the startup JS code (from the URI)
// has not been executed yet.
}
NSURL *url = [NSURL URLWithString:@"http://my.server.com/path/to/code.js"];
LCMicroService *service = [[LCMicroService alloc] initWithURL:url delegate:self];
[service start];
...
- (void) onStart:(LCMicroService*)service synchronizer:(LCSynchronizer* _Nullable)synchronizer
{
// .. The environment is live, but the startup JS code (from the URI)
// has not been executed yet.
}
A micro service communicates with the host through a simple EventEmitter
interface, eponymously called LiquidCore
. For example, in your JavaScript startup code (code.js in this example):
LiquidCore.emit('my_event', {foo: "hello, world", bar: 5, l337 : ['a', 'b'] })
On the iOS side, the host app can listen for events through the LCMicroServiceEventListener
protocol:
// ... in the onStart:synchronizer: method:
service.addEventListener("my_event", listener: self)
...
func onEvent(_ service: LCMicroService!, event: String!, payload: Any?) {
var p = (payload as! Dictionary<String,AnyObject>)
NSLog(format:"Event: %@: %@", args:event, p["foo"]);
// logs: Event:my_event: hello, world
}
// ... in the onStart:synchronizer: method:
[service addEventListener:@"my_event" listener:self];
...
- (void) onEvent:(LCMicroService*)service event:(NSString*)event payload:(id _Nullable)payload
{
NSLog(@"Event: %@: %@", event, payload[@"foo"]);
// logs: Event:my_event: hello, world
}
Similarly, the micro service can listen for events from the host:
var payload = ["hallo" : "die Weld"]
service.emitObject("host_event", object:payload)
NSDictionary *payload = @{ @"hallo" : @"die Weld" };
[service emitObject:@"host_event" object:payload];
Then, in Javascript:
LiquidCore.on('host_event', function(msg) {
console.log('Hallo, ' + msg.hallo)
})
LiquidCore creates a convenient virtual file system so that instances of micro services do not unintentionally or maliciously interfere with each other or the rest of the iOS filesystem. The file system is described in detail here.
There are many uses for micro services. They are really useful for taking advantage of all the work that has been done by the Node community. But we want to be able to create our own native applications that do not require much, if any, interaction from the host. To achieve this, we will introduce one more term: Surface. A surface is a UI canvas for micro services.
There are two surfaces so far:
-
ConsoleSurface
. AConsoleSurface
is simply a Node.js terminal console that displays anything written toconsole.log()
andconsole.error()
. It also allows injection of Javascript commands, just like a standard Node console. TheConsoleSurface
is included in the LiquidCore framework. Run theLiquidCoreiOSTestApp
to see it in action. -
ReactNativeSurface
. You can drive native UI elements using the React Native framework from within your micro app. This is a fork of the React Native project that has modifications to allow it to run on LiquidCore. It is very experimental at this point and I haven't written any documentation yet. But it does work. Edit: This is an old build of RN and only works(ed?) on Android. I will be updating for both Android and iOS shortly.
There are other surfaces under consideration, including:
-
WebSurface
- aWebView
front-end where a micro service can write to the DOM -
CardSurface
- a limited feature set suitable for driving card-like UI elements in a list -
OpenGLSurface
- an OpenGL canvas
Eventually, we would like to have virtual/augmented reality surfaces, as well as non-graphical canvases such as chat and voice query interfaces.
(You can find all the code below in a complete example project here if you get stuck).
To use a micro service, you need two things: the micro service code, and a host app.
We will start by creating a very simple micro service, which does nothing more than send a welcome message to the host. This will be served from a machine on our network. Start by creating a working directory somewhere.
$ mkdir ~/helloworld
$ cd ~/helloworld
Then, install the LiquidCore server (aptly named LiquidServer) from npm
:
$ npm install -g liquidserver
Now let's create a micro service. Create a file in the ~/helloworld
directory called service.js
and fill it with the following contents:
/* Hello, World! Micro Service */
// A micro service will exit when it has nothing left to do. So to
// avoid a premature exit, let's set an indefinite timer. When we
// exit() later, the timer will get invalidated.
setInterval(function() {}, 1000)
// Listen for a request from the host for the 'ping' event
LiquidCore.on( 'ping', function() {
// When we get the ping from the host, respond with "Hallo, die Weld!"
// and then exit.
LiquidCore.emit( 'pong', { message: 'Hallo, die Weld!' } )
process.exit(0)
})
// Ok, we are all set up. Let the host know we are ready to talk
LiquidCore.emit( 'ready' )
Next, let's set up a manifest file. Don't worry too much about this right
now. Basically, the manifest allows us to serve different versions based
on the capabilities/permissions given by the host. But for our simple example,
we will serve the same file to any requestor. Create a file in the same
directory named service.manifest
:
{
"configs": [
{
"file": "service.js"
}
]
}
This tells LiquidServer that when a request comes in for service.js
, it should
serve our service.js
file. This may seem dumb, but there are other useful attributes
which can be set. For our purposes, though, they are not yet needed.
You can now run your server. Choose some port (say, 8080), or LiquidServer will create one for you:
$ liquidserver 8080
You should now see the message, Listening on port 8080
. Congratulations, you just
created a micro service. You can test that it is working correctly by navigating to
http://localhost:8080/service.js
in your browser. You should see the contents of
service.js
that you just created with some wrapper code around it. The wrapper is simply
to allow multiple Node.js modules to be packed into a single file. If you were to
require()
some other module, that module and its dependencies would get wrapped into this
single file.
You can leave that running or restart it later. Now we need to create a host app.
- In XCode, create a new project by selecting File->New->Project->Single View App
- Fill out the basics and press
Next
(Product Name:HelloWorld
, Organization Name:LiquidPlayer
, Language:Swift
). Leave the rest as defaults. - Select a location for it and press
Create
- Open the
ViewController.swift
file and replace the code with the following contents:
import UIKit
class ViewController: UIViewController {
var text: UILabel = UILabel()
var button: UIButton = UIButton(type: .system)
override func viewDidLoad() {
super.viewDidLoad()
text.textAlignment = .center
text.text = "Hello World!"
text.font = UIFont(name: "Menlo", size: 17)
self.view.addSubview(text)
button.setTitle("Sprechen Sie Deutsch!", for: .normal)
button.titleLabel?.font = UIFont(name: "Menlo", size: 17)
button.addTarget(self, action: #selector(onTouch), for: .touchUpInside)
self.view.addSubview(button)
self.text.translatesAutoresizingMaskIntoConstraints = false
self.button.translatesAutoresizingMaskIntoConstraints = false
let top = UILayoutGuide()
let bottom = UILayoutGuide()
self.view.addLayoutGuide(top)
self.view.addLayoutGuide(bottom)
let views = [ "text": text, "button": button, "top":top, "bottom":bottom ]
let c1 = NSLayoutConstraint.constraints(withVisualFormat: "H:|-[text]-|", metrics: nil, views: views)
let c2 = NSLayoutConstraint.constraints(withVisualFormat: "H:|-[button]-|", metrics: nil, views: views)
let c3 = NSLayoutConstraint.constraints(withVisualFormat: "V:|[top]-[text]-[button]-[bottom(==top)]|",
metrics: nil, views: views)
self.view.addConstraints(c1 + c2 + c3)
}
@objc func onTouch(sender:UIButton!) {
}
override func didReceiveMemoryWarning() {
super.didReceiveMemoryWarning()
// Dispose of any resources that can be recreated.
}
}
You now have a basic app that does very little. Go ahead and run it in your emulator. You should see a white background with a message that says "Hello World!" and a button below it that says "Sprechen Sie Deutsch". This is just a simple Hello World app. We are going to teach it to speak German by using our LiquidCore micro service.
Now it is time to connect LiquidCore. First, you must add the framework. Follow the instructions at the top of the file for this. The first time you run carthage update
, it will take a long time as it needs to clone the entire repo. But after the first time, it should be quicker. Everything should continue working the same. Once this is done, re-run your app. It should continue working as before.
Now, let's connect our button to the micro service. Edit ViewController.swift
in our app, and replace the first couple of lines with the following:
import UIKit
import LiquidCore
let serverAddr = "192.168.21.113:8080" // <-- CHANGE THIS TO YOUR SERVER'S ADDRESS!
class ViewController: UIViewController, LCMicroServiceDelegate, LCMicroServiceEventListener {
Make sure you change the internet address to the correct IP address or name on your network.
Now, replace the onTouch()
function with the following:
@objc func onTouch(sender:UIButton!) {
let url = URL(string:"http://" + serverAddr + "/service.js")
let service = LCMicroService(url: url!, delegate: self)
service?.start()
}
func onStart(_ service: LCMicroService!, synchronizer: LCSynchronizer?) {
service.addEventListener("ready", listener: self)
service.addEventListener("pong", listener: self)
}
func onEvent(_ service: LCMicroService!, event: String!, payload: Any?) {
if event == "ready" {
service.emit("ping")
} else if event == "pong" {
DispatchQueue.main.async {
var p = (payload as! Dictionary<String,AnyObject>)
self.text.text = p["message"] as? String
}
}
}
Again, make sure you change serverAddr
to your server's address. Now, restart the app and then click the button. The "Hello World" message should change to German. You have successfully connected a micro service to a host app!
To demonstrate the instant update feature, leave the app and server running. Now, edit service.js
on your server machine to respond with a different message and then save:
...
LiquidCore.emit( 'pong', { message: 'Das ist super!' } )
...
Go back to the app and press the button again. Your message should update.
That's it. That's all there is to it. Of course, this is an overly simplified example. We can do other useful things, like utilizing existing Node.js modules. To try this, create a new file named bn.js
, and fill it with the following:
var BigNumber = require('bignumber.js')
setInterval(function() {}, 1000)
LiquidCore.on( 'ping', function() {
var x = new BigNumber(1011, 2) // "11"
var y = new BigNumber('zz.9', 36) // "1295.25"
var z = x.plus(y) // "1306.25"
LiquidCore.emit( 'pong', { message: '' + x + ' + ' + y + ' = ' + z } )
process.exit(0)
})
LiquidCore.emit( 'ready' )
We will now be using the BigNumber module. Be sure to install it first:
% npm install bignumber.js
You will also need the manifest file, bn.manifest
in the same directory:
{
"configs": [
{
"file": "bn.js"
}
]
}
Now navigate to http://localhost:8080/bn.js
in your browser and you should now see that the bignumber.js
module has also been wrapped.
In your Hallo, die Weld app, change the following line:
let url = URL(string:"http://" + serverAddr + "/service.js")
to:
let url = URL(string:"http://" + serverAddr + "/bn.js")
Then restart the app. You should now see an equation that utilized the module when you click the button.
Ok, one last little trick. Let's modify the bn.manifest
file to include a transform. Replace with this:
{
"configs": [
{
"file": "bn.js",
"transforms": [ "uglifyify" ]
}
]
}
You will need to clear the server cache, so simply delete the .lib
directory:
% rm -rf ~/helloworld/.lib
And then restart the server. Now when you navigate to http://localhost:8080/bn.js
, you will see that the code has been minified in order to save space. The manifest file can do a bunch of things, but we'll save that for later as it is still in its infancy.
If you are interested in building the library directly and possibly contributing, you must do the following:
% git clone https://github.com/liquidplayer/LiquidCore.git
% cd LiquidCore/LiquidCoreiOS
% carthage build --no-skip-current
Your framework now sits in LiquidCoreiOS/Build/iOS/LiquidCore.framework
. You can also build it inside of XCode without issue.
Copyright (c) 2014-2018 Eric Lange. All rights reserved.
Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:
-
Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.
-
Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.