levure

Levure Application Framework

Levure is an application development framework for LiveCode. The primary goals of Levure are the following:

1. Lightweight. The framework has a minimal amount of code for loading, managing, and packaging your application. Common functionality is added via helper components.
2. Provide common features such as preferences, logging, and undo management.
3. Easily extensible. Helpers all developers to develop features as helpers which can easily be added to any application.
4. Easy to organize. Levure applications are organized using the file system. Easily browser your app structure and add files.
5. Designed for use with version control systems. Wherever possible configuration and scripts are text files. While developers can take advantage of the efficiency of binary stack files for the UI, almost all of the scripts should be stored in script only stack files and assigned as behaviors.

Screencasts

You will find screencasts about Levure on Trevor DeVore's YouTube channel.

Learn How To Use Levure

Visit the Levure Wiki to get started.

How To Help

Want to help this project? There are a number of ways to contribute.

• Review the wiki and submit improvements.
• Need to decide how errors should be reported when loading helpers. Should a developer throw an error or use some other mechanism? Ideally the application should report the error to the end user and then quit. We don't want the application hanging around if an error occurs on loading.
• Create module for iOS prefs that uses NSUserDefaults.
• Move preferences external for OS X into a module.
• Create a helper component for the MAS (security-scoped bookmarks and licensing).
  • secscopGetBookmarkFromURL(pUTF8Filename) to generate bookmark data for a filename
  • secscopInitializeURLFromBookmarkData(pBookmarkData) to generate security scoped filenames using bookmark data
  • secscopStopUsingURL(pSecurityScopedFilename) to release a security scoped filename.
• Help with an auto update helper component
  • Needs module wrapped around WinSparkle: https://winsparkle.org
  • Needs module wrapped around latest Sparkle: https://sparkle-project.org
• Wrap YAML C++ library in module for full YAML support.

Known Issues

• If you use scripts for all behaviors then you have to manually construct behaviors with behaviors when a stack opens. A script only stack can't have a behavior property assigned to it. This is not an issue for behaviors loaded through the behaviors key in app.yml as the LoadBehavior message is dispatched to each stack and it can set its own behavior. For behaviors that are part of your ui components you need to make sure that you assign the parent behavior somewhere else (e.g. in a preopenstack message or in the InitializeApplicaiton message).