[tw] Re: [TW5] MacroCall Widget & sub-macros

['Mark S.' via TiddlyWiki]

Even though they may sometimes seem to perform as functions, macros just 
support text substitution. Your version would have had a widget inside of a 
widget, which probably won't work, except on the 2nd Tuesday of months with 
full moons. Or something. I don't quite have it right yet.

This code seems to work. Hopefully it will be close to what you need:

\define myDataMacro(var2) <$transclude tiddler="$:/data/dataExample" index
={{$var2$!!keyfield}} />


<$macrocall $name="myDataMacro"  var2={{!!mytarget}} />




On Sunday, December 11, 2016 at 5:47:47 PM UTC-8, William RENOU wrote:
>
> I'm currently trying to link a tiddler's field to a DataTiddler 
> (dictionary tiddler). My (semi) working prototype has a SelectWidget 
> pulling up a list of Tiddlers. When one is selected, its fields are 
> displayed. The title of the current displayed tiddler is stored in a field 
> inside the viewer tiddler. One of these fields is codified (to save time 
> when editing this type of tiddler & to save time in case of field 
> codification changes). This field key values are stored in a Dictionary 
> Data Tiddler. My goal is to display the value of the field instead of its 
> stored key. 
> I use two macros to do so :
>
>- To retrieve the key to look for 'in the data tiddler) stored in the 
>target tiddler
>
> \define targetKey() <$transclude tiddler={{!!myTarget}} field="keyField"/>
>
>- I have a second macro that'll look for the value to be displayed in 
>my Data Tiddler 
>
> \define myDataMacro(var:0) <$transclude tiddler="$:/data/dataExample" 
> index=$var$/>
>
>- I globaly use them using a MacroCallWidget
>
> <$macrocall $name="myDataMacro" var=<>/>
>
>
>- My Data Tiddler has currently these test values
>
> 0:White1:Green2:Blue3:Orange4:Red5:Yellow
>
>
> My issue is the values aren't displayed. It should display the value 
> associated with the correct key, e.g. : when I try it to select a test 
> tiddler having "1" (without the quotes) as value for the *keyField* field, 
> instead of displaying *Green *it displays its value *1.*
> Using the MacroCallWidget without specifying the *var *variable displays 
> correctly the default value set in the *myDataMacro. *Using a key instead 
> of the sub-macro displays it's value correctly.
>

-- 
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 tiddlywiki+unsubscr...@googlegroups.com.
To post to this group, send email to tiddlywiki@googlegroups.com.
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/01ea2864-1f53-49bf-8f32-999f90a48264%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[tw] Re: [TWC] tw3jsPlugin (alpha) -- A plugin to use three.js in TW classic

[Vincent Yeh]

Thanks!

Have fun!
Vincent

On Sunday, December 11, 2016 at 2:18:48 AM UTC+8, Ste Wilson wrote:
>
> Of course. Clue's in the title. As you were. Carry on. :)

-- 
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 tiddlywiki+unsubscr...@googlegroups.com.
To post to this group, send email to tiddlywiki@googlegroups.com.
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/558fb77a-4f0b-4801-886b-9359ded43038%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[tw] [TW5] MacroCall Widget & sub-macros

[William RENOU]

I'm currently trying to link a tiddler's field to a DataTiddler (dictionary 
tiddler). My (semi) working prototype has a SelectWidget pulling up a list 
of Tiddlers. When one is selected, its fields are displayed. The title of 
the current displayed tiddler is stored in a field inside the viewer 
tiddler. One of these fields is codified (to save time when editing this 
type of tiddler & to save time in case of field codification changes). This 
field key values are stored in a Dictionary Data Tiddler. My goal is to 
display the value of the field instead of its stored key. 
I use two macros to do so :

   - To retrieve the key to look for 'in the data tiddler) stored in the 
   target tiddler

\define targetKey() <$transclude tiddler={{!!myTarget}} field="keyField"/>

   - I have a second macro that'll look for the value to be displayed in my 
   Data Tiddler 

\define myDataMacro(var:0) <$transclude tiddler="$:/data/dataExample" index=
$var$/>

   - I globaly use them using a MacroCallWidget

