Re: [android-developers] Re: Best practices for tablet-centric development

2011-03-11 Thread Chris Stewart
Nathan,

Perhaps my use of the word simple was taken a little too literally.  As I
said, I don't really have a grasp on Fragments yet, and if they work as well
as described I'll certainly go that route.  I do have rather simplistic
Activities so maintaining those wouldn't be terribly difficult in my
situation, but the article TreKing linked to provided a lot of insight into
Fragments and really addressed some of the questions I had about them.
 Definitely seems like the path to take.

--
Chris Stewart
http://chriswstewart.com



On Thu, Mar 10, 2011 at 8:26 PM, Nathan critter...@crittermap.com wrote:

 On Mar 10, 1:59 pm, Chris Stewart cstewart...@gmail.com wrote:
 I've always thought that simply maintaining two views
  for each Activity, one for a phone and one for a tablet, would be a good
 way
  to go.  You'd then need to maintain two sets of Activities in your code
 base
  (one for each view, for each Activity), but at least you're simply

 Simple?

 I admire you for having such a thin, easily maintainable Activity. My
 main activity is 3000 lines of code. Sure, it could and should be
 less, but I see it doing a lot of things that should be done in an
 activity - findingviews by id, responding to events, changing the
 state of other views. There are lots of views in the hierarchy, and
 onyl the activity can see them all.

 For me, maintaining two activities would not be small.

 If the fragements API is usable back to 1.6, Is your intention just to
 maintain compatibility with 1.5? All that work for 3% of users when
 you are primarily targeting tablets?

 Nathan

 --
 You received this message because you are subscribed to the Google
 Groups Android Developers group.
 To post to this group, send email to android-developers@googlegroups.com
 To unsubscribe from this group, send email to
 android-developers+unsubscr...@googlegroups.com
 For more options, visit this group at
 http://groups.google.com/group/android-developers?hl=en


-- 
You received this message because you are subscribed to the Google
Groups Android Developers group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en

[android-developers] Re: Best practices for tablet-centric development

2011-03-10 Thread Nathan
On Mar 10, 1:59 pm, Chris Stewart cstewart...@gmail.com wrote:
I've always thought that simply maintaining two views
 for each Activity, one for a phone and one for a tablet, would be a good way
 to go.  You'd then need to maintain two sets of Activities in your code base
 (one for each view, for each Activity), but at least you're simply

Simple?

I admire you for having such a thin, easily maintainable Activity. My
main activity is 3000 lines of code. Sure, it could and should be
less, but I see it doing a lot of things that should be done in an
activity - findingviews by id, responding to events, changing the
state of other views. There are lots of views in the hierarchy, and
onyl the activity can see them all.

For me, maintaining two activities would not be small.

If the fragements API is usable back to 1.6, Is your intention just to
maintain compatibility with 1.5? All that work for 3% of users when
you are primarily targeting tablets?

Nathan

-- 
You received this message because you are subscribed to the Google
Groups Android Developers group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en