Jonathan,
With respect to the Support4 project you pointed me at; I am getting the
following exception at line 153 of the LoaderCursorSupport class file:
"The type of namespace 'CursorLoader' does not exist in the namespace
Android.Support.V4.App (are you missing an assemble reference?)"
Code li
Jonathan,
Which version of the Mono.Android.dll should I be using in the Support4
project?
I am getting a whole lot of “'Fragment' is an ambiguous reference between
'Android.App.Fragment' and 'Android.Support.V4.App.Fragment'” errors.
Thanks
--
View this message in context:
http://mono-for
Jonathan,
Which version of the Mono.Android.dll should I be using in the Support4 project?
I am getting a whole lot of “'Fragment' is an ambiguous reference between
'Android.App.Fragment' and 'Android.Support.V4.App.Fragment'” errors.
Thanks,
Doug Pettitt
From: topgenorth [via
No, I could not find it anywhere on my system after I had downloaded all of the
Android packages.
I did, finally, find it in the Support4 solution though.
From: topgenorth [via Mono for Android]
[mailto:ml-node+s1047100n5656786...@n5.nabble.com]
Sent: Saturday, April 21, 2012 2:33 PM
To:
You didn't mention this, so thought I would ask- did you also add a
reference to the Mono.Compatibility.v4.dll assembly as well?
On Sat, Apr 21, 2012 at 12:48, drpettitt wrote:
> Jonathan,
>
> I'm having the same problems.
>
> I've added the file "android-support-v4.jar" file to a "SupportLib"
>
It needs to be set to AndroidJavaLibrary.
You are not going to get Intellisense for it in the axml. You'll just
need to use it properly and it should work.
Here's a sample project that uses the Support Library:
https://github.com/xamarin/monodroid-samples/tree/monodroid-4.1-preview/Support4
Jonathan,
I'm having the same problems.
I've added the file "android-support-v4.jar" file to a "SupportLib"
directory in my Project. I've tried setting the Build Action to both
"AndroidJavaLibrary" and AndroidJavaSource" and rebuilding the whole
solution and is still not available in my axml.
I´ve set both ways, but i get same problem, can´t find the library.
Bye
--
View this message in context:
http://mono-for-android.1047100.n5.nabble.com/Using-the-New-Compatibility-Packages-and-TabActivity-Deprication-tp4705492p5081663.html
Sent from the Mono for Android mailing list archive at Na
On Dec 16, 2011, at 4:19 AM, Oscar R Lopez wrote:
> Someone has some example running compatibility package?
>
> I´ve put android-support-v4.jar on my project with "AndroidJavaSource"
> compilation, but i can´t reference anything from it
Try setting the Build action to AndroidJavaLibrary.
Thanks,
Someone has some example running compatibility package?
I´ve put android-support-v4.jar on my project with "AndroidJavaSource"
compilation, but i can´t reference anything from it, on my axml like
viewpager
I always get an inflate error. (ClassNotFound)
Bye
--
View this message in context:
ht
Jonathan Pryor-2 wrote
>
> Note "may" above. There are some known "forward incompatibilities" in
> Android (e.g. methods moving from MotionEvent to InputEvent), and if you
> use those types/members, things will break on downlevel platforms. If it
> works, though, it should work. :-)
>
Jon,
Tha
Wally McClure wrote
>
> Yes, I get what you are talking about.I read it initially as "Is there
> Fragment support?"
>
No problem Wally, your help is much appreciated :)
--
View this message in context:
http://mono-for-android.1047100.n5.nabble.com/Using-the-New-Compatibility-Packages-and-
On Dec 7, 2011, at 12:12 PM, Olaf Kammerman wrote:
> The thing is that I want to develop a generic app that I can deploy to both
> phone (Android 2.x) and tablet (Honeycomb) and that by making use of the
> Fragments API the UI changes depending on the used device (phone/tablet).
IIRC the fragments
Olaf,
Yes, I get what you are talking about.I read it initially as "Is there
Fragment support?"
Wally
> Date: Wed, 7 Dec 2011 09:12:15 -0800
> From: olaf.kammer...@altran.nl
> To: monodroid@lists.ximian.com
> Subject: Re: [mono-android] Using the New Comp
Wally,
The thing is that I want to develop a generic app that I can deploy to both
phone (Android 2.x) and tablet (Honeycomb) and that by making use of the
Fragments API the UI changes depending on the used device (phone/tablet).
But from what I understand this is not possible at this time. So I'm
@jpobst.com
> To: monodroid@lists.ximian.com
> Subject: Re: [mono-android] Using the New Compatibility Packages and
> TabActivity Deprication
>
> No, the compatibility library is not bound in this release. It will be
> included in a future release.
>
> Jonathan
>
>
No, the compatibility library is not bound in this release. It will be
included in a future release.
Jonathan
On 12/7/2011 9:59 AM, Olaf Kammerman wrote:
> Hi Jon,
>
> Since Mono For Android 4.0 was released this week, is it now possible to
> make use of the Fragments API in .NET and target An
Hi Jon,
Since Mono For Android 4.0 was released this week, is it now possible to
make use of the Fragments API in .NET and target Android 2.x by including
the Android compatibility library?
Olaf
--
View this message in context:
http://mono-for-android.1047100.n5.nabble.com/Using-the-New-Compati
On Nov 8, 2011, at 2:18 AM, gabriel.b...@gmail.com wrote:
> There are any news in this subject?
The current news is that public support for this will be delayed until 2.2 in
an effort to get 2.0 out the door sooner.
I apologize for the inconvenience.
- Jon
There are any news in this subject?
2011/8/16 Jonathan Pryor
> On Aug 16, 2011, at 3:38 PM, jondavidjohn wrote:
> > By Deprication issues I mean that it seems to be a pretty high priority
> to get Fragments involved as the previous TabActivity pattern is now
> depricated...
> >
> > is this at al
On Aug 16, 2011, at 3:38 PM, jondavidjohn wrote:
> By Deprication issues I mean that it seems to be a pretty high priority to
> get Fragments involved as the previous TabActivity pattern is now
> depricated...
>
> is this at all near the top of Xamarin's priorities?
Absolutely, improving suppor
ok, I do like java, I'm just not sure how practical it would be to try and
juggle between the two.
By Deprication issues I mean that it seems to be a pretty high priority to
get Fragments involved as the previous TabActivity pattern is now
depricated...
is this at all near the top of Xamarin's pr
On Aug 16, 2011, at 3:13 PM, jondavidjohn wrote:
> Is the new ViewPager, ActionBar, and Fragments available to Mono for Android
> Users?
Only if you like Java. :-)
https://github.com/mono/monodroid-samples/tree/master/GoogleMaps
http://android.xamarin.com/Documentation/Build_Pro
Is the new ViewPager, ActionBar, and Fragments available to Mono for Android
Users?
if so how do you use them?
if not are there any plans to keep up with deprecation issues with android?
--
View this message in context:
http://mono-for-android.1047100.n5.nabble.com/Using-the-New-Compatibility-P
24 matches
Mail list logo
