This service is archived, please use www.eclipse.org/forums


Home » Archived Projects » Kitalpha » Problem with odesign diagram extension
Problem with odesign diagram extension [message #759] Thu, 31 March 2016 07:39 Go to next message
labin78.hotmail.com is currently offline  labin78.hotmail.com
Messages: 51
Registered: December 2015
Member
Hi,

1) In my application, there is the following model:
index.php/fa/203/0/

2) In kitalpha, i write the monvp.diagram.vptext :

Diagrams monextension.diagram {
	
	DiagramExtension "diagramExtension_1" {
		extended-diagram:[b] Mon Diagram[/b] //extended diagram
		Mapping {
			Container [b]LeafExtensionContainer[/b] {
				import: [b]Leaf Component[/b] //import a container
				Contains {
					Node Test{
						
                                                  ....
						
						}
						Contains {
							
						}
					}
				}
			}
		}
		Actions {
			....
		}
	}



3) After the generation, the following odesign is generated:
index.php/fa/204/0/
I think there is a problem, because the Root Component should be the parent of the Leaf Component. The display in my application is false.

4) The good odesign should be this one ?
index.php/fa/205/0/

Thanks.
Re: Problem with odesign diagram extension [message #764 is a reply to message #759] Wed, 06 April 2016 08:36 Go to previous messageGo to next message
labin78.hotmail.com is currently offline  labin78.hotmail.com
Messages: 51
Registered: December 2015
Member
Hi,

When I inspect in the kitalpha source code, there is a MappingImportKing enum.
This enum can be "SPECIFIED" or "AUTO".
I understand that this enum has impact on my problem. When i modify the enum's value (in the source code) then the "odesign" is correctly build.
Can we configure the value of this enum ?


Thanks
Re: Problem with odesign diagram extension [message #808 is a reply to message #764] Tue, 26 April 2016 07:58 Go to previous message
boubekeur.zendagui@thales is currently offline  boubekeur.zendagui@thales
Messages: 54
Registered: April 2015
Member
Hi,

This enumeration is technical and is used only by the diagram generation. It allows to separate between the MappingImports specified by end-users (in *.diagram.vptext) and the ones imported automatically.

The MappingImports generated automatically are computed by diagram generation. Without them, the extended Sirius diagram behavior will change when the generated diagram extension is activated.

I gess in monappli.odesign, the Leaf Component reuses the Root Component. Anyway, the diagram generation should be improved to manage that case.

Regards,
Boubekeur.
Previous Topic: Kitalpha and Grammar extension
Next Topic: Transposer from something to ecore
Goto Forum:
  


Current Time: Tue Feb 18 07:18:39 EST 2020

Total time taken to generate the page: 0.01651 seconds