howdy, scottt!

greetings from Android Open!

hello. i wasnt sure you'd notice me enter with all the activity in here

the crickets got tired of chirping

damn lazy crickets

i'm envious. i'd would have loved to go

anything in particular that I can help you with today?

has their ever been an east coast conference? i really dont think all the android devs are in silicon valley (or particularly want to go there)

no, i just popped in for some and dev inspiration

I am not aware of a US East Coast conference

I argued with the AnDevCon folks that if they're going to do two a year, they should be bi-coastal

lost that fight, at least for 2011

morning

howdy, fitz!

I thought you were in CA this week?

I am

running this chat from my hotel room

you talking otday?

conference doesn't start for another hour and change

yes

The Action Bar: Front to Back

was trying to get comp ticket - did not happen

so is this conference worth going to next year?

i'd pay for tix, but not tix + cross-country travel

I'm a fairly lousy judge of that

I'm not really a conference-goer in general

ok have a great day

this conference is a bit different than others, in that it has more hardware/firmware coverage, rather than plain development

howdy, brian!

hi

need to jet - thought I would pop in and say HI

got time for a question?

brian: go ahead

have a great show

thanks!

Have you tried migrating ActivityGroups to Fragments for use in a TabActivity like setting?

I've avoided ActivityGroup like the plague

with tabs, I've long advocated views-in-tabs, not intents-in-tabs

and I've never implemented any other form of ActivityGroup

ok

off the cuff, each activity that had been in the group would turn into a fragment

what you then do with those fragments depends a bit on how you were using the ActivityGroup

second question, then. For an app that uses a database, is it advisable to open and close for each Activity that uses it in onResume/onPause or to create a singleton and somehow manage the db in another way

ah, we were just discussing that on [android-developers] today

I'm doing the former because I can't really figure a way to keep track of how to know when to close.

I need to update my Tutorials book for this

Ok, cool. Thanks for the link.

either you don't close (which, by all reports, is safe), or you use the reference-count trick outlined by one of the posts in that thread, or something

a content provider never closes, for example, so it never has a chance to close the database

but, to answer the question, use the singleton

at least if you're using background threads

which, for a database, ideally you would

BTW, a chapter on the loader framework will show up in the next Advanced Android update, probably coming out on Monday

OK. Awesome. Thanks for the time. I'll try to duck in a little earlier next time. :)

no problem -- another chat is Thursday, same time

cya.

have a pleasant day!