I'm with Stephen on this. I realize that there is a lot of magic happening behind the scenes to get things up and going. Personally, I'm amazed the dog talks at all listening to some of the conversations I have heard on this. A few thoughts:
if there are any people cycles on the mono side that can be used to optimize performance, i think it would be of benefit to us all. if there are any instructions/help that anyone can provide to document the splash screen process, that would be great. Wally PS. I'm not complaining, merely trying to move us along in what I hope 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 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 improve in-app performance? > > Use a splash-screen. :-) > > See also Firefox Mobile, which on my N1 isn't ready for input until ~10s > after launching. > > The problem is that there's a great deal of extra work that needs to be done > during app startup, such as initializing the runtime, creating the initial > AppDomain, parsing the .apk for assemblies and loading any required > assemblies, and this needs to be done before the tapped Activity can even be > created (which will likely involve loading additional assemblies & types, > along with registering Java native methods so that things Just Work). > > It may be possible to improve this (speed up runtime init, assembly loading, > etc.), but there will always be some degree of overhead involved. Using a > splash screen can provide a quicker response while letting the user know that > the app can't be used yet. > > Unfortunately we have no samples for what to do for custom splash screens, > but it involves writing a Java activity (the "real" activity) which displays > the splash screen (google for Java code) then launches the managed activity > through the generated Java proxy. You'll want to investigate e.g. > obj/Debug/android/src to see the generated Java proxies (for types & names) > and obj/Debug/android/AndroidManifest.xml (which also provides the types & > names you can use with Activity.startActivity). > > - Jon > > _______________________________________________ > Monodroid mailing list > Monodroid@lists.ximian.com > > UNSUBSCRIBE INFORMATION: > http://lists.ximian.com/mailman/listinfo/monodroid
_______________________________________________ Monodroid mailing list Monodroid@lists.ximian.com UNSUBSCRIBE INFORMATION: http://lists.ximian.com/mailman/listinfo/monodroid
