Hello Eric,
воскресенье, 10 ноября 2013 г., 21:29:48 UTC+4 пользователь Eric Shulman
написал:
On Sunday, November 10, 2013 9:24:38 AM UTC-8, Yakov wrote:
* ... recalc the styling on change of the ColorPalette
Any ideas?
Try adding this to your plugin:
Hi Mario,
nice trick with an updatable shadow. May be you also know how to solve the
following problem:
* I have a plugin which applies some styling, one rule is this:.c:before
{ content: [; color: [[ColorPalette::Foreground]]; }
* I have another plugin which changes ColorPalette (to
On Sunday, November 10, 2013 9:24:38 AM UTC-8, Yakov wrote:
* ... recalc the styling on change of the ColorPalette
Any ideas?
Try adding this to your plugin:
store.addNotification(ColorPalette,refreshStyles);
enjoy,
-e
Eric Shulman
TiddlyTools / ELS Design Studios
HELP ME TO HELP YOU -
I'm unclear on the 'granularity of the CSS tagging within a tiddler.
If I enter a number of lines of text, each seperated by a newline, just
that, not a double newline to geenrate a blank line, then there is no
spacing, there this no 'after paragraph margin'. I don't want that full
blank line
TiddlyWiki classic doesn't create paragraph p elements. That's why there
are some styling problems. It allways creates br elements for linebreaks.
div[tags~=Storyline].tiddler .viewer .p {margin-bottom: 5px; }
try padding-bottom
div[tags~=Storyline].tiddler .viewer .p {padding-bottom: 5px;
PMario said the following on 11/10/2013 02:19 PM:
[...]
--
The following stuff may not work for youbut who knows. For me it
increases the readability of the source text a lot. I use it with all
of my spaces.
That interesting and I can see cases where it applies. Just a matter of
PMario said the following on 11/10/2013 02:19 PM:
[...]
--
The following stuff may not work for youbut who knows. For me it
increases the readability of the source text a lot. I use it with all
of my spaces.
Then surely in my case this should work.
br {margin-bottom: 15px; }
But it
Anton Aylward said the following on 11/10/2013 05:09 PM:
PMario said the following on 11/10/2013 02:19 PM:
[...]
--
The following stuff may not work for youbut who knows. For me it
increases the readability of the source text a lot. I use it with all
of my spaces.
Then surely in my
On Sunday, November 10, 2013 10:26:43 PM UTC+1, Anton Aylward wrote:
I suppose I need those br's changed to /pp when they terminate a
paragraph and the next item is a paragraph. Skip headers and lists.
That really needs to get back in to the formatter, somehow.
IMO this won't work, since
Scott Simmons said the following on 10/27/2013 04:12 PM:
Again, something is not right.
The way you've worded that it seems that the dynamic system reads the
shadow tiddlers then adds internally the css from the user defined
StyleSheet tiddler and then adds 'invisibly' the
Hi folks,
First some info, why things are, as they are ...
Styling a TiddlyWiki can be quite tricky. IMO this has several reasons:
a) TiddlyWiki style origins date back prior to 2004
b) TiddlyWiki lets the end user change styles with the StyleSheet tiddler.
c) TiddlyWiki has shadow tiddlers
I did write Four Versions to create a shadow tiddler which may be
interesting
http://pmario.tiddlyspace.com/#%5B%5BFour%20Versions%20to%20create%20a%20shadow%20tiddler%5D%5D
-m
--
You received this message because you are subscribed to the Google Groups
TiddlyWiki group.
To unsubscribe from
On Saturday, October 26, 2013 10:49:22 PM UTC-4, Anton Aylward wrote:
Scott Simmons said the following on 10/26/2013 09:49 PM:
Consider what happens if you have a standard, non-fancy HTML page with
two external stylesheets referenced in the source. You open that page
in the browser,
Interesting, I guess since I use more specific CSS due to my complex deigns
I've never noticed that Plugin Shadow style sheets loads after StyleSheet.
To me this seems like a major flaw, and I'd like to propose that this is
should be fixed/changed as really it's a self defeating system, as it
I disagree.
Remember, styles set by plugins with setStylesheet() will NOT override any
styles in the user's StyleSheet — so you can circumvent/supersede/replace
any of those classes you want by simply adding your own rules in the
StyleSheet and knowing that conflicting rules set by
But you are needlessly taking power out of the users hands, and making the
whole thing more convoluted than it needs to be.
I'm all for hacking things but we should be striving to make systems that
minimize the need for such things as it creates fragmented plugins that get
scattered all over
I can appreciate the development philosophy, but I don't see a compelling
need for a fix here. Said fix, as far as I can conceive it, would
involve blocking plugin authors from using a (relatively obscure)
workaround and prevent — what exactly? Hypothetical style-hijacking? It's
not like
You wouldn't be blocking the authors form using this feature you would just
be switching it so that all shadow style sheets are rendered before the
users style sheet.
No plugin should be using these styles to override users styles to start
with and is highly unlikely to do any damage to a
If you would like to keep all functionality of the correct system than I'd
say the best option would be to make two user style sheets.
Where:
StyleSheet (Is always loaded last)
A new StyleSeet like SubStyleSheet? (Is Loaded where the current StyleSheet
is for special needs people like
If you look at your shadow tiddlers you'll notice you have:
StyleSheet
StyleSheetColors
StyleSheetLayout
By default
StyleSheet is where you as a user would put your styles.
StyleSheetColors contains all the built in core Color CSS
StyleSheetLayout contains all the built in core layout CSS
It IS a bit confusing at first glance! I'll take a stab at explaining some
bits, too.
The TiddlyWiki core does indeed contain some CSS. You don't have to go
digging in the source HTML to find it, though, because it's parsed and
viewable through the TW interface as four shadow tiddlers —
A couple of things about colors and the ColorPalette tiddler:
First, ColorPalette doesn't cascade the way CSS does. There's only one
ColorPalette, and it exists as a shadow tiddler in an empty TiddlyWiki. To
edit it, just find it (under More � Shadowed in the timeline), edit it,
and save it
Scott Simmons said the following on 10/26/2013 06:19 PM:
It IS a bit confusing at first glance! I'll take a stab at explaining
some bits, too.
The TiddlyWiki core does indeed contain some CSS. You don't have to go
digging in the source HTML to find it, though, because it's parsed and
viewable
I'm way limited on time so I'll try to address a couple of the things.
Shadow Tiddlers such as StyelSheetColors are not rebuilt every time but
they are built into a fresh empty TiddlyWiki and will rebuild themselves to
their original state if you delete them. AKA: If you change
On Saturday, October 26, 2013 7:19:35 PM UTC-4, Anton Aylward wrote:
When you say 'parsed viewable' do you mean that dynamically or
statically? Are these tiddlers generated a new every time the browser
reads in the source and run the javascript?
Others may be able to explain this
Arc Acorn said the following on 10/26/2013 07:57 PM:
Shadow Tiddlers such as StyelSheetColors are not rebuilt every time but
they are built into a fresh empty TiddlyWiki and will rebuild themselves
to their original state if you delete them. AKA: If you change
StyleSheetColors and than
Scott Simmons said the following on 10/26/2013 08:50 PM:
That would, to me, imply that *ALL* the CSS is parsed, including that
'built-in' to the plugins. So every time I install a plugin that has
its own css, save and reload, I'll get a renewed set of those 4 files.
The browser
Scott Simmons said the following on 10/26/2013 08:50 PM:
Styles added invisibly by plugins are added AFTER the shadow styles
from the core and user-defined styles from the StyleSheet tiddler. If
there's a plugin-supplied style you don't like or need to modify, there
are a couple of ways to
On Saturday, October 26, 2013 9:22:15 PM UTC-4, Anton Aylward wrote:
Scott Simmons said the following on 10/26/2013 08:50 PM:
The browser certainly rakes through it, looking at all the text.
All *what* text?
The HTML source code (from which the browser builds the working DOM).
I suppose one thing I should mention here is that I'm a hacker type, and
not a programming type especially when it comes to JavaScript.
Plugins Either make a shadow stylesheets or use element styling: eg div
class=thingone style=border:2px #FF0 solid/div
What does the 'setStylesheet()
Scott Simmons said the following on 10/26/2013 09:49 PM:
Consider what happens if you have a standard, non-fancy HTML page with
two external stylesheets referenced in the source. You open that page
in the browser, and the browser reads the code to display the page,
building a working version (a
Just as an FYI for order of how things go:
setStylesheet() Function is done when the plugins load which means these
styles should be loaded very early on before any stylesheets, and if
plugins had conflicting rules the one loaded lower would win AKA: zzPlugin
would override yyPlugin
eg your
Arc Acorn said the following on 10/26/2013 11:13 PM:
Just as an FYI for order of how things go:
setStylesheet() Function is done when the plugins load which means these
styles should be loaded very early on before any stylesheets, and if
plugins had conflicting rules the one loaded lower would
If a plugin uses the setStylesheet() method than no, or at least I can
not see a way for them to override the system style tiddlers.
If a plugin makes it's own stylesheet shadow tiddler than yes, it's
stylesheet should than override the systems.
As far as I can tell the built in shadow
And of course if you want a plugin to override all stylesheets you would
use Element styles, which would than force a user to to use the !important
flag to override them.
If for some reason you wanted to force a user to have to hack your plugin
to change a style you could make element styles
35 matches
Mail list logo
