Redian新闻
>
CookSwt: Xml to Swt preview
avatar
c*t
3
hmm, where better ah?
1. As for menu, I don't see the difference.
2. As for layout, CookSwt is better. gridData/rowData etc are really
the layout information for the container. Putting them inside the
child component obscure the layout, particularly when you have child
composite component which in turn has its own layout. Also, CookSwt
allows FormLayout.
3. CookSwt has arrays support such as String[], etc. So, you can
do




【在 c*****s 的大作中提到】
: This works better for me
: http://jakarta.apache.org/commons/jelly/jellyswt.html

avatar
c*s
4
Well, they are doing the same thing so one of them can not be more POWERFUL
than the other. The difference is kind of syntax sugar.
$ expression is used in Velocity, ANT and all jelly syntax in the
same way even the implementations are different. I've been using velocity for
more than 3 years, and using jelly since it was born two years ago. I would
prefer it.
Jelly is so generic that people can use it to do ANYTHING related to XML.
Actually in the two companies I worked in China and US, all xml

【在 c*****t 的大作中提到】
: hmm, where better ah?
: 1. As for menu, I don't see the difference.
: 2. As for layout, CookSwt is better. gridData/rowData etc are really
: the layout information for the container. Putting them inside the
: child component obscure the layout, particularly when you have child
: composite component which in turn has its own layout. Also, CookSwt
: allows FormLayout.
: 3. CookSwt has arrays support such as String[], etc. So, you can
: do
:

相关阅读
logo
联系我们隐私协议©2024 redian.news
Redian新闻
Redian.news刊载任何文章,不代表同意其说法或描述,仅为提供更多信息,也不构成任何建议。文章信息的合法性及真实性由其作者负责,与Redian.news及其运营公司无关。欢迎投稿,如发现稿件侵权,或作者不愿在本网发表文章,请版权拥有者通知本网处理。