blocks|key|1739837|text|这里有一些建议。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1739838|我相信这是一个好主意，不仅因为显而易见的设计原因，而且还因为它将使向后兼容变得更容易。例如，Support+Package有助于将推荐的设计元素带到旧平台，而此包的新版本可能会使其与最新的设计指南更接近。|offset|length|1739839|1739840|即使你不认为你现在对碎片的需求很大，但它们是Android设计的未来，大屏幕Android的数量可能会增长得非常快。尽管它们增加了一些额外的复杂性，但我认为它们通过将视图从活动中分离出来，鼓励了良好的设计。|1739841|允许通过Support+Package+(也称为兼容性库)使用片段。这相当简单，我在做这件事时没有遇到任何问题。只需确保您的导入如下所示：|1739842|import+android.**support.v4**.app.Fragment;|code-block|syntax|javascript|1739843|1739844|1739845|第三，使用文档中描述的主题启用ICS/HC+actionbar。为此，您需要使用ActionBarSherlock或ActionBarCompat示例。这两个都是很好的解决方案，但它们增加了应用程序的复杂性。在当前版本的支持包中没有actionbar，这显然是由于技术问题，但我怀疑他们正在试图解决这些问题。|1739846|因此，如果你想保持简单，考虑到你的应用程序在ICS和HC上有一个actionbar是合理的，而在更早的平台上没有actionbar。实际上，在过去的几天里，Android+Dev+blog发布了一篇文章，专注于在这种情况下管理菜单和操作项。|1739847|另外，考虑到稍后在你的应用程序中添加一个预蜂窝actionbar+(例如，使用ActionBarCompat示例中的代码)不会那么糟糕--在我看来，更容易一些，然后再重新编写代码中的片段。|1739848|最后，请注意，您将需要使用最新的SDK，以便可以引用诸如holo主题(用于ICS+actionbar)和showAsAction="ifRoom"元素等元素，因此您的清单将包含以下内容：|style|CODE|1739849|<uses-sdk+android:minSdkVersion="8"+android:targetSdkVersion="15"+/>|1739850|entityMap|0|LINK|mutability|MUTABLE|url|http://developer.android.com/sdk/compatibility-library.html|1|2|http://actionbarsherlock.com/|3|http://developer.android.com/resources/samples/ActionBarCompat/index.html|4|http://android-developers.blogspot.com/^0|0|1A|F|0|0|0|0|4|F|1|0|0|0|0|14|H|2|1M|F|3|0|26|G|4|0|0|1G|L|0|0^^$0|@$1|2|3|4|5|6|7|1I|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|1J|8|@]|9|@$D|1K|E|1L|1|1M]]|A|$]]|$1|F|3|-4|5|6|7|1N|8|@]|9|@]|A|$]]|$1|G|3|H|5|6|7|1O|8|@]|9|@]|A|$]]|$1|I|3|J|5|6|7|1P|8|@]|9|@$D|1Q|E|1R|1|1S]]|A|$]]|$1|K|3|L|5|M|7|1T|8|@]|9|@]|A|$N|O]]|$1|P|3|-4|5|6|7|1U|8|@]|9|@]|A|$]]|$1|Q|3|-4|5|6|7|1V|8|@]|9|@]|A|$]]|$1|R|3|S|5|6|7|1W|8|@]|9|@$D|1X|E|1Y|1|1Z]|$D|20|E|21|1|22]]|A|$]]|$1|T|3|U|5|6|7|23|8|@]|9|@$D|24|E|25|1|26]]|A|$]]|$1|V|3|W|5|6|7|27|8|@]|9|@]|A|$]]|$1|X|3|Y|5|6|7|28|8|@$D|29|E|2A|Z|10]]|9|@]|A|$]]|$1|11|3|12|5|M|7|2B|8|@]|9|@]|A|$N|O]]|$1|13|3|-4|5|6|7|2C|8|@]|9|@]|A|$]]]|14|$15|$5|16|17|18|A|$19|1A]]|1B|$5|16|17|18|A|$19|1A]]|1C|$5|16|17|18|A|$19|1D]]|1E|$5|16|17|18|A|$19|1F]]|1G|$5|16|17|18|A|$19|1H]]]]

