Hiya, Jeremy :) On Saturday, July 23, 2016 at 7:57:31 AM UTC-4, Jeremy Ruston wrote: > > Hi Zaphod > > I’ll pick up the end of your comments first: > > Sorry in advance if my questions sound dense, but I've seen some amazing > things accomplished by your wonderful creation, and find it hard to believe > that this simple 'feat' is this hard to overcome. > > > First, it’s positively encouraged to ask questions here. It’s when people > engage in back and forth discussion that knowledge and techniques get > teased out, here in the open where anyone can join in. There’s a good > chance that while I’m typing this somebody else will dive in with > ready-to-use code for the needs you describe. > > Secondly, addressing why this apparently simple feat is hard to achieve. > There’s a double whammy here: what you want to do is not directly supported > by the core, which means that there is no ready-to-use mechanism. The > second part is that what you want to do is in the domain of CSS. The > trouble here is that understanding CSS requires an understanding of HTML, > and both are quite complex. TiddlyWiki does a little to ease writing CSS, > but it doesn’t really attempt to hide the true, horrific nature of CSS. >
Well, your statement about *"the true, horrific nature of CSS"* is certainly accurate - While being quite elegant and enabling us to do marvelous things, it can also be an ugly beast at times. > > So, as a beginner you’ve got the complexities of CSS/HTML and TiddlyWiki > multiplied together, and therefore quite a mountain to climb to implement > relatively complex new features. > I understand and can write/manipulate HTML fairly well, and have a *slightly-above-novice* grasp of CSS, having been digging into it for the past year or so. > As I said at the beginning, there’s a good chance that someone else in the > community can help with your immediate needs, as they have in other > threads. But the best response to the situation may be to keep on digging > into TiddlyWiki, and learn as much as you can by example :) > > Anyhow, in particular, you’ll need to understand transclusion, and the way > that it is used in stylesheets to fully implement the solution. But a key > part is that the CSS syntax for using an external image as a background is > different; > > background-image: url(http://www.example.com/bck.png); > > So, if you’ve got the image URL readily accessible, it’s pretty easy to > set the background colour for an element. > Yes, this has been no problem - I have several different background images in my Stylesheet that I have been using for testing (all but the current one commented out (/*)) and can switch them by editing the commenting notation. But, I'm still not able to get that same result from the ControlPanel section - It will accept and display any *tiddler* with a base64-encoded image inside, but I cannot understand how to feed it a URL to an external image??? Also --and something I didn't realize until just now-- whenever I have a background image selected through the ControlPanel/Theme Tweaks, it overrides any that I have declared in my Stylesheet. I assumed up until now that the Stylesheet tiddler was 'the last word' as far as CSS customization was concerned, overriding everything else... --Zaphod > Best wishes > > Jeremy > > -- You received this message because you are subscribed to the Google Groups "TiddlyWiki" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/tiddlywiki. To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/f6844e4a-cf00-4ace-870a-a2164f815154%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
