Hi TreKing, Thanks for replying. The reason I am doing so is I need to
execute a common piece of logic when some action is taken from components
in first activity or any other components from other activities. So based
on actions from components from multiple activities I need to route them
via
On Sun, Jan 4, 2015 at 1:34 PM, Ji wrote:
> The reason I am doing so is I need to execute a common piece of logic when
> some action is taken from components in first activity or any other
> components from other activities. So based on actions from components from
> multiple activities I need to
Static methods makes sense if I have to access the abstracted logic in only
my application, but if I have to expose this logic to be used by any other
activity of different application then bound service approach will help
isn't it. Please feel free to share you opinion it will help to get my
3 matches
Mail list logo
