Re: Web Widgets, Where Art Thou?

2013-07-29 Thread Marcos Caceres
Hi Daniel, On Monday, July 29, 2013 at 8:22 PM, Daniel Buchner wrote: > FWIW, I ran a dev poll last week: ~95% of respondents What was the sample size? Who were the developers? Where was the poll run? > preferred a simple, separate HTML document specifically for their widget and > use all th

Re: Overlap between StreamReader and FileReader

2013-07-29 Thread Jonas Sicking
On Jul 29, 2013 7:53 PM, "Takeshi Yoshino" wrote: > > On Tue, Jul 30, 2013 at 5:16 AM, Jonas Sicking wrote: >> >> Couldn't we simply let the Stream class have a content type, which > > > That's what I meant. In Feras's proposal Stream has type attribute. I copied it to my draft. read(As)Text woul

Re: Overlap between StreamReader and FileReader

2013-07-29 Thread Jonas Sicking
On Mon, Jul 29, 2013 at 5:37 PM, Anne van Kesteren wrote: > On Mon, Jul 29, 2013 at 4:13 PM, Jonas Sicking wrote: >> On Mon, Jul 29, 2013 at 3:20 PM, Anne van Kesteren wrote: >>> How about we use what XMLHttpRequest and WebSocket have? >>> >>> Stream.prototype.readType takes an enumerated string

Re: Overlap between StreamReader and FileReader

2013-07-29 Thread Anne van Kesteren
On Mon, Jul 29, 2013 at 4:13 PM, Jonas Sicking wrote: > On Mon, Jul 29, 2013 at 3:20 PM, Anne van Kesteren wrote: >> How about we use what XMLHttpRequest and WebSocket have? >> >> Stream.prototype.readType takes an enumerated string value which is >> "arraybuffer" (default) or "text". >> >> Strea

Re: Overlap between StreamReader and FileReader

2013-07-29 Thread Jonas Sicking
On Mon, Jul 29, 2013 at 3:20 PM, Anne van Kesteren wrote: > On Mon, Jul 29, 2013 at 1:16 PM, Jonas Sicking wrote: >> Couldn't we simply let the Stream class have a content type, which >> could contain an encoding. Then when stream.readText is called, if >> there's an explicit encoding, it would u

Re: Overlap between StreamReader and FileReader

2013-07-29 Thread Anne van Kesteren
On Mon, Jul 29, 2013 at 1:16 PM, Jonas Sicking wrote: > Couldn't we simply let the Stream class have a content type, which > could contain an encoding. Then when stream.readText is called, if > there's an explicit encoding, it would use that encoding when > converting to text. How about we use wh

Re: [widgetsapi] reference to WebIDL

2013-07-29 Thread Arthur Barstow
On 7/29/13 4:15 PM, ext Yves Lafon wrote: Hi, In the PR [1], the text referencing WebIDL is not using one of the three conformance clauses defined in WebIDL [2]. Could "This specification uses [WebIDL] to specify application programming interfaces." be clarified using one of the proposed word

[widgetsapi] reference to WebIDL

2013-07-29 Thread Yves Lafon
Hi, In the PR [1], the text referencing WebIDL is not using one of the three conformance clauses defined in WebIDL [2]. Could "This specification uses [WebIDL] to specify application programming interfaces." be clarified using one of the proposed wordings from WebIDL? (likely 'Conforming IDL

Re: Overlap between StreamReader and FileReader

2013-07-29 Thread Jonas Sicking
Couldn't we simply let the Stream class have a content type, which could contain an encoding. Then when stream.readText is called, if there's an explicit encoding, it would use that encoding when converting to text. / Jonas On Mon, Jul 29, 2013 at 6:38 AM, Takeshi Yoshino wrote: > On Thu, Jul 18

Re: Web Widgets, Where Art Thou?

2013-07-29 Thread Daniel Buchner
FWIW, I ran a dev poll last week: ~95% of respondents preferred a simple, separate HTML document specifically for their widget and use all the existing DOM APIs and modules from across the web for things like storage, localization, etc. In fact, of the only 2 respondents opposed to the idea, one fu