makelesno.blogg.se - november 2022

JavaOne 2012: JavaFX on Smart Embedded Devices.

JavaOne 2012: Building Mobile Apps with HTML5 and.

JavaOne 2012: Custom Static Code Analysis.

JavaOne 2012: Griffon, Up Close and Personal.

JavaOne 2012: JSR 353: Java API for JSON Processing.

JavaOne 2012: JavaFX Graphics Tips and Tricks.

JavaOne 2012: Diagnosing Your Application on the JVM.

JavaOne 2012: Up, Up, and Out: Scaling Software wi.

JavaOne 2012: Mastering Java Deployment.

JavaOne 2012: Getting Started with the NetBeans Pl.

JavaOne 2012: Observations and Impressions.

NetBeans 7.3 Beta is More Than Easel: Hints and FX.

Java/NetBeans: Overridable Method Call in Constructor.

It's probably not something I'll be able to use in the near future, but it was fun to see and think about the possibilities. Those points being stated, I still did enjoy the presentation and found it interesting. The abstract seemed a bit misleading as there was no mention of Tiggzi-specific solution in that abstract. The title of the session seemed a little misleading as there was next to no coverage of Java other than mention that Twitter uses Java and the first example uses Twitter. He said that if you use promo code " javaone12" at you can get the Pro Plan for a trial period. Katz recognized that we "don't want to buy stuff," but provided an overview of Tiggzi's pricing strategy (pricing based on number of deployed applications and all plans have all features). The answer was "no" and that Tiggzi supports XML or JSON over REST only. One of the audience members asked if Tiggzi supports SOAP. I'd say that the tool's interface itself is probably more complicated than the applications most developers would develop on it, but that could probably be said for Java IDEs as well. It seemed to have responsiveness similar to a decent desktop Java IDE. I was surprised at how fluid the behavior was for the most part. One of the nifty things he demonstrated was the reporting of the equivalent curl command for accessing the data via REST.Īll of Katz's demonstrations were implemented within the Google Chrome web browser. Katz moved onto another example that accessed data from the database rather than from Twitter's API. It was one of the more impressive real-time demonstrations I've seen. It really drove home how easy this cloud-based solution is to use and deploy. It was pretty impressive to be able to reload/ refresh the application as he worked on it on my laptop and on my Droid. Desktops could access and mobile devices could access. Katz made his example public and created a TinyUrl for it. He pointed out that because this example is based on JavaScript and jQuery, it can be used on any web browser.

He stated by working on an example application to connect to Twitter via their exposed REST interfaces. He explained that this is a cloud-based tool as we waited for it to load. Katz only had a single slide before going into demonstration mode.