[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
RE: [e4-dev] how to contribute to toolkit model ?
|
Hi Hallvard,
I think we should not push a solution for technology reason. It is what I
said to use a technology blindly like a religion. Each technology has been
designed for a specific purpose and therefore it has its limitation. A magic
pill for illnesses doesn't exist.
We should focus on what we should provide as solution in e4, and select a
suitable solution to reach this goal.
As for e4, We are in short time. We should not reinvent the wheel. As you
said, XAML is proved by industry, it is complete and safe solution.
However, AFIAK, TM is still in research stage. In general, from research to
industry, the path may be long.
Best regards
Yves YANG
-----Original Message-----
From: e4-dev-bounces@xxxxxxxxxxx [mailto:e4-dev-bounces@xxxxxxxxxxx] On
Behalf Of Hallvard Trætteberg
Sent: Monday, August 31, 2009 4:22 PM
To: E4 Project developer mailing list
Subject: Re: [e4-dev] how to contribute to toolkit model ?
yves (yingmin) yang wrote:
>> i think that e4 should definitly work on this emf-centric toolkit
> instead of XWT...
>
> With all respects to you and your solution, I remind you kindly to give us
> your arguments when you compare to another solution.
In the minutes of the last e4 call, the final bullet asked if e4 should
include both TM and XWT. I think it should include only one of them, but
whatever the choice, there's nothing preventing the other to co-exist as
an installed plugin.
There are many ways of comparing TM and XWT, but what is most important
when it comes to deciding which to support? E.g. we can compare feature
by feature, like how easily a custom widget may be supported (XWT wins,
I believe). Another could be how it will blend in with and potentially
be used by other parts of e4 and "core" Eclipse technologies (TM wins, IMO).
Personally, I think (something like) TM should be chosen, not because TM
is better (or much different) than XWT, but because of EMF is preferable
to XML, in the context of e4 and Eclipse. Although XML is used
throughout industry for a many purposes and many good XML tools exist,
EMF has reached a very high penetration within the Eclipse community,
while Eclipse's support for XML is still not that good. Interesting
EMF-based projects seems to pop up everywhere, and frameworks like CDO
increases the potential of EMF-based tools manyfold. E.g. TM UI + EMF
data + CDO = Shared, cloud ready applications.
There's really no point, that only Yves and I argue over this, as it's
us all as a community that should discuss and decide...
Hallvard
_______________________________________________
e4-dev mailing list
e4-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/e4-dev
Internal Virus Database is out of date.
Checked by AVG - www.avg.com
Version: 8.5.392 / Virus Database: 270.13.58/2306 - Release Date: 08/16/09
06:09:00
