Johan Sundström wrote:
> [snip]
>
> Breaking Exhibit into smaller pieces doesn't necessarily break with
> being able to cater the past default piecework of having three
> components you drop somewhere; we could probably fairly easy retain
> that functionality and adopt those three DOM nodes if they exist,
> prepopulating them with whichever widgets they hold today, if a
> forthcoming freer-form layouting model emerges. My gut feeling says it
> might be a good idea.
>
> Or at least allowing for a similarly small deployment threshold with
> the new style deployment format.
>
I totally agree. And the challenge is to support smooth transition from
simple beginnings to ultimate sophistications.
> +1. Especially if we open an opt-out mode by query variable, similar
> to ?bundle=false and friends, for environments where minimum namespace
> clobbering is of the essence. (After all, getting your own is a mere
> ${myexhibit}.getDatabase() call away -- but I agree that its being
> available as "database" fits the javascript-in-browsers model very
> well.)
>
Good point about minimum namespace clobbering. I have a feeling that
little client-side code has a global variable called "database" right
now, but then I haven't built many 3-tier web apps.
>> Initially, you would need to include exhibit-api.js to get "database".
>> But after a while, perhaps your browser will come built-in with a native
>> implementation of "database". Now if "database" is built in, then it can
>> load data from other domains, too, and we won't need the JSONP hack.
>>
>
> Similarly, once Douglas Crockford's JSONRequest (RFC 4627,
> http://rfc.roxen.com/4627) gets widely deployed / promoted to internet
> standard, we will also overcome the JSONP hack. (I'd guess that will
> happens sooner, but hopefully that we'd get browser native "database"
> eventually too.)
>
How do you see RFC 4627 helping us out? I was referring to the callback
trick that Google Data API uses so that it can pass data cross-domain.
>> Once the database is broken off, it's more natural to break the UI off
>> into small pieces. It'd be nice to write small blobs of html code as
>> follows and place them _anywhere_ on the page:
>>
>
> +1. I vigorously like this. :-)
>
Awesome. Should we carry on some design discussion on [EMAIL PROTECTED] or ... ?
I guess we should update the release site of Exhibit at some point and
then freeze it while these major changes are being worked on.
David
_______________________________________________
General mailing list
[email protected]
http://simile.mit.edu/mailman/listinfo/general
