Comments on: JDA Emulator: Spring for JavaScript

By: Peter Svensson

Peter Svensson — Fri, 02 Mar 2007 11:17:46 +0000

I haven’t coded in prolog ever, so I can’t verify what you say. But it’s good that the JDA folks have rediscovered a good thing, then.
psvensson@gmail.com

By: Jeff

Jeff — Thu, 01 Mar 2007 19:38:39 +0000

This is all somewhat humorous. Very soon now someone will notice that inversion of control + dependency injection + autowiring == limited logic programming. Bit by bit the ideas from prolog and other logic programming languages are sneaking into the mainstream.

Infotron == predicate. Input and output terminals == predicate arguments.

By: Peter Svensson

Peter Svensson — Mon, 29 Jan 2007 13:17:56 +0000

Argh! Sorry :) Actually, the best details are in the pdf’s at the site, but for a quick run-up of what DJA does, I’ve posted some clarification on my blog;

http://unclescript.blogspot.com/

But it really does do very little. What little it does makes pages incredibly easy to read, though. It is a standard for wiring together ‘infotrons’. Yes, me neither. Anyway, an infotron is a DOM element with some extra attributes. When you ‘boot’ the JDA “kernel”, it goes through the page and registers all infotrons. An infotron can be defined in a separate .js-file, but it’s more efficient to bunch all definitions together in just one file (obviously). It’s all the same to JDA.

Each infotron declares a number of input and output ‘terminals’. These are then used inside the infotrons when parsing a message (or receiving a startup message from JDA), and when posting something to one of its output terminals.

It sounds horrid and abtuse, but I really, really like it. See the HTML source on some of my examples on the site (I’ve two at the moment and is working on a more complex third);

http://www.mashupstation.com/Wikka/wikka.php?wakka=JdaEmulator

Mail me directly if you have more questions, or comment the blog (or the page)

Cheers,
PS

By: Ivan

Ivan — Mon, 29 Jan 2007 05:03:38 +0000

Instead of an application creating dependencies and managing object lifecycles, a framework like Spring can manage these for you. The poster can probably add what specifically it brings to the table, but I would expect dependency injection at the bare minimum. Basically, theoretically a lot less code to get the job done.

I’m familiar with stuff like this for middleware, but I’m not sure how it will adjust to gui stuff…

More details! :)

By: nm

nm — Sun, 28 Jan 2007 18:46:15 +0000

copy that on language use, i guess part of the reason java has so many frameworks is the wonderful use of words.

By: Mike

Mike — Sat, 27 Jan 2007 22:59:45 +0000

What Matt (and me) don’t understand is basically everything. It doesn’t say what this does anywhere. It says things like:

An attempt to promote evolutionary design and to bring about seamless interoperability to the Web

Well hey, I’ll tell my boss, he’ll be thrilled. But as a developer I don’t have the faintest idea what it means. Here’s some other examples of this type of language:

enable real-time communities
visualize impactful applications
target real-time convergence

Doesn’t make sense to a lot of people, sorry…

By: Peter Svensson

Peter Svensson — Fri, 26 Jan 2007 09:12:26 +0000

Matt, what is it that you don’t understand? Please mail me if you want some assistance to start wiring things with JDA.

Cheers,
PS

By: hoapham

hoapham — Fri, 26 Jan 2007 07:48:48 +0000

test

By: Matt

Matt — Thu, 25 Jan 2007 21:39:34 +0000

In english please? Can anyone translate in plain terms? Thanks kindly!