Here are some suggestions.

First, pay attention to the new <a href="http://developer.android.com/design/index.html">Android Design guidelines</a>. I believe this is a good idea, not only good for the obvious design reasons, but also because it will make backward compatibility easier. For example, the <a href="http://developer.android.com/sdk/compatibility-library.html">Support Package</a> helps bring recommended design elements to old platforms and new revs of this package will likely bring it into closer alignment with the latest design guidelines.

<hr>

Second, use <a href="http://developer.android.com/guide/topics/fundamentals/fragments.html">fragments</a>. Even if you don't think you have much need for fragments now, they are the future of Android design and the number of large screen Androids is likely to grow very quickly. And though they add some extra complexity, I think they encourage good design by separating the view from the activity.

Enable the use of fragments via the <a href="http://developer.android.com/sdk/compatibility-library.html">Support Package</a> (also known as the compatibility library). This is fairly simple and I have not encountered any problems doing this. Just make sure that your imports look like this:

<pre><code>import android.**support.v4**.app.Fragment;
</code></pre>

so that you are getting them from the support package rather then calling the native ICS API's directly.

<hr>

Third, enable the ICS/HC actionbar using themes as described in the docs. Note that this does not give your app an actionbar on pre-Honeycomb platforms. For that you either need to use something like <a href="http://actionbarsherlock.com/">ActionBarSherlock</a> or the <a href="http://developer.android.com/resources/samples/ActionBarCompat/index.html">ActionBarCompat</a> sample. Both are good solutions but they add to the complexity of your app. There is no actionbar in the current rev of the support package, and this is apparently due to technical issues, but I would suspect that they are trying to resolve those issues.

So, if you want to keep is simple, consider that it is reasonable for your app to have an actionbar on ICS &amp; HC, and no actionbar on earlier platforms. Actually, the <a href="http://android-developers.blogspot.com/">Android Dev blog</a> had a post in the last few days that focussed on managing menus and action items under these circumstances.

Also, consider that adding a pre-Honeycomb actionbar to your app later (e.g. using the code from ActionBarCompat sample) won't be that bad - much easier, in my opinion, then reworking your code for fragments later.

Finally, note that you will need to use a recent SDK so that you can refer to elements such as the holo theme (for the ICS actionbar) and the <code>showAsAction="ifRoom"</code> element, so your manifest will include something like:

<pre><code>&lt;uses-sdk android:minSdkVersion="8" android:targetSdkVersion="15" /&gt;
</code></pre>

Android 4.0 (ICS) has lots of <a href="http://developer.android.com/design/patterns/pure-android.html" rel="noreferrer">new UI guidelines</a> which are great. The problem is that going forward, I'm not sure how to build an app for Android 4.0 and make sure that the app looks the same/similar on devices running Android 2.2 and 2.3.

There is the <a href="http://developer.android.com/sdk/compatibility-library.html" rel="noreferrer">Android compatibility library</a>, and a <a href="http://developer.android.com/resources/samples/ActionBarCompat/index.html" rel="noreferrer">backwards compatible Action Bar</a>, but I was looking for a more concrete solution for porting post-ICS apps to pre-ICS phones.

Am I on the right track? Anyone have any thoughts?

How to make Android 4.0 apps backwards compatible?

Android

Android4.0 (ICS)有很多很棒的。问题是，展望未来，我不确定如何为Android 4.0构建一个应用程序，并确保该应用程序在运行Android 2.2和2.3的设备上看起来相同/相似。有和，但我正在寻找一种更具体的解决方案，用于将后ICS应用程序移植到前ICS手机。我在正确的轨道上吗？有人有什么想法吗？

问如何让Android 4.0应用程序向后兼容？
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问如何让Android 4.0应用程序向后兼容？EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问如何让Android 4.0应用程序向后兼容？
EN