You are here: Home › Featured › JavaFX & Multitouch

JavaFX & Multitouch

After JavaOne I had a wonderful time Canada. On my trip home I couldn’t resist to touch the keyboard again 🙂 Another passenger and I had a discussion on Java and JavaFX. Finally, I gave him a short introduction to JavaFX. One of the demos we developed is the following small and simple demo application:

The sample code covers multitouch, animations and css. The code consists of just one .java file and one .cssfile.

Requirements

JDK >= 1.7.u25
Netbeans >= 7.4 (may also work with older versions)

Download

Download the project here: MultiTouch01

Fedback

If you have further questions or if you found a bug feel free to contact me!

Stay tuned and follow me on Twitter

6 Responses to "JavaFX & Multitouch"

Jim says:

November 21, 2013 at 14:34

Very nice, but I have a question? Why make a program that depends on a particular IDE? By doing this you exclude a lot of people from using your code. Maybe you don´t care and that is fair enough. The beauty of Java is that it only needs a JRE to run. Why lose that advantage?
1. miho says:
  
  November 21, 2013 at 14:50
  
  Usually I use Gradle which is compatible with most IDEs (see VWorkflows). But since this was a spontaneous tutorial in the plane(!) I did indeed not care about IDE compatibility. If you need help converting it to a Gradle project then just ask :)https://mihosoft.eu/wp-admin/post.php?post=940&action=edit#comments-form
  1. Jim says:
    
    November 21, 2013 at 15:49
    
    He he, I don’t use Gradle either. This is my point again. I don’t mean to be out of order though mate. As I say, you are free to do things as you want but I do think these extra layers stifle adoption. All the best.
    1. miho says:
      
      November 21, 2013 at 16:35
      
      He he, I don’t use Gradle either.
      
      What do you use then? Hopefully not just javac on the command line. This will not work for non trivial projects that incorporate dependencies & resources etc.
      
      As I say, you are free to do things as you want…
      
      Sure, I know that 😉
      
      …I do think these extra layers stifle adoption.
      
      True for IDE specific projects. Wrong for Gradle.
Jim says:

November 21, 2013 at 16:46

I use Eclipse, so not command line! But note that I am not saying you should make projects for me in Eclipse. I mean that for adoptions sake, you would be better just giving your code that can be run in Eclipse, Netbeans or whatever. Maybe you would also need to supply any jars that your code might depend on. Does you code absolutely need Java/JavaFX to run? YES Does you code absolutely need Gradle to run? NO

…I do think these extra layers stifle adoption.

… True for IDE specific projects. Wrong for Gradle.

I disagree! Many people will come to your code and think ‘ah, I need gradle to run this, should I install it and learn how to use it? errr, maybe later’. Hence adoption stifled.

The demo looks very cool, but IMHO you are limiting its reach.

Peace
1. miho says:
  
  November 21, 2013 at 17:07
  
  I disagree! Many people will come to your code and think ‘ah, I need gradle to run this, should I install it and learn how to use it? errr, maybe later’. Hence adoption stifled.
  
  Wrong! You DON’T need to install Gradle. That’s the point! It’s just another Jar file in your project. It only depends on the JDK.
  
  When I teach students I discover that explaining them how to add Jar files as dependencies in their favourite IDE takes much more time than just telling them to either type ./gradlew run on the command line or to just open the Gradle project in e.g., NetBeans. Not to mention multi-project builds!
  
  Please read a bit more about Gradle. Gradle is all about building projects WITHOUT manually downloading dependencies or build tools. Everything that you need to get startet is part of your project. You can auto-download via maven or just add plain Jars to the project. It runs flawless on Linux, OS X and Windows. I use it in NetBeans, IntelliJ and Eclipse.
  
  I’m closing the comments now since we are totally off-topic. Maybe I should tell more about Gradle in an extra post.

Comments are closed.