By bloid
via eclipsezone.com
Published: Feb 20 2007 / 02:36
Ok, every flame-war about Swing vs SWT and how IBM is trying to sink Sun's boat aside, SWT is a pretty interesting toolkit. It's one of only two major Java GUI APIs available today. Yet, despite all this "cool ooze", SWT adoption remains fairly low.
-
Using HoverMenuExtender with ASP.NET ListView to Update, Delete and Insert Records
-
Update on the GDR that is coming for .NET Framework 3.5 SP1
-
Mastering Eclipse V3.4: Java Development Tools (JDT)
-
Let Internet Explorer 6 Behave Like Internet Explorer 7
-
What does ‘SharePoint in the cloud’ really mean?
-
This is How the Web Gets Regulated
Comments
jola_zm replied ago:
Buyer beware...
http://www.hacknot.info/hacknot/action/showEntry?eid=74
tjsnell replied ago:
Went to test a new product from a vendor the other day. They used SWT. Go to start the application and get an SWT library not found type error. Lovely. Head over to Eclipse.org to just download the swt install. Oops, no SolarisX86 support. Done. Competitor's product won, it's Swing based and runs everywhere I have a JRE.
daniel replied ago:
This is exactly why SWT isn't a more commonly used framework. There's a lot of misinformation floating around about it. And a lot of the "information" which is out there is misleading.
SWT actually does support Solaris. Also, in this case the competitor's product really deserved to win. Not because they used Swing, but because they didn't horribly botch their deployment. If you install an application, you don't inspect to have to install a third party library yourself to make it work, the application should do that for you. The problem you're describing is a shortcoming with the application's deployment, not a problem with SWT.
tjsnell replied ago:
Misleading?
Please give me a link to download Solaris86 (NOTE the 86, SWT does indeed support Solaris Sparc but that doesn't do me any good).
tjsnell replied ago:
And another reason SWT will continue to only live on the fringe. I have to have OS specific stuff for every OS I want my app to run on when I package it. I'd rather not mess with packaging up os specific libraries with my Java app.
daniel replied ago:
Either the Motif or the GTK+ ports (compiled for x86 linux) should work just fine. Either that, or you could compile your own based on the source for those two ports without a problem.
As I said, this is a problem with the deployment process of the app in question, not SWT. They should have made certain you had the necessary libraries.
tjsnell replied ago:
I have no desire to compile my own. I went to use an SWT app (USE NOT DEVELOP) and we told by multiple people, yeah, you have to compile it for Solaris86. The vendor chose SWT and therefore doesn't support Solaris86. Their target market is not developers and they've limited the OS choice of their customers by going SWT over Swing.
Yeah, SWT is going to take off!
Voters For This Link (9)
Voters Against This Link (0)