About the build:
I hope the org.eclipse.e4.tm.example, org.eclipse.e4.tm.doc and
org.eclipse.e4.emf.javascript.doc projects can be included in the build.
I will update the wiki in parallel with the docs, but it's nice to
have them in the build, too.
About the tests:
Embarrassing, one of
Hi Kai,
I have no answer to your direct question but everything part of the
context is subject to get injected using @in.
IIRC a new value is always injected when the value in the context
changes but my informations are a bit out dated.
Tom
Toedter, Kai schrieb:
All,
the current cvs breaks
On Fri, May 29, 2009 at 2:45 AM, Toedter, Kai kai.toed...@siemens.com wrote:
All,
the current cvs breaks both Boris' photo demo and my contacts demo. Before I
start filing bugs I would like to understand the strategy behind parameter
injection.
Simple Example: Until yesterday, I could
Hi Angelo,
I think we must not compute default styles but return default SWT
values to reset CSS styles.
Yes, I agree.
I would expect that an SWT based css engine resets all SWT widgets to
the SWT defaults. After the reset, the Look Feel would be the same if
the application would not have used
Hi all modellers and UI programmers,
I've begun documenting an example of the Toolkit Model, to give a better
impression and understanding of how it works. The documentation is part
of the org.eclipse.e4.tm.doc project, while the examples itself is in
org.eclipse.e4.tm.examples, both in CVS.
That's the conclusion I came to as well.
The underlying problem is the interaction between the CSS declarative
styling, and programmatic changes to the widget. In a world where you only
expect CSS to style the widgets then the right answer is as discussed, you
reset the widget to it's default
