MotionApps: WebOS, Classic Q&A

oooocoooo

MotionApps: WebOS, Classic Q&A

/ D) H) g. H5 R& g8 v/ z+ W$ q# g

by PalmWebOS.org on April 13th, 2009

Last week there was quite a stir when folks noticed a little icon named “Classic” appeared in a “look but don’t touch” video demo of the Palm Pre, creating speculation that WebOS would support Palm OS applications. That rumor was verified as fact when MotionApps announced their “Classic” application and it got a brief video demonstration. But the information starved Palm enthusiasts demanded more and MotionApps - the company who made the “Classic” application - was bombarded with questions.
5 D4 m* }% H" e, e) XNow we’ve got answers.
0 r2 H+ B% s  ?4 T, |In a blog post on the company’s website, MotionApps answers detailed and technical questions about the Classic application. We’ve copied and pasted the Q&A below for your convenience, but do them a solid and hit up their original Q&A article to show them some love for the transparency!

7 q* `5 E# t' q* F  _

Q: What is the main difference between Classic running on webOS hardware and “real” PalmOS?
A: Most important difference between the two is that the Classic is an application for webOS running in parallel with other webOS apps, while the PalmOS running on Treos and Centros is the operating system of those devices. This means that Classic cannot take the full and unlimited control of the hardware it is working on. This imposes certain rules of good behavior that Classic must comply with – for example, Classic cannot turn off the device or network which normally is a responsibility of an OS, simply because there may be some other webOS apps running outside of it that are using the same services at the same time. Unlike this, on “real” PalmOS devices, there can be nothing else running in parallel with the operating system, so in that case PalmOS can and should coordinate everything that is going on with the device.
Q: Which of the existing PalmOS devices are closest to Classic in terms of features?
A: During development of Classic we strived for compatibility with Palm Centro smartphones. Thus, certain features that may be available on other PalmOS handhelds are not supported in Classic (like screens larger than 320×320 pixels, DIA input API and some other rarely used APIs). Of course, this doesn’t mean that you will be limited only to applications that are designed specifically for Centro: majority of existing PalmOS apps are device-agnostic and will run on any PalmOS system, including Classic.
! v& D9 Q" ^0 _7 AQ: I have PalmOS applications that I would like to continue using in Classic. Do I need to buy them again?
A: As far as Classic is concerned – you don’t. Classic will enable you to run existing PalmOS applications without any modifications or limitations. However, if you have commercial PalmOS applications you may need to check the licenses you received from their developers for using it on a different/new device.
0 u: [6 G) H; p' y+ C  oQ: Can I run multiple Classic instances at the same time?
A: No, you cannot. The design of webOS is such that it allows only a single instance of a given application to be run at a time. If you try to launch Classic from the main webOS launcher while another Classic is running, the system will simply switch to (bring to focus) the existing Classic instance.
Q: Can Classic run the native ARM code (a.k.a. ARMlets, PNOlets…)?

1 n2 A1 R* ~8 E3 U" ^; e0 C. [" MA: Yes, it can. PalmOS applications containing both 68K and ARM code will work in Classic without modifications.
7 n0 j. ~! p% r% h" O% \% E9 ZQ: Can PalmOS applications running in Classic access the SD card slot? What kind of access is supported?
: e2 m) _5 W5 t! C2 i3 F( m0 E* z
% D; o$ W9 `3 Y  LA: Palm® Pre™ device does not have an SD card slot. However, Classic contains a full emulation of SD card related APIs. We have implemented this through a dedicated folder on device’s file system which mimics the SD card. PalmOS application can access files and folders in this virtual storage card using the standard PalmOS VFS API, without any restrictions. This means that PalmOS apps can create, read, modify or delete files and folders on the virtual SD card just as they did on real SD card on real PalmOS devices (it can even be formatted through standard PalmOS API). From the PalmOS application’s perspective, there is a fully functional SD card in Classic.
- d: y5 ^9 J$ _Q: Is there a HotSync support in Classic?

A: Unfortunately, not in the first release. HotSync and conduits are some of the most requested features we have received requests for so far and we are looking into various ways for solving this problem, but there are some serious technical and other obstacles for adding HotSync support to Classic.
Q: What is the “HotSync ID” icon that is present on some of the Classic screenshots?
A: It is a simple PalmOS application that we have bundled with Classic which enables you to define your HotSync ID. Since the only way for defining the HotSync ID on real PalmOS devices is by performing a HotSync operation – which is not supported on Classic – we have included this utility so that you can configure Classic to use the same HotSync ID you used on Treo/Centro. This application has nothing to do with actual HotSync – it just configures the ID that many applications require for registration purposes.
Q: Are the native PalmOS PIM databases (contacts, calendar, memos and tasks) supported in Classic?
2 `" s  @4 c' Y$ K  [1 F2 eA: Classic includes PalmOS Contacts, Calendar, Tasks and Memos apps and their databases so that the other apps relying on those databases can be used in Classic. Access to native webOS PIM databases is not supported at this time.
- v2 P, k* B7 Y8 dQ: Which screen resolutions are supported in Classic?

A: Classic supports 320×320 resolution, including 16-bit and 8-bit screen depths.
0 L1 e- D1 p! _7 E' o3 S- iQ: Is direct screen access supported in Classic?

2 V* m3 R2 n/ M- r5 K8 DA: Yes, PalmOS applications can directly access the screen memory for faster rendering, just as they do on real PalmOS devices.
+ _, K- a4 j# n9 y: QQ: Will Classic integrate into the webOS device hardware and to what extent?

3 Y! o- G$ m. ~* ?/ HA: The ability of Classic to integrate with underlying hardware is limited. This means that Classic will not be able to access Bluetooth, wireless modem (phone radio), GPS, light sensors or accelerometer (nor the IR port – because there isn’t any on Pre). One exception to this is the network access which is fully supported. Also, there are some other hardware integration points in Classic: for example a PalmOS application can obtain IMEI, IMSI, ESN and similar identifiers from the modem, device’s serial number and some other information that is typically used by many PalmOS applications for purposes of product registration and licensing. This is done through a standard PalmOS APIs, just like on real PalmOS hardware.
( }3 K7 z0 x2 k2 r9 pQ: Is there a network support in Classic?
A: Yes, there is. The PalmOS Network Library is fully supported in Classic. PalmOS applications running in Classic can access the Internet the same way they do on real PalmOS hardware. (Geek stuff: what is not possible from Classic is configuring the network routes or proxy servers – i.e. a PalmOS application cannot decide whether the request will go through cellular or WiFi networks – these details are handled by underlying TCP/IP implementation in webOS).
3 G) i( A7 I/ E8 u; YQ: Is the PalmOS web browser (Blazer) included in Classic?
% y: j, T0 q8 {0 n  fA: No, it is not. webOS contains a significantly more powerful web browser. However, there are lots of PalmOS applications that rely on Blazer services for displaying on-line content. When such an application attempts to launch Blazer and navigate to a web page, Classic will open the default webOS browser and point it to the requested location.
Q: Can I install a third party PalmOS web browser or e-mail client in Classic?
A: Yes you can. Classic fully supports network access, so applications like web browsers, e-mail client, RSS readers, IMs or any other apps that are communicating with remote servers over the network will work with Classic.
  ?- E( y' f, HQ: What other restrictions exist in Classic, comparing to real PalmOS devices?
' `9 C* ]) H- g' N
, M) r( P8 n( x3 KA: In addition to limitations described above, following PalmOS features are not supported in Classic:
& j: D3 J2 J1 E& z· Access to built-in camera
" R0 f$ _! c  {1 r) m5 e5 R· Access to external hardware devices through Bluetooth, serial or USB ports however access to network peripherals is supported
· PalmOS development tools, like POSE, Gremlins, debuggers and similar
· Audio/video codecs – due to licensing limitations there are no built-in audio/video codecs in Classic (e.g. MP3, MP4, AMR and others available on Centro).
, |  L; \$ w1 a2 d6 r1 T

chunqiangl

E文看不懂

rwxld

不错,看来大问题解决了,呵呵

notell

不错，就是没有说明是否支持漢文

tycho

palmOS仿真器“classic"的最新细节和技术解答

! V' i0 {" T, y! M  `4月12日，MotionApps网站发布了palmOS仿真器“classic"的最新细节和技术方面的问答。
* T- t  W6 y' C5 u- Xhttp://motionapps.blogspot.com/2009/04/classic-faq.html

我选择了一些问答，简单翻译如下：
. U$ Y- D% ~. A& _+ x) T/ a1 v/ m' q
* u3 U: j* K' I8 n7 @问：运行在webOS的classic和真实的palmOS有什么主要区别？
答：最主要的区别是classic和其它webOS的软件一样是运行在webOS上的一个应用软件，而PalmOS是运行在treo或centro之类设备上的操作系统。这意味着classic不能完全无限制的控制它所运行的硬件。classic必须要遵守某些规则，例如，classic不能关闭设备或者网络，而这些真实的PalmOS是可以执行的。
5 Z  d3 E+ \. m
: F# R' R% }, X2 e3 @. o$ P问：在特性上，classic最接近于哪个现有的PalmOS设备？
( b2 Y' F! Z) q/ i" U答：在classic开发中，我们是力求兼容于centro的。因此有些其它palmOS设备支持的特性，classic是不支持的（像大于320x320的屏幕，DIA 输入API 和一些很少用到的API）。按我的理解是不支持480x320的宽屏显示界面，没有虚拟输入盘。
1 C0 `& x! y% U* r
3 T; b  |+ G$ Q' K6 z- `问：我现有的palmOS软件，如果要在classic上运行，需要重新购买吗？
6 S8 n; J1 _& J: V( [! m答：不需要。classic可以让你运行现有的palmOS软件，无须修改，没有限制。但是，如果是商业软件，你要留意软件的开发者对软件运行在别的设备上是否有版权的法律要求。
( m' G) w. F9 c& z. x- W$ ?/ r
9 V$ n6 g% E: b5 y问：可以同时运行多个classic吗？
答：不可以。
3 i( Y% }: Y( T6 G* D8 g* U
9 T: f- {: e) r; K问：classic能否支持原生ARM代码（像 ARMlets, PNOlets）
! W; H& i- C7 o" p' j2 ?/ h答：能够。包含68k或者arm代码的palmOS软件都可以在classic上运行，无须修改。

/ G; ^0 l" s) s3 d1 v8 z/ n; M7 T问：在classic上运行的palmOS软件可以访问SD卡吗？支持哪种访问？
6 `1 f& l$ z: g) N* N答：虽然pre没有SD卡槽，但是classic包含了SD卡相关API的完整仿真。我们在设备的文件系统中建立一个专用的文件夹去模拟SD卡。PalmOS软件可以使用标准的PalmOS VFSAPI去访问这个虚拟存储卡中的文件和文件夹，没有任何限制。也就是说可以在这个虚拟SD卡上创建、读写、删除文件和文件夹，就像对真实palmOS设备中的真实SD卡所进行的操作一样（甚至可以通过标准palmOS API进行格式化）。

, ~* e+ o) \  V" L# t. b9 q问：classic是否支持hotsync热同步？
0 u4 d" p. p( H( B' B$ P答：很遗憾，第一个发布的版本不会支持。我们正在寻找不同的方法去实现，但目前有一些技术上的障碍。
/ X0 ]" u( N/ N- R
问：一些classic的截屏图片中出现的“Hotsync ID”图标是什么？
答：它是一个classic附带的简单软件，可以让你设定你的HotsyncID（同步名）。因为在真实的PalmOS设备上设定同步名，唯一方法是通过热同步，但classic目前是不支持热同步的，所以我们附带这个软件使你可以在classic设定和你的treo或centro上一样的同步名，便于注册软件。

问：classic是否支持原生的PalmOS PIM 数据库(contacts, calendar, memos and tasks)？
答：支持。但目前不支持原生的WebOS PIM数据库。
) z# w! [0 I  L  R  r3 i  J! j
问：classic支持什么屏幕分辨率？
答：支持320x320，包括8位和16位色深。
1 x3 N' P; f7 a
问：classic是否支持直接屏幕访问？
8 Z5 p, X! {* K3 E答：支持。palmOS软件可以直接访问屏幕缓存以加快渲染，就和在真实PalmOS设备上操作的一样。
2 u8 n7 P' `( \6 _' p6 u
# Y8 ~  O2 `: Q问：Classic将会集成到webOS设备硬件上吗？集成到什么程度？
答：classic与WebOS设备底层硬件集成的能力有限。因此，classic不能够操作蓝牙、手机信号无线modem、GPS、光学感应器和加速度感应器（也没有红外线，因为pre没有红外线接口）。有一个例外，就是网络访问，是完全支持的。另外，classic还支持一些硬件集成，例如palmOS软件可以从modem、设备序列号等获取IMEI、IMSI、ESN和其它识别信息，用于软件的版权或注册。这是通过标准的PalmOSAPI完成的。

问：classic是否支持网络？
答：支持。Classic 完全支持PalmOS NetworkLibrary。在classic上运行的PalmOS软件可以像在真实palmOS设备上那样访问网络。（但classic不能设置网络路由和代理服务器，例如classic不能决定访问请求是走手机还是wifi网络，这些是由WebOS底层的tcp/ip层去处理的。）
, Y- T$ E7 }" M' b4 u. x
* ~5 V# [9 L6 P, k+ s9 ?问：classic是否包含Palm Web浏览器（即blazer）？
答：不包含。因为webOS拥有一个非常强大的浏览器。但很多palmOS软件需要依赖blazer去打开网上的内容，如果这样的软件发出请求运行blazer浏览某个网页，classic会自动运行webOS默认的浏览器去浏览该网页。
, u- S$ J5 R8 N9 k' V! V
' Q+ b7 B+ p2 Z* N! i- U1 h问：我可以在classic上安装第三方的PalmOS网络浏览器和邮件客户端吗？
9 F7 Y6 L8 X- f4 G( W+ h$ {答：可以。classic完全支持网络访问，所以像网络浏览器、邮件客户端、rss阅读器、IM软件等通过网络和远端服务器进行通信的应用，在classic都可以工作。
( `0 C' {) O5 X$ M
问：相比于真实的PalmOS设备，classic还有什么其它限制？
答：除了上面提到的限制，classic还有以下几点是不支持的：

• 操作内置相机。

• 通过蓝牙、串口、usb端口操作外置的硬件设备，但是访问网络外围设备是支持的。
• PalmOS开发工具，像POSE, Gremlins, debuggers或类似软件。
• 音频和视频的解码。由于版权限制，classic没有内置的音频和视频解码（像mp3、mp4、AMR等）

AKGG

以前很多人的担心是多余的，现在担心对中文的支持相信也是多余的。