| Re: [xwt-dev] Status of this project |
>What about using it somewhere e.g. in platform.ui? It is used by the Papyrus. Best regards From: xwt-dev-bounces@xxxxxxxxxxx [mailto:xwt-dev-bounces@xxxxxxxxxxx] On Behalf Of Hoepfner, Marcus Cool. What about using it somewhere e.g. in platform.ui? Or is it too much effort due to usually missing databinding? Means, actually databinding has to be implemented as well. Might introduce new bugs. Thanks, Marcus From: <xwt-dev-bounces@xxxxxxxxxxx> on behalf of Yves YANG <yves.yang@xxxxxxxxxxx> Hi, >on the project page I see only a few contributions in the last year. XWT becomes already mature. Therefore, there are few changes now. For the new version of eclipse, we are working on build now. >So I wonder what is the status of the framework? Is it useable with e.g. EMF and all the flavors like computed values, converters and so on? Yes, it is still usable with EMF. XWT is designed in a standard and extensible architecture. All computed values, converters can be supported. Best regards From: xwt-dev-bounces@xxxxxxxxxxx [mailto:xwt-dev-bounces@xxxxxxxxxxx] On Behalf Of Hoepfner, Marcus Hi, on the project page I see only a few contributions in the last year. So I wonder what is the status of the framework? Is it useable with e.g. EMF and all the flavors like computed values, converters and so on? I wonder why I do not see it in action somewhere in e.g. platform. I really like it and I have used declarative programming in UI5 framework. In my opinion this is actually state-of-the-art. And it supports separation of concerns since I do not mix up business logic and UI as I do with programmatical style. Also it makes UIs easier to reuse. So actually XWT should sell like hotcake 😊 Thanks in advance for your answer. BR, Marcus |