hello, Bob!

Hi

how can I help you today?

hello, Jeff!

Bob: do you have a question?

Hi Mark

yes

but I don't want to interrupt. I can wait a few minutes

well, we'll come back to Bob after yours, since he has not yet chimed in

Jeff: go ahead

I made an update to eclypse and now I getting some syntax. GINGERBREAD logic isn't being recognized, I had to convert some case statements to if-else, and now I'm having trouble where the R file isn't being created.

The code originally worked fine.

Bob: what do you mean by "made an update to Eclipse"?

zncroid SDK manager

android

OK, I do not know precisely what you did, so we will leave that alone for now

if the R file is not being created, there is a problem with either one of your resources, or with your manifest

Gingerbread can not be resolved to a field

ok

thanks

my question, which you can answer in any order, is what is a good way to store phone specific settings. For example, I need to rotate a picture 90 degrees with certain phones. Right now, I have code that would fail a CS class. I'm thinking of putting it all in a /res/xml file but then I have parse and find a specific phone. Is there some common solution before I go at this?

do you mean Build.VERSION_CODES.GINGERBREAD?

I don't want to reinvent the wheel

yes

Bob: either your build target (Project > Properties > Android in Eclipse) is missing, or is set to something earlier than API Level 9

OK thanks

depending on what you have there, that might also explain the problems that you are experiencing with your R class

so, I would check there

Jeff: by "phone specific settings", do you mean "device model specific settings"?

or do you mean "settings for this app installation on this phone?"

OK thanks

or something else?

device model specific settings

OK

I am not aware of a common solution for it

in fact, I need to invent one

I have the same sort of issue in my CWAC-Camera library

lots of model-specific quirks to work around

yes, right now I have lots of ifs

I'd like to do it in xml

That was the Gingerbread issue. I had it set to 2.2

what I am planning on trying is name-mangling the MODEL and MANUFACTURER to get a resource name (e.g., R.xml.{{MANUFACTURER}}_{{MODEL}})

and seeing if that exists

if not, I will try R.xml.{{MANUFACTURER}}

ooh - that's nice

and if that's not there, assume there are no model-specific overrides

most manufacturer and model codes that I have seen would work in a resource name

though I'll need to run a few replaceAll()s to be sure

then will you have a file for R.xml.{{MANUFACTURER}}?

if there's something that seems universal for a manufacturer's devices, yes

so you open the file and parse the specifics?

right now, I think I got rid of my last of those, but it could crop up again

correct

right now, the specifics are subclasses of a DeviceProfile

why not put them all in one big xml file with inner tags for specific devices

I'll convert that to XML and parse them into a SimpleDeviceProfile that holds the values

it's easier for others to contribute files if they are independent

and, there could be a lot of them over time

but your approach would work

excellent point about others contributing files

Thanks

Uno: hi! do you have a question?

Uno: do you have a question?

hello

OK, Bob, back to you: do you have another question?

Uno: do you have a question?

OK, does anyone have a question?

hmm.. suddenly i forget what i want to ask. let me think

i just still confuse about the difference of tardgetsdk and buildsdk

what is the best practice to set two set those parameters

I do not quite know what you mean by either of them

is "buildsdk" referring to the version of Android that you are compiling against? what you set in Project > Properties > Android in Eclipse?

(BTW, if anyone else has a question, feel free to chime in)

yes build sdk is project > properties

OK, typically you will choose something relatively new

the real rule is: you want to choose something that has all of the classes and methods that you want to use in your code

so it does not have to be the absolute latest one, but you probably do not want one from 2009, either :-)

is "tardgetsdk" referring to android:targetSdkVersion?

yes tartgetsdk=android:targetSdkVersion

choosing a targetSdkVersion is a bit of an art

more than a science

at least for your initial value, when you start the project

typically, I will choose the latest version of Android, unless I have a strong reason to do something else

however, as months go by, and new versions of Android are released, you will need to consider whether or not to increase your targetSdkVersion

Well I got it clean compiled and working again. Thanks for your help:)

Bob: glad to hear it!

I just have 1 more question

Uno: if you read http://developer.android.com/reference/android/... you will see what the changes are that will occur when you set your targetSdkVersion to a particular API level

Bob: go ahead

for buildsdk: does it mean to set as lower sdk as possible ?

Uno: no

What is a good software (cheap) that I could use to create a custome icon for my apps.

as long all the class and methods are included in that sdk ?

Uno: that is the minimum requirement

however, bear in mind that the older of an SDK you use, the less features and functionality your app can have for newer devices

what you do not want to do is only use stuff from four years ago

as your app will look and behave "out of date" right away

that being said, so long as your app works, you can do whatever you want

Bob: for serious icon work, use a graphic designer

whether an individual or some online service

OK thats what I've been looking for

beyond that, everyone has their own preference, and so my approach (Inkscape) is not necessarily common

(BTW: Jeff, if you have a question, feel free to chime in)

I just began looking at inkscape

I need to look at their docos

I am fan of vector art, and Inkscape is one of the few open source vector art programs out there, particularly for Linux

let say, i want to include google mobile ads that have the minimum sdk=9, and i want to add navigator drawer too. what do you suggest for buidsdk and targetsdk?

Mark Thanks

Uno: well, personally, I have largely given up development for devices older than API Level 15, for new apps

they represent less than 20% of the market, and that market share is declining

so, I would choose at least API Level 14 as my build target

but, if you still want to support API Level 9-10, DrawerLayout will work with the AppCompat action bar (and, with a little work, with ActionBarSherlock as well)

Have a great evening all:)

ActionBarSherlock will require a build target of API Level 14 or higher; I forget what AppCompat requires

Bob: see you around!

build target= buildsdk ?

Uno: yes, build target = buildsdk

then the targetsdk is the latest right ? so targetsdk=19 ?

yes, that is what I would start with as my targetSdkVersion

i prefer to use AppCompat rather than actionbarsherlock

to support lever 9

while AppCompat will support API Level 7 on up, the build target (what you compile against) may be higher

bear in mind that the build target is *not* the oldest version of Android that you support

that is the android:minSdkVersion

actually what is the disadvantage if i choose build target = the latest sdk ?

there is no disadvantage

hmmm

so long as your android:minSdkVersion is set to be the oldest version of Android that you support, your build target can be whatever level you want, including the latest

if you try using classes and methods that are available in your build target, but are newer than android:minSdkVersion, the build tools will yell at you

that's where you will see @TargetSdk annotations, to tell the build tools that you know what you are doing :-)

little bit clearer

can i have another question?

sure, go right ahead

this is about @targetsdk and subclasses, i have to search the source code in your book first... please wait

Uno: the chat is almost over -- do you have another question?

hmm.. i can't find the source code... maybe next time

OK

is there anything else I can answer for you today?

see you next

can i save the chat?

Uno: the chat transcript will be archived at http://commonsware.com/office-hours/ shortly after the chat ends

Hi Mark - just wanted to offer that I would contribute the phones I test to your configuration framework if you create it.

um, are you working with the camera?

yes, a lot

oh

well, keep tabs on my CWAC-Camera library

if you recall, we swapped email about the Droid Mini

OK

well, no offense, but there's more than one Jeff in the world :-)

huh

;)

and I am hoping to work on that Droid Mini bug tomorrow or Saturday

I have a big release coming up for the library

happy to contribute - I'll watch your library

sounds great!

and that's a wrap for today's chat

I just rotated the picture after taking it

good night

the next chat is Monday at 10am

it's morning now here.. :D

US Eastern Time, that is

have a pleasant day!

thanks