Jump to: navigation, search

Difference between revisions of "Graphical Modeling Framework/Versions/GMF 2.3"

Line 18: Line 18:
  
 
== 2.3 M2  ==
 
== 2.3 M2  ==
 +
 +
[https://bugs.eclipse.org/bugs/show_bug.cgi?id=283717 | bugzilla 283717] Custom PropertyTab classes now follow common pattern to produce boilerplate code conditionally, i.e. users may specify existing property tab or let GMF generate a boilerplate code to fill in.
  
 
== 2.3 M3  ==
 
== 2.3 M3  ==
  
 
== 2.3 M4  ==
 
== 2.3 M4  ==
 +
[https://bugs.eclipse.org/bugs/show_bug.cgi?id=282331 | bugzilla 282331] Ant build script for generating GMF diagram editors. GMF comes with a template that generates an Ant build file from a given .genmodel, which can be later run to produce a diagram editor. There are certain distinctions with regular code generation (the one user triggers from UI), namely no code formatting and code merging. Both can be added, if needed, by modification of the Xpand template which produces the Ant build script.
  
 
== 2.3 M5  ==
 
== 2.3 M5  ==
Line 27: Line 30:
  
 
[[Image:CopyToImageDialogQualityOption.png]]
 
[[Image:CopyToImageDialogQualityOption.png]]
 +
 +
== 2.3 M6  ==
 +
[https://bugs.eclipse.org/bugs/show_bug.cgi?id=242150 | bugzilla 242150] Specification of the output folder is now possible for code generator. Those who didn't like default 'src' value - joy and happiness ;)
 +
 +
[https://bugs.eclipse.org/bugs/show_bug.cgi?id=256461 | bugzilla 256461] EObject is implicit superclass now for any object in GMF Xpand and model validation OCL constraints. You can now access operations from EObject (e.g. eContainer()) without any extra quirks with your models.
 +
 +
[https://bugs.eclipse.org/bugs/show_bug.cgi?id=138179 | bugzilla 138179] Expression-backed labels. This is a long-demanded option. One can use OCL (and any other expression language GMF supports) to define how labels look like.
 +
 +
[https://bugs.eclipse.org/bugs/show_bug.cgi?id=304421 | bugzilla 304421] Code generation now is capable to run in background. Well-known Eclipse feature finally for long-running code generation process.

Revision as of 14:55, 10 March 2010

Graphical Modeling Framework 2.3 New and Noteworthy items

See GMF Project Plan for more details

Back to Graphical Modeling Framework

Previous Release N&N Pages

GMF 2.2 New and Noteworthy - Released: June , 2009

GMF 2.1 New and Noteworthy - Released: June 12, 2008

GMF 2.0 New and Noteworthy - Released: June 28, 2007

GMF 1.0 New and Noteworthy - Released: June 30, 2006

2.3 M1

2.3 M2

| bugzilla 283717 Custom PropertyTab classes now follow common pattern to produce boilerplate code conditionally, i.e. users may specify existing property tab or let GMF generate a boilerplate code to fill in.

2.3 M3

2.3 M4

| bugzilla 282331 Ant build script for generating GMF diagram editors. GMF comes with a template that generates an Ant build file from a given .genmodel, which can be later run to produce a diagram editor. There are certain distinctions with regular code generation (the one user triggers from UI), namely no code formatting and code merging. Both can be added, if needed, by modification of the Xpand template which produces the Ant build script.

2.3 M5

A new quality option is available in Save As Image File dialog to select quality parameter for compression if image format support it (currently only JPEG).

CopyToImageDialogQualityOption.png

2.3 M6

| bugzilla 242150 Specification of the output folder is now possible for code generator. Those who didn't like default 'src' value - joy and happiness ;)

| bugzilla 256461 EObject is implicit superclass now for any object in GMF Xpand and model validation OCL constraints. You can now access operations from EObject (e.g. eContainer()) without any extra quirks with your models.

| bugzilla 138179 Expression-backed labels. This is a long-demanded option. One can use OCL (and any other expression language GMF supports) to define how labels look like.

| bugzilla 304421 Code generation now is capable to run in background. Well-known Eclipse feature finally for long-running code generation process.