Skip to main content

Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: for the plan.

Jump to: navigation, search

Orion/Meeting minutes/20110331


  • EclipseCon / Orion Summit update
  • Client side includes
  • Dojo 1.6 adoption


  • Susan McCourt
  • John Arthorne
  • Andrew Niefer
  • Boris Bokowski
  • Felipe Heidrich
  • Sileno Quarti
  • Libing Wang
  • Mark Macdonald
  • Simon Kaegi
  • Grant Gayed
  • Szymon Brandys
  • Tomasz Zarna
  • Gosia Janczarska
  • Richard Backhouse
  • Jon Ferraiolo


  • Protocol changes in crossfire
  • About to go into Firebug and JSDT
  • JavaScript tests running in the build
    • Some timeout problems that require further investigation
    • p2 repositories produced by build
  • Going through the process of dual-licensing our code
  • Added support for IE 9 in the editor, fixed performance problems
  • Some initial support for iOS in the editor
  • Working on getting compare editor to be mutable/saveable
    • Investigating algorithms for merging conflicts
    • Support for comparing two arbitrary commits
  • Working on being able to self-host Orion development using site configurations
    • Host client side code from running site
    • Still working on problems handling redirects
  • Legal process underway for RequireJS and Dojo 1.6
  • Git log page in progress
    • Open editor on arbitrary commit
    • Working on performing diff between various points
  • Working on figuring out work flow for handling merges and conflicts
  • Working on storing SSH info in local storage
  • Refactoring editor container to support compare editor and Firebug integration
    • Pulled out some functionality from editor container into other places
    • Additional work needed to support different file types, different key binding maps, etc

Client side includes

  • Currently we use client-side injection by defining HTML header and footer content in a JS file
  • When the JS gets minified this code gets copied into many places which makes it hard to maintain
  • Each page still has to manage the dependencies of any JS code in the header/footer
  • Possible option to use dijit template mechanism
  • Two main pain points
    • When deploying to orionhub want to update the footer in one place
    • When common commands add dependencies, want to avoid forcing every page to update dependencies

Dojo 1.6 / RequireJS

  • Want to move to dojo 1.6 early in M7
  • Once dojo 1.6 in place, try moving to RequireJS
  • Dojo 1.7 apparently coming end of June
  • Bug about better error message when browser not supported is bug 340509

Back to the top