<$macrocall $name="myDataMacro" var=<>/>


   - My Data Tiddler has currently these test values

0:White1:Green2:Blue3:Orange4:Red5:Yellow


My issue is the values aren't displayed. It should display the value 
associated with the correct key, e.g. : when I try it to select a test 
tiddler having "1" (without the quotes) as value for the *keyField* field, 
instead of displaying *Green *it displays its value *1.*
Using the MacroCallWidget without specifying the *var *variable displays 
correctly the default value set in the *myDataMacro. *Using a key instead 
of the sub-macro displays it's value correctly.

-- 
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 tiddlywiki+unsubscr...@googlegroups.com.
To post to this group, send email to tiddlywiki@googlegroups.com.
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/a4584345-a4cd-45fe-a005-1ffe855a4cb6%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[tw] Re: Tiddlywiki for business

[Dragon Cotterill]

This is where I see the real downsides of using TW in a business situation.

Within a business the immediate necessity is to allow multiple users to 
access it at the same time. Obviously for reading this is not an issue. But 
for updating then this is where it's not so good.

Using Node to act as server-side to allow multiple users still doesn't 
solve these issues for TW usage. Because there is no communication 
mechanism to notify users that the page they are looking at has been 
modified. With software such as Confluence 
( https://www.atlassian.com/software/confluence ) this has all been 
resolved. TWederation is possibly one way around this limitation, but it's 
not quite there yet.

But for a single user, then there is nothing else which comes close to the 
flexibility of TW in terms of cost.

-- 
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 tiddlywiki+unsubscr...@googlegroups.com.
To post to this group, send email to tiddlywiki@googlegroups.com.
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/0f573920-04f4-4eab-991c-e296bee1938d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[tw] Tiddlywiki for business

[sidven5000]

What would be the best platform for big businesses, if they want to access 
and edit a lot of information in tiddlywikis from different computers? And 
will one tiddlywiki file be able to store all the information?
Like node.js, or tiddlydesktop etc.

-- 
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 tiddlywiki+unsubscr...@googlegroups.com.
To post to this group, send email to tiddlywiki@googlegroups.com.
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/c36918c0-1dbb-4a64-9742-ba7b9ea77d84%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [tw] Conveying: Moans about poor documentation

[Mat]

Jeremy wrote

Ultimately and ideally, we should base TiddlyWiki documentation efforts on 
> TiddlyWiki itself



Agree 100% and - (talking to everybody now.) - this is why I'm against 
distracting interim solutions or parallel solutions of other kinds. ANY 
other system would mean people would have to e.g register for yet another 
thing, learn new UI's and more lingo and it would scatter and fragment the 
docs and info (or repeat it) and I strongly fear this would split the 
community and be confusing. If the idea is to ultimately have TW be 
sufficient in itself, then... why shouldn't we just focus on creating that!?

The big problem is that "we creating that" is, implementation-wise, limited 
to very few knowledgeable individuals. However, the first step is still to 
define how we (all) would like for it to function. So maybe that's the best 
start? This makes sense even if you insist on some non-TW solution - i.e 
defining what a system should fulfill and what it should feature.


The solution is simple: switch to using TiddlyWiki in a 
> server-based configuration, but you lose the offline capability.  [...] 
> federation on the server under Node.js, where the technical difficulties 
> melt away. That’s how the threaded discussion on 
> http://tiddlywiki.com/tiddlywiki-eu-meetup-2016/ was built; the result is 
> a simple HTML file that downloads swiftly.
>
 
None of the alternative solutions (github, mediawiki, reddit, discourse, 
etc) work offline either AFAICT ..but, with a server-based TW one could (as 
pointed out) download the result and probably have it integrate well with 
ones own TW if that is desired.

@Jeremy - would it not be possible with a symbiotic solution including both 
a server-based node.js configuration and the vanilla version? Those 
inclined could host server based solutions used as exchange hubs for e.g 
documentation to/from which others could "post" or download documentation.

"Posting" would, perhaps, be done in a workflow similar to how the 
TWederation experiments are approaching it; Server-wikis would, from wikis 
they're following, *fetch *specified tiddlers (e.g tiddlers tagged "docs"). 
Because "Docs" is of interest to many people, it is likely to be 
redundantly hosted by multiple server wikis, thus protecting accessibility.

Not thought through: but how about a twitteresque system with UUIDs as 
hashtags (with potential aliases) for original issues and replies/whatever 
to such issues can be tagged with these UUIDs to associate it with the 
original issue. 

<:-)

