libraries

Contents

• Main libraries to 'USE'
• Other Libraries
• USE(ing) LiveCode Script Libraries

Main libraries to USE

There are several USE headers that allow LCB to load various support modules (dependencies/libraries)

• use these to add their functionality
• use lines should go above other at the top of other definitions in your .lcb file

name	description
com.livecode.canvas	Provides the syntax and types for 2D drawing allowing developers to draw to a canvas. Required if creating a widget.
com.livecode.engine	Contains syntax for all extension building such as "dispatch" and "log".
com.livecode.widget	Contains syntax specific to widget building such as "my width" and "the mouse position".
com.livecode.library.widgetutils

Other libraries

name	description
com.livecode.arithmetic
com.livecode.array
com.livecode.assert
com.livecode.binary
com.livecode.bitwise
com.livecode.byte
com.livecode.char
com.livecode.codeunit
com.livecode.date
com.livecode.emscription
com.livecode.engine
com.livecode.file
com.livecode.java
com.livecode.language
com.livecode.list
com.livecode.logic
com.livecode.math
com.livecode.mathfoundation
com.livecode.obc
com.livecode.sort
com.livecode.stream
com.livecode.string
com.livecode.system
com.livecode.type
com.livecode.typeconvert
com.livecode.unittest

USE(ing) LiveCode Script Libraries

You can also USE LiveCode Script libraries and then call their functions and handlers directly...apparently (see reply to Bug 23944. In the NavBar widget, the svg library is used, but it does not appear in the dictionary. Panos said that's because it is an LCS library.

Therefore I infer that you can USE any LCS library..