I have to agree whole-heartedly. I've not purchased this despite initially demonstrating some functionality on devices using the beta versions. It would be suitable if it forced a load screen, or had a time limited operation without a license, but not being able to test and demonstrate the functionality properly in advance is a major challenge for getting sign-off on the product and development time.
From: [email protected] [mailto:[email protected]] On Behalf Of Josh Handel Sent: 01 December 2011 9:00 PM To: Discussions related to Mono for Android Subject: Re: [mono-android] What Debugger isn't Slow? Thanks, your comments below are pretty much what I have come to accept as the reality of Android development.. Though Eclipse/Emulator isn't that bad, Mono/Emulator is impossibly slow. Ximian needs to come up with a way to let us test drive on a device.. Because I promise they are loosing sales to slow emulator testing and the risk of investing in the product given the perceived performance via the emulator experience.. I know internally here it is a risk I am having discussions around with the people that sign the checks :-P Josh Handel Senior Lead Consultant 512.328.8181 | Main 512.328.0584 | Fax 512.577-6568 | Cell www.catapultsystems.com<https://webmail.catapultsystems.com/owa/UrlBlockedError.aspx> CATAPULT SYSTEMS INC. THE MICROSOFT CONSULTING COMPANY ________________________________ From: [email protected] [[email protected]] on behalf of Richard Wilburn [[email protected]] Sent: Thursday, December 01, 2011 2:51 PM To: Discussions related to Mono for Android Subject: Re: [mono-android] What Debugger isn't Slow? I think ultimately what could help you the most is android x86 (this is not supported yet i beileve, but is probably more useful than many realise for people that don't own an android device). Android ARM is very slow in emulating (where as iphone has an awesome emulator). I would also recommend developing against a phone u do have such as iphone, or windows phone (windows phone can be nicely emulated on windows) and then u can make sure u are only debugging android specific issues (minimizing your need for debugging). We are developing android first for our project however, but we use unit tests and physical devices where we can. Some of the android tablets coming out now are quite cheap, and could worth investigation. As others have said, the android emulator is very slow. The best advice for speeding that up is to leaving it running for long periods of time. it does then cache alot of stuff and run faster (but still nastily slow). Im not convinced that a fast hard drive speeds it up, as i have a feeling that android simulators are probably translating cpu instructions and that is where the bottle neck lies. I also run a RAID 0 at home, and notice no difference in simultor speed really between that and non raid enviroments. I would definately recommend that you make sure you rom size is over 1 gig because if the android simulator hits the max limit, it can corupt your android vm which u won;t notice. all it will do is not connect to the internet. Then if u restart emulator it complains its corrupted. Since i made my vm sizes over 1 gig i have never had that issue. I love android but their simulator is a very poor effort (the worst it could be while justifying its use) compared to windows phone and iPhone. -Richard. On Thu, Dec 1, 2011 at 2:02 PM, Sayed Arian Kooshesh <[email protected]<mailto:[email protected]>> wrote: also, what kind of hard drive do you use? How much ram do you have. The hd speed can vastly effect such things as can the quality of your ram. Trying looking at gaming machines. They are built for speed, and coincidentally, faster debugging. I know the "freeze" in normal development all too well. On Wed, Nov 30, 2011 at 5:22 PM, Jonathan Pobst <[email protected]<mailto:[email protected]>> wrote: > The upcoming release (soon!) should have all known instances of the > debugger being slow fixed. If you still have a test case where the > debugger is slow on it, please let us know. > > Note this is for debugging on devices. Doing *anything* is slow on the > emulator, and debugging has to do a lot of somethings, so there's not > much that can be done for emulator debugging. > > Jonathan > > > On 11/30/2011 5:16 PM, jhandel wrote: >> Guys, >> Which of the versions of Mono for Android on VS2010 or Windows >> MonoDevelop aren't slow? I heard that some are speed up.. but 1.9.2 is Crazy >> crazy slow.. so if I don't want to wait a minute or more between presses of >> f10 what version should I be using? >> >> Thanks! >> Josh >> >> -- >> View this message in context: >> http://mono-for-android.1047100.n5.nabble.com/What-Debugger-isn-t-Slow-tp5037055p5037055.html >> Sent from the Mono for Android mailing list archive at Nabble.com. >> _______________________________________________ >> Monodroid mailing list >> [email protected]<mailto:[email protected]> >> >> UNSUBSCRIBE INFORMATION: >> http://lists.ximian.com/mailman/listinfo/monodroid >> >> > > _______________________________________________ > Monodroid mailing list > [email protected]<mailto:[email protected]> > > UNSUBSCRIBE INFORMATION: > http://lists.ximian.com/mailman/listinfo/monodroid -- Extreme Knowledge is not something for which he programs a computer but for which his computer is programming him. -Wozniak _______________________________________________ Monodroid mailing list [email protected]<mailto:[email protected]> UNSUBSCRIBE INFORMATION: http://lists.ximian.com/mailman/listinfo/monodroid
_______________________________________________ Monodroid mailing list [email protected] UNSUBSCRIBE INFORMATION: http://lists.ximian.com/mailman/listinfo/monodroid
