| [koneki-dev] "Execution Environment" Usage |
Hi all, I’ve submitted a bug on the Bugzilla on this topic but thought I’d start a thread here to get everyone’s input. I wanted to discuss some tweaking of the usage of "execution environment", the terminology used when referring to imported content assist zips. To me the term "execution environment" refers to the actual application framework runtime / vm inside the target hardware. For content assist to work it needs info/doc on a given exec env so the IDE needs to "add support for a given execution environment" but not "add/install an execution environment." The difference to me is "adding support" means we're enabling integration with a device that has that exec env while "install exec env" means we're actually installing the exec env virtual machine into the IDE or the user's app. Some specific examples of what we could change: 1. In the Preferences screen (ldt_pref_exec_env.jpg) we could change "Installed execution environments" to "Supported execution environments". 2. In the New Projects screen (ldt_new_proj.jpg) we could change "Execution Environment" to "Targeted Execution Environment". Thoughts? -Kevin __________________________________________________________________________ Kevin Lloyd :: Product Manager, AirVantage SIERRA WIRELESS Main (760) 476 8700 :: Direct (760) 476 8718 :: Fax (760) 476 8701 2200 Faraday Avenue, Suite 150 :: Carlsbad, CA, USA 92008 klloyd@xxxxxxxxxxxxxxxxxx :: www.sierrawireless.com __________________________________________________________________________ This message and any attachments (the "Message") are confidential and intended solely for the addressees. Any unauthorized modification, edition, use or dissemination is prohibited. Neither Sierra Wireless nor any of its subsidiaries shall be liable for the Message if altered, changed, falsified or edited, diffused without authorization. |
Attachment:
ldt_pref_exec_env.jpg
Description: ldt_pref_exec_env.jpg
Attachment:
ldt_new_proj.jpg
Description: ldt_new_proj.jpg
