[android-developers] Re: What's new in honeycomb?

2011-01-27 Thread Craig Mitchell
 That is, no postage stamp in the middle like we did for apps
 targeting prior to 1.6 that only ever thought about 480x320
 mdpi screens

FYI:  Just run a 1.5 app on the Honeycomb Preview Emulator and it did
not postage stamp it!  Woohoo!  There was a lot of space around
widgets (as expected), but the OpenGL stuff looked great!

...yes, I am still going to move my apps off 1.5.  There are a lot of
changes (direct buffers, bitmap decode scaling, screen touch coords,
even the back button functionality seems to have changed!).


On Jan 10, 5:12 pm, Dianne Hackborn hack...@android.com wrote:
 In fact since the APIs for this have been in the platform since 1.6, by the
 simple act of saying you are targeting 1.6 or later (with
 android:targetSdkVersion=4 or larger), you are telling the platform you
 know about different screen sizes and will get the full available space.
  You already see this today on the Samsung Tab, and if you set up a larger
 screen in the emulator.

 The best way to prepare for tablets is to do what is already there: say you
 support larger screens, and ensure you do work on them.

 The only thing that is really different is xlarge screens.  Those were
 introduced in 2.3.  Prior to that, we never really defined what the maximum
 size of a large screen is, so the cut-off points between these is now more
 formalized.  Also because we never defined the limit for large, it is
 unlikely that we will do any kind of compatibility for apps that say they
 support large but don't support xlarge.  That is, no postage stamp in the
 middle like we did for apps targeting prior to 1.6 that only ever thought
 about 480x320 mdpi screens.  Once you are in the I know screens are more
 than 480x320 world, you need to be sure you do something reasonable for any
 screen larger than the minimum size class you have said you support.









 On Sun, Jan 9, 2011 at 6:36 PM, Romain Guy romain...@android.com wrote:
  It depends on how your app is setup. Depending on how applications declare
  how they support multiple screens and densities the app might be boxed,
  scaled or simply fill the screen and rely on layout to look correct.

  On Sun, Jan 9, 2011 at 6:09 PM, Craig Mitchell craig...@gmail.com wrote:

  And you all have done a fantastic job at that.  However, I'm not a fan
  of boxing an app for large screens.  I would much prefer an app to be
  expanded to the full screen size and look a little pixelated, then
  only take up a small section of the screen.

  ...apologies that this comment is off topic.

  On Jan 10, 9:44 am, Dianne Hackborn hack...@android.com wrote:
   We try hard to not break apps in newer versions of the platform, as long
  as
   they are written correctly.

   On Sun, Jan 9, 2011 at 2:40 PM, sblantipodi 
  perini.dav...@dpsoftware.orgwrote:

I would like to know if our applications written for 2.2 and 2.3
tablets will work
on honeycomb without modifications.

On Jan 7, 1:27 am, Dianne Hackborn hack...@android.com wrote:
 On Thu, Jan 6, 2011 at 3:39 PM, sblantipodi 
perini.dav...@dpsoftware.orgwrote:

  Obviously this new android will grant compatibility to olter apps
  right?

 You may have seen the numerous developer blogs posts on preparing
  for
larger
 screens and such. :)

 --
 Dianne Hackborn
 Android framework engineer
 hack...@android.com

 Note: please don't send private questions to me, as I don't have
  time to
 provide private support, and so won't reply to such e-mails.  All
  such
 questions should be posted on public forums, where I and others can
  see
and
 answer them.

--
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.comandroid-developers%2Bunsubs
 cr...@googlegroups.comandroid-developers%2Bunsubs
  cr...@googlegroups.com
For more options, visit this group at
   http://groups.google.com/group/android-developers?hl=en

   --
   Dianne Hackborn
   Android framework engineer
   hack...@android.com

   Note: please don't send private questions to me, as I don't have time to
   provide private support, and so won't reply to such e-mails.  All such
   questions should be posted on public forums, where I and others can see
  and
   answer them.

  --
  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.comandroid-developers%2Bunsubs
   cr...@googlegroups.com
  For more options, visit this group at
 http://groups.google.com/group/android-developers?hl=en

  --
  Romain Guy
  Android framework engineer
  romain...@android.com

  Note: 

[android-developers] Re: What's new in honeycomb?

