hi :)

Hi!

hello, Gabriele and Teo!

Thanks for the book Mark

Teo: it looks like you got in first, so... do you have a question?

you're very welcome!

yes! I'm confused with build types and flavors.

can you be more specific?

1st excuse my bad English. If I wanna have a version with lets say crashlytics. Then this will be a build type ?

I don't know

build types model your development process

product flavors model your distribution channels

so, when would you use a build with Crashlytics, and when would you use a build without Crashlytics?

a debug build without crashlytics for me and a debug build with crashlytics so I can test it with friends.

then that sounds like a custom build type

let me take a question from Gabriele, and I will be back with you shortyl

ok, thanks.

er, shortly

Gabriele: your turn! do you have a question?

As you probably remember, I'm writing a small irc client. I'm using the same viewPager to swipe Channels and/or Private messages. I have, also, an edittext at bottom, where users write their messages; they must send these messages to the active fragment (which is a channel window or private message window). So, to send the message to the right recipient I must associate each fragment to a "user private window" or to a "channel window", how can I achieve that? I'm already listening OnEditorActionListener to detect when the user sends a message, but even if I detected it, I don't know which is the right action to accomplish, because I don't know which is the current fragment and the user/channel it is associated.

"I don't know which is the current fragment" -- you know which is the current item via getCurrentItem() on ViewPager

figuring out which fragment that it is will be up to you

it might be a bit simpler with my ArrayPagerAdapter

why simpler?

because FragmentPagerAdapter does not give you a way to find out the *existing* fragment for a given position

and, IIRC, ArrayPagerAdapter does

(and if it doesn't, I need to add it...)

so I should access mypageradapter from inside my listener or you think it's better to use event model and let the pageradapter manage this event?

IMHO, PagerAdapter is not a controller, so it would not handle the event

so, you either need a way to get the fragment for the current index, or go an event bus route and arrange to register/unregister for the event properly with the fragments

so the visible page is the one with the registered subscriber for the event

hm

so inside my onEditorAction method, I should be able to access the pager adapter?

(if choosing the first way)

if that method is on the activity, then yes

assuming the activity is hosting the ViewPager

let me take a question from Teo, and I will be back with you in a bit

sure, thanks

Teo: your turn! do you have another question?

I don't have a question to ask at the moment.

OK

if you come up with a question, let me know, and I'll swing back to you

ok

Gabriele: over to you!

no, the method isn't on the activity, I have the listener in a separate "java" class

make it an inner class of the activity, or have it hold the PagerAdapter, or something

maybe the inner class is better, yes

considering it's strictly related

another thing, I'm using eventbus register insidea java class, but I have to unregister it, I thought that when the activity that has the object reference is called stop() or something, I can call unregister to that class and unregister it, is this a decent way of doing it?

um, I do not know, as I do not completely understand your situation

I recommend registering and unregistering tied to the hosting component's lifecycle methods

I have an activity which holds a java class, A

this class is registering (register(this)) to an event

but then I have to unregister... how should I do it? I thought: when the activity stop()'s get called, I call stop() to the object A, too?

in terms of timing, stick to the lifecycle method pairs

*when* are you registering the object?

(or there is a better way to register/unregister the object of type A?)

I'm doing it when the activity is created

that feels perhaps a bit early, but if that's what you want, unregister in onDestroy()

if you want to unregister in onStop(), then register in onStart()

if I remember correctly I'm not sure that onDestroy gets called, right?

the only times it will not get called are if your process is terminated (in which case, the whole event bus is gone) or you have an unhandled exception (in which case, you have other problems)

and if the app gets "deleted" from the recent apps, with a swipe, what happens?

the process is terminated

in which case it doesn't matter, because event bus gets too

right

ok, thank you Mark

I don't have questions anymore, today! Thanks, as always!

you are very welcome

good continuation and have a nice day (if it's not too late, to you!)

see you the next time :)

the next chat is next Tuesday at 7:30pm US Eastern Time

I have to leave now. I'll be back next Tuesday with questions. Thank you

have a pleasant day!

you too!

hello, Jim

Jim: Teo is currently out of questions, so, do you have a question?

Hello,

do you have Gradle installed? if so, what version?

It just updated itself to 0.8.9

that's Android Studio, not Gradle

I need to point out on the GitHub repository, and in the book, that you need your own installed copy of Gradle 1.12 to be able to import the projects

Is that the standalone gradle, not the plugin?

yes, from gradle.org

OK, I just started, and I was confused about plugin vs standalone. Will both play together

I am not sure exactly what plugin you are referring to

There is a plugin for gradle installed with the Android Studio bundle>

yes, that plugin will work with Gradle installed from gradle.org

OK, I will install 1.12 from Gradle. Thanks