Comments for page "9 - CSS module for per-page styling"

Re: Nice&useful

Wed, 30 Sep 2009 11:04:02 +0000

In fact in-page CSS is essential for making building blocks.

Nice&useful

Wed, 30 Sep 2009 10:51:45 +0000

It's nice and useful.

If it's used smartly, you can do thing like this:

[[module CSS]] .my-very-custom-listpages div { something } .my-very-custom-listpages div a { something } [[/module]] [[div class="my-very-custom-listpages"]] [[module ListPages]] Something in here [[/module]] [[/div]]

If it's used non-smartly, this can lead to vandalism. But vandalism can be done already

Re: Could you give a bit more info on Symbolic insertion?

Wed, 16 Sep 2009 14:02:16 +0000

pieterh wrote: I'll clarify the symbolic insertion section.

Symbolic replacement

This section removed for now.

Yep, that's definitely clarified. No room for misunderstanding now! =)

Re: Could you give a bit more info on Symbolic insertion?

Tue, 15 Sep 2009 08:25:22 +0000

I'm thinking about 'tag variables', which are tags in the form 'name:value', so that setting a new value replaces existing ones. This would let you do things like 'state:_open' in an issue tracker, or 'assign:steven', or 'status:green'.

That's independent of the CSS module. There would be only one value, so no {n}.

I'll clarify the symbolic insertion section.

Could you give a bit more info on Symbolic insertion?

Mon, 14 Sep 2009 11:54:23 +0000

I am not really sure about what you mean with Symbolic insertion, so the thought that jumped to my mind is maybe a stupid one but…
if %%css%% inserts the value of the first tag…
maybe %%css{n}%% can insert the Nth value

Awesome

Thu, 10 Sep 2009 13:29:48 +0000

Wow XD good idea James!

Re:

Wed, 09 Sep 2009 23:45:44 +0000

Hmm. And what if one were to use the code:

[[module CSS disable="{$code1}"]] Scheme 1 [[/module]] [[module CSS disable="{$code2}"]] Scheme 2 [[/module]] [[module CSS disable="{$code3}"]] Scheme 3 [[/module]]

Then you could make an include on another page:

[[include page |code1=false |code2=true |code3=false ]]

Good idea Pieter :D

(no title)

Wed, 09 Sep 2009 11:29:46 +0000

I don't understand the second option… if you don't want the code to appear in the html head, then why would you put it in a CSS module?

I can think of a few use cases. E.g. you have two or three CSS schemes you want to switch between, but have all visible. Or you are working on some CSS but it's caused some problems and you want to disable it for now, but still have visible.

Re:

Wed, 09 Sep 2009 11:08:14 +0000

What about show = "true | false" , instead of two separate attributes, show and disable?

Huh? Shall I requote myself?

So by choosing the having show="true", we are making the code visible

Edit: I see the page has been updated

Well, you have two independent options:

whether to show the code in the page, or not

whether to use the code in the html head, or not

I don't understand the second option… if you don't want the code to appear in the html head, then why would you put it in a CSS module?

Re:

Tue, 08 Sep 2009 21:38:08 +0000

What about show = "true | false" , instead of two separate attributes, show and disable?

Well, you have two independent options:

whether to show the code in the page, or not
whether to use the code in the html head, or not

You need two options, or one option with four values (clumsy).

Re:

Tue, 08 Sep 2009 19:58:43 +0000

Okay, that sounds logical.

What about show = "true | false" , instead of two separate attributes, show and disable ?

Re:

Tue, 08 Sep 2009 05:32:24 +0000

Well, the module shouldn't be visible at all, you know? It's just adding CSS to the page.

But on places like the Wikidot Community Forums, we may want to show the CSS code we're using, and it doesn't make much sense to duplicate code on a page. So by choosing the having show="true", we are making the code visible, without creating a duplicate [[code]] block with the same data within it.

(no title)

Tue, 08 Sep 2009 05:21:40 +0000

This looks useful. Can't say I'd use it regularly, but well worth implementing in my opinion.

Not sure I understand the "suggested attributes" section though. Are you saying that it should be possible to hide a code block?