howdy, Suzanne!

howdy, Mark!

have you used honeycomb much yet?

i gots me a XOOM right here, yo

:-)

all right! :-)

if you mean from a development standpoint, some

I want to create a dialog box that opens from an action bar item

where the dialog is a 2x4 grid of 8 small icons

do I use a custom dialog?

well, you have three major choices

1. truly create a custom Dialog (i.e., subclass of Dialog)

2. use AlertDialog.Builder and supply the View to go in the "guts" of the dialog

3. go the DialogFragment route, if this is fully Honeycomb'd (or you have early access to Ms. Hackborn's compatibility library)

I haven't played with DialogFragment yet

ok. but can I create a custom dialog using xml, as in the linked doc above?

(btw, howdy scottt, Julius, and fitz!)

just observing Mark

(howdy)

hello everyone. just lurking again

Suzanne: oh, yeah, I forgot about that

I keep thinking you have to subclass Dialog

AFAIK, that should work fine

really? you mean, it would work?

you talking/conferences at all in San Fran area this coming year?

cool !!

the action bar won't affect the dialog any

ok

no different than an options menu item

got it

fitz: I'm yammering at AnDevCon in two weeks (as is Suzanne)

well, OK, *I'm* yammering

Suzanne is probably speaking much more coherently than that

thanks, mark :-)

I should be attending I|O, but that's pretty much exclusively Googler-led content

otherwise, right now, I have nothing scheduled for the Bay Area

scottt: you still lurking, or do you have a question?

Julius: do you have a question?

Yes

If I have a listview and there are rows each with an imageview say and each has a tag - if two of those imageViews has the same tage

what if I try to fetch the view by tag?

you get one at random, most likely

I would like to update both at the same time

do you have any ideas of the best way to do this?

or have you seen something good that works?

either don't look them up by tag, or scope the lookup-by-tag to do so on a per-row basis, so you can only get one

(btw, howdy, Matt!)

most likely, it'd be the latter

ok thank you for the ideas

no different than finding them by ID

Thanks...just here to lurk for now...working my way through your books. Like the style.

Matt: thanks!

fitz: do you have a question?

(can't wait for some material on 3.0 - I'm being asked to make 3.0 versions and I don't have a device yet)

ya but we only have 1 hr :) - not right now just lurking waiting on someone that is late for a meeting

Honeycomb-flavored updates to the books will be rolling out frequently between now and end of March

first update may be as soon as tomorrow

(still lurking, no questions today)

howdy, scott k!

hi all

scott k: everyone else has had a turn -- do you have a question?

yes, but it may not be your department

i published my "talking quotes" app

when i log in the developers site it says "This .apk requests 1 features that will be used for Android Market Filtering"

android.hardware.touchscreen

i don't know how i am requesting this feature

my manifest specifies:

android:configChanges="keyboardHidden|orientation"

which i lifted from your book

my app doesn't require touchscreen that i know of

what is your minSdkVersion?

4

my guess is that it is there for backwards-compatibility reasons

but, that's just a guess

it runs in the emulator, and shows up when i search, so maybe its not a problem

you could try <uses-feature android:name"android.hardware.touchscreen" android:required="false" />

thanks, i will try that

OK, back to Suzanne: do you have a question?

yes, but I think I just found an example. what's the best way to update a progress dialog from a background thread?

also here - http://developer.android.com/guide/topics/…

I don't think a ProgressDialog necessary dictates the options

so, AsyncTask's onPublishProgress would be my default

okay, thanks

if you're not using AsyncTask, then post() on a View, or runOnUiThread()

welcome back, Julius!

will do it

(hi left too soon)

scottt, fitz, Matt: if you come up with a question, let me know

gotta run, but thanks mark, and see you soon

see ya!

scott k: do you have another question?

i'm leaving to watch the Discovery space launch as i'm in Cocoa, Fl

cool!

thanks for your help - talk to you next time

see ya

OK, if any of you come up with a question, chime in

I'm coming from a Python background; not much java. Any good resources to get me up to speed with the bits of Java most commonly used on Android?

http://commonsware.com/blog/2010/08/02/jav….

Nice! Thanks.

(it's nice weather to watch a launch ~ just under 80 and not very humid here in florida)

Thanks for the link. I'm sure I'll stop by again for a later office hour session with questions.

i found the Osborne scjp study guides (Sierra/Bates) to be pretty good for learning java

Thanks. I'll look those up.

BTW, if either of you have any XOOM questions, I am XOOM'd, so fire away

cool. i was wondering what you were using for 3.0 dev

well.......I........had........been........using........the........emulator........

lol

they *so* gotta get an x86 emulator going

why?

to help fix the emulator speed issue

I mean, a VirtualBox of an x86 Android would be cool, but VirtualBox is an Oracle property, so I doubt they'll go that route

I suspect they'll stick with qemu

speaking on speed issues, is it just me or is the 2.3 emu much slower than the older ones?

each release gets a bit slower for the same screen size

3.0 is dramatically worse, mostly due to screen size, AFAICT

are there any setting tweaks that one can make to make it any better?

not that I am aware of

well, restate that

"Device ram size" in the SDK and AVD Manager definitely has an impact

particularly on larger screen sizes

I couldn't even get 3.0 to boot on 512MB -- had to goose it to 1GB

I haven't tried that on a 2.3 WVGA to see if that would help any

there are lots of qemu switches, but I'm not sure if any will help w/o breaking

ok, back to "x86 emulator"... i'm not sure what u mean. are u using an x86 in an android device?

Most Android devices run ARM processors

the Android emulator emulates an ARM processor

so, the emulator is loading ARM instructions and converting them to x86 instructions to run on your PC/Mac

this is not especially speedy

Android clearly can run on x86 -- Google TV boxes are based on Intel Atom

a version of the Android emulator that used x86 instructions natively would skip the ARM->x86 conversion

and speed things up a fair bit

there are signs that this is in the works in the Googleplex

oh, i got it now. i was just being dense. too many all-nighters :-)

(hi again)

welcome back!

add in the jvm and you end up with essentially a vm within a vm

scottt: yes

Julius: do you have another question? (quick! before you vanish again!)

:-)

(heh)

yes

I have a project where I have a few reuasble layouts

however, I'd like to have reusable Java code too

throw in running your os with a vm and perhaps running a scripted language and you get 4 levels. yuck!

I'm having trouble figuring out how to create reusable Java in cases where views in activities are accessed - perhaps I need to subclass my activities. Anyhow - question is do you have any documentation in your ooks on this?

ooks => books

(err not a well asked question :))

there is the Reusable Components chapter in the Advanced Android book

ah

you probably want Android library projects, which are covered in there

sounds great thank you

is the xoom really $800?

mark you developing on a windows 64bit box or 32 bit - does one work faster/better for android dev?

neither

Linux 64-bit

:>

I'm not sure the 32-bit vs. 64-bit will make much difference, other than in available RAM

ok thanks

what version of Linux you running

Ubuntu 10.10

cool thanks

bfn - thanks for your pointers

you're very welcome

any other questions?

thanks for today see ya next time

none from me

thanks, and have a great evening

you too!