2011-01-14 Thread Scott

 You may have seen the numerous developer blogs posts on preparing for larger
 screens and such. :)

I've thought about it and come up with two ways to better allow apps
to use that bigger real-estate.
A) Add a new Resource size (current: hdpi, mdpi, ldpi) such as an
'xhdpi' or 'tdpi' tag for tablet screen sizes (most likely option,
IMO, based on the Gingerbread changes to the status bar icons with the
addition of the -v9 suffix for those directories)
i) Very simple, and natural next step.
B) Allow nested activities to allow developers to quickly transition
their apps from smart-phone based to tablet-based. Then people could
easily transition apps to Tablet form factors.
i) Example: Have a listView of emails on the left that sends
intents to the right half of the screen to display those emails.
ii) Although it doesn't flow the regular way android applications
are architectured, I think it would quickly allow developers to make
their apps awesome for tablets without putting in a lot of man hours
to change their apps.
iii) Could be done by adding an extra piece of information to the
intent,  Much like a web page with multiple frames works.

Those were my guesses, but based on Dianne's answer, I think it's safe
to assume that A will come. All of the current blog posts encourage
developers to make use of the resource architecture that's been
implemented in Android.
screen geometry post: 
http://android-developers.blogspot.com/2010/09/screen-geometry-fun.html
Example blog post on uses-features in tablets and Google TV:
http://android-developers.blogspot.com/2010/10/five-steps-to-future-hardware-happiness.html

This is just my opinion, looking at the situation and such.

Hope this helps people also speculating about what Honeycomb will
bring.

Thanks for reading,
Scott MacWatters

-- 
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


Re: [android-developers] Re: What's new in honeycomb?

2011-01-14 Thread Phil Bayfield
I'd make the assumption that with higher resolution phones on the way soon
that Honeycomb would be for phones also with a similar UI and the same API,
would be interesting to hear more on this though if anyone knows and is
allowed to reveal at this stage.

On 10 January 2011 08:43, mort m...@sto-helit.de wrote:

 I don't know if I get a bit off-topic, but it's still related to
 Honeycomb and tablets:
 I've seen several apps in the Honeycomb videos which displayed in one
 screen what must've been multiple Activities before, like e.g. the
 mail list and single mail view.
 Will there be an easy way to support multiple visible Activities, or
 is it just hard work to create mightier Widgets (e.g. something like
 the mail list as Widget instead of ListActivity) and lots of if that
 Widget exists in the current layout ...?
 I think it'd be a good idea to give developers some chance to prepare
 for things like that. Properly supporting tablets is more than just
 supporting a different screen size, it's often a completely different
 UI that must be supported in the same app...
 Also, can you give some hints how the future way is planned? Will
 there be a Honeycomb for smartphones with a different UI? Will tablet
 and smartphone APIs remain compatible? (You know the problem with the
 bad long f word... ;))

 --
 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.comandroid-developers%2bunsubscr...@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

Re: [android-developers] Re: What's new in honeycomb?

2011-01-14 Thread TreKing
On Sat, Jan 8, 2011 at 9:22 PM, Scott scott.macwatt...@gmail.com wrote:

 A) Add a new Resource size (current: hdpi, mdpi, ldpi) such as an 'xhdpi'
 or 'tdpi' tag for tablet screen sizes


http://developer.android.com/guide/practices/screens_support.html#qualifiers

-
TreKing http://sites.google.com/site/rezmobileapps/treking - Chicago
transit tracking app for Android-powered devices

-- 
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: What's new in honeycomb?

2011-01-10 Thread mort
I don't know if I get a bit off-topic, but it's still related to
Honeycomb and tablets:
I've seen several apps in the Honeycomb videos which displayed in one
screen what must've been multiple Activities before, like e.g. the
mail list and single mail view.
Will there be an easy way to support multiple visible Activities, or
is it just hard work to create mightier Widgets (e.g. something like
the mail list as Widget instead of ListActivity) and lots of if that
Widget exists in the current layout ...?
I think it'd be a good idea to give developers some chance to prepare
for things like that. Properly supporting tablets is more than just
supporting a different screen size, it's often a completely different
UI that must be supported in the same app...
Also, can you give some hints how the future way is planned? Will
there be a Honeycomb for smartphones with a different UI? Will tablet
and smartphone APIs remain compatible? (You know the problem with the
bad long f word... ;))

