I ended up ditching the library. I ran into an issue where every once in
awhile, the callback would never get called. I switched to my own custom
wrapping AsyncTask wrapper. Also it seems
that http://loopj.com/android-async-http/ would have been a better choice.
On Thursday, January 17, 2013
Thanks! Yeah, I agree that AQuery doesn't seem near as powerful as jQuery.
I do know that this library uses reflection in certain instances,
particularly for callbacks in network calls. This doesn't seem to cause
issues though I just started using it.
I liked in particular the lack of
On Thu, Jan 17, 2013 at 10:19 AM, gloesch gloe...@taximagic.com wrote:
Thanks! Yeah, I agree that AQuery doesn't seem near as powerful as jQuery. I
do know that this library uses reflection in certain instances, particularly
for callbacks in network calls. This doesn't seem to cause issues
I'm curious to know if there's a general consensus about the Android Query
(AQuery) library, particularly for async calls. Has anyone out there used
it in a production environment?
http://code.google.com/p/android-query/wiki/API
--
You received this message because you are subscribed to the
It looks perhaps useful because it has lightweight options which allow
you to prototype things quickly, but it's not really the same kind of
killer JQuery is. JQuery is really nice because:
- JQuery gives you (essentially) one way to do things, if you want
something else you get a plugin.
-
5 matches
Mail list logo
