Re: [tw] Re: Testers needed for TiddlyServer

[codacodercodacoder]

On Wednesday, October 11, 2017 at 10:03:34 PM UTC-5, Arlen Beiler wrote:
>
>  If you use the nexe zip, it should not matter what version of node you 
> have installed.
>
>
Good.
 

> I cannot see a reason that a 412 would suddenly start happening unless 
> perhaps if two saves happened too close to each other, but the normal 
> autosave mechanism doesn't seem to work like that.
>

Agreed.  I did try again, and on one of the tests, the second manual save 
brought the error up.  The file had only been open a matter of seconds.  
All other instances took much longer and, as I said before, happens during 
autosave.

 

> But I'll check into it. I have a couple ideas.
>
> If it was happening to me the first thing would be to pause Dropbox. But I 
> use Dropbox all the time for this stuff. And I never run into trouble with 
> it.
>
>
Dropbox is not in my setup, but Ander's stores his files in his dropbox 
folder.
 

-- 
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/b3c0b545-ef0b-4748-80aa-a930f10d7509%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [tw] Re: Testers needed for TiddlyServer

[codacodercodacoder]

On Wednesday, October 11, 2017 at 4:08:16 PM UTC-5, Arlen Beiler wrote:
>
> The reason I asked about the terminal output is because the line that 
> specifies the put request also specifies the response that the server 
> returned, which in this case should be 412. 
>
>

Yep, here it is:

Settings file: C:\Wikis\TiddlyServer-2.0.7-nexe\settings.json
Open your browser and type in one of the following:
127.0.0.1:8080
[2017-10-11T16:22:35.406-0500] PUT 127.0.0.1  200 127.0.0.1 
/books/testwiki
.html   854.115 ms - -
[2017-10-11T16:22:59.737-0500] PUT 127.0.0.1  200 127.0.0.1 
/books/testwiki
.html   146.147 ms - -
[2017-10-11T16:23:02.356-0500] PUT 127.0.0.1  200 127.0.0.1 
/books/testwiki
.html   143.149 ms - -
[2017-10-11T16:23:03.996-0500] PUT 127.0.0.1  200 127.0.0.1 
/books/testwiki
.html   144.009 ms - -
[2017-10-11T16:23:05.605-0500] PUT 127.0.0.1  200 127.0.0.1 
/books/testwiki
.html   146.161 ms - -
[2017-10-11T16:23:06.878-0500] PUT 127.0.0.1  200 127.0.0.1 
/books/testwiki
.html   155.558 ms - -
[2017-10-11T16:23:08.573-0500] PUT 127.0.0.1  200 127.0.0.1 
/books/testwiki
.html   168.605 ms - -
[2017-10-11T16:23:53.250-0500] PUT 127.0.0.1  200 127.0.0.1 
/books/testwiki
.html   144.057 ms - -
[2017-10-11T16:24:00.915-0500] PUT 127.0.0.1  200 127.0.0.1 
/books/testwiki
.html   144.234 ms - -
[2017-10-11T16:24:40.083-0500] PUT 127.0.0.1  200 127.0.0.1 
/books/testwiki
.html   143.304 ms - -
[2017-10-11T16:25:38.675-0500] PUT 127.0.0.1  412 127.0.0.1 
/books/testwiki
.html   1.528 ms - -
[2017-10-11T16:26:05.757-0500] PUT 127.0.0.1  412 127.0.0.1 
/books/testwiki
.html   0.654 ms - -


I also got this on the very first attempt.  I restarted and didn't see it 
again:

[2017-10-11T16:18:20.981-0500] OPTIONS 127.0.0.1  200 127.0.0.1 
/books/testwiki
.html   1.254 ms - -
[2017-10-11T16:18:33.329-0500] PUT 127.0.0.1  200 127.0.0.1 
/books/testwiki
.html   153.159 ms - -
TypeError: Cannot read property 'length' of undefined
at Function.morgan.token [as local-addr] 
(C:\Wikis\TiddlyServer-2.0.7-nexe\d
ist\server.exe:1598:37)
at eval (eval at compile 
(C:\Wikis\TiddlyServer-2.0.7-nexe\dist\server.exe:3
181:10), :7:26)
at developmentFormatLine 
(C:\Wikis\TiddlyServer-2.0.7-nexe\dist\server.exe:1
632:9)
at Array.logRequest 
(C:\Wikis\TiddlyServer-2.0.7-nexe\dist\server.exe:2912:1
8)
at listener (C:\Wikis\TiddlyServer-2.0.7-nexe\dist\server.exe:2688:17)
at onFinish (C:\Wikis\TiddlyServer-2.0.7-nexe\dist\server.exe:2619:7)
at callback (C:\Wikis\TiddlyServer-2.0.7-nexe\dist\server.exe:2475:12)
at Socket.onevent 
(C:\Wikis\TiddlyServer-2.0.7-nexe\dist\server.exe:2513:7)
at emitOne (events.js:101:20)
at Socket.emit (events.js:188:7)
at emitErrorNT (net.js:1277:8)
at _combinedTickCallback (internal/process/next_tick.js:80:11)
at process._tickCallback (internal/process/next_tick.js:104:9)
caught process uncaughtException
closing server

-- 
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/be8a3978-a0d7-4b5f-8326-de9efd003d9e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [tw] Re: Testers needed for TiddlyServer

[codacodercodacoder]

On Wednesday, October 11, 2017 at 4:08:16 PM UTC-5, Arlen Beiler wrote:
>
> The reason I asked about the terminal output is because the line that 
> specifies the put request also specifies the response that the server 
> returned, which in this case should be 412. 
>
>
I'll pay closer attention when I try it again.


> One more question, what version of node are you both using, or are you 
> using the nexe version that I posted at the top of this thread?
>
>
I asked you that a couple of times.  I have Node 5.5.0 installed but I 
would guess yours is being used (I guess it's "in" the nexe build, right?)


-- 
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/160d7dd8-867f-473d-be5a-8b4ed616f7e8%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[tw] Re: [TW5] Macro Question: Is there an easier way to achieve this?

[codacodercodacoder]

On Wednesday, October 11, 2017 at 1:34:57 PM UTC-5, Stephan Hradek wrote:

 > also think we need a few more operators

THIS.

But that's some pretty nifty filtering, Stephan.  I'd have been holding my 
breath running a recursive filter ;)

I certainly think there is need for some basic string manip macros -- they 
seem to follow on naturally from the enlist operator, IMO.

Coda

-- 
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/9561e82c-a3b5-41c1-817c-9fe82169aa9e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [tw] Re: Testers needed for TiddlyServer

[codacodercodacoder]

You can discount the dropbox theory, not in play here.

I'm intrigued by your point #4 though.  How long do you typically wait for 
the problem to magically "go away"?

On Wednesday, October 11, 2017 at 2:59:26 PM UTC-5, Anders Jonsson wrote:
>
> I keep my TWs on an internal drive. 
>
> But that reminds me that I have them stored in my Dropbox folder, and 
> wondering if the Dropbox-syncing might affect things? (Guessing blindly, me 
> knowing next to nothing about the ”under the hood network stuff”...) 
>
> //Anders

-- 
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/3cf7813a-ae77-45d7-8cbb-ea7cde390264%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [tw] Re: Testers needed for TiddlyServer

[codacodercodacoder]

On Wednesday, October 11, 2017 at 2:21:54 PM UTC-5, Anders Jonsson wrote:
>
> I will chime in to say that I’ve also had plenty of this 412/RSOD problem 
> (and I’m relying on equal measures of manual saves and autosaves; win10, 
> FF56, TW5.1.14)... 
>
> 1. White box stating ”Error while saving: XMLHttpRequest error code: 412” 
> 2. The big, red ”embarrasment” box stating ”TypeError: xhr is undefined” 
> (3. In the TiddlyServer window the 412 code is given for the last PUT) 
> 4. Generally no saving possible afterwards without reloading the 
> tiddlywiki (thereby losing any changes since last successful save), but 
> sometimes I’ve found that the problem ”goes away” by itself after me 
> waiting a while, meaning that I can once again start saving normally 
> without having to reload... 
>
>
Apart from the message posted to the server window, that's identical to my 
system.  One thing I did wonder... my wikis are on an external drive.  
Yours?
 

-- 
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/49f88e13-08ba-43cb-bc18-442acbc4e6f6%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [tw] Re: Testers needed for TiddlyServer

[codacodercodacoder]

On Wednesday, October 11, 2017 at 1:07:38 PM UTC-5, Arlen Beiler wrote:
>
> So even after you start getting the error it will still manually save 
> without errors?
>

No.  Once I've seen the error, the only cure is to close the TW and reopen 
it.

 

> And when you say save, do you mean it saves to the server?
>

Yes, regular saving.

 

> Or does the manual download saver kick in? 
>

No.  If I try to save AFTER seeing the error, I get the error again. It 
DOES NOT save.
 

>
> Or do you mean that the error only starts occurring when using autosave? 
>

That's hard to say.  I rarely save manually so I have only seen the error 
appear under regular autosave conditions. 

 

>
> What version is your TiddlyWiki file? 
>

5.1.14
 