-- 
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


Re: [android-developers] Re: What's new in honeycomb?

2011-01-10 Thread Dianne Hackborn
On Mon, Jan 10, 2011 at 12:43 AM, mort m...@sto-helit.de wrote:

 I've seen several apps in the Honeycomb videos which displayed in one
 screen what must've been multiple Activities before, like e.g. the
 mail list and single mail view.
 Will there be an easy way to support multiple visible Activities, or
 is it just hard work to create mightier Widgets (e.g. something like
 the mail list as Widget instead of ListActivity) and lots of if that
 Widget exists in the current layout ...?


I think Andy made a comment about this a while ago.  I can't get into
details about Honeycomb at this point.

-- 
Dianne Hackborn
Android framework engineer
hack...@android.com

Note: please don't send private questions to me, as I don't have time to
provide private support, and so won't reply to such e-mails.  All such
questions should be posted on public forums, where I and others can see and
answer them.

-- 
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: What's new in honeycomb?

2011-01-10 Thread Craig Mitchell
 That is, no postage stamp in the middle like we did for apps
 targeting prior to 1.6 that only ever thought about 480x320
 mdpi screens.

That is what I was talking about.  I would prefer 1.5 and earlier apps
to expand and not get boxed to a postage stamp.

...and yes, I know, I really should upgrade my apps to 1.6.  :-)


On Jan 10, 5:12 pm, Dianne Hackborn hack...@android.com wrote:
 In fact since the APIs for this have been in the platform since 1.6, by the
 simple act of saying you are targeting 1.6 or later (with
 android:targetSdkVersion=4 or larger), you are telling the platform you
 know about different screen sizes and will get the full available space.
  You already see this today on the Samsung Tab, and if you set up a larger
 screen in the emulator.

 The best way to prepare for tablets is to do what is already there: say you
 support larger screens, and ensure you do work on them.

 The only thing that is really different is xlarge screens.  Those were
 introduced in 2.3.  Prior to that, we never really defined what the maximum
 size of a large screen is, so the cut-off points between these is now more
 formalized.  Also because we never defined the limit for large, it is
 unlikely that we will do any kind of compatibility for apps that say they
 support large but don't support xlarge.  That is, no postage stamp in the
 middle like we did for apps targeting prior to 1.6 that only ever thought
 about 480x320 mdpi screens.  Once you are in the I know screens are more
 than 480x320 world, you need to be sure you do something reasonable for any
 screen larger than the minimum size class you have said you support.









 On Sun, Jan 9, 2011 at 6:36 PM, Romain Guy romain...@android.com wrote:
  It depends on how your app is setup. Depending on how applications declare
  how they support multiple screens and densities the app might be boxed,
  scaled or simply fill the screen and rely on layout to look correct.

  On Sun, Jan 9, 2011 at 6:09 PM, Craig Mitchell craig...@gmail.com wrote:

  And you all have done a fantastic job at that.  However, I'm not a fan
  of boxing an app for large screens.  I would much prefer an app to be
  expanded to the full screen size and look a little pixelated, then
  only take up a small section of the screen.

  ...apologies that this comment is off topic.

  On Jan 10, 9:44 am, Dianne Hackborn hack...@android.com wrote:
   We try hard to not break apps in newer versions of the platform, as long
  as
   they are written correctly.

   On Sun, Jan 9, 2011 at 2:40 PM, sblantipodi 
  perini.dav...@dpsoftware.orgwrote:

I would like to know if our applications written for 2.2 and 2.3
tablets will work
on honeycomb without modifications.

On Jan 7, 1:27 am, Dianne Hackborn hack...@android.com wrote:
 On Thu, Jan 6, 2011 at 3:39 PM, sblantipodi 
perini.dav...@dpsoftware.orgwrote:

  Obviously this new android will grant compatibility to olter apps
  right?

 You may have seen the numerous developer blogs posts on preparing
  for
larger
 screens and such. :)

 --
 Dianne Hackborn
 Android framework engineer
 hack...@android.com

 Note: please don't send private questions to me, as I don't have
  time to
 provide private support, and so won't reply to such e-mails.  All
  such
 questions should be posted on public forums, where I and others can
  see
