Re: [mono-android] Slow/poor performance

2011-09-15 Thread SRI
Hi Please read this article http://android-developers.blogspot.com/2009/03/window-backgrounds-ui-speed.html Instead of using a Splash screen, you can create a Theme with Background Tile as in the above article and you will see that the screen will instantaneously display. Best Regar

Re: [mono-android] Slow/poor performance

2011-09-15 Thread PVoLan
Brian Long wrote: > > The sample Mono for Android app at > http://blong.com/Downloads/MonoAndroidJavaSplashScreenApp.zip uses a > Java splash screen, which appears pretty promptly. > I've launched this example on my HTC. Got "slideshow effect", because blur was too heavy for my weak graphic acce

Re: [mono-android] Slow/poor performance

2011-09-13 Thread efontana
4:14 you need to remove all these things from the csproj: 14:14 ..\debug.keystore 14:14 ..\debug.keystore 14:14 android 14:14 androiddebugkey 14:14 android 14:15 That was it! Thanks. 14:16 np Thanks to jpobst that fixed the problem. -- View this message in context: ht

Re: [mono-android] Slow/poor performance

2011-09-13 Thread efontana
I'm also getting this error about the jarsigner: Microsoft (R) Build Engine Version 4.0.30319.1 [Microsoft .NET Framework, Version 4.0.30319.235] Copyright (C) Microsoft Corporation 2007. All rights reserved. Build started 9/13/2011 1:55:51 PM. Project "C:\Users\eric\Downloads\splash\SplashApp.c

Re: [mono-android] Slow/poor performance

2011-05-14 Thread Brian Long
Tom > Just gave this a quick try - got a 'System.Exception: "jarsigner" exited with > code 1.'. > Before I dig too deep into this, thought I'd see if there were any sage words > of advice.  :) Erm. No - not seen that one It seems Piotr found my example went through ok The only issues I'd had

Re: [mono-android] Slow/poor performance

2011-05-14 Thread Piotr Kryger
I got the same error, when trying to setup splash screen in my project (though sample project from Brian worked fine). I found the problem was line setContentView(R.layout.splash) in SplashActivity.java - commenting this one made my project compile and deploy fine. As a workaround I replaced consta

Re: [mono-android] Slow/poor performance

2011-05-13 Thread Tom Opgenorth
Just gave this a quick try - got a 'System.Exception: "jarsigner" exited with code 1.'. Before I dig too deep into this, thought I'd see if there were any sage words of advice. :) TIA. On Thu, May 12, 2011 at 16:30, Brian Long wrote: > >>if there are any instructions/help that anyone can provi

Re: [mono-android] Slow/poor performance

2011-05-13 Thread Jon Dick
It would be nice to see this somehow incorporated into Mono for Android so that the app author could choose a few settings: 1) Yes/No Enable Splash Screen a) If Enabled, path to image to use Could go so far as to also have a check box to show or not show an activity indicator, as well as the c

Re: [mono-android] Slow/poor performance

2011-05-12 Thread Brian Long
>>if there are any instructions/help that anyone can provide to document the >>splash screen process, that would be great. Wally, I may be able to help on this one The sample Mono for Android app at http://blong.com/Downloads/MonoAndroidJavaSplashScreenApp.zip uses a Java splash screen, which ap

Re: [mono-android] Slow/poor performance

2011-05-12 Thread Wally McClure
is a positive direction. > From: jpr...@novell.com > Date: Thu, 12 May 2011 09:39:12 -0400 > To: monodroid@lists.ximian.com > Subject: Re: [mono-android] Slow/poor performance > > On May 12, 2011, at 9:25 AM, Stephen Long wrote: > > While my findings are not exactl

Re: [mono-android] Slow/poor performance

2011-05-12 Thread Jonathan Pryor
On May 12, 2011, at 9:25 AM, Stephen Long wrote: > While my findings are not exactly quantitative or conclusive, it raises > immediate viability concerns. Along with other concerns regarding various > issues of general IDE/debugging performance and issues, are there any plans > to dramatically

[mono-android] Slow/poor performance

2011-05-12 Thread Stephen Long
I have been performing tests with porting code between native Java apps w/ Eclipse + ADT to VS2010 + Monodroid. My initial findings are as follows: Even for a simple/contrived application with a minimal UI/logic, start-up times for a Mono app are in the 5-10 second range. This improves on subseq