>
> Also, could you paste in the entire logs from the TiddlyServer terminal 
> window?
>
>
It's gone now -- I had to return to my old system (using tiddlyfox).  I can 
assure you, the server window only contained regular PUT statements which 
suggests to me, the server "thinks" it has saved the wiki (but clearly 
hasn't since it responded with a 412).  Which preconditions are you 
setting/checking?  If-Unmodified-Since?  Anything else? 

I may be able to retry TS properly later.

Coda
 

-- 
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/3915c92c-ddeb-445d-ab81-fb2c37991ab2%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [tw] Re: Testers needed for TiddlyServer

[codacodercodacoder]

On Wednesday, October 11, 2017 at 10:32:41 AM UTC-5, Arlen Beiler wrote:
>
> The 412 is thrown if the server thinks the client is working from a stale 
> copy. Is it somehow possible that another application updated the html file 
> on disk?
>

No, single copy open in the browser.  Note that they occur from autosaves 
(closing an edited tiddler, for example) not manual saves by clicking the 
save icon.

 

> Especially if you can do several saves and then start getting the error. 
>

Right.  And once I have the errors appear, there is no way back except to 
close and reopen the TW.


 

> The other errors are a little puzzling, but I think might involve an 
> unrelated bug in TiddlyWiki (
> https://github.com/Jermolene/TiddlyWiki5/issues/2989). 
>

Note that error #1 appears first while error #3 appears in the console.  
When the dialog in #1 is cleared, #2 appears in the UI and #4 appears in 
the console.  IOW, it's a sequence that always repeats.  And once it has 
occurred, clicking the TW save icon will repeat the whole thing again.
 

>
> On Wed, Oct 11, 2017 at 11:03 AM,  
> wrote:
>
>> Hi Arlen,
>>
>> I've tried it this morning and all seemed to go well for a while then 
>> errors started to occur when saves are made.
>>
>> 1 - An alert pops up with XMLHttpRequest error code: 412
>>
>> 2 - Then a Red Internal JS Error TypeError: xhr is undefined
>>
>> 3 - The console says XML Parsing Error: no root element found Location: 
>> http://127.0.0.1:8080/books/testwiki.html Line Number 1, Column 1:
>>
>> 4 - Followed by TypeError: xhr is undefined
>>
>> Nothing is mentioned in the server console, just the regular PUT 
>> statement.
>>
>> If I close the testwiki and reopen, it starts working again (until it 
>> eventually fails again).
>>
>> Coda
>>
>>
>> On Tuesday, October 10, 2017 at 7:06:58 AM UTC-5, Arlen Beiler wrote:
>>
>>> Good Morning everyone,
>>> I just released an update to TiddlyServer. This release brings support 
>>> for nexe. So now I need people to test it. If you are interested, go to 
>>> https://github.com/Arlen22/TiddlyServer/releases/tag/2.0.7 and download 
>>> one of the nexe builds. 
>>>
>>> For now, I only have windows and mac builds in 64 bit. The 
>>> settings.json file still belongs in the root folder, but the executable is 
>>> in the dist folder. Let me know how it works. 
>>>
>>> Thanks,
>>> Arlen
>>>
>> -- 
>> 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 https://groups.google.com/group/tiddlywiki.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/tiddlywiki/ea2dd98e-e1f0-4f35-8c3e-199094e48aa8%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/b351e4b4-f946-4e37-830d-45360bd893ae%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[tw] Re: Testers needed for TiddlyServer

[codacodercodacoder]

Hi Arlen,

I've tried it this morning and all seemed to go well for a while then 
errors started to occur when saves are made.

1 - An alert pops up with XMLHttpRequest error code: 412

2 - Then a Red Internal JS Error TypeError: xhr is undefined

3 - The console says XML Parsing Error: no root element found Location: 
http://127.0.0.1:8080/books/testwiki.html Line Number 1, Column 1:

4 - Followed by TypeError: xhr is undefined

Nothing is mentioned in the server console, just the regular PUT statement.

If I close the testwiki and reopen, it starts working again (until it 
eventually fails again).

Coda


On Tuesday, October 10, 2017 at 7:06:58 AM UTC-5, Arlen Beiler wrote:
>
> Good Morning everyone,
> I just released an update to TiddlyServer. This release brings support for 
> nexe. So now I need people to test it. If you are interested, go to 
> https://github.com/Arlen22/TiddlyServer/releases/tag/2.0.7 and download 
> one of the nexe builds. 
>
> For now, I only have windows and mac builds in 64 bit. The 
> settings.json file still belongs in the root folder, but the executable is 
> in the dist folder. Let me know how it works. 
>
> Thanks,
> Arlen
>

-- 
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/ea2dd98e-e1f0-4f35-8c3e-199094e48aa8%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[tw] Re: Suggestions Box ...

[codacodercodacoder]

IMO, the UI for fields could do with some love, care and attention.  I have 
frequently wanted to copy/move a set of fields from one tiddler to 
another.  A way to do that without going through the standard UI would be 
very helpful.  Imagine "marking" the required fields (via checkboxes, 
perhaps?) then clicking a button "Copy" or "Move".  Open the target tiddler 
and click "paste".  The marked fields are then copied/moved into the target 
tiddler. Done.

On Tuesday, October 10, 2017 at 4:27:32 AM UTC-5, @TiddlyTweeter wrote:
>
> There are so many great programmers here I thought it might be a useful 
> idea to have a general "Suggestions Box" for stuff that has not been (as 
> far as I know) been implemented they might be interested 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/2bdcc403-ad29-4fde-bec2-ada6fd3aeaf0%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [tw] Re: Testers needed for TiddlyServer

[codacodercodacoder]

On Tuesday, October 10, 2017 at 10:18:36 PM UTC-5, Arlen Beiler wrote:
>
> I'm sorry for the confusion.
>
>- Download TiddlyServer-2.0.7-nexe-win-64.zip from 
>https://github.com/Arlen22/TiddlyServer/releases/tag/2.0.7
>- Unzip to your desired location.
>- Copy your settings.json inside the folder you just unzipped, next to 
>the dist, assets, and tiddlywiki folders.
>- Open the dist folder, and double-click on server.exe
>
>
Bingo.
 

> Don't worry about start.bat, it isn't needed in this case.
>
> If something is not clear, please ask. I am sorry that I am not so clear 
> the first time around.
>
>

I'll play with it more tomorrow.

THANKS!
Coda

-- 
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/822551ef-8a7d-4958-9954-149a47b50a38%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [tw] Re: Testers needed for TiddlyServer

[codacodercodacoder]

No luck, Arlen...

On Tuesday, October 10, 2017 at 9:44:11 PM UTC-5, Arlen Beiler wrote:
>
>
> @codacoder, tiddlyserver-2.0.7-nexe is the download with the executable. 
> The one you downloaded is tiddlyserver-2.0.7-bundled. I'm sorry for the 
> confusion, I don't think I explained it correctly. 
>
>
Okay, I downloaded the nexe zip, extracted it, copied the folders from the 
unzipped set over the previous unzipped set, ran start.cmd, same error.

Next, I unzipped the nexe zip again (clean), copied the start.cmd and 
settings.json from the old set into the nexe set up and got this:


C:\DL\TiddlyServer\TiddlyServer-2.0.7-nexe>node server
module.js:341
throw err;
^

Error: Cannot find module 
'C:\DL\TiddlyServer\TiddlyServer-2.0.7-nexe\server'
at Function.Module._resolveFilename (module.js:339:15)
at Function.Module._load (module.js:290:25)
at Function.Module.runMain (module.js:447:10)
at startup (node.js:139:18)
at node.js:999:3

C:\DL\TiddlyServer\TiddlyServer-2.0.7-nexe>pause
Press any key to continue . . .

So, here's where I'm at:

I have Windows 7 with Node version 5.5.0 already installed.

1 - is having node already installed a problem for TS?

2 - Which download and which set of instructions should I follow?

Coda

-- 
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/9e274859-4442-4575-9168-f0a542a2ef84%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[tw] Re: Testers needed for TiddlyServer

[codacodercodacoder]

On Tuesday, October 10, 2017 at 7:06:58 AM UTC-5, Arlen Beiler wrote:
>
> Good Morning everyone,
> I just released an update to TiddlyServer. This release brings support for 
> nexe. So now I need people to test it. If you are interested, go to 
> https://github.com/Arlen22/TiddlyServer/releases/tag/2.0.7 and download 
> one of the nexe builds. 
>
> For now, I only have windows and mac builds in 64 bit. The 
> settings.json file still belongs in the root folder, but the executable is 
> in the dist folder. Let me know how it works. 
>
> Thanks,
> Arlen
>

I get this:


C:\DL\TiddlyServer\TiddlyServer-2.0.7>node server
C:\DL\TiddlyServer\TiddlyServer-2.0.7\src\server.js:186
return server_types_1.obs_stat(state)(favicon).mergeMap(([err, 
stat]) => {
 ^

SyntaxError: Unexpected token [
at exports.runInThisContext (vm.js:53:16)
at Module._compile (module.js:387:25)
at Object.Module._extensions..js (module.js:422:10)
at Module.load (module.js:357:32)
at Function.Module._load (module.js:314:12)
at Module.require (module.js:367:17)
at require (internal/module.js:16:19)
at Object. 
(C:\DL\TiddlyServer\TiddlyServer-2.0.7\server.js:1:63)
at Module._compile (module.js:413:34)
at Object.Module._extensions..js (module.js:422:10)

C:\DL\TiddlyServer\TiddlyServer-2.0.7>pause
Press any key to continue . . .

I downloaded the bundle zip file, extracted it, started with the example 
settings.json and cleaned out the comments, added a single alias "books": 
"some_path" and ran start.cmd.

Does it matter the version of node installed if it's already installed? Or 
will it use the one in the bundle first?

Coda

-- 
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/86412638-8944-4a7f-8e8b-da2b55a170e4%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[tw] Re: Using TiddlyFox into the future

[codacodercodacoder]

On Wednesday, October 4, 2017 at 12:04:35 PM UTC-5, Rob Hoelz wrote:
>
> I can see where RichardWilliamSmith is coming from - 
>

Me, too.  The way they handled it was indeed poor.  For example, they could 
have made an exception and made FF56 an ESR release but (as yet) not so.  
FF52 is the last ESR with regular addons support.

 

>
> That being said, I was looking through the Web Extensions APIs, and it 
> looks like the downloads API 
>  
> could potentially be used to implement some of TiddlyFox's functionality.  
> It means you would need to keep your tiddlywiki.html file under your 
> Downloads folder, but it's better than nothing.
>

You can change the location of downloads in the preferences (Options) 
settings.  If you want to have the best of both worlds, you can set up 
different profiles for TW files (I do my TW work that way).  Having tested 
this for a few weeks, I quite like it.  I no longer see the loss of 
tiddlyfox as an 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/f3131b89-18ef-4849-8365-64b57fe4bdba%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[tw] Re: TiddlyWiki not working properly on latest version of firefox

[codacodercodacoder]

Forgive me but my reply was to Adrian's original post, nothing else.  
Reading anything else into it is a problem for the reader ;)

My 5 cents (with interest) :)

On Monday, October 2, 2017 at 1:23:43 PM UTC-5, @TiddlyTweeter wrote:
>
> Ciao codacoder...
>
>> I've tested 55, 56, 57 and 58 and all my wikis run fine (ignoring the 
>> fated tiddlyfox plugin).
>>
>
> That post is a little bit confusing in that you are not saying HOW you 
> save. Folk coming up to 57 dependent on TiddlyFox need to be clearer about 
> the alternative ways that folk save.
>
> My 2 cents.
>
> Best wishes
> Josiah
>

-- 
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/b8ef7b2b-5a9c-431f-9e18-bd38ea22d4ed%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[tw] Re: TiddlyWiki not working properly on latest version of firefox

[codacodercodacoder]

Hi Adrian

Well, you were talking about a layout issue, not about tiddlyfox (which 
WILL be a problem from FF57 onward).  I was commenting about your layout 
issues which, to me, sound like CSS problems which I could not repeat using 
the FF versions I mentioned.

Regarding the tiddlyfox issue, there are many threads below this one 
addressing that exact problem.  You could, for example, try the default 
save mechanism enhanced by *Mark S* here:

https://groups.google.com/forum/#!msg/tiddlywiki/lPDUD66GBD8/nyxytP_DEwAJ


On Monday, October 2, 2017 at 1:01:11 PM UTC-5, Adrian Holbrook wrote:
>
> If the tiddlyfox plugin does not work how do you save the file? Whenever i 
> tried without the plug in - and even with the plugin until I enabled  it to 
> save - the file would disappear and not get saved.
>
> On Monday, October 2, 2017 at 5:59:01 PM UTC+1, codacoder...@outlook.com 
> wrote:
>>
>> Latest full release of Firefox (at time of writing) is 56.0 (not 55x).
>>
>> I've tested 55, 56, 57 and 58 and all my wikis run fine (ignoring the 
>> fated tiddlyfox plugin).
>>
>>
>> On Monday, October 2, 2017 at 10:32:14 AM UTC-5, Adrian Holbrook wrote:
>>>
>>> Just updated to Firefox 55.0.3 and the right hand menu does not work any 
>>> more. I can still use the scroll bar but i get a ghosted menu that scrolls 
>>> and another copy behind it that stays in the same place. Clicking on any of 
>>> the menu items no longer works. Can anyone help?
>>>
>>

-- 
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/16ccafdd-2bc1-476a-9518-fae9a0b86c91%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[tw] Re: Query: Are Regular Expressions Regular in TW?

[codacodercodacoder]

Bingo!

Thank you Mark, that's a really useful addition to my toolbox.


On Friday, September 29, 2017 at 7:46:54 PM UTC-5, Mark S. wrote:
>
> Thank you for the feedback.
>
> There was a bug in the javascript macro. I've attached a new version.
>
> Also, for your finder filter, you (probably) need to add the non-greedy 
> operator ("?").  So your filter looks like:
>
> <$list filter='[tag[TestGroups]get[text]regexps[(?g)bk-ann 
> ".+?"]regexps[bk-ann "(.+?)"]]'  >
>
> HTH
> Mark
>
> On Friday, September 29, 2017 at 4:37:58 PM UTC-7, 
> codacoder...@outlook.com wrote:
>>
>> Sorry I'm so late coming to this Mark, but I think I've found an issue...
>>
>> On Friday, August 25, 2017 at 9:18:05 AM UTC-5, Mark S. wrote:
>>>
>>> This version will return  sub-groups for non-global searches. So in 
>>> codacoder's example, this search:
>>>
>>> <$list filter='[tag[TestGroups]get[text]regexps[(?g)bk-ann 
>>> ".+"]regexps[bk-ann "(.+)"]]'  >
>>>
>>> will change this:
>>>
>>>
>>> <>X

 and

   <>>> macros">>


>>> Into
>>>
>>>
>>> Explain the use of the Tiddlywiki's macro system
 Explain the scope rules of Tiddlywiki macros
>>>
>>>
>>> Notice that it takes 2 regexps filters to accomplish this (the first 
>>> global one finds the items, the second trims them).
>>>
>>>
>> Understand that there may be zero or more (usually more than one) bk-ann 
>> in any given tiddler.  So, in the case of the example (if both are included 
>> in one tiddler, I see only
>>
>> Explain the use of the Tiddlywiki's macro system
>>
>> IOW, once a match is found, the rest of the text is ignored.  Is there a 
>> way to make the regex less greedy and carry on to do the rest?
>>
>>  Coda
>>
>
>

-- 
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/69954b5f-eee9-40c8-a8d2-da92169c3fce%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[tw] Re: [TW5] New Plugin - Json Mangler!

[codacodercodacoder]

Hi Joshua

I think there's a problem... I did as suggested "Edit one of the existing 
Json Tiddlers to get started" and after clicking "Push Fields", I get 
this...



Win7, Firefox 55 and 57 (Nightly)

-- 
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/5a514431-cac5-40e4-91ae-c68b49ef4edd%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [tw] Query: Markup Parsers

[codacodercodacoder]

On Wednesday, September 13, 2017 at 12:55:28 PM UTC-5, @TiddlyTweeter wrote:
>
> TonyM & Coda 
>
> Let me expose my age as its likely near yours. And since you broke this 
> thread.
>
> Back in the days of Dos only, what you had was "programs" (extremely 
> boring things that only worked one way) and "TSRs" (extremely interesting 
> gizmos that let you rule programs).
>
>
Ah, yes, TSRs - recall I had a chat with Jeremy about Terminate and Stay 
Resident code.  Wrote a few -- some of them were even quite useful :)
 

> AutoHotKey(AHK) is a great evolution of the TSRs that survived. Most of 
> them died on PCs with Windows. At one time TSRs were considered as 
> important as applications--and often they were better than them. Windows 
> killed most of them.
>


One could argue that most modern OSs are built from TSRs.

 

>
> Enough nostalgia.
>
> To the nub. 
>
> WHAT has AHK got to do with TiddlyWiki? I think VERY LITTLE. 
>

AHK has nothing to do with TW.  But in combination, they work well together.

 

>
> Talk-back ...
>
>
I did.  :) 

-- 
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/4212e9a1-d479-4439-ae1e-16e08b4b1b70%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [tw] Query: Markup Parsers

[codacodercodacoder]

Tony,

Try these:

;Pretty quotes
^':: SendInput “
^+':: SendInput ”



That's Ctrl ' and Ctrl-Shift '  (that's a single-quote at the end of each)


-- 
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/f60873fe-fd9d-42cb-9a72-131f6bcc0e62%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [tw] Query: Markup Parsers

[codacodercodacoder]

Hi jan

On Tuesday, September 12, 2017 at 4:31:56 PM UTC-5, Jan wrote:
>
> Hi Coda,
> I would like to avoid expressions looking to technical in the inputText.
> In my concept the macro is transcluded by the rolename:
>
> {{Peter}} like all roles leads to a tiddler which a only macro called 
> <> as text. The macro is defined:
> \define role() 
> <$list 
> filter="[{!!title}tag[emphasis]]"><$list 
> filter="[{!!title}has[name]]"emptyMessage={{!!title}}>{{!!name}}
> \end
>

That's completely fine (I think).  I hate typing out << and >> everywhere 
-- when authoring, it breaks my concentration and "flow".

My "system" doesn't care what the markup looks like (it can be any 
TW-valid-text -- a macro, a transclusion or any combination you can dream 
up).  My question was to make sure you're okay with seeing regular TW 
markup in the editor and have the system output something else entirely 
(which, when it is displayed in VIEW mode looks entirely different again).  
I guess I didn't phrase the question properly.

Perhaps I should explain my system?  I hope you're running Windows...

I use a combination of AutoHotKey (AHK) and TW macros to produce markup.  I 
find it extraordinarily useful for oft repeated phrases which occur a lot 
(when authoring) and should always look the same.  So, for example, in TW, 
I define a single macro for each main character.  <> and <>, 
for example.  Then, in AHK I define another macro which *triggers* the TW 
macro reference as output -- I make sure that the AHK macro is as short as 
possible, made up of one or two or at most three characters unlikely to 
occur "naturally" -- using a hyphen at the start or end can help.

While I can't "see" exactly what it is you're trying to achieve (again, I 
don't know screenwriting lingo), I'm now convinced the combination of TW ~ 
AHK is the way to trigger anything you want to "magically appear" in the 
editor with one or two keystrokes.

So, final example, here's my section divider in TW:

\define break() 

And here is the AHK macro that triggers it:

:*:brk::   <>

In TW, I type brk and out pops a call to <> which, as you can see 
will end up with a P element, a BR element and so on. 

Now, just in case I haven't explained my system good enough for you, let me 
say it another way...

AHK doesn't care how long or complex its output is.  With a suitably 
short/obscure key combo, you can output as much TW-wiki syntax as you like, 
identically, a thousand times over, with ease.

Any questions?  You know where I am :)

AHK Link:  https://autohotkey.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/d27dda66-e1c3-4e10-b293-c71f19e6e7c1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [tw] Query: Markup Parsers

[codacodercodacoder]

Thanks Jan.  That's very helpful.

Okay, next question...

In principle, are you happy with using references to TW macros in the input 
text?  For example:

<>

Which would generate the following in the output (i.e. when viewed in TW)

PETER

NOTE:  I said "in principle" and "using references".  I'm not proposing 
that have to *type* them like that in the editor.  Also, don't get hung up 
on my choice of macro name (<>) it could be <> - it's not 
important right now.

One step at a time... :)

On Tuesday, September 12, 2017 at 1:21:06 PM UTC-5, Jan wrote:
>
> Hi Coda,
> I hope this is what you want:
>
>
> InputText:
>
> !Peter and Bob are doing some Action
> {{Peter}}Now I say something. 
> Single Linebreaks are //okay//.
> {{AnotherNamelaterreplacedbyBob}} And here I answer.
> > Here the spaces schould be displayed
>
> OutputText:
>
> *Peter and Bob are doing some Action*
>
> PETER
> Now I say something. 
> Single Linebreaks are *okay*.
>
> BOB 
> And here I answer.
>  Here the spaces schould be displayed
>
>
> I hope this demonstration is okay.
> Basically this is what I want. 
>
>
> Thanks for your help
> Jan
>
>
>
>
>
>
>
>
>
> Am 12.09.2017 um 16:43 schrieb codacoder...@outlook.com :
>
> Thanks Jan.
>
> It would be better if you present this DEVOID of JARGON.  I don't know 
> (nor do I want to learn) screenwriting.  Take what you've written here, and 
> present it like this:
>
> I want to write something like this in the TW editor:
>
> INPUT TEXT HERE
>
> I want it to render (wikify) to something like this:
>
> OUTPUT TEXT HERE
>
> That way I can see what you are trying to achieve without getting bogged 
> down in a bunch of terminology which, frankly, might be irrelevant.
>
> Hope that makes sense.
>
> It's possible my idea may work for you guys.  It's also possible it 
> won't.  But I need something representative to test.  Okay?
>
>
>
> On Tuesday, September 12, 2017 at 9:01:17 AM UTC-5, Jan wrote: 
>>
>> Hi Coda.
>> My concept for formating is quite simple
>> I built a tool which is transclusions for the rolenames, which are 
>> automatically inserted by Alain Dutech Comptext-Plugin.
>> For simplicity I would use headings for the action, and the 
>> Tiddler-Ttitle (or an Alias inserted by the Alias-Plugin) for the 
>> scene-title.
>>
>> Thus:
>>
>> *Peter and Bob are doing some Action*
>>
>> PETER
>> Now I say something. 
>>
>> BOB 
>> And here I answer.
>>
>> Would look like that in Editmode:
>>
>> !Peter and Bob are doing some Action
>> {{Peter}}Now I say something. 
>> {{AnotherNamelaterreplacedbyBob}} And here I answer.
>>
>> The issue of indent rolenames can be handled by using -Elements which 
>> should give a
>> :Forced negative indent Line.
>>
>> My use for the replacePragma would the following to avoid breaking the 
>> list by forgetting the preceding blank line:
>>
>> \replace /\n!/\n\n!/
>> \replace /\n:/\n\n:/
>> \replace /\n{{/\n\n:{{/
>> \replace /}}/}} /
>>
>> Thanks for your help!
>> Jan
>>
>>
>>
>>
>>
>>
>>
>>
>> Am 12.09.2017 um 14:46 schrieb codacoder...@outlook.com:
>>
>> Hi Joshua
>>
>> Let me ask a question (apologies if this is answered somewhere above but 
>> since this thread and its "parent" thread are long, I wanted to ask it and 
>> get a straight answer) ...
>>
>> What does the text look like that you wish to enter into a tiddler in 
>> EDIT mode?
>>
>> Second Question...
>>
>> What does the text look like that TW will render assuming you have your 
>> ideal magical tool?
>>
>> Please, keep regexes, javascript et al out of this - keep it simple.
>>
>> Coda
>> -- 
>> 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 https://groups.google.com/group/tiddlywiki.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/tiddlywiki/28cfb2f3-483f-446e-acbb-3a3b86dfbd7e%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+...@googlegroups.com .
> To post to this group, send email to tiddl...@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/d0e976f6-d5e9-4a08-a4fa-d2563cc02396%40googlegroups.com
>  
> 
> .
> For more options, visit 

