m00sey

Loading plugins from the AndroidManifest.xml As an alternative to registering plugins through JavaScript plugins can now be loaded via the AndroidManifest, using the meta-data element.

A demo can be found at https://github.com/m00sey/Toasty (you'll need to update the jar to 9.6.1)

Registering a plugin

Plugin names are prefixed with plugin. this is so the keys can be identified when loading the meta data. The value is the fully qualified name.

m00sey

-Dee.executable=${ee.home}/simulator/fledge 
-Dee.bootclasspath=${ee.home}/lib/net_rim_api.jar 
-Dee.javadoc=file:${ee.home}/docs/api

m00sey

package com.yourpackage;

import org.json.JSONArray;

import com.phonegap.api.Plugin;
import com.phonegap.api.PluginResult;


public class ToastPlugin extends Plugin {

m00sey

;Exercise 1.5.
;Ben Bitdiddle has invented a test to determine whether the interpreter he is faced with is using
; applicative-order evaluation or normal-order evaluation. He defines the following two procedures:
;(define (p) (p))
;
;(define (test x y)
;  (if (= x 0)
;      0
;      y))
;