472841 – Introduce model adaptation API

Bug 472841 - Introduce model adaptation API

Summary: Introduce model adaptation API

Status:	RESOLVED FIXED

Alias:	None

Product:	Handly
Classification:	Technology
Component:	Core (show other bugs)
Version:	0.4
Hardware:	All All

Importance:	P3 enhancement
Target Milestone:	0.4
Assignee:	Vladimir Piskarev
QA Contact:

URL:
Whiteboard:	modeladaptation
Keywords:	api

Depends on:
Blocks:	472840
	Show dependency tree

Reported:	2015-07-16 09:53 EDT by Vladimir Piskarev
Modified:	2015-11-03 01:05 EST (History)
CC List:	0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Vladimir Piskarev

2015-07-16 09:53:48 EDT

Need to introduce a model adaptation API for supporting legacy models (see bug 472840 for the general context).

The API would define a one-to-one correspondence (bijection) between elements of a Handly based model and elements of an adapter model. The Handly based IDE components such as an outline framework could then deal with the adapter model's content via this API.

Comment 1 Vladimir Piskarev

2015-07-16 10:21:30 EDT

Pushed to master:

http://git.eclipse.org/c/handly/org.eclipse.handly.git/commit/?id=ec31efe9320d0283ace7caacf211daff21834b41

Comment 2 Vladimir Piskarev

2015-07-22 09:17:53 EDT

Further polish:

* http://git.eclipse.org/c/handly/org.eclipse.handly.git/commit/?id=9d3d6e5dcd0f42371864c61cb16e282e3b29c8f0

* http://git.eclipse.org/c/handly/org.eclipse.handly.git/commit/?id=a8b23e494331f1a0613c07fb5ce9ddbfb9b8cc26

Comment 3 Vladimir Piskarev

2015-07-22 10:11:31 EDT

The use of the term 'adapter model' in comment 1 is unfortunate because either model can actually be the 'adapter' from implementation point of view. It's better to restate it in other words:

The API would define a one-to-one correspondence (bijection) between elements of a Handly based model and elements of some other model. The Handly based IDE components such as an outline framework could then deal with the other model's content via this API.