Re: [tw] Query: Markup Parsers

[codacodercodacoder]

Thanks Jan.

It would be better if you present this DEVOID of JARGON.  I don't know (nor 
do I want to learn) screenwriting.  Take what you've written here, and 
present it like this:

I want to write something like this in the TW editor:

INPUT TEXT HERE

I want it to render (wikify) to something like this:

OUTPUT TEXT HERE

That way I can see what you are trying to achieve without getting bogged 
down in a bunch of terminology which, frankly, might be irrelevant.

Hope that makes sense.

It's possible my idea may work for you guys.  It's also possible it won't.  
But I need something representative to test.  Okay?



On Tuesday, September 12, 2017 at 9:01:17 AM UTC-5, Jan wrote:
>
> Hi Coda.
> My concept for formating is quite simple
> I built a tool which is transclusions for the rolenames, which are 
> automatically inserted by Alain Dutech Comptext-Plugin.
> For simplicity I would use headings for the action, and the Tiddler-Ttitle 
> (or an Alias inserted by the Alias-Plugin) for the scene-title.
>
> Thus:
>
> *Peter and Bob are doing some Action*
>
> PETER
> Now I say something. 
>
> BOB 
> And here I answer.
>
> Would look like that in Editmode:
>
> [Title]
> !Peter and Bob are doing some Action
> {{Peter}}Now I say something. 
> {{AnotherNamelaterreplacedbyBob}} And here I answer.
>
> The issue of indent rolenames can be handled by using -Elements which 
> should give a
> :Forced negative indent Line.
>
> My use for the replacePragma would the following to avoid breaking the 
> list by forgetting the preceding blank line:
>
> \replace /\n!/\n\n!/
> \replace /\n:/\n\n:/
> \replace /\n{{/\n\n:{{/
> \replace /}}/}} /
>
> Thanks for your help!
> Jan
>
>
>
>
>
>
>
>
> Am 12.09.2017 um 14:46 schrieb codacoder...@outlook.com :
>
> Hi Joshua
>
> Let me ask a question (apologies if this is answered somewhere above but 
> since this thread and its "parent" thread are long, I wanted to ask it and 
> get a straight answer) ...
>
> What does the text look like that you wish to enter into a tiddler in EDIT 
> mode?
>
> Second Question...
>
> What does the text look like that TW will render assuming you have your 
> ideal magical tool?
>
> Please, keep regexes, javascript et al out of this - keep it simple.
>
> Coda
> -- 
> 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 https://groups.google.com/group/tiddlywiki.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/tiddlywiki/28cfb2f3-483f-446e-acbb-3a3b86dfbd7e%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/d0e976f6-d5e9-4a08-a4fa-d2563cc02396%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [tw] Query: Markup Parsers

[codacodercodacoder]

Well, cool, but I don't need an exhaustive presentation of every possible 
combination...  Give me some examples, just a few.

I have an idea that something I'm already doing *could* be of benefit to 
you.  So gimme something to test... okay?



On Tuesday, September 12, 2017 at 8:39:19 AM UTC-5, @TiddlyTweeter wrote:
>
> Ciao Coda
>
> Very encouraging to have your interest!!
>
> Good questions.
>
> Give me a couple of days so I don't burden you with a half-baked-ostrich.
>
> Briefly: Input in EDIT is plain text. Output is rendered HTML after 
> scavenged by Regex. But I need get the examples working better before I 
> show you. On the RegEx side I know what I'm doing (for a change :).
>
> Very best wishes
> Josiah
>
>
>
> On Tuesday, 12 September 2017 14:46:14 UTC+2, codacoder...@outlook.com 
> wrote:
>>
>> Hi Joshua
>>
>> Let me ask a question (apologies if this is answered somewhere above but 
>> since this thread and its "parent" thread are long, I wanted to ask it and 
>> get a straight answer) ...
>>
>> What does the text look like that you wish to enter into a tiddler in 
>> EDIT mode?
>>
>> Second Question...
>>
>> What does the text look like that TW will render assuming you have your 
>> ideal magical tool?
>>
>> Please, keep regexes, javascript et al out of this - keep it simple.
>>
>> Coda
>>
>

-- 
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/6531faff-7fea-47d6-8d88-91b9ae19c6c8%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [tw] Query: Markup Parsers

[codacodercodacoder]

Hi Joshua

Let me ask a question (apologies if this is answered somewhere above but 
since this thread and its "parent" thread are long, I wanted to ask it and 
get a straight answer) ...

What does the text look like that you wish to enter into a tiddler in EDIT 
mode?

Second Question...

What does the text look like that TW will render assuming you have your 
ideal magical tool?

Please, keep regexes, javascript et al out of this - keep it simple.

Coda

-- 
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/28cfb2f3-483f-446e-acbb-3a3b86dfbd7e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[tw] Re: How append "-foo" to a field?

[codacodercodacoder]

Couldn't you store an exclusions list somewhere and always add it to the 
filter?  It starts empty... then has (in this example) -foo added.


On Saturday, September 9, 2017 at 8:02:26 AM UTC-5, Mat wrote:
>
> For the Batch Manipulator , I 
> need a button to append foo and [[frotz gronk]] "negatively" to an 
> existing field value so it looks like this
>
> foo bar [[frotz gronk]] -foo -[[frotz gronk]]
>
> If this is then input for a filter, the result in "bar" only. But I need 
> the above statement to exist visibly/statically in a field.
>
> I assume I should use listops but fail to get that "negative append". 
> Here's the code:
>
>
> \define negative(...)
> <$button>
> Remove
> <$action-listops $tiddler="mylist"  $subfilter="???" />
> 
> \end
>
> <$edit-text tiddler=mylist tag=input/>
>
> <>
>
>
> The actual use for it in Batch Manipulator is to have a button next to 
> each listed tiddler so that individual titles can be excluded from the 
> batch manipulation.
>
> Thank you in advance! 
>
> <:-)
>

-- 
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/06da77de-47af-47e4-9f21-dd62aab55077%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [tw] Parse PDF into tiddlers

[codacodercodacoder]

On Wednesday, September 6, 2017 at 2:16:36 PM UTC-5, tib...@sunyit.edu 
wrote:
>
> I found a tool that can convert a PDF textbook to epub, with minimal 
> loss/corruption. Do we have an epub import tool lying around? I think Steve 
> Schneider did something with epub in the spring.
>
>
epub is a zip file.  If you unzip an epub file it will show you (among 
other things) its raw html content. 

-- 
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/fef19342-116a-43c6-8603-8bf6769db6cb%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[tw] Re: Make a borderless table

[codacodercodacoder]

On Wednesday, September 6, 2017 at 10:11:52 AM UTC-5, Vayu Asura wrote:
>
> maybe it has to do with some surrounding tags.
>
>
Something might be messing with it, but since the css border property is 
not inherited, it's unlikely.

Is it possible you have another css setting somewhere?  The "cascade" might 
be throwing you off.

Take a look in DevTools Inspector -- what does that show?

Open your Tiddler that has the table element in VIEW mode (not edit mode), 
right-click on the table element, choose the "Inspect" option.  You could 
then send a screen capture here for us to take a look.


-- 
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/281ea5a2-7fa0-40c8-9865-e4d4521ec9a6%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[tw] Re: Make a borderless table

[codacodercodacoder]

On Tuesday, September 5, 2017 at 2:16:13 PM UTC-5, Vayu Asura wrote:
>
>
> when invoked with  it keeps the 
> outermost border of the table
>
>
I see no border using Eric's code.  I checked the css and looked in 
DevTools inspector.  Apart from TW's row styling being applied to the 
wikitext version, they're identical with respect to borders. 

-- 
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/1822bd28-5f5f-4dc8-9cf8-37017e5a7e17%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[tw] Re: Make a borderless table

[codacodercodacoder]

On Tuesday, September 5, 2017 at 1:27:03 PM UTC-5, Vayu Asura wrote:
>
> I want a specific table to be bordeless
>
> The syntax for wiki tables allows that style string in the top. 
>
> However I couldn't either find a proper style in the default stylesheet to 
> get the invisible border or make my own:
>
> tagged `$:/tags/Stylesheet`
>
> .no-border {
> border: 0px;
> }
>
> and the table I want to make borderless in another tiddler:
>
> |.no-border|k
> |myfield|myvalue|
>
> Dev-tools show 
>

 
Remove the dot from the class:


> 
>



-- 
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/95adef48-19da-48ca-90e7-727e74fdf1f0%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[tw] Re: [video] HowTo Save TiddlyWiki wihh every browser using IIS and WebDAV

[codacodercodacoder]

Very comprehensive.  Thanks Mario.

I'll be doing this on Win7 shortly and will post back the results.

On Friday, September 1, 2017 at 10:03:50 AM UTC-5, PMario wrote:
>
> Hi folks,
>
> Inspired by Lost Admin's "[TW5] WebDav Saver Observations" [1]. I did 
> create 3 short videos, that describe, how to save TiddlyWiki using the MS 
> Internet Information Service (IIS) and the WebDAV plugin. 
>
>  - Playlist: How to Save TiddlyWiki with ISS and WebDAV 
>  
>
> The videos use Windows 10 Pro, so depending on your OS, the dialogs may be 
> slightly different, but the concept should be the same. 
>
> It should also work with *Windows Vista, 7, 8.x and 10*. as described here 
> . 
> Home editions should work too!
>
> Feedback is very welcome!
>
> have fun!
> mario
>
> [1] https://groups.google.com/forum/#!topic/tiddlywiki/8HB0R_ADYac
>

-- 
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/2a5f9221-8af7-452a-8641-b6b1241ac400%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [tw] Re: Query: Markup Parsers

[codacodercodacoder]

Hi Mark

Yes, agreed, but only where you want to print a set of tiddlers -- like the 
story river.  If, on the other hand, you use a macro/tiddler to "stream" 
the participating tiddlers into one long chunk (the "output" tiddler), you 
could then apply the css to the elements in the output.

I haven't tried it myself, but it principle it should work, I think.


On Thursday, August 31, 2017 at 2:44:07 PM UTC-5, Mark S. wrote:
>
>
>
> Page breaks are controllable in theory using CSS: 
>> https://www.w3schools.com/cssref/pr_print_pageba.asp – hope this helps 
>> for your tests Josiah! 
>>
>>
> Yes, but how would you use this in practice? You'd have to do a preview 
> print. Then, based on the print, insert MANUALLY any pagebreaks. Then 
> repeat to make sure things still paginate. Then repeat again. Imagine doing 
> that with a 50 page document, and then having to repeat every time there 
> was a change to the script.
>
> Mark 
>

-- 
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/130f1490-7dba-4299-9788-c6a3228a232c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[tw] Re: Plugins Group?

[codacodercodacoder]

On Sunday, August 27, 2017 at 9:03:57 AM UTC-5, @TiddlyTweeter wrote:
>
> Caro, my only concern about a separate group is* whether it gets used*.
>

Of course, mine too.  Proactive encouragement in its early days, I think...
 

> It has the advantage that you can set it up as you want 
>

yep
 

> & make sure it works as you want. 
>

Key point.  And make the header crystal clear as to its purpose.
 

> In any case, you could revert to here if it didn't work because you are 
> talking about the same kind of system. 
>

I have no problem with plugin discussion remaining here or in the correct 
thread on the plugin group.  It's the *topics* I'm looking to condense (in 
the new group) to mitigate the search fiasco.
 

> Periodic cross-posting could alert people it exists.
>

Precisely.  And should probably to be encouraged (at least, in the early 
days).
 

>
> Interesting to see what it might lead to--filling in what is missing here.
>

Yep.

-- 
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/fd0faf16-dc62-4a72-89f2-ac1337da3967%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[tw] Re: Plugins Group?

[codacodercodacoder]

On Sunday, August 27, 2017 at 7:41:47 AM UTC-5, @TiddlyTweeter wrote:
>
> Coming back to your original post. Several practical comments ...
>
> 1 - Despite Google being the great search engine--on Google Groups its 
> Neandertal. Basically it does NOT work. If anyone is assuming that 
> prefixing a post with "Query:" would bring up ONLY such prefixed posts they 
> are mistaken. Its UNWORKABLE unless you are an expert in search. THIS is 
> important to grasp. In my own attempts to find my own posts later I 
> included the word "Houston" in a post. Even THAT doesn't bring up the exact 
> match.
>

100% agree.  Search results are vague at best.
 

> 2 - IMO the way ahead, *given we are lumbered with Google Groups*, is PINNED 
> threads. Everything else enters the swamp quickly. NO NEWBIE would ever 
> search for what they have no idea exists somewhere. *For PINNING you 
> would need Jeremy Ruston to agree its looking useful* to activate it.
>
> 3 - WHAT PINNED threads would help BOTH us and new users?
>
>- NEW HERE? - Basic notes for Newbies about (a) what TW is; (b) how to 
>use the group to learn more. Overall, helping them hang in here.
>
>
>- SHOWCASE - Links to good TW that show what it does.
>
>
>- KIT - Links to Plugins, Bundles & Macros that help you get things 
>done. IMO this needs to be curated.
>
>
Agree with your reasoning, but don't agree with pinning as a solution.  
Pinning was my first thought, too.  But it doesn't scale, and that's why I 
chose a separate group, forcibly maintained to contain ONLY announcements.

We're on the same page regarding regarding the reasoning (I knew we would 
be), but we differ on efficacy of the proposed solutions.

With plugins (et al) numbering in the tens, perhaps... maybe... but a 
hundred?  more?  No thanks - that would be one ugly chat/help group.  It 
might destroy what this group is good for.

-- 
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/0e8a16c0-3cff-4bc3-a2a5-6b4599e0cdff%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[tw] Re: Plugins Group?

[codacodercodacoder]

On Saturday, August 26, 2017 at 11:43:12 PM UTC-5, TonyM wrote:
>
>
> I am not sure what you mean by a Goolag group ...
>

https://www.spreadshirt.com/goolag-A59998b22f6c60d694f086552


-- 
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/0fb18746-7f1e-4083-8327-8a53ac63a586%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[tw] Re: Help With the Strex Macro

[codacodercodacoder]

That's a pretty nifty use of the ::before pseudo element.  Love it.

On Saturday, August 26, 2017 at 4:32:50 PM UTC-5, Stephan Hradek wrote:
>
> As there was a small typo in the CSS and I wanted to experiment with a 
> macro, please see below a macro-version.
>
> CSS:
> span.strex:before {
> content:"\00a0...\00a0";
> background-color: lightgray;
> border: 1px solid black;
> }
> span.strex > span {
> display: none;
> }
>
> span.strex:hover:before {
> content:"";
> border: none;
> }
> span.strex:hover span {
> display:inline;
> }
>
> Macro + usage
>
> \define strex(text) $text$
>
> The ''TextStretch'' macro is a great tool < of hypertext">> to keep the message short. Your readers can discover more 
> details easily.
>
>
>
>
>

-- 
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/44cb26a8-25f9-4569-8377-1ced3bb3a627%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[tw] Re: Plugins Group?

[codacodercodacoder]

