Blackberry WebWorks 是一个好的开发选择吗？
这是一个愚蠢的问题，但我知道 Blackberry 的经典风格 JDE 开发，但我从未尝试过使用 WebWorks。 BB 网站称可以为智能手机（操作系统 6.0+）和平板电脑构建应用程序 - 听起来很棒，但价格是多少？
这里有人每天使用 WebWorks 并且能够描述其优点和缺点吗？
提前致谢
This is kind of a dumb question but I've aware of classic style JDE development for Blackberry but I've never tried using WebWorks. BB website says that it's possible to build applications for both smartphones (OS 6.0+) and tablets - sounds fantastic, but what's the price?
Is here anyone using WebWorks on a daily basis and capable of describing pros and cons?
Thanks in advance
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（4）
如果您事先构建 webOS 应用程序，我建议您使用它。它使移植到黑莓变得轻而易举。
如果您了解 html5、Css3 和 javascript（而不是 Java 和 C++），请使用 WebWorks。
我还没有遇到任何 webWorks 问题，移植了两个应用程序也没有遇到任何问题。它是您喜爱的标准 html5、css3 和 javascript，以及黑莓 API
I would suggest using it if you build webOS applications before hand. It make porting to the blackberry a breeze.
Use WebWorks if you know html5, Css3 and javascript over Java and C++.
I haven't ran into any issues with the webWorks, ported two applications without running into any issues. Its your standard html5, css3 and javascript you love with blackberry APIs
WebWorks 是一个不错的开发选择，特别是因为它允许从早期的 BB 操作系统轻松迁移到 BB10。它主要是标准的 Web 技术（HTML5、CSS3 等），团队似乎专注于使其性能良好（例如硬件加速的 WebGL 图形），同时提供 BlackBerry 特定的 API 以使 WebWork 应用程序能够运行并具有良好的用户体验（例如，您可以使其看起来像本机应用程序）。
对于本机应用程序，您应该查看Cascades。这是一个现代化的开发环境，具有良好的工具、加速的图形和用于构建时髦应用程序的 API。这是最有可能成为“黑莓应用程序”的应用程序。
AIR 仍然是一个选择，但我会推荐 WebWorks 而不是 AIR，因为甚至 Adobe 也在从 Flash 迁移到 Web 技术。同样，您可以在 BB10 上开发 Android 应用程序，但除非您热衷于 Java 编程，否则您将从 WebWorks（甚至 AIR）获得更多跨平台支持，因此没有特别的理由走 Android 路线。
WebWorks is a good development choice, particularly as it allows easy migration from earlier BB OSes to BB10. It's mostly standard web technologies (HTML5, CSS3, etc.) and the team seems focused on making it perform well (e.g. hardware accelerated WebGL graphics) while at the same time providing BlackBerry-specific APIs to make WebWork apps capable and with good UX (e.g. you can make it look like a native app).
For native apps, you should look into Cascades. This is a modern development environment with good tooling, accelerated graphics, and APIs for building snazzy apps. It's the one that will most be a "BlackBerry app".
AIR remains an option, but I would recommend WebWorks over AIR, as even Adobe is migrating from Flash to web technologies. Likewise, you can develop Android apps on BB10, but unless you are keen on Java programming, you will get more cross-platform support from WebWorks (or even AIR) so there's no particular reason to go the Android route.
WebWorks API 是有限的，例如它没有套接字，因此您无法将 VNC（UltaVNC、tightVNC ..）移植到它，但您可以使用 JDE 来做到这一点。
对于 UI，WebWorks 使我能够快速轻松地编写质量可接受的 UI，这是我使用 JDE 从未成功过的事情。
还是在 UI 方面，我可以利用多点触控（PlayBook），我认为这在 JDE 中是不可能的。
因此，根据您的需求，您应该选择 WebWorks 或 Native，因为听说 BB10 可能不支持 Java，而且 Air 可能无法面向未来（Adobe 更喜欢 HTML5 而不是 Flash）。 Android 应用程序在 PlayBook 上运行时启动会出现一些滞后，一些客户对初始响应时间很敏感，甚至只是一倍的缓慢响应时间。
WebWorks API is limited, for example it does not have socket, so you cannot port a VNC (UltaVNC, tightVNC ..) to it but you can do it with JDE.
For UI, WebWorks allowed me to write UI of acceptable quality quickly and easily, a thing that I have never succeeded with JDE.
Still on the UI side, I can make use of multi-touch (PlayBook), I don't think this one is possible with JDE.
So depending on your needs you should go either WebWorks or Native, having heard that Java may not be supported in BB10, and Air may not be future proof (Adobe favors HTML5 instead of Flash). Android appli has some lag on start up when it is run on PlayBook, some customers are sensitive to the initial even just one time slow response time.
我是 Webworks 的坚定支持者。自从我开始使用它以来，它很快就成为我的应用程序的默认选项。特别是对于像我这样只是兼职写一些应用程序的人来说，我没有时间用 C++ 来做。
我正在编写的应用程序围绕家庭自动化。它们从一开始就是基于客户端/服务器的。
这就是我喜欢它的原因：
首先也是最重要的是，原生 API 支持。我可以非常轻松地创建自己的活动框架，从其他应用程序导入调用（想想相机之类的东西）。我可以将我的 webworks 应用程序的部分导出为调用卡！这意味着我可以编写 3 个独特的应用程序（在本例中为家庭自动化、灯光、恒温器、安全摄像头）。我可以很容易地将每个应用程序的功能转移到另一个应用程序中。也许我想打开客厅的灯，我还可以从 IPcam 应用程序导入相机卡并查看结果，而无需将该代码添加到我的灯光应用程序中并维护两个单独的代码行。
快速设计。由于我从小就开始涉足 html，现在对我来说很容易在短时间内创建一个吸引人的 UI。由于如今的网络引擎在图形功能方面提供了良好的性能，因此我还可以制作运行非常流畅的应用程序。
考虑到制作漂亮东西的时间，对我来说很难离开 webworks 并转向 c++ 中的东西。此外，最大的优点是我制作的这些应用程序通常适用于多种设备，即我手机上的应用程序并托管在我的个人网站上。通过维护两个略有不同的 css 文件，大多数时候我不需要更改代码，只需根据它是手机还是 PC 加载不同的 css 即可。 （如果您正在开发一个常规的旧网站，这正是您会做的事情）。
就此而言，我实际上没有将代码放在设备上，而是将所有 html 和 javascript、图像等托管在我的服务器上。 webworks 应用程序只是将其源指向我的服务器的 config.xml 和一个图标。主屏幕上的一个美化的网站书签，唯一的区别是我可以使用本机 API 并且应用程序中没有浏览器栏。
此外，这样我仍然可以继续在服务器上编辑相同的单个代码行，并立即将更改应用到浏览器内应用程序和设备上应用程序。
如果您正在设计一个所有数据都在“云”中的应用程序，假设您在一家出版物工作并且您想要编写一个杂志应用程序来从网络上的服务器中提取内容，那么这尤其酷。
I'm a huge proponent of Webworks. Ever since I've started using it, it quickly became the default option for my apps going forward. Especially for someone like me who is just writing a few apps on the side, I don't have the time to do it in c++.
The apps I'm writing revolve around home automation. They are client/server based from the get go.
Here's why I like it:
First and foremost, native API support. I can very easily create my own active frames, import invocation from other apps (think camera, stuff like that). I can export portions of my webworks app as an invocation card! Which means I can write say 3 unique apps (in this case home automation, lights, thermostat, security cameras). And I can very easily pull features from each app into the other. Maybe I want to turn my lights on in the living room, I can also import the camera card from my IPcam app and view the results, without having to add that code into my lights app and maintain two separate code lines.
Rapid design. Since I've been dabbling in html since I was a kid, it's now very easy for me to whip up an appealing UI in little time. Because web engines these days offer good performance in terms of graphics capability, I also can make apps that behave very fluid.
Considering the time to make something beautiful, it's hard for me to leave webworks and go for something in c++. Also the big plus is often these apps I'm making are intended for multiple devices, namely an app on my phone and being hosted on my personal website. By maintaining two slightly different css files, most of the time I need no code changes, just load a different css depending on if it's a phone or a pc. (Exactly what you'd do if you were developing a regular old website).
For that matter, I actually don't put my code on the device, I host all of my html and javascript, images etc on my server. The webworks app is just the config.xml pointing it's source to my server, and an icon. A glorified website bookmark on the homescreen, only difference is I can use native API and there's no browser bar in the app.
Also, this way I can still continue to edit the same single codeline on my server, and instantly apply changes to the in-browser app and the on-device app.
This is especially cool if you're designing an app where all of it's data is out in the "cloud", say you work for a publication and you want to write a magazine app which pulls content from your servers on the net.