====================
  MULTIPACK README
====================

This sample illustrates how to include multiple versions of an application in a single package, choosing which version to launch at runtime based on the environment in which the app is running.

(Note that the technique illustrated here applies only to applications of type: "web", not to standalone PDK apps.)

This technique is useful primarily for packaging a legacy Mojo version of your app along with a new Enyo version, such that the Mojo version runs on webOS 2 and earlier and the Enyo version runs on webOS 3 and later. Doing so enables you to support both webOS 3 and earlier versions of webOS with a single entry in the App Catalog.

You might also extend or adapt this technique for other purposes -- for example, to include separate Mojo versions targeting webOS 1.x and 2.x.

If you don't have an existing Mojo app and don't need to support webOS 2 or earlier, you can skip this sample and start from one of the basic Enyo templates to build an app targeting webOS 3 and later.


The structure of this sample may be a bit confusing, since the technique requires the files for both versions of the app to exist in the same directory. The files and directories in the sample break down as follows:


---------------------
    SHARED FILES
---------------------

appinfo.json
index.html (as defined in appinfo.json)
icon.png (as defined in appinfo.json)


---------------------
     ENYO FILES
---------------------

enyo.html (as defined in index.html)
depends.json
enyo/ (as defined in depends.json)


---------------------
     MOJO FILES
---------------------

mojo.html (as defined in index.html)
sources.json
framework_config.json
app/
images/
stylesheets/


The Mojo files and directories in this example have been kept in their default locations, so it should be simle to apply this technique to your existing project if you have used the Mojo defaults.

However, you actually have quite a bit of flexibility to reorganize your files as needed, since you can define specific paths to most of your project's assets (using appinfo.json for shared assets, depends.json for Enyo assets, and sources.json for Mojo assets).