On Saturday, August 26, 2017 at 1:51:56 PM UTC-5, Mark S. wrote:
>
> Maybe the problem is the "wiki" part of the name. People looking for 
> alternatives to a product know to look up something like "program like 
> lotus 123". But most people don't need or want an alternative to a "wiki". 
> The people who do want an alternative to existing wikis (and we know who 
> you are) already know where to look.
>
>
+1 Mark.  See also my reply to Mat.

If it were up to me, I'd lose the name Tiddlywiki (sorry if that offends, 
Jeremy).  But I'd keep the TW monica.  Nobody (new) would care what it 
means.  But the investment in "TW" is *not* something I'd want to lose 
(again, if it was left to me).


-- 
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/cf1df89d-a321-4eb3-bf05-d9ba711566b9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[tw] Re: Plugins Group?

[codacodercodacoder]

On Saturday, August 26, 2017 at 4:35:35 PM UTC-5, Mat wrote:
>
> Mark S. wrote:
>>
>> Maybe the problem is the "wiki" part of the name. [..] 
>>
> ... 
>
> So is TW really a Wiki? Or a personal information manager?
>>
> ...
>> Maybe rebranding ...
>>
>
>
> Topic is drifting but, that aside, I agree.  
>

Me too.  But it speaks to the problem even if it is tangential 
(sub)thread.  If TW were to suddenly "take off", due to a name-change or 
something else, we'd certainly need something better than we have for 
managing "what we have".  The disparate solutions out there are many, 
difficult to find, some well maintained, others less so.  A plugins group, 
I believe, would solve that problem.

 

> Wikipedia is probably the *only* contact most people have had with a wiki 
> - at least *as far as they know*. 
>

Great point.  TW is far and away "better than a wiki" and if Joe newbie 
thinks "oh, it's one of those things... ugly as sh1t" then that's a lost 
opportunity.
 

>  But that type of pure "articles" wiki is of course not what TW is about. 
> Plus the editing is pretty awful in Wikipedia (and thus, presumably, 
> MediaWiki). So... who the heck is looking for that when they want an, um... 
> whatever it is they want?
>
>
*whatever it is they want*  -- precisely my point earlier about searching.  
I know what I *want* to solve, but little idea of what to search for.  
Gimme a group I can just *read*.
 

> I'm reminded of an attempt I made at identifying software categories of 
> possible relevance for TW 
> . ...as if this 
> thread isn't drifting off topic already.
>
>
It's complete valid, Mat.  Like I said, were we to solve *that*, my 
plugins/bundles group will be a *must* have, IMO.

Coda

-- 
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/90798c96-f368-428a-8b4d-d4b329d247f2%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[tw] Re: Plugins Group?

[codacodercodacoder]

On Friday, August 25, 2017 at 8:13:21 PM UTC-5, TonyM wrote:
>
> All,
>
> Why not promote Posts in the current groups whose titles are prefixes 
> [announcement]  or [Plugin] ?
>
> It is easy to search a group for such strings, 
>

It's easy to search, agreed.  But the results from what you're suggesting 
are unsuccessful at worst, vague at best.  People don't use consistent 
phrasing to make announcements (nor would I expect them to).  Just to be 
sure, I checked:  There are instances of "Announcing", "Presenting" and 
(most vague) "Plugin" (which could be talk about the plugin, not an 
announcement).

In addition, part of the problem is not knowing how to search for something 
that solves  - you don't know in advance 
*what* text might hit the plugin on the nose.  My idea has this covered -- 
ask a question here in the chat group, and one of us suggests a 
plugin/bundle/whatever in the plugin group.

 

> and most of the plugins I know about were found in this group, 
>

me too. But, key point:  

*where are the plugins you DON'T know about?*To be sure to know about all 
of them, it requires 


   - either staying in touch with the group (at least weekly, if not more 
   often) but I don't expect most "average" users would be willing to do that, 
   or...
   - searching this group, which, as I've intimated, is too hit-and-miss

 
My idea is a separate group.  When Joe newbie shows up here and asks "Is 
there a way to do X", someone here posts a link to the relevant 
announcement thread on the plugin group.  *That* is easy.  Once there, they 
can search for more/other plugins or just read the posts. *That* is easy, 
too -- very possibly thinking "wow, this is cool - so organised too!"  At 
least, that's my hope.


so we need to maintain access to the history. If you find a plugin in the 
> current groups you may be able to create a new post [plugin] plugin name 
> function with a link to a previous post.
>
> If we can build an index (using search) within the group to plugin 
> references then we can at least find them, and when we decide on a 
> repository, registry or library of plugins we can harvest the details from 
> the group to start.
>
>
While that would work, I think that represents more work.  Maintenance is a 
thankless task most likely to suffer from entropy. The path of least 
resistance is best.  I'm not sure my idea is the best path, yet -- that 
remains to be seen. 
 

> I am prepared to build and host such a registry but it must openly allow 
> plugin authors and enthusiasts to add and edit it with us all chipping in. 
> It also must take account of the existing helpful repositories or plugin 
> sets documented by those who have already put some effort into this. This 
> means it naturally needs to be a tiddlywiki itself in my view.
>
>
That's admirable.  Really.  However, as much as I dislike goolag groups, it 
is and is likely to remain, "always around".  Again, path of least 
resistance...

Thanks for the input, it's very valuable.  At the very least, it helps me 
consolidate my thinking.
 
Coda

-- 
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/77b16416-2d37-4a08-b073-066c90a6e587%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[tw] Re: Plugins Group?

[codacodercodacoder]

+2 :)

On Friday, August 25, 2017 at 11:26:43 AM UTC-5, Mark S. wrote:
>
> Yes. A forum just for announcements esp. re plugins , kits, or bundles 
> (since not all good things come in plugins) is a good idea to tweak the 
> signal-to-noise ratio. 
>
> On Friday, August 25, 2017 at 9:06:10 AM UTC-7, codacoder...@outlook.com 
> wrote:
>>
>> +1
>>
>> Thanks, Mark.  You just consolidated my thoughts better than I could.  
>> That last para is killer, (assuming you mean go with something like my 
>> original post up top?).
>>
>>
>>
>> On Friday, August 25, 2017 at 10:45:58 AM UTC-5, Mark S. wrote:
>>>
>>> About the Google forums, I know I may be in the minority, but I don't 
>>> think the current arrangement is so bad. That may be partially because 
>>> whenever I find something interesting, I clip it and save it, usually in 
>>> TiddlyWiki. Then, whenever someone else comes along that has a similar 
>>> question or interest, I can look up the information and thread.
>>>
>>> If you look around, you can find lots of open source projects that have 
>>> their own website, but they are dead as the proverbial door nail. This is 
>>> probably because over the long haul it was just too much effort to keep the 
>>> site current and active. If those sites have an active component, it's 
>>> usually the forum, which is usually a link to another site, such as the 
>>> Google or Yahoo forums, or a mail list.
>>>
>>> Mark
>>>
>>>
>>>
>>>

-- 
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/eb472e36-3d31-452d-bdf8-cc89bc421203%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[tw] Re: Plugins Group?

[codacodercodacoder]

I can't overtly disagree with any of that - the evidence is right before 
our eyes (even if the actual data might prove hard to amass and interpret).

So, do YOU think a plugins group might serve us and new users better?  I'm 
thinking also that Mark's approach would work a little easier if not very 
much better with a one-stop-shop to target...

Mark said

...because whenever I find something interesting, I clip it and save it, 
> usually in TiddlyWiki. Then, whenever someone else comes along that has a 
> similar question or interest, I can look up the information and thread.
>




On Friday, August 25, 2017 at 11:28:13 AM UTC-5, @TiddlyTweeter wrote:
>
> codacoder...@outlook.com wrote:
>>
>> Originally, I was having *very* similar thoughts.  Then I realised it 
>> needs to be (essentially) "free" - $$$ becomes a barrier to entry for a lot 
>> of people, which, depending on the topic, includes me.
>>
>
> Ciao on this codacoder ...
>
> I want to add that the ACTIVIST userbase for TW is VERY small relative to 
> other projects of equal maturity. What's  interesting is, despite that, its 
> vibrant, evolves and works. BUT most every attempt to "scale-out" at the 
> moment hits barriers. NOT of will. But of hours. Of not enough people.
>
> A DOWNSIDE is also that because of the locked-in-state on Google that 
> commits you to forever wading in a history-fogged swamp (better, your 
> "goolag"---you only cope via PERSONAL memory) I think its VERY tough for 
> newbies to find their feet without a clear history. That becomes a bit of a 
> Catch-22. I am sure there are readers who never write. Look & flee.
>
> So PART of this, for me, is about WHO are we losing? And HOW to appear 
> more inviting.
>
> Best wishes
> Josiah
>
>
>

-- 
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/7035c678-abaf-4d65-b26e-671f52354744%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[tw] Re: Plugins Group?

[codacodercodacoder]

+1

Thanks, Mark.  You just consolidated my thoughts better than I could.  That 
last para is killer, (assuming you mean go with something like my original 
post up top?).



On Friday, August 25, 2017 at 10:45:58 AM UTC-5, Mark S. wrote:
>
> About the Google forums, I know I may be in the minority, but I don't 
> think the current arrangement is so bad. That may be partially because 
> whenever I find something interesting, I clip it and save it, usually in 
> TiddlyWiki. Then, whenever someone else comes along that has a similar 
> question or interest, I can look up the information and thread.
>
> If you look around, you can find lots of open source projects that have 
> their own website, but they are dead as the proverbial door nail. This is 
> probably because over the long haul it was just too much effort to keep the 
> site current and active. If those sites have an active component, it's 
> usually the forum, which is usually a link to another site, such as the 
> Google or Yahoo forums, or a mail list.
>
> Mark
>
>
>
>

-- 
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/cde9d7a9-5bf2-4755-bbe3-b4d6abbb7fab%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[tw] Re: Plugins Group?

[codacodercodacoder]

Originally, I was having *very* similar thoughts.  Then I realised it needs 
to be (essentially) "free" - $$$ becomes a barrier to entry for a lot of 
people, which, depending on the topic, includes me.

It is an intriguing idea, nonetheless.  But, as Mat said, the proposed 
approach is a "good interim solution" - I don't want to lose sight of that, 
initially.  It's best, I think, to get something working better than the 
status quo that solves the numero uno problem - how the hell do I find 
something that solves my immediate problem.  A one-top-shop for plugins 
(with GOOD explanations in the announcements) might just solve that.


On Friday, August 25, 2017 at 10:02:05 AM UTC-5, Lost Admin wrote:
>
> OR, and I'm just spit-balling here, we could all donate $1 (or £1) a month 
> to fund a dedicated Tiddlywiki server with forums, plugin library, 
> source-code repository, individual wiki sites, and regular video tutorials 
> posted by the "staff". 
>
> Hmm, that might take more along the lines of $10 (or £10) a month. Never 
> mind. ;-)
>
> On Friday, August 25, 2017 at 10:46:50 AM UTC-4, Mark S. wrote:
>>
>> Probably there should be a rule that the actual announcement should have 
>> [ANN] at the start of the first line. Maybe a rule that people can either 
>> post an announcement or comment on an existing announcements, but not make 
>> non-announcement first-posts.
>>
>> I could probably volunteer. Let me know.
>>
>> Mark
>>
>> On Friday, August 25, 2017 at 7:24:16 AM UTC-7, Mat wrote:
>>>
>>> That could be a good interim solution (...no more than 25 years) and I'm 
>>> surprised nobody has suggested it before.
>>>
>>> But if it is strictly for announcements, that would mean one has to post 
>>> in *both *groups or people cannot come with input. And, presumably 
>>> again in both groups for update notices. Not a huge problem but it is an 
>>> extra step that is not obvious. On the other hand, if announcements only 
>>> then anyone can make the announcement, not necessarily the plugin creator. 
>>> Should the creator not be happy with someone elses announcement of his 
>>> plugin, then I guess he can request deletion in that thread and post a new 
>>> announcement instead.
>>>
>>> Any volunteering moderators? It would be best with several moderators 
>>> because of the ebb-and-flow type participation people have (including 
>>> myself). So, if a few more are volunteers then I can be one.
>>>
>>> <:-)
>>>
>>

-- 
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/5d499dbf-930a-401f-b8d0-a95190c86528%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[tw] Re: Plugins Group?

[codacodercodacoder]

On Friday, August 25, 2017 at 9:24:16 AM UTC-5, Mat wrote:
>
> That could be a good interim solution (...no more than 25 years) and I'm 
> surprised nobody has suggested it before.
>
> But if it is strictly for announcements, that would mean one has to post 
> in *both *groups or people cannot come with input.
>

Not quite what I meant Mat.  When you announce BatchManipulator, for 
example, I can post feedback to that thread.  So I *should* have said, 
announcement *topics* only.  Better?

 

> And, presumably again in both groups for update notices.
>

As the topic OP, you get to update the original, or, you post again (new 
topic) making the new post a new announcement which seeds higher in the 
list anyway.

 

> Not a huge problem but it is an extra step that is not obvious. On the 
> other hand, if announcements only then anyone can make the announcement, 
> not necessarily the plugin creator. Should the creator not be happy with 
> someone elses announcement of his plugin, then I guess he can request 
> deletion in that thread and post a new announcement instead.
>

There are those (hopefully) rare occurrences, yes.  But what we have right 
now is inferior, IMO.  A plugins group should aid search and, if that's not 
the case in some circumstances, you can just read all the headlines in one 
place.

Thinking further, authors *could* say "Post feedback and questions to the 
main discussion group, please!"  But I personally think it would be better 
in the plugin group, possibly.

 

>
> Any volunteering moderators? It would be best with several moderators 
> because of the ebb-and-flow type participation people have (including 
> myself). So, if a few more are volunteers then I can be one.
>

Yeah, me too - guilty as charged, guv.

;)

-- 
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/cb6a642a-d611-4e1a-93e9-3739416a15be%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[tw] Plugins Group?

[codacodercodacoder]

I know there has been talk of moving away from goolag -- sorry, google -- 
groups but it's what we have and it's where new users come and other folks 
are.  

I also know that many have opined the lack of a one-stop-shop/curated list 
of plugins (TiddlyTweeter being the most vociferous/ardent on the topic, I 
think -- he's right, IMO, too).

That said...

Why is there not (or is there?) a goolag group for Plugins?  
TiddlywikiPlugins?

If it was *strictly* for plugin announcements (all other kinds of msgs are 
forcibly removed), wouldn't that be better than the status quo?  If it was 
very strict, then, hopefully, searching would improve, also.

Thoughts?

Coda

-- 
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/fe39f83b-3ce9-4981-a733-eebc5abbdae6%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[tw] Re: Query: Are Regular Expressions Regular in TW?

[codacodercodacoder]

Thomas!!!

Awesome (not a word a throw around like confetti).  Just AWESOME!!!

I recall we talked about textstretch when it was "new", quite some time 
ago. I ended up going my own route with *bk-ann* (and a couple of others, 
like *bk-note* and *bk-problem* which use different colors and are 
"transient" since they're like TODOs).  But *extract* was the missing 
"elephant in the room" ;)  

I'm so pleased and thankful!  Thank you!

Coda

On Thursday, August 24, 2017 at 5:31:31 PM UTC-5, codacoder...@outlook.com 
wrote:
>
> Excellent Thomas - thank you.  I'll grab it later (or tomorrow, more 
> likely) and let you know how it goes.
>
> Danke!
>
> On Thursday, August 24, 2017 at 4:50:23 PM UTC-5, Thomas Elmiger wrote:
>>
>> Hi Codacoder 
>>
>> Something like synopsis extraction exists in an experiment I developed 
>> some time ago: 
>>
>>
>> https://tid.li/tw5/numbers.html#Chapter%201:%5B%5BChapter%201%5D%5D%20Footnotes
>>  
>>
>> Here I extract footnotes from a text using my extract macro based on 
>> existing TW5 technology. 
>>
>> https://tid.li/tw5/hacks.html#Extract%20Macro 
>>
>> Problem: It does not work for transcluded sections … that would be the 
>> same with a regexp solution. 
>>
>> Cheers, 
>> Thomas
>
>

-- 
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/f5902f55-8b50-4325-9c16-895f6936f078%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[tw] Re: Query: Are Regular Expressions Regular in TW?

[codacodercodacoder]

Excellent Thomas - thank you.  I'll grab it later (or tomorrow, more 
likely) and let you know how it goes.

