[tw5] Question about node.js and saving

[Jim Barr]

I have a TiddlyWiki instance running under Docker using Node.js. Can the 
entire install be saved out as a single Tiddlywiki file?

And likewise, can a standalone Tiddlywiki .html file be saved as a Node.js 
install?

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 view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/ab121b9d-1399-4e71-bb34-ee14a7595080n%40googlegroups.com.

[tw5] Re: Can I reference a data tiddler using a field value?

[Jim]

Thanks all for the help and hints.  Some of the examples I couldn't get to 
work, but finally managed to do what I wanted. 

This is, at the moment, just experimenting with workflows and what's 
possible.  The under-lying ideas are separation of data from display, 
linking a tiddler to a data tiddler via an id number, and easier updating 
of data tiddler via external scripts instead of using fields which are 
embedded in a normal tiddler.  

Here is a simple demo in progress:  
https://amreus.github.io/product-demo.html

Thanks again for the comments.



-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/e41efdc0-63a4-43fc-b8cc-dc220d3137ec%40googlegroups.com.

[tw5] Remove a tag on command line?

[Jim]

Hello.

I'm using node to load, modify, and then render a html wiki.  Is it 
possible to remove a tag from a tiddler before rendering it out again?


-- 
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/6f0cb63d-e57f-4f65-8470-612623c63ddc%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[tw5] Re: [Off Topic] Why I Like OLD firefox

[Jim]

I have been using (getting used to) Firefox Multi-Account Containers 
 
which allows you to have different accounts assigned to color-coded tabs.  
It doesn't use Firefox Profiles, but the result is similar.  You can setup 
a container for each of your gmail accounts for example and have them each 
open in a tab.  Long-click the "add a tab" button to select the account the 
new tab is opened for.



On Monday, September 10, 2018 at 6:53:43 AM UTC-4, @TiddlyTweeter wrote:
>
> I'm slowly moving from FF 52 to the WebExtensions version.
>
> There are still two things very easy in the old FF I use a lot that I 
> can't find new equivalents for... 
>
> Easy ability to launch multiple profiles (ProfilistPortable add-on) ...
>
>
>
> Split in browser (TileTabs add-on) so you can drag & drop between sections 
> ...
>
>
>
> My question: Does anyone know of alternatives for WebExtensions?
>
> Any help appreciated.
>
> 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/de726461-2a60-494f-9377-5437282085dc%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[tw5] Re: Timimi plugin - released for firefox/chrome/chromium in linux/mac/windows

[Jim]

On Sunday, September 2, 2018 at 8:27:11 AM UTC-4, Riz wrote:
>
> Jim,
>
> Appreciate you taking time to write that note. Would you share your OS and 
> browser version?
>
 
Windows 10 Home 1803 64-bit & Firefox 61.0.2 64-bit


-- 
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/848be283-303f-47a3-85c1-ef8e0b9ead82%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[tw5] Re: Timimi plugin - released for firefox/chrome/chromium in linux/mac/windows

[Jim]

I just wanted to say thanks for this browser extension - it really 
simplifies TW workflow when you don't need to consider file location or 
servers before starting. 

-- 
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/07ae10b3-ea79-482b-922a-331f9db75ba7%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[tw5] Re: sameday filter - off by one?

[Jim Farrand]

On Friday, 20 July 2018 22:41:13 UTC-7, Mark S. wrote:
>
> This is an experimental fix to the sameday filter. *ABSOLUTELY* make a 
> backup if you try this, because javascript errors can be insidious.
>
> Drag and drop onto your tw (greenbar at top) and import. Save. Reload. 
> Test.
>
> The real fix would probably affect two core tiddlers, but for convenience 
> I put the changes just into one.
>
>
Hi Mark,

Thanks, this feels like progress!

For me your change errors with: 

TypeError: tiddler.getFieldDay is not a function

I'm on 5.1.13 and I can't see that method in the source code for that 
version.  I notice that it is present in the code on github, so I guess 
maybe I just need to update my install to a new version.  Unfortunately 
it's late here in PDT, but I'll try to do this ASAP.

