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
