仅打印drupal field_view_field值(print drupal field_view_field value only)

 所有跨平台框架（包括HTML）通常具有相同的优点和缺点。 
 
 优点： 
 
 
 
 编写一次代码，在每个目标平台上工作相同。 
 
 
 缺点： 
 
 
 
 它的工作方式往往不是那么美妙。 
 
 
 性能通常比本机实现低。 
 
 
 有些也有他们自己的小部件集，看起来不合适。 
 
 
 由于个人平台怪癖，你仍然需要到处测试。 
 
 
 您可以通过最低公分母来访问功能。 当支持本地功能时，通常只能以一种方式访问​​它：便携式框架的方式。 这有时与目标平台的首选方式不一致。 
 
 
 如果您可能访问目标平台特有的功能，那么您将失去运行无处不在的可移植性。 
 
 
 每个所谓的“跨平台”框架本身都是一个平台。 先看一下关于怪癖的一点：现在，不必知道N个平台，你必须知道N + 1。 
 
 
 为了以多个平台为目标获得最佳效果 
 
 用一个定义良好的API来干净地设计你的核心逻辑（不使用任何UI的部分）。 使其足够普遍，可以在环境之间轻松移植。 （Objective-C和Java中的SQLite真的不同吗？） 
 
 根据目标平台的最佳实践设计您的用户界面，使其看起来很棒（并且适合）每个用户。 （对于Android，请参阅http://developer.android.com/design ）让UI通过您创建的API与核心逻辑进行交互。 

All cross-platform frameworks (including HTML) generally share the same advantages and disadvantages.
 
Advantages:
 
 
 
Write code once that works the same on every target platform.
 
 
Disadvantages:
 
 
 
The way it works is often not that wonderful.
 
 
Generally lower performance than native implementations.
 
 
Some also have their own widget set that looks out of place.
 
 
Due to individual platform quirks, you still have to test everywhere.
 
 
You get lowest-common-denominator access to features. When a native feature is supported, often you can only access it in one way: the portable framework's way. This is sometimes at odds with the target platform's preferred way.
 
 
In the event that you may access features unique to a target platform, you lose run-everywhere portability.
 
 
Every so-called "cross-platform" framework is a platform in its own right. See earlier point about quirks: Now, instead of having to know N platforms, you have to know N+1.
 
 
For best results targeting multiple platforms, I recommend the following:
 
Design your core logic (the part that doesn't use any UI) cleanly, with a well-defined API. Make it general enough to be fairly easily ported between environments. (Is SQLite really that different in Objective C vs. Java?)
 
Design your UI following the best practices of your target platforms so that it looks great (and fits in) on each one. (For Android, see http://developer.android.com/design) Have the UI interact with the core logic via the API you created.