Change Log
Only big or breaking changes are listed. Since there is no semantic versioning for MontiGem, the changes are tagged with a date.
2026-11-05: 7.10.0-SNAPSHOT
- New module
@montigem/chatwith the componentsGemChat,GemChatMessageandGemChatSourcefor AI chats. - Integration of the chat module into the dashboard module and example.
2026-11-03: 7.10.0-SNAPSHOT
- Attribute qualified associations become maps (GemMaps), keyed by an attribute or a to-one
association role of the value:
The owner gets
association Course [[login]] -> (byLogin) Student [1];putByLogin(student),getByLogin(key),containsKeyByLogin(key),removeByLogin(key)and the livejava.util.MapgetByLoginMap(); changing the key attribute of a value moves it in every map holding it. Primitive andStringkeys make aGemValueMap, domain object keys aGemEntryMap. The association must be unidirectional (0xCDC6A) and the value side[1](0xCDC6C); the qualifier must be an attribute or a role of the value (0xCDC69), an attribute of a primitive,Stringor domain class type, notOptional, a collection or an array (0xCDC68), and a role with the cardinality[1](0xCDC6B). Qualified roles are not supported in GUI models yet (0x00032). - Breaking:
java.util.Mapin transpiled Java becomes the asynchronousIUMLPMapof@umlp/commonj2ts, likejava.util.ListbecomesIUMLPList: handwritten TypeScript has toawaitits methods, e.g.await BaseClassObjectMapper.getInstance().getBaseDeSers().get(name) @umlp/commonj2tsmoved to version 9.1.0
2026-10-28: 7.10.0-SNAPSHOT
- The domain model can be copied into the assets of the app, where it is served as
assets/models/<Name>.umlp. It is off by default. Enable it in thebuild.gradleof the frontend:If the domain consists of severalmontigem { publishDomainModels = true }.umlpfiles, the merged model is copied. - The generator uses the npm libraries (
@umlp/*,@montigem/*) of the same build via the dist-tagg-<version>, e.g.g-7.10.0org-7.10.0-SNAPSHOT. The libraries are published as prerelease versions, even if a maven release version of MontiGem is published. An existingpackage-lock.jsonkeeps the old library versions: rungradle :frontend:clean :frontend:npmInstall(ornpm update) to get the current ones *.override.jsonfiles can use Gradle properties, e.g."@umlp/editor": "g-${mg_version}"inpackage.override.json(preferred way to add further@umlp/*or@montigem/*libraries)
2026-10-23: 7.10.0-SNAPSHOT
- MontiCore (and CD4A, GUIDSL, CD2GUI, MontiArc, MCLSG) updated to 7.10.0-SNAPSHOT
2026-10-20: 7.9.3-SNAPSHOT
- Breaking: Reusing class diagrams no longer uses the
<<extends="...">>stereotype. A class diagram now extends every UMLP class diagram it imports from, either via a star import (import CDBase.*;) or an import of a single class (import CDBase.BaseClass;). Remove the stereotype and keep the import. - Cyclic imports between class diagrams are reported as an error (
0x70881)
2026-10-14: 7.9.3-SNAPSHOT
- Support for the
localmodifier of class diagrams
2026-10-07: 7.9.3-SNAPSHOT
-
@umlp/chartsmoved to version 10.0.0 -
Charts migrated to Plotly:
GemBarChart,GemBoxPlot,GemBulletChart,GemCandlestickChart,GemGaugeChart,GemLineChart,GemTimelineChart,GemHeatmapChart,GemPieChart,GemRadarChart,GemSunburstChartandGemScatterPlot- the component definitions (parameters) did not change, but the rendering, layout and styling of the charts may differ from before
- charts now adapt to the size of their container
GemVennDiagram,GemNetworkGraphandGemTimeSeriesChartstill use their previous libraries- vis-lib contains layout/resize tests for the charts (
examples/vis-lib/frontend/src/test/ts/manual)
-
Every chart component has a configuration (context) menu, opened via the gear button
- new parameter
boolean showConfig = falseon every chart controls whether the gear button is shown
- new parameter
-
Fixes for the MontiGem theme (see 7.9.2), which may change the layout of existing pages:
GemRowandGemColumndefault toheight = "auto"andwidth = "auto"(was"100%"); setheight = "100%"explicitly where a container should fill its parentGemTextdefaults towidth = "auto"andheight = "auto"(was"100%")hAlign = "left"andvAlign = "top"inGemRow/GemColumnwork againGemButtonno longer has a minimum width of8remand no extra inner margin, so thewidthandmarginparameters are respected; new parameterString ariaLabelfor buttons without visible textGemImagerespects itswidth/heightparameters and no longer gets a margin and border from the theme- Sass
@importdeprecation warnings are silenced in the generatedangular.json
-
GemButtonhas a new parameterboolean active = falsethat highlights the button as the selected one (e.g. the current category of a navigation bar) GemNavItemhighlights the entry of the current page again; it no longer depends on routerScrollevents and also checks the current route when it is created- The label of
GemLoadingSpinneruses the theme's text color, so it is readable in dark mode - The header cells of
GemTableare styled like the header of aGemCard(with the smaller padding of a table cell) GemMarkdownsupports the dark mode (text, tables, code blocks, quotes and rules use the colors of the theme)MonacoEditorfollows the dark mode of the app: the light themesvs,vs-light,Light +andhc-lightswitch tovs-darkresp.hc-blackwhile the dark mode is activeGemNavListuses the navbar colors of the theme (also in dark mode) and left-aligns the text of its items- Dark mode fixes for the inputs:
GemRangeInput: readable label and tick labels; no highlight box when the slider is clickedGemDropdownInputandGemAutocompleteInput: dark field and dark list of options- Edited inputs (e.g.
GemTextareaInput) are highlighted dark grey instead of light green while focused and invalid inputs dark red instead of light pink GemDateInput: dark calendar popup
- Dark mode for the charts:
- The Plotly based charts get a transparent background, light axis labels, titles and legends and dark grid lines
(see
GemCharts.scssof the theme); colors given by the charts or their data are kept - The settings menu of
GemChartOptionsand the labels ofGemChartLegenduse the colors of the theme
- The Plotly based charts get a transparent background, light axis labels, titles and legends and dark grid lines
(see
2026-08-12: 7.9.2-SNAPSHOT
-
New MontiGem default theme (#4920), see
docs/unstructured/MontiDefTheme.md- the SCSS files of the Gem components moved to
umlp-rte/frontend/theme/src/main/gui/mc/fenix/theme/src/componentsand were renamed to PascalCase (e.g.GemButton.scss) - colors are defined as CSS variables in exchangeable theme designs (
base/theme-designs, e.g.rwth-blue) - new component
GemDarkModeSwitchtoggles between light and dark mode - to use the theme, an app's
styles.scssimports@umlp/theme/.../themeand calls@include montigem-theme(); - the look of existing pages changes (buttons, inputs, cards, images, ...)
- the SCSS files of the Gem components moved to
-
AppComponent ts,html and scss are now generated and do not have to be handwritten anymore
- if you want to modify them their new location is inside the hwc gui directory
- along with this change MontiGem apps are now using the standalone component bootstrap
-
upgraded to Angular 22
- every handwritten Typescript Angular components should add
changeDetection=ChangeDetectionStrategy.EAGERto have the old zone.js based change detection and behavior
- every handwritten Typescript Angular components should add
2026-08-06
- enable package, tsconfig and angular.json override. This will greatly improve frontend dependency update roll-outs for the MontiGem team
- see ProjectSetup.md on how to use them
2026-07-31: 7.9.1-SNAPSHOT
-
Upgraded MontiGem to version 7.9.1-SNAPSHOT
- frontend TypeScript libraries moved to version >8.0.0
-
JSweet transpilation updates which may require adaptations of handwritten typescript:
- GUI-DSL Lists are now
IUMLPList(async) in TypeScript.- if you need a TypeScript array in TypeScript you should use
GemListUtil.toArray(list)
- if you need a TypeScript array in TypeScript you should use
- List, Set, and Stream are not transpiled to JavaScript native array operations
anymore and instead use
AsyncList.ts,AsyncSet.ts,AsynStream.tsimplementations this enables correct behavior of GemLists - any constructor call is now async by default this is achieved by generating
replacing any constructor call with the generated __
Constructor
- GUI-DSL Lists are now
-
Client GemLists are now loaded in batches from the Backend
-
Context Conditions for unsupported Java Code that is transpiled by JSweet. This should stop the current need to guess which code can be transpiled and which not.
2025-09-25
Changes
- Migrated to jsweet
umlp-rte- login module
-
comment module
-
Updated default app project structure, see the top section of project setup.
-
Update default module project structure to closely resemble app project structure
-
Updated gradle plugins:
- Renamed plugins. Naming schema
<SomeCustom>Plugin, for example,ModuleFrontendPlugin,BackendPlugin - Reworked application and module plugins. The details are explained in the
top section of project setup
- Moved common script logic to plugins
umlp-rteis now also a module
- Renamed gradle tasks. Naming schema mostly follows rules:
- something-to-something transformations:
<main_input_type>2<main_output_type>, for example,umlp2sym,cd2gui,gui2jsweetAdapter,umlpJava2ts - there are exceptions:
gui2java2ts- executesgui2java,gui2jsweetAdapter,guiJava2ts;gui2java2- custom project-specific task main_input_typeandmain_output_typemeans "the most important" artifacts, for example,gui2java2tsproduceshtml,sym, JSweet configurations, etc., but the most important produced isjava(andts), because it contains the most of component specification.- creation tasks:
createSymlink,setupFrontend
- something-to-something transformations:
- Updated gradle tasks groups according to their purpose:
- build and jar:
build(buildApp,gui2symJar) - publish:
publishing(publishLib) - tests:
verification(test,slowtest) - transformations and app/module setup:
umlp(umlp2java,setupFrontend,gui2sym)
- build and jar:
- Tasks use lazy API more, for example,
named("gui2java").configure ...vsgetByName("gui2java") - Explicit task dependencies are omitted, if can be properly resolved by Gradle (you may ignore this change)
-
Replaced some deprecated API usage, for example,
getHwcofCommonMCTask- Tasks marked as
Deprecatedmay still use the deprecated features
- Tasks marked as
-
Added default setup for projects in umlp repo (examples, products, experiments): added defaults for
package.json,tsconfig.json -
Removed these configuration files where can
-
Handwritten
jsweetconfig.jsonare now merged into generated one. The location for handwritten file is specified on top in project setup doc. The JSON properties specified in handwrittenjsweetconfig.jsonoverwrite the generated ones (arrays and objects are not merged, except the top-most object). -
Renamed JSweet adapters
- Added JSweet adapters (only generally useful are listed):
ModuleGUIAdapter- transforms*.javagenerated from*.cd(PoJos) and*.gui, specific to MontiGem modules. Equivalent adapter for applications is theGUIAdapter.ModuleUMLPAdapter- transforms*.javagenerated from*.umlp, specific to MontiGem modules. Equivalent adapter for applications is theUMLPAdapter.ConditionalAdapterand some of it implementations. ImplementingskipConditionmethod of this adapter and supplying it with some adapterFooas input will skip theFoowhenskipConditionhits. TheConditionalAdaptercannot skiponTranspilationStartedmethod.
MontiGem is prepared for
umlp2tsgenerator removal. The removal will happen whenPromoDBproject migration is accepted.
2025-06-26
Changes
For MontiGem developers:
Changes in GUI DSL AST and corresponding type checks:
-
Add type parameters
grammar GUIDSL extends de.monticore.symbols.OOSymbols, de.monticore.literals.MCCommonLiterals, de.monticore.types.MCSimpleGenericTypes, + de.monticore.types.TypeParameters, de.monticore.expressions.CommonExpressions, de.monticore.ocl.SetExpressionsTypeParametersare type parameter lists that can be used to declare generic model elements.This change enables the declaration of generic GUI components as follows:symbol GUIComponentDeclaration implements Function = - (["component"] | ["page"]) Name "(" + (["component"] | ["page"]) Name TypeParameters? "(" (GUIParam || ",")* ")" GUIComponentAdaptation? GUIBlock? ;Currently, a CoCo is implemented for GUIDSL that forbids the usage ofcomponent FamilyTree<T>() {}extendsin a type parameter -
Add type arguments
A list of type arguments (defined inscope GUIComponent implements Expression = id:GUIVariableDeclaration? "@" - Name@GUIComponentDeclaration GUINamedArgs + Name@GUIComponentDeclaration GUITypeArgs? GUINamedArgs ; + GUITypeArgs = "<" (MCTypeArgument || ",")* ">";GUITypeArgs) can be added to a GUI component usingMCTypeArgumentprovided inMCSimpleGenericTypes.
This change enables following:
1 | package example.generic;
2 |
3 | import example.Domain.Person;
4 |
5 | page PersonHeritageDetails() {
6 | @FamilyTree<Person>();
7 | }
Person (imported in line 4) as type argument of component FamilyTree in line 6.
2025-03-15
Changes
For MontiGem users:
Enable filtered commands in backend of MontiGem apps. The feature is a prototype. Given a command as a string, for example:
{\"id\":12,\"commandType\":\"loadingtests.commands.Person_get_filtered\",\"participantId\":1,\"filter\":\"[ p | p in Person, p.age > 18, p.age < 23, p.age >= 15, p.age <= 66, p.name == \\\"Alice\\\", p.name != \\\"Bob\\\"]\" }
CommandObjectMapper to deserialize to get a command
object. The command object may also be created using a new constructor with
String filter as an input. The command with a filter will be processed and
return ids of objects satisifying the filter.
Only simple filters can currently be defined. Supported filter options:
- a single generator (p in Person)
- comparison operators (<, >, <=, >=, !=, ==)
- the expressions used in a comparison can either constants (18, "Alice") or
simple field access (p.age) The fteature only supports SQL databases.
Most of the restrictions have a corresponding error message.
For MontiGem developers:
Given a class diagram Foo with a class Bar, following infrastructure (sorted
by the order of execution) handles the commands with filters:
Bar_get_filteredFooManager#_doGetFilteredBarListFooDAOFactory.getBarDAO().selectFilteredBarList(filter)BarDAO#ensureSelectFilteredBarCreatedOCL2SQL(RTE)OCL2SQLPrinter(RTE)BarQueryBuilderMapBarQueryBuilder
2025-02-20
Changes
For MontiGem developers:
Changes in GUI DSL AST and corresponding type checks:
-
add OCL SetExpressions
OCLgrammar GUIDSL extends de.monticore.symbols.OOSymbols, de.monticore.literals.MCCommonLiterals, de.monticore.types.MCSimpleGenericTypes, de.monticore.expressions.CommonExpressions, + de.monticore.ocl.SetExpressionsSetExpressionsincludesSetEnumeration(SetEnumerationis anExpression), which replacesGUIList. This enables lists as default parameter values:7 | List<String> textLines = ["Hello", " world!"],GUIListis removed from GUI DSL:- GUIList = "[" (GUIArgValue || ",")* "]";SetExpressionsincludesSetComprehension, which enables following:9 | List<Car> cars = [c | c in Car, c.color.equals("red")] -
GUIComponent,GUIIterate,GUIGuardimplementExpression:- scope GUIComponent = + scope GUIComponent implements Expression = id:GUIVariableDeclaration? "@" Name@GUIComponentDeclaration GUINamedArgs ; - scope (non_exporting) GUIIterate = + scope (non_exporting) GUIIterate implements Expression = id:GUIVariableDeclaration? "@iterate" "(" IterateControl ")" GUIBlock ; - GUIGuard = + GUIGuard implements Expression = id:GUIVariableDeclaration? "@guard" "(" condition:Expression ")" thenStatement:GUIBlock ("else" elseStatement:GUIBlock )? ;This change enables following:
5 | GUIViewElement title = @GemText(value = "Good"),11 | @iterate(GUIViewElement elem : [@GemText(), @GemButton()]) {Since
GUIComponent,GUIIterate,GUIGuardandGUIListare currently used in places, where anExpressionis being used, the corresponding Production rule is removed:- GUIArgValue = Expression | GUIComponent | GUIGuard | GUIIterate | GUIList; - GUINamedArg = Name@GUIParam "=" GUIArgValue; + GUINamedArg = Name@GUIParam "=" Expression; GUIAdapt = - position:["before" | "after" | "replace"] Name@Variable ":" GUIArgValue; + position:["before" | "after" | "replace"] Name@Variable ":" Expression;
2025-01-15
Additions
- added "generate TypeScript for library" (
gen4TSLib = true) flag to the generator and frontend plugin. The flag forces the generator to generate relative import paths instead of path for source roots. Details in visualization library README.
Changes
For MontiGem users:
- changed source root from
@src/to empty string, e.g.,Migration script:- import { Bar } from '@src/foo/Bar'; + import { Bar } from 'foo/Bar';find . -type d -name "build" -prune -o \( -type f \( -name "*.ts" -o -name "*.java" \) -exec sed -i 's|@src/||g' {} + \) - adjusted default
tsconfig.jsonfile accordingly. In most cases deleting the file should be enough. Adding library paths totsconfig.jsonis no longer necessary. - changed paths to styles from theme library, e.g.,
Migration script:
- @import "../node_modules/@umlp/theme/theme"; + @import "../node_modules/@umlp/theme/src/mc/fenix/theme/theme";find . -type d -name "build" -prune -o -type f -name "styles.scss" -exec sed -i 's|umlp/theme|umlp/theme/src/mc/fenix/theme|g' {} +
For MontiGem developers:
- restructured visualization library. Details in visualization library README.
- partially moved import handling for TypeScript files to
TSImportHelper.
2024-07-24
Additions
- added generator for GUI RTE types, which can now be used backend-side to create gui data.
Documentation can be found in
rte/RTETypesGenerator.md.
2024-06-10
Additions
- from every list or constructor call a local variable is created in a
component, if the object is created outside
@iterate. If the object is inside an@iterate, an entry is added to a local (nested) map pointing to the object.
Example:
GUI model:
page Foo() { bar@PersonCreate(p = Person()); }
class Foo {
protected Person barP_0;
public Person getBarP_0() { /*...*/ }
}
Note: unlike most of the GUI things, the lists and constructors are created once, so we create values once and put them into local variables.
- every component, list, constructor call, component input parameter, and an
iterable of an
@iteratehas an initialization method. Those methods are chained together in a correct order, where the main initialization method is aninitmethod. In Java code, theinitmethod is not called. In TS code, the method is called fromngOnInitof the Angular extension (XComponent.tsclass file).
Example:
GUI model:
page Foo(Person baz) { bar@PersonCreate(p = Person()); }
class Foo {
/* ... attrs ... */
public void init() {
this.initBaz();
}
public void initBaz() {
/* ... baz initialization ... */
initBarP_0();
}
public void initBarP_0() {
/* ... barP_0 initialization ... */
initBarP_0();
}
}
Note: the order is not optimal, will be changed #4130
- every component now has a
destroymethod thatManager.removeObserver(this)
Changes
- no longer allowed to use an unreferencable variable in a GUI model, methods have to be used instead
Example:
Error:
@GemText(value = iDontExist)
@GemText(value = iDontExist())
- allowed to use methods as values for component arguments and iterables of
@iterate. Not allowed to use methods in complex expression that can be refactored as a simple method call.
Note: can be used pretty much anywhere where expected, except
@guardcondition #4131
- renamed
routerto_router
Helpful script for migration:
find . -type d -name 'node_modules' -prune -o -type f -name '*.ts' -exec sed -i 's/this\.route/this\._route/g' {} +
-
replaced DomainBuilder-typed attributes via Domain-typed attributes, e.g.,
PersonBuilder p->Person p. Domain-typed attributes have relevant methods, suchisBuildable(added) andisBuildFinished. -
generated list attributes are changed from
GemListtoArraytypeNote: the conversion is handled by the
initchain, the updates are done viaObserverimplementation. Observer of associations are not handled yet #4133 -
generated constructors now always have 0 parameters. You should call
setmethods for setting input parameters of components. Overridden TS constructors have to callsuper()instead ofsuper(route, router). -
initialization logic must always be in overridden
init.ngOnInitshould not be overridden, unless you know exactly why you need to do it. -
Derived class generation: renamed
getmethods tocalc.getmethods now callcalcby default in Java. In TSgetmethods are abstract (in derived classX), or return local variable (in classXImpl).
Example:
CD:
/ class DerivedInfo {
Foo bar;
}
// DerivedInfo.java
public Foo getBar() {
return calcBar();
}
public abstract Foo calcBar();
Note: needed for init chain
Helpful script for migration:
find . -type f \( -name "*Impl.java" -o -name "*Impl.ts" \) \
-not -path "*/node_modules/*" \
-not -name "ManagerImpl.java" \
-not -name "ClientImpl.java" \
-not -name "ManagerImpl.ts" \
-not -name "ClientImpl.ts" \
-exec sed -i 's/ get/ calc/g' {} +
- renamed derived
sizetocalcSize. Same explanation as above.
Helpful script for migration:
find . -type f \( -name "*Impl.java" -o -name "*Impl.ts" \) \
-not -path "*/node_modules/*" \
-not -name "ManagerImpl.java" \
-not -name "ClientImpl.java" \
-not -name "ManagerImpl.ts" \
-not -name "ClientImpl.ts" \
-exec sed -i 's/ size/ calcSize/g' {} +
-
moved Observer logic from
XComponenttoXclass -
Observerin TS are now extended using mixins instead of local variable initialized with an anonymous class.
Fixes
- Constructor calls and lists should now work properly
Example:
page Foo(Person p) {
@NestedThing(
myNestedList = [[Person(), Person()], p.friends, [p]]
);
}
Eventparameters now get correspondingEventEmitterattributes that are called if the parameter is bound to other event in GUI model.Note: reference parameters still miss proper event emitter logic #4119