java - Swing versus SWT -


What criteria should I use to choose between SWT and swing? I think they offer both satisfactory GUI performance and platform availability.

Currently in my personal criteria include:

  • Layout / Layout Manager;
  • Data binding;
  • Pre-built controls;
  • Ease of development SWT and swing to choose between my criteria:

      Quality and documentation availability (pieces of docs, books, tutorials)
    1. Number of custom components (both commercial and free)
    2. The quality of the development tools like RAD Window Builder And platform for availability, automatic GUI testing etc.
    3. Learning curve (related to a point) / ease of development

  • Em> notice : my Near small project, there is only professional experience with SWT and my swing experience is very small which can not be taken seriously - my knowledge is rather theoretical rather than practical.

    In short, after my SWT / Eclipse RCP experience - I choose swing on the next project it seems easy to me (SWT) To prevent memory leaks, hand-to-hand diagnostic components do not have to be handled, you add component instead of building components with the information of the original panel, formerly close to my previous experience ... etc.), See native And it seems that you can also come in the swing, Mgr performance is quite good (swt should be faster because it is using the basic components of Bakd OS - but the performance advantage is really big supporter? I do not think so ..). And much more custom components in the swing (it is quite capable of swing) than SWT.


Comments

Post a Comment