Skip to main content

Home/ Sensorica Knowledge/ Group items tagged prompt

Rss Feed Group items tagged

Filter: All | Bookmarks | Topics Simple Middle
Kurt Laitner

Are you ready for 3-D printing? | McKinsey & Company - 0 views

www.mckinsey.com/...are_you_ready_for_3-d_printing

3d printing mckinsey additive

shared by Kurt Laitner on 24 Feb 15 - No Cached
  • But patent expirations and new entrants in Asia should apply downward pressure over the next ten years
  • The cost of materials ought to drop in the long term as third-party firms become credible alternative powder suppliers and as increased demand for powder enhances scale efficiencies more generally
  • Throughput rates are expected to increase on the back of growing laser power, higher numbers of lasers, and better projection technology. All of that will serve to reduce expensive machine time
  • Kurt Laitner on 24 Feb 15
     
    Overly focused on additive 3d printing (the ecosystem of automated fabrication (ie fablab scale) and its exponential cost decreases are far more interesting).  The expiration of patents in the space is also a key feature of the current transformation, and should prompt discussions of dysfunctional IPR.  Comments on costs trends are also supportive.  No mention of the next big thing which is cradle to cradle desktop manufacturing.
Philippe Comtois

Prompt - Financement de la R-D en TIC - 1 views

promptinc.org/index_fr.html

shared by Philippe Comtois on 21 Nov 11 - No Cached
  • Philippe Comtois on 21 Nov 11
     
    RD financing
Tiberius Brastaviceanu

Google Apps Script - introduction - 0 views

code.google.com/...guide_events.html

google script apps Programming javascript tool tools infrastructure

shared by Tiberius Brastaviceanu on 03 May 11 - No Cached
  • script that you want to run every day at a specific time
  • script that should run after a user submits a data-collection form.
  • Google Apps Script provides simple event handlers and installable event handlers, which are easy ways for you to specify functions to run at a particular time or in response to an event.
  • ...39 more annotations...
  • let's consider the terminology we use for events
  • event triggers
  • triggers
  • in response
  • event handler
  • event
  • onInstall function
  • onOpen function.
  • onEdit function
  • the simple event handlers are restricted in what they are permitted to do:
  • The spreadsheet containing the script must be opened for editing
  • cannot determine the current user
  • cannot access any services that require authentication as that user
  • Calendar, Mail and Site are not anonymous and the simple event handlers cannot access those services.
  • can only modify the current spreadsheet. Access to other spreadsheets is forbidden.
  • see Understanding Permissions and Script Execution.
  • The onOpen function runs automatically when a user opens a spreadsheet.
  • add custom menu items to the spreadsheet's menu bar.
  • onEdit function runs automatically when any cell of the spreadsheet is edited.
  • record the last modified time in a comment on the cell that was edited.
  • The onInstall function is called when a script is installed from the Script Gallery.
  • setting up custom menus for the user.
  • the script can call onOpen from onInstall.
  • Installable event handlers are set on the Triggers menu within the Script Editor, and they're called triggers in this document.
  • When a specific time is reached
  • When a form is submitted
  • When a Spreadsheet is edited
  • When a Spreadsheet is opened.
  • They can potentially access all services available to the user who installed the handler.
  • are fully-capable scripts with none of the access limitations of simple event handlers
  • may not be able to determine which user triggered the event being handled
  • The spreadsheet containing the script does not have to be open for the event to be triggered and the script to run.
  • You can connect triggers to one or more functions in a script. Any function can have multiple triggers attached. In addition, you can add trigger attributes to a function to further refine how the trigger behaves.
  • When a script runs because of a trigger, the script runs using the identity of the person who installed the trigger, not the identity of the user whose action triggered the event. This is for security reasons.
  • Installing an event handler may prompt for authorization to access
  • An event is passed to every event handler as the argument (e). You can add attributes to the (e) argument that further define how the trigger works or that capture information about how the script was triggered.
  • an example of a function that sends email to a designated individual containing information captured by a Spreadsheet when a form is submitted.
  • With Google Apps, forms have the option to automatically record the submitter's username, and this is available to the script as e.namedValues["Username"]. Note: e.namedValues are only available for Google Apps domains and not for consumer Google accounts.
  • The available attributes for triggers are described in the following tables.
  • Tiberius Brastaviceanu on 03 May 11
     
    script that you want to run every day at a specific time
1 - 4 of 4
Showing 20▼ items per page