-- 
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 tiddlywiki+unsubscr...@googlegroups.com.
To post to this group, send email to tiddlywiki@googlegroups.com.
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/62f60e93-bd02-48db-9f88-4c293abc31bd%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [tw] Re: [TW5] Host on github for free without any git knowledge or software installation

[Olegh Bondarenko]

Dear Danielo,

thanks once more for the job done.

I think explanation on two important files, namely: *.travis.yml*

 and *publish.sh*
,
added
into your instruction would allow getting the result a bit more
strightforward. These two actually made a stumble stone for me.

I'd like to use your approach further on for some TW5 based projects. In
this connection I'm looking for open authorization (or access control)
instruments at Github and Github Pages.

Would you be able to point me to the right direction?

Sincerely
Olegh


Olegh Bondarenko
http://goo.gl/bzDZfd




2016-12-11 4:48 GMT+02:00 Danielo Rodríguez :

> Hello oleghbond, I'm glad that you finally make it work.
> I'm curious, what were you doing wrong?
>
> Regards
>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "TiddlyWiki" group.
> To unsubscribe from this topic, visit https://groups.google.com/d/
> topic/tiddlywiki/s8pnvQW5UgY/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> tiddlywiki+unsubscr...@googlegroups.com.
> To post to this group, send email to tiddlywiki@googlegroups.com.
> 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/02781051-d940-414d-8dbe-8258159a3afc%40googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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 tiddlywiki+unsubscr...@googlegroups.com.
To post to this group, send email to tiddlywiki@googlegroups.com.
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/CAERWQ8m77q8Lq9iVw4zvgyig%2BEGSyMgATnL3Hs3ZnX95E8jYxg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[tw] Re: How to do an exact match of tags

[Tobias Beer]

Hi Steve,
 
Thanks for your reply. I still have no idea why you want a list of tiddlers 
that are "only tagged foo" but not any other tag ...about the process you 
imagine where this would be useful.

Since I have you "on the line" so to speak is there any way to combine the 
> contains and count macros
> into a single filter (instead of two)?
>

There always is a way, but as things stand, there is no motivation I can 
think of. Do you experience any problems with chaining the filters you need?

Best wishes,

Tobias. 

-- 
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 tiddlywiki+unsubscr...@googlegroups.com.
To post to this group, send email to tiddlywiki@googlegroups.com.
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/cab665b4-5adc-483b-acb1-df7c04b95e66%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [tw] Re: Automatic backup

[Jeremy Ruston]

Hi Questorian

Backup is fundamental - and I lost a few weeks work with the dreaded zero
> bytes html file from FF crash. A real waste.
>

That is indeed heartbreaking, and I appreciate that the built-in features
of TiddlyWiki don't on their own provide sufficient data security for most
users. I did do some work on a TiddlyFox update that includes backups at
the end of last year, but I'm afraid it remains unreleased. However, some
imminent technical changes to Firefox are going necessitate releasing a new
version in the next few weeks, so this will finally be attended to.

Best wishes

Jeremy


