blocks|key|292255|text|如果你计划只在4.0下开发，我建议使用本地库，因为可执行文件会变得更小。确实，在早期版本中您可能会遇到bug问题，但我认为大多数问题都应该是相当容易解决的。另外，兼容性库应该映射到本机片段，以防你在4.0或更高版本上运行。所以你最终可能不得不与这些类型的问题作斗争。支持库的问题是，有很多类出现了2倍(一次在支持包结构中，一次在“本机”包结构中)，这使得开发变得有点麻烦。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|292256|然而，如果你也想发布4.0之前的应用程序，那么就没有办法绕过支持库了。此外，由于2.3上的用户约占所有用户的38%25，因此将此操作系统版本包括在内可能具有商业意义。在这种情况下，您可以将support库与Jake+ActionBarSherlock结合使用(或在最终发布后与googles+ActionBar库结合使用)。|292257|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

IMHO if you are planning to develop for 4.0 only, I would recommend going with the native libraries since the executable will get smaller. It is true that you might run into problems of bugs in early versions, but I think most of these should be fairly trivial to work around. Also the compatibility library is supposed to map to the native fragments in case you are running on 4.0 and higher anyway. So you might end up having to struggle with these kinds of problems anyway.
The problem with the support libraries is that you have a lot of the classes appear 2x (once in the support package structure and once in the "native" package structure) which makes development a bit more cumbersome.

However, if you want to also release your app pre 4.0 then there is no way around the support library. Also since there are about 38% of all users on 2.3 it might make business sense to include this OS version. In such a case you can use the support library in combination with Jake Wartons ActionBarSherlock (or with googles support ActionBar Library once it is finally released).

blocks|key|75004|text|根据我的经验，在所有Android设备上使用相同的片段实现是一个很大的优势。当在Android4.0上使用本地片段保存状态时，我无法摆脱所有的NullPointerExceptions，随着支持库的消失，它们都消失了。此外，到目前为止，我看不到这种方法有任何缺点。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|75005|所以我现在对我自己的问题的回答是:当为Android4.x进行开发时，使用支持库中的片段是一个好主意。支持库修复了旧的片段实现中仍然存在的错误，并且经常使用更多的错误修复进行更新。|75006|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

From my experience, using the same fragment implementation on all Android devices is a great advantage. I could not get rid of all NullPointerExceptions when state is saved on Android 4.0 using native fragments, with the support library they are all gone. Also I could not see any disadvantage so far with this approach.

So my answer to my own question is now: When developing for Android 4.x, using the fragments from the support library is a good idea. The support library has bugs fixed that are still present in older fragment implementations and is frequently updated with more bug fixes.

blocks|key|75040|text|坚持使用SupportFragment的一个重要原因是，在API17之前，您不能访问ChildFragmentManager。支持库将为您提供子片段管理器的支持版本。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|75041|如果你有包含其他片段的片段，这就成了一个大问题。这在非常复杂的tablet应用程序中很常见，并且/或者您的整体架构要么基于选项卡式布局，要么使用导航抽屉。|75042|entityMap^0|4|F|16|K|0|0^^$0|@$1|2|3|4|5|6|7|J|8|@$9|K|A|L|B|C]|$9|M|A|N|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|O|8|@]|D|@]|E|$]]|$1|H|3|-4|5|6|7|P|8|@]|D|@]|E|$]]]|I|$]]

One big reason to stick with the <code>SupportFragment</code> for a while is that you do not have access to the <code>ChildFragmentManager</code> until API 17. The support library will give you a support version of the child fragment manager.

This becomes a big deal if you have fragments that contain other fragments. This is common in tablet applications with a good deal of complexity and/or your overall architecture is based on either a tabbed layout or uses the navigation drawer.

I am developing an app that supports Android >= 4.0. It uses fragments from the <code>android.app</code> package. As I am facing problems with the older fragment implementation in 4.0, like <a href="https://stackoverflow.com/questions/13540712/app-crashes-on-super-onsaveinstancestate">this one</a>, that are already fixed in the support library, I am considering switching back to the fragment implementation from the support library to get a more reliable and consistent implementation.

What is your opinion on this? Are you using fragments from the support library, even though they are already available, when developing for Android 4?

Fragment or Support Fragment?

Android

我正在开发一个应用程序，支持安卓>= 4.0。它使用android.app包中的片段。由于我在4.0中遇到了一些问题，比如，在支持库中已经修复了这些问题，所以我正在考虑从支持库切换回片段实现，以获得更可靠和一致的实现。你对此有何看法？在为Android4进行开发时，您是否正在使用支持库中的片段，即使它们已经可用？

问片段还是支持片段？
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问片段还是支持片段？EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问片段还是支持片段？
EN