c*****t
发帖数: 1879 | 1 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*****t
发帖数: 1879 | 2 http://cookxml.sourceforge.net/cookswt/
The only thing that is lacking is the synchronization of button states.
There seems no listener for enable/disable state.
Resources such as font/color/image will be automatically disposed. |
|
c*****t
发帖数: 1879 | 3 My CookSwt on cookxml.sourceforge.net/cookswt is an XML->GUI thing, but
you need to know pretty well about SWT GUI. There is no JFace XML
converter yet (there is an in-progress version in CVS).
BTW, they are not visual builders. |
|
|
c*****s
发帖数: 214 | 5 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
发帖数: 1879 | 6 Finally got some energy to make some improvements to CookXml.
http://cookxml.sourceforge.net/
CookXml is an XAML which simplifies XML processing. You can pretty much
ignore DOM etc if you use this toolkit. In most cases, it takes one
line of java code to create a new tag to a tag library. This is how I
could single handed finish Swing and SWT tag libraries each in couple days.
New version of CookXml has improved exception handling. It is now
possible to configure CookXml with your own except |
|
