Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "Orion/Meeting minutes/20130110"
< Orion | Meeting minutes
(→Minutes) |
(→Minutes) |
||
| Line 21: | Line 21: | ||
'' ''Libing'': will open a new bug regarding cancellation of Operations. | '' ''Libing'': will open a new bug regarding cancellation of Operations. | ||
* ''Eyal'': working on a POC using Orion. Discussing UI with Susan. Considering use of service extensions. Working with the Orion Node server. | * ''Eyal'': working on a POC using Orion. Discussing UI with Susan. Considering use of service extensions. Working with the Orion Node server. | ||
| − | + | ** 'Will the Node server have SCM (Git) integration?' Team in Poland is investigating a JS-Git implementation, but that's a long ways out. For now, consider running multiple Orion servers, each providing different services. Orion's Node plan for 2.0 is a single-user environment without SCM. Feature parity with Java server is important in the long run. | |
* ''Susan'': Changed banner: removed favorites star, moved progress UI around. NLS binding to widget templates. Dialog changes & bugfixes. Dojo removal from low-traffic pages. Forthcoming: more Dojo/Dijit removal, dialog fixes. Rework "Create New Content" extension point in anticipation of Anton's work on Projects. | * ''Susan'': Changed banner: removed favorites star, moved progress UI around. NLS binding to widget templates. Dialog changes & bugfixes. Dojo removal from low-traffic pages. Forthcoming: more Dojo/Dijit removal, dialog fixes. Rework "Create New Content" extension point in anticipation of Anton's work on Projects. | ||
* Discussion about Dijit removal. Orion is not building a library for "widget" abstraction. UI components are built using HTML+JS, targeting the DOM. We use simple HTML "templates" when necessary. Dynamic behavior implemented with small amounts of JS when necessary. Ultimately aiming at W3C *decorator* approach. | * Discussion about Dijit removal. Orion is not building a library for "widget" abstraction. UI components are built using HTML+JS, targeting the DOM. We use simple HTML "templates" when necessary. Dynamic behavior implemented with small amounts of JS when necessary. Ultimately aiming at W3C *decorator* approach. | ||
| Line 29: | Line 29: | ||
* ''Mark'': Dojo/Dijit removal for Settings page. Investigating test runner (Mocha) for the Node server. | * ''Mark'': Dojo/Dijit removal for Settings page. Investigating test runner (Mocha) for the Node server. | ||
* ''Ken'': Preparing a demo showing the use of Orion for Node development: starting fresh, installing npm modules, deploying to Cloud Foundry. Implementing deployment to Cloud Foundry. | * ''Ken'': Preparing a demo showing the use of Orion for Node development: starting fresh, installing npm modules, deploying to Cloud Foundry. Implementing deployment to Cloud Foundry. | ||
| − | * ''Anton'': Committed UI for a Project page. Working on the model underlying Projects. | + | * ''Anton'': Committed UI for a Project page. Working on the model underlying Projects. For M2, hoping to have workflows implemented for creating SFTP projects, and also vanilla HTML file projects. |
Revision as of 12:54, 10 January 2013
Attendees
- Gosia
- Szymon
- Eyal
- Susan
- Simon
- Anton
- Grant
- Libing
- Mark
- Ken
- McQ
Announcements
- M2 in two weeks (January 25), then 2.0 end-game starts
Minutes
- Szymon: Working on removal of Dojo. Planning to write examples showing how a plugin can contribute page visuals.
- Gosia: Released changes to progress support. Forthcoming changes related to how progress is presented on various pages.
- Discussed cancellation of asynchronous calls (Deferred) and operations. Bug 397801 is a possible use case for UI of cancellation.
Libing: will open a new bug regarding cancellation of Operations.
- Eyal: working on a POC using Orion. Discussing UI with Susan. Considering use of service extensions. Working with the Orion Node server.
- 'Will the Node server have SCM (Git) integration?' Team in Poland is investigating a JS-Git implementation, but that's a long ways out. For now, consider running multiple Orion servers, each providing different services. Orion's Node plan for 2.0 is a single-user environment without SCM. Feature parity with Java server is important in the long run.
- Susan: Changed banner: removed favorites star, moved progress UI around. NLS binding to widget templates. Dialog changes & bugfixes. Dojo removal from low-traffic pages. Forthcoming: more Dojo/Dijit removal, dialog fixes. Rework "Create New Content" extension point in anticipation of Anton's work on Projects.
- Discussion about Dijit removal. Orion is not building a library for "widget" abstraction. UI components are built using HTML+JS, targeting the DOM. We use simple HTML "templates" when necessary. Dynamic behavior implemented with small amounts of JS when necessary. Ultimately aiming at W3C *decorator* approach.
- Grant: Dojo removal from Shell page is near completion. Working on extending File/Directory types in the Shell page, and defining the API for services consuming those types.
- Simon: Will be remove Dojo from Unit Test page.
- Libing: Implemented npm support in the Node server. Posted to mailing list post explaining how to use npm. Fixed bugs in copy&paste files/folders between the Orion Node filesystem and other filesystems. Bugfixes both in client + Node server code.
- Mark: Dojo/Dijit removal for Settings page. Investigating test runner (Mocha) for the Node server.
- Ken: Preparing a demo showing the use of Orion for Node development: starting fresh, installing npm modules, deploying to Cloud Foundry. Implementing deployment to Cloud Foundry.
- Anton: Committed UI for a Project page. Working on the model underlying Projects. For M2, hoping to have workflows implemented for creating SFTP projects, and also vanilla HTML file projects.