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/Meeting Minutes/Status 20110922"
< E4 | Meeting Minutes
(→Minutes) |
|||
(2 intermediate revisions by the same user not shown) | |||
Line 21: | Line 21: | ||
* We will switch to require range of EMF to allow installing features that | * We will switch to require range of EMF to allow installing features that | ||
* Working on fixing problem with fast views closing too aggressively | * Working on fixing problem with fast views closing too aggressively | ||
+ | * Fixing GTK+ problems with fade effects | ||
+ | * Working on moving to Cairo for graphics operations | ||
+ | * People are wanting to customize their CSS, but on Windows the install directory is not end user writable. | ||
+ | * Discussion of to what extent CSS customization should be exposed to end users | ||
+ | ** Some products may want to lock this down | ||
+ | ** Other products want to allow customization, but end users can't be expected to understand CSS | ||
+ | ** If we expose a layer of preferences we have to reconcile with the CSS |
Latest revision as of 10:51, 22 September 2011
Attendees
- Bogdan Gheorghe
- Brian DeAlwis
- Dean Roberts
- John Arthorne
- Oleg Besedin
- Remy Suen
- Tom Schindl
Minutes
- Constant memory churn is still a problem
- Still burning about 1MB of memory every second (not a leak though)
- Oleg optimizing context computation updates
- Cleaning up stale computations in the background rather than eagerly
- Improves open/close view and perspective switch
- Was 10x slower, now 6x slower on micro-benchmark performance tests
- Working on trim stack changes
- Getting increase in external bug reports
- We will switch to require range of EMF to allow installing features that
- Working on fixing problem with fast views closing too aggressively
- Fixing GTK+ problems with fade effects
- Working on moving to Cairo for graphics operations
- People are wanting to customize their CSS, but on Windows the install directory is not end user writable.
- Discussion of to what extent CSS customization should be exposed to end users
- Some products may want to lock this down
- Other products want to allow customization, but end users can't be expected to understand CSS
- If we expose a layer of preferences we have to reconcile with the CSS