This week's book giveaway is in the Kotlin forum.
We're giving away four copies of Kotlin in Action and have Dmitry Jemerov & Svetlana Isakova on-line!
See this thread for details.
Win a copy of Kotlin in Action this week in the Kotlin forum!
  • Post Reply Bookmark Topic Watch Topic
  • New Topic

JSF or Swing Applet?  RSS feed

 
Dave White
Greenhorn
Posts: 3
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I am currently evaluating java technologies and need to make a design decision whether to use JSF or a Swing applet. The product that I am developing is a type of painter that has a toolbar. From the toolbar users must have the ability to "drag and drop" components, draw connections between components, move those components by dragging, etc. While the user is designing within this painter state must be maintained before the set of changes is committed by the user to the server. Accessibility (e.g. section 508 compliance) is desired but not absolutely necessary.

I have designed similar products in the past as non-Swing java applets. My concern with JSF is that it cannot support the GUI requirements I have for this product, especially the "drag and drop" functionality.

Is JSF a good candidate for my requirements, or, should I use java Swing even though it looks like JSF is replacing Swing?

Thanks...
 
Gregg Bolinger
Ranch Hand
Posts: 15304
6
Chrome IntelliJ IDE Mac OS X
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
No, JSF won't work. And I'd advise against an Applet. Look into Java WebStart.
[ June 16, 2005: Message edited by: Gregg Bolinger ]
 
Dave White
Greenhorn
Posts: 3
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
While Java Web Start has many advantages, it looks like one of its main purposes is to separate the application from the browser. My painter application is to interact with other web pages. For example, clicking on a component within the painter would take you to a configuration page within the browser. When the user is done with the screen, (s)he submits the form and returns to the painter application.

Given this scenario, would you still recommend using Java Web Start over a Swing applet? If so, should all configuration pages associated with the painter application be bundled with the application in order to make it "self-contained" outside the browser?

Surprisingly, the Java Web Start specification allows applets to be defined within the JNLP file. Perhaps the Java Web Start application functions as the "parent" application of the applet rather than the browser?

Thanks...

Dave
 
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!