I've read all the how to's (Thanks Mark!) and made a little test app that actually runs on a emulator. But all the docs I read jump over the fact that we need to make changes and then re-compile/refresh/whatever... and skip straight to making release packages and publishing to Google Play etc. What happened to debugging, making changes, re-testing etc.? e.g. I tried to change a label on a menu and can't for the life of me understand why it doesn't change in the emulator. I would like to know what the process is for making changes - i.e. for what changes do I need to update the BT panel, publish, download+extract etc. and when I can make simple changes to the files in Eclipse, and what is the process for that? Also, do I need to delete the emulator and exit Eclipse every time I make a little change? A step by step process for both little changes and big changes would be appreciated.

When creating your project for testing (whether Android or iOS), the environment (xcode, eclipse) will create a temporary folder with all of your app information. It will then compile that information and place it on your device. Sometimes, those cached resources will still be used, whether you want them to or not. Often I will 'clean' my project. This is the process in which the environment will go through it's cache and remove any recent project related cache files, thus 'cleaning' your trials. You can 'clean' your project from the menus. under the project menu in xcode, product menu in eclipse (or the other way around… it's in the menu somewhere…) Another thing I do from time to time is REMOVE the app from my device or simulator. A Fresh reinstall of your app is another good way to remove any unwanted ghost resources. In Android, just 'quit' the simulator, and it will start fresh the next round. In iOS, you remove an app the same was as on the device. Cheers! -- Smug

That helps a bit :) Pls explain: 1) how to do a "fresh reinstall" as mentioned above? i.e. Do I need to shut everything down, exit Eclipse, and start all over? Sorry if this sounds dumb but Eclipse and the Emulator take forever to reload and I assume there has to be a quick way to re-iterate coding/testing, no? 2) How to "Quit the Simulator"? Do I close the window or is there some button to push?

...also how to "Remove the app"? Thanks, Peter

In Android, you remove the app from your device by going into your 'settings' and selecting 'application manager'. When you select the application, you have the option to uninstall. In iOS, you press and hold on the icon for a few seconds, until it starts dancing. Then click on the 'x' that becomes visible. When I say 'fresh install' it is because you've removed the app from the device/simulator, and as far as the device is concerned, it's a brand new installation of a new app. Not an update or re-install over existing stuff. "Quitting the simulator" would depend on your environment. I'm using a Mac, so I just quit using the "command-q" shortcut. On either platform though, there should be a menu choice to quit the application. hope this helps, but let me know if I missed something! Cheers! -- Smug

Ahh woot! Removing the app from the phone (in settings/app settings/app mgr) made all the difference. Now when I clicked "run" in Eclipse it loaded the app fresh and the changes I made in Eclipse now appear, and I could keep the emulator device running throughout. I think this was the missing link and is a key tidbit that is missing in the docs and videos. Thanks again, Peter

Not sure if you're on Mac or PC, but in either case, the solution will be more RAM. I recently upgraded my Mac from 4GB to 16GB, and most applications, and specifically my Android simulator, is showing a respectable increase in speed. I used to go make a pot of coffee when I was waiting on the simulator to get going. Now I only have time to pour a cup ;) Cheers! -- Smug

[dup]

I have 6gb RAM w/ over 2Gb free. I turned down the RAM/SD card settings for the emulator to 10Mb and that helps a bit.

@pdog, looks like Smug got you sorted, he's pretty good at that! I have just been working on developing some handy tips for newbies like me so take a look at this as a reference for next time. https://www.dropbox.com/s/sggxk3897ghxx07/Android_PublishOrCompile.pdf @Smug, can you take a look and check it's right! Thanks. Paul

Paul, That's so cool! Honestly, I kind of liked it in BT 2.1.8 where you didn't have a choice of plugins; you got them all. A bit more weight, but far simpler on most folks. I tend to add as many plugins as I have anyway, because you never know when you'll want a change in your app, that the plugin you didn't compile is the very plugin you need the most, lol! Nice work! Cheers! -- Smug Edit: If you 'edit' a post, the URL goes out the window. It retains the 'built in' link it creates on the post. So when you do, you'll have to edit the URL to bring it back to 'normal' before you 'submit' again. It's annoying, but you get used to it. Just try not to edit a post with multiple links, lol! :) 2nd Edit: Ha! And While I was editing this, you were editing that. Lol! :)

Good stuff - nice flowchart. My only comment (from noob p.o.v.) is that when you say "Provided your ‘refresh’, ‘caching’,etc settings are set correctly, the changes will be pushed to the App. " this will just beg the question: "What are the settings and where do we do this?"... Thanks, Peter

@pdog, sorry for the confusion, I best edit that bit out! Mostly, changes made in BT will filter through to App using Publish. At the time I was mainly thinking in regards to html type screens and how they react to each page's 'Behaviour' settings in relation to the Apps focus of being online or offline. eg. If you create a custom html page and do not change any of the Behaviour settings, all will be ok UNTILL you have no data service (wifi etc) and inadvertently hit the left button and select the 'reload page' function! Your cached file will be lost and you wont be able to view it again until you have data service again whereas if you set the 'Show Refresh Button' to No you will stop the risk of dumping cached file. Working on a 'tips about page behaviours' shortly! Paul

I'll get this up in the How To's page today! Say the other trick that is important is to put the "Live" version of the JSON into your BT_config.txt file the last thing before publishing your app. Then keep the design version on your testing device.