>
> Really - TWC has a thing where it just saved and datestamped the file on
> each open - can we have the same? Really does not matter if there are
> hundreds of files in  folder - better than none!
>
> Otherwise - great tool, and fantastic work - many thanks.
>
> On Friday, August 7, 2015 at 6:26:31 PM UTC+2, Jeremy Ruston wrote:
>>
>> My plan is to implement backups for TiddlyWiki5 within an updated
>> TiddlyFox.
>>
>> > A couple of them, such as download, could add a backup option out of
>> the box; or add a way to manually select a saver to use for backup.
>>
>> The download saver already supports backups, if you make Chrome download
>> a new file each time you save. It's not super convenient, but it's fairly
>> robust.
>>
>> > 1 - What is the current best strategy for auto-backup TW5 files (I'm
>> currently serving my wikis through dropbox. Perhaps I could put my dropbox
>> TW folder inside my google drive folder?)
>>
>> Dropbox keeps a version history for files, so you'll already have a
>> backup :) I believe it's limited to 30 days unless your a paid customer.
>>
>> > 2 - If indeed TW5 radically changed its approach to versioning, what is
>> the history and thinking behind this change? What were the trade-offs
>> involved that led to this change?
>>
>> The approach to versioning hasn't changed: neither TWC nor TW5 natively
>> supports tiddler versioning. We added it via TiddlyWeb/TiddlySpace to TWC,
>> but the only current approach for TW5 is to use the Node.js edition and
>> keep the tiddler files in GitHub.
>>
>> But I think you mean backup; it has only changed inasmuch as I wanted to
>> move support for backups into TiddlyFox, so that the backup policies could
>> be configured across all local wikis in one place. But, as I say, backups
>> are not yet implemented in TiddlyFox.
>>
>> Best wishes
>>
>> Jeremy.
>>
>>
>>
>>
>> On Wed, Aug 5, 2015 at 7:24 AM, RichardWilliamSmith <
>> richardwi...@gmail.com> wrote:
>>
>>> 1 - What is the current best strategy for auto-backup TW5 files (I'm
 currently serving my wikis through dropbox. Perhaps I could put my dropbox
 TW folder inside my google drive folder?)

>>>
>>> Dropbox backs everything up for you. If you visit the files online, you
>>> can see earlier revisions. I'm not sure how long they are kept etc.
>>>
>>>
 2 - If indeed TW5 radically changed its approach to versioning, what is
 the history and thinking behind this change? What were the trade-offs
 involved that led to this change?

>>>
>>> As Jeremy mentioned above, autosave is about to be added. It's been
>>> quite a while since I used twClassic but I seem to remember it just saved
>>> lots of copies of the file with time-stamps appended to their titles. Is
>>> that what you mean by versioning?
>>>
>>> Regards,
>>> Richard
>>>
>>> --
>>> 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 tiddlywiki+...@googlegroups.com.
>>> To post to this group, send email to tiddl...@googlegroups.com.
>>> Visit this group at http://groups.google.com/group/tiddlywiki.
>>> To view this discussion on the web visit https://groups.google.com/d/ms
>>> gid/tiddlywiki/5375e689-6843-414c-a1f5-2b5630ad85be%40googlegroups.com
>>> 
>>> .
>>>
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>>
>>
>> --
>> Jeremy Ruston
>> mailto:jeremy...@gmail.com
>>
>


-- 
Jeremy Ruston
mailto:jeremy.rus...@gmail.com

-- 
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 tiddlywiki+unsubscr...@googlegroups.com.
To post to this group, send email to tiddlywiki@googlegroups.com.
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/CAPKKYJZEBpGAoWVNXUuUNOER%3DUv9roNf-3GfhZKyT27HNLuJog%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [tw] Re: Testing Tech TW on my site. Feedback wanted!

[Eneko Gotzon]

On Sat, Dec 10, 2016 at 12:51 PM, David Gifford  wrote:

> maybe I missed something…
> ​
>

[Current Mac operating system writing form: macOS​ (no MacOS). Sorry]

-- 
Eneko Gotzon Ares
enekogot...@gmail.com

-- 
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 tiddlywiki+unsubscr...@googlegroups.com.
To post to this group, send email to tiddlywiki@googlegroups.com.
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/CAEV4i4UoR%3D3PKcLPMukwExXprmnETj%3D0nrV4gMQ33VpzfXE72g%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [tw] Re: fiddling with italic

[Eneko Gotzon]

Thank you very much Tobias.

Something seems wrong in the second coding option because both italic and
line breaking are not displayed, but *don't worry about*, *don't waste your
time with me*: I have a lot to learn here, I must go step by step.

Have a great live.

On Fri, Dec 9, 2016 at 7:32 PM, Tobias Beer  wrote:

>  Hi Eneko,
>
>
> *Note: Below, the styles would go into a Stylesheet tiddler.*
>
> I would think the cleanest way in terms of reusability would be to either
> do:
>
> @@.poem
> Axolagabe, ardura barik, berekoi, gaizto
> eta gainontzeko apal zein egundoko
> beste keria saldo guztiez
> jori, bapo elikatzen diren
> pentsaera, jarrera, jokaera
> trauskil, lakar, gordin edota ankerki
> atxilotzaile, herstaile, zapaltzaile, erauzle, moztaile, zikiratzaile
> ororen aitzi
> ''IZAN''
> besterik ez
> eta ondorioz
> ekin,
> beti.
> @@
>
> 
> .poem { white-space: pre; font-style:italic;}
> .poem strong {font-style:normal;}
> 
>
> Or to even have the tiddler be tagged *Poem *and then do:
>
> Axolagabe, ardura barik, berekoi, gaizto
> eta gainontzeko apal zein egundoko
> beste keria saldo guztiez
> jori, bapo elikatzen diren
> pentsaera, jarrera, jokaera
> trauskil, lakar, gordin edota ankerki
> atxilotzaile, herstaile, zapaltzaile, erauzle, moztaile, zikiratzaile
> ororen aitzi
> ''IZAN''
> besterik ez
> eta ondorioz
> ekin,
> beti.
>
> 
> .tc-tagged-Poem .tc-tiddler-body { white-space: pre; font-style:italic;}
> .tc-tagged-Poem .tc-tiddler-body strong {font-style:normal;}
> 
>
> Best wishes,
>
> Tobias.
>
> --
> 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 tiddlywiki+unsubscr...@googlegroups.com.
> To post to this group, send email to tiddlywiki@googlegroups.com.
> 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/af1cc0ae-eed4-4a46-9caa-4a9a5146d55d%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Eneko Gotzon Ares
enekogot...@gmail.com
Tfn (+34) 943.273.431 — 639 626 858
Donostia, EUS

-- 
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 tiddlywiki+unsubscr...@googlegroups.com.
To post to this group, send email to tiddlywiki@googlegroups.com.
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/CAEV4i4WYdJQK2NA1dpe6BbVPwDs4h1VbzB5TR-0Pvp3%3DNL46Fg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[tw] Re: [TW5] Wikitext: using Transclusion as Link Target

[Riz]

If anyone is not very particular about having those two buttons inside the 
tabbed structure, you can just add <$button 
to={{$:/temp/toc/selectedTiddler}}>Yo anywhere in your tiddlywiki 
and achieve the same result. Has the advantage of not having to redefine 
the whole macro and probably having the button on sidebar. 

-- 
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 tiddlywiki+unsubscr...@googlegroups.com.
To post to this group, send email to tiddlywiki@googlegroups.com.
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/b949c317-f304-4be2-80dc-fdf6d0364c66%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[tw] Re: [TW5] Wikitext: using Transclusion as Link Target

[Mat]

@grundyunderhill
Thanx for sharing but forgive my dull brain - could you please post an 
actual example of this?
To simplify for you, I put up this on 
tiddlyspot (password: password) which includes some dummy tiddlers tagged 
"tag1".
Would be appreciated.

<:-)




