Important Notice: Our web hosting provider recently started charging us for additional visits, which was unexpected. In response, we're seeking donations. Depending on the situation, we may explore different monetization options for our Community and Expert Contributors. It's crucial to provide more returns for their expertise and offer more Expert Validated Answers or AI Validated Answers. Learn more about our hosting issue here.

Why should I use XWT instead of writing a Swing Java Applet that uses SOAP/XML-RPC?

April 26, 2017applet Java Soap swing uses writing xml-rpc XWT

0

Posted

Why should I use XWT instead of writing a Swing Java Applet that uses SOAP/XML-RPC?

1 Answer

0

Posted

• Microsoft omitted the MSJVM from Windows XP, and many XP machines do not have Service Pack 1 (which reintroduces the JVM). Installing the Java2 plugin is cumbersome, complex and requires a 15MB download, compared with XWT’s one-click launch and slim 500kb download. • Swing is ugly. • Writing applets requires a real programmer — somebody familiar with computer science. XWT user interfaces, on the other hand, can be developed by designers with little programming experience. • XWT runs as native code on Win32 and Linux (and soon will on Solaris and MacOSX), making it much faster and more responsive than applets. This is especially noticable when scrolling or smooth-resizing. • XWT user interfaces take much less time to develop.