Closed wangmengyan95 closed 8 years ago
It makes sense. I just want to use ParseQueryAdapater
, and I don't have any interest on the Login part. Regarding the breaking change, I don't care changing my imports from com.parse
to com.parse.widget
: it's just an small change (Find and Replace).
We are a bunch of people waiting for ParseUI to be published to maven and this is the last issue to fix so please take a decision and act now. It's a pain to move jars and folders up and down.
Since we add
ParseImageView
andParseQueryAdapter
to the repo, it make no sense to still keep them all in one login module.We propose to split the
ParseLoginUI
into two modules.ParseUI-Login
module for all login related classes.ParseUI-Widget
module forParseImageView
,ParseQueryAdapter
and future widgets.For packaging, in
ParseUI-Login
, all classes are still under packagecom.parse.ui
for backward compatibility. InParseUI-Widget
,ParseImageView
andParseQueryAdapter
are incom.parse
, the future widgets will be incom.parse.widget
.Check PR #65 for details.
Please leave you opinions, suggestions or any thoughts under this issue.
Thanks.