and
 answer them.

--
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.comandroid-developers%2Bunsubs
 cr...@googlegroups.comandroid-developers%2Bunsubs
  cr...@googlegroups.com
For more options, visit this group at
   http://groups.google.com/group/android-developers?hl=en

   --
   Dianne Hackborn
   Android framework engineer
   hack...@android.com

   Note: please don't send private questions to me, as I don't have time to
   provide private support, and so won't reply to such e-mails.  All such
   questions should be posted on public forums, where I and others can see
  and
   answer them.

  --
  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.comandroid-developers%2Bunsubs
   cr...@googlegroups.com
  For more options, visit this group at
 http://groups.google.com/group/android-developers?hl=en

  --
  Romain Guy
  Android framework engineer
  romain...@android.com

  Note: please don't send private questions to me, as I don't have time to
  provide private support.  All such questions should be posted on public
  forums, where I and others can see and answer them

   --
  You 

Re: [android-developers] Re: What's new in honeycomb?

2011-01-10 Thread Dianne Hackborn
On Mon, Jan 10, 2011 at 4:43 PM, Craig Mitchell craig...@gmail.com wrote:

  That is, no postage stamp in the middle like we did for apps
  targeting prior to 1.6 that only ever thought about 480x320
  mdpi screens.
 That is what I was talking about.  I would prefer 1.5 and earlier apps
 to expand and not get boxed to a postage stamp.
  ...and yes, I know, I really should upgrade my apps to 1.6.  :-)


Yes, you really should update your app to either say it *knows* about
something more than 1.5 (through android:targetSdkVersion) or that it knows
about larger screens.

We have been talking about this stuff for well over a year.  I think it is
unlikely at this point to have a UI for users to be able to switch apps
between postage stamp and letter box, because that is a poorer experience
than one where the apps just do the right thing in the first place.  And
besides, it wouldn't help any existing tablets that are now shipping or will
soon.  If you care about the user experience here with your app, make it do
*something* reasonable.

-- 
Dianne Hackborn
Android framework engineer
hack...@android.com

Note: please don't send private questions to me, as I don't have time to
provide private support, and so won't reply to such e-mails.  All such
questions should be posted on public forums, where I and others can see and
answer them.

-- 
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: What's new in honeycomb?

2011-01-10 Thread Craig Mitchell
Yes, agreed.  I just would have preferred the users to get a letter
box size, rather then a postage stamp size.

I am impressed that this is the first change I have had to do since
Android 1.5, and the change is really only to support new hardware.

Excellent work Android team!  :-)


On Jan 11, 2:09 pm, Dianne Hackborn hack...@android.com wrote:
 On Mon, Jan 10, 2011 at 4:43 PM, Craig Mitchell craig...@gmail.com wrote:
   That is, no postage stamp in the middle like we did for apps
   targeting prior to 1.6 that only ever thought about 480x320
   mdpi screens.
  That is what I was talking about.  I would prefer 1.5 and earlier apps
  to expand and not get boxed to a postage stamp.
   ...and yes, I know, I really should upgrade my apps to 1.6.  :-)

 Yes, you really should update your app to either say it *knows* about
 something more than 1.5 (through android:targetSdkVersion) or that it knows
 about larger screens.

 We have been talking about this stuff for well over a year.  I think it is
 unlikely at this point to have a UI for users to be able to switch apps
 between postage stamp and letter box, because that is a poorer experience
 than one where the apps just do the right thing in the first place.  And
 besides, it wouldn't help any existing tablets that are now shipping or will
 soon.  If you care about the user experience here with your app, make it do
 *something* reasonable.

 --
 Dianne Hackborn
 Android framework engineer
 hack...@android.com

 Note: please don't send private questions to me, as I don't have time to
 provide private support, and so won't reply to such e-mails.  All such
 questions should be posted on public forums, where I and others can see and
 answer them.

-- 
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


Re: [android-developers] Re: What's new in honeycomb?

2011-01-10 Thread Dianne Hackborn
Thanks, we appreciate it. :)

