Book Image

LiveCode Mobile Development Beginner's Guide

By : Colin Holgate
Book Image

LiveCode Mobile Development Beginner's Guide

By: Colin Holgate

Overview of this book

LiveCode is a tool for developing mobile apps designed for those who don't want to use Objective-C, C++ or Java. Although it is a tool full of rich features to create apps it can be challenging to get beyond the basics and build interactive and fun apps. Using this book, you can develop various apps and this book guides you through "till you upload the apps in the appstore."LiveCode Mobile Development Beginner's Guide" will explain how to create applications with the easiest, most practical cross platform framework available, Livecode Mobile and upload the apps to the appstore with minimal effort.Throughout the book, you'll learn details that will help you become a pro at mobile app development using LiveCode. You begin with simple calculator application and quickly enhance it using LiveCode Mobile. Start by learning the interface controls for videos and images of LiveCode's environment. Dig into configuring devices, building user interfaces, and making rich media applications, then finish by uploading the mobile applications to App Stores. You will learn how to build apps for devices such as iPhone, Android with the recently developed LiveCode Mobile through sample applications of increasing complexity.
Table of Contents (16 chapters)
LiveCode Mobile Development Beginner's Guide
Credits
About the Author
About the Reviewers
www.PacktPub.com
Preface
Index

Time for action – making a links extraction function


Sometimes it's handy to create tests in a separate stack, and then to copy the function you've made into your application stack.

  1. Create a new Mainstack. Save it, just to be safe!

  2. Add a couple of fields and a button.

  3. Set the button's script to this:

    on mouseUp
       put url "http://www.runrev.com/" into field 1
       put getLinks(field 1) into field 2
    end mouseUp
  4. Edit the stack script, and create a function for getLinks. Start with it just returning what it's sent:

    function getLinks pPageSource
       return pPageSource
    end getLinks
  5. If you were to try clicking on the button at this point, you will see that the whole page source appears in field 2.

  6. We're going to use the filter function, and that needs the text to be in separate lines. So we want each link to be in a line of its own. The replace function can do that nicely. Add these two lines to the script (before the return line, of course!):

       replace "/a>" with "/a>" & return in pPageSource...