Re: [mono-android] Debugging in VS2010 is unusable!

2012-12-22 Thread dfabri
i too am not having a good debugging experience on windows vs2010 win7 64bit.

i am using the x86 image and it is just so unstable and slow.

can you debug on your phone without buying the product?

i am currently evaluating the runtime and do not want to commit unless i
feel that this is a viable solution.  I LOVE WHAT I SEE SO FAR

just the debugging is awful!

can someone post how to debug on your phone, how does that work against
vs2010?



--
View this message in context: 
http://mono-for-android.1047100.n5.nabble.com/Debugging-in-VS2010-is-unusable-tp4796099p5712669.html
Sent from the Mono for Android mailing list archive at Nabble.com.
___
Monodroid mailing list
Monodroid@lists.ximian.com

UNSUBSCRIBE INFORMATION:
http://lists.ximian.com/mailman/listinfo/monodroid


Re: [mono-android] proguard

2012-12-22 Thread Atsushi Eno
Not now, but actually it is one of my wishlist item to do. Jonp is right 
on that it is not realistic to let the tool to eliminate unnecessary 
classes automatically. But it might be still possible to have proguard 
intercept the build and reduce whatever you specified (at your risk :-) .
Actually, I once actually tried to get it working but never successfully 
done with it. I haven't really spent a lot of time, so it is not really 
determined as impossible, but we still need to investigate what it could 
be like.


Atsushi Eno

Jonathan Pryor wrote:

On Dec 19, 2012, at 8:52 AM, Jeremy A. Kolb - ARA/NED  wrote:

Is there a way to use proguard to shrink jars that’s compatible with Xamarin?

I'm not sure this will ever be possible. Proguard is conceptually similar to our linker, 
and as such it requires a "global" view of all Java bytecode so that it knows 
which types and members to preserve. The problem is that it can't have such a global 
view, because the actual use is in C# code, which Proguard can't investigate.

This might be possible if we altered the build system so that the generated ACWs 
contained type+method references that mirrored the C# code, but any C# method can 
reference a Java type, not just ACWs, so even this idea would be incomplete. A 
"complete" solution would be a major undertaking, and we have many higher 
priority tasks to work on before even considering this...

  - 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


Re: [mono-android] Splash Page on Resume

2012-12-22 Thread Atsushi Eno

Hello,

For exactly the same reason you are stuck, I prefer this approach for 
splash screen:



public class MySpashScreenActivity extends Activity {

private TimerTask task;

protected void onCreate (Bundle bundle)
{
super.onCreate (bundle);
ImageView iv = new ImageView (this);
iv.setImageResource (R.drawable.mysplashdrawing);
ViewGroup.LayoutParams ivparams = new ViewGroup.LayoutParams 
(ViewGroup.LayoutParams.FILL_PARENT, ViewGroup.LayoutParams.FILL_PARENT);

setContentView (iv);

task = new TimerTask () {
@Override
public void run ()
{
finish ();
Intent intent = new Intent (MySpashScreenActivity.this, 
ActualMainLauncher.class);

intent.setFlags (Intent.FLAG_ACTIVITY_NEW_TASK);
startActivity (intent);
}
};
new Timer ().schedule (task, 2000);
}
}


Atsushi Eno

craig wrote:

I saw this tutorial on splash pages:

http://docs.xamarin.com/Android/Guides/User_Interface/Creating_a_Splash_Screen

However, boss wants the app to reload data from server and re-display splash
page whenever app is resumed from background, which could be in the middle
of the app instead of at the very beginning.  Is there a good strategy for
doing this?

I've tried a couple different ways but all have flaws.  Thanks for your
help.



--
View this message in context: 
http://mono-for-android.1047100.n5.nabble.com/Splash-Page-on-Resume-tp5712633.html
Sent from the Mono for Android mailing list archive at Nabble.com.
___
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


Re: [mono-android] Library resources

2012-12-22 Thread Atsushi Eno
Sorry for late reply, I had been stuck at machine trouble (and away from 
work now). Anyways...


Aren't you trying to add files to some existing library project that was 
created prior to 4.2.8? It won't work, because 4.2.8 adds some project 
properties that are required for the resource build steps.


If you want to enable resource builds in such old projects, add some 
project properties in your .csproj like this (line 12 and 13 will do the 
trick):

https://github.com/xamarin/monodroid-samples/blob/master/ManagedAndroidResourceTest/ManagedAndroidResourceLibrary/ManagedAndroidResourceLibrary.csproj#L12

Atsushi Eno

mario federici wrote:

Thank you, Eno, for your prompt response.

I have an other question: I develop my application with VisualStudio; 
I've not been able to change my source to work like yours (even 
tampering directly with a text editor in the csproj file).  That 
because I found no way to generate ResourceDesigner.cs (while your 
example did).
My solution was to copy your library project, rename it, change the 
namespace and so on. In that way I've got a working solution.


So, in VisualStudio, what's the trick to make Resgen working?

Regards,

   Mario


___
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


Re: [mono-android] DatabaseUtils.getTypeOfObject binding is missing

2012-12-22 Thread Atsushi Eno

Hello,

I don't see such a method in Android API Reference - maybe it is some 
internal API?

http://developer.android.com/reference/android/database/DatabaseUtils.html

Atsushi Eno

Jeremy A. Kolb - ARA/NED wrote:


I’m not seeing this function in DatabaseUtils.



___
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


[mono-android] Confusing Main Launcher Icon Behavior

2012-12-22 Thread craig
I have recently noticed that the launcher icon seems to behave
inconsistently.

If you install the app and run it for the first time, navigate from the
first screen to a secondary screen, press the home button, and then
re-launch the app by using the launcher icon, then it will open on the 1st
screen again instead of resuming where you left off on the 2nd screen.

If you force quit the app and then take the same steps as above then it will
behave the opposite; it will resume on the 2nd screen where you left off
instead of opening the 1st screen.

Has anyone else noticed this behavior?  Is it specific to Mono for Android
or is this behavior inherent to Android in general?  It seems like it should
always resume where you left off rather than restarting on the 1st screen.

I am running on Jellybean.



--
View this message in context: 
http://mono-for-android.1047100.n5.nabble.com/Confusing-Main-Launcher-Icon-Behavior-tp5712674.html
Sent from the Mono for Android mailing list archive at Nabble.com.
___
Monodroid mailing list
Monodroid@lists.ximian.com

UNSUBSCRIBE INFORMATION:
http://lists.ximian.com/mailman/listinfo/monodroid


Re: [mono-android] Confusing Main Launcher Icon Behavior

2012-12-22 Thread craig
I tested on an older emulator (api level 8) and experienced the same
behavior.  Then i test on standard java android without using mono and it
worked correctly... so at first glance it appears to be a mono bug.

As stated above it, when suspending and resuming the app it doesn't return
to the last screen where you left off, instead it always returns you back to
the very 1st screen.  However, if you force quit the app then restart it,
then it will behave correctly from that point on.

It doesn't matter if you install the app using visual studio debug mode or
if you install the app using a release, signed apk file, error still is
present either way.  Tried in a couple different emulators and on an actual
device.

I am running MfA 4.2.7.



--
View this message in context: 
http://mono-for-android.1047100.n5.nabble.com/Confusing-Main-Launcher-Icon-Behavior-tp5712674p5712675.html
Sent from the Mono for Android mailing list archive at Nabble.com.
___
Monodroid mailing list
Monodroid@lists.ximian.com

UNSUBSCRIBE INFORMATION:
http://lists.ximian.com/mailman/listinfo/monodroid