Skip to main content

Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

Difference between revisions of "Orion/Meeting minutes/20141125"

Line 16: Line 16:
 
* Work in progress on multi-cursor / multiple selections in the editor
 
* Work in progress on multi-cursor / multiple selections in the editor
 
** Basic navigation working, but multiple edits not yet working
 
** Basic navigation working, but multiple edits not yet working
 +
*  Work on cf debug launcher
 +
*  Adding support for plugins/delegated uis to submit forms
 +
* added client side tracking for associating user with events being sent (currently using login id)
 +
* Adding lifecycle commands for cf launcher

Revision as of 13:55, 25 November 2014

Attendees

John, Bogdan, Anton, Anthony, Libing, Eric, Insoo, Aidan, Simon, Mark, Grant, Curtis, Mike, Szymon

Minutes

  • Adding support for seeing commit details in repository browser widget
  • Working on Orion dark page theme, in particular the theme implications for Git page
  • Work in progress on file change event support in Orion Java server
  • New server API to return flat list of all files in a workspace
  • Adding support to dynamically load natural language bundles based on browser language, to avoid cost of loading all bundles for all users on all pages
  • Adding support for second pane in content assist which shows documentation on currently selected proposal
  • Adding various Quick Fixes for JavaScript
    • Need to add support for making multiple concurrent edits out of a quick fix
    • This may be pushed into the core editor as part of multi-cursor support
  • Work in progress on multi-cursor / multiple selections in the editor
    • Basic navigation working, but multiple edits not yet working
  • Work on cf debug launcher
  • Adding support for plugins/delegated uis to submit forms
  • added client side tracking for associating user with events being sent (currently using login id)
  • Adding lifecycle commands for cf launcher

Back to the top