On Mon, Jan 10, 2011 at 7:46 PM, Craig Mitchell craig...@gmail.com wrote:

 Yes, agreed.  I just would have preferred the users to get a letter
 box size, rather then a postage stamp size.

 I am impressed that this is the first change I have had to do since
 Android 1.5, and the change is really only to support new hardware.

 Excellent work Android team!  :-)


 On Jan 11, 2:09 pm, Dianne Hackborn hack...@android.com wrote:
  On Mon, Jan 10, 2011 at 4:43 PM, Craig Mitchell craig...@gmail.com
 wrote:
That is, no postage stamp in the middle like we did for apps
targeting prior to 1.6 that only ever thought about 480x320
mdpi screens.
   That is what I was talking about.  I would prefer 1.5 and earlier apps
   to expand and not get boxed to a postage stamp.
...and yes, I know, I really should upgrade my apps to 1.6.  :-)
 
  Yes, you really should update your app to either say it *knows* about
  something more than 1.5 (through android:targetSdkVersion) or that it
 knows
  about larger screens.
 
  We have been talking about this stuff for well over a year.  I think it
 is
  unlikely at this point to have a UI for users to be able to switch apps
  between postage stamp and letter box, because that is a poorer experience
  than one where the apps just do the right thing in the first place.  And
  besides, it wouldn't help any existing tablets that are now shipping or
 will
  soon.  If you care about the user experience here with your app, make it
 do
  *something* reasonable.
 
  --
  Dianne Hackborn
  Android framework engineer
  hack...@android.com
 
  Note: please don't send private questions to me, as I don't have time to
  provide private support, and so won't reply to such e-mails.  All such
  questions should be posted on public forums, where I and others can see
 and
  answer them.

 --
 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.comandroid-developers%2bunsubscr...@googlegroups.com
 For more options, visit this group at
 http://groups.google.com/group/android-developers?hl=en




-- 
Dianne Hackborn
Android framework engineer
hack...@android.com

Note: please don't send private questions to me, as I don't have time to
provide private support, and so won't reply to such e-mails.  All such
questions should be posted on public forums, where I and others can see and
answer them.

-- 
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: What's new in honeycomb?

2011-01-09 Thread sblantipodi
I would like to know if our applications written for 2.2 and 2.3
tablets will work
on honeycomb without modifications.

On Jan 7, 1:27 am, Dianne Hackborn hack...@android.com wrote:
 On Thu, Jan 6, 2011 at 3:39 PM, sblantipodi 
 perini.dav...@dpsoftware.orgwrote:

  Obviously this new android will grant compatibility to olter apps
  right?

 You may have seen the numerous developer blogs posts on preparing for larger
 screens and such. :)

 --
 Dianne Hackborn
 Android framework engineer
 hack...@android.com

 Note: please don't send private questions to me, as I don't have time to
 provide private support, and so won't reply to such e-mails.  All such
 questions should be posted on public forums, where I and others can see and
 answer them.

-- 
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


Re: [android-developers] Re: What's new in honeycomb?

2011-01-09 Thread Dianne Hackborn
We try hard to not break apps in newer versions of the platform, as long as
they are written correctly.

On Sun, Jan 9, 2011 at 2:40 PM, sblantipodi perini.dav...@dpsoftware.orgwrote:

 I would like to know if our applications written for 2.2 and 2.3
 tablets will work
 on honeycomb without modifications.

 On Jan 7, 1:27 am, Dianne Hackborn hack...@android.com wrote:
  On Thu, Jan 6, 2011 at 3:39 PM, sblantipodi 
 perini.dav...@dpsoftware.orgwrote:
 
   Obviously this new android will grant compatibility to olter apps
   right?
 
  You may have seen the numerous developer blogs posts on preparing for
 larger
  screens and such. :)
 
  --
  Dianne Hackborn
  Android framework engineer
  hack...@android.com
 
  Note: please don't send private questions to me, as I don't have time to
  provide private support, and so won't reply to such e-mails.  All such
  questions should be posted on public forums, where I and others can see
 and
  answer them.

 --
 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.comandroid-developers%2bunsubscr...@googlegroups.com
 For more options, visit this group at
 http://groups.google.com/group/android-developers?hl=en




-- 
Dianne Hackborn
Android framework engineer
hack...@android.com

Note: please don't send private questions to me, as I don't have time to
provide private support, and so won't reply to such e-mails.  All such
questions should be posted on public forums, where I and others can see and
answer them.

