Re: A way around the default table?

YES!

I found a way around.

A temporary one, but do what we need when we do not want the default two columns styling.

To do that, I mix-matched CSS selectors by reading the uncompressed CSS files (it is indeed messy).

I could make a simple three column data table using this wiki markup


{| class="mw-datatable os-suggest-results filehistory"
|+VMs usage comparsion
|-
|Current
|Future
|-
|production:
* A
* B
|production:
* C
* D
temporary:
* Z
* Maybe E
|}


Yay!!


Renoir 
~

On 2013-08-14, at 5:18 AM, Dominique Hazael-Massieux <dom@w3.org> wrote:

> Le mercredi 14 août 2013 à 01:15 -0400, Doug Schepers a écrit :
>> This is one of those weird formatting issues that is a confluence of 2 
>> poor design decisions in the system:
>> 
>> 1) Semantic MediaWiki (I think) outputs topic lists as tables for 
>> formatting reasons (this is really the fault of CSS for not doing 
>> flowing columnar layout sooner)
>> 
>> 2) MediaWiki makes "layout tables" without proper headings where it 
>> should, and doesn't distinguish between layout tables and real tables in 
>> its output, meaning we either have to style tables
>> 
>> Neither of these things is really in our control.
>> 
>> We could simply make the category index manually (which defeats the 
>> purpose of using a CMS) or we can live with it until we migrate to 
>> another system.
> 
> FWIW, I think an alternative would be to create a new Result format for
> Semantic MediaWiki (as part of the Semantic Result Formats stuff [1]),
> and then replace our Category pages by a Semantic Media Wiki query (with
> another extension à la
> http://www.mediawiki.org/wiki/Extension:CategoryMagicWords )
> 
> Of course, it may or may not be practical to do so given existing
> priorities, available resources, etc.
> 
> 1. https://git.wikimedia.org/tree/mediawiki%2Fextensions%
> 2FSemanticResultFormats.git
> 
>> Of these 2 options, I favor the first... not least because we could also 
>> get rid of the hideous page names (also a terrible artifact of SMW)... 
>> so we could have "CSS Regions API" instead of "apis/css-regions".
>> 
>> This sort of auto-categorization should be a feature of the future CMS.
>> 
>> Regards-
>> -Doug
>> 
>> On 8/12/13 5:24 PM, Jonathan Garbee wrote:
>>> I'd like to know why this is using a table in the first place. It isn't
>>> tabular data and should be possible by using regular div elements which
>>> carry no real meaning. But, this is from the first-child styling of the
>>> table class being applied. So that would need to be changed or
>>> overridden in the CSS and page template.
>>> 
>>> I'll file a bug for this in the PM system.
>>> 
>>> 
>>> On Mon, Aug 12, 2013 at 4:55 PM, Julee <julee@adobe.com
>>> <mailto:julee@adobe.com>> wrote:
>>> 
>>>    Hi, folks:
>>> 
>>>    I'm looking at a category page that just looks horrible.[1]
>>> 
>>>    Any way to unstyle a table so it just looks like a table without the
>>>    weird first-column-as-lede style and without the column restrictions?
>>> 
>>>    Thanks.
>>> 
>>>    Julee
>>>    [1] http://docs.webplatform.org/wiki/Category:CSS-Regions
>>> 
>>>    ----------------------------
>>>    julee@adobe.com <mailto:julee@adobe.com>
>>>    @adobejulee
>>> 
>>> 
>> 
>> 
>> 
> 
> 
> 
>