RE: [xml-dev] Xlink Isn't Dead

["Len Bullard" <cbullard@hiwaay.net>]

Possibly so but the more one desires the more one is back to a full-up
programming language.  As I posted some posts back, that is where these
discussions lead and always have as long as I can remember on the web and
before it.

Scope Creep:  the ultimate enemy of interoperability because better is not
the enemy of good, it is the enemy of more.

So again, 

1) Linking is an old concept in terms of information systems even before
there were such things as computers.  Bibliographic citation is the common 
pre-computer science example.

2) As soon as the topic of linking comes up, we tend to mean slightly
different things by that, want to do different things with it, and have
different means to get that done.  Are link types the answer?  The web
pioneers didn't accept that.  Should we now?  If so, drag out a copy of ISO
10744 and learn from the last set of losers.  I'm not against revolution;
I'm against broken needles, cracked speakers and noisy amplifiers.

That makes a common linking standard, so far, elusive.  HyTime did as much
with it as I believe can be done and historically, it was too much.

len

-----Original Message-----
From: Peter Hunsberger [mailto:peter.hunsberger@gmail.com] 

On 9/26/06, Robert Koberg <rob@koberg.com> wrote:
> Peter Hunsberger wrote:
>
> > Although Microsoft may have got these two aspects more-or-less correct
> > they unfortunately did so with an implementation that gives you poor
> > reusability.  It's been a while since I attempted to use their
> > implementation but as I recall event mapping is cumbersome and there
> > is very little capability to exploit any kind of polymorphism.  In
> > particular, one should be able to define parameters (dynamic and
> > static) that are passed with the event notification to the handler, a
> > feature that is completely missing in the MS implementation.
> >
>
> FWIW, the dojo toolkit (ajax/javascript) has made a way to publish and
> subscribe to an object's events. For example you have some link/button
> object/widget where you define an onClick method:
> ...
> onClick: function() {
>    dojo.event.topic.publish(this.widgetId+"/onBeforeClick", {some:
> "set", of: properties});
>
>    //handle onClick
>
>    dojo.event.topic.publish(this.widgetId+"/onAfterClick", this);
> }
> ...
>
> then in some other code you can subscribe by referencing the identifier
> and giving it a handler function, like:
>
> dojo.event.topic.subscribe("metadata_page/onBeforeClick", setupMetadata);

We use Dojo.  The model is somewhat different; you're back to
programmatic attaching the events to the objects based on DOM
traversal (even if Dojo helps hide some of those details).  The MS
model Len was referring to is done by attaching the event handlers at
the CSS level.  There's really nothing else out there like it, but as
I said, the implementation leaves a lot to be desired.

-- 
Peter Hunsberger

_______________________________________________________________________

XML-DEV is a publicly archived, unmoderated list hosted by OASIS
to support XML implementation and development. To minimize
spam in the archives, you must subscribe before posting.

[Un]Subscribe/change address: http://www.oasis-open.org/mlmanage/
Or unsubscribe: xml-dev-unsubscribe@lists.xml.org
subscribe: xml-dev-subscribe@lists.xml.org
List archive: http://lists.xml.org/archives/xml-dev/
List Guidelines: http://www.oasis-open.org/maillists/guidelines.php