On Saturday, December 10, 2016 at 7:54:59 AM UTC+1, grundyunderhill wrote:
>
> Hi all,
> Not sure whether anyone is still following this thread; if so, maybe 
> you'll find this interesting.
>
> Ton Gerner was kind enough to point me here, in response to a question I 
> posed a few days ago, essentially looking to do same thing as Alex -- 
> create a link to open the current tiddler from a *toc-tabbed-internal-nav* 
> into the main story river.  I envisioned it being part of a template 
> tiddler, but couldn't figure out how to override the link-trapping 
> functionality of the macro.
>
> Based on the conversation here, though, I gleaned enough knowledge to do 
> something just as cool: an adapted version of the macro with the "break 
> out" link built into the right-hand pane.  In short, I've borrowed Tobias' 
> solution for creating the link, and paired it with a tweaked copy of the 
> *toc-tabbed-external-nav* macro.
>
> *toc-tabbed-external-nav* became the basis because that's where the 
> two-pane structure is defined -- *toc-tabbed-internal-nav* simply wraps a 
> call to this with a *<$linkcatcher>* widget.  My tweak places 
> *<$linkcatcher>* directly around transcluded content within the 
> right-hand pane instead, so that additional links, etc may be added outside 
> the *<$linkcatcher>* but still within the pane.  So altogether we have 
> this:
>
> \define tocTools( to )
> @@.tocTools
> <$button to="$to$">{{$:/core/images/link}}
> <$button to="$to$" 
> message="tm-edit-tiddler">{{$:/core/images/edit-button}}
> @@
> \end
>
> \define smokeMirrors( selected )
> <$macrocall $name="tocTools" to={{$selected$}}/>
> \end
>
> \define toc-tabbed-internal-nav-gu( tag, sort:"", 
> selectedTiddler:"$:/temp/toc/selectedTiddler", unselectedText, missingText, 
> template:"" )
> <$tiddler tiddler={{$selectedTiddler$}}>
>   
> <$linkcatcher to="$selectedTiddler$">
>   
> <$macrocall $name="toc-selective-expandable" tag="""$tag$""" 
> sort="""$sort$""" itemClassFilter=< selectedTiddler:"""$selectedTiddler$""">>/>
>   
> 
> 
>   <>
>   <$linkcatcher to="$selectedTiddler$">
> <$reveal state="""$selectedTiddler$""" type="nomatch" text="">
>   <$transclude mode="block" tiddler="$template$">
> <>
> <$transclude mode="block">$missingText$
>   
> 
> <$reveal state="""$selectedTiddler$""" type="match" text="">
>   $unselectedText$
> 
>   
> 
>   
> 
> \end
>
> ...which provides both "navigate" and "edit" links for the current tiddler 
> as buttons.  The *.tocTools* style wrapping the buttons can be defined 
> however you like, of course.  I have them floating right, with a small top 
> margin to put some space between them and the pane border.
>
> Muchos gracias, Tobias and Eric, for the hints about deferred linking and 
> the macros' use of *<$linkcatcher>*.  Hope my take on the solution will 
> be helpful to someone too.  Maybe one of these days I'll package it up as a 
> plug-in...
>

-- 
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 tiddlywiki+unsubscr...@googlegroups.com.
To post to this group, send email to tiddlywiki@googlegroups.com.
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/e6b1f2c6-6fa4-475e-9f83-80b6941456b7%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [tw] TW5 on node.js no longer loads server. Error executing boot module $:/plugins/tiddlywiki/text-slicer/modules/slicer.js: {"code":"MODULE_NOT_FOUND"}

[Rich]

Thanks Holger, 

took me a bit to figure out how to install the xmldom plugin, but that did 
the trick.  THanks!

On Saturday, December 10, 2016 at 1:56:11 AM UTC-10, Holger wrote:
>
> Am 09.12.16 um 01:57 schrieb Rich: 
> > ok, sorted out a workaround that gets it to serve anyway: 
> > | 
> > rich[tiddlers]$ mv '$__plugins_tiddlywiki_text-slicer.json.tid' 
> > '$__plugins_tiddlywiki_text-slicer.json.tid.bk' 
> > 
> > | 
> > 
> > but that removes the slicer plugin.  There was some problem some 
> > component of the most recent update in tw5 for node.js, but I can't 
> > remember/find what it was that made the workaround work.  any help?  I 
> > don't use the slicer too much but it would be nice to have it. 
>
> Hi, 
>
> do you have the "Wrapper for xmldom" plugin installed? It's needed by 
> the text slicer plugin. I have the current node.js version running with 
> the text slicer plugin without a problem (after a bit of the same errors 
> I think and discovering the dependency). 
>
> Cheers, 
>
> H 
>
>

-- 
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 tiddlywiki+unsubscr...@googlegroups.com.
To post to this group, send email to tiddlywiki@googlegroups.com.
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/9bc6e427-966f-4bbb-9c29-0f54065bba08%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.