Danke!

On Thursday, August 24, 2017 at 4:50:23 PM UTC-5, Thomas Elmiger wrote:
>
> Hi Codacoder 
>
> Something like synopsis extraction exists in an experiment I developed 
> some time ago: 
>
>
> https://tid.li/tw5/numbers.html#Chapter%201:%5B%5BChapter%201%5D%5D%20Footnotes
>  
>
> Here I extract footnotes from a text using my extract macro based on 
> existing TW5 technology. 
>
> https://tid.li/tw5/hacks.html#Extract%20Macro 
>
> Problem: It does not work for transcluded sections … that would be the 
> same with a regexp solution. 
>
> Cheers, 
> Thomas

-- 
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/61357f0c-a162-4628-943b-1e44cb44610d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[tw] Re: Query: Are Regular Expressions Regular in TW?

[codacodercodacoder]

Hi Mark

On Thursday, August 24, 2017 at 2:59:52 PM UTC-5, Mark S. wrote:
>
> Regular expressions in javascript can return sub-groups for non-global 
> expression searches. It might be possible to implement this in regexps, if 
> someone can think of a good use-case. Mostly, instead of "removeprefix" and 
> "removesuffix", you could grab whatever text you wanted from the middle of 
> a tiddler title or filter stream. You could even make a single title (or 
> field) split into multiple filter outputs. Once again -- what would be a 
> use-case?
>
>
Okay, I'm trying my best to not make this long-winded.  My use case is as 
follows...

I'm writing a documentation TW for an app.  It has logical *chapters* and 
*sections* within chapters called *chapsec*s (*1 chapsec* = 1 tiddler).  
I'm trying to take the approach that the system will be a good authoring 
tool for... well, authoring anything "book-like".

Within *chapsec* tiddlers, I use annotations macros to annotate the text. 
Annotations can be enabled (made visible) and disabled (made invisible) 
globally. The annotation macro is named *bk-ann*. 

What I'd like to do is, for each *chapsec*, find all *bk-ann*s in the text 
field and list their content.  An example might be...

  <>

and

  <>


As you can see, this text could become a synopsis of each *chapsec* if I 
could figure out a way to re-use the annotation text.  The output would 
render:

*  Section 1-010 synopsis:*




*Explain the use of the Tiddlywiki's macro systemExplain the scope 
rules of Tiddlywiki macros*
I'm guessing we're not quite there yet?  But hoping I'm wrong :)


-- 
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/a54ee59d-f453-4c8f-9a77-51d1d9dc263c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[tw] Re: Query: Are Regular Expressions Regular in TW?

[codacodercodacoder]

On Wednesday, August 23, 2017 at 1:19:35 PM UTC-5, @TiddlyTweeter wrote:
>
>
> I am aware there is a regexp operator, but can it RETURN its exact match 
> for processing, or is it what it looks like: a match with something IN a 
> field it adds to a list to display but then the match itself is discarded?
>
>
Timely.  I was looking to do this yesterday.  No, I didn't find a solution 
either.  What's happening is, TW5 is using the regexp op to filter 
in-or-out the tiddler during that run, not the matched string.  Be a nice 
addition to have at some point, though.

*rexpexps* -- matches the specified string of text and //returns it//.

However, I'm not sure there would be enough people voting it up - but I 
could be wrong.


-- 
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/e3d9135c-069b-4d99-beca-02b065a4b257%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [tw] Re: Prevent filter from filtering out copies?

[codacodercodacoder]

On Tuesday, August 22, 2017 at 4:32:22 PM UTC-5, Jeremy Ruston wrote:
>
>
> It would be useful to find the earlier discussions. ...
>
>
This?  https://github.com/Jermolene/TiddlyWiki5/issues/2123 

-- 
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/16f80721-0a9f-42c7-87fa-e823bfd0851e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[tw] Re: Prevent filter from filtering out copies?

[codacodercodacoder]

On Tuesday, August 22, 2017 at 3:05:13 PM UTC-5, Mark S. wrote:
>
> Wouldn't a prefilter=none option turn off de-duplication for the entire 
> filter?
>


Likely.  Why I also mentioned some kind of pragma approach or even a new 
kind of list widget.  But without knowing at what level of granularity it's 
best to address/apply the solution, it's hard to say what might be the 
better approach (from a core perspective, I mean).

Jeremy, before posting a wish on github,..  attr? filterop? new freelist 
widget? something else?  does any of this grab you?


-- 
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/45312428-eae3-4ae8-9bb0-5ed26a45c393%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[tw] Re: Prevent filter from filtering out copies?

[codacodercodacoder]

Methinks there's mileage in this... kudos!

On Tuesday, August 22, 2017 at 2:05:31 PM UTC-5, Mark S. wrote:
>
> It's pretty easy to make a "cheater" filter "enlist2" that splits at space 
> boundaries.  Then code like this:
>
> <$list filter="[enlist2[2 2 3 2]]" >
> <$view field="title"/> - 
> 
>
>  Will enumerate like 2 - 2 - 3 - 2 - 
>
> It's a cheater because it doesn't do a full parse for titles like [[My 
> Real Tiddler]]. That would take longer (have to look at existing parse 
> code) but this might be good enough to test if it gets you towards your 
> goal. Backup, of course ;-)
>
> HTH
> Mark
>
>
>
>
>

-- 
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/313f5d26-9675-4f34-bb29-49993a135b6b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [tw] Re: Prevent filter from filtering out copies?

[codacodercodacoder]

On Tuesday, August 22, 2017 at 11:02:21 AM UTC-5, Jeremy Ruston wrote:
>
> All of the logic around uniquifying lists actually happens within the 
> filter mechanism, ...
>
>
Which I believe is also in use when managing data entered via a field 
called list - right?


-- 
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/0154945b-5a8d-4cec-9203-fc2b810432e6%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[tw] Re: Prevent filter from filtering out copies?

[codacodercodacoder]

On Tuesday, August 22, 2017 at 10:29:43 AM UTC-5, Mat wrote:

>
> BTW, I'm surprised we (all of us) have not had this discussion before. At 
> least not as far as I know.
>
>
Like I thought I said in my first response (but didn't, I must have edited 
out), when I first stumbled on the problem, I thought it was me being 
stupid.  Then when I learnt more about TW5, the penny started to drop.  
Then (long time after) you posted this, I copied into TW.com and played 
around and... *it all came rushing back! *:)  :(

So yeah... now we're having the discussion.  We probably need some kind of 
ungoverned, unsupervised list op/widget/tool/thingy (tm).

:)


-- 
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/5202ebad-e616-4b04-892e-b2934f63f410%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[tw] Re: Prevent filter from filtering out copies?

[codacodercodacoder]

On Tuesday, August 22, 2017 at 9:40:39 AM UTC-5, Mat wrote:
>
> codacoder wrote:
>>
>> The "everything is a tiddler" philosophy doesn't always sit well with 
>> dominantly-appended lists (either list fields or the list widget itself)[1].
>>
>
> As far as I can tell, this is not a matter of the "everything is a tiddler 
> philosophy" because the arguments are deliberately omitted in the filter. 
> ...which, btw and IMO, is particularly inappropriate where the user 
> explicitly puts those arguments in the filter. 
>
>
>
Precisely *why* I said it doesn't sit well (expanded upon in my footnote 1 
about recipes) . In your case, it's *user data* input, in mine it was my 
*programmer 
supplied* input.  Again, *sometimes* treating everything as a tiddler 
(which is what the core is doing, even with your inputs 1, 2, 3, 2, 2, 2, 2 
-- they're being treated as tiddlers (or references to tiddlers) which if 
listed twice (eg in the UI) would be a problem.  So "I totally get" why it 
behaves this way, it's just that in this use case, it's a footgun.

I don't know if I'm making it any clearer or not - perhaps Jeremy can step 
in and help us out (and, perhaps, correct my thinking?).

 

>   The dominant append approach is vital for UI construction, for obvious 
>> reasons, 
>>
>
> Hm, I feel like I'm nit-picking semantics but does "dominent append 
> approach" necessarily mean it also filters out stuff?
>
>
yep.  It has to (for UI construction reasons).
 

>  
>
>> <$list filter="blah" prefilter=none> ...
>>
>
> Yeah. If I recall, Jeremy said the listwidget is very complex and he is 
> not in favour of introducing further complexity for it. I might have it 
> mixed up with some other widget. Still, it is such a central widget so IMO 
> it must either be very powerful or we need multiple niche widgets.
>
>
That does not surprise me at all.  Maybe a new widget - $freelist ?
 

> Thanks for your input, codacoder :-)
>

np. ;) 

 

-- 
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/736e75a5-1545-453e-a384-0a5b49092f60%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[tw] Re: Prevent filter from filtering out copies?

[codacodercodacoder]

I feel your pain, Mat.  I've been here before.  The "everything is a 
tiddler" philosophy doesn't always sit well with dominantly-appended lists 
(either list fields or the list widget itself)[1].  The dominant append 
approach is vital for UI construction, for obvious reasons, but if the list 
widget had some kind of pragma attribute that controlled its behavior in 
this regard, then we could stop using the pre-restricted *list* field 
(which is also a problem) and use any other field(s) for lists where the 
content is under user (our) control.  Something like...

<$list filter="blah" prefilter=none> ...

[1] There are many use cases where a given list might need to contain 
duplicates.  Recipes, for example, where discrete methods might be stored 
as individual tiddlers.  If you try to store *those *in a list, you can't 
build a Recipe tiddler that needs to repeat a given method (say) three 
times.


On Tuesday, August 22, 2017 at 5:14:53 AM UTC-5, Mat wrote:
>
> Richard, I appreciate your attempts. And yeah, first though "must be easy 
> - even trivial"... but no.
>
> I think your proposal still could not handle *arbitrary* lists where the 
> items (in this case numbers) are not predictable so it wouldn't be possible 
> to make separate fields for them... at least not without using a listwidget 
> and a solution that can handle repeated items... which is the problem to 
> begin with ...
>
> Futher ideas appreciated!
>
> <:-)
>
>

-- 
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/0b834031-000e-4eac-b4ed-df9fb8818817%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[tw] Re: Tobias' Delete All Tiddlers By Filter

[codacodercodacoder]

Cool.  Thanks Mario!

On Thursday, August 10, 2017 at 11:50:39 AM UTC-5, PMario wrote:
>
> Hi,
> Try this one: https://wikilabs.github.io/editions/remove-states/ ... it 
> shouldn't be that destructive, because you can see, what you delete. 
> -m
>

-- 
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/09c7b2b2-622c-417b-8d22-efcd4763cc43%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[tw] Re: Presenting: GRAPHS - pies, bars, scatter and whatever turns you on

[codacodercodacoder]

I forgot about this little gem!  Especially HashStr -- excellent solution 
to the problem of having to supply/think of IDs per use.  I'm using HashStr 
already :)

On Thursday, August 10, 2017 at 8:05:03 AM UTC-5, Thomas Elmiger wrote:
>
> Hi Mat
>
> Great to hear that my rpn plugin is of use to others!
>
> Your remaining problem with chart slices >50% reminds me of a similar 
> problem you had with CircleBar … please feel free to steal back from my 
> variant on https://tid.li/tw5/styles.html in case you want to integrate 
> something similar in Graphs!
>
> Happy graphing,
> Thomas
>
> Am Dienstag, 8. August 2017 23:31:51 UTC+2 schrieb Mat:
>>
>> Update (still beta)
>>
>> Main change is not noticeable but the previous calculation plugin has 
>> been exchanged for fellow @Thomas Elmigers rpn plugin! (Thank you Thomas!) 
>> It simplified the code in a few places thanks to the "built in" 
>> wikification of the result and I'm doing some experiments with its 
>> randomization feature.
>>
>> Hopefully fellow Danielo will also be happy with the Pie demo now. The 
>> special slice serving should hopefully show up better on small screens.
>>
>> Thanks to everyone for the kind words.
>>
>> <:-)
>>
>

-- 
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/0b4e0dae-4ed7-4eb8-a594-b04c30855e6b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[tw] Tobias' Delete All Tiddlers By Filter

[codacodercodacoder]

I stumbled across this 
and 
thought it would make a good starting point for a JS macro.  Having tried 
it on a couple of TWs (where I had a ton of archaic temp/state tiddlers I 
wanted to remove) it seems there is a very destructive bug in there 
somewhere -- it destroys the TW (and since the wikis have passwords, they 
will no longer decrypt).  The size of one of the wikis went from ~6.5KB to 
103KB.  Ouch.

Here is Tobias' original code:

