- From: Ian Hickson <ian@hixie.ch>
- Date: Wed, 10 Oct 2007 04:35:49 +0000 (UTC)
On Thu, 13 Sep 2007, Dimitri Glazkov wrote:
>
> 1. Instead of using "application" attribute, move the declaration into a
> separate head element, like link rel="application". This provides the
> ability to reference multiple applications and also name each reference:
>
> <link rel="application" type="text/html" id="dojo"
> href="http://dojotoolkit.org/files/manifests/dojo-0-9-0.html">
I'm not sure exactly how that would help really.
> (I am implicitly suggesting that the manifest is in XOXO format, but
> that's another topic for another day)
The spec ended up using a simpler format, for what it's worth.
> 3. For each declared application, a scripting context exists. The
> context is a JS object and can be accessed by querying
> document.application[id], where id is the value of the "id" attribute on
> the link element (a bit kludgy, better idea needed here). For instance:
>
> document.application.dojo.parser = function() { ... }
> alert(document.application.dojo.version);
That seems to conflate multiple features which we'll eventually have. I'm
not sure they need to be so closely related to each other.
> 4. The scripting context is persistent for the duration of the browser
> session. In other words, it retains scope and values of the context
> members across documents, being initialized when the application is
> first encountered during a browsing session and shutting down when the
> browser session is terminated. I realize how complex this is
> implementation-wise.
Probably too complex for now. :-)
--
Ian Hickson U+1047E )\._.,--....,'``. fL
http://ln.hixie.ch/ U+263A /, _.. \ _\ ;`._ ,.
Things that are impossible just take longer. `._.-(,_..'--(,_..'`-.;.'
Received on Tuesday, 9 October 2007 21:35:49 UTC