Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 314986

Summary:	Conditions and loops in e4xmi
Product:	[Eclipse Project] e4	Reporter:	Kirill Zotkin <kyrillzotkin>
Component:	UI	Assignee:	Project Inbox <e4.ui-inbox>
Status:	CLOSED WONTFIX	QA Contact:	Boris Bokowski <bokowski>
Severity:	enhancement
Priority:	P3	CC:	bokowski, pwebster, remy.suen, tom.schindl, yves.yang
Version:	unspecified
Target Milestone:	4.1
Hardware:	PC
OS:	Windows XP
Whiteboard:

Description Kirill Zotkin

2010-05-29 15:27:17 EDT

Build Identifier: I20100406-1034

Lack of conditions, switches & loops are a main drawback of declarative xml before  imperative java while defining ui. I suggest to add them to e4xmi format or make it "templatable" to include java code.

Reproducible: Sometimes

Comment 1 Kirill Zotkin

2010-05-30 08:33:21 EDT

Excuse me, i forgot that e4xmi defines ui of entire app.
This could be applied to the separate views if they wasn't defined in java.

Comment 2 Paul Webster

2010-05-31 08:19:35 EDT

e4xmi is the XML representation of EMF.  If we need conditionals in it we would probably allow ECMAScript to be used.

XWT is a declarative GUI XML language.  I'm not sure if it has conditionals and loops.

PW

Comment 3 Yves YANG

2010-05-31 08:35:48 EDT

(In reply to comment #2)
> XWT is a declarative GUI XML language.  I'm not sure if it has conditionals and
> loops.
> 
XWT supports a concept of triggers. The condition expression is used. 

There are several types of triggers:
  1. Control trigger
  2. Multiple Control trigger
  3. Data Trigger
  4. Multiple Data Trigger
  5. Event Trigger

Here is my blog:
http://dev.eclipse.org/blogs/yvesyang/2009/10/12/xwt-ui-trigger-1/

You can find more detail information about this concept. 

yves

Comment 4 Thomas Schindl

2010-05-31 08:38:38 EDT

You don't have to build an application using e4xmi-Files in the latest e4 builds you have 2 possibilities to make up the application in a progammatic way:

a) Using Processors
   * Create a minimal e4xmi (it only has the Application-Element)
   * Create a contribution.e4xmi and install a Processor on the element
   => Create your UI model in Java

b) Replace the default ModelResource Handling
   (available since last week)
   => You can redefine the model resource creation by creating your own 
      implementation of IModelResourceHandler and redefine the resource-loading 
      instance in your product-extension point like this:
---------8<---------
         <property
               name="modelResourceHandler"
               value="platform:/plugin/my.plug.in/MyModelResource">
         </property>
---------8<---------

Comment 5 Thomas Schindl

2010-05-31 08:41:24 EDT

I think those 2 possibities make this request obsolete or are we now discussing XWT then I think we should move this bug to XWT.

Comment 6 Thomas Schindl

2011-08-15 14:26:22 EDT

as my last comment suggest this is nothing we are going to implement in e4xmi. To define the inner part of a view you'd use XWT and if they don't support this please reopen this bug and move it to XWT