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.
Difference between revisions of "E4/Meeting Minutes/Status 20111006"
< E4 | Meeting Minutes
| Line 6: | Line 6: | ||
= Minutes = | = Minutes = | ||
| + | |||
| + | * Looking at test failures in 3.x stream. | ||
| + | * Reviewing patches from community | ||
| + | * Looked at WTP CSS editor to see if we could use it | ||
| + | ** Doesn't seem to be a way to contribute custom content assist for our crazy extensions | ||
| + | * Moved further down the XText CSS editor route. | ||
| + | ** It pulls in a number of dependencies so there may be an issue with packaging in SDK | ||
| + | * Looking at memory consumption of context code. Made some improvements. | ||
Discussion of how to organize UI development to avoid overhead and reduce risk of failure across 3.x and 4.x. | Discussion of how to organize UI development to avoid overhead and reduce risk of failure across 3.x and 4.x. | ||
| + | |||
* Currently we have two copies of 95% of our code that is in common (via branching) | * Currently we have two copies of 95% of our code that is in common (via branching) | ||
* How do we avoid the duplication in all the common code but keep a structure that makes it easier to keep ui.workbench branches up to date. | * How do we avoid the duplication in all the common code but keep a structure that makes it easier to keep ui.workbench branches up to date. | ||
Revision as of 10:55, 6 October 2011
Attendees
- Tom Schindl
- David Williams
- Brian DeAlwis
Minutes
- Looking at test failures in 3.x stream.
- Reviewing patches from community
- Looked at WTP CSS editor to see if we could use it
- Doesn't seem to be a way to contribute custom content assist for our crazy extensions
- Moved further down the XText CSS editor route.
- It pulls in a number of dependencies so there may be an issue with packaging in SDK
- Looking at memory consumption of context code. Made some improvements.
Discussion of how to organize UI development to avoid overhead and reduce risk of failure across 3.x and 4.x.
- Currently we have two copies of 95% of our code that is in common (via branching)
- How do we avoid the duplication in all the common code but keep a structure that makes it easier to keep ui.workbench branches up to date.