Datasets:
UWECProgrammer
/
ConsolidatedMentionResolutionBenchmark

Dataset card Data Studio Files
xet
Community
1
sentence
stringlengths
1
1.38k
label
stringclasses
3 values
This might suit perfectly as it's a tried and proven framework.
p
URL_http://en.wikipedia.org/wiki/Java_Swing [Swing] Based on AWT as previously stated.
o
In its infancy it was regarded as slow and buggy and caused IBM to create SWT for Eclipse.
n
However with Java 5 (or 6?
o
) Swing became the framework of choice for building new applications.
o
Swing has a lot of rich components but are still lacking in some areas.
n
One example being that there isn't a full featured TreeTable component which can do sorting and filtering/searching.
o
URL_http://en.wikipedia.org/wiki/Standard_Widget_Toolkit [SWT] Created by IBM for Eclipse, they seemed to think that Swing was not suited for Eclipse at the time.
o
By itself is pretty low-level, and it uses the platform's native widgets through JNI.
n
It is not related to Swing and AWT at all.
o
Their API is however somewhat clunky and not intuitive.
p
They do have some advanced component's like a TreeTable.
o
(but i don't think they support sorting and filtering out of the box).
o
SWT uses some native bindings (through JNI?
o
) and the rant on the internet is that this framework should not be used in today's projects.
n
(why not?
o
) URL_http://en.wikipedia.org/wiki/SwingX [SwingX] Based on Swing and it's mission is to create rich components for swing.
o
Still under development.
o
(not very active though.
o
) Have a very nice set of components, like for example TreeTable.
p
But the TreeTable does not support filtering and sorting as far as i know.
o
It does however support searching with highlighting.
p
Note that SwingX is components (AFAIU) that are extensions or compositions of existing Swing components A framework which i know nothing about... What is it's strengths and weaknesses?
o
What set's Jgoodies apart from the rest?
o
JGoodies OTOH is about PLAFs and layouts.
o
URL_http://en.wikipedia.org/wiki/JavaFX [JavaFX] The latest flagship of Java/Oracle.
o
promising to be the facto standard in developing rich desktop or web applications.
p
URL_http://en.wikipedia.org/wiki/Apache_Pivot [Apache-Pivot] It renders UI using Java2D, thus minimizing the impact of (IMO, bloated) legacies of Swing and AWT.
n
(@Augustus Thoo) It's main focus seems to be on RIA (Rich internet applications), but it seems it can also be applied to desktop applications.
o
And as a personal comment, Looks very interesting!
p
I Especially like that it's an apache project.
o
URL_https://cwiki.apache.org/PIVOT/frequently-asked-questions-faq.html [ URL_https://cwiki.apache.org/PIVOT/frequently-asked-questions-faq.html ] URL_http://en.wikipedia.org/wiki/Qt_Jambi [Qt-Jambi] A java wrapper to the native qt library which is written in c/c++.
o
Very powerful, widely used and accepted.
p
Has a lot of GUI components and a easy to use API.
p
URL_http://qt-jambi.org/ [ URL_http://qt-jambi.org/ ] So, to try to summarize a bit of what im asking: Say i wanted to create a desktop application today in Java which involves a lot of advanced components, what should i choose?
o
And why?
o
Which one of these frameworks should be recognized as deprecated and which should be recognized as the frameworks of the distant future?
o
What is todays de-facto-standard framework and which tools do you utilize to create java gui applications?
o
I might regret asking this, but ill try it anyways: C#/.Net is said to have a very good set of easy to use components which can be flexed in every direction possible.
p
And after investigating different java frameworks to some extent i can't seem to say the same about Java.
o
Why is this?
o
_Why doesn't java (which is the most widely used programming language in the world) have the same set of GUI components?_ Is it just that java has based their gui components at a much lower level, and it is possible to write all these advanced components that im looking for, but you have to do much if not all of the work yourself?
o
Hi.
o
I am using JFace and RCP for rich clients.
o
Both are SWT based and provide UI features and helpers that would be tedius to implement in native SWT.
o
+1 for _Why doesn't java (which is the most widely used programming language in the world)_.
o
AWT might however look somewhat ugly on some operating systems.
n
"* I disagree.
o
It uses native components, so it will only look as beautiful or ugly as the other components generally seen in that OS.
n
Or to put that another way, it would look much like the equivalent Swing components when they are set to the native PLAF.
o
AWT's major failing is it's lack of components & functionality.
n
E.G.
o
no tree, no table, no HTML rendering support..
o
@Andrew, thanks.
o
ill update the text.
o
@netbrain Thanks back at you for asking an interesting, well researched question.
p
If it was rubbish, I would not have been motivated to correct one minor misunderstanding.
n
I wasn't aware that SWT was "based on a combination of AWT and Swing".
o
Is that really the case?
o
I thought it was pure JNI to invoke the OS's windowing system...
o
@Rich Oh, it was said in one of the answers comments.
o
I just assumed they knew what they were talking about.
o
I think you confuse "UI Toolkit" and "GUI framework".
n
AWT, Swing and SWT are UI toolkits but I would certainly not call them "frameworks".
o
Frameworks are based upon a given UI toolkit and provide the glue to build your application.
o
First, you should choose the UI toolkit and then choose a framework that works on that toolkit.
p
FWIW, I would choose Swing with my own home-made Guts-GUI framework :-).
o
It's almost always Swing vs. SWT (for me at least), for small comparison you could check [What are the main things that an experienced Java SWT programmer should be aware of when moving to Swing?
o
]( URL_http://stackoverflow.com/questions/6659413/what-are-the-main-things - that-an-experienced-java-swt-programmer-should-be-aware/6661296)..
o
is no more part of preview SDK and it is available for Production use.
o
please update this post.
o
I just use AWT and Swing and I can do almost everythig, so thumbs up for them :).
o
Can we downvote all the people who voted this closed as "not constructive"?
o
The question close nannies strike again!.
o
Close as not constructive is subjective at best.
p
Why should some person that may have a grudge or having a bad day be able to remove content valuable to a community?
o
Maybe we can get some votes to reopen this question?
o
Decision tree: 1.
o
Frameworks like Qt and SWT need native DLLs.
o
So you have to ask yourself: Are all necessary platforms supported?
o
Can you package the native DLLs with your app?
o
URL_http://stackoverflow.com/questions/2037220/how-can-i-creating-executable- jar-with-swt-that-runs-on-all-platforms [See-here,-how-to-do-this-for-SWT] .
o
If you have a choice here, you should prefer Qt over SWT.
p
Qt has been developed by people who understand UI and the desktop while SWT has been developed out of necessity to make Eclipse faster.
p
It's more a performance patch for Java 1.4 than a UI framework.
o
Without JFace, you're missing many major UI components or very important features of UI components (like filtering on tables).
o
If SWT is missing a feature that you need, the framework is somewhat hostile to extending it.
o
For example, you can't extend any class in it (the classes aren't final, they just throw exceptions when the package of CODETERM1 isn't CODETERM2 and you can't add new classes in that package because it's signed).
n
2.
o
If you need a native, pure Java solution, that leaves you with the rest.
o
Let's start with AWT, Swing, SwingX - the Swing way.
o
AWT is outdated.
o
Swing is outdated (maybe less so but not much work has been done on Swing for the past 10 years).
o
You could argue that Swing was good to begin with but we all know that code rots.
p
And that's especially true for UIs today.
o
That leaves you with SwingX.
o
After a longer period of slow progress, URL_http://java.net/projects/swingx/sources/svn/history?
o
[development-has- picked-up-again] .
o
The major drawback with Swing is that it hangs on to some old ideas which very kind of bleeding edge 15 years ago but which feel "clumsy" today.
n
For example, the table views do support filtering and sorting but you still have to configure this.
o