Comments for Life's Passion http://dev.eclipse.org/blogs/yvesyang My Projects in Eclipse Tue, 24 Nov 2009 03:49:40 +0000 http://wordpress.org/?v=2.6.5 Comment on XWT - UI Trigger (1) by ekkehard http://dev.eclipse.org/blogs/yvesyang/2009/10/12/xwt-ui-trigger-1/#comment-72 ekkehard Sat, 17 Oct 2009 08:43:40 +0000 http://dev.eclipse.org/blogs/yvesyang/?p=51#comment-72 I'm going a different way - we're developing redview http://redview.org (Riena EMF Dynamic Views for Business Applications) all SWT Widgets (more from Nebula will come) are available, can be designed from a WYSIWYG editor inside eclipse IDE with live-pushing to running RCP Apps thru CDO all based on EMF models and dynamically rendered at Runtime -- first releases in nov/dec runs on eclipse 3.6 - at beginning of 2010 we'll also integrate with e4 redView is developed with the goal to simplify RCP Business Applications and based on Eclipse Runtime (Riena, Equinox) and Eclipse Modeling (EMF, CDO) with integration to Xpand/Xtend/MWE for a whole model-driven life-cycle ekke I’m going a different way - we’re developing redview http://redview.org
(Riena EMF Dynamic Views for Business Applications)
all SWT Widgets (more from Nebula will come) are available,
can be designed from a WYSIWYG editor inside eclipse IDE
with live-pushing to running RCP Apps thru CDO
all based on EMF models and dynamically rendered at Runtime
– first releases in nov/dec
runs on eclipse 3.6 - at beginning of 2010 we’ll also integrate with e4
redView is developed with the goal to simplify RCP Business Applications and based on Eclipse Runtime (Riena, Equinox) and Eclipse Modeling (EMF, CDO) with integration to Xpand/Xtend/MWE for a whole model-driven life-cycle
ekke

]]> Comment on XWT - UI Trigger (1) by Yves YANG http://dev.eclipse.org/blogs/yvesyang/2009/10/12/xwt-ui-trigger-1/#comment-71 Yves YANG Fri, 16 Oct 2009 21:42:25 +0000 http://dev.eclipse.org/blogs/yvesyang/?p=51#comment-71 For sure, the data binding is important and fundamental. XWT already supports it, which is demonstrated in the e4 contact demo: http://wiki.eclipse.org/E4/XWT/Running_the_demos And this concept is also showed in e4 Webinar. You just need to select the Java model class, and then you generate the presentation with data binding. The declarative UI about dynamic aspect is nice-to-have, particularly for MDA: UI generation based on business model. Can you image the difficulties to generate dynamic control in Java code? For sure, the data binding is important and fundamental. XWT already supports it, which is demonstrated in the e4 contact demo:
http://wiki.eclipse.org/E4/XWT/Running_the_demos

And this concept is also showed in e4 Webinar. You just need to select the Java model class, and then you generate the presentation with data binding.

The declarative UI about dynamic aspect is nice-to-have, particularly for MDA: UI generation based on business model. Can you image the difficulties to generate dynamic control in Java code?

]]> Comment on XWT - UI Trigger (1) by JD http://dev.eclipse.org/blogs/yvesyang/2009/10/12/xwt-ui-trigger-1/#comment-70 JD Fri, 16 Oct 2009 19:11:42 +0000 http://dev.eclipse.org/blogs/yvesyang/?p=51#comment-70 Nice. While I second Stephan's opinion, I recon it can be used quite well to provide additional feedback to the user, though. Nevertheless Stephan is right. It is dangerous from an architect's point of view. There will be a lot of programmers out there who will be tempted to implement enforcement of constraints, which can not be put directly into the model on this level. For example something among the lines "Checkbox A must be checked when Checkbox B is checked. Quite like you've actually showed in the examples, Yeves. What's really needed here is a declarative controller-markup in the middle, which binds the model to the GUI. Nice.
While I second Stephan’s opinion, I recon it can be used quite well to provide additional feedback to the user, though.
Nevertheless Stephan is right. It is dangerous from an architect’s point of view. There will be a lot of programmers out there who will be tempted to implement enforcement of constraints, which can not be put directly into the model on this level. For example something among the lines “Checkbox A must be checked when Checkbox B is checked. Quite like you’ve actually showed in the examples, Yeves.
What’s really needed here is a declarative controller-markup in the middle, which binds the model to the GUI.

]]> Comment on XWT - UI Trigger (1) by Yves YANG http://dev.eclipse.org/blogs/yvesyang/2009/10/12/xwt-ui-trigger-1/#comment-69 Yves YANG Thu, 15 Oct 2009 20:20:10 +0000 http://dev.eclipse.org/blogs/yvesyang/?p=51#comment-69 >As far as I understood, the idea was to separate UI notation and behavior. >But now you give again e.g. with setter the possibility to add behavior where it NOT should be, in the UI declaration. It is the separation of UI aspect with business logic behind. All presentation aspect should stay as maximum as possible in declarative UI. >What is the next step? >Loops, Calculation, … At the end why we need java any more? Java is used to develop application model, business logic and other aspects that Declarative XML doesn't handle. >As far as I understood, the idea was to separate UI notation and behavior.
>But now you give again e.g. with setter the possibility to add behavior where it NOT should be, in the UI declaration.

