Re: [whatwg] Appcache feedback (various threads)

2011-02-01 Thread Patrick Mueller
On 2/1/11 11:47 AM, Adam de Boor wrote: On Mon, Jan 31, 2011 at 3:28 PM, Ian Hicksoni...@hixie.ch wrote: On Fri, 13 Aug 2010, Patrick Mueller wrote: On 8/12/10 6:29 PM, Ian Hickson wrote: On Wed, 19 May 2010, Patrick Mueller wrote: I've been playing with application cache for a while now

Re: [whatwg] Appcache feedback (various threads)

2010-08-13 Thread Patrick Mueller
. -- Patrick Mueller - http://muellerware.org

Re: [whatwg] Appcache feedback (various threads)

2010-08-13 Thread Patrick Mueller
On 8/12/10 6:29 PM, Ian Hickson wrote: On Wed, 19 May 2010, Patrick Mueller wrote: I've been playing with application cache for a while now, and found the diagnostic information available to be sorely lacking. For example, to diagnose user-land errors that occur when using appcache

[whatwg] Need more diagnostic information for ApplicationCache events

2010-05-19 Thread Patrick Mueller
might be the best thing to do for all three of the mechanisms I suggested - extend the events used with a new attribute of type ApplicationCacheStatus, and add a new attribute to ApplicationCache of type ApplicationCacheStatus, etc. -- Patrick Mueller - http://muellerware.org

[whatwg] ProgressEvent for appcache - loadedItems vs loaded

2010-05-18 Thread Patrick Mueller
and totalItems. These attributes might be better suited to be used rather than the total and loaded attributes. Same for step 18, which indicates a final ProgressEvent should be sent at the completion of the cache download process. -- Patrick Mueller - http://muellerware.org

Re: [whatwg] Global Script proposal

2009-08-24 Thread Patrick Mueller
Patrick Mueller wrote: Michael Nordman wrote: I'm confused about the manual loading of the script into the context? The original proposal called for providing a script url when creating/connecting to an instance of a global-script... in which case each client page expresses something more

Re: [whatwg] Global Script proposal

2009-08-21 Thread Patrick Mueller
Patrick Mueller wrote: Time to work on some examples. This would relatively easy to prototype in something like Rhino (or my nitro_pie python wrapper for JavaScriptCore), at least API wise, so we could see what the user-land code would look like, and see it run. I developed a simulator

Re: [whatwg] Global Script proposal.

2009-08-21 Thread Patrick Mueller
call ClassLoader hell. -- Patrick Mueller - http://muellerware.org

Re: [whatwg] Global Script proposal

2009-08-21 Thread Patrick Mueller
(); context.onload = function () {...} context.onerror = function () {...} context.load('foo.js'); -- Patrick Mueller - http://muellerware.org

Re: [whatwg] Global Script proposal.

2009-08-19 Thread Patrick Mueller
available? In the current scenario with a no-arg constructor, what happens when I invoke it again? If it should return the same object, then don't use a constructor, use a plain old function - SharedScope.getCurrent(). -- Patrick Mueller - http://muellerware.org

Re: [whatwg] Global Script proposal.

2009-08-19 Thread Patrick Mueller
more of an opt-out. And I don't have a use case for I don't want to share, nor could I claim that even if they didn't want to, it would be unsafe if they did anyway (ie, it might be safe even if they didn't want to share). Just thinking aloud. -- Patrick Mueller - http://muellerware.org

Re: [whatwg] Global Script proposal.

2009-08-19 Thread Patrick Mueller
? The load() method is very similar to the worker loadScript() (or whatever) function. Perhaps we should combine them into one API, that allows sync or async in a worker, but only allows async in a GlobalScript. Or at least advises against use of sync. -- Patrick Mueller - http

Re: [whatwg] Global Script proposal.

2009-08-19 Thread Patrick Mueller
Michael Nordman wrote: On Wed, Aug 19, 2009 at 1:34 PM, Patrick Mueller pmue...@muellerware.orgwrote: Can I create additional GlobalScript's from within an existing GlobalScript? That's a good question... (just having fun... oh the tangled web we weave;) I'm not sure any has thought thru

Re: [whatwg] Installed Apps

2009-07-28 Thread Patrick Mueller
need a lot of head shaping around asynchronous message sending? Futher question would be whether there are two issues: dealing with asynchronous messages, and direct DOM API. If we could get over the hurdle of the async, do we still need the direct DOM API? -- Patrick Mueller - http

Re: [whatwg] Audio synthesis

2009-07-21 Thread Patrick Mueller
such a clip seamlessly. It makes me wonder what the use of having the seamful looping actually is, besides of course annoying people. :-) -- Patrick Mueller

Re: [whatwg] Audio synthesis

2009-07-21 Thread Patrick Mueller
Robert O'Callahan wrote: On Wed, Jul 22, 2009 at 1:36 AM, Patrick Mueller pmue...@muellerware.orgwrote: I've just started playing a bit with audio. One thing I noticed with both FF 3.5 and WebKit nightlies is that usage of the loop attribute set to true does not provide seamless looping. ie

Re: [whatwg] Proposal: JavaScript stack traces

2009-06-12 Thread Patrick Mueller
stuff that's going on, and a Google Group that will be set up to discuss. I'll post back to the es-discuss group as I hear more. -- Patrick Mueller

[whatwg] native ordered dictionary data type in web storage draft

2009-04-14 Thread Patrick Mueller
how someone might make use of the ordered-ness in a plain old for/in loop, for instance. It would also be impossible, in the JavaScript in use today, AFAIK, to emulate this with user-land JavaScript. -- Patrick Mueller

Re: [whatwg] native ordered dictionary data type in web storage draft

2009-04-14 Thread Patrick Mueller
Aryeh Gregor wrote: On Tue, Apr 14, 2009 at 1:54 PM, Patrick Mueller pmue...@muellerware.org wrote: Still doesn't seem like it makes sense to go ahead and build dependencies on this (unfortunate, IMO) behavior. Isn't HTML5 all about mandating and building dependencies on unfortunate

Re: [whatwg] native ordered dictionary data type in web storage draft

2009-04-14 Thread Patrick Mueller
Maciej Stachowiak wrote: On Apr 14, 2009, at 1:03 PM, Patrick Mueller wrote: This seems slightly different because it's making a dependency on (unspec'd) JavaScript behavior. Though I'd guess there are other examples. FWIW I believe the next version of the ECMAScript spec will specify