Associate Instructor - Hofstra University
Amazon Top 750 reviewer - Blog - Unresolved References - Book Review Blog
-Nate
Write once, run anywhere, because there's nowhere to hide! - /. A.C.
Associate Instructor - Hofstra University
Amazon Top 750 reviewer - Blog - Unresolved References - Book Review Blog
-Nate
Write once, run anywhere, because there's nowhere to hide! - /. A.C.
Ed Burnette, Author of Hello Android
Blog: ZDNet's Dev Connection - Twitter: @eburnette
Originally posted by Nathan Pruett:
I thought the beef Sun had with MS is that they were providing "platform specific functionality" (i.e. bindings to COM and other MS specific stuff.) inside the core classes (java.lang.*).
Associate Instructor - Hofstra University
Amazon Top 750 reviewer - Blog - Unresolved References - Book Review Blog
Associate Instructor - Hofstra University
Amazon Top 750 reviewer - Blog - Unresolved References - Book Review Blog
But people forget that a "fast" application is not only widget-responsiveness, in real life, applications suck at database calls and business logic, there SWTs speed wont help you in any way.
Originally posted by Ed Burnette:
Everything has its place. Here are some rules of thumb I suggest for people looking at user interfaces:
1. If your primary concern is competing with native desktop applications such as Windows apps written using C++/MFC or C# then you should take a good hard look at SWT (and JFace).
2. If your primary concern is writing a program that runs the same way on Unix, Mac, PC, etc. then Swing is a good choice.
3. If you're trying to target confined platforms with old versions of Java then AWT might be a good choice.
Co-author of <a href="http://www.jdg2e.com" target="_blank" rel="nofollow">The Java Developer's Guide to Eclipse</a>, 2nd Edition<br />(Yahoo group <a href="http://groups.yahoo.com/group/JDG2E/" target="_blank" rel="nofollow">JDG2E</a>)
Consider Paul's rocket mass heater. |