It is the separation of UI aspect with business logic behind. All presentation aspect should stay as maximum as possible in declarative UI.

>What is the next step?
>Loops, Calculation, … At the end why we need java any more?
Java is used to develop application model, business logic and other aspects that Declarative XML doesn’t handle.

]]> Comment on XWT - UI Trigger (1) by Stephan http://dev.eclipse.org/blogs/yvesyang/2009/10/12/xwt-ui-trigger-1/#comment-68 Stephan Thu, 15 Oct 2009 19:53:47 +0000 http://dev.eclipse.org/blogs/yvesyang/?p=51#comment-68 I personally think, most of this is a step backwards! As far as I understood, the idea was to separate UI notation and behavior. But now you give again e.g. with setter the possibility to add behavior where it NOT should be, in the UI declaration. What is the next step? Loops, Calculation, ... At the end why we need java any more? We have a new language and we are at the starting point, putting all in one ... -> stop it now ! PS: I know this is provoking but what do other think? everybody viewless? I personally think, most of this is a step backwards!

As far as I understood, the idea was to separate UI notation and behavior.
But now you give again e.g. with setter the possibility to add behavior where it NOT should be, in the UI declaration.

What is the next step?
Loops, Calculation, … At the end why we need java any more?

We have a new language and we are at the starting point, putting all in one …

-> stop it now !

PS: I know this is provoking but what do other think? everybody viewless?

]]> Comment on XWT - UI Trigger (1) by Yves YANG http://dev.eclipse.org/blogs/yvesyang/2009/10/12/xwt-ui-trigger-1/#comment-67 Yves YANG Wed, 14 Oct 2009 22:52:47 +0000 http://dev.eclipse.org/blogs/yvesyang/?p=51#comment-67 Sure. I have answered you in the forum. Sure. I have answered you in the forum.

]]> Comment on XWT - UI Trigger (1) by Erdal http://dev.eclipse.org/blogs/yvesyang/2009/10/12/xwt-ui-trigger-1/#comment-66 Erdal Wed, 14 Oct 2009 17:05:15 +0000 http://dev.eclipse.org/blogs/yvesyang/?p=51#comment-66 Can this also be applied to viewers? See http://www.eclipse.org/forums/index.php?t=msg&th=155894&start=0&S=5c8d14ffa36fae8250bc04b4ff719861 How can this be used to make a viewer reload its input based on the selection of another control? Can this also be applied to viewers?

See http://www.eclipse.org/forums/index.php?t=msg&th=155894&start=0&S=5c8d14ffa36fae8250bc04b4ff719861

How can this be used to make a viewer reload its input based on the selection of another control?

]]> Comment on XWT - UI Trigger (1) by Yves YANG http://dev.eclipse.org/blogs/yvesyang/2009/10/12/xwt-ui-trigger-1/#comment-65 Yves YANG Mon, 12 Oct 2009 21:59:14 +0000 http://dev.eclipse.org/blogs/yvesyang/?p=51#comment-65 you can use the binding expression with static extension text="{x:Static y:Message.Name}" where y the prefix of a namespace corresponding to Java package, Message is a Java Resource bundle, and name is a static constant. It is already supported by XWT you can use the binding expression with static extension

text=”{x:Static y:Message.Name}”

where y the prefix of a namespace corresponding to Java package, Message is a Java Resource bundle, and name is a static constant.

It is already supported by XWT

]]> Comment on XWT - UI Trigger (1) by ekkehard http://dev.eclipse.org/blogs/yvesyang/2009/10/12/xwt-ui-trigger-1/#comment-64 ekkehard Mon, 12 Oct 2009 21:51:30 +0000 http://dev.eclipse.org/blogs/yvesyang/?p=51#comment-64 nice idea, but.... ... how do you localize it ? in business apps values are never hardcoded nice idea, but….

… how do you localize it ?
in business apps values are never hardcoded

]]> Comment on XWT - Getting started by Rencana http://dev.eclipse.org/blogs/yvesyang/2009/01/17/xwt-getting-started/#comment-63 Rencana Sat, 19 Sep 2009 18:39:04 +0000 http://dev.eclipse.org/blogs/yvesyang/?p=8#comment-63 Hi Yves, thanks for reply. when i run databinding, it should be display "toto" at the text field, right ? but i don't see any text there, what should i do for this ? Thanks, CanA Hi Yves, thanks for reply.
when i run databinding, it should be display “toto” at the text field, right ?
but i don’t see any text there, what should i do for this ?

Thanks,
CanA

]]>