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

Feature request: modularization #28

Open
jakubvimn opened this issue Apr 12, 2017 · 1 comment
Open

Feature request: modularization #28

jakubvimn opened this issue Apr 12, 2017 · 1 comment

Comments

@jakubvimn
Copy link

Currently all the extensions are in one library. This library has a dependency to appcompat. So if the library is used by a project that doesn't use appcompat, it will be automatically added (unless it's explicitly excluded).
It would be good to divide the library to a set of libraries that contains extensions for each module, e.g.

  • android classes
  • support v4
  • appcompat

Additionally, a no-code module could be created, which can contain dependencies to all the separate modules. It's the same approach that is currently used e.g. by Google Play Services.

@pawegio
Copy link
Owner

pawegio commented Apr 12, 2017

It is planned, however currently I have no time to perform this separation on my own.

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

2 participants