So, I have literally been up all night trying to setup eclipse on my osx10.6 machine. The ios xcode setup took me all of 10 minutes and that included the download... I have done the install of the android sdk, eclipse, the google apis and the android dev tools literally 7 times... when I create a new project (using a buzztouch server2.0 folder), using the google api 2.2... I get 520 errors... the fist 100 (what I can see) say: R cannot be resolved to a variable BT_act_controller.java I ask someone to please have mercy on me before I...#@#$#@ This is complete torture... Thank you in advance, GM

See if this helps: http://stackoverflow.com/questions/885009/r-cannot-be-resolved-android-error

https://myskylla.wordpress.com/2012/01/03/got-milk-is-eclipse-setup-correctly-got-sdk-adt-platform-tools/ This should help to determine if eclipse & related is installed, so you don't need to reinstall several times.

Wow! You were able to download the 1Gb+ Xcode+SDK file and install it in less than 10 minutes?! Amazing! You must have a blazingly fast Internet connection! Another doc to help you out : http://www.buzztouch.com/resources/Setting_Up_Your_Android_Development_Environment_v1.2.pdf Mark

Thanks guys: Fred: I been then there done that... but thanks... Raveyd: Do you know if this is normal for a downloaded buzztouch server app? I am really trying to wrap my head around this... My assumption (which may be flawed) is that importing a buzztouchserver android app into eclipse should be an objective (black/white) matter... I can understand cross platform and device compatibility issues... but I cannot even get out of the gate... and to add to the matter... I am on a sleep strike until I get his figured out... : 0 ) Please help free me...? Thanks, GM

Hi GM, Yeah, it should be a more or less black/white matter. So long as you have the correct Google APIs installed, and there are no issues with your downloaded code, then it should pretty much just work. You will see at least 100 warnings, but there should be no errors. Have you checked out this doc? http://www.buzztouch.com/resources/Compiling_Your_Android_Application_v1.0.pdf I would also consider downloading the source again, and trying one more time with new code. Sometimes that fixes things. Mark

So, I created a blank project in buzztouch server, added an icon. downloaded the files... and opened up a new project using the 2.2 google apis and got 136 errors... Id venture to say that my eclipe setup must be the culprit... Anyone have experience setting up eclipse for buzztouch on a mac?

Also check out the readme and instructions files in your eclipse project download for some setup and debugging advise. The .pdf Mark (GoNorthWest) linked to is very helpful for properly setting up your eclipse environment. Be sure to go through that too. There are also some more guides at: http://www.buzztouch.com/resources/

@ muhromatic - re: Raveyd: Do you know if this is normal for a downloaded buzztouch server app? It seems to be a fairly common occurence for any app project loaded into a fully updated eclipse environment. It sometimes adds generic 'r' imports to the java files in a project even if there are specific equivalent project imports. Never used a mac, but I guess it's going to be the same issue. I get this problem all the time with non-bt open source code that's slightly out of date. It's usually a simple matter of removing the offending imports, saving the files, doing Project > Clean and following any quick fix recommendations (red squiggle under code - mouse over and choose the quick fix). Also, you have two ways to get a project into eclipse. File > Import or File > New Android Project. try one or the other, sometimes one option will be strewn with errors while the other option is error free. It's a tempermental environment!

So, is there anyone on a MAC that has gotten an android app to load into eclipse? if so, can you please tell me what versions of eclipse and sdk etc... I have spent 27 hours trying to get this to work... Insanity: doing the same thing over and over again and expecting different results. - Albert Einstein Thanks Everybody...

http://www.buzztouch.com/forum/thread.php?tid=D025EB352CAB262E6042A08 You two should talk.

hahaha... But I love buzztouch... No sleep yet... strike is still on... I am committed to getting through this... Thanks Fred...

Dear fellow BT enthusiasts... So, In my pitiful state of disarray... and after long consultations with both my therapist and some of you loyal BT comrades... I decided to try and load one of my BT 1.5 apps into eclipse to see what errors that it would trigger... Low and behold...it loaded without a hitch... So, my eclipse environment is not a complete lost cause... but any app that I create on my BT server and download into eclipse currently is... Any further advice would be appreciated... and maybe/hopefully this thread will help the magical people at BT grow a stronger strain on app making goodness... As always, thank you all for your time, passion and dedication... Glenn BTW: If this some type of newbie buzztouch hazing ritual...(based on a vision I had in the middle of the night)... I don't give up that easy... this BT cake smells and looks too good... I want a piece...

There's some screens btv1.5 that seem to cause problems. (maps) I don't have much btv2.0 experience to say if any particular plugin will be a problem. I'd start with a simple app btv2.0 and try adding plugins one at a time. Fred

Hard to say if it's BT related, Eclipse related, Android related, or possibly Java related! So many pieces of the puzzle. I struggled with BT 2.0 Android weirdness today, and it eventually came together for no good reason. I think it's mostly related to Eclipse and Android...BT is pretty solid in most respects! Mark

UPDATE... I finally got my apps to load into eclipse with no errors... how, why...? First off, I must thank everyone here... because by reading so many various posts I was able to not only solve my issue (fingers crossed) but, equally important, I was able to learn so much other valuable information... When I had set up my BT server... I thought that more was better... and I loaded up all of the plugins... including the third party plugins from other sources... BIG MISTAKE... (Not that there cannot be helpful plugin resources out there)... Once I removed the third party plugins... All of my projects loaded into eclipse with 0/zero/nada errors... The point is... I spent over a week of my time... pulling my hair out... questioning this platform... for no reason, except... my own naiveté in trusting third party plugins solely based on FEATURES... VALUABLE LEASON LEARNED... and, I am sorry for taking time away from those of you who were so forthcoming with your time, advice, and encouragement... THANK YOU AGAIN... GM

On a previous post where the modified plugin was announced I suggested that we should have a server to test new plugins. Given that it's possible to installed BTv2 on some of the free hosted Servers it's probably something a few of us should look into. Your experience is why I've not installed the modified simple list, though it's a plugin I'd really would like to use.

It seems to me that there's a fundamental lack of understanding by third party creators in how plugins are created. A shared testing server would be a great idea. I think it should also be made clear that as the server is in BETA, plugins should be shown to be in BETA as well. It might save people days or weeks of tearing their hair out if they know beforehand that there will likely be issues. A beta environment isn't the place for people with limited knowledge of the platform to be trying to make it work. If @muhromatic had been aware that this platform is in beta, he would have known to post his environment, PLUGINS used, set up etc and this could probably have been solved in minutes rather than days.

@ muhromatic, question: Did the modified plugin cause problems with all your BTv2.0 apps or only with the app the plugin was used in?

@Fred All of my apps... They worked fine in xcode... but when I loaded even a blank app in eclipse ( in OSX ) there would be several hundred errors... and to be honest... I didn't take the time to isolate which one(s) were causing the problem... The three that were installed came from buzztouchmods.com and they worked fine in xcode. GM

@raveyd makes in incredibly valid, and important point : I think it should also be made clear that as the server is in BETA, plugins should be shown to be in BETA as well. What beta means is that the code is good enough to be run, but you should expect it to be buggy. Generally, beta code is not feature complete, and people should not get too disappointed when their favorite feature isn't available. But, perhaps the most important thing you should take away from the beta designation, is that you should NEVER trust anything in production to beta software. In my personal, and professional (I do software/hardware testing for living), BT has produced a pretty darn stable beta version of Buzztouch Server 2.0. However...there are still bugs, and there are still features to be implemented (I assume), so any app you build on it and submit to the store...there's the potential that it will be broken down the line if we (all of us running BT Server) as beta testers find a major bug. If that happens...you have to suck it up, realize you made the decision to submit an app based on beta software, and figure out what to do. It's a gamble, so choose wisely! Related to that, any third-party plugins should test exhaustively tested on both simulators and real devices. And, since they are tied to beta software, they should be labeled beta as well, until the underlying software gets officially released and you can put it into production. But I really want to stress the testing on both simulators and real devices part...that's super important. It appears, from the number of errors that people are logging about some third-party software, that this is not always the case. I want to stress again a couple things, because I think they are worth mentioning again : (1) I believe BT Server is pretty solid code, and lots of successful apps can be created with what Buzztouch has thus far released; however, (2) BT Server IS BETA SOFTWARE, and if you choose to run it as released, production software, you are signifying that you understand the risks associated with doing so. Just my two cents! Mark

Hey GNW, you've destroyed my world, I didn't know this was Beta, now what am I suppose to do? (Think Skipper told Guilligan he couldn't fly, causing Guilligan to fall to the ground.) Send your two cents to . . .

Hi @Fred...sorry to be the bearer of bad news!

Beta, New, Released, it's all a matter of perspective. Consider this, Gmail was beta for 4 years. Funny. I think the biggest challenge with BT (hosted or server) is the idea that because it's not a simple platform, and you're required to compile whatever project you make (which means you'll always be responsible for understanding the compile process) that there will always be very high probability that something isn't what you expect. This possibility is of course greatly increased when the person that installed eclipse then downloaded a project has almost zero understanding of the process. It's an adventure for sure. It's my opinion that the old-fashion Alpa, Beta, Release, Update, Upgrade model is no longer as useful in web environments. Imagine how SLOW iterations would be if all releases were moved through this process. Yikes, could take months and months to release any code at all if it had to make all the stops in all the different stages before anyone got it. Because of this, all sorts of startups, SAS's models, and new ways of helping people with code have emerged. Heck, GitHub has based an entire site on the idea that things change fast. I think the biggest priority for us, as we move forward, is to somehow both simplify what BT 'does' and to simplify how to learn to use it to your advantage. The power, and flexibility, and sophistication of how it works is very tough for non-programmers to understand. This has zero to do with it being beta or public release. Either way, even if it were100% 'error free' , lots of folks would still not understand it and consider it to be buggy, or broken, or somehow incomplete because the see errors (not related to bt code), funky results (not related to bt code) and other surprises that negatively reflect on the idea. The challenge continues..

David makes some excellent points here. No software project will EVER be 100% error/defect free. Nothing would ever ship if it waited to hit that bar. Every software product that you use has tons of known bugs...some known to everybody, most known only to a select few. But I will posit that every software platform has to reach a point where it can say the particular version is done - feature complete enough and stable enough that people can count on particular things to work most all of the time. If we never reached that level...well, we'd never have solid products in areas that absolutely require them to be solid. I think we all just need to keep in mind that software is an adventure. Some people want it to do everything for them...one button solutions so to speak. Others are content to dig around a bit, and work to understand how to get things done. Still others want access to the guts, so they can modify and enhance at will. And everybody will have different views on what works and what doesn't. I'll say it again, and continue to say it until the last breath leaves my body - Buzztouch is nothing short of amazing software. If you take some time to understand what it can do, and it's limitations, then you'll be absolutely floored by what can be accomplished. It's a huge labor of love, as I believe every software project is - including YOUR app. You apps will most certainly get the same type of scrutiny that buzztouch, and every other software project gets. Just a part of the way it goes! OK, now I really AM rambling! Mark