Hi Stephan
- I understand that the tiddlers inside a plugin are considered shadow
tiddlers regardless of the name but I don't understand the why. Is it
simply the fact they are in a plugin that makes them shadow tiddlers?
It is to keep all tiddlers of a plugin bundled so when
All it takes is a rather simple build script (within TiddlyWIki), one that
isn't all too different from the one that creates TiddlyWiki itself... and
we're set.
With the approach that I'm suggesting we'd only need a build process for
generating static documentation snapshots. For interactive use,
Just a follow up, I was able to follow Tobias's directions and now I have a
pull down menu with Delete to allow me to delete mistakes without opening
first.
I use this in my Dev TW so when I try things out and they get FUBAR quickly
I can undo what I did just as quickly.
Rich Shumaker
--
You
Hi Jeremy,
Thanks, I actually decided to downgrade to TWc (on TiddlySpot)
since it's much more lightweight for any redirecting to kick in. ^^
Best wishes, Tobias.
--
You received this message because you are subscribed to the Google Groups
TiddlyWikiDev group.
To unsubscribe from this group
First thanks Tobias and Mario.
Tobias your pages are awesome and when I look at the details of the Tiddler
you have made your sites very dynamic.
Add something here and it pops up in other places, it has helped me a lot
to think about designing my TW's differently and more efficiently.
I also
Hi Rich,
Your Tiddler http://tobibeer.github.io/tb5/#Tobias%20Beer turns to mush
when dragged and dropped to my TW.
Well, that's pretty obvious if you grab one that constructs its contents
via the list macro or something making use of that. ^^
Not quite sure why you'd actually import it.
For interactive use, you'd just install the JS parser and view the raw
tiddler modules to see the formatted documentation inline with the code.
That appears to quite constrain documentation abilities as there is no way
to address and manage individual functions other than render them
On Friday, February 6, 2015 at 9:49:21 AM UTC+1, Tobias Beer wrote:
As for non-existing macros, it would perhaps be good if one could set a
flag in the controlpanel
so that a message appears telling you that you don't have it when looking
at a tiddler using it.
There has been some
Shadow tiddlers are special system tiddlers. They are there, that users can
change the default behaviour. ... But if something goes wrong, the user can
just delete the modified tiddler and the system tiddler will take over
again.
TiddlyWiki always used this behaviour as a backup feature. ..
Hi Rich,
Perhaps the most pragmatic approach is to be specific.
What exactly did you grab and what did you notice didn't come along?
Then I can perhaps think about better exposing this or make a little
tiddler telling you what to get.
~
As for non-existing macros, it would perhaps be good if
Tiddlywiki automatically prefixes the plugin tiddlers with the plugin
prefix so this can't happen.
Eventually, there will only be one GettingStarted that wins.
So, I believe Stephen's question is: Which and why?
Best wishes, Tobias.
--
You received this message because you are subscribed
Hi Stephen,
I understand that the tiddlers inside a plugin are considered shadow
tiddlers regardless of the name but I don't understand the why. Is it
simply the fact they are in a plugin that makes them shadow tiddlers?
http://tiddlywiki.com/#ShadowTiddlers — if you feel like something
Hi Danielo
What if I want to create a new deserializer? Makes no sense to load a
deserializer after al tiddlers are loaded. That's why I did not include the
deserializer as a tiddler, but I created them on the fly.
Yes, it's a bit of a chicken and egg thing. It's one of the reasons that
you
@Jeremy: any pointers where to start looking?
If you mean where to start looking for the way that the readme files are
built for the TW5 repo, then that's done here:
https://github.com/Jermolene/build.jermolene.github.io/blob/master/readme-bld.sh
You may find the step-by-step build
Which and why?
I think it's entirely down to the order in which the tiddlers get loaded
into the wiki. A later tiddler of the same title will override an earlier
one.
The order may differ between Node.js and the browser.
See *$tw.loadTiddlersBrowser()* and *$tw.loadTiddlersNode()* in
Where would I best hook what type of module
so as to redirect all incoming links (on a TiddlySpot) to a new location?
I have the feeling that it doesn't matter all that much as the whole page
will load anyway.
Best wishes, Tobias.
--
You received this message because you are subscribed to the
The order may differ between Node.js and the browser.
See *$tw.loadTiddlersBrowser()* and *$tw.loadTiddlersNode()* in
*$:/boot/boot.js*.
I get the feeling that it's not the best idea to overwrite a core component
using a plugin.
After all, two plugins may want to do the same and then
Hi Stephen
I understand that the tiddlers inside a plugin are considered shadow
tiddlers regardless of the name but I don't understand the why. Is it
simply the fact they are in a plugin that makes them shadow tiddlers?
Yes, although the logic makes more sense the other way around: shadow
You could try adding a tiddler with the tag $:/tags/RawMarkup and something
like this (not tested):
script
document.location = http://newurl.com#; + document.location.hash;
/script
Best wishes
Jeremy.
On Fri, Feb 6, 2015 at 2:49 PM, Tobias Beer beertob...@gmail.com wrote:
Where would I
19 matches
Mail list logo