-- 
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: What's new in honeycomb?

2011-01-09 Thread Craig Mitchell
And you all have done a fantastic job at that.  However, I'm not a fan
of boxing an app for large screens.  I would much prefer an app to be
expanded to the full screen size and look a little pixelated, then
only take up a small section of the screen.

...apologies that this comment is off topic.


On Jan 10, 9:44 am, Dianne Hackborn hack...@android.com wrote:
 We try hard to not break apps in newer versions of the platform, as long as
 they are written correctly.

 On Sun, Jan 9, 2011 at 2:40 PM, sblantipodi 
 perini.dav...@dpsoftware.orgwrote:









  I would like to know if our applications written for 2.2 and 2.3
  tablets will work
  on honeycomb without modifications.

  On Jan 7, 1:27 am, Dianne Hackborn hack...@android.com wrote:
   On Thu, Jan 6, 2011 at 3:39 PM, sblantipodi 
  perini.dav...@dpsoftware.orgwrote:

Obviously this new android will grant compatibility to olter apps
right?

   You may have seen the numerous developer blogs posts on preparing for
  larger
   screens and such. :)

   --
   Dianne Hackborn
   Android framework engineer
   hack...@android.com

   Note: please don't send private questions to me, as I don't have time to
   provide private support, and so won't reply to such e-mails.  All such
   questions should be posted on public forums, where I and others can see
  and
   answer them.

  --
  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.comandroid-developers%2Bunsubs 
  cr...@googlegroups.com
  For more options, visit this group at
 http://groups.google.com/group/android-developers?hl=en

 --
 Dianne Hackborn
 Android framework engineer
 hack...@android.com

 Note: please don't send private questions to me, as I don't have time to
 provide private support, and so won't reply to such e-mails.  All such
 questions should be posted on public forums, where I and others can see and
 answer them.

-- 
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


Re: [android-developers] Re: What's new in honeycomb?

2011-01-09 Thread Romain Guy
It depends on how your app is setup. Depending on how applications declare
how they support multiple screens and densities the app might be boxed,
scaled or simply fill the screen and rely on layout to look correct.

On Sun, Jan 9, 2011 at 6:09 PM, Craig Mitchell craig...@gmail.com wrote:

 And you all have done a fantastic job at that.  However, I'm not a fan
 of boxing an app for large screens.  I would much prefer an app to be
 expanded to the full screen size and look a little pixelated, then
 only take up a small section of the screen.

 ...apologies that this comment is off topic.


 On Jan 10, 9:44 am, Dianne Hackborn hack...@android.com wrote:
  We try hard to not break apps in newer versions of the platform, as long
 as
  they are written correctly.
 
  On Sun, Jan 9, 2011 at 2:40 PM, sblantipodi 
 perini.dav...@dpsoftware.orgwrote:
 
 
 
 
 
 
 
 
 
   I would like to know if our applications written for 2.2 and 2.3
   tablets will work
   on honeycomb without modifications.
 
   On Jan 7, 1:27 am, Dianne Hackborn hack...@android.com wrote:
On Thu, Jan 6, 2011 at 3:39 PM, sblantipodi 
   perini.dav...@dpsoftware.orgwrote:
 
 Obviously this new android will grant compatibility to olter apps
 right?
 
You may have seen the numerous developer blogs posts on preparing for
   larger
screens and such. :)
 
--
Dianne Hackborn
Android framework engineer
hack...@android.com
 
Note: please don't send private questions to me, as I don't have time
 to
provide private support, and so won't reply to such e-mails.  All
 such
questions should be posted on public forums, where I and others can
 see
   and
answer them.
 
   --
   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.comandroid-developers%2bunsubscr...@googlegroups.comandroid-developers%2Bunsubs
 cr...@googlegroups.com
   For more options, visit this group at
  http://groups.google.com/group/android-developers?hl=en
 
  --
  Dianne Hackborn
  Android framework engineer
  hack...@android.com
 
  Note: please don't send private questions to me, as I don't have time to
  provide private support, and so won't reply to such e-mails.  All such
  questions should be posted on public forums, where I and others can see
 and
  answer them.

 --
 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.comandroid-developers%2bunsubscr...@googlegroups.com
 For more options, visit this group at
 http://groups.google.com/group/android-developers?hl=en




