Difference between revisions of "E4/Meeting Minutes/Status 20130905"

From Eclipsepedia

Jump to: navigation, search
(Minutes)
(Minutes)
 
(One intermediate revision by one user not shown)
Line 16: Line 16:
 
* Investigating replacement of SAC CSS parser with different parsers
 
* Investigating replacement of SAC CSS parser with different parsers
 
* Working on enabling use of some IDE views like navigator in an e4 RCP app
 
* Working on enabling use of some IDE views like navigator in an e4 RCP app
 +
* Enhanced NLS work from Tom+Dirk
 +
** Everyone in favour of moving into e4 runtime bundle
 +
* e4 Scripting
 +
** There is a group looking at reviving scripting support in Eclipse
 +
** e4 is a potential initial home for the investigation
 +
** We should let them know about the existing e4 scripting work that has been done already
 
* Jface generics
 
* Jface generics
 
** work has moved into a branch
 
** work has moved into a branch

Latest revision as of 11:08, 5 September 2013

[edit] Attendees

  • Brian
  • Dani
  • Daniel
  • Paul
  • John

[edit] Minutes

  • We are done with Kepler SR1
  • Respin was needed last night due to build problems
  • Revisiting window rendering workflow to simplify it
  • Looking at recent report of performance problem in CTabFolder in app with large number of tabs
  • Touching bundles to fix inner jar signing problems - need to make sure we sign what we used to sign
  • Investigating replacement of SAC CSS parser with different parsers
  • Working on enabling use of some IDE views like navigator in an e4 RCP app
  • Enhanced NLS work from Tom+Dirk
    • Everyone in favour of moving into e4 runtime bundle
  • e4 Scripting
    • There is a group looking at reviving scripting support in Eclipse
    • e4 is a potential initial home for the investigation
    • We should let them know about the existing e4 scripting work that has been done already
  • Jface generics
    • work has moved into a branch
    • need to ensure we have a functionally complete subset generified, and at least some concrete viewers ported over to validate the approach
    • Aiming for completion in M3
  • Forking JFace
    • Could enable other kinds of investigation
    • Would be hard to co-exist and adopt
    • Not clear if it is needed for generics alone
    • JFace already makes fairly extensive use of collection-based methods alongside array-based methods