release

app_builder.js

@@ -750,7 +750,7 @@ ab.launch = function(){ //happens in ui env, called from Insert menu item when u
         </center>
 `,
     title: '<span title="Build the code for a window that becomes\nthe interface to an application.\nWrap it in a function that, when called,\nshows the window.">' +
-           'Application Builder</span>',
+           'Build Window</span>',
     width:480,
     height:590,
     x:540, //x and y positioned so that if you shrink this window, it will as much as pssible not occlude the most useful DDE info.

doc/browser_vs_dde.html

@@ -1 +1 @@
-<style>    .doc_details {        margin-left:20px;        font-size:16px;    }    .doc_details summary { font-weight: 600; }</style><div style='font-size:16px;'><h2>Browser vs. DDE</h2><i>Fry July 7, 2017</i><p/>A good way to understand DDE at a high level is to compare it to a web browser.A browser is an application that displays content from the web or files on your computer.The content can be dynamically generated based on user actions and underlying code thatcomputes the content to be displayed. The browser provides the runtime engine for running that code. Major browsers also have tools for helping you debug that code, though these are hidden from most users.<p/><b>The Browser Mindset</b><br/>In the browser mindset, most users are “content viewers”.They are distinct from “content creators”. The idea is that most people want to read, but not write.In the broad world, this is roughly true, though most people do at least a little writingfrom time to time. None-the-less, while most Internet users know how to view content on the web, they do not know how to author content. And most people that can author content, only know how to write static text, not more complex, definitive data formats or programs  that can compute and generate content.<p/>Because of the separation of readers from writers, different tools serve thesedifferent classes of users. This makes sense. The readers don’t want their worldcluttered with tools they don’t need to use. But if a reader wants to become a writer,the separation of tools makes it harder to transition from reader to writer.You have to learn a new toolset.<p/>There is literally a plethora (in the worst sense of the word) of tools to choose fromand learn how to use, to author web content. Typically they interact poorly with eachother as they were designed and implemented by separate teams that were only attemptingto solve part of the problems that writers face.<p/><b>The DDE Mindset</b><br/>DDE maintains the opposite mindset. There is no difference between readers and writers.Every content viewer should (and will need to at some point) become a content creator.DDE strives to make that transition as smooth as possible.<p/>You can think ofDDE more like Microsoft Word than a browser. Yes you can read documents in it.Yes you can even print documents using it. But the bulk of its functionality is to helpusers author those documents.<p/>Microsoft Word is for viewing, writing and printing text & graphic documents.DDE is for viewing, writing and “printing” 3D objects. Rather than control adesktop inkjet 2D printer as MS Word does, DDE controls Dexter, a 5 axis robot armthat is far more versatile than an inkjet printer because it can use many differentprocesses for making things.<p/><b>Multi-Process Making</b><br/>Conventional 3D printers use just one process, Fused Deposition Modeling (FDM)for printing files in a ridged file format called “STL” that describes3D dimensional surfaces using a set of many triangles. STL is transformed into layersby an application called a “slicer”, and the printer prints each layer, one on top of another.<p/>Dexter is fundamentally a motion platform that can, under program control,pick up different tools (called “end effectors” in robotics) that perform different functionsat the location that the motion platform moves them to.These end effectors can perform FDM, cutting with a laser, move parts(pick and place) and a wide variety of other tasks. In fact, Dexter is designed toaccommodate end effectors we haven’t even thought of yet.<p/>Who will? Dexter’s users. Through open source sharing, we promote the developmentof end effectors. To control these end effectors that will do a myriad of tasks,new processes need to be developed. Larger processes will be composed of differentkinds of smaller, narrower processes. Viewing, authoring, and operating theseprocesses is what DDE is for.<p/><b>Browser Comparison Revisited</b><br/>Despite all these differences with browsers, DDE does share a lot with them.First, it manipulates the same information formats, HTML, CSS and JavaScriptthat comprise web pages. Second it uses the underlying Chrome browser rendering,and JavaScript runtime engines. You can even take advantage of Chrome’s debugging tools within DDE.<p/>But DDE extends the browser by allowing programmatic access to the file system of yourlocal computer (a security restriction of browsers). It has access to other underlyingcapabilities of a computer’s operating system (WindowsOS, MacOS and Linux) alsorestricted due to security concerns in browsers. Additionally, DDE provides high level extensionsto JavaScript to help users author and run processes on Dexter.(These are called <i>Jobs</i>). DDE includes programmatic low level access to Dexter itself.Finally, DDE contains an extensive help system to make it easy for users to become,not just content viewers, but content creators.</div>
+<style>    .doc_details {        margin-left:20px;        font-size:16px;    }    .doc_details summary { font-weight: 600; }</style><div style='font-size:16px;'><h2>Browser vs. DDE</h2><i>Fry July 7, 2017</i><p/>A good way to understand Dexter Development Environment at a high levelis to compare it to a web browser.A browser is an application that displays content from the web or files on your computer.The content can be dynamically generated based on user actions and underlying code thatcomputes the content to be displayed. The browser provides the runtime engine for running that code. Major browsers also have tools for helping you debug that code, though these are hidden from most users.<p/><b>The Browser Mindset</b><br/>In the browser mindset, most users are “content viewers”.They are distinct from “content creators”. The idea is that most people want to read, but not write.In the broad world, this is roughly true, though most people do at least a little writingfrom time to time. None-the-less, while most Internet users know how to view content on the web, they do not know how to author content. And most people that can author content, only know how to write static text, not more complex, definitive data formats or programs  that can compute and generate content.<p/>Because of the separation of readers from writers, different tools serve thesedifferent classes of users. This makes sense. The readers don’t want their worldcluttered with tools they don’t need to use. But if a reader wants to become a writer,the separation of tools makes it harder to transition from reader to writer.You have to learn a new toolset.<p/>There is literally a plethora (in the worst sense of the word) of tools to choose fromand learn how to use, to author web content. Typically they interact poorly with eachother as they were designed and implemented by separate teams that were only attemptingto solve part of the problems that writers face.<p/><b>The DDE Mindset</b><br/>DDE maintains the opposite mindset. There is no difference between readers and writers.Every content viewer should (and will need to at some point) become a content creator.DDE strives to make that transition as smooth as possible.<p/>You can think ofDDE more like Microsoft Word than a browser. Yes you can read documents in it.Yes you can even print documents using it. But the bulk of its functionality is to helpusers author those documents.<p/>Microsoft Word is for viewing, writing and printing text & graphic documents.DDE is for viewing, writing and “printing” 3D objects. Rather than control adesktop inkjet 2D printer as MS Word does, DDE controls Dexter, a 5 axis robot armthat is far more versatile than an inkjet printer because it can use many differentprocesses for making things.<p/><b>Multi-Process Making</b><br/>Conventional 3D printers use just one process, Fused Deposition Modeling (FDM)for printing files in a ridged file format called “STL” that describes3D dimensional surfaces using a set of many triangles. STL is transformed into layersby an application called a “slicer”, and the printer prints each layer, one on top of another.<p/>Dexter is fundamentally a motion platform that can, under program control,pick up different tools (called “end effectors” in robotics) that perform different functionsat the location that the motion platform moves them to.These end effectors can perform FDM, cutting with a laser, move parts(pick and place) and a wide variety of other tasks. In fact, Dexter is designed toaccommodate end effectors we haven’t even thought of yet.<p/>Who will? Dexter’s users. Through open source sharing, we promote the developmentof end effectors. To control these end effectors that will do a myriad of tasks,new processes need to be developed. Larger processes will be composed of differentkinds of smaller, narrower processes. Viewing, authoring, and operating theseprocesses is what DDE is for.<p/><b>Browser Comparison Revisited</b><br/>Despite all these differences with browsers, DDE does share a lot with them.First, it manipulates the same information formats, HTML, CSS and JavaScriptthat comprise web pages. Second it uses the underlying Chrome browser rendering,and JavaScript runtime engines. You can even take advantage of Chrome’s debugging tools within DDE.<p/>But DDE extends the browser by allowing programmatic access to the file system of yourlocal computer (a security restriction of browsers). It has access to other underlyingcapabilities of a computer’s operating system (WindowsOS, MacOS and Linux) alsorestricted due to security concerns in browsers. Additionally, DDE provides high level extensionsto JavaScript to help users author and run processes on Dexter.(These are called <i>Jobs</i>). DDE includes programmatic low level access to Dexter itself.Finally, DDE contains an extensive help system to make it easy for users to become,not just content viewers, but content creators.</div>

doc/guide.html

@@ -8,8 +8,8 @@
 
 <details class="doc_details"><summary>About</summary>
     This is <a href="http://hdrobotic.com/" target="_blank">Dexter</a> Development Environment<br/>
-    version:  <span id="dde_version_id">2.0.8</span><br/>
-    released: <span id="dde_release_date_id">Jul 29, 2017</span>
+    version:  <span id="dde_version_id">2.0.9</span><br/>
+    released: <span id="dde_release_date_id">Aug 3, 2017</span>
     <p/>
     DDE helps you create, debug, and send software to a Dexter robot.
     You can use any JavaScript augmented with DDE-specific functions to help find out about,