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 "E4/Scripting/telcon20130904"
(→Choices) |
(→Nex meetings) |
||
| (4 intermediate revisions by the same user not shown) | |||
| Line 22: | Line 22: | ||
*** Metadatas | *** Metadatas | ||
*** Some work on python | *** Some work on python | ||
| − | *** Migrate DOMs into modules. The module will now be loaded thanks to the loadModule instruction or statically thanks to the metadata. (Next | + | *** Migrate DOMs into modules. The module will now be loaded thanks to the loadModule instruction or statically thanks to the metadata. (Next Friday meeting) |
| − | * A new | + | * A new repository will be created on github waiting for integration in eclipse. First committers : |
** Christian Pontesegger, Infineon | ** Christian Pontesegger, Infineon | ||
** Martin Oberhuber, WindRiver | ** Martin Oberhuber, WindRiver | ||
| Line 30: | Line 30: | ||
* Deadlines | * Deadlines | ||
| − | ** Aim to make write the proposal before the end of | + | ** Aim to make write the proposal before the end of September |
| − | + | ||
==Tasks== | ==Tasks== | ||
| Line 48: | Line 47: | ||
**Look for correct Eclipse Architecture of builds | **Look for correct Eclipse Architecture of builds | ||
| − | * | + | *Pierre |
| − | ** Find a way to integrate Jython,JRuby and | + | ** Find a way to integrate Jython,JRuby and Groovy interpreter into eclipse fondation (in progress with EMO) |
| − | == | + | ==Next meetings== |
| − | * 09/06/2013 11 am | + | * 09/06/2013 11 am - Discuss module mechanism |
| − | * 09/11/2013 11 am | + | * 09/11/2013 11 am - Discuss project progress |
Latest revision as of 05:48, 11 September 2013
Contents
Attendees
- Arthur Daussy, ATOS
- Christian Pontesegger, Infineon
- Martin Oberhuber, WindRiver
Agenda
The aim of this meeting was to discuss technical solution for the new eclipse project. Agenda :
- Eclipse Monkey Revival Vs EScript
- Make choice about language syntax
- Team Organization
- Deadlines
Choices
- Technical choices
- The EScript project will be use a base. Cause
- The project is more recent
- The architecture is more clear and quite close the Eclipse Monkey one( Not difficult to integrate Eclipse Monkey contribution)
- Eclipse Monkey contribution to migrate to new project
- Script Tree view
- Script Menu
- Metadatas
- Some work on python
- Migrate DOMs into modules. The module will now be loaded thanks to the loadModule instruction or statically thanks to the metadata. (Next Friday meeting)
- The EScript project will be use a base. Cause
- A new repository will be created on github waiting for integration in eclipse. First committers :
- Christian Pontesegger, Infineon
- Martin Oberhuber, WindRiver
- Arthur Daussy, ATOS
- Deadlines
- Aim to make write the proposal before the end of September
Tasks
- Arthur
- Create a new repo
- Change namespace to be Eclipse compliant
- Migrate Eclipse Monkey contribution + samples
- Work to make python work
- Migrate Topcased Dom
- Christan
- Integrat current work (debugger etc...)
- Make maven build work in new space
- Martin
- Look for correct Eclipse Architecture of builds
- Pierre
- Find a way to integrate Jython,JRuby and Groovy interpreter into eclipse fondation (in progress with EMO)
Next meetings
- 09/06/2013 11 am - Discuss module mechanism
- 09/11/2013 11 am - Discuss project progress