Re: [whatwg] rename CanvasPixelArray

[Calogero Alex Baldacchino]

Anne van Kesteren ha scritto:
Wouldn't it make more sense to give this a more generic name, just 
like the object it is associated with? That way we can later reuse it 
for  elements and the like (if we want) without it having to look 
silly and poorly thought out like the rest of the platform. :-P (E.g. 
ImagePixelArray.)





Other elements would need a rendering context anyway, thus the same 
reasoning could be applied to CanvasRenderingContext2D, CanvasGradient 
and CanvasPattern. Perhaps the best way to generalize their name is to 
remove the "Canvas" part (or changing it into "Graphics" or the alike -- 
both PixelArray and ImagePixelArray could be fine). However, "canvas" 
might be enough generic, when thinking to a graphics context, to be 
referred to whatever object allowing custom rendering without any 
confusion or poor association (like saying that a  is the main 
element for custom/dynamic rendering and that other elements might use 
the Canvas framework to provide similar capabilities). Personally, I'm 
fine with both choices.


WBR, Alex


--
Caselle da 1GB, trasmetti allegati fino a 3GB e in piu' IMAP, POP3 e SMTP 
autenticato? GRATIS solo con Email.it http://www.email.it/f

Sponsor:
Con Danone Activia, puoi vincere cellulari Nokia e Macbook Air. Scopri come
Clicca qui: http://adv.email.it/cgi-bin/foclick.cgi?mid=8547&d=23-1

[whatwg] rename CanvasPixelArray

[Anne van Kesteren]

Wouldn't it make more sense to give this a more generic name, just like  
the object it is associated with? That way we can later reuse it for   
elements and the like (if we want) without it having to look silly and  
poorly thought out like the rest of the platform. :-P (E.g.  
ImagePixelArray.)



--
Anne van Kesteren

Re: [whatwg] Video and Audio schema for validators

[Anne van Kesteren]

On Fri, 23 Jan 2009 05:19:48 +0100, Chris Double  
 wrote:
On Fri, Jan 23, 2009 at 1:55 PM, Arne Claassen   
wrote:
In particular, I came across a couple of event handlers in examples  
that i

can't find defined anywhere in the specs, like ondataunavailable and
oncanshowcurrentframe


These are probably some of my examples that I wrote back when the spec
used to have those. I've not updated the examples on that page to
match the current spec.


Note that these will be part of the specification, Hixie just hasn't  
gotten around to adding the new event handler attributes yet as far as I  
can tell.



--
Anne van Kesteren

Re: [whatwg] HTML5 fo ecommerce

[Benjamin Hawkes-Lewis]

On 23/1/09 08:10, Mynthon wrote:

On my companys page there are no articles and sections. There are
products and product lists. Isnt it wrong to use


   
 product1
 some data
   
   
 product2
 some data
   
   
 product3
 some data
   


while it wil be misleading screen readers? For users without
disabilities there is no problem but for eg. blind peple? Calling
product list an article is... hmmm... wrong.


Why?

You're not marking the product list as an "article". That's just the 
name of the element. You're marking it up as "a section of a page that 
consists of a composition that forms an independent part of a document, 
page, or site. This could be a forum post, a magazine or newspaper 
article, a Web log entry, a user-submitted comment, or any other 
independent item of content."


http://www.whatwg.org/specs/web-apps/current-work/#dfnReturnLink-1

Similarly, when you mark something up as an "address", you're not 
marking any old snail mail address, but rather any sort of contact 
information (e.g. telephone, email) for the author of that part of the 
document:


http://www.whatwg.org/specs/web-apps/current-work/#the-address-element

Conclusion: The names of HTML elements are not a perfect guide to what 
they represent. If it is correct to say your product list is "a section 
of a page that consists of a composition that forms an independent part 
of a document, page, or site", then marking it up with an "article" 
element will not mislead conforming user agents, screen readers or 
otherwise.


However, whether it's the best element to use in your case is debatable. 
A case might be made for using OL, depending on what sort of product 
list this is. For example, if it's a search results page for 
"grabowski", I'd use an OL:




Search Results
Results 1-5 of 5 for grabowski.

3.99usd
This is description of product …





(Compare the OL elements in the search result pages of Google and 
Yahoo!, with which screen reader users are familiar.)


I'd also use an OL if it's a sorted list (e.g. sorted by price).

On the other hand, if the order is editorial, I'd probably just use an 
"article" with nested "article" elements or "section" elements.


HTML5 provides extension mechanisms that can be used to annotate HTML to 
make product data extractable. The microformats community is working on 
markup for product lists and products:


http://microformats.org/wiki/hlisting-proposal

http://microformats.org/wiki/hproduct

hListing is already in use on Kelkoo:

http://developer.yahoo.net/blog/archives/2008/03/kelkoo_goes_mic.html


Will be very cool for me and many other.


If you're proposing new features, you need to begin with the end-user 
problems you're trying to solve, not specific HTML element proposals:


http://wiki.whatwg.org/wiki/FAQ#Is_there_a_process_for_adding_new_features_to_the_spec.3F

It's not clear to me whether the problem you're hinting at is that the 
name "article" is insufficiently generic for what it represents or 
whether you're attempting to solve additional problems (data extraction? 
special navigation?).


Naming elements tends to be a case of choosing the least worst option, 
unfortunately.


--
Benjamin Hawkes-Lewis

[whatwg] HTML5 fo ecommerce

[Mynthon]

Hi everyone.

I have some questions about html. I really like new  tag
and its possibility to have its own  structure. Dont like mixing
 levels but thats BTW.

I have strange feeling that in next 5 years not only blogs will be
available on the web but also some e-commerce pages (online shop,
auctions). Also some new applications. Now i cant figure out how to
use html5 for those sites.

On my companys page there are no articles and sections. There are
products and product lists. Isnt it wrong to use


  
product1
some data
  
  
product2
some data
  
  
product3
some data
  


while it wil be misleading screen readers? For users without
disabilities there is no problem but for eg. blind peple? Calling
product list an article is... hmmm... wrong.

The same goes for pages with advertisements and announcements, e-mail
web frontends, forums, and every other page that is not blog or
newspage. If there are new tags for blogs (, ,
, ) are there plans for tags usable for other pages
(, , , , ,
,  etc.)

Something like:

  New book
  by Chris Grabowski
  old price: 5usd
  Now only: 3.99usd
  This is description of product ...


Will be very cool for me and many other.

If it is not in plans how to acheve it with html5. Thanx for any example code!