-- 
Romain Guy
Android framework engineer
romain...@android.com

Note: please don't send private questions to me, as I don't have time to
provide private support.  All such questions should be posted on public
forums, where I and others can see and answer them

-- 
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

Re: [android-developers] Re: What's new in honeycomb?

2011-01-09 Thread Dianne Hackborn
In fact since the APIs for this have been in the platform since 1.6, by the
simple act of saying you are targeting 1.6 or later (with
android:targetSdkVersion=4 or larger), you are telling the platform you
know about different screen sizes and will get the full available space.
 You already see this today on the Samsung Tab, and if you set up a larger
screen in the emulator.

The best way to prepare for tablets is to do what is already there: say you
support larger screens, and ensure you do work on them.

The only thing that is really different is xlarge screens.  Those were
introduced in 2.3.  Prior to that, we never really defined what the maximum
size of a large screen is, so the cut-off points between these is now more
formalized.  Also because we never defined the limit for large, it is
unlikely that we will do any kind of compatibility for apps that say they
support large but don't support xlarge.  That is, no postage stamp in the
middle like we did for apps targeting prior to 1.6 that only ever thought
about 480x320 mdpi screens.  Once you are in the I know screens are more
than 480x320 world, you need to be sure you do something reasonable for any
screen larger than the minimum size class you have said you support.

On Sun, Jan 9, 2011 at 6:36 PM, Romain Guy romain...@android.com wrote:

 It depends on how your app is setup. Depending on how applications declare
 how they support multiple screens and densities the app might be boxed,
 scaled or simply fill the screen and rely on layout to look correct.


 On Sun, Jan 9, 2011 at 6:09 PM, Craig Mitchell craig...@gmail.com wrote:

 And you all have done a fantastic job at that.  However, I'm not a fan
 of boxing an app for large screens.  I would much prefer an app to be
 expanded to the full screen size and look a little pixelated, then
 only take up a small section of the screen.

 ...apologies that this comment is off topic.


 On Jan 10, 9:44 am, Dianne Hackborn hack...@android.com wrote:
  We try hard to not break apps in newer versions of the platform, as long
 as
  they are written correctly.
 
  On Sun, Jan 9, 2011 at 2:40 PM, sblantipodi 
 perini.dav...@dpsoftware.orgwrote:
 
 
 
 
 
 
 
 
 
   I would like to know if our applications written for 2.2 and 2.3
   tablets will work
   on honeycomb without modifications.
 
   On Jan 7, 1:27 am, Dianne Hackborn hack...@android.com wrote:
On Thu, Jan 6, 2011 at 3:39 PM, sblantipodi 
   perini.dav...@dpsoftware.orgwrote:
 
 Obviously this new android will grant compatibility to olter apps
 right?
 
You may have seen the numerous developer blogs posts on preparing
 for
   larger
screens and such. :)
 
--
Dianne Hackborn
Android framework engineer
hack...@android.com
 
Note: please don't send private questions to me, as I don't have
 time to
provide private support, and so won't reply to such e-mails.  All
 such
questions should be posted on public forums, where I and others can
 see
   and
answer them.
 
   --
   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.comandroid-developers%2bunsubscr...@googlegroups.comandroid-developers%2Bunsubs
 cr...@googlegroups.com
   For more options, visit this group at
  http://groups.google.com/group/android-developers?hl=en
 
  --
  Dianne Hackborn
  Android framework engineer
  hack...@android.com
 
  Note: please don't send private questions to me, as I don't have time to
  provide private support, and so won't reply to such e-mails.  All such
  questions should be posted on public forums, where I and others can see
 and
  answer them.

 --
 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.comandroid-developers%2bunsubscr...@googlegroups.com
 For more options, visit this group at
 http://groups.google.com/group/android-developers?hl=en




 --
 Romain Guy
 Android framework engineer
 romain...@android.com

 Note: please don't send private questions to me, as I don't have time to
 provide private support.  All such questions should be posted on public
 forums, where I and others can see and answer them

  --
 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.comandroid-developers%2bunsubscr...@googlegroups.com
 For more options, visit this group at
 http://groups.google.com/group/android-developers?hl=en




-- 
Dianne Hackborn
Android framework engineer