W3C home > Mailing lists > Public > www-style@w3.org > July 2007

Re: <table presentation="pie"> (was: Re: <table chart="pie">)

From: Mike Bremford <mike-css@bfo.co.uk>
Date: Tue, 31 Jul 2007 16:08:07 +0100
Message-Id: <BA373C94-8489-43DD-8F2F-5128105CFF2A@bfo.co.uk>
To: www-style <www-style@w3.org>

Dmitry, if you want to draft a specification then please go right ahead.

Areas I expect you'll need to cover are 3D rotation of graphs,  
extensions of slices from pies, position of text labels or markers on  
slices of pies, position, shape, size and style of call-outs to those  
labels... and PieGraphs are the easy ones. You've got bars, scatter  
plots, line graphs, box-whisker charts, combinations of all of the  
above against regular axes, logarithmic axes, axes with gaps, axes  
displaying text or dates or floating point or fractions or every  
third day of the month.

You'll need to clearly define rules for what happens if you mix your  
new "graph" values with the rest of CSS, which focuses on the box model:

<table style="display:piegraph">
   <tr style="display:block">What happens here?</tr>
   <div style="float:left">Or here?</div>
   <ns:foo style="position:absolute">Or here?</ns:foo>
   <span style="display:piegraph">Or even here?</span>

Then, of course, you'll need to persuade developers to set aside  
their time and resources to actually *implement* your idea. This  
means a clear use-case that shows your design meets a requirement  
that users, in their teeming millions, are clamouring for, and that  
it's the best conceivable approach - which means it's clearly  
defined, limited in scope, doesn't clash with or complicate existing  
codebases or specifications and can't be done using a simpler,  
cleaner approach.

Have fun!

Cheers... Mike

On 31 Jul 2007, at 14:08, Dmitry Turin wrote:

> MB> this should be done ... not overriding tables
> You think, this is non-table ? You are wrong.
> This is __other presentation__ of table.
>                 QUANTITY OF ROWS
>                   1-3      4-...
> numerical          +        +
> chart              +        -
>   "Plus"-es mean,
> that three rows can be displayed both as numbers and as chart.
> "Minus" means,
> that it's impossible to display four (and above) rows,
> because we can't draw 4D-space.
>   As much as in MS Excel, 1-3 rows can be dispayed as chart,
> if they contain only numbers (instead of words or embeded html- 
> elements).
>   I think to change @chart to @presentation with "numeric" as  
> default value.
> <table presentation="numeric / pie / etc">
> PNA> Why not "simply" create an XHTML type of <chart> that has a
> PNA> <chart_datapoint> member or something like that?
> MB> bet way to handle this is to use XHTML
> MB>     <body>
> MB>      <chartns:piechart>
> MB>       <chartns:data key="this" value="123"/>
> MB>       <chartns:data key="that" value="456"/>
> MB>      </chartns:piechart>
> MB>     <body>
> (1) Recall about razor of Occam: don't enter entity without needs.
> (2) Because your way is __more__ (comparison characteristic) difficult
> for applied specialists (biologists, technologists, etc). For  
> simple man.
> MB> A table is for tables, not charts.
> PNA> it was not intended to be
> Orthodox-ness. No more.
> Dmitry Turin
> HTML6     (6.3.0)  http://html6.by.ru
> SQL4      (4.1.3)  http://sql40.chat.ru
> Unicode2  (2.0.1)  http://unicode2.chat.ru
> Computer2 (2.0.3)  http://computer20.chat.ru
Received on Tuesday, 31 July 2007 15:08:32 UTC

This archive was generated by hypermail 2.3.1 : Monday, 2 May 2016 14:27:29 UTC