var filter = "tag[FOO]"; 
filter = "[all[tiddlers]!prefix[$]" + subfilter + "]";
var tids = $tw.wiki.filterTiddlers(filter, null); 
if(confirm('Delete all ' + tids.length + '?\n\n' + tids)){
  for(var t=0; t

[tw] Re: The Beauty of Data Dictionary Tiddlers

[codacodercodacoder]

On Wednesday, August 2, 2017 at 3:18:35 PM UTC-5, Mark S. wrote:
>
> It seems like this is more of a request for someone to make an interface 
> for data tiddlers.
> ...
>

That's pretty sweet :)  Shame the select options are sorted (removing 
sort[] from the filter didn't help - which is weird).

BTW, you have a stray (broken)  tag in there - oops.

-- 
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/e09f2f8e-d274-4cb7-bdf9-adfa9e9bed6f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[tw] Re: vaguely off-topic: are there any "prove you are a person" solutions other than captcha?

[codacodercodacoder]

On Wednesday, August 2, 2017 at 3:28:41 PM UTC-5, Thomas Elmiger wrote:
>
> I know of a technique where you have a field that is hidden via CSS. 
> People don’t put anything in it as it is invisible. Robots don’t realize it 
> is hidden and fill in a value … 
>

Precious :) 

-- 
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/5f853945-5dcb-49b0-a164-c2b6f5468647%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[tw] Re: [NoteSelf] Bug fixes and (cool) new features

[codacodercodacoder]

"NoteSelf - The Missing Manual - Part II"

Seriously... excellent, Lost Admin.  Thank you!



On Thursday, July 20, 2017 at 8:06:46 AM UTC-5, Lost Admin wrote:
>
>
>
> On Thursday, July 20, 2017 at 3:19:06 AM UTC-4, @TiddlyTweeter wrote:
>>
>> Tutti, Small comments ...
>>
>> *NoteSelf is currently largely MAGIC*.  
>>
>> Meaning *its actually quite difficult to conceptually grasp* what it is 
>> & how it works. In time it will get clearer. That is NOT a criticism. Its 
>> an observation on a technology that just works a different way.
>>
>> I am still myself unclear on several points ...
>>
>> (1) CORS settings in Cloudant and what the addressing they ask you for 
>> there does? Do you need a "stub" at the address?
>>
>
> I had to look this one up too, when I first ran into it. CORS stands for 
> Cross-Origin Resource Sharing. One needs to understand a bit about how the 
> web works. A website serves up an HTML document. That HTML document has 
> links to other things that are used to render the final page. These things 
> include pictures and stylesheets and javascript. If they all come from the 
> same http server (host and domain) they they are from the "same origin". If 
> they get them from some other http server, then they are cross-origin.
>
> For example, if you create a website that makes use of jquery you can 
> choose to host a copy of the jquery library on your own website 
> (same-origin) or to have your html page get it from the public google 
> repository (cross-origin).
>
> CORS came into existence to stop thing like linking images from other 
> people's websites without permission among other things like CouchDB.
>
> The reason you need to set-up CORS is that CouchDB was designed from the 
> start to be a database server that is accessible directly over the 
> Internet. As such they made a few unusual design decisions (from a database 
> perspective). Whereas a traditional database (like say MySQL) uses an SQL 
> interface with a somewhat simple network protocol, CouchDB chose to use 
> HTTP as the interface and network protocol.
>
> So, we use CORS (a relatively recent extension of HTTP) as a security 
> setting in CouchDB. It tells the CouchDB server what other websites are 
> allowed to send code to a browser that can be used to make calls to the 
> CouchDB server.
>
>
>> (2) Still unclear in the difference between the DOWNLOAD version and the 
>> ONLINE version.
>>
>
> This also takes a bit to grasp. In the simplest way I can think of, 
> NoteSelf takes TiddlyWiki (a single-file document) and turns it into the 
> client side of a client-server application. Danielo's genius was in 
> figuring out how to make it do that so elegantly.
>
> One of Danielo's plugin(s) is like a modification to the TiddlyWiki json 
> export function. Except instead of exporting to a file for download, it 
> exports to a CouchDB server through a REST call. And it does it 
> automatically every time you save a tiddler.
>  
>
>>
>> (3) Am very hazy about COOKIE setting when using the ONLINE version.
>>
>
> This is a requirement from CouchDB. The CouchDB server uses http cookie 
> based authentication. When you log-in to the CouchDB, it sets a cookie. 
> That cookie is used as a token to say "hey this guy logged in".
>
> Since CouchDB supports people writing their own login forms, Danielo did 
> that. That is what the login popup does when you click the OFFLINE button 
> and it turns into a cloud. It sends your credentials to the CouchDB server, 
> and if login succeeds, you get cookie.
>  
>
>>
>> (4) I get the impression that some tiddlers -- like PLUGINS for instance 
>> -- can be "hard-coded" into the DOWNLOAD version, rather than be in the 
>> browser database. *In other words, there is a "sort-of" TW that exists 
>> outside the PouchDB for the download version?*
>>
>
> The DOWNLOAD version is the traditional TW way.
>
> There is exactly a TW that exists outside of PouchDB. But if you do it 
> entirely the NoteSelf way, that TW is always the empty.html version. 
> Everything else comes from CouchDB.
>
> PouchDB is like CouchDB, except it is written entirely in javascript, only 
> usable by the browser that runs it, and uses the Browser's local storage 
> (specifically the recently introduced IndexDB local storage). 
>
>
>> (5) I'm unclear IF and HOW one can convert a DOWNLOAD version into a 
>> synchronising one with a cloud database version.
>>
>
> Danielo's PouchDB plugin holds all the magic. It has the PouchDB and the 
> interface for CouchDB. If you put it into any existing TW5, you have turned 
> it into a NoteSelf (I think that's all it takes). You then, of course, need 
> to set-up the cloud database server stuff.
>
> This next bit I'm not completely clear on (I haven't dug into Danielo's 
> code enough yet). I believe that once you have the PouchDB plugins added 
> and you've added the settings to communicate with the CouchDB, it works 
> pretty much like a new TiddlyWiki saver. When you save a 

[tw] Re: [NoteSelf] Bug fixes and (cool) new features

[codacodercodacoder]

Wow.  "NoteSelf - The Missing Manual"


On Wednesday, July 19, 2017 at 8:05:27 AM UTC-5, Lost Admin wrote:
>
> I might regret this, but I'm going to attempt to help you JWHoneycutt.
>
> NoteSelf does not work like TiddlyWiki even though it is built on top of 
> TiddlyWiki.
>
> NoteSelf stores all of your content online on a server. The server in 
> question uses the Apache CouchDB server software. There is a service 
> provider called Cloudant that hosts that software and offers use of it for 
> free provided you stay below some limits they have defined. Because of the 
> nature of NoteSelf, it is almost impossible for a single person using a 
> single NoteSelf to actually go over those limits.
>
> The NoteSelf html file that Danielo says to download is a collection of 
> HTML, CSS, and Javascript that implements a front-end to the CouchDB server 
> and provides the same functionality as TiddlyWiki. But, unlike TiddlyWiki, 
> it doesn't save your changes locally. Instead it saves them to the server. 
> To speed things up for you NoteSelf also stores a copy in the browser's 
> local data (more on this later). This also means that if you use your 
> NoteSelf when you are unable to connect to the CouchDB server, your changes 
> get stored in the browser and sync to the server the next time that browser 
> on that computer is used and connected to the server.
>
> In order for the browser to be connected to the server, you need to log-in 
> to the server. That is where the cloud/offline button comes in. If it shows 
> offline, then you need to log-in. If it shows the cloud, then you are 
> logged in and it will try to sync.
>
>
> Here is a picture of a sample NoteSelf that is successfully connected to 
> the CouchDB server, note the cloud icon:
>
>
> 
> Here is a chopped up screenshot of the browser locally stored data that 
> Noteself created and uses: You can see yours (on Chrome) :
> 1 in the Chrome Menu (3 vertical dots) -> More Tools -> Developer Tools
> 2 open Noteself
> 3 in the developer tools window (mine is on the right side of the browser 
> window) choose Application (menu near the top of the developer tools area)
>
>
> 
>
> And, the same information also exists on the CouchDB server. Here is a cut 
> of a screenshot of the couchdb management interface showing the database 
> that stores the data for the above NoteSelf:'
>
>
> 
> finally, the actual contents of the Start Tiddler in CouchDB:
>
>
> 
>
> Did that help or make things even more confusing?
>
>
> On Saturday, June 24, 2017 at 6:40:13 PM UTC-4, Danielo Rodríguez wrote:
>>
>> Hello everyone,
>>
>> New weekend and new version of NoteSelf. I'm proud to announce that we 
>> have fixed several bugs and also added a couple of modest features.
>>
>> Bug Fixes
>>
>>- There was a bug preventing any kind of tiddler exportation, instead 
>>a JSON representation of the database was exported. This bug has been 
>> fixed 
>>and now you can export any tiddler in any format as usual
>>- Now it is possible to properly save the wiki in html.
>>   -  Previously, because the synchronous nature of the saving 
>>   mechanism (and the async one of the syncer module) you may end with 
>>   incomplete files (not containing all your tiddlers). 
>>   - Now when you save the wiki we make sure that all the tiddlers 
>>   are loaded
>>   - Please note that for some reason this only works on the offline 
>>   version. *IT WILL NOT WORK ON THE ONLINE ONE*
>>- Palettes and palette tiddler have been added to the list of startup 
>>tiddlers. No more colors suddenly appearing after startup!! 
>>
>> New features
>>
>>
>>- Better login flow. Now if the browser has a cookie it will be 
>>picked automatically. This will save you unnecessary login typing!! 
>>   - This is also way more secure than the basic authentication used 
>>   before.
>>- Synchronization changes are (almost) reflected instantly. Check it 
>>out this small GIFbetween two browsers simulating this situation
>>   - This feature is somewhat experimental, and may benefit from 
>>   performance improvements in the future
>>
>>
>> 
>>
>>
>>
>>- From the previous GIF you may have noticed that different tiddlers 
>>were 

[tw] Re: Background image works via stylesheet but not style block

[codacodercodacoder]

That's weird.  Testing in Firefox, using devtools, if you disable/enable 
the background-image rule (or the class), the image appears.

I even tried a transclusion

{{Using styleblock attempt 1}}

Nope.

Strange!



On Tuesday, July 18, 2017 at 9:32:31 AM UTC-5, Mat wrote:
>
> I succeed in getting this to work
>
> background-image: url(<>);
>
> when it is in a separate *stylesheet*. But when it is in a local *style 
> block* it doesn't work. 
>
> Demo 
>
> Help appreciated!
>
> <:-)
>

-- 
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/e39b78ab-ea3b-4f7f-9d02-437646c96f75%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[tw] Re: [NoteSelf] Bug fixes and (cool) new features

[codacodercodacoder]

Me too. Can't use it locally at all.

On Monday, July 17, 2017 at 9:17:46 AM UTC-5, Alfonso Arciniega wrote:
>
> JWHoneycutt,
>
> You are not alone. The "Internal JavaScript Error" happened to me every 
> time when using NoteSelf offline. Now I see it also happens online too...
>
> Best,
>
> Alfonso
>
> On Friday, July 14, 2017 at 12:35:04 PM UTC-6, JWHoneycutt wrote:
>>
>> How far I've gotten:
>>
>>- 7) I drag this newly renamed file to the FireFox 
>>
>> <#80700af6-8125-4ef7-a626-5292fe9de514@googlegroups.com_1fbbd287-77e4-4def-ad8a-792938eb6e7a@googlegroups.com_FireFox>
>>  address 
>>bar and it fails to load with a big red error box: "Internal 
>>JavaScript 
>>
>> <#80700af6-8125-4ef7-a626-5292fe9de514@googlegroups.com_1fbbd287-77e4-4def-ad8a-792938eb6e7a@googlegroups.com_JavaScript>
>>  Error, 
>>Well, this is embarrassing. It is recommended that you restart 
>>TiddlyWiki 
>>
>> <#80700af6-8125-4ef7-a626-5292fe9de514@googlegroups.com_1fbbd287-77e4-4def-ad8a-792938eb6e7a@googlegroups.com_TiddlyWiki>
>>  by 
>>refreshing your browser -ReferenceError 
>>
>> <#80700af6-8125-4ef7-a626-5292fe9de514@googlegroups.com_1fbbd287-77e4-4def-ad8a-792938eb6e7a@googlegroups.com_ReferenceError>:
>>  
>>$TPouch is not defined" - since refreshing the address bar doesn't help - 
>> I 
>>close the tab in FireFox 
>>
>> <#80700af6-8125-4ef7-a626-5292fe9de514@googlegroups.com_1fbbd287-77e4-4def-ad8a-792938eb6e7a@googlegroups.com_FireFox>
>>- 9) If (happens half the time) TiddlyWiki 
>>
>> <#80700af6-8125-4ef7-a626-5292fe9de514@googlegroups.com_1fbbd287-77e4-4def-ad8a-792938eb6e7a@googlegroups.com_TiddlyWiki>
>>  Desktop 
>>does load it - when I try to open it - it gives the same "Internal 
>>JavaScript 
>>
>> <#80700af6-8125-4ef7-a626-5292fe9de514@googlegroups.com_1fbbd287-77e4-4def-ad8a-792938eb6e7a@googlegroups.com_JavaScript>
>>  Error" 
>>in a big red box.
>>- 10) Same error if I just try to double click JWH_NoteSelf.html in 
>>the dropbox folder (set to default open with FireFox 
>>
>> <#80700af6-8125-4ef7-a626-5292fe9de514@googlegroups.com_1fbbd287-77e4-4def-ad8a-792938eb6e7a@googlegroups.com_FireFox>
>>)
>>
>>

-- 
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/053b9adb-037e-4697-87f6-c7e5298af397%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[tw] Re: Command line from TiddlyWiki

[codacodercodacoder]

On Monday, July 17, 2017 at 9:25:00 AM UTC-5, @TiddlyTweeter wrote:
>
> i would trust it from a friend.
>
>
A word of advice: 

That is precisely the attack vector to which you (we) are most vulnerable.  
You cannot know or ascertain whether your friends are or have been exposed 
to malware *designed* to use that precise attack vector.  Attackers and 
their code *rely* on us behaving that way.

Be safe. Take extreme care with ALL sources - even more care with friends.



 

> PMario wrote
>
>> I'm pretty sure, that you don't want to run arbitrary scripts form 
>> untrusted sources on your computer
>>
>

-- 
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/ca7ed5f1-f7bd-4b2c-adb8-f2fdd0075668%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[tw] Re: Permalinks/Permaview in TiddlyDesktop

[codacodercodacoder]

I did, but I can't find it.  I took the following approach...

The HOME button clears out the story and replaces it with the content of 
$:/DefaultTiddlers . What 
I did was, stash the current content somewhere else (for later), then 
copied another list of tiddlers (retrieved from MyOtherListOfTiddlers, for 
example) into $:/DefaultTiddlers 
. Later, I restored the 
content of $:/DefaultTiddlers 
 from the stash.

Something like that.

HTH

On Sunday, June 25, 2017 at 12:32:16 PM UTC-5, ste...@gmail.com wrote:
>
>
> On Sunday, June 25, 2017 at 5:55:29 PM UTC+2, ste...@gmail.com wrote:
>>
>>
>> Example: In the browser, I often open a list of tiddlers I need for a 
>> particular project. Then, I create a persistent URL for this view with the 
>> "permaview" button, which I bookmark. This way, I can always access the 
>> same list of tiddlers through the bookmark.
>>
>
> I guess it's possible to copy the contents of $:/StoryList to another 
> tiddler and then copy it back via <$action-setfield> later on. Has anybody 
> already done something like this?
>
> ~~Stef
>

-- 
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/c735c16c-2946-459b-a530-234bc763eac5%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[tw] Re: Any CSS HORIZONTAL layouts yet for TW?

[codacodercodacoder]

Hi Joshua

No, doubtful.

That sample looks as though you want/need a CSS-grid layout. Or maybe CSS 
flex (steeper learning curve). Or you could use CSS display:table et al. 
Worst case (not recommended) HTML tables.

All my code is doing is using CSS columns on suitably tagged tiddlers. When 
one of those tiddlers is displayed, its content is "split" into columns of 
the specified width/height. It does NOT display multiple tiddlers in some 
kind of host tiddler (ie not a transclusion mechanism).

HTH

On Saturday, June 17, 2017 at 4:38:20 PM UTC-5, @TiddlyTweeter wrote:
>
> It may help with this layout issue I have... ???
>
>
>
> Each of those is a Tiddler. I really need to better understand modern CSS 
> flows.
>
> Josiah
>
> On Friday, 16 June 2017 17:21:44 UTC+2, codacoder...@outlook.com wrote:
>>
>> Yes, I've sort-of done it.
>>
>> In my case, certain tiddlers format the tiddler body as a set of css 
>> columns with fixed height(s).  Those tiddlers then scroll horizontally.
>>
>> So, not a "storyriver", but certainly a horizontal presentation of the 
>> content with no vertical scroll at all.
>>
>> .tc-tagged-bk-layout .tc-tiddler-body {
>>   max-height:770px;
>>   overflow-x:auto;
>>   width: 100%;
>>   position: relative;
>>  
>>   columns:3; -moz-columns:3; -webkit-columns:3;
>>   column-gap:3em; -moz-column-gap:3em; -webkit-column-gap:3em;
>>   column-rule: 3px dotted #ddd; -moz-column-rule: 3px dotted #ddd; 
>> -webkit-column-rule: 3px dotted #ddd;
>> }
>>
>>
>>

-- 
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/c1552211-dc56-4e3f-af45-339fd5810c1d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[tw] Re: Any CSS HORIZONTAL layouts yet for TW?

[codacodercodacoder]

Yes, I've sort-of done it.

In my case, certain tiddlers format the tiddler body ( ) as a set of css 
columns with fixed height(s).  Those tiddlers then scroll horizontally.

So, not a "storyriver", but certainly a horizontal presentation of the 
content with no vertical scroll at all.

.tc-tagged-bk-layout .tc-tiddler-body {
  max-height:770px;
  overflow-x:auto;
  width: 100%;
  position: relative;
 
  columns:3; -moz-columns:3; -webkit-columns:3;
  column-gap:3em; -moz-column-gap:3em; -webkit-column-gap:3em;
  column-rule: 3px dotted #ddd; -moz-column-rule: 3px dotted #ddd; 
-webkit-column-rule: 3px dotted #ddd;
}




On Thursday, June 15, 2017 at 3:02:11 PM UTC-5, @TiddlyTweeter wrote:
>
> Rather than go with the vertical newspaper metaphor of a column, I wonder 
> if anyone has a horizontal Story River.
>
> It could be good for presenting some kinds of Tiddlers. Particularly good 
> for graphics.
>
> Anyone had a shot at it yet?
>
> Best wishes
> Josiah
>
>
>  
>

-- 
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/2d63875a-6ea5-4bac-b015-e1dff03a5a67%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [tw] Re: [TW5] Presenting the Details Widget

[codacodercodacoder]

Demo works fine here

FF 53.0.3

Win7


