As someone who creates a lot of personal plugins integrating, various 3rd party frameworks, I though I'd share a tip. You will find that when you are buying or creating plugins that a lot of people are integrating different frameworks that aren't in the initial Buzztouch package. For example ATRAINS Tweetsheet utilises the twitter.framework. The Aurasma plugin I've developed is linked to no less than 23 frameworks. But what does this mean. When you compile your source code Buzztouch includes every plugin in your control panel even if you haven't created a screen with it. Thus when you try and compile you will get dozens of linker errors. Now not every app requires aurasma, twitter, store kit, revmobs, gamecenter etc. (to list but a few) To avoid these errors I only ever include the plugins I require. I do this by: 1. follow the instructions and drag the plugins folder into Xcode 2. Highlight and remove each plugin that isn't required, by right clicking, pressing delete, choose remove references. This will remove the offending plugins. The reason we remove references only is so we can add the plugins back in if we decide to add more screens. I do this by right clicking on the BT_plugins folder, press show in finder, drag the plugin back into xcode. Hopefully this has made a little bit of sense. We will find over the coming months with the plugin market, that this will be causing the majority of the errors. *******Remember if you are using a buzztouch developers plugin make sure you follow all of the instructions before ranting on the forum.******

Yep I agree.. I was thinking yesterday as well if there was an option in the control panels to only download or choose from only live or used plugins. but of course later i realized if you want to add features or new plugins in a live app it wouldnt work. I guess if you are 100% sure that you will not use a plugin in the future of the app that is live, deleting it is the best option. Its a fine line :) But i agree with the above comment! Read instructions thoroughly befor ranting hehe

To be honest you would know whether you needed the aurasma or gamecenter before you started. With the twitter one it's only one framework. Some of the plugins I've designed use a lot of frameworks. To be honest if you were adding aurasma, I think a proper app store update is the way to go to advertise your cool new feature, instead of a back door boogie.

yeah no back door boogie in a bad way, of course app store updates are very important for the end user and of course as a developer. however it could be a scenario for some folks..

well if that's the case prepare to install 50 different frameworks, every time you download the source code, it would be good if there was a faster way.

Good tip, exactly how I handle them as well. Very curious to see how developers deal with support with some of these newer plugins, esp the ones that use 3rd party SDK's and require some very specific project settings. I use a lot of them, but the idea of walking non coders thru some of those steps is not very appealing. I mess up enough of my own projects testing these things. I've been lobbying to have some standard text set for plug-ins that ue them. Something like 'this was tested and works in this enviroment. If you are trying to install in a different enviroment, please note it has not been fully tested and may not be supported' I also always suggest backing up the project and storing a clean zip away before trying to integrate a new SDK in a project. Frameworks are pretty benign, but nice to have an UNDO. One other framework tip - you can set it as OPTIONAL. That helps if you want to keep the framework in your project, but build for devices that might not support it. LOL @ the rant, people never RTFM until they run into problems..... time for football, enjoy the weekend and keep coding kittsy!

Hello Everyone, That's a great tip! In Eclipse, when developing a new plugin, can users delete other java screens and xmls that are not related to the plugin? LA

That is interesting! I was wondering why I had stray files and errors appearing from plugins I had bought, but had not used. Top tip!

Great tip. I agree with LA - someone should make a how-to for removing unnecessary Android plugins :)

Yeah I've not really mastered android yet

who has..lol