Framework

Introduction

Status: 29.11.2010

This section describes the Framework prototype. Framework enfolders all files and resources that:

a.) belong to a logically group of files/resources, like the The-M-Project core or the application data.

b.) should combined to a single JavaScript file.

A Framework has three main tasks:

1. Read in the resources

2. Provide a function to save (write) its resources to the local file system.

3. Provide a function to attache its files to a Server, to deliver them.

Prototype

Read files

This is a description of the process that is responsible for reading the files and resources in a framework, during the build step. A framework is instantiated by the App, path of the files, a framework is working with, is passed during the instantiation from the app. So every new framework is aware of the path, where to look for resources. (see also: Architecture)

When called espresso build, the App calling build() on every framework. This is the call for the a framework to read-in there resources. This is done in a asynchrony way - to improve the build process. The following diagram showing the read file process: