From 39f60d4e9a20b9b9b01d6da73a491e30c7e4f5a9 Mon Sep 17 00:00:00 2001
From: Sadeep Madurange
Before settling on a desktop application, we contemplated a browser extension. -We decided against that because we didn’t want the browser vendor to dictate -Bumblebee’s capabilities. Furthermore, the company’s security policy prohibited -browser extensions, complicating its deployment. The initial prototype used a -C# wrapper of the Chromium project instead of WebView. WebView’s more intuitive +
Before settling on a desktop application, we contemplated designing Bumblebee +as a browser extension. We decided against that because we didn’t want the +browser vendors to dictate Bumblebee’s capabilities. Besides, the company’s +security policy, which prohibited browser extensions, would have complicated +the deployment of an extension-based solution. The initial prototype used a C# +wrapper of the Chromium project instead of WebView. WebView’s more intuitive API and its seamless integration with Windows Forms led us to choose it over the Chromium wrapper.
-Bumblebee reduced the time we spent on authoring scripts from hours to a few -minutes. Since the rules for code generation were written and optimized by -experts in web technologies, the output was more robust.
+Bumblebee predictably reduced the time we spent on authoring scripts from hours +to a few minutes. Since the code generation rules were written and optimized by +experts in web technologies, the quality of the scripts improved as well.
-- cgit v1.2.3