This question already has answers here:
What is Java's answer to WPF? [closed]
(3 answers)
Closed 9 years ago.
We are doing an evaluation of what to use for client technology, I was wondering what Java has to offer.
I know that this is a close duplicate to this question:
What is Java's answer to WPF?
But the answer in the above question is over 2 years old, so the answer today could be different.
This 2011 Java wil lunch JavaFX 2.0, you will use the JavaFX API's with core Java language instead of the JavaFX Script in 1.x versions.
I concur with the others here that JavaFX was probably intended to be Sun's answer to WPF and Silverlight, but it's never quite reached the standard that Microsoft's technologies have.
Another Java alternative to Silverlight is BlazeDS and Spring BlazeDS which use a Java application server as the backend, and Adobe Flash as the client (using Flex). I've never used it, but the combination looks pretty similar to using Silverlight.
JavaFX is in full swing and Oracle has already made early access release available. More answers can be found here, but surely a competitor is in the making that will give its counterpart a tough time soon
I think that JavaFX still lives. You can check Eclipse Rich Ajax Platform too. I think this is suitaible answer to Silverlight.
Related
This question already has answers here:
Java / Jakarta EE web development, where do I start and what skills do I need? [closed]
(9 answers)
Closed 5 years ago.
For my bachelor degree I need to develop a responsive Web Application using JSF and Prime Faces.
My problem is that I have no clue of how to start it.
Can you recommend me what tools should I use (all of them)? Where can I find a "Hello world!" like tutorial, explained for users with no experience? From where can I get UI components like buttons, menus, etc?
Thank you very much.
PS: English is not my native language.
I don't know why you asking it, because the answer is on the official site, they have learning section: http://www.primefaces.org/documentation
It has a lot of information which I am sure will be enough for your project.
All tutorials are easily found using google, here is one of them: http://www.journaldev.com/5516/primefaces-tutorial-with-example-projects
This question already has answers here:
Embedding Java Applet into .html file
(2 answers)
Closed 6 years ago.
How can i embed a java applet in blogger. I am writing a blog on blog spot.com and I want to attach a java applet in that. Is it possible to do so? if yes, then how?
I tried to write this code in blog's html tab
<applet code="calculator.class" height="500" width="500"></applet>
but it doesn't work...
You don't.
Probably nobody told you so far, but applets are "dead technology". The only reason to do anything with Applets in 2016 is because you are working in some company that still uses them for some of their internal stuff. Then, and only then you should be spending your time on learning/programming applets. But in any other case, you would be wasting your time.
You see, browser like chrome have stopped supporting Java/applets quite some months ago.
Nobody does reasonable front work using applets any more. In other words: look into JavaScript or any of the huge frameworks around that. And figure how to use something like that instead of applets.
Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 10 years ago.
Improve this question
These days I got an offer related to a desktop application that I should create.
I'm a Java programmer. I had worked with Swing API about 4 years ago, so I can say that I have some experience with it. I also had worked with Flex 4 about one year ago, but I think it is not a good option for what I need. In my opinion it is not stable enough (present some strange behavior) and I think it is no longer maintained for Linux platform. - (if you think I'm wrong here, tell me).
So, I search for a good Desktop UI API that I should use with Java.
What are the actual desktop UI "trends", taking in account that questions on that issue are relatively old on SO?
N.B. When it comes to talk about platform independence and SWT, I think there are some issues. That's why I would not opt for it.
I would personally use JavaFX for any new UI development work in Java - it's now a 100% Java API and Oracle appear to be pushing it quite strongly:
JavaFX has become more tightly integrated with Java SE, and will soon become a standard component of the platform. Starting with JavaFX 2.0.2 / Java SE 7u2, the JavaFX SDK has become part of the Java SE 7 JDK, avoiding a separate download for developers. The next step in this integration is to include the JavaFX runtime libraries as part of the JRE, which will be achieved through the Java SE 7u6 / JavaFX 2.2 releases in summer 2012. This will ensure widespread adoption of JavaFX on Java-enabled computers, while leveraging synchronized updates and security fixes.
Having used it myself, in my opinion it's also far nicer than Swing in its API (more like SWT in that respect), looks far nicer by default, and far more flexible in what it allows you to do.
This question already has answers here:
What is Java's answer to WPF? [closed]
(3 answers)
Closed 4 years ago.
Is there an Java equivalent to the WPF platform?
No, but there is JavaFX which can be compared to Flash/Flex & SilverLight
The most likely answer is Soyatec's eFace. It supports several key features of WPF. It uses XAML and databinding, so you can apply MVVM and test your ViewModel. Also it supports templating.
Also, this is used in Eclipse e4.
JavaFX is SUN's trial to compete with WPF.
It can be used in both Applets and Desktop applications
You can see this comparison
Please take a look at Qt Jambi. It uses the Qt framework:
http://qt-jambi.org/
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 2 years ago.
Improve this question
I just saw a comment of suggesting J#, and it made me wonder... is there a real, beneficial use of J# over Java? So, my feeling is that the only reason you would even consider using J# is that management has decreed that the company should jump on the Java bandwagon... and the .NET bandwagon. If you use J#, you are effectively losing the biggest benefit of picking Java... rich cross platform support. Sure there is Mono, but it's not as richly supported or as full featured right? I remember hearing Forms are not fully (perhaps at all) supported.
I'm not trying to bash .NET here, I'm just saying, if you are going to go the Microsoft route, why not just use C#? If you are going to go the Java route, why would J# enter the picture?
I'm hoping to find some real world cases here, so please especially respond if you've ACTUALLY used J# in a REAL project, and why.
J# is no longer included in VS2008. Unless you already have J# code, you should probably stay away.
From j# product page:
Since customers have told us that the
existing J# feature set largely meets
their needs and usage of J# is
declining, Microsoft is retiring the
Visual J# product and Java Language
Conversion Assistant tool to better
allocate resources for other customer
requirements. The J# language and JLCA
tool will not be available in future
versions of Visual Studio. To preserve
existing customer investments in J#,
Microsoft will continue to support the
J# and JLCA technology that shipped
with Visual Studio 2005 through to
2015 as per our product life-cycle
strategy. For more information, see
Expanded Microsoft Support Lifecycle
Policy for Business & Development
Products.
The whole purpose of J# is to ease the transition of Java developers to the .NET environment which didn't work so well (I guessing here) so Microsoft dropped J# from Visual Studio 2008.
For your question, "Is there a real benefit of using J#?"..
in a nutshell... No..
Instead of J#, I would rather prefer IKVM (http://www.ikvm.net/) to convert my JARs to .NET assemblies as well as access Java APIs in C#.
One of the killers I've found with J# in the past is that there is no built in support for referencing web services. That alone has been enough to deter me from it ever since.
C# syntax is so close to Java (and better in some ways) that you might as well learn C# instead of J#. And since C# is more widely used, you can easily find Java --> C# tutorials on google or check out http://www.asp.net/learn and watch some videos.
I don't think it's a matter of which language is better. In the .NET world there are some inconsistencies between the libraries different languages provide. There are certain functionality that is available in VB.NET that you might like to use from C# but can't. I remember I had to use J# to use some ZIP libraries that were not available in any other language in .NET.
I have used J# as an easy interim step to port a java library into C#. It made for a good way to port code I don't plan to maintain from Java to .Net. However, all new development is being done in C#.
Strongly agree that syntactically C# beats Java hands down, so there is really no reason to lament the demise of j#. Now trying to get c# compiling to Java bytecode might be an interesting move as Sun's hotspot jvm is great software.
Or, for a bit of fun with what might well become the next generation of Java, how about Scala on the CLR...