(Ironically I'm travelling back to BST tomorrow where this bug will impact 
me a lot less, but I'd still be glad to see if fixed.  :) )

Cheers,
Jim

 

> -- Mark
>
> On Friday, July 20, 2018 at 11:51:50 AM UTC-7, Jim Farrand wrote:
>>
>>
>> I have recently created a tiddler, which has created timestamp: 
>> 20180720180051119.  I would naively assume that the filter:
>>
>> [sameday:created[20180720]]
>>
>> would return this tiddler, but it doesn't.  It is, however, returned by 
>> this filter:
>>
>> [sameday:created[20180721]]
>>
>> Is this just how sameday works, or do I have some sort of setup problem?  
>> If sameday works this way, I would have thought this might be mentioned in 
>> the documentation for that operator, so I suspect I have some issue 
>> specific to me.  I'm currently in timezone PDT, whereas my "normal" 
>> timezone is BST, so I'm wondering if I have some confused configuration 
>> somewhere which is screwing things up.
>>
>> (I'm trying to create a journal template that includes the list of 
>> tiddlers created/modified on that day.)
>>
>> Thanks in advance,
>> Jim
>>
>

-- 
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/d13746e4-1916-4ba2-91bb-6b31f28635ac%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[tw5] Re: sameday filter - off by one?

[Jim Farrand]

On Friday, 20 July 2018 21:21:16 UTC-7, TonyM wrote:
>
> Jim,
>
> The other way around I would think, all dates utc and when you view them 
> the local timezone offset is applied. Including daylight.
>
> This is nessasary for time zone shared wikis. I can say this since I live 
> at +10
>

I agree, I think we are both suggesting the same thing.  As far as I can 
tell, the dates are already stored in UTC.  It's 20180720 22:29 here in 
PDT, and I just created a tiddler, and lookted at the timestamp in the file 
on disk is  201807210529 which is the time in UTC.  sameday needs to make 
the corresponding conversion to UTC so that it's comparing like to like 
(and as you say, display functions needs to convert either to local time, 
or to an explicit timezone if thay are given one).

Reading issue 2061, it seems that at least some people think that the 
timezone should also be stored on disk.  I disagree.  But it's also 
irrelevant because even if that change were to be made, we would still need 
to fix sameday etc.  Storing the timezone on disk is IMHO the wrong thing 
to do, but I don't see how it fixes the problem by itself, and it seems 
that no-one can be bothered to do it anyway.  So we might as well just fix 
sameday etc, which is easier, cleaner, and actually solves the problem.

I guess I'm hoping that a dev will pipe up and either say "go ahead and 
make this change, we'll probably accept the patch", OR... point out the 
missing line of reasoning that explains why it isn't the right solution.
 

> The view widget has the template parameter with the utc option and you can 
> format the same full date code to the micro second. Perhaps using the view 
> widget with or without utc before you feed it into your sameday filter in a 
> variable, will solve this issue?
>

I'm not sure how that would work.  What does the syntax look like to run a 
filter on the result of the view widget?
 
Regards,
Jim

To me date field values are barly readable as they are so why not maintain 
> them in utc and always filter and display them as local time.
>
> Evans formula plugin and the rpn maths plugins provide a little more in 
> the date, Maths and the pickaday plugin is good for date selection with a 
> popup calendar.
>
> Regards
> Tony
>
>

-- 
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/8016aaa0-a008-4563-a31e-9b7793cf2a9b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[tw5] Re: sameday filter - off by one?

[Jim Farrand]

On Friday, 20 July 2018 20:08:21 UTC-7, TonyM wrote:
>
> Jim,
>
> In your examples you use a litteral date, surely you need it to come from 
> a field a value or something else. How do you plan to actualy use sameday 
> in your tiddlers?
>
>

Hi Tony,

Yes, I simplified for the sake of the discussion.  In the real thing, I 
have the date stored in a field, and I'm using a macro to put it into the 
filter.  I have this all working, apart from the fact that I get the 
previous days tiddlers attached to each journal entry.

Looking through those tickets on github, I wonder if there is some 
analysis-paralysis happening.  The issue about sameday doing the wrong 
thing has been closed in favour of a much bigger and more controversial 
discussion about whether or not tiddlywiki should store timezones alongside 
dates.

The proposed storage change seems like a bit of a distraction.  Regardless 
of whether or not that change is made, sameday etc need to convert the 
query dates into the same timezone as the stored dates before doing the 
comparison.  Isn't is a pretty clear win to make sameday take an optional 
timezone (and treat argument as local time by default)?  There might be 
some small number of people who are relying on the buggy behaviour - they 
will have to update their code to explicitly mention UTC if that is the 
behaviour they really want.  But I think that number of people will be 
small compared to those who will benefit.

Regards,
Jim


 

> I have been doing a lot with dates of late.
>
> Regards
> Tony
>
>

-- 
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/4debb66b-4246-4206-a980-1c3bdaed0e32%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[tw5] sameday filter - off by one?

[Jim Farrand]

I have recently created a tiddler, which has created timestamp: 
20180720180051119.  I would naively assume that the filter:

[sameday:created[20180720]]

would return this tiddler, but it doesn't.  It is, however, returned by 
this filter:

[sameday:created[20180721]]

Is this just how sameday works, or do I have some sort of setup problem?  
If sameday works this way, I would have thought this might be mentioned in 
the documentation for that operator, so I suspect I have some issue 
specific to me.  I'm currently in timezone PDT, whereas my "normal" 
timezone is BST, so I'm wondering if I have some confused configuration 
somewhere which is screwing things up.

(I'm trying to create a journal template that includes the list of tiddlers 
created/modified on that day.)

Thanks in advance,
Jim

-- 
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/fbe963fe-0b47-4b89-bbb4-b7f2e5010993%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[tw5] Re: Minimal Ruby Server

[Jim]

Cool, thanks.

On Sunday, May 13, 2018 at 6:39:49 PM UTC-4, Mark S. wrote:
>
> I've made a PR:
>
> https://github.com/Jermolene/TiddlyWiki5/pull/3277
>
> Thanks!
> -- Mark
>
> On Sunday, May 13, 2018 at 7:32:49 AM UTC-7, Jim wrote:
>>
>> > You should add this as a PR as saver #21 at TiddlyWiki.com
>>
>> I'm not against it, but have no idea.
>>
>>
>>

-- 
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/e904a1a9-2e24-46de-a610-a44f00d49532%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[tw5] Re: Minimal Ruby Server

[Jim]

Sorry Tony I don't have the knowledge to help with that.  I agree with Mark 
- I would only use it locally and as-needed, shutting it down when you no 
longer need it. 


On Sunday, May 13, 2018 at 8:29:38 PM UTC-4, TonyM wrote:
>
> Jim,
>
> My cpanel account permits the use of Ruby on Rails. Can you possibly 
> provide guidence on using this to serve tiddlywiki files that can be saved?
>
> Regards
> Tony
>
>

-- 
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/060ec5f8-a23b-491d-9707-298324aee0fc%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[tw5] Re: Minimal Ruby Server

[Jim]

Both of these work - a remote image and a local image:


[img[https:
//discourse-cdn-sjc1.com/sketchup/uploads/default/6259/f745c81b340274a6.png]]

[img[00439.png]]



On Sunday, May 13, 2018 at 12:18:33 PM UTC-4, Mark S. wrote:
>
> No, I meant images to external files. Adding images to TW directly slows 
> it down very quickly. 
>
> -- Mark
>
> On Sunday, May 13, 2018 at 7:32:49 AM UTC-7, Jim wrote:
>>
>> I've updated the file to create a back-up file on save. It might slow 
>> things down on large TW's but better to be safe than sorry.
>>
>> > You should add this as a PR as saver #21 at TiddlyWiki.com
>>
>> I'm not against it, but have no idea.
>>
>> > Will this also serve images?
>>
>> Images in a TW (which is just html)? Then yes it works. 
>>
>> On Saturday, May 12, 2018 at 10:32:45 AM UTC-4, Jim wrote:
>>>
>>> I use Ruby and so always have it installed. If you do too, here's a 
>>> minimal server using Ruby Webrick. It just serves up files from the same 
>>> folder and handles saving. 
>>>
>>> Once running, just point yor web browser at localhost:8000 to view the 
>>> folder listing, and click on your wiki html file.
>>>
>>> https://gist.github.com/jimfoltz/ee791c1bdd30ce137bc23cce826096da
>>>
>>>
>>>

-- 
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/44ca8478-5445-45f3-9943-8ebec0f2d4c2%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[tw5] Re: What happened to my tiddler Type field?

[Jim]

Brilliant! Thank you.  

Is it a bug?


On Sunday, May 13, 2018 at 10:37:57 AM UTC-4, Eric Shulman wrote:
>
> On Sunday, May 13, 2018 at 5:21:17 AM UTC-7, Jim wrote:
>>
>> Good morning. 
>>
>> I'm not sure what I did but does anyone know how to fix this?
>>
>
> In the Control Panel, Settings tab, make sure that
>[x] Enable links to missing tiddlers 
> is checked.
>
> enjoy,
> -e
> Eric Shulman
> TiddlyTools.com: "Small Tools for Big Ideas!" (tm)
> InsideTiddlyWiki: The Missing Manuals
>

-- 
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/6d1d44d2-768d-4cb7-bfe6-ba7f632963f5%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[tw5] Re: Minimal Ruby Server

[Jim]

I've updated the file to create a back-up file on save. It might slow 
things down on large TW's but better to be safe than sorry.

> You should add this as a PR as saver #21 at TiddlyWiki.com

I'm not against it, but have no idea.

> Will this also serve images?

Images in a TW (which is just html)? Then yes it works. 

On Saturday, May 12, 2018 at 10:32:45 AM UTC-4, Jim wrote:
>
> I use Ruby and so always have it installed. If you do too, here's a 
> minimal server using Ruby Webrick. It just serves up files from the same 
> folder and handles saving. 
>
> Once running, just point yor web browser at localhost:8000 to view the 
> folder listing, and click on your wiki html file.
>
> https://gist.github.com/jimfoltz/ee791c1bdd30ce137bc23cce826096da
>
>
>

-- 
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/c0a049c7-8ce9-483d-9e7b-da9661e05f04%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[tw5] What happened to my tiddler Type field?

[Jim]

Good morning. 


I'm not sure what I did but does anyone know how to fix 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/46fc1527-b80a-48b3-941d-71f86cc8480b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[tw5] Minimal Ruby Server

[Jim]

I use Ruby and so always have it installed. If you do too, here's a minimal 
server using Ruby Webrick. It just serves up files from the same folder and 
handles saving. 

Once running, just point yor web browser at localhost:8000 to view the 
folder listing, and click on your wiki html file.

https://gist.github.com/jimfoltz/ee791c1bdd30ce137bc23cce826096da


-- 
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/b31ad40e-23be-4dd9-aab8-e6c8e12f6547%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[tw5] Re: Extract Tiddler Files From HTML Tiddlywiki

[Jim]

You'll need a node executable <https://nodejs.org/en/download/> and the TW5 
source <https://github.com/Jermolene/TiddlyWiki5/releases>. 

I'm using Windows. Here's a batch file example:

set node_exe="C:\Users\Jim\Downloads\node-v8.11.1-win-x64\node.exe"
set tw_js="C:\Users\Jim\Downloads\TiddlyWiki5-5.1.17\tiddlywiki.js"

set wiki_html=%1

%node_exe% %tw_js% --verbose --load %wiki_html% ^
--output ./tiddlers ^
--render "[!is[system]]" "[encodeuricomponent[]addsuffix[.tid]]"  
"text/plain" "$:/core/templates/tid-tiddler"



-- 
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/da88694f-b4b2-414c-a3df-667feead708a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[tw] Re: [INTRO] File Save and Backup AddOn for FireFox 57++

['Jim McD' via TiddlyWiki]

Thanks for this.  Version 0.2.1 tested and working on Windows 8.1 Pro, FF 
57, Classic Tiddlywiki.

-- 
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/8bf9cc53-8351-412b-a21e-8b93ee53115a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[tw] Re: Testers needed for TiddlyServer

[Jim]

This is what I get





:


-- 
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/3132176c-9448-4942-9a6e-7ec0acf0146d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[tw] Re: Is there a permanent TiddlyFox solution?

[Jim W]

Yeah I actually do have system level encryption turned on, so I'm fine if 
someone were to physically steal my laptop but I primarily use TiddlyWiki 
at work connected to my work domain. I don't necessarily trust every IT 
user that walks in the door or is planning to leave the company. So the 
technically double encryption I was using with the single file was 
necessary in my opinion. Even besides protecting my data from an internal 
rogue admin, an outside actor might compromise an privileged domain account 
trawl the network and grab my data. I'm considering putting my node.js 
tiddly inside of a veracrypt container (as recommended 
<https://github.com/Jermolene/TiddlyWiki5/issues/1073#issuecomment-330896212> 
by Jeremy) but that will be a lot more cumbersome than the single file full 
encryption was and really I'll be similarly vulnerable once the container 
is mounted and unencrypted. Maybe I'm overthinking that, I'm sure even with 
the the single file encryption there were vulnerabilities to consider, but 
it seems fairly trivial to me to grab the unencrypted file sitting on the 
file-system once the OS is unlocked.

On Wednesday, September 20, 2017 at 7:42:06 PM UTC-5, PMario wrote:
>
> On Wednesday, September 20, 2017 at 3:37:20 PM UTC+2, Jim W wrote:
>>
>> I converted over to Node.js but I guess now I've lost the ability to 
>> encrypt all my tiddlers 
>> <https://github.com/Jermolene/TiddlyWiki5/issues/1073>? There's a plugin 
>> <https://github.com/danielo515/TW5-EncryptTiddlerPlugin> to manually 
>> encrypt tiddlers but it looks abandoned without the important feature of 
>> confirming 
>> the password  
>> <https://github.com/danielo515/TW5-EncryptTiddlerPlugin/issues/4>(I want 
>> to avoid ruining a tiddler with one typo). 
>>
>
> If you are able to use the node version, you should be also able to set up 
> your OS to encrypt every file in your data directory on the system level. 
> ... So there should be no need to encrypt the stuff 2 times. 
>
> Most people I know, don't consider this option, because it's conpletely 
> transparent. So you basically don't see, that the files are encrypted. They 
> just look like normal files. ... And if you can't see it, ... it's not 
> there ... right?
>
> just my 2 cents
> -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/8c935d8e-cfa5-4a85-8f92-ff4a5368ddfb%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[tw] Re: Is there a permanent TiddlyFox solution?

[Jim W]

I converted over to Node.js but I guess now I've lost the ability to 
encrypt all my tiddlers 
<https://github.com/Jermolene/TiddlyWiki5/issues/1073>? There's a plugin 
<https://github.com/danielo515/TW5-EncryptTiddlerPlugin> to manually 
encrypt tiddlers but it looks abandoned without the important feature of 
confirming 
the password  
<https://github.com/danielo515/TW5-EncryptTiddlerPlugin/issues/4>(I want to 
avoid ruining a tiddler with one typo). 

Whatever option for moving past FF57 becomes consensus (and I fully agree 
with Riz's concerns) I hope easy full encryption will still be an option. 
If I move over to TiddlyServer is there a workable path toward that?

On Monday, September 18, 2017 at 3:12:53 PM UTC-5, Lost Admin wrote:
>
> To the best of my knowledge, there is no planned replacement for TiddlyFox 
> (Jeremy, please correct me if I'm wrong). The extension mechanism that 
> TiddlyFox relies on will be removed from Firefox when version 57 gets here. 
> The mechanism that replaces it will not support the functionality needed to 
> write a replacement add-on (also, correct me if I'm wrong as I'm not an 
> extension developer).
>
> There are a number of alternatives. Some exist today, some are still in 
> discussion. None are exactly like TiddlyFox. Some of them include:
>
> Running TiddlyWiki on Node.js (
> http://tiddlywiki.com/static/TiddlyWiki%2520on%2520Node.js.html)
> Running TiddlyServer on your computer (
> https://github.com/Arlen22/TiddlyServer)
> Running Noteself instead (https://noteself.github.io/)
> Running IIS or Apache locally configured to support WebDAV (various 
> discussions on this forum)
>
> Each of those options has benefits and disadvantages. All of them (except 
> using Noteself) require you to install software on your computer (this 
> might not be an option in some situations).
>
> Noteself with a properly configured CouchDB server somewhere on the 
> Internet (or on your local computer) is a pretty interesting solution but 
> some people are having challenges getting set-up the way they want. Without 
> a CouchDB server you could easily lose everything (clearing all local data 
> would delete all your saved content if you don't have CouchDB).
>
>
> On Monday, September 18, 2017 at 3:42:52 PM UTC-4, Jim W wrote:
>>
>> Forgive my ignorance, I've looked for some kind of consensus on what 
>> happens when TiddlyFox stops working when Firefox 57 gets here but haven't 
>> really found one. For a long time TiddlyWiki/TiddlyFox user what's the best 
>> course of action if I'm not willing to give up standard Firefox (I don't 
>> really like the idea of using something like FirefoxESR)? Or what options 
>> are there? I feel like I must be missing something, seems like main 
>> TiddlyWiki.com instructions would stop advising you to install TiddlyFox if 
>> it's slated to stop working?
>>
>> On Sunday, September 17, 2017 at 5:32:20 PM UTC-5, RichardWilliamSmith 
>> wrote:
>>>
>>> Hi,
>>>
>>> Tiddlyfox is slated to stop working altogether with Firefox 57 and they 
>>> might be preparing you for that eventuality by disabling it. If you goto 
>>> "about:addons" (type it in the address bar) do you see Tiddlyfox listed as 
>>> running? (it should say 'legacy' but it might also be disabled by default).
>>>
>>> Regards,
>>> Richard
>>>
>>

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywiki+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/48df4315-9c47-4d11-8cac-d6280f18b98e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[tw] Re: Is there a permanent TiddlyFox solution?

[Jim W]

>From the FirefoxESR page: "Who is it not for? Individual users who always 
want the latest features, performance enhancements and technologies in 
their browser without waiting for them to become available in ESR several 
development cycles later."

Unfortunately I fall into that camp but the further I look into FF57 (I 
think I've been caught off guard since most of my preferred add-ons are 
getting the ax and no word on 57+ updates) I might be using FirefoxESR 
while I try to settle on a new browser. As far as TiddlyWiki the replies 
here have really helped, I'll be looking into converting over to Node.JS or 
maybe dig into TiddlyServer.

On Monday, September 18, 2017 at 4:46:53 PM UTC-5, @TiddlyTweeter wrote:
>
>
> Jim: I don't really like the idea of using something like FirefoxESR
>
> Why? Has it got diseases? Lol. 
>
> Its just Firefox that lags behind on cutting edge. But it has full 
> security updates. Once 57 fully comes in it will be the ONLY Mozilla 
> supported Firefox left that will run TiddlyFox. It should continue to run 
> TidelyFox till March, or later, next year.
> Notte
> 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/4cb3be36-200d-4517-b8a0-27d5e37ef2c4%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[tw] Re: Is there a permanent TiddlyFox solution?

[Jim W]

Forgive my ignorance, I've looked for some kind of consensus on what 
happens when TiddlyFox stops working when Firefox 57 gets here but haven't 
really found one. For a long time TiddlyWiki/TiddlyFox user what's the best 
course of action if I'm not willing to give up standard Firefox (I don't 
really like the idea of using something like FirefoxESR)? Or what options 
are there? I feel like I must be missing something, seems like main 
TiddlyWiki.com instructions would stop advising you to install TiddlyFox if 
it's slated to stop working?

On Sunday, September 17, 2017 at 5:32:20 PM UTC-5, RichardWilliamSmith 
wrote:
>
> Hi,
>
> Tiddlyfox is slated to stop working altogether with Firefox 57 and they 
> might be preparing you for that eventuality by disabling it. If you goto 
> "about:addons" (type it in the address bar) do you see Tiddlyfox listed as 
> running? (it should say 'legacy' but it might also be disabled by default).
>
> Regards,
> Richard
>

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywiki+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/5c9cf08d-f271-489d-b834-61179f2b1fdf%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[tw] Re: Hello and a question.

[Jim]

An example assumption I made.  

You use [[ ]] to create links. You use {{!!field}} to include a field.  
Therefore, [[{{!!field}}]] will create a link using the value of the field. 

-- 
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/405ef1f8-6dd4-4dfa-b90c-61423a46aded%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [tw] Hello and a question.

[Jim]

Hi Alex - yes I did but I don't get a link, only the text.  What I just now 
found is that if I include the brackets in the field, then the {{!!field}} 
syntax generates a link. So the field needs to be: [[First Middle Surname]] 
instead of just First Middle Surname.

It's the kind of thing that that messes me up when trying to use TW. 



On Friday, September 15, 2017 at 5:21:59 PM UTC-4, AlexHough wrote:
>
> Hi Jim,
>
> Welcome.
>
> have you tried this syntax: {{!!field}} ?
>
>
> Alex
>
>

-- 
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/cf50485e-68a3-4598-8f80-d24878d23814%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[tw] Need help -- have $$$ (well, $)

[Jim Tobias]

Hi All,

I built a concept map in Freeplane for a complex work project. It worked 
okay for me, but was not useful to the team I'm working with for several 
reasons. So I'm looking around again, and noticed that there's TiddlyMap 
that links a wiki to a concept map. But I need some help evaluating 
TiddlyWiki/Map, figuring out how it might work for my project, and 
especially any way to avoid copy-pasting my entire Freeplane map into it. 
Is there anyone available for paid assistance? Probably just a few hours? 
Thanks 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/6b772729-c464-424f-8930-f5a445057e08%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[tw] (TW5) Save not working in node.js

[Jim]

Hi,

I'm trying to run TW5 on node.  My first attempts involved following the 
instructions on the TW site for running TW under node.js exactly.  Things 
appear to be working correctly on the server side.  I get messages 
indicating that new tiddlers have been created and they physically exist on 
the server but I don't see any newly-created tiddlers when I refresh the 
browser.  I've searched the discussion groups and every other source I 
could find and tried anything that seemed relevant but nothing solves the 
problem.

I've tried so many different configurations in my attempt to debug this 
problem that it's difficult to list them all.  I've used several different 
linux distributions running under VirtualBox and in native mode.  My 
primary OS is Linux Mint 17, browser is Firefox.  Any help would be greatly 
appreciated.  I've included a listing of the server-side output below 
although it may not be that helpful because it looks valid.  The only 
anomaly is the new tiddlers not appearing in the browser.

$ tiddlywiki mywiki --server
Serving on 127.0.0.1:8080
(press ctrl-C to exit)
syncer-server: Dispatching 'save' task: Draft of 'New Tiddler'
FileSystem: Saved file /home/tiddlywiki/mywiki/tiddlers/Draft of 'New 
Tiddler'.tid
syncer-server: Dispatching 'save' task: Draft of 'New Tiddler'
FileSystem: Saved file /home/tiddlywiki/mywiki/tiddlers/Draft of 'New 
Tiddler'.tid
syncer-server: Dispatching 'save' task: Draft of 'New Tiddler'
FileSystem: Saved file /home/tiddlywiki/mywiki/tiddlers/Draft of 'New 
Tiddler'.tid
syncer-server: Dispatching 'save' task: Draft of 'New Tiddler'
FileSystem: Saved file /home/tiddlywiki/mywiki/tiddlers/Draft of 'New 
Tiddler'.tid
syncer-server: Dispatching 'save' task: Draft of 'New Tiddler'
FileSystem: Saved file /home/tiddlywiki/mywiki/tiddlers/Draft of 'New 
Tiddler'.tid
syncer-server: Dispatching 'save' task: Draft of 'New Tiddler'
FileSystem: Saved file /home/tiddlywiki/mywiki/tiddlers/Draft of 'New 
Tiddler'.tid
syncer-server: Dispatching 'delete' task: Draft of 'New Tiddler'
FileSystem: Deleted file /home/tiddlywiki/mywiki/tiddlers/Draft of 'New 
Tiddler'.tid
syncer-server: Dispatching 'save' task: NewTiddlerTest01
FileSystem: Saved file /home/tiddlywiki/mywiki/tiddlers/NewTiddlerTest01.tid
^C$ 

-- 
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 http://groups.google.com/group/tiddlywiki.
For more options, visit https://groups.google.com/d/optout.

Re: [tw] (TW5) Save not working in node.js

[Jim]

Hi Jeremy,

I just started using TW so I didn't even think of that but now that you 
mention it, it seems obvious to look for them there.  The new tiddlers are 
in fact there and I can open them.  For some reason I made the assumption 
they would be automatically displayed in the default initial view.  I'm 
glad the solution is this simple but a bit embarrassed that it turned out 
to be lack of knowledge on my part.  Thanks much for your incredibly quick 
and helpful response!

Best, Jim


On Wednesday, March 25, 2015 at 12:09:28 PM UTC-4, Jeremy Ruston wrote:

 Hi Jim

 Those server messages indicate that the changes are being saved to the 
 server without problems. Do you see your newly created tiddlers under the 
 Recent tab?

 Best wishes

 Jeremy


 On Wed, Mar 25, 2015 at 4:07 PM, Jim jim@gmail.com javascript: 
 wrote:

 Hi,

 I'm trying to run TW5 on node.  My first attempts involved following the 
 instructions on the TW site for running TW under node.js exactly.  Things 
 appear to be working correctly on the server side.  I get messages 
 indicating that new tiddlers have been created and they physically exist on 
 the server but I don't see any newly-created tiddlers when I refresh the 
 browser.  I've searched the discussion groups and every other source I 
 could find and tried anything that seemed relevant but nothing solves the 
 problem.

 I've tried so many different configurations in my attempt to debug this 
 problem that it's difficult to list them all.  I've used several different 
 linux distributions running under VirtualBox and in native mode.  My 
 primary OS is Linux Mint 17, browser is Firefox.  Any help would be greatly 
 appreciated.  I've included a listing of the server-side output below 
 although it may not be that helpful because it looks valid.  The only 
 anomaly is the new tiddlers not appearing in the browser.

 $ tiddlywiki mywiki --server
 Serving on 127.0.0.1:8080
 (press ctrl-C to exit)
 syncer-server: Dispatching 'save' task: Draft of 'New Tiddler'
 FileSystem: Saved file /home/tiddlywiki/mywiki/tiddlers/Draft of 'New 
 Tiddler'.tid
 syncer-server: Dispatching 'save' task: Draft of 'New Tiddler'
 FileSystem: Saved file /home/tiddlywiki/mywiki/tiddlers/Draft of 'New 
 Tiddler'.tid
 syncer-server: Dispatching 'save' task: Draft of 'New Tiddler'
 FileSystem: Saved file /home/tiddlywiki/mywiki/tiddlers/Draft of 'New 
 Tiddler'.tid
 syncer-server: Dispatching 'save' task: Draft of 'New Tiddler'
 FileSystem: Saved file /home/tiddlywiki/mywiki/tiddlers/Draft of 'New 
 Tiddler'.tid
 syncer-server: Dispatching 'save' task: Draft of 'New Tiddler'
 FileSystem: Saved file /home/tiddlywiki/mywiki/tiddlers/Draft of 'New 
 Tiddler'.tid
 syncer-server: Dispatching 'save' task: Draft of 'New Tiddler'
 FileSystem: Saved file /home/tiddlywiki/mywiki/tiddlers/Draft of 'New 
 Tiddler'.tid
 syncer-server: Dispatching 'delete' task: Draft of 'New Tiddler'
 FileSystem: Deleted file /home/tiddlywiki/mywiki/tiddlers/Draft of 'New 
 Tiddler'.tid
 syncer-server: Dispatching 'save' task: NewTiddlerTest01
 FileSystem: Saved file 
 /home/tiddlywiki/mywiki/tiddlers/NewTiddlerTest01.tid
 ^C$ 

 -- 
 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 javascript:.
 To post to this group, send email to tiddl...@googlegroups.com 
 javascript:.
 Visit this group at http://groups.google.com/group/tiddlywiki.
 For more options, visit https://groups.google.com/d/optout.




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

-- 
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 http://groups.google.com/group/tiddlywiki.
For more options, visit https://groups.google.com/d/optout.

Re: [tw] [TW5] Static sites - sitemap and ATOM plugins updated...

[Jim Lehmer]

On Monday, January 26, 2015 at 5:49:12 AM UTC-6, AlexHough wrote:

 Thanks Tobias,

 The sitemap makes it easier for google to index...

 A huge topic!


Correct. And while there is some discussion about whether they are used 
much by the search engines any more, both Google and Bing have ways to 
register your sitemap location with them, and some people want them, so I 
decided why not develop it in anticipation of being asked for it? 

-- 
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 http://groups.google.com/group/tiddlywiki.
For more options, visit https://groups.google.com/d/optout.

[tw] Re: TiddlyWiki Hangout #76 will be on Tuesday 6th January at 4pm GMT

[Jim Lehmer]

On Tuesday, January 27, 2015 at 9:51:41 AM UTC-6, Jeremy Ruston wrote:

 TiddlyWiki Hangout #77 is about to start.


Thanks for posting this today or I would've missed the call. I am still not 
getting invites. 

-- 
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 http://groups.google.com/group/tiddlywiki.
For more options, visit https://groups.google.com/d/optout.

[tw] [TW5] Static sites - sitemap and ATOM plugins updated...

[Jim Lehmer]

*ATOM feed *- https://github.com/dullroar/TW5-atomfeed
*Sitemap *- https://github.com/dullroar/TW5-sitemap

Both contain the following bug fixes:

1. Use the approved TW date formatting (/$tw.utils.formatDateString()/), 
per Mario's suggestion on 1/18 (thanks, Mario).
2. Gracefully handle tiddlers that do not have a modified field, per the 
bug sini-Kit reported on 1/18 (thanks, sini-Kit).
3. Use their respective /atomserver///sitemapserver/ tiddlers to specify 
the server URL to use throughout the output files (I was using them in 
some places but not others).


I hadn't forgotten about these, just life with work, running, a wife and 
daughter in college, and two teens still in high school and both 
involved in extracurricular activities plays havoc with trying to get 
any fun work 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 http://groups.google.com/group/tiddlywiki.
For more options, visit https://groups.google.com/d/optout.

Re: [tw] Re: [TW5] New plugin for generating sitemap.xml for static sites

[Jim Lehmer]

On 1/18/2015 7:40 AM, Jim Lehmer wrote:
So, if the error is happening in my code, that tells me there is a 
tiddler or tiddlers without a /modified /field. I would have always 
expected that field to get created (it seems to on any tiddlers I 
create). I wonder if some system tiddlers are built without the 
/modified /field? Does anyone else know?


And the answer is, Yes, there are lots of system tiddlers in the node 
version (and I would expect in the standalone version) that don't have 
either /created /or /modified /fields.


When you use the plugin, are you passing it a filter to filter out 
system tiddlers?


Which then leads to needing to filter out system tiddlers (which should 
be filtered out, anyway, because they're not going to be meaningful in a 
sitemap).


--
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 http://groups.google.com/group/tiddlywiki.
For more options, visit https://groups.google.com/d/optout.

Re: [tw] Re: [TW5] New plugin for generating sitemap.xml for static sites

[Jim Lehmer]

On 1/18/2015 8:45 AM, Tobias Beer wrote:
So, what to do with tiddlers that don't have a modified date and a 
sitemap?

Is it ok for them not having any?

I guess you want to use a custom filter anyway,
if only to not index system tiddlers
...or just all tagged blog or whatever you use
to distinguish content from overhead.


That was precisely my case - I can't see any reason to not filter out 
system tiddlers.


I note in the sitemap spec http://www.sitemaps.org/protocol.html that 
the /lastmod /element is optional, so I will probably end up changing 
the code to only call the date formatting routine and generate that 
element if there is actually a /modified /field, just to insulate from 
this error. Will go create an issue on Github to remind myself of it now.


--
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 http://groups.google.com/group/tiddlywiki.
For more options, visit https://groups.google.com/d/optout.

Re: [tw] Re: [TW5] New plugin for generating sitemap.xml for static sites

[Jim Lehmer]

Good to know. I will log another issue in my repo. :)

On 1/18/2015 1:45 PM, PMario wrote:

see:  core/modules/utlis/utils.js

exports.formatDateString = function(date,template)

-

$tw.utils.formatDateString(new Date, -MMM)
will give you 2015-January

-m
--
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/Xton0F9QtHE/unsubscribe.
To unsubscribe from this group and all its topics, send an email to 
tiddlywiki+unsubscr...@googlegroups.com 
mailto:tiddlywiki+unsubscr...@googlegroups.com.
To post to this group, send email to tiddlywiki@googlegroups.com 
mailto:tiddlywiki@googlegroups.com.

Visit this group at http://groups.google.com/group/tiddlywiki.
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 http://groups.google.com/group/tiddlywiki.
For more options, visit https://groups.google.com/d/optout.

Re: [tw] Re: javascript macro / macrocall problem

[Jim Lehmer]

On 1/12/2015 7:24 AM, 'Stephen Kimmel' via TiddlyWiki wrote:
preview pane, the editor is little more than a textarea box. If we 
could get it to look as good as the editor we use when posting 
messages to this group, I would be ecstatic. And it would make life a 
lot easier on the new users without detracting from Tiddlywiki's power.


I have had the very same thought, multiple times when typing a TW group 
message into Google Groups - I want */this /*editor in TW! Especially 
since I tend to move between Markdown (er, CommonMark :) and TW quite a 
bit, and am always using the wrong syntax (I posted a pull request to 
another project on GitHub the other day and used TW's link syntax!)


The editor would still need a way to drop to native syntax for 
specifying widgets, defining macros, etc., but for the type of people 
(including me at times) who just want to use TW for quick notetaking and 
not have to remember the syntax for bolding, I think it would be a huge 
win. In fact, given that Ctrl-B, Ctrl-I, Ctrl-U are almost all uniform 
in meaning across most WYSIWYG editors, just having those three hot keys 
enabled would be a great start.


Tiddlywiki is also, by a fair margin, the most sophisticated program 
I've run into in years (and I'll wager my number of years in the 
computer field rival anyone else's)


I've been 35 years in the industry, 27 with 
programmer/engineer/architect attached to my title. Am I close? :)


--
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 http://groups.google.com/group/tiddlywiki.
For more options, visit https://groups.google.com/d/optout.

Re: [tw] Re: javascript macro / macrocall problem

[Jim Lehmer]

On 1/12/2015 12:36 PM, 'Stephen Kimmel' via TiddlyWiki wrote:
Close. Not that it matters at all but... My first job as a programmer 
started in 1965. In November of 1979, I was a contributing editor of 
Creative Computing magazine.


You win. :)

Although even so I realized I am not good doing math with really big 
numbers, because this is my 29th year programming professionally, not my 
27th. Yikes!


And I remember /Creative Computing/.

Now in respect to the other list members, we greybeards should quit 
discussing our back in the day bonafides. :)


Hey, you kids! Get offa my dot matrix printer! (waves cane)

--
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 http://groups.google.com/group/tiddlywiki.
For more options, visit https://groups.google.com/d/optout.

[tw] Re: Tiddlyspot - Gallery for TW5

[Jim Lehmer]

On Saturday, January 10, 2015 at 7:08:55 AM UTC-6, Atul Grover wrote:

 There is a tiddlyspot gallery where various Tiddlywikis are showcased ( 
 http://tiddlyspot.com/?page=gallery ). 
 Should we create a page where we showcase different variant of TW5  
 bottomtabs... scholars. etc.
 Each one solving a specific need of the end user. 

 Example: 

 1. TW5 with phone gap can leverage the camera of mobile phones to create a 
 scrapbook like solution for learning.
 2. Tiddly Talky can be used for ppt like presentations
 3. http://tiddlywiki.com/editions/introduction/; can be used for story 
 telling for young students


I just posted about a desire to see something like that in another thread 
(on macros and macrocalls, although it is far beyond that topic now :). 
Except what I was calling for was various small variants on Empty.html that 
are each focused on demonstrating a single TW concept (buttons and select 
widgets, for example).

TB, that customize concept is great, and yes, would be fantastic for TW5.

-- 
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 http://groups.google.com/group/tiddlywiki.
For more options, visit https://groups.google.com/d/optout.

[tw] Tip for serving TW5 on node to local network

[Jim Lehmer]

Just a quick tip - most of you might already know this. In my scenario I 
have a TW set up to run under node. It is on Dropbox, and depending on 
what I am trying to do I may run it on either one of my Windows or Linux 
boxes. But I want a single command to be able to run it on either 
without change */and /*I also be able to browse to it from anywhere on 
the */local /*network, not just on the same machine (in other words, I 
don't want to run it on 127.0.0.1).


The secret is instead of doing /ipconfig/ifconfig /and binding the 
server to the specific IP address of your box, simply bind to 0.0.0.0:


tiddlywiki --server 8080 $:/core/save/lazy-images text/plain text/html Jim  
0.0.0.0


Works great, and now I don't have to worry about what machine I launch 
it on.


--
You received this message because you are subscribed to the Google Groups 
TiddlyWiki group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywiki+unsubscr...@googlegroups.com.
To post to this group, send email to tiddlywiki@googlegroups.com.
Visit this group at http://groups.google.com/group/tiddlywiki.
For more options, visit https://groups.google.com/d/optout.

Re: [tw] Re: Tiddlyspot - Gallery for TW5

[Jim Lehmer]

On 1/11/2015 1:30 PM, Tobias Beer wrote:

How to protect the tiddler against maleficent?
Perhaps watch less Disney.


:)

That's why in my other post I mentioned curated. Of course, that 
implies a level of attention to detail that may not be available from 
anyone to be a curator. Of course, for the blessed sample TWs I'm 
talking about (e.g., /ButtonsAndSelect.html/), if they were part of the 
tiddlywiki.com edition, they'd have to be created and vetted but that 
should be pretty easy, since they would be smaller, with 1-n tiddlers to 
demonstrate and document the concept and that's it.


--
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 http://groups.google.com/group/tiddlywiki.
For more options, visit https://groups.google.com/d/optout.

Re: [tw] Re: Fun with bookmarks

[Jim Lehmer]

On 1/6/2015 10:48 PM, Jed Carty wrote:
I did get a red box of doom when I selected c++ as the tag though, I 
would guess that the ++ part may interact strangely with the regexp 
filter.


Yes, unfortunately I created that tag before I switched over to using 
regex's. And like the joke about REs go, now I have two problems. Spent 
an hour trying out various things with no success (mostly around trying 
to use a set widget to pre-and-postpend various RE escapes to the tag). 
May keep trying or change the tag to cplusplus. :)


I may have to ban special characters from tags in this, because .net 
causes issues, too (it works, but it also finds any other tag that has a 
single character in front of net - because of course it does).


One thing that may be useful to add is a search box next to the tag 
select drop down as an alternative to CTRL+F. I the sort of search I 
am talking about here 
http://inmysocks.tiddlyspot.com/#Search%20by%20field%20content and a 
few other places on my wiki if you do want to implement it.


Good stuff. Thanks.


Do you create the tiddler for each bookmark manually?


Unfortunately, yes. They were in another TW in another format not easy 
to extract. Note, however, if this were on a node-served TW creating 
each bookmark tiddler programmatically would be super-easy.


--
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 http://groups.google.com/group/tiddlywiki.
For more options, visit https://groups.google.com/d/optout.

[tw] Fun with bookmarks

[Jim Lehmer]

Searching through archives, how-to's and other resources, it seems like 
bookmarks and associated functionality are one of the more popular uses for 
TW, especially when first starting out. I decided to try my hand at it, and 
it was actually quite a learning experience. Consider the TW here:

https://dl.dropboxusercontent.com/s/pzgn3bukhi6yx4d/bookmarks.html

Some things to note:

1. The default view is of all bookmarks sorted under their associated tags.
2. Bookmarks can show up under multiple tags. That's a feature, because I 
often like to cross-reference a single resource multiple ways.
3. There is a select widget at the top that allows you to quickly filter to 
see a specific tag's bookmarks.
4. The select widget also has an all by names option (up one from the 
default all by tags option) to see all the bookmarks without tags, sorted 
by name (because sometimes Ctrl-F is the fastest way to find something :).
5. There is also an untagged option at the bottom of the select widget to 
show any bookmarks that aren't tagged (since otherwise they won't show up 
in the list).
6. Actually uses a regex filter under the covers. (Now you have two 
problems http://regex.info/blog/2006-09-15/247.)
7. Does some things with set widgets turning tv-wikilinks off and on so 
that when displaying the title of a bookmark (which links to the external 
site), any CamelCase words don't show up as wikilinks.

I almost gave up a few times, because figuring all the above out wasn't 
easy, and I had a vision I wanted to work. But glad I stuck with it. It 
was...fun. :)

Besides all the tiddlers for each bookmark, the entire thing is implemented 
solely in the Bookmarks tiddler, as follows:

''Tag:'' $select tiddler=$:/temp/bookmarkfilter
option value=\W(all by name)/option
option value=\w selected=true(all by tags)/option
$list filter=[tags[]sort[]]
option$view field=title//option
/$list
option value=untagged(untagged)/option
/$select

$reveal type=nomatch state=$:/temp/bookmarkfilter text=\W
$list 
filter=[tags[]regexp{$:/temp/bookmarkfilter}!is[system]sort[title]]
$transclude tiddler=$:/core/ui/TagTemplate mode=inline/
ul
$list filter=[all[current]tagging[]sort[title]]
li
$set name=tv-wikilinks value=no
$set name=href value={{!!text}}
a target=_blank href=href ''{{!!title}}''/a
/$set
/$set
$set name=tv-wikilinks value=yes
$link(edit)/$link
/$set
/li/$list/ul
/$list
/$reveal
$reveal type=match state=$:/temp/bookmarkfilter text=\W
ul
$list filter=[tags[]tagging[]sort[title]]
li
$set name=tv-wikilinks value=no
$set name=href value={{!!text}}
a target=_blank href=href ''{{!!title}}''/a
/$set
/$set
$set name=tv-wikilinks value=yes
$link(edit)/$link
/$set
/li
/$list
/ul
/$reveal
$reveal type=match state=$:/temp/bookmarkfilter text=untagged
ul
$list filter=[untagged[]!is[system]!title[Bookmarks]sort[title]]
li
$set name=tv-wikilinks value=no
$set name=href value={{!!text}}
a target=_blank href=href ''{{!!title}}''/a
/$set
/$set
$set name=tv-wikilinks value=yes
$link(edit)/$link
/$set
/li
/$list
/ul
/$reveal

-- 
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 http://groups.google.com/group/tiddlywiki.
For more options, visit https://groups.google.com/d/optout.

[tw] Re: TiddlyWiki Hangout #76 will be on Tuesday 6th January at 4pm GMT

[Jim Lehmer]

For some reason I keep missing these announcements in the group. Sigh.

Since we're using Google Groups, is there a possibility of a TW Google 
Calendar to which I could then subscribe? Google Calendar (and these TW 
groups) are about the last two functions I use from The All-Seeing Eye.

On Friday, January 2, 2015 10:25:44 AM UTC-6, Jeremy Ruston wrote:

 The next TiddlyWiki Hangout will be on Tuesday 6th January at 4pm GMT/UTC. 

 https://plus.google.com/events/crcmq9b8flanpnd9lfnect5h5v4

 You can post questions for the hangout using the QA button on the video 
 preview on the page above. You'll then need to click the grid icon at the 
 top right, and then choose the QA button.

 After this hangout there will be a break of a couple of weeks and then 
 we'll have TiddlyWiki Hangout #77 on Tuesday 27th January:

 https://plus.google.com/events/c0p3611c2m3l7kiml57243v9amk

 Best wishes

 Jeremy

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

-- 
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 http://groups.google.com/group/tiddlywiki.
For more options, visit https://groups.google.com/d/optout.

[tw] Re: [TW5] New plugin for generating sitemap.xml for static sites

[Jim Lehmer]

On Monday, January 5, 2015 9:31:01 AM UTC-6, Tobias Beer wrote:

 Cool stuff, Jim.

 With the increasing information on static pages,
 I have started to collect some notes on the different tidbits...

 http://static.tiddlyspot.com


Thanks, Tobias! 

-- 
You received this message because you are subscribed to the Google Groups 
TiddlyWiki group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywiki+unsubscr...@googlegroups.com.
To post to this group, send email to tiddlywiki@googlegroups.com.
Visit this group at http://groups.google.com/group/tiddlywiki.
For more options, visit https://groups.google.com/d/optout.

[tw] Re: Color highlighting in a snippet of code

[Jim Lehmer]

I figure it out. The sidebar, which has fixed positioning, was overlaying 
the z-index order of the footer, so while you could *see *the links in the 
center of the footer, you couldn't *click *on them. I have added fixed 
positioning to the footer and all seems well now.

On Friday, January 2, 2015 8:45:04 AM UTC-6, Jim Lehmer wrote:

 On Thursday, January 1, 2015 6:10:27 PM UTC-6, RichShumaker wrote:

 I love your bottom TW5 reference.
 I couldn't click it although TiddlyWiki 5 seems like a link.


 Hmmm...In the words of every developer everywhere, It works for me. :)

 I use Cloudflare to protect/CDN my site and wonder if it is getting in the 
 way somehow? Could you do me a favor? In your browser do a View Source 
 and see if the link in the footer section looks like this?

 a class='tc-tiddlylink-external' href='http://tiddlywiki.com/' 
 target='_blank'TiddlyWiki5/a


 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 http://groups.google.com/group/tiddlywiki.
For more options, visit https://groups.google.com/d/optout.

[tw] [TW5] New plugin for generating sitemap.xml for static sites

[Jim Lehmer]

I cloned off my ATOM feed plugin and created one for generating a 
*sitemap.xml* http://www.sitemaps.org/protocol.html file. I have verified 
the results on my web site http://dullroar.com/ successfully against 
Google Webmaster tools. You can see the resulting file here 
http://dullroar.com/sitemap.xml.

I have submitted it to Google as well as updated my *robots.txt *file to 
point to it (I have my *robots.txt *file in my TW and it gets output as 
part of my generate site command). For reference, my *robots.txt *looks 
like this http://dullroar.com/robots.txt.

You can see more about the plugin on GitHub 
https://github.com/dullroar/TW5-sitemap. It's still rough around the 
edges, but it works for my purposes. Note that it prioritizes the home page 
(a tiddler named Home or index, case-insensitive) and the site index (a 
tiddler named SiteIndex, case-insensitive) above other normal pages.

Comments welcome.

-- 
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 http://groups.google.com/group/tiddlywiki.
For more options, visit https://groups.google.com/d/optout.

Re: [tw] Re: Fun with Unicode and TiddlyWiki

[Jim Lehmer]

Very cool! I love bookmarklets and have written a few myself.

--
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 http://groups.google.com/group/tiddlywiki.
For more options, visit https://groups.google.com/d/optout.

Re: [tw] Re: Fun with Unicode and TiddlyWiki

[Jim Lehmer]

On 1/3/2015 12:28 PM, Eric Shulman wrote:
I've done the same thing in TWC (which also uses the @@...@@ format 
for inline CSS).  However, rather than using the somewhat obscure 
Unicode value, I just use an empty block of italics to achieve the 
same result... like this:

   @@color:red; This is NOT red @@

I think that @@ is easier to remember (and easier to type) 
than @#x2060;@


Always multiple ways to peel a wiki, yes? :)

--
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 http://groups.google.com/group/tiddlywiki.
For more options, visit https://groups.google.com/d/optout.

[tw] I must be doing something wrong...

[Jim Lehmer]

I am trying to fix the bugs in the filesystem plugin and am seeing the 
same behavior I saw while trying to develop my own plugin. Here is how I 
have set up, per the online TW dev docs 
http://tiddlywiki.com/dev/index.html#TiddlyWiki5%20Development%20Environment:


1. Forked TW5 into my own GitHub repo.
2. Cloned it down to my local machines (same symptoms occur on Windows 
and Linux boxes, so it is not that).

3. Changed into the TiddlyWiki5 directory and did /npm link/.
4. Made my changes.
5. Copied a Basic client-server edition tiddlywiki.info file into the 
root of the repo, to wit:


   {

description: Basic client-server edition,

plugins: [

tiddlywiki/tiddlyweb,

tiddlywiki/filesystem,

tiddlywiki/codemirror,

tiddlywiki/highlight

],

themes: [

tiddlywiki/vanilla,

tiddlywiki/snowwhite

]

   }

However, when I try to start TW with the following command:

node tiddlywiki --server 8083 $:/core/save/lazy-images text/plain text/html Jim

...I get the following error:

   fs.js:439

  return binding.open(pathModule._makeLong(path), stringToFlags(flags), 
mode);

 ^

   Error: ENOENT, no such file or directory 
'C:\Users\jimle_000\Dropbox\Sandbox\TiddlyWiki5\plugins\tiddlywiki\plugin.info'

at Object.fs.openSync (fs.js:439:18)

at Object.fs.readFileSync (fs.js:290:15)

at $tw.loadPluginFolder 
(C:\Users\jimle_000\Dropbox\Sandbox\TiddlyWiki5\boot\boot.js:1461:34)

at $tw.loadWikiTiddlers 
(C:\Users\jimle_000\Dropbox\Sandbox\TiddlyWiki5\boot\boot.js:1631:23)

at $tw.loadTiddlersNode 
(C:\Users\jimle_000\Dropbox\Sandbox\TiddlyWiki5\boot\boot.js:1671:27)

at $tw.boot.startup 
(C:\Users\jimle_000\Dropbox\Sandbox\TiddlyWiki5\boot\boot.js:1781:7)

at C:\Users\jimle_000\Dropbox\Sandbox\TiddlyWiki5\boot\boot.js:1950:12

at $tw.boot.decryptEncryptedTiddlers 
(C:\Users\jimle_000\Dropbox\Sandbox\TiddlyWiki5\boot\boot.js:1375:2)

at $tw.boot.boot 
(C:\Users\jimle_000\Dropbox\Sandbox\TiddlyWiki5\boot\boot.js:1948:11)

at Object.anonymous 
(C:\Users\jimle_000\Dropbox\Sandbox\TiddlyWiki5\tiddlywiki.js:13:10)

I get the same stack trace in Linux.

What am I doing wrong? I am obviously missing something.

--
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 http://groups.google.com/group/tiddlywiki.
For more options, visit https://groups.google.com/d/optout.

Re: [tw] I must be doing something wrong...

[Jim Lehmer]

On 1/2/2015 11:20 AM, Jeremy Ruston wrote:

Hi Jim

 Copied a Basic client-server edition tiddlywiki.info 
http://tiddlywiki.info file into the root of the repo, to wit:


That's the problem: you're trying to re-use the TiddlyWiki repo as a 
wiki folder. You should either create your wiki folder separately, or 
put it in the 'editions' folder.


That did it. I knew I was misunderstanding something. 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 http://groups.google.com/group/tiddlywiki.
For more options, visit https://groups.google.com/d/optout.

Re: [tw] Re: ATOM feed now a plugin

[Jim Lehmer]

On 1/2/2015 6:29 PM, Mat wrote:
I get at least half of my news via the Feedly reader (and I'm but a 
young lad at 41). I just subscribed to your channel and, by the way, 
and I agree it should probably support /content/ elements for a full 
feed experience ;-)

And I +1 that other point about permalinks too.


I was a grandfather at 41. :)

I have those two issues logged in the project on GitHub and plan on 
implementing them, although frankly getting the content element right 
for all types of tiddlers (images, Markdown, etc.) fills me with fear, 
which is one of the reasons I've delayed it. :)


Right now I am struggling with another issue with the plugin (trying to 
move it to my a dullroar namespace per the docs), and finding that I 
am still not quite there yet on understanding how it all ties 
together. Sigh. Two steps forward, 1. steps back.


Here's a nice read on RSS vs Twitter. 
http://thenewsprint.co/2014/02/06/rss-vs-twitter/I don't know if it 
is Don Quijote fighting new tech but the article is only a year old 
and statements like the following do make me buy:


I don't disagree. I love RSS/ATOM. It is open (+1), it alerts me of 
updates in things I care about (+1), it has lots of clients available 
thanks to Furrygoat's law 
http://www.furrygoat.com/2005/05/15/furrygoats-law/ (+1), and it 
allows me to pay attention to it only when I want to (+1). And like the 
author of that article, I too, unsubscribed to most things years ago, 
and only subscribe to sites/authors who I either know personally or are 
very carefully curated not to waste my time (it was part of a bigger 
move on my part to reach inbox zero, which I've been at for about four 
years now).


--
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 http://groups.google.com/group/tiddlywiki.
For more options, visit https://groups.google.com/d/optout.

Re: [tw] Re: Color highlighting in a snippet of code

[Jim Lehmer]

On Friday, January 2, 2015 4:22:48 AM UTC-6, Jeremy Ruston wrote:

 That's looking really good, well done. I just noticed that I don't think 
 tiddlywiki.com links to any of your stuff; is http://dullroar.com the 
 best place to link to?


Thanks. Just noticed there was one slight bug on that page and fixed it 
this morning. It was actually quite a challenge to get everything formatted 
right for both TW and the resulting HTML output! In fact there was a few 
tricks I did in a couple of places that aren't immediately apparent upon 
casual inspection that may warrant an article in itself.

Actually, use http://dullroar.com/tiddlywiki5.html, because that's a page 
contains links to all articles I tag with *tiddlywiki5*. For example, I 
plan on converting a few more posts I wrote here on my journey to how-to 
pages there and will tag them appropriately.

-- 
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 http://groups.google.com/group/tiddlywiki.
For more options, visit https://groups.google.com/d/optout.

[tw] Re: Color highlighting in a snippet of code

[Jim Lehmer]

On Thursday, January 1, 2015 6:10:27 PM UTC-6, RichShumaker wrote:

 I love your bottom TW5 reference.
 I couldn't click it although TiddlyWiki 5 seems like a link.


Hmmm...In the words of every developer everywhere, It works for me. :)

I use Cloudflare to protect/CDN my site and wonder if it is getting in the 
way somehow? Could you do me a favor? In your browser do a View Source 
and see if the link in the footer section looks like this?

a class='tc-tiddlylink-external' href='http://tiddlywiki.com/ 
view-source:http://tiddlywiki.com/' target='_blank'TiddlyWiki5/a


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 http://groups.google.com/group/tiddlywiki.
For more options, visit https://groups.google.com/d/optout.

[tw] Re: ATOM feed now a plugin

[Jim Lehmer]

On Thursday, January 1, 2015 5:53:31 PM UTC-6, HansWobbe wrote:

 So what has the techie crowd moved on to?  I'd hate to attract their 
 attention accidentally, just by letting someone see that I still rely on 
 feeds. :-)


From what I can tell they have moved on to captive apps on their phones 
that are receiving pushes of pertinent updates. And I use the word 
captive for a reason. :) 

-- 
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 http://groups.google.com/group/tiddlywiki.
For more options, visit https://groups.google.com/d/optout.

[tw] Re: ATOM feed now a plugin

[Jim Lehmer]

Just put up another bug fix, for correctly formatting URLs of tiddlers with 
spaces in their names.

-- 
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 http://groups.google.com/group/tiddlywiki.
For more options, visit https://groups.google.com/d/optout.

[tw] Color highlighting in a snippet of code

[Jim Lehmer]

This is old news for veterans, I am sure, but thought I would pass this 
along in case anyone else hits it. Let's say you have a tiddler that 
displays a code block (you're writing an article on some coding technique 
or whatnot):

```
var foo = 1;
var bar = gonculate(foo);
alert(bar);
```

Which renders like:

var foo = 1;
var bar = gonculate(foo);
alert(bar);

Now you want to show a change, highlighting the changed part in red, like 
so:

var foo = 1;
var bar = xyzzy(foo);
alert(bar);

How do you do that in TW?

Well, you can't use the three back ticks any more, because that would make 
the *@@color:red; *wikitext (or *span style-color:red*) show up as 
code, e.g.,

```
var foo = 1;
var bar =@@color:red; xyzzy(foo)@@;
alert(bar);
```

...renders as:

var foo = 1;
var bar =@@color:red; xyzzy(foo)@@;
alert(bar);

Not what we want.

You also can't use the single back tick ` at the beginning and end of the 
entire block, because everything in that inline code style has red text 
already.

Instead, you simply use the HTML *pre *element, which has most of the 
same styling you already need for a wikitext code block. Then you can use 
*@@color:red; 
*(or *span style-color:red*) just fine:

pre
var foo = 1;
var bar =@@color:red; xyzzy(foo)@@;
alert(bar);
/pre

...renders as:

var foo = 1;
var bar = xyzzy(foo);
alert(bar);

Problem solved.

*HOWEVER: *If your sample code has HTML or TW widgets with angle brackets, 
you have to take another step and make sure all the starting angle 
brackets are escaped into the HTML* lt; *entity, or else they will be 
interpreted by TW during rendering because they are no longer fenced by 
```. In other words, if you have something like:

```

$view field=modified format=relativedate/
```

...which renders as:

$view field=modified format=relativedate/


...and you now want to show a change in part of it, you have to escape the 
opening angle bracket as follows:

pre

lt;$view field=modified@@color:red; format=date template=DDD, MMM DD, 
@@/
/pre


...to get:

$view field=modified format=date template=DDD, MMM DD, /


Just thought I would pass this along. I may make an article out of it on my 
site, but was thinking it could use a tiddler somewhere on the wikitext 
help pages to help newcomers.

-- 
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 http://groups.google.com/group/tiddlywiki.
For more options, visit https://groups.google.com/d/optout.

[tw] Remember kids, file names are case insensitive on Windows

[Jim Lehmer]

TW will alllow you to create both a *Foo *tiddler and a *foo *tiddler, but 
if you're running under node on Windows, whichever one is saved last will 
be the sole contents of the single *foo.tid *file. I am sure it has been 
discussed before but it bit me today and shouldn't have, because I am 
ancient and have seen this same behavior in different software in the hoary 
past (like how Java used to mishandle class name to file name mapping back 
in the day).

Question: Should TW even allow this behavior in the first place, i.e., if 
you create a tiddler *Foo *and then try and create a second tiddler *Foo*, 
you will get a popup asking if you want to overwrite *Foo*. However, if you 
create *Foo *and then create *foo*, it will allow that, and silently 
overwrite the underlying *Foo.tid *file. This seems very unfriendly, and 
would likely cause confusion for non-technical users (although would they 
be running node? :)

-- 
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 http://groups.google.com/group/tiddlywiki.
For more options, visit https://groups.google.com/d/optout.

[tw] Re: Color highlighting in a snippet of code

[Jim Lehmer]

As promised, I made this post a page on my site:

http://dullroar.com/Color%2520highlighting%2520in%2520a%2520snippet%2520of%2520code.html

-- 
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 http://groups.google.com/group/tiddlywiki.
For more options, visit https://groups.google.com/d/optout.

[tw] Re: ATOM feed now a plugin

[Jim Lehmer]

Actually, my goals were a lot simpler than that. I am currently using TW as 
an editor for my web site http://dullroar.com/Home.html, and then 
generate a static set of pages from it. Since my site used to host my blog, 
I was wanting a feed that could alert of changes and updates by 
subscribing to http://dullroar.com/atom.xml for anyone who still uses a 
feed reader in this day and age (I do, but at age 54 I expect the tech 
tribe to push me out on the ice floe any day now :). That was my sole use 
case.

However, I am willing to consider fleshing it out more. For example, while 
the plugin works in-browser, the feed it generates presumes a static set of 
pages and not TW permalinks. That is probably broken and I need to fix it 
(I have created an issue for that 
https://github.com/dullroar/TW5-atomfeed/issues/1). Also, right now it 
supports the *summary *element in ATOM but not the *content *element (in 
other words, it doesn't allow a full feed with all the tiddler content 
but simply a set of tiddler titles and links). I have created an issue for 
that, too https://github.com/dullroar/TW5-atomfeed/issues/2.

On Thursday, January 1, 2015 11:04:29 AM UTC-6, Mat wrote:

 Thanks for sharing Jim! I'm not so versed in these things so I hope it's 
 ok with some basic question:

 Is the purpose of this all to get a way to check+collect tiddlers from 
 whole tiddlywikis, set up in (exclusively) node.js and on any public server?

 Assuming it is (sounds fantastic!!!) - would this allow for a user to have 
 this feed inside a TW and have updaes on external Tiddlywikis automatically 
 be reflected in the users TW? Are tiddlers actually imported (sounds 
 dangerous) or how are things actually expressed/manifested?

 I'm hoping for some method that could be used for what I describe here 
 https://groups.google.com/d/msg/tiddlywikidev/NlPZwuoSsJk/pdkUlK1bocwJ, 
 i.e for a user to have a tiddler that behaves like a live channel either to 
 a specific other TW and that allows for filtering somewhere along the line 
 so to only get the relevant new information (perhaps tiddlers tagged in a 
 specific way) or, even, that this live channel gathers updates from 
 multiple places but, ideally, presented in a user defined way (maybe 
 wrapped inside some CSS).

 Is your ATOM feed something that is relevant for these thoughts? 

 And would it put demands on the provider other than, if I get your 
 right, that he has his TW in node.js form?

 Thank you again, Jim!

 :-)

 Thank 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 http://groups.google.com/group/tiddlywiki.
For more options, visit https://groups.google.com/d/optout.

[tw] Re: Node.js

[Jim Lehmer]

On Tuesday, December 30, 2014 9:26:21 PM UTC-6, Handoko Suwono wrote:

 Is there any introductory note on Node.js and how is it related to TW?


Yes. Start here: http://tiddlywiki.com/#TiddlyWiki%20on%20Node.js 

-- 
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 http://groups.google.com/group/tiddlywiki.
For more options, visit https://groups.google.com/d/optout.

[tw] Re: Cornell's Note Taking Method

[Jim Lehmer]

On Wednesday, December 31, 2014 9:14:31 AM UTC-6, Jeremy Ruston wrote:

 It struck me as an interesting idea for TiddlyWiki. There's been interest 
 in the past in using TiddlyWiki to create and present quizzes; perhaps we 
 can explore creating the necessary features in a way that supports 
 notetaking too.


Has anyone made a view template that can present tiddlers in columns? I am 
not talking about tables - I think that would be too unwieldy to do in real 
time while taking notes. But instead, since you can have multiple tiddlers 
open for edit at the same time, if there was a way to show the story river 
in two columns instead of one you could have two open at the same time for 
edit. Then when studying you wouldn't need to cover up the notes tiddler, 
but instead simply close it... 

-- 
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 http://groups.google.com/group/tiddlywiki.
For more options, visit https://groups.google.com/d/optout.

[tw] Re: ATOM feed now a plugin

[Jim Lehmer]

Just posted a small bug fix. I was relying on *$:/status/UserName *to set 
ATOM's *author *element, but that only works when running in the 
browser/served from node, and not when generating a static site from the 
command line (which is really the whole point). So for now I am simply 
using the creator field from the most recently modified article tiddler 
(a tiddler that has been tagged, which is what I want for my use, anyway).

Was wondering if I could have used the *SetField *command instead to set 
*$:/status/UserName 
*in the command stream, but didn't want to rely on the end user having to 
know to do that.

-- 
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 http://groups.google.com/group/tiddlywiki.
For more options, visit https://groups.google.com/d/optout.

[tw] Static site is working...

[Jim Lehmer]

Well, with my ATOM plugin working, I have completed the road map I laid out 
a few weeks ago:

Following is my road map from the other thread, with progress comments:

1. A *simple* sidebar - title, subtitle, simple TOC with categories 
(tags).

2. Get the tag buttons working, per my Javascript post a while back.

3. A set of pass through tiddlers for things like an .htaccess file, 
favicon.ico, CSS, Javascript I am going to want to embed, etc.

4. ATOM feed.

Results viewable at http://dullroar.com. It ain't fancy, but it suits my 
purposes for now, which are:

1. To have an easy-to-edit mechanism for generating pages on my site.

2. Accessible from both my Windows and Linux laptops (I have the source TW 
in a Dropbox folder shared between those machines with node running on 
both), so that no matter where I am and with whatever machine, I can 
quickly edit and upload.

-- 
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 http://groups.google.com/group/tiddlywiki.
For more options, visit https://groups.google.com/d/optout.

[tw] Re: Cornell's Note Taking Method

[Jim Lehmer]

On Wednesday, December 31, 2014 11:54:40 AM UTC-6, Jeremy Ruston wrote:

 A multi-column view for the story river is something I'm interested in 
 adding.


That would be good. On wide/HD displays especially the two column approach 
currently in place wastes a lot of real estate.

I can think of the following cases for having a more grid-like approach 
to TW:

1. *n *columns all for the story river, a la Tumblr or Pinterest.
2. Being able to pin certain things to certain columns. For example, it 
would be nice to have three columns (or more) with the following abilities:
a. The ability to have any one of them be the current title/control 
panel/TOC/utility column.
b. The ability to have any one of them be a set of pinned tiddlers that 
you always want open and displayed by default. This could be done via a 
filter or else even a new drop down action of pin to this column (which 
then means needing a way to open a specific tiddler in a specific column in 
the first place).
c. The ability to have any one of them be the story river.
 
I think a and b would end up being basically the left and right hand 
columns with the story river in the center, but architecturally I can't 
think of why it would need to be limited that way.

However, here it may be possible to approach it differently: one could 
 imagine a split-screen arrangement like the current preview pane. One side 
 for the notes, one side for the questions. The questions would be stored in 
 a field.


Yeah, I thought about that, too.

-- 
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 http://groups.google.com/group/tiddlywiki.
For more options, visit https://groups.google.com/d/optout.

[tw] ATOM feed now a plugin

[Jim Lehmer]

What am I doing on my Christmas break? Well, I've read all the TW dev 
documentation http://tiddlywiki.com/dev/index.html as well as all of the 
code in *boot.js *(plus some of the core code as I was trying to figure 
various things out). And now I have successfully taken my ATOM feed code 
and made it into a plugin. I have also parameterized more of it, so it is 
not quite as hardcoded as it was before. You can check it out here: 
https://github.com/dullroar/TW5-atomfeed. The readme should help explain 
most of it.

https://github.com/dullroar/TW5-atomfeedComments appreciated.

Jeremy, one thing that caused me some headaches are the instructions at 
http://tiddlywiki.com/dev/index.html#Developing%20plugins%20using%20Node.js%20and%20GitHub.
 
I tried to namespace it per the instructions, i.e., 
*plugins/dullroar/atomfeed*, but *boot.js *didn't like that because it is 
looking for *plugin.info *in each child directory directly under *plugins *and 
doesn't seem to recurse any deeper than that, so it would throw an 
exception in *loadPluginFolder *at this line:

var pluginInfo = JSON.parse(fs.readFileSync(filepath + path.sep + 
plugin.info,utf8));

...because it couldn't find *plugin.info *in *plugins/dullroar*. So I ended 
up just moving the *atomfeed *folder up one to *plugins/atomfeed*. What 
was I doing 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 http://groups.google.com/group/tiddlywiki.
For more options, visit https://groups.google.com/d/optout.

Re: [tw] [TW5] How best to approach an external dependency?

[Jim Lehmer]

On Wednesday, December 24, 2014 2:28:26 AM UTC-6, Jeremy Ruston wrote:

 One option might be to use the built-in Stanford JavaScript Crypto Library 
 that we use for handling encrypted TiddlyWikis:

 http://bitwiseshiftleft.github.io/sjcl/

 It works in the browser and under Node.js. You can call it like this:

 var sjcl = $tw.node ? require(./sjcl.js) : window.sjcl;

 var myHash = sjcl.codec.hex.fromBits(sjcl.hash.sha256.hash(myMessage))


Thanks.

For my (very specific) purposes I needed MD5 because I needed a 128-bit 
value to turn into a pseudo-GUID. I ended up adapting some MD5 code I found 
with a very open license into my ATOM plugin as a library (and a macro that 
uses the library). And that process answered my more general question of 
how to use such resources in TW (by turning them into a library, for 
example).

-- 
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 http://groups.google.com/group/tiddlywiki.
For more options, visit https://groups.google.com/d/optout.

[tw] Re: javascript macro / macrocall problem

[Jim Lehmer]

On Monday, December 29, 2014 3:18:48 PM UTC-6, Stephen Kimmel wrote:

 In the general category of I don't know what I did to make the problem go 
 away but... 

 I've got it working now. I suspect there is something flaky about how some 
 of the browsers handle javascript. 

 Thanks again, Eric for your help.


I have noticed as I work through building my own macros that sometimes 
reloading the TW (or restarting TW under node) will cause code changes to 
be picked up that weren't before. So I've kinda gotten into doing it 
automatically as sort of a Wave a dead chicken over it superstitious 
practice. 

-- 
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 http://groups.google.com/group/tiddlywiki.
For more options, visit https://groups.google.com/d/optout.

[tw] [TW5] How best to approach an external dependency?

[Jim Lehmer]

I am working on my Atom feed exporter, with the hope of eventually making 
it a plugin. Right now it works using the *rendertiddler *command under 
node, and in fact is depending on a node library (crypto) being in place. 
This is because the Atom spec http://www.ietf.org/rfc/rfc4287.txt 
requires an id (a GUID) for each article (tiddler) in the feed:

4.2.6.  The atom:id Element

   The atom:id element conveys a permanent, universally unique
   identifier for an entry or feed.

...

   When an Atom Document is relocated, migrated, syndicated,
   republished, exported, or imported, the content of its atom:id
   element MUST NOT change.  Put another way, an atom:id element
   pertains to all instantiations of a particular Atom entry or feed;
   revisions retain the same content in their atom:id elements.  It is
   suggested that the atom:id element be stored along with the
   associated resource.

   The content of an atom:id element MUST be created in a way that
   assures uniqueness.


I decided to use an MD5 hash of each tiddler's title to generate a 128-bit 
hash, which I then format into a GUID. It works quite well, and I think for 
most foreseeable cases satisfies the spec. I did some research and then 
decided to use node's crypto package, since it had an implementation of MD5 
with an easy API. All is good.

However, when I *browse *to my TW (the original, not the generated static 
output or feed) as opposed to running *commands *on it under node, it gives 
an error at start-up in my module which ultimately I traced down to the 
require(crypto) statement because node's crypto package is not available 
when running in the browser (which makes sense). I could probably do some 
work in my module to try and detect whether it's running in the browser or 
under node and just export an empty *run *method when in the browser 
environment, but that would invalidate one of Jeremy's wishes, which is 
ultimately to be able to generate a feed under a browser-only TW.

So, I see a few possibilities, and want to ask which way is the TW way? 
Jeremy, I'm especially looking from feedback from you on this. I have this 
specific use-case, but am also interested in general to the TW approach to 
external dependencies and libraries.

1. Figure out another way to reliably generate those GUIDs in a repeatable 
manner (same tiddler always gets the same id). Definitely doable, but I 
hate reinventing wheels.

Pros: Eliminates external dependencies.
Cons: Reinvents wheel.

2. Copy in the appropriate pieces of the node code or someone else's open 
source implementation (with an OSS license that explicitly allows that - 
node's seems to), presumably into TW's crypto module.

Pros: Wheel already invented, TW's crypto module probably needs some 
expansion over time anyway.
Cons: Still maintaining another copy of code, cut  paste programming at 
its worse, with all that implies, including maintenance in case of bugs 
upstream, etc.

3. Build TW with the node crypto module included somehow - waving arms here 
a bit.

Pros: Wheel already invented.
Cons: Requires node, but that's already a requirement, anyway?

4. ???Something else??? I note that the *utils *module has a *hashString 
*function 
exported, but it's only a simple 32-bit hash with high possibility of 
collisions. It looks like TW2 had SHA1 hashing code, but (a) that appears 
to be unused except for creating a classic TW edition, and (b) that's a 
160-bit hash, not the 128-bits I would need. Other possibilities? Something 
I'm missing (likely)?

Comments and discussion 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 http://groups.google.com/group/tiddlywiki.
For more options, visit https://groups.google.com/d/optout.

[tw] Re: [TW5] Displaying article dates on a static site

[Jim Lehmer]

On Sunday, December 21, 2014 9:56:18 PM UTC-6, Suzanne McHale wrote:

 Just did this to mine - much better! But when I upgrade my TW, will the 
 changes be overwritten?


That's a good question. So far when I have upgraded TW under node my 
overrides to shadow tiddlers have stayed, but I am not sure if that is 
always the case. However, in this case because of the way the subtitle 
tiddler is used in the templates, I am not sure there is a better way to do 
it without cloning out a whole bunch of other tiddlers to static versions 
and then trying to keep them up to date with each update. I do plan on 
cloning *$:/core/templates/static.tiddler.html* into a new tiddler and 
using that in the *rendertiddlers *command (because there the template gets 
passed by name), and reverting the *$:/core/templates/static.tiddler.html *back 
to its default. But I am unsure how to do something similar with 
*$:/core/ui/ViewTemplate/subtitle 
*without also cloning what depends on it. But I am heartened because it 
does seem like some of this type of editing is sanctioned, at least for the 
*$:/core/ui 
*tiddlers 
http://tiddlywiki.com/#Page%20and%20tiddler%20layout%20customisation (see 
link).

-- 
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 http://groups.google.com/group/tiddlywiki.
For more options, visit https://groups.google.com/d/optout.

[tw] Re: [TW5] Tag buttons on static sites

[Jim Lehmer]

On Sunday, December 21, 2014 4:04:55 AM UTC-6, Tobias Beer wrote:

 Not sure if I'm missing something, but your current version does not yet 
 have any jQuery loaded, does it?


If you're talking about my public site, no, I haven't uploaded the new, 
jQuery-enabed pages there yet, because I am not sure I am completely happy 
with this approach yet.
 

 I like jQuery, so that's not it... but I would sure prefer for a tag 
 button in a static page to work as a simple link to a tiddler. Can't 
 there be the kind of progressive enhancement, whereas the default would be 
 to have it work as a simple link, yet within TiddlyWiki it would be a 
 smart tag-pill?

 The full-blown solution would be that static-site generation would even 
 generate static-tiddlers for non-existing tags, outputting a tagging list.


I concur, that is the best way to go, because then I don't have to remember 
to create a tiddler for every tag to have a static HTML landing page for 
it. I actually started going down that path first, and may return there at 
some point, but right now I am amusing myself trying to adapt a copy of the 
alltiddlers template into an ATOM feed. :)

-- 
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 http://groups.google.com/group/tiddlywiki.
For more options, visit https://groups.google.com/d/optout.

[tw] [TW5] Generating an Atom feed for a static site

[Jim Lehmer]

[Ongoing static blogging generator saga.]

I have a first pass at generating an Atom feed working (Feeds are dead! 
Long live feeds! :) ). I don't have it uploaded to my public site yet, but 
thought I'd share what I've done so far, since it is working in my local 
test environment. I based everything on looking at how the *JsonFile* 
exporter worked. I figured an XML file exporter would be similar (and it 
was).

*Step 1.*

Created an *XmlFile *tiddler, based on the *JsonFile *tiddler. Here are the 
contents of the tid file. Note the *extension *field and the *$:/tags/Exporter 
*tag. Also note the call to an *xmltiddlers *macro.

created: 20141221144856475
creator: Jim
extension: .xml
modified: 20141221173406629
modifier: Jim
tags: static $:/tags/Exporter
title: XmlFile
type: text/vnd.tiddlywiki

\define renderContent()
$text text=xmltiddlers filter:$(exportFilter)$/
\end
renderContent

*Step 2.*

Created an *xmltiddlers.js *macro tiddler using the *jsontiddlers.js *macro 
as a starting point. There is lots of stuff going on here. I have placed /// 
comments below where I think it needs exposition beyond the normal TW macro 
code conventions, which are pretty well documented already.

created: 20141221145616722
creator: Jim
modified: 20141221181223993
modifier: Jim
module-type: macro
tags: static
title: xmltiddlers.js
type: application/javascript

/*\

Macro to output tiddlers matching a filter to XML (ATOM, specifically)

\*/
(function(){

/*jslint node: true, browser: true */
/*global $tw: false */
use strict;

/*
Information about this macro
*/

exports.name = xmltiddlers;

exports.params = [
{name: filter}
];

/// We're going to use Node's crypto lib to generate MD5 hashes of tiddler 
titles because we can then use
/// those to generate GUIDs for Atom's id elements, which are required for 
each entry.
var crypto = require(crypto);

/// The following should probably actually be a separate exported module if 
it is to be more utilitarian in nature.
var XML = {};

/// Make sure embedded , , ,  and ' characters are turned into their 
proper XML entities when embedding TW
/// content into an XML element.
XML.escapify = function(input) {
return input.replace(//gm, lt;).replace(//gm, 
gt;).replace(//gm, amp;).replace(//gm, quot;).replace(/'/gm, 
apos;);
};

/// There is probably a better way to handle TW dates, but by the time this 
macro gets them they are stringified,
/// so this takes the TW date string and makes it into an ISO 8601 date. 
Ugly.
XML.twDateToISO8601 = function(twDate) {
return twDate.substring(0, 4) + - + twDate.substring(4, 6) + - + 
twDate.substring(6, 8) + T + twDate.substring(8, 10) + : + 
twDate.substring(10, 12) + : + twDate.substring(12, 14);
}

/// Here is the heavy lifting for generating each Atom entry. Comments only 
where needed.
XML.stringify = function(data) {
var x = ;

data.forEach(function(element, index, array) {
x += \t\tentry\n;
x += \t\t\ttitle + element.title + /title\n;
/// Generate 128-bit MD5 hash from tiddler title, which we then 
reformat into GUID for Atom's id element.
/// If tiddler's title changes, the hash will change, but we 
probably want that anyway.
var md5 = crypto.createHash('md5');
var md5sum = md5.update(element.title);
var md5digest = md5.digest(hex);
x += \t\t\tidurn:uuid: + md5digest.substring(0, 8) + - + 
md5digest.substring(8, 12) + - + md5digest.substring(12, 16) + - + 
md5digest.substring(16, 20) + - + md5digest.substring(20) + /id\n;
x += \t\t\tlink href='http://dullroar.com/; + 
element.title.replace(/ /g, %20) + .html' /\n;
x += \t\t\tupdated + XML.twDateToISO8601(element.modified) + 
/updated\n;
/// This is a kludge, trying to get the first 20 words of the 
tiddler as a summary. I think there could be
/// better ways, like looking for a summary field in the tiddler 
and if it exists use that instead.
var words = element.text.split(/\s/g, 20);
x += \t\t\tsummary + words.join( ) + /summary\n;
x += \t\t/entry\n;
});

return x;
}

/// Most of this is very similar to the run function in the jsontiddlers.js 
macro, other than trying to catch
/// any native JS Date objects and format them as ISO 8601 (I was hopeful 
that was how I could handle the created
/// and modified tiddler fields, but alas, no).
/*
Run the macro
*/
exports.run = function(filter) {
var tiddlers = this.wiki.filterTiddlers(filter),
data = [];
for(var t=0;ttiddlers.length; t++) {
var tiddler = this.wiki.getTiddler(tiddlers[t]);
if(tiddler) {
var fields = new Object();
for(var field in tiddler.fields) {
if (field.toISOString !== undefined) {
fields[field] = field.toISOString();
} else {
fields[field] = 
XML.escapify(tiddler.getFieldString(field

[tw] Chaining node commands in a script file

[Jim Lehmer]

This may be old hat for people more experienced than me with node and/or 
TW's CLI, but I hit something tonight that I thought I would post just in 
case it saves someone else the time to troubleshoot that it took me.

Scenario: I wanted to be able to serve my static files locally on my dev 
box after they are generated. I found node-static 
https://github.com/cloudhead/node-static, which has a nice CLI. Perfect. 
I figured if I was serving TW in edit mode off the default port 8080, I 
would want the static files served from 8081. So I did:

npm install -g node-static

...and then from my TW project directory:

static -p 8081 output/static

...and was able to browse to *http://localhost:8081/Home.html *successfully. 
Most excellent! I then tried to update my *genstatic.cmd *file to add that 
line after the *tiddlywiki *command, e.g.:

tiddlywiki --rendertiddlers [!is[system]!tag[static]] 
$:/core/templates/static.tiddler.html static text/plain --rendertiddler 
$:/core/templates/static.template.css static/static.css text/plain 
--savetiddler favicon.ico static/favicon.ico --savetiddler Feed-icon.svg 
static/Feed-icon.svg --savetiddler .htaccess static/.htaccess  
--savetiddler googled49bf9dfd179fbc6 static/googled49bf9dfd179fbc6.html 
--output output/static --rendertiddler atomfeed atom.xml text/plain
@rem The following requires node-static to be installed.
@rem npm install -g node-static
static -p 8081 output/static

*Note: *Everything from *tiddlywiki *until the first *@rem *are on one line.

But no matter what I tried, the TW command would run, and then the script 
would exit without invoking the *static *command. Frustrating.

I then got an idea and used the *start *command to start TW in a second 
window:

start tiddlywiki --rendertiddlers [!is[system]!tag[static]] 
$:/core/templates/static.tiddler.html static text/plain --rendertiddler 
$:/core/templates/static.template.css static/static.css text/plain 
--savetiddler favicon.ico static/favicon.ico --savetiddler Feed-icon.svg 
static/Feed-icon.svg --savetiddler .htaccess static/.htaccess  
--savetiddler googled49bf9dfd179fbc6 static/googled49bf9dfd179fbc6.html 
--output output/static --rendertiddler atomfeed atom.xml text/plain
@rem The following requires node-static to be installed.
@rem npm install -g node-static
static -p 8081 output/static

*Note: *Everything from *start *until the first *@rem *are on one line.

This worked! TW would run in the second window and *static *would serve the 
files. I tried to use *start*'s */wait *parameter so *static *wouldn't run 
until there was something to serve, but I still had to manually close the 
second window that TW was running under, which was a pain. I also tried the */b 
*parameter, but that reverted to the old behavior (the script would exit 
after TW was done).

Then I remember the old * *command chaining trick, and that worked. So 
now my script looks like this (especially note the part in *red*):

@rem The following requires node-static to be installed.
@rem npm install -g node-static
tiddlywiki --rendertiddlers [!is[system]!tag[static]] 
$:/core/templates/static.tiddler.html static text/plain --rendertiddler 
$:/core/templates/static.template.css static/static.css text/plain 
--savetiddler favicon.ico static/favicon.ico --savetiddler Feed-icon.svg 
static/Feed-icon.svg --savetiddler .htaccess static/.htaccess  
--savetiddler googled49bf9dfd179fbc6 static/googled49bf9dfd179fbc6.html 
--output output/static --rendertiddler atomfeed atom.xml text/plain  
static -p 8081 output/static

*Note: *Everything from *tiddlywiki *until the end of the example are on 
one line.

It's a nice way to be able to immediately test the static files and have 
them actually served instead of just clicking on files in the file system 
(which breaks things like protocol-less links, e.g., 
*href=//some.cdn.somewhere/resource*).

There are probably better ways of doing all this for those of you more 
experienced at all this than I, but in the mean time, I thought I would 
pass this along. Presumably the same technique would work under bash.

-- 
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 http://groups.google.com/group/tiddlywiki.
For more options, visit https://groups.google.com/d/optout.

[tw] Re: [TW5] Generating an Atom feed for a static site

[Jim Lehmer]

And FWIW, serving my static files using node-static 
https://github.com/cloudhead/node-static, Thunderbird was able to consume 
the *atom.xml *file as a valid feed. It is still sub-optimal because the 
summaries are sort of arbitrary, but the XML *is *valid, at least.

-- 
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 http://groups.google.com/group/tiddlywiki.
For more options, visit https://groups.google.com/d/optout.

[tw] [TW5] Displaying article dates on a static site

[Jim Lehmer]

[Another post on the ongoing quest for a static site.]

One of the other things I've had to override is the subtitle behavior on 
tiddlers. On a normal TW, when you create a new tiddler and save it, the 
subtitle will read something like Jim 1 second ago, that is, the last 
modified time is displayed as a relative date. It then ages over a period 
of minutes, hours, days and weeks and so on (see *getRelativeDate *in 
*utils.js*). The problem with that behavior on a static site is that it is 
frozen in time when you generate. If a given tiddler was showing 1 hour 
ago when you generated the static pages, then the resulting static HTML 
page will *always *show 1 hour ago, forever. Which is probably not what 
you want.

To get around that, I overrode the shadow *$:/core/ui/ViewTemplate/subtitle* 
tiddler, which looks like this out of the box:

div class=tc-subtitle
$link to={{!!modifier}}
$view field=modifier/
/$link $view field=modified format=relativedate/
/div

I changed the *$view *of the *modified *field as shown below in *red* to 
always show a date in Thursday, November 27, 2014 format:

div class=tc-subtitle
$link to={{!!modifier}}
$view field=modifier/
/$link $view field=modified format=date template=DDD, MMM DD, 
//div

Problem solved.

-- 
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 http://groups.google.com/group/tiddlywiki.
For more options, visit https://groups.google.com/d/optout.

[tw] [TW5] Tag buttons on static sites

[Jim Lehmer]

[This presumes you've been following my saga on using TW5 as a static 
blogging engine replacement.]

So, one of my beefs has been that tag buttons on static pages are given 
the finger, that is, the mouse pointer indicates they're clickable but 
clicking on them doesn't do anything because the navigation logic has been 
stripped (since the static site, by definition, doesn't have all the chewy 
goodness of the TW script environment). I think that is bad behavior. I 
could change the static CSS, obviously, but really, I *do *want the tags to 
be clickable.

I had originally thought of trying to update the static template to 
override the tag *button *elements output for each tiddler with *a 
*elements 
that are styled the same as the buttons, but I got lost in the forest of 
macros, templates, inclusions and whatnot. I still think ultimately that is 
the way to go (especially if by static you mean pure HTML/CSS with no 
Javascript, although that is not necessarily what I mean as I pursue this 
project - I will almost assuredly use some scripting in the output).

In the interim I have cheated, as follows:

1. For every tag where I want this clickable behavior (which doesn't 
include the toc tag, for example, for tagging things that I want in the 
TOC), I have created a tiddler with the same name, e.g., for the tech tag 
there is a tiddler named tech that has the following content:

list-links filter:[tag[tech]]

2. I have also created a Categories tiddler that I use in the sidebar TOC 
to have a quick jump to a list of *all *the tag pages. Its contents:

list-links filter:[is[tag]]

3. You can already see all this in action on my site http://dullroar.com. 
Nothing new there since my last post.

4. The thing I added in my local testing today was the following to the 
bottom of my override of *$:/core/templates/static.tiddler.html*. The new 
content is what I inserted between the closing */body *and */html* HTML 
tags:

`/body
script src=http://code.jquery.com/jquery-1.11.2.min.js;/script
script src=http://code.jquery.com/jquery-migrate-1.2.1.min.js;/script
script$(document).ready(function() {
  $(button.tc-tag-label).on(click, function() {
window.location.href = $(this).text().trim()+.html;
  });
});
/script
/html
`

It ain't the TW way, I know, but it *does *work. It simply requires there 
to be a static HTML page generated per tag (see #1).

*Note: *I added the http: to the front of each link to the jQuery CDN 
because otherwise it doesn't load the libs when you're testing by just 
clicking on the generated static *.html *files in your local file system 
(as opposed to running them under a web server). In production I will go 
back to just the //code.jquery.com/jquery-1.11.2.min.js style URLs 
preferred by the jQuery site 
http://jquery.com/download/#using-jquery-with-a-cdn, because that will 
help serve it with no warnings whether my site is being access via HTTP or 
HTTPS.

Anyway, I thought I would share my progress (which hasn't been much of 
late, due to other demands on my time). Comments appreciated, especially 
pointing to what would be a more TW-compliant way to get what I want out of 
the static template.

-- 
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 http://groups.google.com/group/tiddlywiki.
For more options, visit https://groups.google.com/d/optout.

[tw] Progress on static site generation with TW5

[Jim Lehmer]

Thanks to Jeremy's help (tug o' the forelock in thanks), I now have the TOC 
generating correctly in a static sidebar. You can see the very limited 
results so far here http://dullroar.com/Home.html.

Following is my road map from the other thread, with progress comments:

1. A *simple* sidebar - title, subtitle, simple TOC, a tag cloud *that 
works* (more on that in a bit), some other fixed text (copyright, pointer 
to TW, etc., so that isn't repeated in every tiddler).

I have title, subtitle and TOC working. I have moved the fixed IP text to 
a proper footer element in the template (instead of the sidebar), which is 
also ultimately where the TW link will go.

2. Per the TOC, I am not looking for a fancy one that expands and contracts 
- for now I am working on the idea that static remains just that, and 
doesn't have any or much of the TW Javascript magic in it. I have made some 
other tiddlers, like one called Categories, that is actually an auto list 
of tags, So, if the TOC has Home, Categories, and a few other things, 
that's enough. I can hide the complexity behind tiddlers the TOC then 
points to to do the heavy lifting that the expandable TOC does in a 
live TW.

This is working. The TOC is currently only two components - one pointing to 
Categories (which are actually a tag substitute) and a link pointing back 
to the Home page.

3. Get the tag buttons working, probably by generating them not as buttons 
but as links that are styled the same as the buttons. Personally, I believe 
the behavior of the current static template (which generates the buttons 
with CSS that causes them to receive the clickable pointer when you hover 
over them but that do nothing when you click on them) to be a bug in the 
static CSS if nothing else.

This is where I am concentrating now. I can already tell it is not going to 
be easy. My ultimate goal is two-fold:

3.a Tag buttons in each tiddler/page should actually work.

3.b I would like a simple tag cloud in the side bar.

4. I already have a set of tiddlers that I ignore in the main 
rendertiddlers via a filter and then pass through using savetiddler for 
things like an .htaccess file, favicon.ico, CSS, Javascript I am going to 
want to embed, etc. That all works just fine. The details are here 
http://dullroar.com/Static%2520Pages%2520How-To.html, which are just an 
expansion of the static example on the TW5.com site.

The .htaccess file is to set Home.html as the default page, so I don't have 
to have a lame index tiddler to be picked up as index.html. The favicon 
works, etc.

5. I figure I will copy and adapt the alltiddlers template to generate an 
ATOM/RSS file (I believe someone already did that for classic TW, but 
haven't seen that for TW5).

This is my lowest priority, but will still be a good thing to work out.

If I can get all of the above working, I think that's a minimum for a good 
static site generator that can be a simple blog engine aimed at the likes 
of Pelican, Bloxsom, et al.

Comments welcome.

-- 
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 http://groups.google.com/group/tiddlywiki.
For more options, visit https://groups.google.com/d/optout.

Re: [tw] [TW5] Getting a TOC in the sidebar of static pages...

[Jim Lehmer]

That, in fact, did work. Thanks.

I support your recent effort to spend December doing more documentation, 
because frankly I have spent probably somewhere between 20 and 30 hours 
trying to figure this out over the course of two weeks, including profiling 
code, reading code, doing code searches, etc. I consider myself reasonably 
technical (programmer since 1986, architect since 1996) and I don't know 
that I would have *ever *figured that out (I was absolutely *sure *it was 
because of the *tv_wikilinks *macro after reading the code that uses it, 
and had spent the last few hours trying to hunt down where it was getting 
set to no with obviously no success, since that wasn't the issue).

I like TW, I am impressed with it and want to use it, but I know 99% of 
people would simply have stopped about 10 days ago. I just happen to like a 
good mystery. :)

Thanks, again.

On Sunday, December 7, 2014 1:55:32 PM UTC-6, Jeremy Ruston wrote:

 Hi Jim

 My apologies for the late reply.

 When static templates are rendered, they are saved as plain text. That's 
 why the raw html in the template is enclosed in backticks, to force it to 
 be treated as text rather than interpreted as HTML when it is parsed.

 The mechanism for  including content so that the HTML tags are rendered is 
 to use $view field=text format=htmlwikified /. The easiest way to do 
 this is to put your content into a tiddler and transclude it the template 
 $:/core/templates/html-tiddler. For example:

 {{$:/static/toc||$:/core/templates/html-tiddler}}

 Where $:/static/toc contains your invocation of the toc macro.

 Let me know how it goes,

 Best wishes

 Jeremy.





 On Sun, Dec 7, 2014 at 6:41 PM, Jim Lehmer jim.l...@gmail.com 
 javascript: wrote:

 I replaced the toc macro with a single link widget and it has the same 
 behavior, i.e., it outputs the text contained in the widget, but doesn't 
 wrap it in an anchor tag.

 Reading in the documentation for the link widget, I note this:

 tv-wikilinks

 Links are suppressed if the macro tv-wikilinks evaluates to the string 
 no. For example:

 \define tv-wikilinks() no


 However, the static.tiddler.html tidder does not define that macro one 
 way or another, and even trying to redefine it with a value of yes doesn't 
 change behavior. I have searched through the npm package and found all 
 places that is set to no, but none seem relevant here.




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

-- 
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 http://groups.google.com/group/tiddlywiki.
For more options, visit https://groups.google.com/d/optout.

Re: [tw] [TW5] Getting a TOC in the sidebar of static pages...

[Jim Lehmer]

Some progress. First I moved the opening (but not the closing) 
$importvariables widget to just after the body tag, followed by the toc 
macro. Then I ended up duplicating the $importvariables widget (open and 
closing tags) to there and sticking the toc macro in between. In either 
case I get some progress, but not quite, in that I now get the display text 
for the TOC links, but nothing else (it is just text - no HTML tags or 
anything). I also tried a list and link widgets with basically the same 
result (which isn't surprising, since by my poking around that's what the 
TOC macro resolves to anyway under the covers). So, closer, but not quite 
there.

Will keep poking and prodding. I really want this to work.

-- 
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 http://groups.google.com/group/tiddlywiki.
For more options, visit https://groups.google.com/d/optout.

Re: [tw] [TW5] Getting a TOC in the sidebar of static pages...

[Jim Lehmer]

On Thursday, December 4, 2014 8:22:14 AM UTC-6, Jeremy Ruston wrote:

 Hi Jim

 Terrific. Can you share where you've got?

 Many thanks

 Jeremy


Following, although I've been trying to figure all this out on my own 
because it feels like cheating to keep asking Dad for help. :)

\define tv-wikilink-template() $uri_doubleencoded$.html
\define tv-config-toolbar-icons() no
\define tv-config-toolbar-text() no
\define tv-config-toolbar-class() tc-btn-invisible
$importvariables filter=[[$:/core/ui/PageMacros]] 
[all[shadows+tiddlers]tag[$:/tags/Macro]!has[draft.of]]
`!doctype html
html
head
meta http-equiv=Content-Type content=text/html;charset=utf-8 /
meta name=generator content=TiddlyWiki /
meta name=tiddlywiki-version content=`{{$:/core/templates/version}}` /
meta name=format-detection content=telephone=no
link id=faviconLink rel=shortcut icon href=favicon.ico
link rel=stylesheet href=static.css
title`{{$:/core/wiki/title}}`/title
/head
body class=tc-body
`{{$:/StaticBanner||$:/core/templates/html-tiddler}}
`div class=tc-sidebar-scrollable style=overflow: auto;
div class=tc-sidebar-header
`$reveal state=$:/state/sidebar type=match text=yes default=yes 
retain=yes
`h1 class=tc-site-title`$transclude tiddler=$:/SiteTitle 
mode=inline/`/h1
div class=tc-site-subtitle`$transclude tiddler=$:/SiteSubtitle 
mode=inline/`/div
div class=tc-table-of-contents
`toc toc
`/div
`/$reveal
`/div
/div
section class=tc-story-river
`$view tiddler=$:/core/ui/ViewTemplate format=htmlwikified/
/$importvariables`
/section
/body
/html
` 

-- 
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 http://groups.google.com/group/tiddlywiki.
For more options, visit https://groups.google.com/d/optout.

Re: [tw] [TW5] Getting a TOC in the sidebar of static pages...

[Jim Lehmer]

At work, so I will keep this brief for now.

The roadmap for what I want is as follows:

1. A *simple* sidebar - title, subtitle, simple TOC, a tag cloud *that 
works* (more on that in a bit), some other fixed text (copyright, pointer 
to TW, etc., so that isn't repeated in every tiddler). I have title and 
subtitle working, am at least getting the display text for the TOC now, so 
it is an incremental journey.
2. Per the TOC, I am not looking for a fancy one that expands and contracts 
- for now I am working on the idea that static remains just that, and 
doesn't have any or much of the TW Javascript magic in it. I have made some 
other tiddlers, like one called Categories, that is actually an auto list 
of tags, So, if the TOC has Home, Categories, and a few other things, 
that's enough. I can hide the complexity behind tiddlers the TOC then 
points to to do the heavy lifting that the expandable TOC does in a 
live TW.
3. Get the tag buttons working, probably by generating them not as buttons 
but as links that are styled the same as the buttons. Personally, I believe 
the behavior of the current static template (which generates the buttons 
with CSS that causes them to receive the clickable pointer when you hover 
over them but that do nothing when you click on them) to be a bug in the 
static CSS if nothing else.
4. I already have a set of tiddlers that I ignore in the main 
rendertiddlers via a filter and then pass through using savetiddler for 
things like an .htaccess file, favicon.ico, CSS, Javascript I am going to 
want to embed, etc. That all works just fine.
5. I figure I will copy and adapt the alltiddlers template to generate an 
ATOM/RSS file (I believe someone already did that for classic TW, but 
haven't seen that for TW5).

Ultimately my goal is to get a decent but simple static site capability 
that has a useful but static sidebar and tags that work, allowing me to 
compose in TW and then with a simple command file (already in place) 
generate a static site. I think I am about 60% there given the above.

On Thursday, December 4, 2014 9:34:17 AM UTC-6, Tobias Beer wrote:

 Some questions...

 Say, there are a number of static pages. How do you intend to display the 
 toc on each page?

 The easiest way would be to just show all expanded and the current tiddler 
 perhaps highlighted.

 A more sophisticated way would be to only expand the lowest level in 
 which the tiddler resides and all those up the tree, but not 
 parent-siblings.

 If that was doable it would be perfect.

 By the way, how is this rendering done? Are you sending messages to 
 widgets in a fakedom?

 Best wishes, Tobias.


-- 
You received this message because you are subscribed to the Google Groups 
TiddlyWiki group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywiki+unsubscr...@googlegroups.com.
To post to this group, send email to tiddlywiki@googlegroups.com.
Visit this group at http://groups.google.com/group/tiddlywiki.
For more options, visit https://groups.google.com/d/optout.

[tw] Using JetBrains WebStorm's spy-js to profile TiddlyWiki 5 under node.js

[Jim Lehmer]

While digging into my static site project, I wanted to capture something I 
got working the other day using WebStorm (I am on the free 30-day trial :) 
). They have a profiling tool called spy-js, and it shows some interesting 
things, although ultimately it didn't give me the detail I wanted 
(especially on parameter contents on method calls). However, I did gain 
some insight into how TW5 works that helps flesh out the architectural 
documentation I've read (which isn't all of it, yet).

I am thinking njsTrace https://github.com/valyouw/njstrace (open source, 
which is better) may be a better choice. Has anyone here used it to trace 
TW under node?

Anyway, just in case anyone else stumbles across this doing a search, here 
is how I set up the run profile (with my userid in the Users directory 
elided). It is with node installed per default on Windows and *npm install 
tiddlywiki *run under my own user id, with the actual TW set up in a 
sandbox location.

https://lh6.googleusercontent.com/-rNs61-gobIw/VICNiMp1EtI/AAABO-c/D4EIVm0orjg/s1600/WebStorm%2BSpy-Js%2Bfor%2BNode%2BRun%2BConfiguration.JPG

Here is a sample of the output;

https://lh6.googleusercontent.com/-FwWWcOQJ_fk/VICOP6kiF4I/AAABO-o/8gQUvHzzS6U/s1600/Spy-Js%2BResults.JPG
Hopefully someone finds this useful or interesting, at least.

-- 
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 http://groups.google.com/group/tiddlywiki.
For more options, visit https://groups.google.com/d/optout.

Re: [tw] [TW5] Getting a TOC in the sidebar of static pages...

[Jim Lehmer]

Thanks for the reply. I was beginning to wonder if I was just being so 
stupid it wasn't worth responding to. :)

I will give your suggestion a try, hopefully it works and brings to a close 
over a week of trying to figure it out, including installing third-party 
node profiling tools to get more insight into what is going on under the 
covers.

Ultimately, the use case I am trying to get to with TW5 in this instance is 
to replace using something like Pelican for generating my static web site 
and just use TW instead. Getting the site title and subtitle into the 
sidebar were the first step. TOC will be the second step. The final step 
will be figuring out how to get the tag buttons for tiddlers to be 
anchors with appropriately transformed URLs on a static page (right now the 
buttons show up and onhover causes the pointer to change to indicate 
they're clickable, but obviously clicking on them does nothing). I have 
been looking into that. I presume figuring out a way to replace button 
widgets with link widgets in the static template is my main hope. But 
before I dirty this thread more, I will give it a go and if I have specific 
questions around that will post a different thread.

I also have a small bug in a TW documentation tiddler I plan on filing a 
pull request once I get a bit of time. It is related to a bug I filed a few 
months back.

Anyway, if I can get those three pieces in place, then I think using TW to 
be a static site generation tool will be easy, and I plan on documenting 
and publishing how as I go. Thanks again.

On Wednesday, December 3, 2014 11:32:24 AM UTC-6, Jeremy Ruston wrote:

 Hi Jim

 My apologies for the late reply. Getting the TOC working for static sites 
 is an excellent idea.

 I think that the problem is that the core global macros are explicitly 
 imported into $:/core/templates/static.tiddler.html via the 
 $importvariables widget. This means that those macros are only available 
 within the content area of the $importvariables widget.

 You can move the $importvariables widget so that it wraps the entire 
 template to resolve this problem.

 Best wishes

 Jeremy.

 On Sat, Nov 29, 2014 at 6:45 PM, Jim Lehmer jim.l...@gmail.com 
 javascript: wrote:

 I feel like I am real close on this, but keep hitting barriers. I have a 
 working TOC using the *toc *macro. I have changed the 
 *$:/core/templates/static.tiddler.html 
 *to successfully show the *SiteTitle *and *SiteSubtitle *just like on 
 the normal (Javascript-enabled) wiki:

 body class=tc-body
 `{{$:/StaticBanner||$:/core/templates/html-tiddler}}
 `div class=tc-sidebar-scrollable style=overflow: auto;
 div class=tc-sidebar-header
 `$reveal state=$:/state/sidebar type=match text=yes default=yes 
 retain=yes
 
 `h1 class=tc-site-title`$transclude tiddler=$:/SiteTitle 
 mode=inline/`/h1
 div class=tc-site-subtitle`$transclude tiddler=$:/SiteSubtitle 
 mode=inline/`/div

 This works fine. Under those I don't want all the buttons and tabs in the 
 static sidebar (since they wouldn't work anyway), but just a TOC. When I 
 add the following right after the above, it shows the dynamically generated 
 TOC successfully in the *$:/core/templates/static.tiddler.html *once I 
 leave edit mode:

 div class=tc-table-of-contents
 `{{Table of Contents}}`
 /div

 But when I render out the static site, the *div 
 class=tc-table-of-contents *and closing */div *are inserted into 
 the static HTML, along with some blank lines between them (for presumably 
 each TOC list entry). I have tried both transcluding the existing *Table 
 of Contents* tiddler as well as calling the *toc *macro directly within 
 the above *div*, just like in the *Table of Contents *tiddler itself, 
 but in both cases I get the same results. What am I missing?

 BTW, I have been working on getting a usable sidebar for a static site 
 for days now - it is a lot of work for what I would think is something many 
 would want. I am trying to document what I am doing so I can write some 
 articles about it, but if someone has already done the heavy lifting, I 
 would appreciate pointers. I've searched this group and the web, but not 
 with much success.

 Thanks,

 Jim

 -- 
 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 javascript:.
 To post to this group, send email to tiddl...@googlegroups.com 
 javascript:.
 Visit this group at http://groups.google.com/group/tiddlywiki.
 For more options, visit https://groups.google.com/d/optout.




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

-- 
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

[tw] [TW5] Getting a TOC in the sidebar of static pages...

[Jim Lehmer]

I feel like I am real close on this, but keep hitting barriers. I have a 
working TOC using the *toc *macro. I have changed the 
*$:/core/templates/static.tiddler.html 
*to successfully show the *SiteTitle *and *SiteSubtitle *just like on the 
normal (Javascript-enabled) wiki:

body class=tc-body
`{{$:/StaticBanner||$:/core/templates/html-tiddler}}
`div class=tc-sidebar-scrollable style=overflow: auto;
div class=tc-sidebar-header
`$reveal state=$:/state/sidebar type=match text=yes default=yes 
retain=yes

`h1 class=tc-site-title`$transclude tiddler=$:/SiteTitle 
mode=inline/`/h1
div class=tc-site-subtitle`$transclude tiddler=$:/SiteSubtitle 
mode=inline/`/div

This works fine. Under those I don't want all the buttons and tabs in the 
static sidebar (since they wouldn't work anyway), but just a TOC. When I 
add the following right after the above, it shows the dynamically generated 
TOC successfully in the *$:/core/templates/static.tiddler.html *once I 
leave edit mode:

div class=tc-table-of-contents
`{{Table of Contents}}`
/div

But when I render out the static site, the *div 
class=tc-table-of-contents *and closing */div *are inserted into the 
static HTML, along with some blank lines between them (for presumably each 
TOC list entry). I have tried both transcluding the existing *Table of 
Contents* tiddler as well as calling the *toc *macro directly within the 
above *div*, just like in the *Table of Contents *tiddler itself, but in 
both cases I get the same results. What am I missing?

BTW, I have been working on getting a usable sidebar for a static site for 
days now - it is a lot of work for what I would think is something many 
would want. I am trying to document what I am doing so I can write some 
articles about it, but if someone has already done the heavy lifting, I 
would appreciate pointers. I've searched this group and the web, but not 
with much success.

Thanks,

Jim

-- 
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 http://groups.google.com/group/tiddlywiki.
For more options, visit https://groups.google.com/d/optout.

[tw] Re: Announcing TiddlyWiki version 5.0.18-beta

[Jim McD]

Thank you Eric.  I am good with Perl but none of those unfortunately.  
Actually after clicking around in TW5 I can't see editable code in the same 
way as classic TW.  Has it been foolproofed in some way ?

Jim

On Thursday, September 18, 2014 9:06:25 PM UTC+1, Eric Shulman wrote:

 On Thursday, September 18, 2014 6:23:57 AM UTC-7, Jim McD wrote:

 dumb Q1  What skills do I need to develop/customize TW5 ?


 As with TiddlyWiki Classic, the core code is written in *Javascript*, and 
 the page display is a combination of *CSS *and *HTML*, so knowing at 
 least a bit of these technologies is a good idea.  There's also a lot of 
 TiddlyWiki5 architecture to learn: new *WikiText *formatting, a set of 
 built-in *widgets* for generating output, a powerful *filter* syntax for 
 selecting tiddlers, and much more!   There's also new ways to set up your 
 TiddlyWiki: in addition to the single-file usage familiar to TiddlyWiki 
 Classic users, you can also install TiddlyWiki5 using *nodeJS*, so it 
 runs as a local server using a folder of tiddlers stored as separate 
 files, and support for server-based storage is also integrated into the 
 TiddlyWiki5 core, so hosting your tiddlers online is now much more 
 efficient and flexible (you can save individual tiddler changes, rather 
 than uploading the entire file)

 dumb Q2  In the old tiddlywiki you could edit any tiddler by double 
 clicking.  Even tiddlers that contained code, like plugins.  How can I edit 
 stuff now ?  Not by viing the whole file I am sure.


 By default, there are 3 icons that appear in the top right of each tiddler 
 shown: info (an i in a circle), edit (a pencil), and close (an X). 
  Click the pencil to start editing the tiddler.  When editing there are 
 three icons as well: delete (a trashcan), cancel (an x in a circle), and 
 save (a checkmark).  When you are done editing, click the checkmark to save 
 your tiddler changes.

 enjoy,
 -e
 Eric Shulman
 TiddlyTools / ELS Design Studios

 YOUR DONATIONS ARE VERY IMPORTANT!
 HELP ME TO HELP YOU - MAKE A CONTRIBUTION TO MY TIP JAR...
http://TiddlyTools.github.com/fundraising.html#MakeADonation

 Professional TiddlyWiki Consulting Services...
 Analysis, Design, and Custom Solutions:
http://www.TiddlyTools.com/#Contact


-- 
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 http://groups.google.com/group/tiddlywiki.
For more options, visit https://groups.google.com/d/optout.

[tw] Re: Briefcase Plugin -- a GTD tool

[Jim McD]

Hi Danielo

I didn't intend to critisize your suggestions (In fact I did not read your 
posts yet). I was talking about mGSD users, mainly in 2007 to about 2010, 
and the suggestions they left in groups and on Simons mGSD blog.

My own preference would be a pure GTD tool, with non-GTD functionality into 
other specialised apps.   In view of the highly modular nature of TW5, they 
could go into optional plugins.  This is the approach taken in the Allen 
book, which I have read twice, and it is what gives GTD so much power and 
clarity.  Again just my opinion as a fan.



On Thursday, September 18, 2014 3:59:50 PM UTC+1, Danielo Rodríguez wrote:



 I can't avoid feeling referenced by that comment. 
 IF you think my suggestions does not worth to be on the implementation of 
 Briefcase, I would like to hear why.
 Rather than only asking for new features, I gave code ready to be used. 
 One of my main suggestions (that is already implemented on my personal 
 version) is to give context to the actions. I reviewed the OLD version of 
 mGSD and the context is present.

 Here is a snapshot of how what I customized looks like. Let me know if you 
 find it useful or not:




 https://lh3.googleusercontent.com/-sBki8KF3Mes/VBrzCZTj0ZI/Lgo/w9IQ7OUjLDg/s1600/myDashboard.PNG

 Anyway, mGSD looks like a very matured tool. If you like it, there is 
 nothing that will make you leave it. TW5 is a reboot, a new point of view 
 so is normal to expect that things could change.


 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 http://groups.google.com/group/tiddlywiki.
For more options, visit https://groups.google.com/d/optout.

[tw] Re: Briefcase Plugin -- a GTD tool

[Jim McD]

Roma

Thanks for this.  I have been using mGSD/GTD continuously since 2006, and 
praying for a TW5 conversion.

Rather than shower you with update requests, I would just say one thing.  
Please make Briefcase a one-for-one conversion of mGSD, and make it easy 
for users to tweak.  Everybody has different things they want it to do/not 
do.  IMO the best way to accommodate that is to make Briefcase a strict, 
core interpretation of the David Allen book, but at the same time allow 
users to tweak it easily, hopefully without being full time developers.  
Each can then embellish or reduce it as they will.

In the old mGSD, Simon Baird used to get bombarded with requests to make 
mGSD do things that are not part of GTD and are already covered by other 
tools, eg make it a diary, a contacts database, a project manager.  If 
somebody wants a contacts manager, there are a thousand apps they can knock 
themselves out with. But good GTD apps are very rare.  Thankfully Simon 
resisted that and mGSD remains an efficient, clean GTD tool.  I would love 
Briefcase to take over that role.

My 2 cents worth.

Thanks again.
Jim

-- 
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 http://groups.google.com/group/tiddlywiki.
For more options, visit https://groups.google.com/d/optout.

[tw] Re: Announcing TiddlyWiki version 5.0.18-beta

[Jim McD]

Hi Jeremy

dumb Q1  What skills do I need to develop/customize TW5 ?

dumb Q2  In the old tiddlywiki you could edit any tiddler by double 
clicking.  Even tiddlers that contained code, like plugins.  How can I edit 
stuff now ?  Not by viing the whole file I am sure.

Jim

On Thursday, September 18, 2014 12:05:38 PM UTC+1, Jeremy Ruston wrote:

 Hi Matabele,

 Glad it worked out.

 I thought I was the only person to use the word belay these days; it's 
 an awesome nautical term that I rather like. Glad to see it being used!

 Best wishes

 Jeremy


 On Thu, Sep 18, 2014 at 5:42 AM, Matabele matabe...@gmail.com 
 javascript: wrote:

 Hi

 Belay that -- this occurred only in the first offline copy I downloaded 
 after I had been messing around with a few settings. I can no longer 
 replicate this error.

 regards


 On Thursday, September 18, 2014 6:16:24 AM UTC+2, Matabele wrote:

 Hi Jeremy

 Checking the boxes or clicking the 'home, 'close all', 'permaview' or 
 'import' buttons of the 'Tools' tab in the sidebar results in confusing 
 behaviour.

 regards

 On Wednesday, September 17, 2014 11:26:58 PM UTC+2, Jeremy Ruston wrote:

 I'm delighted to announce that TiddlyWiki version 5.0.18-beta has been 
 released:

 http://tiddlywiki.com/

 You can upgrade at:

 http://tiddlywiki.com/upgrade.html

 As usual, please take care to ensure that you keep a careful backup 
 before attempting to upgrade.

 This is a minor release in preparation for coming out of beta on 
 Saturday. There are more improvements to the documentation, and a number 
 of 
 bug fixes. See the release note for more details.

 With just a couple of days before the full release I'd very much 
 appreciate any attention you can give to testing this release.

 I'd like to thank all the contributors to this release, including 
 @BramChen, @buggyj, @Eucaly, @pmario and @xcazin.

 Please reply here with any issues or questions.

 Best wishes

 Jeremy.



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



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

-- 
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 http://groups.google.com/group/tiddlywiki.
For more options, visit https://groups.google.com/d/optout.

[tw] Re: [TW5] How to lower case

[jim]

But this can't be the only problem, since replacing the css and using c 
pa's macro (see above) doesn't change anything. The resulting value of the 
*somefield 
*field is still the non-evaluated macro call. Or wasn't it this macro type 
you are speaking of?

\define lower2()
$macrocall $name=setlowercase title=$(setsort)$/
\end

$set name=setsort value=Rand 
$button set=!!somefield setTo=lower2/
/$set

jim

Am Montag, 15. September 2014 09:21:08 UTC+2 schrieb Stephan Hradek:

 The problem is: You do NOT convert to lowercase! The variable's content is 
 just DISPLAYED in lower case. That's what the CSS is doing.

 If you really want to convert the stored text to lowercase, you need a 
 JavaScript macro which can change a field's value.


-- 
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 http://groups.google.com/group/tiddlywiki.
For more options, visit https://groups.google.com/d/optout.

[tw] Re: [TW5] How to lower case

[jim]

First I'd like to thank you. I didn't want my problem to take so much space 
and I certainly didn't expect this generous help. 

I couldn't achieve my goal with your javascript macro, but I feel we are 
very close:) The problem seems to be again the macro not evaluating 
correctly a given variable. So I tried to $macrocall your javascript macro, 
which didn't work at first because your macro definition wasn't in the same 
tiddler as the call (as it seems to me). I turned to the starting point 
using simple css (thanks to Eric Shulman):

\define lower(text)
@@text-transform: lowercase;$text$@@
\end

\define lower2()
$macrocall $name=lower text=$(setsort)$/
\end

$set name=setsort value=Rand 
lower2
/$set

Everything works fine (resulting in *rand *in the text field). But as I try 
to direct the output to a field by the buttonWidget (code down), the last 
step isn't evaluated anymore (resulting in *$button set=!!somefield 
setTo=Rand/* in the *somefield *field).

$set name=setsort value=Rand 
$button set=!!somefield setTo=lower2/
/$set

What do think about this?

jim

 

Am Freitag, 12. September 2014 10:35:07 UTC+2 schrieb jim:

 Hello
 I'd need a small macro with no other purpose than putting a specified text 
 to lower/upper case. I am sure this isn't difficult to implement; 
 nevertheless I require your help.

 jim


-- 
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 http://groups.google.com/group/tiddlywiki.
For more options, visit https://groups.google.com/d/optout.

[tw] [TW5] Userfriendly Linking Transclusion

[jim]

Hello

I am proposing an idea for a plugin. Proposing is everything I can in this 
case. Perhaps this meets somebody's developing skills ?:)

Transcluding (or linking) tiddlers is still rather tedious if one uses long 
tiddler titles and/or tries to reorganise certain tiddlers. I thought it 
might be useful dispose of a mechanism similar to the import mechanism: one 
could just drop the link of the sidebar into the regrouping tiddler where 
the link or the transclusion is set at, say, the end.
I'd find it very useful too, if transcluding tiddlers are visible, just as 
the linking tiddlers under *References.*

Thank you
jim

-- 
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 http://groups.google.com/group/tiddlywiki.
For more options, visit https://groups.google.com/d/optout.

[tw] [TW5] How to lower case

[jim]

Hello
I'd need a small macro with no other purpose than putting a specified text 
to lower/upper case. I am sure this isn't difficult to implement; 
nevertheless I require your help.

jim

-- 
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 http://groups.google.com/group/tiddlywiki.
For more options, visit https://groups.google.com/d/optout.

[tw] Re: [TW5] How to lower case

[jim]

Thank you for your help. Now, it works fine if I transmit plain text. What 
if I should handle the text variable dynamically: 

\define TableHeaders()
$list filter=[is[current]split:table-headers[,]] variable=currentField
th$set name=currentFieldSet value=currentField $button class=
tc-btn-invisible set=!!sort-field setTo=lower $(currentFieldSet)$  
currentField /$button/$set/th/$list
\end

\define lower(text)
@@text-transform: lowercase;$text$@@ 
\end



In the end the *sort-field* field of the tiddler should contain the 
currentField in lower case. I have changed a few times the emplacement 
of the variable assignement:  I get the definition of the *lower *macro or 
*true*.

(I am working on the Inline Editable Table by Danielo.)

jim


Am Freitag, 12. September 2014 10:35:07 UTC+2 schrieb jim:

 Hello
 I'd need a small macro with no other purpose than putting a specified text 
 to lower/upper case. I am sure this isn't difficult to implement; 
 nevertheless I require your help.

 jim


-- 
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 http://groups.google.com/group/tiddlywiki.
For more options, visit https://groups.google.com/d/optout.

[tw] Re: [TW5] How to lower case

[jim]

Thank you c pa!
The problem with this attempt is that *sort-field* is assigned to *in* 
TableHeaders(). This can't be done elsewhere because of *currentField* 
being rendered inside TableHeaders. Or am I wrong?

 I think, I misunderstand some basic concept about the variable assignment:

\define TableHeaders()
$list filter=[is[current]split:table-headers[,]] variable=currentField
th$button class=tc-btn-invisible set=!!sort-field 
setTo=lowerSortField 
text=currentField currentField/$button/th/$list
\end

\define lower(text)
@@text-transform: lowercase;$text$@@ 
\end

\define lowerSortField(text)
lower $text$
\end


I want lowerSortField() to return the evaluated string. With the code above 
I get *true. *Perhaps my macro-nesting is defective?

When I try to transmit the currentField in a way similar to c pa's 
proposition by wrapping it in a setWidget, i.e.
\define TableHeaders()
$list filter=[is[current]split:table-headers[,]] variable=currentField
th$set name=currentFieldSet value=currentField $button class=
tc-btn-invisible set=!!sort-field setTo=lowerSortField 
currentField/$button/$set/th/$list
\end

\define lower(text)
@@text-transform: lowercase;$text$@@ 
\end

\define lowerSortField()
lower $(currentFieldSet)$
\end

I get *lower a *where *a* is the the *currentField* value. 

I'll be much obliged for any further help.

jim

Am Freitag, 12. September 2014 17:09:07 UTC+2 schrieb c pa:

  In the end the sort-field field of the tiddler should contain the 
 currentField in lower case. 
 To do that you need to convert currentField to lower case before 
 calling the TableHeaders macro
 So you need a macro that does the conversion then calls TableHeaders 
 Something like the following: 
 \define lowerTableHeaders()
 $set name=sort-field setTo=lower $(currentField)gt; 
 TableHeaders
 /$set

 \end


-- 
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 http://groups.google.com/group/tiddlywiki.
For more options, visit https://groups.google.com/d/optout.

[tw] [TW5] Popup for Missing Tiddlers

[jim]

Hello
I would like to have a popup showing the referencing tiddlers when I click 
on any link to a missing tiddler. Actually, similar to the one already 
implemented in the *Missing* tab (in the *More* tab). Are there any ideas 
on how to realize this?

Thank 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 http://groups.google.com/group/tiddlywiki.
For more options, visit https://groups.google.com/d/optout.

[tw] Re: [TW5] Theme adjustment request

[jim]

Is it possible to have the same sticky-effect in the edit mode?

Am Freitag, 25. April 2014 07:31:24 UTC+2 schrieb Leo Staley:

 For the Open tab on the right, would it be possible to change the 
 default main theme so that it will highlight which tiddler is the one 
 you're currently viewing? This would be useful for the same reason that 
 your current browser tab looks different from all the other browser tabs. 

 Personally, I much prefer the Browser tabs look achieved by the TWC 
 Tiddler's bar, but I also understand why some might like it always visible 
 on the side. So if it's going to be the prefered way of doing it with TW5, 
 it would go a long way towards helping users, beginners and advanced alike, 
 to realize what they are looking at and use it more effectively. 

 I certainly know that If as I scrolled down the main page to a new 
 tiddler, and the highlighted item on the right shifted with me as I 
 scrolled down, It would feel far less lost on the page than I do now. 


-- 
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 http://groups.google.com/group/tiddlywiki.
For more options, visit https://groups.google.com/d/optout.

[tw] Re: Backup button, problems with assigning text field to value

[jim]

You're absolutely right. Thank you.

Am Dienstag, 17. Juni 2014 08:17:20 UTC+2 schrieb Stephan Hradek:

 Isn't it sufficient to use the tiddler to backup as the skeleton?

 \define myNewTitle()
 $:/_backup/$(tiddlerTitle)$/$(todaysDate)$
 \end


 $set name=tiddlerTitle value={{!!title}}
 $set name=todaysDate value=dateTime 
 $newtiddler title=myNewTitle class=btn-invisible skeleton={{!!title
 }}Verlauf/$newtiddler
 /$set
 /$set




-- 
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 http://groups.google.com/group/tiddlywiki.
For more options, visit https://groups.google.com/d/optout.

[tw] Re: Backup button, problems with assigning text field to value

[jim]

I am sorry, this might seem obvious: how do I add the field caption 
afterwards. Should I use fieldmangler?

Am Dienstag, 17. Juni 2014 09:36:50 UTC+2 schrieb jim:

 You're absolutely right. Thank you.

 Am Dienstag, 17. Juni 2014 08:17:20 UTC+2 schrieb Stephan Hradek:

 Isn't it sufficient to use the tiddler to backup as the skeleton?

 \define myNewTitle()
 $:/_backup/$(tiddlerTitle)$/$(todaysDate)$
 \end


 $set name=tiddlerTitle value={{!!title}}
 $set name=todaysDate value=dateTime 
 $newtiddler title=myNewTitle class=btn-invisible skeleton={{!!
 title}}Verlauf/$newtiddler
 /$set
 /$set




-- 
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 http://groups.google.com/group/tiddlywiki.
For more options, visit https://groups.google.com/d/optout.

[tw] Re: Backup button, problems with assigning text field to value

[jim]

Do you know whether the strange behaviour of the {{!!text}} assignment is 
an issue of the newtiddler widget? (The assignment only works in text 
fields without line breaks)
Thanks a lot

Am Dienstag, 17. Juni 2014 14:49:17 UTC+2 schrieb Stephan Hradek:



 Am Dienstag, 17. Juni 2014 12:35:07 UTC+2 schrieb jim:

 I am sorry, this might seem obvious: how do I add the field caption 
 afterwards. Should I use fieldmangler?


 I have no clue. I haven't yet looked at what fieldmangler does. 
 newtiddler itself can't add fields. 


-- 
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 http://groups.google.com/group/tiddlywiki.
For more options, visit https://groups.google.com/d/optout.

[tw] Backup button, problems with assigning text field to value

[jim]

I'm trying to set up a backup mechanism for individual tiddlers. I think 
the mechanism is fairly simple: clicking a button in the tiddler's toolbar 
will copy the tiddler and change the title, so it remains in the 
background. The idea is to access it later on through a tab in the info 
panel and to be capable of restoring it by clicking another button. 
However, my first attempts concerning the button creating a backup work 
only for text fields with no line breaks. I can't see why. Can anyone help 
me? Am I using the newtiddlerWidget incorrectly?

This is the code for the backup-button. To evitate stack overflow I 
specifically tag the tiddler containing the code:

\define myNewTitle()
$:/_backup/$(tiddlerTitle)$/$(todaysDate)$
\end

$list filter=[is[current]!tag[$:/tags/noBackup]]
span title=Backup: Speichere in Verlauf
$set name=tiddlerTitle value={{!!title}}
$set name=todaysDate value=dateTime 
$set name=verlauf value={{!!title}}
$set name=text value ={{!!text}} 
$set name=datum value =dateTime .0MM.0DD.0hh.0mm 
$set name=caption value=dateTime DD MMM  0hh:0mm 
$set name=tag value=Verlauf

$newtiddler title=myNewTitle class=btn-invisible skeleton=
$:/_backup-skeletonVerlauf/$newtiddler

/$set
/$set
/$set
/$set
/$set
/$set
/$set
/span
/$list



Thank you very much.

-- 
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 http://groups.google.com/group/tiddlywiki.
For more options, visit https://groups.google.com/d/optout.

Re: [tw] Re: Implementing a directed acyclical graph with TiddlyWiki5

[Jim Weaver]

Nice! Thanks Jeremy and Mario for your help.

Regards,
Jim Weaver

 On Dec 3, 2013, at 4:17 PM, Jeremy Ruston jeremy.rus...@gmail.com wrote:
 
 Hi Jim
 
 On Tue, Dec 3, 2013 at 8:51 PM, James Weaver james.l.wea...@gmail.com 
 wrote:
 I think that I'm answering my own question here:  It seems that a tiddler is 
 only a tag when it is tagging a tiddler; it can't be defined as a tag 
 explicitly.  If this is incorrect, please advise.
 
 That's correct.
 
 Tags themselves can be tagged, so you could create tiddlers for all your tags 
 and tag them with the tag tag. Then you can get a list of tags with 
 [tag[tag]].
 
 Best wishes
 
 Jeremy
 
  
 
 Thanks,
 Jim Weaver
 
 
 On Tuesday, December 3, 2013 2:39:49 PM UTC-5, James Weaver wrote:
 Thanks Mario.  A hierarchical structure of tags that you described should 
 work for my purposes.  I'll need to be able to distinguish between a 
 tiddler that is a tag (used for categorization) and a tiddler that isn't a 
 tag (used for content).  I suppose I could do this with a naming 
 convention, as tags are supposed to begin with lower-case, but do you know 
 of other ways?  I could use the tagging filter, but if a given tag 
 doesn't happen to be tagging tiddlers at a given moment, it seems that it 
 would indicate that it isn't a tag.  Hope that makes sense.
 
 Thoughts?
 Jim
 
 On Tuesday, December 3, 2013 1:32:56 PM UTC-5, PMario wrote:
 Hi Jim, 
 
 I think what you describe is the standard TW tagging mechanism. 
 
 eg: 
 
 - if you create a tiddler named task  .. and 
 - several tiddlers eg:
   - Go to Mordor
   - Get the Ring
 - tag those tiddlers as task 
 
 What you get is a parent child relation between task = parent and 
 Go .. / Get .. = children
 
 I'm using those examples, because you can find exactly that at 
 http://five.tiddlywiki.com
 So you can open it and see the stuff described below. 
 
 If you open the tiddler Go to Mordor you can see, that it is tagged 
 task ... 
 If you click the task pill, 
  - You can see all other tiddlers tagged with task
 
 If you open the task tiddler
  - click the (i) info button 
  - open the Tagging tab  ... you'll see all tiddlers that are tagged 
 with task
 
 IMO the mechanism is, (almost) what you described. ... But I think the 
 implementation is different, to what you expect. ... because
 
 The tagging list is created at runtime.
 So if you click the tagging tab, the TW core searches for all tiddlers 
 that are tagged task ... the tiddler named task doesn't contain a 
 field tagging or in your case children. 
 
 IMO adding parent and children fields (or RDF tiddlers) can be done. 
 But there is a whole lot of syncing problems that will pop up. Every 
 time you rename / create / update / delete / import / export ... a 
 tiddler, you'll need to check all tiddlers and keep them in sync. Exactly 
 at that point you create a real database behaviour. ... and databases 
 are kind of complicated, highly optimized beasts. ...
 
 I think a similar usecase was introduced by Leo at a hangout #19 [1]. 
 IMO if we need a real database behaviour, we should use a real database. 
 May be the storage is not so important, but I think the query language to 
 retrive the data is ... and TW is no database, even if it is quite close :)
 
 After the hangout 19 I did stumble upon ArangoDB [2] which imo would be a 
 nice backend for TW5. It supports tiddlers out of the box (key-value 
 store) and it would be possible to create real graph indexes with a 
 graph query language. 
 
 @Jeremy, 
 Did you know ArangoDB?
 
 have fun!
 mario
 
 [1] http://www.youtube.com/watch?v=wYaFsOzXnPY#t=509
 [2] http://www.arangodb.org/
 
 -- 
 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 http://groups.google.com/group/tiddlywiki.
 For more options, visit https://groups.google.com/groups/opt_out.
 
 
 
 -- 
 Jeremy Ruston
 mailto:jeremy.rus...@gmail.com
 -- 
 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/GyRqdjGWM0Y/unsubscribe.
 To unsubscribe from this group and all its topics, send an email to 
 tiddlywiki+unsubscr...@googlegroups.com.
 To post to this group, send email to tiddlywiki@googlegroups.com.
 Visit this group at http://groups.google.com/group/tiddlywiki.
 For more options, visit https://groups.google.com/groups/opt_out.

-- 
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 http