> The above example will work. But may be your real CSS wont. If you'd
provide a link to a short testcase (real CSS) it would help.
Yeah, I probably made some mistake. I tested it once more and it
worked.
>> /*{{myClass{*/
>> [CSS]
>> /*}}}*/
>I wouldn't do this. The first */ will be rendered.
True. Moreover, all the /**/ before and after CSS are shown. The CSS
is rendered correctly, but myClass is not applied. Anyway, one of the
biggest reasons to use CSS was to skip scrolling which is on the
bottom of the CSS, but cutting it into parts solves this. Editing
<pre> isn't good since it is widely used apart the CSS.
Basing on this, one more important question, though: are there any
mechanisms of making hypretext-based CSS, like, say, CSS based on
tags? It would be beatiful a solution - to represent all the [[food
recipes]] tiddler with some style customized namely for tiddlers with
such tag, wouldn't it? Or
pre "in StyleSheets" { background-color: white; }
...
>If you do something like this
>/*{{{*/
>.button { display: block;}
>/*}}}*/
>some comment
>/*{{{*/
>.button { display: block;}
>/*}}}*/
>It will not work, because "some comment" is no comment!
Sure, but
/*{{{*/
.button { display: block;}
/*}}}*/
/***
some comment
***/
/*{{{*/
.button { display: block;}
/*}}}*/
works perfectly. Man, even the following works!! With some undesired
nonsense though, but some tweaking may help..
/*{{{*/
CSS1
/*}}}*/
/***
tw-comments!
<<slider chkSliderCSSSectionInStyleSheet [[StyleSheet##CSS-section]]
"second part" "">>
/%
!CSS-section
1
***/
/*{{{*/
.title { color: green;}
/*}}}*/
/***
2
/%%/
3
***/
An extra "/%" hides "%/" that's shown in the opened slider. As for
nonsence, the "1", "2", "3" make a bit more clear what's going on, but
I don't understand it fully.
On 10 ноя, 22:59, PMario <[email protected]> wrote:
> On Nov 10, 6:57 pm, Yakov <[email protected]> wrote:> Thanks,
> that's it. One more question, thought. Those comments-based
> > wrappings (/*{{{*/) make me think that StyleSheet is rendered as usual
> > CSS - but in this case I don't understand why
>
> > /*{{{*/
> > [some CSS]
> > /*}}}*/
> > /*{{{*/
> > [more CSS]
> > /*}}}*/
>
> > works so that "more CSS" is not applied. Any ideas?
>
> The above example will work. But may be your real CSS wont. If you'd
> provide a link to a short testcase (real CSS) it would help.
>
> > Also this seems to mean that I can use any other wrapper like
>
> > /*{{myClass{*/
> > [CSS]
> > /*}}}*/
>
> I wouldn't do this. The first */ will be rendered. If you need a
> different style change the <pre> or/and <code> definitions in your
> StyleSheet.
>
> > /*"""*/
> > [CSS]
> > /*"""*/
>
> > I think I'll try some such tricks.
>
> See above.
>
> =======
> If you do something like this
> /*{{{*/
> .button { display: block;}
> /*}}}*/
> some comment
> /*{{{*/
> .button { display: block;}
> /*}}}*/
>
> It will not work, because "some comment" is no comment! The browser
> treats everything, which is not covered inside /* ... */ as CSS
> commands, and "some comment" is not valid. Most of the time, the rest
> of the tiddler is ignored, by the >>browser<<
>
> The only thing, that tw does, is, that it renders something like this
> /*{{{*/
> .button { display: block;}
> /*}}}*/
>
> as a <pre> block, to get a better view. But the above has to be valid
> CSS !!!
>
> -m
--
You received this message because you are subscribed to the Google Groups
"TiddlyWiki" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/tiddlywiki?hl=en.
