Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Automatic registration of callbacks #5

Open
smover opened this issue Oct 12, 2016 · 2 comments
Open

Automatic registration of callbacks #5

smover opened this issue Oct 12, 2016 · 2 comments
Assignees

Comments

@smover
Copy link
Contributor

smover commented Oct 12, 2016

The goal is to register all the possible callbacks for all the objects.

There are two main mechanism to register callbacks.

  1. One is to extend the methods when the app code extends a framework class (e.g. the onCreate method for an activity object)
  2. The other is to register the callback through a specific method on a framework object.
@smover
Copy link
Contributor Author

smover commented Oct 12, 2016

@ftc just added the issue. I think we should document here how we want to implement the registration

@ftc
Copy link
Member

ftc commented Oct 14, 2016

Current plan: write code to find the callbacks which are implemented in MUSE corpus apps using either Graph Extractor or Feature Extractor. These can be detected by finding methods implemented in the app which are inherited from framework objects or from interfaces.

finding registration methods:

  • look for methods which say "set.*Listener"
  • look for methods where something of the type of the framework class the callback is inherited from is taken as a paremeter

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants