hello, Yurii

how can I help you today?

Hi Mark, how are you?

I'm about to implement new Drawer pattern, and want to ask your advice

should I go with one activity and multiple fragments approach or parent activity ?

IMHO, the nav drawer pattern does not imply one or the other

hence, I would use whatever you would have used without the nav drawer

but I want to use drawer to navigate between activity and want it to be available in all activities I will have a lot of code dublication, don't I?

not necessarily

most of the Java code could be in a base class or a helper class

the DrawerLayout definition itself could be driven in part by <include> tags

ok let say I have activities A1 and A2 and drawer in fragment Drawer,

moreover, the decision to go with several activities or one activity/several fragments is a MAJOR architectural decision

right!!! <include> how could I forgot about this one :) Thank you

code duplication is one criteria, but not the sole one, or (IMHO) even the primary one

what is the primary one in your opinion?

I don't know that I can name one primary one

navigation flows (e.g., how the BACK button works), entry points (e.g., what <intent-filter> elements you need), memory management (one fat activity?) all play a part

thanks, another question, have you seen https://github.com/coocood/VContentProvider ?

I think I clicked on that link before, but I have never downloaded or used it

is there any easy way to create ContentProvider? except standard one?

I do not know what you mean by "standard one"

one by documentation

since I avoid content providers wherever possible, I have not researched third-party code to try to simplify their creation

how do you prefer have UI update? implementing Observer by hand?

I am a fan of the event bus approach: Otto, greenrobot's EventBus, LocalBroadcastManager, etc.

you could call that "implementing Observer by hand"

what is your opinion on Volley?

it is undocumented and unsupported

otherwise, it's cool

of the current cool HTTP wrappers, I'd lean towards Retrofit and Picasso if they fit your needs

but if you have HTTP operations that aren't images and aren't Retrofit-compatible REST, Volley is worth considering

I expect to cover all of these in a chapter in the book in the next few months

that is great news, will wait for that. Another question will be on encryption

I haven't read encryption chapter in book yet, but I can see that there is openFile()m so basically I will be able to encrypt all the date and serv it unencrypted state to "Video Player" and Doc reader?

do you mean from a ContentProvider?

yes

then for a document, that is very possible

while I do not do encryption, I show how to serve up streams via pipes and openFile()

it's one of the few things I like about ContentProvider...

however, video is a problem, because video players need to traverse forwards and backwards

and ContentProvider-supplied streams are forward-only

hence, I'll be surprised if you can get video playback to work

even audio won't work for all codecs

so basically only device encryption can provider that workflow?

*provide

I am sorry, but I do not understand your question

for example I've got video file from back-end, encrypted it and stored in file system

I have no idea how to handle that scenario

sorry

now I want to play it to user, user will have to w8 till whole 50mb file will be decrypted before playing?

no worries, you already helped a lot, Thank you for such a great book.

I am glad that you like it!

do you plan release a paper version? I'd be happy to have one on my table

at over 2300 pages, it's a bit impractical to print

moreover, it is not very cost-effective to print, either

however, there is no DRM on the book, so you are welcome to print it out yourself

just don't tell any trees that you're doing it, or they might get mad

:-)

:)

looks like I will stack with PDF format

it is just search takes a while in the PDF format.

search will be slower in print :-)

if I am lucky, I will get time in July to update the APK edition with a full-text index for rapid keyword searching

that will be terrific