hello, Angelos!

how can I help you today?

Hello Mark, I have a question about async tasks and configuration changes. Up to now I'm using asynctasks as part of a retained fragment which is kept in configuration changes. Is this still the recommended way to handle them? I'm not 100% developing on android so I'm not sure if something else came up to tackle this

no, AFAIK, if you're using AsyncTask, a retained fragment is still the best solution

now, more and more developers are moving away from AsyncTask into other solutions (threads with an event bus, Rx, etc.)

:( ok

where can i find some more info on this ? I'm willing to rewrite the code because managing the fragments is quite a nightmare

If i remember correctly, on your book example for event bus you were still using a retained fragment (model) ?

in your question, what is "this"?

sorry, 'this'= event buses

the tutorial is using a model fragment not for managing async tasks, but for retaining model data across configuration changes

that too has not changed

however, there is no requirement that a background operation have to produce something that might need to be retained across configuration changes

I'm not sure exactly where the "nightmare" comes into play with a model fragment, though I suppose there can be one

fragments overall, for GUI work, can get complex, but a pure model fragment is pretty simple

in terms of how to use event buses, I use greenrobot's EventBus in a lot of samples

however, I do not remember off the top of my head which ones might not involve a retained fragment

the 'nightmare' is for my retained fragments, I'm using 1 retained fragment for each ui fragment. So if a have a SongsFragment i also have a SongsDataFragment (retained), ArtistFragment an ArtistDataFragment etc

I usually keep the model fragment as being a per-activity thing

not a per-fragment thing

each fragment could contribute to that model, though, for things that are unique to it

but that doesn't require a separate model fragment for each UI fragment, any more than you need a separate server for each UI fragment that does network I/O

ok Mark, I'll have a look greenrobot

one more question, which image library do you suggest? I was using universal image loader which is now deprecated

they deprecated UIL?

I missed that

I think I still have a book example using it

:-(

anyway, my go-to solution is Picasso

yeah, the developer doesn't have enough time to support it.

yup, all too common

that was all Mark, thank you for your support

that doesn't mean you can't use it, but it's definitely something to move off of eventually, either to a maintained fork or to another library

you are very welcome!