On Wednesday, June 14, 2017 at 1:19:40 PM UTC-5, Thomas Elmiger wrote:
>
> Hi Mark
>
> On my Mac it works in FF, but I can confirm that there is an issue with FF 
> for Win7. 
> Not sure when I will find time for this. 
>
> :(
> Thomas
>
> 2017-06-14 18:00 GMT+02:00 'Mark S.' via TiddlyWiki <
> tiddl...@googlegroups.com >:
>
>> Am I the only one having trouble making this work in FF?  I can see what 
>> it's supposed to look like on Chrome, but on my FF the open and close 
>> doesn't work. 
>>
>> Thanks,
>> Mark
>>
>> FF 47.0.2
>> Windows 7 Home Prem
>>
>> On Sunday, January 22, 2017 at 8:45:18 AM UTC-8, Thomas Elmiger wrote:
>>>
>>> Hi all – here comes my first attempt to build a widget: 
>>>
>>> The details widget creates an HTML 5  section including a 
>>> . Users can click on the summary to open and close a block 
>>> containing more details. The parameter *open* defines the initial state 
>>> at load time.
>>>
>>> See documentation here: http://tid.li/tw5/hacks.html#DetailsWidget
>>>
>>> I just finished a first version and the documentation and I am very 
>>> happy with it. BUT: I am not a javascript expert! So *do yourself a 
>>> favour and save a backup* of your wiki first. 
>>>
>>> Let me know if it works for you!
>>>
>>> All the best, 
>>> Thomas
>>>
>> -- 
>> 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/sRUVnlIaT3E/unsubscribe.
>> To unsubscribe from this group and all its topics, send an email to 
>> tiddlywiki+...@googlegroups.com .
>> To post to this group, send email to tiddl...@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/a015ff42-be28-4a6a-87f3-0e3a235765c2%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/56843861-703b-4ec1-9ad8-9de48e01885b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[tw] Re: how to share with people (without them being able to edit)

[codacodercodacoder]

I completely missed that. Thanks for highlighting it, Ton. That's really 
useful.

On Tuesday, June 13, 2017 at 3:08:23 AM UTC-5, Ton Gerner wrote:
>
> Hi Stef,
>
> Nice concise solution.
> Never thought constructions (with tags="-...">) of
>
> <$action-setfield $tiddler="$:/core/ui/SideBar/More" 
> tags="-$:/tags/SideBar"/>
>
> were possible.
>
> Thanks for sharing.
>
> Cheers,
>
> Ton
>
>

-- 
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/01e5f19d-522e-4fe3-a593-ac4f2112f9cc%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [tw] TiddlyWiki European Meetup 2017 Details

[codacodercodacoder]

On Monday, June 12, 2017 at 5:24:57 AM UTC-5, Mat wrote:
>
> @Saq Imtiaz for his totally unexpected "drop in" in the form of a double 
>> story river mini-presentation video (was this published anywhere?). I 
>> really hope we'll see more of you again! :-D
>>
>
>
That sounds VERY intriguing! 

 

-- 
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/39b3f086-b32a-487d-9f22-a256663f137e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[tw] Re: [INTRO] Tiddler Bundle Plugin

[codacodercodacoder]

On Monday, June 12, 2017 at 6:02:23 AM UTC-5, PMario wrote:
>
>
>  So it shows a text: "Existing tiddler will be overwritten!" now.
>
> -m
>

Excellent approach. Thanks! 

-- 
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/42b0be53-da30-4f27-aa16-ed560811d49a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[tw] Re: [INTRO] Tiddler Bundle Plugin

[codacodercodacoder]

On Saturday, June 10, 2017 at 7:24:13 PM UTC-5, PMario wrote:
>
> On Friday, June 9, 2017 at 11:05:03 PM UTC+2, codacoder...@outlook.com 
> wrote:
>>
>> Hi Mario
>>
>>>  - If an imported tiddler exist, they will be renamed. So importing the 
>>> same tiddler, won't overwrite existing content. ... ( I know: There's a lot 
>>> of improvement possibilities here :)
>>>
>>
>> Are you planning a switch to turn that off? 
>>
>
> Hmmm, Now that you say it, it seems to make sense. ... Could be a first 
> step.
>
>
Great. Recall I mentioned in the other thread, I'm using Bundles to create 
something akin to an edition - I *want* to have imports overwrite all 
targets.  It's basically an "upgrade".

What I really want is a "diff", that tells me, what is new and then decide, 
> if I want to import it, or not.   
>

I'm assuming that will be a set of checkboxes? (295 in my case). That might 
be cool as long as I can have  them default to selected=overwrite, sure, 
that would be fine. Otherwise, I'll stick with the beta - it's working 
perfectly for me.

Thanks!


-- 
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/8d38a30f-4b67-4a31-8ca1-31b7ef684392%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[tw] Re: [INTRO] Tiddler Bundle Plugin

[codacodercodacoder]

Hi Mario


>  - If an imported tiddler exist, they will be renamed. So importing the 
> same tiddler, won't overwrite existing content. ... ( I know: There's a lot 
> of improvement possibilities here :)
>
>
Are you planning a switch to turn that off? 

-- 
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/6a36ef1c-b0f0-48dd-ae9b-0c49ba4c9a96%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[tw] Re: TiddlyWiki StackExchange

[codacodercodacoder]

Like any good relationship, it takes commitment.

Done.

-- 
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/7cc197b1-2471-492a-8dc8-52a427443623%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [tw] Bundling - It would help - HOW to do it reliably?

[codacodercodacoder]

This is frankly marvelous. Perfect for a situation I keep on running into 
(and perfectly documented by TiddlyTweeter).

I don't know what the formal definition of an "edition" is, but Bundles is 
certainly an ad hoc edition-creator for use between one's local TWs.

Excellent work, Mario!  Thank you!




On Monday, June 5, 2017 at 1:55:48 PM UTC-5, PMario wrote:
>
> Here is a new version: 
>
> THIS IS STILL BETA !!! use with care. I'll probably change the names again!
>
> - 2 export concepts
>- Bundle function as shown in the existing example
>- Filtered bundles. So you can use filters instead of list tiddlers by 
> name
>
>  - Config option to select position eg: 
>- SideBar or
>- MoreSideBar
>
>  - several examples for "useful" filters
>- including a preview filters in AdvancedSearch
>
>  - visible info about number of tiddlers, that will be exported 
>- eg: 3/4 ... 3 out of 4 tiddlers will be exported. ... So there may be 
> a typo .. 
>
>  - make filtered bundle settings compatible with the "AdvancedSearch: 
> Filter tab". So they will show up there too. 
>
> feedback very welcome!
>
> @Josiah ... Have a closer look at: bundle-plugins tiddler. 
>
> have fun!
> mario
>

-- 
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/1bc73bcb-04f0-4eee-8834-4cefeaebe431%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[tw] Noteself issue

[codacodercodacoder]

Been meaning to try this out for a while so I just downloaded it. It fails 
immediately with a js error.




Same happens when I go to the online version. :(

Firefox 53.0.2


-- 
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/c766aa52-c276-4f59-90fd-f239452b9102%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[tw] Re: What's the point with titles NOT as links?

[codacodercodacoder]

On Wednesday, May 17, 2017 at 12:48:57 PM UTC-5, Mark S. wrote:
>
>
> The big issue would be that nobody really seems to leverage CamelCase as 
> links (you rarely see it being used that way), and that it may confuse 
> newbies. In the 90s, it seemed like a neat idea. But I've never found that 
> I use it that much. In practice, tagging and searching are more useful.
>
>>
>>
+1 

-- 
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/7f1ff16c-ba7d-457e-aa02-0c0f1bd6e151%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[tw] Re: What's the point with titles NOT as links?

[codacodercodacoder]

I think it clear that Mat is asking about *NOT* having them as links. I see 
no strong argument for that. 

There is I guess an argument to be made for not confusing new users - but 
really, I'd make them default to being links so that dragging "just works" 
and cover it with documentation.


On Wednesday, May 17, 2017 at 7:02:01 AM UTC-5, Mat wrote:
>
> What are the arguments to NOT have titles set to be links by default - 
> other than the blue color etc (which is very easily styled to look e.g like 
> plain text) ?
>
> <:-)
>

-- 
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/717e2414-2584-40e2-b8a3-7809f53719a9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[tw] Re: simple question: why is tiddlywiki core considered a plugin?

[codacodercodacoder]

I'd say Jeremy's choice here is the ultimate in dogfooding: 
https://en.wikipedia.org/wiki/Eating_your_own_dog_food


On Friday, May 12, 2017 at 2:59:52 PM UTC-5, @TiddlyTweeter wrote:
>
> why is tiddlywiki CORE considered a plugin?
>
>

-- 
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/cd88e25b-3849-4dd9-b1f7-792e29fbce75%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[tw] Re: doesn't seem to work

[codacodercodacoder]

Watch your case:

  This works

  This does not



On Friday, May 12, 2017 at 2:55:59 PM UTC-5, Thomas Schulte wrote:
>
>  underlines  in the wiki but   tag doesn't stop underlining. What 
> can be done?
>

-- 
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/119857ff-ae7d-4d61-9de1-2fd64dd8511e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[tw] Re: Positive Assertions In One Sentence ... (aka Saying Succinctly What TW Is About ...)

[codacodercodacoder]

*Me*: It's software.

*Person*: Software? That's not saying much.

*Me*: Listen to the stress - *SOFT*ware. It's authored by someone that 
hasn't lost sight of the meaning of "soft".

*Person*: [Eyebrows slowly raising] You... you mean...

*Me*: [Smiling] Yep. Try it.


*Way, WAY too much software is like hardware these days.*

-- 
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/8821663a-719d-4b18-9edf-75ce98d740c4%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[tw] Re: This is how you can (and could) find plugins

[codacodercodacoder]

It should be a sticky post/thread at the top of this group. I'm imagining a 
*single* maintained posting, if that can be arranged (otherwise, it'll 
become too lengthy/tedious to browse/use).

-- 
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/c479f850-4b5a-4cd6-9aac-c1b47d957ba4%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[tw] Re: @ttention plugin issue

[codacodercodacoder]

To be clear, the issue only occurs when ONE tiddler contains many sources 
with identical text

@target1 my message /@
@target2 my message /@
@target3 my message /@


I can live with a rule that states "Multiple sources appearing in the same 
tiddler cannot have identical text messages"

Workaround: Add dots at the start of the message, or extra spaces *after* 
first word:

@target1 my message /@
@target2 .my message /@
@target3 ..my message /@


On Tuesday, April 25, 2017 at 10:47:00 AM UTC-5, Mat wrote:
>
> David and Codacoder, thanks for reporting.
>
> I'll see what I can do. I would think there is some algorithmic 
> best-practice for what is supposed to take place. Will do some searching.
>
> Thanks.
>
> <:-)
>
>
>
> On Saturday, April 22, 2017 at 2:03:04 PM UTC+2, codacoder...@outlook.com 
> wrote:
>>
>> Mat,
>>
>> I think I see the issue.
>>
>> <$list filter="[split:after]" variable="rest">
>>
>> The t var contains *all* the text and split doesn't know *which* occurrence 
>> of ch to split after. My tired brain isn't letting me see what to do about 
>> it though :( 
>>
>

-- 
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/ec9c9fa9-fc5c-4cfb-8eab-a0aefa06ced8%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [tw] Is Firefox Dying? Do we need to pact with The Devil for saving?

[codacodercodacoder]

This.

On Tuesday, April 25, 2017 at 9:26:24 AM UTC-5, Mark S. wrote:
>
> TW on node.js doesn't serve images. The fact that node.js can serve images 
> is totally irrelevant until someone writes a version of TW on node.js that 
> does. 
>
> The thing is, if you start having to run a server, you no longer have a 
> simple solution. In fact, you could run any of a half dozen wikis or 
> content managers which would all have true databases and virtually 
> unlimited size allowances. The charm of a single-file, no-install, 
> runs-everywhere solution would be gone.
>
> Mark
>
> On Tuesday, April 25, 2017 at 6:59:25 AM UTC-7, Arlen Beiler wrote:
>>
>> Node serves images. Chrome apps might be able to as well if done right, 
>> but never tried. Any server-type solution will be able to serve images.
>>
>> On Tue, Apr 25, 2017 at 9:49 AM, 'Mark S.' via TiddlyWiki <
>> tiddl...@googlegroups.com> wrote:
>>
>>> Much of the world spends their computing times on tablets and smart 
>>> phones. Some models can run a terminal (mine can't) if you want to spend a 
>>> lot of time fiddling with that sort of thing -- but by then you no longer 
>>> have a simple, easy to use turnkey solution. 
>>>
>>> It still doesn't address the images problem which is a non-starter for 
>>> me.
>>>
>>> -- Mark
>>>
>>> On Tuesday, April 25, 2017 at 6:43:11 AM UTC-7, Arlen Beiler wrote:

 This is true, but on windows it is very easy to run a portable version, 
 and may be on Linux as well, I'm not sure. I'm pretty sure that covers 
 most 
 of our users, though I realize it doesn't cover everyone. But isn't that 
 already a problem with TiddlyFox and TiddlyChrome?

 On Tue, Apr 25, 2017 at 9:14 AM, 'Mark S.' via TiddlyWiki <
 tiddl...@googlegroups.com> wrote:

> If TW on node.js served up images and other files, that might be 
> almost acceptable. Of course, you would still have problems when away 
> from 
> your home node.js server.
>
> Mark
>
> On Tuesday, April 25, 2017 at 4:39:49 AM UTC-7, Arlen Beiler wrote:
>>
>> If someone knew how to do it, they would have. My TiddlyChrome plugin 
>> is the easiest way that I know of for Google Chrome. One thing I have 
>> not 
>> explored is whether I can have the user select a folder and then edit 
>> any 
>> file in that folder. Other than that (which is a good option) I don't 
>> know 
>> of any way to save in Chrome. 
>>
>> However, "Never say it can't be done. Someone might actually believe 
>> you." This is so true when it comes to technology.
>>
>> Now the best option I see outside of chrome would be to run a node 
>> store.js file in a certain folder and it would serve that folder on 
>> localhost and allow saving. That would work in any browser and would 
>> work 
>> fine in a localhost or local network environment. I haven't taken the 
>> time 
>> to put that together yet, but it is very possible. It would work 
>> identical 
>> to how my current https://twcloud.github.io/tw5-dropbox/ works, 
>> possibly and could also be configured to do automatic backups.
>>
>> Those are my thoughts. 
>> -Arlen
>>
>> Never say it can't be done. Someone might actually believe you.
>>
>> On Mon, Apr 24, 2017 at 12:04 PM, @TiddlyTweeter > > wrote:
>>
>>> Firefox looks like its chosen to die for a while. 
>>>
>>> Its userbase is shrinking month by month. 
>>>
>>> Its ALREADY a minority report.  
>>>
>>> In November this year its goes over to WebExtensions. 
>>>
>>> By that time how will it differ from Chrome with market share 
>>> already?
>>>
>>> Would it be best if TiddlyWiki could have an OFFICIAL add-on to save to 
>>> at least one browser easily? The browser MOST users use?
>>>
>>> Thoughts, only 
>>> slightly 
>>> in 
>>> advance.
>>>
>>> Josiah
>>>
>>>
>>> -- 
>>> 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 https://groups.google.com/group/tiddlywiki.
>>> To view this discussion on the web visit 
>>> https://groups.google.com/d/msgid/tiddlywiki/084dd598-24fd-4a09-8d0b-288c547450fd%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 

[tw] Re: printing

[codacodercodacoder]

On Monday, April 24, 2017 at 9:41:00 AM UTC-5, @TiddlyTweeter wrote:
>
> Ciao Ton
>
> *Let us not disagree where there is none.*
>
> 1 - The point was, for me, THE QUESTION was on PRINTING a Tiddler. I 
> suggested it EASIEST via "Open In new window"
>
> 2 - In Firefox on Windows it behaves as expected. You open a new Tiddler 
> via  "Open in new window" and right click and get a Print option for it. 
> Easy and to the point. Elegant prints come out without messing about in 
> convoluted print directives.
>
>
I don't see a print option in the Firefox context menu in Windows 7 or 
Windows 10 - how did you make it appear there?

 

-- 
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/18f2f903-29a3-4512-a8cf-92b3ada01315%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[tw] Re: @ttention plugin issue

[codacodercodacoder]

Mat,

I think I see the issue.

<$list filter="[split:after]" variable="rest">

The t var contains *all* the text and split doesn't know *which* occurrence 
of ch to split after. My tired brain isn't letting me see what to do about 
it though :( 

-- 
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/c8dd721a-76ff-4358-96b7-44d245b3be53%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[tw] Re: @ttention plugin issue

[codacodercodacoder]

Actually, disregard my previous. When I renamed Mat's macros, I'd missed 
one of his calls to "loop". Now I'm seeing the same issue as Dave.

On Saturday, April 22, 2017 at 6:13:26 AM UTC-5, codacoder...@outlook.com 
wrote:
>
> I'm seeing a different problem. Only the *first* message shows up at a 
> given target.
>
> @target this appears /@
>
> @target this does not /@
>
>
> On Friday, April 21, 2017 at 5:04:12 PM UTC-5, David Gifford wrote:
>>
>> Hi Mat
>>
>> When you paste the same text twice or more in a tiddler, and push it to 
>> different tiddlers, it will appear in some of the tiddlers more than once.
>>
>> See http://giffmex.org/experiments/bible.chpkg.html#3%20John%20ESV and 
>> compare to http://giffmex.org/experiments/bible.chpkg.html#Joy
>>
>> Dave
>>
>

-- 
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/ae419843-6998-4846-91f5-16929db5e722%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[tw] Re: @ttention plugin issue

[codacodercodacoder]

I'm seeing a different problem. Only the *first* message shows up at a 
given target.

@target this appears /@

@target this does not /@


On Friday, April 21, 2017 at 5:04:12 PM UTC-5, David Gifford wrote:
>
> Hi Mat
>
> When you paste the same text twice or more in a tiddler, and push it to 
> different tiddlers, it will appear in some of the tiddlers more than once.
>
> See http://giffmex.org/experiments/bible.chpkg.html#3%20John%20ESV and 
> compare to http://giffmex.org/experiments/bible.chpkg.html#Joy
>
> Dave
>

-- 
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/060c81bb-c228-4fe6-b618-4b75472548ea%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [tw] Mat's @ttention plugin

[codacodercodacoder]

On Friday, April 21, 2017 at 5:49:03 PM UTC-5, Mark S. wrote:
>
> The complication I see is that there is no delimiter to say when the title 
> is complete.
>

The @ symbol begins the text. The /@ pair of symbols ENDS the text

@title like this./@

If the title contains spaces...

@[[title with spaces]] works like this\@


-- 
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/ecbf4e90-6779-47bb-a3ee-6fa79a4c0942%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[tw] Re: Is anybody on this group an active Genealogist?

[codacodercodacoder]

On Thursday, April 20, 2017 at 5:37:08 PM UTC-5, Richard Evans wrote:
>
> Hi,
>
> First of all I want to thank you all for replying. Though I most of you 
> seem to have jumped to the conclusion, that I am trying to replace 
> genealogical programs. I am not. In fact, I believe I have identified, a 
> gap in the market.
>
> I would direct you to the phrase I used in my initial post:
>
> "TiddlyWiki to aid in guiding, documenting and planning the research on an 
> individual."
>
> The operative word there is individual. I am considering a TiddlyWiki that 
> concentrates on a single person. 
>
>
Which is *exactly*  how my wife uses TW.  She's a genealogy nutcase, total 
addict and has... I dunno, 30? 40? TWs devoted to the research and data 
curation.  She uses Scrivener for "presentation" (having tried and given up 
trying to use it for the data/research side) and now sticks with TW for 
"everything".

I know from my own experience that managing the research is the most 
> critical area when tracing your Family Tree. The number of times I have 
> completed a piece of research, only to find I have already done it some 
> years previously and not documented the results properly. 
>

Jeez... you *sound* like her ;)

 

> Goodness knows how many times I have duplicated a research task that had a 
> negative result. I frequently find I have essential information missing 
> from important people in my tree. Or I am just confused about how best to 
> proceed on researching an individual.
>
>  A genealogist's requirements can be broken down into three components, a 
> research plan or checklist, a research log and documentation of the 
> results, positive and negative. There are various tools used by 
> genealogists to manage their research. People use Word or One Note or 
> Evernote or pen and paper. 
>

or TW :)

And census data changes all the time, where people on Ancestry.com 
transcribe old docs and (obviously) make mistakes in doing so.
 

> Personally, I think only pen and paper has the flexibility to handle all 
> three components.
>
>
My wife does a lot with pen and paper but for genealogy, she insists on TW.

Just my $0.02 by proxy :)

