Code Repository for the Siva Siva Mobile App
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Permalink
Failed to load latest commit information.
assets updated release notes; turned off blinking audio stop icon in settings Jul 19, 2017
behaviors finalized journal Look and feel, fixed audio resume, added audio stop… Jul 19, 2017
controllers
libraries
models many updates to get Surprise to work with sharing Jul 16, 2017
modules small update to settings Jul 19, 2017
source/zResources merging: solving conflicts Dec 7, 2016
splash screens - app icons Splash screens added to respository, but not to the stack files in th… Mar 25, 2017
stacks updates to stack to ensure no crashing on navigation Mar 7, 2017
views finalized journal Look and feel, fixed audio resume, added audio stop… Jul 19, 2017
.gitignore Deleted duplicate set of alpha images; updates everywhere in stack; k… May 1, 2017
CHANGELOG.md Removed documents folder and creates instead several models. Oct 14, 2016
DECISIONS.md
README.md
Siva-Siva-App-broken.livecode updated compositor setting in init. Apr 2, 2017
Siva-Siva-App.json implemented share on all modules navigation bar Jul 10, 2017
Siva-Siva-App.livecode updated release notes; turned off blinking audio stop icon in settings Jul 19, 2017
Siva-Siva-Portal.livecode
ideads.txt updates to encompass now settings info-display control Jun 14, 2017

README.md

Siva-Siva-App

Code Repository for the Siva Siva Mobile App

File Structure

The code lives inside the source folder. A shared folder hosts both libraries and shared assets. Modules live in their own folder inside the modules folder.

Configuration for the app (config.json)

This JSON file holds the configuration for the app itself. Individual modules may host their own configuration JSON as well.

The most important items in this file are:

  • The autoload array which lists which libraries to load at the start of the app.
  • The launch module item which specifies which module should be considered the home module.

API

The loader stack provides a backscript for the API to be shared between modules, this exists inside a button called API backscript. Libraries also share their code on the message path for other modules to use but the core routines are a part of this backscript.

Working Back Ups

add this to the preopenstack handler of any module: backupStack to create incremental backups of your work stack every 15 minutes. be sure .gitignore includes ".bac"