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

Upgrade default API Level to 16 #43

Closed
guersam opened this issue May 27, 2013 · 4 comments
Closed

Upgrade default API Level to 16 #43

guersam opened this issue May 27, 2013 · 4 comments

Comments

@guersam
Copy link
Contributor

guersam commented May 27, 2013

I'm trying to merge support-v4 package into this repo using SBT's multiple project feature to provide consistent Scaloid API.

Unfortunately, current supported API level is 8 only which causes when extracting support-v4-r7 classes due to that it requires Android 4.0.1.2 at least.

For 2.0 release, I suggest increasing API level to 16 and providing support-v4 in this repo because most famous third-party libraries support it.

guersam added a commit to guersam/scaloid that referenced this issue May 27, 2013
- Upgrade API version to 16 (pocorall#43)
- Initial 'support-v4' wrapping
- Improved listener extraction
guersam added a commit to guersam/scaloid that referenced this issue May 27, 2013
Changes:
- Upgrade API version to 16 (pocorall#43)
- Initial 'support-v4' wrapping
- Improved listener extraction

Todo:
- Extract android classes only once
- Improve 'support-v4'
@pocorall
Copy link
Owner

I chosen Android Lv8 because it covers 98 percent of activated devices.

To be accepted by wide range of Android developers, Scaloid should be run on most of the devices.

@guersam
Copy link
Contributor Author

guersam commented May 28, 2013

From Android developer guide:

Updates to the framework API are designed so that the new API remains compatible with earlier versions of the
API. That is, most changes in the API are additive and introduce new or replacement functionality. As parts of the
API are upgraded, the older replaced parts are deprecated but are not removed, so that existing applications can
still use them.

Usually using higher level of SDK doesn't prevent running on older devices. For example, even ActionbarSherlock uses platform version 4.0.1.2 for compilation (here's pom.xml) and it runs on my old GingerBread device.

My suggestion is as follows:

  • Compile with reasonably recent SDK version.
  • Keep Android dependency scope as 'provided'
  • Macro-based workaround for backward compatibility (We can determine if given LayoutParams class has MATCH_PARENT in compile time)

Then we don't need to publish Scaloid 2.0_8, 2.0_16, or etc. simultaneously.

@pocorall
Copy link
Owner

OK, thank you for your good suggestion 👍

@placrosse
Copy link
Contributor

+1 on this suggestion

On Tue, May 28, 2013 at 9:53 AM, Sung-Ho Lee notifications@github.comwrote:

OK, thank you for your good suggestion [image: 👍]


Reply to this email directly or view it on GitHubhttps://github.com//issues/43#issuecomment-18551664
.

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

No branches or pull requests

3 participants