-- 
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/1f2f7dc9-eeb8-4fb3-8cfc-de84fc2b5654%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [tw] Mat's @ttention plugin

[codacodercodacoder]

On Thursday, April 20, 2017 at 6:31:54 PM UTC-5, Mat wrote:
>
> Glad you like it :-)
>
> I had to change it a bit - I didn't want it to work via the 
>> ViewTemplate, so I hacked off the tag, removed the last div and call the 
>> roam macro where I need it. 
>>
>
> Yeah, if I recall, the first version (cherrypicker) had a separate macro. 
> The limitation is of course that you can no longer do your "pushing" off 
> the cuff as you write and have it appear automatically wherever.
>  
>

Depends what you mean... I have a set of tiddlers that don't use the 
regular ViewTemplate and it's these tiddlers which should receive the 
pushes - the normal/standard tiddlers don't require them. Hence...

I removed the ViewTemplate tag 
removed the "cherry-area" div 
tagged the plugin as macro and renamed it
(Aside: I also renamed the macros to have "attention-" prepended)

Now I can push from anywhere into those "special" tiddlers that need it - 
works great.  And of course, if I decide later I actually *do* want them 
everywhere, I can re-add the ViewTemplate tag.

 

>
> I'd also like to hide the source-push-@ call somehow... 
>>
>
> Yes, this is definitely part of a much extended version I have in mind 
> where one should be able to assign arbitrary start and end markers that 
> control what happens to the encompassed segment. The markers would be 
> visible/hidden depending on which marker it is. For example, we should be 
> able to easily highlight text segments without the markers being visible in 
> view mode. I guess this can be called "arbitrary parser rules". 
>
> What I have in mind would be much smoother if the user could mark a text 
> and then *select* markers, perhaps via some text-completion tool. Just 
> the other day, I found Simplete  by 
> none other than Grand TWizard FND! It is not made for TW though. And there 
> is Alain Dutechs edit-comptext 
>  which is great already 
> with the @ttention plugin... but it is, as far as I know, not maintained 
> and I've found some glitches.
>
>
Wow, edit-comptext is a pretty sweet tool - (glitches: doesn't work in 
Opera/Win7 - no biggy, I use Firefox for TW).

But back to @ttention...

I'm developing an authoring tool for TW5 (I guess it would be better as an 
"edition" but I'm not ready yet).  The tools are designed to aid an author 
writing a book. Book chapters have titles like "1-010" (chapter 1, section 
010) "3-060" (chapter 3, section 060). The name of a chapter-section -- 
"Jack meets Jill" -- is stored in a subtitle field. (These are the tiddlers 
that are typically *not* viewed via the standard ViewTemplate).

In addition, I use specialized tiddlers for things like "plot", 
"character", "keystages", "location", "problems" etc. So I have 
"1-010-plot", "1-010-location", "1-010-problems" etc.

I already have the ability to add annotations/notes etc "inline" in chapter 
tiddlers -- all of which can be controlled (made visible/invisible) 
globally and individually. What I've been missing is the ability to 
*push*... that's why I jumped on @ttention. For example, if I'm working on 
plot and I'm editing "1-020-plot" and I decide "Jack" has red hair instead 
of dark brown, I can push the note to 1-010, indeed, *any/all* previous 
chapters-sections. This is *extremely* useful and so *direct* it saves a 
bunch of searching/opening/editing/saving/closing. So, yeah, thanks again!

I don't know if my use-case makes sense to you... or if it touches on any 
of the future ideas you mentioned above (confession: I didn't quite follow 
where you were going).

Regards...


-- 
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/14303d80-9cb9-42ac-9395-8c3ad7ce0c4c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[tw] Re: Random Thoughts about the new version of TW.

[codacodercodacoder]

My 2 cents...

Yes to IDs.

No to users creating them. Ever.

 They should be GUIDs.
   Not concatenated titles+dates or anything related to existing tiddler 
data. This will likely fail and scale poorly.
   They must be created "behind the scenes",  but easily discovered/usable 
by experienced users.

Linking should support both titles and GUIDs (either/or)
  Contract: GUID links are robust and must therefore work in any environment
  Contract: titles are "optimistic" and "best effort, good faith" attempts 
at succeeding. In a standalone TW, they'll be as good as they are already.

Eric's "caption" approach is equivalent to my "subtitle" approach. Works 
fine for a TW-book edition I'm developing (very slowly, not published yet). 
And it works fine in the context ("domain") I'm trying to support (no js 
required!).  My Chapters and sections have ID-like titles. My subtitles are 
stored in a subtitle field.

If you're going to TWederate (publish) a given tiddler, I can imagine a 
routine that trawls the text looking for links that do NOT carry a GUID... 
and warn against potential breakages before allowing you to proceed <- off 
the cuff brainfart ;)

Like I said, my 0.02


-- 
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/b0d24ed4-fa5a-442f-bc48-e82863c60b7a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[tw] Re: Presenting: StretchText - an alternative to links or popups

[codacodercodacoder]

nota

http://www.thefreedictionary.com/nota+bene


On Wednesday, July 13, 2016 at 11:04:36 AM UTC-5, Thomas Elmiger wrote:
>
> Thank you, Eric, for pointing this out. 
>
> How about “strex”? 
> Reminds of stretch and expand, could also stand for STRing EXpander. 
>
> (According to Google it is also used in life science as well as mobile 
> payment in Norway.) 
>
> Suggestions welcome! 
> Thomas

-- 
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/61bc0941-8cf9-4bc7-b71e-9c8cc9580fdf%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[tw] Re: Presenting: StretchText - an alternative to links or popups

[codacodercodacoder]

Thanks Thomas. Replies within..

On Tuesday, July 12, 2016 at 12:26:13 AM UTC-5, Thomas Elmiger wrote:
>
> Thanks for your feedback, Coda! 
> You are right, I will have to explain the id better … and in fact I had 
> tried to eliminate this parameter at first. But I came to the conclusion 
> that it might be a feature in some cases, while it is not a real issue in 
> most others. 


If it's a feature in some cases, make it optional (and apply a guid perhaps 
if the id is not supplied by the user).

If it's "not a real issue" for the user then it's (usually) not too 
difficult to handle it in the code, either.

Believe me, I'd *love* to use it, but the id is one param too many, for the 
reasons I described.  Let me expand on that here...

Nothing in vanilla TW5 forces me to "think" about IDs - Jeremy got this 
100% right. When moving stuff around between tiddlers (i.e. cut and paste 
wikitext/markup) I generally do not need to worry about the surrounding 
context (unless it's macro/template code, of course). But when the text 
contains IDs, I certainly will need to ensure I don't have clashes so that 
all id="5" TS blocks don't open up when the intent was one specific TS. And 
searching through a chapter/section of a book, 12,000 chars long for id 
clashes is not my idea of productive (or fun) use of my time.

The bigger a TW5 tome becomes, the review-edit-change cycle will get more 
"expensive" on the user and resistance-to-change will build due to the 
tediousness of having to manage those IDs by hand. Trust me - I know. I 
have a catalogue of my own (early TW5) mistakes in this regard which are 
now so embedded in my system, "life's too short" to fix them.

I hope that made sense?

The key benefit of Mat's solution was "speed of use" at "authoring-time". 
And whether or not he uses an id internally, it wasn't left to me to manage 
it during the scenario I mention above. (I only decided not to use it on 
cosmetic grounds... but that was a while ago, I should check it out again.)

Anyway, I hope this feedback is useful...


-- 
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/b045a1cd-4699-47c2-8593-85b6c912c3ef%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[tw] Re: Presenting: StretchText - an alternative to links or popups

[codacodercodacoder]

On Sunday, July 10, 2016 at 1:41:11 PM UTC-5, Thomas Elmiger wrote:
>
>
> Hi everyone,
>
> May I introduce my own variant of this great idea? I tried to simplify a 
> bit for my limited usecase and I gave it a stretchy appearance (tested in 
> some browsers only).
>
> The result can be found here: http://tid.li/tw5/hacks.html#TextStretch – 
> Yep, I just switched the components of the name, I hope this is not 
> confusing … 
>
> Thanks for the inspiration, Mat!
>
> Kind regards and happy stretching
> Thomas
>

It's a beautiful things Thomas. However, it would be vastly improved if the 
user did not need to supply the id. If you look at Mat's original, it did 
not need an id. That makes Mat's "better" for larger texts/TWs - managing 
ids will become a huge headache for those users working on vast 
tomes/thousands of tiddlers.

If you can manage the id internally to the macro, you'll have the killer 
stretchy-thing (tm) ;)

Coda

-- 
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/df36a9cd-d948-4062-8e35-efe0e54c6b96%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [tw] triggering action widgets

[codacodercodacoder]

Well, it's hard to say unless Neil comes back to clarify. All we have is 
his original statement:

> the contents of the select widget are buried at the grandchild level 
rather than being immediate children

which led me down the path of P tags.


On Wednesday, June 29, 2016 at 2:21:31 AM UTC-5, Jeremy Ruston wrote:
>
> Hi Codacoder
>
> You’re correct about the extraneous paragraph tags but I don’t think it’s 
> the problem here: shortly after the message below we changed the core so 
> that action widgets do not have to be an immediate child of the triggering 
> widget:
>
>
> https://github.com/Jermolene/TiddlyWiki5/commit/f9c4f6898e4e52137a6e5a87ff353839408c409b
>
> https://github.com/Jermolene/TiddlyWiki5/commit/758ba5edc2cb8bf06a60013d9ebeaaa5a3912b78
>
> Best wishes
>
> Jeremy
>
> On 28 Jun 2016, at 22:22, codacoder...@outlook.com  wrote:
>
>
>
> On Sunday, January 11, 2015 at 3:05:32 AM UTC-6, Jeremy Ruston wrote:
>>
>> >  the contents of the select widget are buried at the grandchild level 
>> rather than being immediate children
>>
>> Why is that happening? The action widgets are supposed to be the 
>> immediate children of the triggering widget. 
>>
>
> Probably because of this or similar:
>
> <$select>
>
> 1
> 2
> 3
> 
>
>
>
> which produces this (unusable) html
>
> 1
>
>
> @Neil - take care with whitespace in TW5, it's not as "insignificant" as 
> you may think.
>
> @Jeremy: I think that's a bit too fragile - perhaps the docs should make 
> people more aware. Of course, embedded whitespace pretty much anywhere else 
> in the block is fine:
>
>
> <$select>
> 1
>
>
> 2
> 3
>
>
> 
>
>
> ^ works.
>
> HTH
>
>
>
>

-- 
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/e161e1b8-2b69-49a6-88d2-b1d84baa2e56%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[tw] Re: Concatenating (Joining) Hard and Indirect text within a Filter

[codacodercodacoder]

On Tuesday, June 28, 2016 at 1:18:30 PM UTC-5, Thomas McLeod wrote:
>
> So I want to be able to search for all items tagged with String+Title. 
> Example: 
> Input: Company{{!!title}}
> Output: CompanyApple
> Where: Company is the string and Apple is the title of the tiddler
>
> Now I want to be able to do this with a filter.
> <>
>
> This just returns nothing. 
>
> I've also tried:
> <>
>
> <>
>
>
Something like this?

 \define build-fullname() $(prefix)$$(title)$

<$set name=prefix value=Company>
<$set name=title value={{!!title}}>
<$set name=fullname value=<>>
<> List:

<$list filter="[tagsort[]]">







-- 
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/da9118ce-cce0-4399-9641-a0f8ad4b47cc%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [tw] triggering action widgets

[codacodercodacoder]

On Sunday, January 11, 2015 at 3:05:32 AM UTC-6, Jeremy Ruston wrote:
>
> >  the contents of the select widget are buried at the grandchild level 
> rather than being immediate children
>
> Why is that happening? The action widgets are supposed to be the immediate 
> children of the triggering widget. 
>

Probably because of this or similar:

<$select>

1
2
3




which produces this (unusable) html

1


@Neil - take care with whitespace in TW5, it's not as "insignificant" as 
you may think.

@Jeremy: I think that's a bit too fragile - perhaps the docs should make 
people more aware. Of course, embedded whitespace pretty much anywhere else 
in the block is fine:


<$select>
1


2
3





^ works.

HTH


-- 
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/7907fffd-7c47-4424-86ab-e73dd790fb2f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.