Using DropBox for Faster Mobile Development
mikedoub at gmail.com
Fri Feb 17 18:35:47 CST 2012
Ah Ha!! I found a non printable character in the url that is being pulled out of the first line of the file.
On 02/17/2012, at 6:50 PM, Scott Rossi wrote:
> I would be surprised if you could get this to work as DropBox states
> specifically that you cannot link to folders in your Public folder:
> "While you can't link to folders in your Public folder, you can link to
> files within sub-folders"
> That said, you could generate a simple text file in your Public folder with
> a list of your available files, and read from that. It's a bit manual, but
> you could automate the process in your LiveCode development.
> Scott Rossi
> Creative Director
> Tactile Media, UX Design
> Recently, Michael Doub wrote:
>> I am trying to take your concept and make it a bit more generic but I feel
>> like I must be in the Friday blues.
>> I am stuck on syntax or I am loosing my mind. Probably the latter. ;-)
>> Rather than go to the stack directly I wanted to pick up the url from the
>> first line of a text file so it is
>> easy to switch stacks. Sounds easy enough but its is not working! The
>> correct URL is in fact in the StacktoLoad variable.
>> What am I missing in the syntax?
>> on mouseUp
>> put URL "http://dl.dropbox.com/u/4379494/LiveCode/LoadLinks" into list
>> put line 1 of list into StacktoLoad
>> go URL StacktoLoad
>> end mouseUp
>> -= Mike
>> On 02/11/2012, at 8:32 PM, Scott Rossi wrote:
>>> This may already be old news, but I thought I'd throw it out there in case
>>> this helps someone... If you're already using your DropBox account to help
>>> speed up your mobile development process, read no farther.
>>> I've been developing stacks for iOS use on and off over the last year, and
>>> have been annoyed with the bottleneck process of building standalones,
>>> uploading them to the device, launching the test app on the device, finding
>>> everything that doesn't work, and then starting the whole process over every
>>> time I make a change. Even using the simulator just takes too long and is
>>> sometimes inaccurate compared to running on a real device. So I wondered if
>>> I could save some time using LC's "go url xyz..." ability to access a stack
>>> remotely with DropBox. And it actually works perfectly.
>>> First I loaded my dev stack to my Public DropBox folder, and right-clicked
>>> on the stack to get its DropBox address.
>>> Then I built a simple mobile standalone that contains a single button with
>>> the script:
>>> go url "http://dl.dropbox.com/path_to_my_stack.livecode"
>>> After uploading the simple standalone *one time* to my mobile device, I
>>> launch the simple standalone, press the button, and my dev stack appears on
>>> my device within a couple of seconds. With the original stack open on my
>>> desktop system (saved in DropBox), I save any changes, relaunch the simple
>>> standalone on the mobile device, and press the button to immediately see my
>>> changes. No uploading or file transfers are needed. I do this for all the
>>> mobile devices I want to test on -- as soon as I save the dev stack in my
>>> DropBox, all my testing devices have immediate access to it.
>>> I haven't tried this on Android yet, but I assume it will wok the same.
>>> This process has saved me a significant amount of time and sanity -- maybe
>>> it will for you.
>>> Scott Rossi
>>> Creative Director
>>> Tactile Media, UX Design
>>> use-livecode mailing list
>>> use-livecode at lists.runrev.com
>>> Please visit this url to subscribe, unsubscribe and manage your subscription
>> use-livecode mailing list
>> use-livecode at lists.runrev.com
>> Please visit this url to subscribe, unsubscribe and manage your subscription
> use-livecode mailing list
> use-livecode at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
More information about the use-livecode