On Thu, Mar 10, 2011 at 10:29 AM, Justin Anderson <[email protected]> wrote: > Create a Preference subclass for each preference xml file and inflate the > appropriate layout
Couldn't you have done just one Preference subclass, with the child XML file as a custom attribute? I ask in part because I think your approach may become more necessary. Right now, a "legacy" PreferenceActivity with nested PreferenceScreen elements looks bad on Android 3.0: http://commonsware.com/blog/2011/02/25/nested-preferencescreens-honeycomb-ugly.html And PreferenceFragment is not in the Android compatibility library. Off the cuff, that means the way to get single-source cross-version decent-looking nested preference screens may be via your approach. -- Mark Murphy (a Commons Guy) http://commonsware.com | http://github.com/commonsguy http://commonsware.com/blog | http://twitter.com/commonsguy Android Training Worldwide: http://commonsware.com/training -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
