JDNC and Rich Internet Applications

It seems impossible to find out whether JDNC (JDesktop Network Components) are really designed to contribute to the development of RIA or not. When used in a web-page, JNDC are essentially applets but they can be configured with the same XML configuration files as their desktop equivalents. Futhermore the components, because they are 'network' aware, can fetch their data from the originating web-site. Thus they have precisely the characteristics to make them a valuable component on a web-page.

But the documentation seems only too keen to point out the problems with using them on web-pages (variable Java support, longer load times, the need to reload after a page refresh). JDNC demos are all WebStart based and nobody is saying anything about scripting JDNC or allowing them to interact with other page content, be it HTML content accessible through the DOM or a Flash component. While it might be possible to drive JDNC components with Javascript (just because it can already speak to applets) the real question is whether they are designed to be scripted. For example can Javascript be used to scroll a JDNC 'table' component to a selected row or, more revealingly, can a row selection in a JDNC 'table' component trigger some Javascript?

With JDNC and JDIC Sun is obviously making a renewed effort on the desktop. But from the 'vision thing' point of view the most significant thing would seem to be Java WebStart. This brings many, if not virtually all, of the deployment advantages of pure web applications to the desktop. Whereas initiatives like JDNC and JDIC are [just] new tools for building conventional desktop applications in Java, albeit far more productively. But web deployable, desktop applications are not RIA. Where is the 'vision thing' for Java and RIA? It would have to be something that acknowledges the existence and importance of the web-browser as a primary tool of user interaction. With the web-browser comes a set of expectations related to choices and technology and the ability to combine them. If JDNC is part of a Java/RIA vision then it has to acknowledge that Java-based components, no matter how functional and how rich they are, are just that; components to be mixed and matched with any other Internet capable component.

[UPDATE] a reply to this post from Mark Davidson has prompted me to try an articulate things better in another post.

Comments

Post a Comment

Popular posts from this blog

A Review of hReview

microformats may well represent a path from where we are today to the [lowercase] semantic web. If so, one of the first waypoints along such a path could be the emergence of aggregators capable of taking advantage of suitably marked-up content. Applying a 'microformat' approach to tagging, Technorati introduced the rel="tag" approach to marking-up tags. Technorati also supply the corresponding aggregation service, e.g. see posts tagged with microformat . Given this minimalist approach to tagging, the hReview specification comes as something of a surprise. It seems to represent a format developed independently of the environment in which it is most likely to be used. The rel="tag" approach makes a major, simplifying assumption. This is that the tag refers 'to a major portion of the current page (i.e. a blog post)' . I am assuming that it could apply equally to a blog entry in an RSS/Atom feed. Thus an aggregator can associate a tag with two p...
Read more

SmartLink

Image
In a previous post I tried to describe how I thought technologies like SmartTags and AutoLink ought to behave. With greasemonkey in Firefox I've been able to build a proof-of-concept demonstrator. For the moment I'm calling it Smart Tag/Auto Link. SmartLink is based upon the idea that content authors should mark-up content that can be 'smart-linked', using standard XHTML constructs. This has two advantages: it effectively provides an 'opt-in' mechanism for content providers it doesn't require 'magic' to identify what can be smart-linked and thus provides a much more extensible approach. of course there is one fairly major disadvantage: there isn't any suitably marked-up content out there, with the exception of some test posts I've put together for the purpose. Getting Started If you want to know a bit more about SmartLink then click here . Alternatively if you want to see how SmartLink behaves and you're using Firefox t...
Read more

Google I/O 2013

With Google I/O approaching it is time to start speculating... Last year the keynotes at Google I/O were very different in tone; the one for Android and the one for Chrome OS. It will be interesting to see if there is any big change this year, now that Sundar Pichai will - indirectly - have a role in both. Google's commitment to the web and the evolution of Chrome has taken them to an extraordinary place.  Soon it will be possible to develop apps using standard web technologies and deploy them to a wide range of environments; desktops running OS X, Linus or Windows as well as Chrome OS. There seems to be a genuine desire to get Chrome apps to play nice in their host environments, not just within the browser. For example the launcher that was part of Chrome OS now has a variant in some desktop environments. The Chromebook Pixel has a touch screen, so developing Chrome apps for a touch interface is clearly on the agenda. So isn't it about time for Chrome apps on Android...
Read more