Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
Next revisionBoth sides next revision
research:plomo [2013/09/21 09:11] – mdenkerresearch:plomo [2013/09/21 09:16] – mdenker
Line 118: Line 118:
   *  Faster MSE import.   *  Faster MSE import.
  
-We participated to the new release of Pharo 1.4 and 2.0 and are actively developing Pharo3. The speed of Pharo development is increasing with each version. For Pharo2, a list of changes can be found on the [[http://code.google.com/p/pharo/wiki/ActionsInPharo20|website]]. +We participated to the new release of Pharo 1.4 and 2.0 and are actively developing Pharo3 (http://pharo-project.org). The speed of Pharo development is increasing with each version. For Pharo2, a list of changes can be found on the [[http://code.google.com/p/pharo/wiki/ActionsInPharo20|website]]. 
-PLOMO members contributed many smaller and larger improvements found while doing the research work described in this report. When visiting, PLOMO members take care to organize Pharo Sprints (open meetings focussed on fixing bugs and integrating features).+PLOMO members contributed many smaller and larger improvements found while doing the research work described in this report. When visiting, PLOMO members take care to organize Pharo Sprints, open meetings focussed on fixing bugs and integrating features.
  
-An example for how PLOMO directly contributed can be seen with the type system work. While type-checking the code of the Pharo system, a number of problems where detected. Examples where dead code, wrong inheritance relationships between classes and others. All these problems have been fixed in Pharo2.+A small example for how PLOMO directly contributed can be seen with the type system work. While type-checking the code of the Pharo system, a number of problems where detected. Examples where dead code, wrong inheritance relationships between classes and others. All these problems have been fixed in Pharo2.
  
 For Pharo3, PLOMO contributed in a major way: the Opal Compiler replaced the old default compiler infrastructure. For Pharo3, PLOMO contributed in a major way: the Opal Compiler replaced the old default compiler infrastructure.
Line 191: Line 191:
  
 == From PLEIAD to RMoD == == From PLEIAD to RMoD ==
-  * Vanessa Peña and Alexandre Bergel, Aug 15 until Aug 20, 2011. From Aug 20 until Aug 28 they attended [[ESUG|http://www.esug.org/wiki/pier/Conferences/2011]], a conference co-organized by RMoD. The topic of this research visit is test coverage and software visualization. Result of the research activity on software visualization and code profiling have been presented at ESUG. +  * Vanessa Peña and Alexandre Bergel, Aug 15 until Aug 20, 2011. From Aug 20 until Aug 28 they attended [[http://www.esug.org/wiki/pier/Conferences/2011/ESUG]], a conference co-organized by RMoD. The topic of this research visit is test coverage and software visualization. Result of the research activity on software visualization and code profiling have been presented at ESUG. 
   * Romain Robbes from July 18 until July 24, 2011. Partially funded by Pleiad.   * Romain Robbes from July 18 until July 24, 2011. Partially funded by Pleiad.
   * Esteban Allende from July 19 until October 2, 2011. Esteban's stay was partially funded by the French Embassy in Chile.    * Esteban Allende from July 19 until October 2, 2011. Esteban's stay was partially funded by the French Embassy in Chile.