AOP support

by Raja Nagendra Kumar » Sat, 02 May 2009 23:15:55 GMT


Sponsored Links
 Hi,

Does AOP support with in Android sdk. If no, is it possible to use the
exsiting AOP  impl. and use them to bulild the application. Does AOP
break Andriod applications design in any way.

Any URL to know more on this topic would be very useful.

Regards,
Raja Nagendra Kumar,
C.T.O
www.tejasoft.com
--~--~---------~--~----~------------~-------~--~----~



AOP support

by Raja Nagendra Kumar » Mon, 04 May 2009 14:30:59 GMT


 Any inputs please.. we are looking for Aspect's approach to enforce
login and security etc..
Any of the forum members have any experience towards this pl. share..

Regards
Raja Nagendra Kumar,
C.T.O
www.tejasoft.com
--~--~---------~--~----~------------~-------~--~----~


Sponsored Links


Other Threads

1. How service get notified when "stopService" is called

AFAICT, there isn't any way exposed to the SDK to be notified when
stopService is called.  However, there is an onDestroy() method that you can
implement that Android calls when it is about to get rid of the service, but
I don't think that is necessarily what you are looking for.


----------------------------------------------------------------------
There are only 10 types of people in the world...
Those who know binary and those who don't.
----------------------------------------------------------------------





>

2. How can a parent handle touch events BEFORE its children?

I have a custom view (A) that contains a ViewFlipper, which flips
between three custom views (B1, B2, B3).  Each B view is a
LinearLayout containing a TextView and a GridView.  The problem is
that i need touch events on the GridView to be handled by the A view.
This is so that fling events on any GridView get handled by the
ViewFlipper.

It seems simple enough... just make the touch listeners for the B
views and GridViews return false, right?  Wrong.  It doesnt work.  The
B.onTouchEvent() is never called by touch events on a GridView and
neither is ViewFlipper.onTouchEvent().   Strange but true, and I have
the Logs to prove it.

I tried passing an instance of the parent A view to each of the B
views so that when a touch event happens I can dispatch all touch
events to the parent A view.  The result...an infinite loop and stack
overflow because the A view first passes the event back to its
children.

How do I get a view to handle all of its touch events without passing
those events to its children?  In truth, i dont need children to
respond to ANY touch events at all.  Ideally, I would like ALL touch
events to be handled by the A view and never by any of its children.
Is there a way to force this?

Thanks.

-- 

3. Video Chat

4. feedback from an Alert dialog

5. Advice needed for app navigation methods

6. APK not visible in market for HTC Tattoo Android Phone ?

7. The method versionName() is undefined for the type PackageInfo