Tony, We're like you, we're currently working on what to do regarding changes and items that are still incomplete. I'm currently working with Wrox and Xamarin to understand what will change and how that effects us. Specifically, we want to include mapping and tablet/honeycomb support in our book. We (our editor at Wrox and I) believe that these are features that our readers want to know about and will give the readers the most value for their money, thus, we have decided to wait before publishing the book. Hopefully, you will agree with this. Regarding the November conference, it will include:Content from March. Many of the things that you do now, you will need in future versions of m4a.Some content that I have fixed/changed since March. There were some things that I just flat out did wrong in March. This content has been updated to reflect a better way of doing things.Hopefully Xamarin will have some new APIs that will be covered in November (cough......mapping......cough). Hopefully, you can come to conference in November and sit in. Wally PS. We don't know anything more than you. Jon has been really communicative regarding what is going to ship along with relative timeframes. > From: [email protected] > Date: Wed, 7 Sep 2011 13:50:24 -0400 > To: [email protected] > Subject: Re: [mono-android] stability and major changes ahead? > > On Sep 7, 2011, at 1:18 PM, Tony H wrote: > > I wonder if the content for the book in Feb. will align with his tech > > presentation at the conference in Nov. > > > Having seen the March presentation, I can assure you that most of the content > will align. :-) > > Much of the March presentation had to do with Android itself, e.g. what an > Activity is, what a Service is, etc. As long as we're following the current > "expose the underlying platform" approach, these concepts will remain. (We > don't plan on changing our "expose the underlying platform approach," ever; > it's our selling point. :-) > > So, it makes me wonder, are the libraries and code base for Mono for > > Android going through some major churn right now? Should I anticipate major > > changes in the forthcoming realeases? > > > That depends upon how we define "major changes." :-) > > What's important? The exposed class library is important, and it's fairly > stable. The only changes we plan on are additional int->enum conversions, and > API additions (Honeycomb support, etc.). Consequently, code written today > should continue to work as-is, and the semantics should not change. I > consider this stable. > > The toolchain is important, e.g. how we use Visual Studio/MonoDevelop. Some > of these semantics have already changed, though not necessarily in > user-visible ways (e.g. per-app debug keystore to a per-user debug keystore, > done in 1.0.3). The basic workflow of package creation, installation, > debugging, etc. shouldn't change much. > > Thus, the question is this: what do you consider as a "major change"? > > - Jon > > _______________________________________________ > Monodroid mailing list > [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
