[tw5] Interact with content in view mode

[Anjar]

Hi all,

I wondered if any of you have experimented with interaction with content in 
view mode? I am mainly thinking of hightligheted text, some examples:

   - make the highlighted text into a link
  - e.g., I highlight the text *this is a test* in view mode, use a 
  keyboard shortcut or button, and the text in the tiddler is replaced with 
*[[this 
  is a test]]*
   - reformat the highlighted text
  - e.g., I highlight the text *this is a test* in view mode, use a 
  keyboard shortcut or button, and the text in the tiddler is replaced 
  with *this is a test*
   - replace the highlighted text with a macro
  - e.g., I highlight the text *this is a test* in view mode, use a 
  keyboard shortcut or button, and the text in the tiddler is replaced with 
*<>*
   - create a new tiddler from the  highlighted text
  - e.g., I highlight the text *this is a test* in view mode, use a 
  keyboard shortcut or button, and a new tiddler is created in the 
background 
  with timestamp as title and *this is a test*  as content
   - create a new tiddler from the highlighted text
   - e.g. , I highlight the text *this is a test* in view mode, use a 
  keyboard shortcut or button, and a new tiddler is created in edit-mode 
with *this 
  is a test*  as title
   

Any thoughts?


Best regards,
Anders

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/7652a699-b1c5-4f80-acab-2160a3e0ff28n%40googlegroups.com.

[tw5] 2D tiddler grid (?): nulis.io

[Anjar]

Hi,

I just found nulis.io and it seems very interesting: https://nulis.io/ In 
short, it is tiddlers but in 2D. Perhaps someone can use it for inspiration

Best,
Anders

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/364db145-8728-4122-8683-504d2a15113cn%40googlegroups.com.

[tw5] Re: Your main Tags - Your main Tabs

[Anjar]

A few inputs;

In my head, things became a bit easier with the keyword field in drift; 
https://akhater.github.io/drift/#Example%20Keywords%20Source Then tags can 
be reserved for broader topics and I add specifics to the keyword field.

A generalization of that approach, I guess, is that every field is a tag 
field, and that fields are in a sense tags themselves. In your case; would 
it make sense to have a URL field in the tiddlers you use in the example? 
Then you know that the tiddlers with a URL field have stuff from the 
internet and can use that for filtering. This approach is also establishing 
relationships between tiddlers, e.g. the tag "Sigmund Freud" is very broad, 
but you can add a field "author" with value "Sigmund Freud" to tiddlers on 
his books, link to [[Sigmund Freud]] in tiddlers where you critique him, 
have a field "relatives" in the tiddler on Anna Freud where [[Sigmund 
Freud]] is listed or a field "inspired.by" where he is listed in a tiddler 
on Carl Jung and so on

Another take on tabs is thinking more along the lines of "board", e.g. 
https://andjar.github.io/TiddlyMenu/board.html

Best,
Anders

søndag 30. mai 2021 kl. 14:13:41 UTC+2 skrev Mat:

> While I didn't use TW as a "Personal Knowledge Management" system, at 
> least not specifically, I'd say the general answer to your question is how 
> direct your access to the data needs to be, and put this in relation to how 
> cluttered you want your UI to be.
>
> For example, I would personally not want a lot of sidebar tabs. But then, 
> if there's something I use a lot, then why not. But if there are *many" 
> things that I use a lot then, again, I wouldn't want them as sidebar tabs. 
> But then, if I could make the sidebar tabs more subtle or e.g hide them so 
> they don't clutter, then I might want them there. But that comes at the 
> cost of the direct access, so... etc. The conclusion is that it's a 
> question of finding a balance and this is a subjective preference. I wish 
> there were be some kind of measurement system that counts the number of 
> times you actually use a feature and then proposes that you should make it 
> more or less prominent in the UI but then what does "use a feature mean"? 
> For example, sometimes it's enough that I *see *a title, not open the 
> tiddler. Obviously no (current) way to measure this.
>
> From a more pragmatic perspective I say; make reasonable guesses for your 
> design, and then master TW. Over time, you'll *modify *your system 
> according to your needs. In addition, I find that my needs shift over time, 
> depending on what I focus on. Consequently my TW's shift. All UI's are 
> compromises. All implementations balance cost-benefit. So the secrete is 
> not to find "the perfect setup" but rather to gain the knowledge how to 
> tweak it.
>
> <:-)
>
>
> On Sunday, May 30, 2021 at 12:57:53 PM UTC+2 Atronoush wrote:
>
>> Recently there were some interesting discussions on better utilizing 
>> Tiddlywiki for Personal Knowledge Management (PKM)
>>
>> Tiddlywiki is an amazing tool, but one quickly lost in the jungle of 
>> tiddlers, tags, tabs, etc...
>> You can easily add tags, tabs, tiddlers, ... Tiddlywiki tends very much 
>> to increase its entropy!
>>
>> Example:
>> I do not know if I should tag *link* anything I find from the internet 
>> and add to my wiki, or tag it as a *reference*?
>> Should I add a sidebar Tab as soon as I have several tiddlers on the same 
>> topic or not?
>>
>> Soren in his Zettelkasten shows some workflow for this! I wish to know 
>> how I can effectively use Tiddlywiki as PKM?
>>
>> - Do you recommend some main tags?
>> - Do you recommend limiting the number of tags? Or the number of tags in 
>> your wiki are more than the number of tiddlers?
>> - Do you recommend categorization?
>> - Do you recommend unlimited use of sidebar tabs or limited?
>>
>> In overall how to have a useful PKM using Tiddlywiki? I am talking general
>>
>> Question: Does using TW as PKM needs some design practice?
>>
>> --Atro
>>
>>

-- 
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/dbbabf77-404a-47db-a3d6-65f337bf782fn%40googlegroups.com.

[tw5] Fade-in background image

[Anjar]

Hi all,

I tried to make a single tiddler view where the background image changes 
when you change tiddler, and it works 
okay: https://andjar.github.io/TiddlyMenu/lighthouse.html

However, the transitions are a bit harsh, so I wondered if it would be 
possible to add a transition/animation (e.g. fade)? Since CSS seems to be 
restrictive regarding background animation (?), would it be easiest to 
modify zoom.js? Any experiences?

Best,
Anders

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/d0c84e74-32a7-41b7-ac30-dde5b1ca0ba8n%40googlegroups.com.

Re: [tw5] Re: Specify in link if tiddler should open above or below current

[Anjar]

Hi Mohammad,

This worked perfectly, thank you very much!


Best,
Anders

søndag 23. mai 2021 kl. 21:54:14 UTC+2 skrev Mohammad:

> Anders,
>
>  Have you seen the simple-navigation in the Utility plugin?
>   What you need is Next|Previous button plus opening in next 
> previous position in story river am I right?
>
> If so, hack the Utility plugin and add one more action as below
> 1. for the previous button add the opening tidder to $:/StoryList  (list 
> field) using *putbefore *
> 2. for the next button add the opening tidder to $:/StoryList  (list 
> field) using *putafter*
>
> This way when a tiddler is open in the story river, Next button opens the 
> next tiddler below current and Previous button opens previous tiddler 
> before current tiddler!
>
>
>
> Best wishes
> Mohammad
>
>
> On Mon, May 24, 2021 at 12:06 AM Anjar  wrote:
>
>> Thank you both!
>>
>> I tried your solution, @Eric, but it didn't seem to work; I tried to move 
>> <$action-navigate 
>> $to=<> /> into the body, but that didn't help either. 
>> So perhaps the problem is more complex than simply changing 
>> $:/config/Navigation/openLinkFromInsideRiver
>>
>> However, this was a very interesting way to force a specific sequence of 
>> events!
>>
>> Best,
>> Anders
>>
>> søndag 23. mai 2021 kl. 17:50:27 UTC+2 skrev Eric Shulman:
>>
>>> On Sunday, May 23, 2021 at 7:53:40 AM UTC-7 Anjar wrote:
>>>
>>>> Hi,
>>>> I have some tiddlers in sequence with links to previous/next at the 
>>>> bottom. To keep the order in the story, I want previous tiddlers to open 
>>>> above the current but he next to open below. Is it possible to achieve 
>>>> this 
>>>> in some way?
>>>> I tried this, but without success:
>>>>
>>>> <$button class="tc-btn-invisible tc-tiddlylink">
>>>> <$action-setfield 
>>>> $tiddler="$:/config/Navigation/openLinkFromInsideRiver" text="above"/>
>>>> <$action-navigate $to=<> />
>>>> <$action-setfield 
>>>> $tiddler="$:/config/Navigation/openLinkFromInsideRiver" text="below"/>
>>>> << Previous
>>>> 
>>>>
>>>
>>> The problem is that button actions are not guaranteed to be processed in 
>>> the order they are listed.  This is because some actions (such as 
>>> $action-navigate) are handled asynchronously during the TWCore refresh 
>>> cycle.  In your example code, both setfield widgets are processed before 
>>> the navigate widget.  Thus, by the time the navigate widget is invoked, 
>>> "openLinkFromInsideRiver" has already been reset back to "below".
>>>
>>> However, there *is* a way to split the actions into two parts, so that 
>>> the first part is performed (and *completed*) before the second part is 
>>> invoked.  To do this, you use actions that are in the body of the $button 
>>> widget as well as the actions=... parameter of the $button widget.  The 
>>> "body" actions will be performed first, followed by the parameter actions.
>>>
>>> Try this:
>>> <$button class="tc-btn-invisible tc-tiddlylink" actions="""
>>><$action-navigate $to=<> />
>>><$action-setfield 
>>> $tiddler="$:/config/Navigation/openLinkFromInsideRiver" text="below"/>
>>> """>
>>> <$action-setfield 
>>> $tiddler="$:/config/Navigation/openLinkFromInsideRiver" text="above"/>
>>> << Previous
>>> 
>>>
>>> enjoy,
>>> -e
>>>
>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "TiddlyWiki" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to tiddlywiki+...@googlegroups.com.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/tiddlywiki/30882e1f-bbc9-46c6-b57e-1bb997bc21e4n%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/tiddlywiki/30882e1f-bbc9-46c6-b57e-1bb997bc21e4n%40googlegroups.com?utm_medium=email_source=footer>
>> .
>>
>

-- 
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/091c11bb-cb2b-4e8a-8cab-fcea8d0e3e1dn%40googlegroups.com.

[tw5] Re: Specify in link if tiddler should open above or below current

[Anjar]

Thank you both!

I tried your solution, @Eric, but it didn't seem to work; I tried to move 
<$action-navigate 
$to=<> /> into the body, but that didn't help either. So 
perhaps the problem is more complex than simply changing 
$:/config/Navigation/openLinkFromInsideRiver

However, this was a very interesting way to force a specific sequence of 
events!

Best,
Anders

søndag 23. mai 2021 kl. 17:50:27 UTC+2 skrev Eric Shulman:

> On Sunday, May 23, 2021 at 7:53:40 AM UTC-7 Anjar wrote:
>
>> Hi,
>> I have some tiddlers in sequence with links to previous/next at the 
>> bottom. To keep the order in the story, I want previous tiddlers to open 
>> above the current but he next to open below. Is it possible to achieve this 
>> in some way?
>> I tried this, but without success:
>>
>> <$button class="tc-btn-invisible tc-tiddlylink">
>> <$action-setfield $tiddler="$:/config/Navigation/openLinkFromInsideRiver" 
>> text="above"/>
>> <$action-navigate $to=<> />
>> <$action-setfield $tiddler="$:/config/Navigation/openLinkFromInsideRiver" 
>> text="below"/>
>> << Previous
>> 
>>
>
> The problem is that button actions are not guaranteed to be processed in 
> the order they are listed.  This is because some actions (such as 
> $action-navigate) are handled asynchronously during the TWCore refresh 
> cycle.  In your example code, both setfield widgets are processed before 
> the navigate widget.  Thus, by the time the navigate widget is invoked, 
> "openLinkFromInsideRiver" has already been reset back to "below".
>
> However, there *is* a way to split the actions into two parts, so that the 
> first part is performed (and *completed*) before the second part is 
> invoked.  To do this, you use actions that are in the body of the $button 
> widget as well as the actions=... parameter of the $button widget.  The 
> "body" actions will be performed first, followed by the parameter actions.
>
> Try this:
> <$button class="tc-btn-invisible tc-tiddlylink" actions="""
><$action-navigate $to=<> />
><$action-setfield 
> $tiddler="$:/config/Navigation/openLinkFromInsideRiver" text="below"/>
> """>
> <$action-setfield $tiddler="$:/config/Navigation/openLinkFromInsideRiver" 
> text="above"/>
> << Previous
> 
>
> enjoy,
> -e
>

-- 
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/30882e1f-bbc9-46c6-b57e-1bb997bc21e4n%40googlegroups.com.

[tw5] Specify in link if tiddler should open above or below current

[Anjar]

Hi,

I have some tiddlers in sequence with links to previous/next at the bottom. 
To keep the order in the story, I want previous tiddlers to open above the 
current but he next to open below. Is it possible to achieve this in some 
way?

I tried this, but without success:

<$button class="tc-btn-invisible tc-tiddlylink">
<$action-setfield $tiddler="$:/config/Navigation/openLinkFromInsideRiver" 
text="above"/>
<$action-navigate $to=<> />
<$action-setfield $tiddler="$:/config/Navigation/openLinkFromInsideRiver" 
text="below"/>
<< Previous


Best,
Anders

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/88e21b56-2f89-47e0-9b7b-1f3f44c3ec79n%40googlegroups.com.

[tw5] Re: Hard-replace macros at tiddler save

[Anjar]

Another use case was just posted (on how to combine the text from several 
tiddlers into a single tiddler so that the original tiddlers can be 
deleted): https://groups.google.com/g/tiddlywiki/c/xTCzMIj0uqs Good 
solutions were suggested, but it would also be very simple to just write 
<<>> and have it replaced with the 
text of those tiddlers or  <> if one 
wants to keep transcluding

Best,
Anders

fredag 14. mai 2021 kl. 16:31:33 UTC+2 skrev PMario:

> On Friday, May 14, 2021 at 12:04:01 PM UTC+2 Anjar wrote:
>
> - You are guaranteed that the output will not change. In the permalink 
>> case, I think, the example would be to replace <> with 
>> something like <$button><$list 
>> filter="[created[..aTitle!!created..]]"><$action-navigate 
>> $to=<> />aTitle where ..aTitle!!created.. 
>> is not a reference but the actual value
>>
>> Thoughts?
>>
>
> I think in general this is a sensible idea. ... But I also think it's 
> "over-engineering" ... 
>
> If exporting "connected" tiddler is a problem, we may need to improve the 
> "export" mechanisms. Which imo would be the right place to tackle this 
> specific problem. 
>
> just a thought.
> 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 view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/6fdfc783-3928-4154-8a4b-610dda4c499cn%40googlegroups.com.

Re: [tw5] Combine tiddlers into one

[Anjar]

Hi,

This would be very easy if we had a general way to hard-replace macros at 
tiddler save; see https://groups.google.com/g/tiddlywiki/c/crnjiJ4Spq4 (I'm 
mentioning it here since google groups doesn't show backlinks..)

Best,
Anders

lørdag 15. mai 2021 kl. 11:41:31 UTC+2 skrev saq.i...@gmail.com:

> Below are three different ways to do this using reduce and without 
> wikify. The last one uses a custom filter printf[] that is attached.
> Note that you can use a tiddler for your template as well.
>
> *#1 - addprefix galore*
>
> <$button> save to a single tiddler 
> <$vars lb="
> "> 
> <$action-setfield $tiddler="report" text={{{ [tag[About]] 
> :reduce[get[text]addprefixaddprefixaddprefix{!!title}addprefix[!!]addprefixaddprefix]
>  
> }}}/> 
>  
> 
>
> *#2 - search-replace*
>
> <$button> save to a single tiddler 
> <$vars template="
> !! _TITLE_
>
> _TEXT_
> "> 
> <$action-setfield $tiddler="report" text={{{ [tag[About]] 
> :reduce[search-replace:gi[_TITLE_],{!!title}search-replace[_TEXT_],{!!text}addprefix]
>  
> }}}/> 
>  
> 
>
> *#3 - printf[]*
>
> <$button> save to a single tiddler 
> <$vars template="
> !! $0$
>
> $1$
> "> 
> <$action-setfield $tiddler="report" text={{{ [tag[About]] 
> :reduce[printf{!!title},{!!text}addprefix] }}}/> 
>  
> 
>

-- 
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/ae1f1f65-d009-4e8b-81cb-252dea543683n%40googlegroups.com.

[tw5] Re: Can ordinary tiddlers be made into shadow tiddlers?

[Anjar]

Thank you for the insights!

mandag 10. mai 2021 kl. 03:33:19 UTC+2 skrev TW Tones:

> Anjar,
>
> Shadow tiddlers is quite a big subject since it relates to a large part of 
> the core, plugins etc... 
>
> I do personally believe there are many opportunities to make use of this 
> infrastructure for much more, which I think you question hints at. I have 
> done quite a lot of exploration in this space and will share but a little 
> in this response.
>
> Shadow tiddlers are known as tiddlers inside a plugin, but a plugin is 
> only a tiddler containing one or more tiddlers defined in JSON. This allows 
> more than one tiddler to be packaged in another tiddler. Accessing such 
> embedded tiddlers is via the shadow tiddler model.
>
> There is already code to support converting tiddlers to JSON, and it is 
> the import process. After dropping a set of tiddlers on a wiki (any wiki), 
> rename the $:/import tiddler before importing, (remove its existing 
> fields). It is then a JSON tiddler. However to convert it so it allows 
> access to the tiddlers within as shadows, you need to change it into a 
> plugin. This is not complex as it the case with most things in TiddlyWiki.
>
> Changing a JSON Tiddler of tiddlers into a plugin and related shadow 
> tiddlers.
>
>- Edit the JSON tiddler and add or change the plugin-type field to 
>have a value of plugin
>
> You now have a plugin tiddlers, and you can find it in the list of 
> plugins, bur it is not making use of all the features, it only has a 
> contents tab.
>
> You can now edit these to turn the shadows into real tiddlers, drag and 
> drop between wikis and export it for import later.
>
> Cool yes?
> Tones
>
> On Monday, 10 May 2021 at 03:12:59 UTC+10 Mark S. wrote:
>
>> Tinka <https://tinkaplugin.github.io/> is a tool for making tiddlers 
>> into a plugin. You could also use it to add tiddlers to an existing 
>> "storage" plugin.
>>
>> On Sunday, May 9, 2021 at 4:28:15 AM UTC-7 Anjar wrote:
>>
>>> Hi!
>>>
>>> Shadow tiddlers have some nice properties, s I wonder: can ordinary 
>>> tiddlers be made into shadow tiddlers or is it technically difficult? So 
>>> that if a new tiddler is created with the same title, the old one 
>>> disappears but is lurking in the background as a shadow?
>>>
>>> Best,
>>> Anders
>>>
>>

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/4238904b-94b6-4947-8b0e-a752b646f9a8n%40googlegroups.com.

[tw5] Hard-replace macros at tiddler save

[Anjar]

Hi,

Somewhere in the thread on permalinks 
 it was suggested to 
have a macro that is actually replaced when the tiddler is saved. Say <<>> will actually be replaced by the wikified output of the macro, 
whereas <> is only replaced at rendering, as it is now

Why would this be useful?
- When sharing a tiddler with someone who doesn't have <> in their 
tiddlywiki
- Enhanced performance (?)
- You are guaranteed that the output will not change. In the permalink 
case, I think, the example would be to replace <> with 
something like <$button><$list 
filter="[created[..aTitle!!created..]]"><$action-navigate 
$to=<> />aTitle where ..aTitle!!created.. 
is not a reference but the actual value


Thoughts?


Best,
Anders

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/fcbce811-7118-406b-8105-722e8b4cd6can%40googlegroups.com.

[tw5] Re: A Prototype of UID's for stable permalinks

[Anjar]

Ad the two latest post; these solutions are very close to the alternative 
permalink button suggested here: 
https://groups.google.com/g/tiddlywiki/c/QOzs3CVtosU/m/QZhVupmUBAAJ 
creating a permalink field with sluggified title + timestamp (always unique 
within a wiki), and keeping old versions so that links will continue to work

Best,
Anders
tirsdag 11. mai 2021 kl. 05:15:34 UTC+2 skrev cj.v...@gmail.com:

> The beauty of your link is that it is obvious what the link is for.  That 
> really is a great thing.  Which I know I would eventually break because I 
> am always slightly tweaking everything towards titles/names/descriptions 
> that better fit changing scope/circumstances/you-name-it.
>
> With a wee number, I'll never monkey around with it..  Which is the safety 
> net I'm looking for: something stable that I know I will never tweak, 
> tweaking being my nature when it comes to text.  I'm just as likely to 
> change a description (scope of tiddler may have changed), or improved the 
> wording or something.
>
> I'm pretty stuck in a method similar to the Oracle Sequence Numbers I'm 
> familiar with.  I've always been more comfortable with identifiers never 
> based on real-world values.
>
>
>
> On Monday, May 10, 2021 at 11:17:22 PM UTC-3 TW Tones wrote:
>
>> Try this; 
>>
>> https://tiddlywiki.com/#:[description[Browser extension for Firefox]]
>>
>> If you could rename and save this tiddler, it will still work until you 
>> modify the description or clone the tiddler.
>>
>> Eureka!
>>
>> I think I have finally come up with a simple, total, robust solution to 
>> permalinks, serial number, UID and GUID's not to put it in words and a 
>> plugin. 
>>
>> I can write the specification if anyone wants to help, otherwise it will 
>> take a little longer
>>
>> Regards
>> Tones
>>
>> On Monday, 10 May 2021 at 03:07:28 UTC+10 cj.v...@gmail.com wrote:
>>
>>> Pff, no worries.  It is very easy to call things by various "names", and 
>>> for the "intent" of words to match exactly all of one's thoughts related to 
>>> the words, while meaning something entirely different to somebody else.
>>>
>>> So context gets jumbled easily.
>>>
>>> Imagine you place in all sorts of places all over the web a URL to a 
>>> specific tiddler in one TiddlyWiki instance.
>>>
>>> So many things can happen to break all of those links.  You might move 
>>> the TiddlyWiki to a completely different host.  You might actually rename 
>>> the TiddlyWiki itself.
>>>
>>> So all kinds of worse problems than having the same URL suddenly pop 
>>> open a few different unrelated tiddlers along with the intended one.  That 
>>> is barely a blip in the scheme of things.
>>>
>>> Easy enough to have some Tiddler in each TiddlyWiki that let's you know 
>>> when you've imported some Tiddler that now has you with duplicate UID's.  
>>> At which point, go to the imported tiddler and delete its UID, giving it a 
>>> new one only if you really need to.
>>>
>>> If your workflow has you importing tiddlers incessantly between your 
>>> TiddlyWikis, then you need to include in your workflow something that helps 
>>> you with weeding your garden.
>>>
>>> Or prepare to have a more complicated system for uniquely identifying 
>>> your tiddlers and having longer and more complicated URL's.
>>>
>>> I'm pretty sure somebody will come up with something much more perfect 
>>> than what I've come up with, but there will be costs / trade-offs.
>>>
>>> Only you know what kind of trade-offs you can live with.  (You won't 
>>> know the trade-offs without trying the various possibilities.)
>>>
>>> For me, this UID-permalink thing (or whatever I finally call it), is the 
>>> good enough lean/mean/simple/robust/no-break-anything-else solution for 
>>> me.  To each his/her own.
>>>
>>> On Sunday, May 9, 2021 at 1:48:33 PM UTC-3 ludwa6 wrote:
>>>
 Sorry Charlie for my sloppy wording: by "named-alike," what i meant was 
 two tiddlers having the same UID-permalink.  As for titles, i am very 
 comfortable with the conflict avoidance measures built into the TW5 import 
 process.

 In any case, i am reassured by your answer(s- this last and the one 
 above) that the risk involved in starting to use this thing -and then only 
 for its intended purpose, as you say- is quite small.  The biggest risk i 
 see is the sort of confusion that might arise if i send somebody a link to 
 something, and what they get instead is a page with an extra tiddler (or 
 few -see below) that would tend to throw into question the relevance of 
 that link that the web user trusted enough to follow -especially if the 
 unintended tiddler(s) appear larger and/or louder, maybe higher on the 
 page 
 (? something i'll only learn thru experience; am comfortable w/ that).

 Still: i do suspect that i'm gonna somehow wind up with multiple 
 tiddlers having the same number in that UID field, and that before very 
 long i will wind up 

[tw5] Re: [discussion] Titles in tiddlywiki

[Anjar]

Hi,

I'm not sure this is what you want to discuss, but *why *do titles need to 
be unique? Aren't these examples kind of equivalent

[[aTitle]] -> <$button><$list filter="[title[aTitle]]"><$action-navigate 
$to=<> />aTitle
{{aTitle}} -> <$list 
filter="[title[aTitle]get[text]]"><>
{{aTitle!!aField}} -> <$list 
filter="[title[aTitle]get[aField]]"><>

I see that there is a problem with templates that have to be unique

However, if titles don't have to be unique, then we can think - why not 
make the standard field (now title) customizable?

Best,
Anders

onsdag 12. mai 2021 kl. 02:11:29 UTC+2 skrev TW Tones:

> Example of 3.
>
> https://groups.google.com/g/tiddlywiki/c/yw51tANUCKI is a link to this 
> discussion
>
>
>- a tiddlewr titles "
>https://groups.google.com/g/tiddlywiki/c/yw51tANUCKI; is not easy to 
>read, but is created if I drop this link on a wiki.
>- Any title prefixed " https://groups.google.com/g/tiddlywiki;  is a 
>google group discussion, so copy the full title to a link field called 
>discussion and keep the title " c/yw51tANUCKI " ready for you to rename 
>with the thread title.
>
> Tones
>
>
> On Wednesday, 12 May 2021 at 09:39:22 UTC+10 TW Tones wrote:
>
>> Folks,
>>
>> I just wanted to start a thread on titles in tiddlywiki. One reason is I 
>> am raising this is I personally never have trouble finding a suitable 
>> title, I rarely need to rename one where it will cause an issue, but others 
>> find this perplexing and difficult. I also have two ideas I believe we 
>> should pursue as a community. So hopefully we can discuss these here;
>>
>>1. Share Tips and tricks in handling naming tiddler titles
>>2. I propose we investigate introducing some tools to help automate 
>>tiddler naming that we can then manually override. An example may be 
>> child 
>>tiddlers being given automatic names, but there may be other tricks 
>>available
>>3. Drag and drop from other tiddlers, wikis, text and links can 
>>create new tiddlers. This is rapid way of capturing content. I would like 
>>to investigate automated tools to take a title such as one containing 
>> http 
>>(because it was a dropped URL) move the title to an appropriate field, 
>>create a link and propose a new tiddler title. Keeping in mind that we 
>> can 
>>parse titles to establish are they email addresses, permalinks, filters, 
>>search urls and much more. 
>>
>> Perhaps respond with references to the above list numbers. We can start 
>> other threads in needed.
>>
>> Tones
>>
>

-- 
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/740dbd13-cf50-4bfa-a124-fee2facf34a1n%40googlegroups.com.

[tw5] Re: Options for keeping revision history?

[Anjar]

@Soren you're right, I was only thinking on the single file edition where 
it would be difficult to follow a tiddler across time if the title is 
changed

mandag 10. mai 2021 kl. 21:07:19 UTC+2 skrev Soren Bjornstad:

> On Monday, May 10, 2021 at 9:10:40 AM UTC-5 Anjar wrote:
>
>> Git isn't able to take care of title changes
>
>
> Really? Git normally detects renames just fine unless you massively change 
> the contents at the same time you change the filename. I found some 
> examples in my own folder wiki controlled by Git 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 view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/910cc2a7-e242-4f7f-a6ec-f835ccf96a15n%40googlegroups.com.

[tw5] Re: Options for keeping revision history?

[Anjar]

Non-plugin alternatives include git and sqlite 
; both will keep the wiki size low, 
but neither will have the history directly available in the wiki. Git isn't 
able to take care of title changes, whereas the SQLite-history follows the 
toddler (but it needs a server and is still under development)

Best,
Anders

mandag 10. mai 2021 kl. 14:33:39 UTC+2 skrev si:

> Thanks Mario for the comprehensive reply.
>
> I have decided to create my own history-saving macro, which I will use 
> only in specific instances, rather than across my whole wiki. For now I'm 
> just saving data, I will worry about other features in the future.
>
> This is what I have at the moment:
>
> \define save-history()
> <$vars timestamp=<> >
> <$vars history-tiddler-title={{{ 
> [addsuffix[/history/]addsuffix] }}} >
> <$list filter="[fields[]]" variable=field-name>
> <$action-setfield $tiddler=<> 
> $field={{{ [addsuffix[-history]] }}} $value={{{ 
> [get] }}}/>
> 
> 
> 
> \end
>
> So every time I activate this macro I should get a new "history-tiddler" 
> named /history/. Relink titles 
> 
>  
> will make sure that this data remains associated with the correct tiddler.
>
> I am wondering if it would make more sense to use a JSON tiddler to store 
> history? I would do essentially the same thing, but all history for a 
> particular tiddler would be stored in a single tiddler called 
> /history as JSON entries (using JsonMangler 
> ). Would this be better in 
> terms of performance when I end up with a large number of history-tiddlers, 
> or do you think it makes more sense to stick with what I have done?
> On Sunday, 9 May 2021 at 18:12:35 UTC+1 PMario wrote:
>
>> On Sunday, May 9, 2021 at 6:40:48 PM UTC+2 si wrote:
>>
>>> I've become kind of interested in keeping a full revision history of my 
>>> wiki - i.e. be able to see every single change I've made to every tiddler. 
>>>
>> I know about http://j.d.revisions.tiddlyspot.com/, which I like a lot, 
>>> but it has a couple of disadvantages for my use case:
>>>
>>
>> As far as I know, that's the only plugin which create revisions. And 
>> there is the "trashbin plugin" [1]
>>  
>>
>>>
>>>1. Revisions are only created when you click the save button from 
>>>the edit toolbar. Most of the time I save tiddlers with Ctrl+Enter. 
>>>
>>> IMO this can be solved. .. but you'll need to mess with the core 
>> EditTemplate ... \define save-tiddler-actions() 
>>
>>>
>>>1. I also use Streams a lot, where again changes made to tiddlers 
>>>won't be recorded by the plugin. 
>>>
>>> I think, Streams is designed, to be modified a lot and it uses 
>> dynamically created tiddler titles. .. So you will probably create a lot of 
>> "strange looking titles". So without some heavy support for a "recovery UI" 
>> you will get problems there. 
>>
>>>
>>>1. I use a single html wiki for all my stuff. Presumably having a 
>>>new tiddler created for every change I make will soon start to inflate 
>>> and 
>>>slow down my wiki? Or maybe I am wrong about this?
>>>
>>> IMO it will make the whole thing a lot more complex. 
>>  
>>
>>> So I guess I'm interested in whether it is even practical to keep such 
>>> an extensive history of my wiki use, and if so what options are available?
>>>
>>
>> I did think about a possibility (just in my mind), that it should 
>> possible to store the "diffs only". ... So similar to, what can be seen in 
>> the TW import mechanism. Where you can see "the diff" the difference 
>> between the newly imported tiddler and an existing one. ... 
>>
>> A similar mechanism would allow us to create something that is called a 
>> "patch". ... So it contains the commands, that need to be applied to the 
>> existing tiddler, to get the OLD tiddler back. ... 
>>
>> The problem with a mechanism like this, would be, that you'll need to 
>> apply the patches in order. .. If 1 patch gets lost, there will be a 
>> problem. ... 
>>
>> So the whole handling thing will be complex. .. I didn't think about it 
>> in detail. 
>>
>> -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 view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/76e7138c-506a-41df-823c-8196526151dfn%40googlegroups.com.

[tw5] Re: Relink vs Permalinks

[Anjar]

Hi,

To remove it, just delete the permalink button: (replace URL with your own) 
https://tiddlywiki.com/#%24%3A%2Fcore%2Fui%2FButtons%2Fpermalink

But I don't think we are changing any core functionality with this button; 
all we have done is replaced the single button and all it does is making a 
new field and copying a string to you clipboard. So I don't think it will 
interfere with anything

Best,
Anders

søndag 9. mai 2021 kl. 14:25:28 UTC+2 skrev ludwa6:

> Anders: much as i appreciate the brilliance of your solution to this 
> problem, i think that -since Charlie's come up w/ a different solution that 
> solves the problem w/o opening core functionality to possible corruption 
> (right? i hope!)- then maybe i would do well to remove this 
> "$__core_ui_Buttons_permalink.json" code from my wiki -yes?  
>
> If so, i have to ask (as i'm still a total n00b when it comes to this core 
> / shadow tiddler stuff, obviously): what tiddler(s) do i need to remove or 
> modify to eliminate this risk of creating clone tiddlers that are gonna 
> break the TW upgrade process, as PMario has explained 
> <https://github.com/Jermolene/TiddlyWiki5/discussions/5668>could be a 
> problem.
>
> On Wednesday, May 5, 2021 at 9:39:02 PM UTC+1 Anjar wrote:
>
>> Hi Walt,
>>
>> I am glad it solved the first problem.
>>
>> Ad #2: You are right, permalinks created *earlier *are not affected by 
>> this solution. However, if you *now *rename 
>> the SolutionToProblemOfLinkRot tiddler to ProblemOfLinkRot and click the 
>> permalink button, then both #:[contains:permalink[
>> *solutiontoproblemoflinkrot*-20210505114349833]] (old) 
>> and #:[contains:permalink[*problemoflinkrot*-20210505114349833]] (new) 
>> will work
>>
>> I think it will be very difficult to solve #2 in a general way that 
>> ensures that links already shared will keep working forever. It may be 
>> possible (but I don't know how) to make a solution to search in the 
>> permalink field if the tiddler couldn't be found (eg. /#ProblemOfLinkRot -> 
>> look for problemoflinkrot in the permalink fields -> list all potential 
>> hits). But if you later make a new tiddler called ProblemOfLinkRot, then 
>> the old link will give you the new one
>>
>> Best,
>> Anders
>>
>> onsdag 5. mai 2021 kl. 21:01:01 UTC+2 skrev ludwa6:
>>
>>> Correction to my last: dunno what caused the phenom i reported as #1 
>>> above, but i can no longer replicate that error; the new URL works fine.
>>> However: problem #2 reported above persists -and so my question about a 
>>> potentially simpler solution to this two-headed problem stands.
>>>
>>> /walt
>>>
>>> On Wednesday, May 5, 2021 at 7:38:32 PM UTC+1 ludwa6 wrote:
>>>
>>>> Your spec ticks all the boxes, Anders... So i installed it, but not 
>>>> getting the hoped-for result, alas.
>>>>
>>>> *What i did:* Changed URL on the "ProblemOfLinkRot" tiddler to 
>>>> "SolutionToProblemOfLinkRot"; selected (modified) Permalink button in 
>>>> pulldown tiddler menu -and it copied the composite URL, composed per your 
>>>> specification, to my clipboard, which is also populating the new 
>>>> "Permalink" field, i see.  So far so good... But there is yet a problem 
>>>> -two actually:
>>>>
>>>>1. When i point my browser to the new URL- 
>>>>
>>>> https://meta.tiddlyhost.com/#:[contains:permalink[solutiontoproblemoflinkrot-20210505114349833]]
>>>>  
>>>>- it pulls a blank page.
>>>>2. The old permalink-  https://meta.tiddlyhost.com/#ProblemOfLinkRot 
>>>>-brings me to a "Missing Tiddler" page (not surprising, since a tiddler 
>>>>with that name indeed exists no more, having been overwritten by the 
>>>> new... 
>>>>And that old URL has no "contains" parameter in it).
>>>>
>>>> I hadn't really thought of this problem in terms of having two 
>>>> different URLs pointing to the same tiddler; instead, i was hoping that a 
>>>> UID could be assigned on tiddler creation (ideally a not-too-weird 
>>>> combo-key: original name (guaranteed unique at the time, as you say) plus 
>>>> date would work), which persists across any renaming event in the 
>>>> Permalink 
>>>> field, but is not the title.  Is there some problem w/ this simpler 
>>>> solution that i'm not seeing?
>>>>
>>>> /walt
>>>>
>>>>
>>

[tw5] Can ordinary tiddlers be made into shadow tiddlers?

[Anjar]

Hi!

Shadow tiddlers have some nice properties, s I wonder: can ordinary 
tiddlers be made into shadow tiddlers or is it technically difficult? So 
that if a new tiddler is created with the same title, the old one 
disappears but is lurking in the background as a shadow?

Best,
Anders

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/22821e6b-80f7-4073-a884-fa4f0a8cc109n%40googlegroups.com.

Re: [tw5] Simple php/sqlite3 adaptor

[Anjar]

Hi,

The scripts at https://github.com/andjar/TW-sqlite3 are now updated to also 
support URL parameters; eg. adding ?test=Hi to the URL will create a 
tiddler $:/url/test with text "Hi". A special parameter is "user". If a 
tiddler has field "user" containing "username", the tiddler will only be 
available if ?user=username

The user feature is working but further refinement. We can imagine having 
some sort of varying tiddler privileges; one user being the owner, some 
users having access to edit, others to edit only specified fields, others 
only to read. Another problem may then be possible title collisions across 
users


Best,
Anders

tirsdag 27. april 2021 kl. 18:10:29 UTC+2 skrev Mohammad:

> On Tue, Apr 27, 2021 at 6:57 PM Anjar  wrote:
>
>> @Mohammad currently, I haven't copied that part of the tw-receiver script 
>> yet because having to edit a PHP is not very user friendly, it seems much 
>> better to have the password saved in the database so that you can actually 
>> set it and change it directly from the tiddlywiki. 
>>
>> Hi Anders,
> Many thanks for clarification!
>
>  
>
>> It's probably also better to collect everything in a single PHP-file that 
>> can both load and save the tiddlywiki; eg. if there is no sqlite files 
>> already existing -> download and load an empty tiddlywiki with a customized 
>> tw-receiver tiddler; if a single sqlite file exist, load it; if multiple 
>> sqlite files exist, show a menu.
>>
>
> Yes, that is correct. I tested on a Windows machine using usbwebserver and 
> it works!
>
> Thank you!
>
>  
>
>>
>> Best,
>> Anders
>>
>> tirsdag 27. april 2021 kl. 05:55:13 UTC+2 skrev Mohammad:
>>
>>> Andres,
>>>  Does this need the same configuration as tw-receiver?
>>>  Is there any need to set a password also for sqlit3?
>>>
>>> I could not find the installation? 
>>>
>>>
>>> Best wishes
>>> Mohammad
>>>
>>>
>>> On Sun, Apr 25, 2021 at 6:54 PM Anjar  wrote:
>>>
>>>> Hi,
>>>>
>>>> I've started on a very simple php/sqlite3 backbone for tiddlywiki: 
>>>> https://github.com/andjar/TW-sqlite3/tree/main
>>>>
>>>> The main feature is perhaps that revisions are kept in the database 
>>>> (deleted tiddlers and edits). The tiddlers are saved to the sqlite file in 
>>>> three tables; tiddlers, tiddlertext, and fields. The tiddlers are assigned 
>>>> a UUID at first save. If the tiddler is deleted, the tiddler table will 
>>>> set 
>>>> the tiddler status to DELETED. If the text or any field is changed, the 
>>>> new 
>>>> value is added as a new row and the former version set to OUTDATED (or 
>>>> DELETED if the field is deleted)
>>>>
>>>> Best,
>>>> Anders
>>>>
>>>> -- 
>>>> You received this message because you are subscribed to the Google 
>>>> Groups "TiddlyWiki" group.
>>>> To unsubscribe from this group and stop receiving emails from it, send 
>>>> an email to tiddlywiki+...@googlegroups.com.
>>>> To view this discussion on the web visit 
>>>> https://groups.google.com/d/msgid/tiddlywiki/bb2c6b4c-e3fb-4a81-8bea-cd429d7bd142n%40googlegroups.com
>>>>  
>>>> <https://groups.google.com/d/msgid/tiddlywiki/bb2c6b4c-e3fb-4a81-8bea-cd429d7bd142n%40googlegroups.com?utm_medium=email_source=footer>
>>>> .
>>>>
>>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "TiddlyWiki" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to tiddlywiki+...@googlegroups.com.
>>
> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/tiddlywiki/6d4630b4-74ec-43fe-b1fa-0bd6040ebd48n%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/tiddlywiki/6d4630b4-74ec-43fe-b1fa-0bd6040ebd48n%40googlegroups.com?utm_medium=email_source=footer>
>> .
>>
>

-- 
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/eee251fe-2e3d-48fc-bf3a-9b344ca3daa0n%40googlegroups.com.

[tw5] Re: Relink vs Permalinks

[Anjar]

Hi Walt,

I am glad it solved the first problem.

Ad #2: You are right, permalinks created *earlier *are not affected by this 
solution. However, if you *now *rename the SolutionToProblemOfLinkRot 
tiddler to ProblemOfLinkRot and click the permalink button, then 
both #:[contains:permalink[*solutiontoproblemoflinkrot*-20210505114349833]] 
(old) and #:[contains:permalink[*problemoflinkrot*-20210505114349833]] 
(new) will work

I think it will be very difficult to solve #2 in a general way that ensures 
that links already shared will keep working forever. It may be possible 
(but I don't know how) to make a solution to search in the permalink field 
if the tiddler couldn't be found (eg. /#ProblemOfLinkRot -> look for 
problemoflinkrot in the permalink fields -> list all potential hits). But 
if you later make a new tiddler called ProblemOfLinkRot, then the old link 
will give you the new one

Best,
Anders

onsdag 5. mai 2021 kl. 21:01:01 UTC+2 skrev ludwa6:

> Correction to my last: dunno what caused the phenom i reported as #1 
> above, but i can no longer replicate that error; the new URL works fine.
> However: problem #2 reported above persists -and so my question about a 
> potentially simpler solution to this two-headed problem stands.
>
> /walt
>
> On Wednesday, May 5, 2021 at 7:38:32 PM UTC+1 ludwa6 wrote:
>
>> Your spec ticks all the boxes, Anders... So i installed it, but not 
>> getting the hoped-for result, alas.
>>
>> *What i did:* Changed URL on the "ProblemOfLinkRot" tiddler to 
>> "SolutionToProblemOfLinkRot"; selected (modified) Permalink button in 
>> pulldown tiddler menu -and it copied the composite URL, composed per your 
>> specification, to my clipboard, which is also populating the new 
>> "Permalink" field, i see.  So far so good... But there is yet a problem 
>> -two actually:
>>
>>1. When i point my browser to the new URL- 
>>
>> https://meta.tiddlyhost.com/#:[contains:permalink[solutiontoproblemoflinkrot-20210505114349833]]
>>  
>>- it pulls a blank page.
>>2. The old permalink-  https://meta.tiddlyhost.com/#ProblemOfLinkRot 
>>-brings me to a "Missing Tiddler" page (not surprising, since a tiddler 
>>with that name indeed exists no more, having been overwritten by the 
>> new... 
>>And that old URL has no "contains" parameter in it).
>>
>> I hadn't really thought of this problem in terms of having two different 
>> URLs pointing to the same tiddler; instead, i was hoping that a UID could 
>> be assigned on tiddler creation (ideally a not-too-weird combo-key: 
>> original name (guaranteed unique at the time, as you say) plus date would 
>> work), which persists across any renaming event in the Permalink field, but 
>> is not the title.  Is there some problem w/ this simpler solution that i'm 
>> not seeing?
>>
>> /walt
>>
>>
>>
>> On Wednesday, May 5, 2021 at 5:12:15 PM UTC+1 Anjar wrote:
>>
>>> Hi,
>>>
>>> Here is a demo for a new permalink button. It creates a new field called 
>>> permalink and inserts -. Since the title is 
>>> unique at creation, this string should be unique (?). Further, it copies 
>>> the appropriate link to the clipboard; 
>>> https://tiddlywiki.com/#:[contains:permalink[new-tiddler-20200509141702846]].
>>>  
>>> If you change the title, the button appends the new >> title>- to the permalink field so that both links go to the same 
>>> tiddler
>>>
>>> Best,
>>> Anders
>>>
>>>

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/1e1b10fe-0fa7-4aa2-b5af-a9161d2e2f4en%40googlegroups.com.

[tw5] Re: Relink vs Permalinks

[Anjar]

Hi,

Here is a demo for a new permalink button. It creates a new field called 
permalink and inserts -. Since the title is 
unique at creation, this string should be unique (?). Further, it copies 
the appropriate link to the 
clipboard; 
https://tiddlywiki.com/#:[contains:permalink[new-tiddler-20200509141702846]]. 
If you change the title, the button appends the new - to the permalink field so that both links go to the same 
tiddler

Best,
Anders

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/7a484ee5-05f0-48cf-a7dd-8cd15c72a6c4n%40googlegroups.com.


$__core_ui_Buttons_permalink.json
Description: application/json

[tw5] Re: Relink vs Permalinks

[Anjar]

Hi Walt,

It should be trivial to modify the permalink button to produce links as 
https://tiddlywiki.com/#:[created[2014090408570]] but the creation time 
is not guaranteed to be unique (the link will then open both tiddlers, so 
no harm is done), although in practice it usually will be

An alternative is to make the permalink button add the current title to a 
separate field (say permalink) and use that field to produce a URL like 
https://tiddlywiki.com/#:[permalink[aReadableTitle]] 
 The strength is 
that the URL then will be human-readable and you have the history of old 
titles, but again, it is not guaranteed to be unique

If you are not afraid to add plugins, there is a plugin (
https://ibnishak.github.io/Tesseract/pluginsandmacros/index.html#UUID%20Plugin) 
to create UUIDs that can also be used to populate a separate field to get 
URLs like https://tiddlywiki.com/#:[uuid[anUUID]] 


Best,
Anders

onsdag 5. mai 2021 kl. 15:50:00 UTC+2 skrev TiddlyTweeter:

> Ciao cj.v..., 
>
> Interesting! 
> Functionally that is working like a SURROGATE permanent REDIRECT. *It is 
> a clever solution!* but requires the logic of the Wiki to change 
> considerably and its owner to know what to do. :-)
>
> HOW, for instance, do you quickly generate a PERMALINK you can quickly 
> post online?
>
> Probing :-)
> TT
>
> On Wednesday, 5 May 2021 at 15:43:16 UTC+2 cj.v...@gmail.com wrote:
>
>> G'day walt,
>>
>> That is a huge pain point for me.  In my previous career, I relied 
>> heavily on the ProjectForum Wiki to keep track of everything.  It did not 
>> use page names in URL links, but rather used auto-generated unique 
>> identifiers.  So I could change page titles to my heart's content, knowing 
>> that URL links were always stable.
>>
>> My approach, still formulating it, is to edit tiddlers via custom forms.  
>> The tiddlers have auto-generated unique identifiers stored in the title.  
>> What would normally be the title goes in a field.
>>
>> That works fine right as-is for structured data.  I haven't looked into 
>> setting up the formatting buttons (bold, italics, etc.) for formatting text.
>>
>> I think this could still work for you well if you have an easy way to 
>> lookup tiddlers via a field instead of via title, and if you can overcome 
>> that mindset change.
>>
>> On Wednesday, May 5, 2021 at 5:34:24 AM UTC-3 ludwa6 wrote:
>>
>>> The more i use TW, the more concerned i become about maintaining data 
>>> integrity -and so this issue has boiled to the top of my queue: how can i 
>>> continue to enjoy the benefits of TW (+ Relink plugin) flexibility, without 
>>> compromising the integrity of Permalinks?  
>>>
>>> This feels like a deep problem that goes right to core TW architecture- 
>>> since, as PMario explained in last thread 
>>> , 
>>> tiddler immutability is tied to its Title (so how can Relink even work, i 
>>> wonder?)- but if i've learned anything here, it is to not underestimate the 
>>> creative problem-solving ability of this group :-)... SO:
>>>
>>> From a non-technical perspective, what i'd like to do is have some 
>>> immutable UID (based on date-time, or maybe date+ a serial number, like 
>>> -mm-dd-serialnum) that is used for Permalinks (i.e. shared w/ the 
>>> outside web that is not Relink-aware), but still have Title field and 
>>> Relink plugin (and everything else for that matter) work just as it does 
>>> now, from the TW editor's perspective.
>>>
>>> Is this a reasonable feature design goal, i wonder?  If so, i'd like to 
>>> do what i can to help make it happen!
>>>
>>> /walt
>>>
>>>

-- 
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/e94c7143-bcee-4c96-9b4f-3de99ed4eefen%40googlegroups.com.

[tw5] Re: Relink vs Permalinks

[Anjar]

Hi,

I agree with you and see the problem. One simple solution is just sharing 
links like https://tiddlywiki.com/#:[created[2014090408570]]

Best,
Anders
onsdag 5. mai 2021 kl. 14:15:43 UTC+2 skrev ludwa6:

> OK @Tones & @TT: if neither of you guys sees this as problematic, then i'd 
> better explain myself better.  Here's a meta-example i've just documented:
>
>1.  Create a tiddler on this topic, and give it a permalink: 
>https://meta.tiddlyhost.com/#AvoidingLinkRot.  Share link with 
>friends, to engage their support in taming this dragon!
>2.  Recall that "Link Rot" is a well-known problem, which Wikipedia 
>might know about- and indeed: see 
>https://en.wikipedia.org/wiki/Link_rot
>3. Realise that- in keeping w/ principle of AtomicGranularity- i 
>should probably limit this tiddler to describing the problem (including 
>link to that Wikipedia article and maybe just my review of that material) 
>and rename it after that article: "ProblemOfLinkRot"
>4. Work away on that renamed tiddler, adding my detailed analysis of 
>the article, and the problem.  
>5. Puzzled after a time as to why nobody is commenting on my work, 
>check the link -and find out that it's broken. (yeesh! and nobody told me? 
>did they even click the link i shared?)
>
> i've run through this loop enough times, it's already getting old.  Could 
> it be that it's just me, i wonder?
>
> /walt
> On Wednesday, May 5, 2021 at 10:51:28 AM UTC+1 TiddlyTweeter wrote:
>
>> Ciao walt,
>>
>> Right. Tiddler PERMALINK-ability posted as URLs elsewhere is intimately 
>> tied to NOT changing Titles.
>>
>> Personally I can't get in a hot sweat over that. That is no different 
>> than any other web page.
>> SURE you could get into REDIRECTS on a server or up the complexity 
>> within  TW of self-REDIRECTS I guess?
>>
>> I don't really see the point though :-). 
>>
>> Best wishes
>> TT
>>
>> On Wednesday, 5 May 2021 at 10:34:24 UTC+2 ludwa6 wrote:
>>
>>> The more i use TW, the more concerned i become about maintaining data 
>>> integrity -and so this issue has boiled to the top of my queue: how can i 
>>> continue to enjoy the benefits of TW (+ Relink plugin) flexibility, without 
>>> compromising the integrity of Permalinks?  
>>>
>>> This feels like a deep problem that goes right to core TW architecture- 
>>> since, as PMario explained in last thread 
>>> , 
>>> tiddler immutability is tied to its Title (so how can Relink even work, i 
>>> wonder?)- but if i've learned anything here, it is to not underestimate the 
>>> creative problem-solving ability of this group :-)... SO:
>>>
>>> From a non-technical perspective, what i'd like to do is have some 
>>> immutable UID (based on date-time, or maybe date+ a serial number, like 
>>> -mm-dd-serialnum) that is used for Permalinks (i.e. shared w/ the 
>>> outside web that is not Relink-aware), but still have Title field and 
>>> Relink plugin (and everything else for that matter) work just as it does 
>>> now, from the TW editor's perspective.
>>>
>>> Is this a reasonable feature design goal, i wonder?  If so, i'd like to 
>>> do what i can to help make it happen!
>>>
>>> /walt
>>>
>>>

-- 
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/5a4e8412-a4b1-4c68-8add-9b611474af8an%40googlegroups.com.

Re: [tw5] Looking for reading material: using javascript libraries in TiddlyWiki

[Anjar]

@cj.v Great! You may have read it, but I accidentally came across this: 
https://phiresky.github.io/blog/2021/hosting-sqlite-databases-on-github-pages/

Best,
Anders
søndag 2. mai 2021 kl. 17:16:25 UTC+2 skrev cj.v...@gmail.com:

> Good grief:  Neocities *is* just for hosting static sites (html, css, 
> javascript and other files.)  sql.js *is *a good fit for Neocities.
>
> On Sunday, May 2, 2021 at 11:54:35 AM UTC-3 Charlie Veniot wrote:
>
>> G'day g'day an Happy Sunday!
>>
>> Neocities if just for hosting static sites.  sql.js would have been a 
>> good fit for Neocities.
>>
>> On Sunday, May 2, 2021 at 11:05:35 AM UTC-3 hww...@gmail.com wrote:
>>
>>> G'day cj.v:
>>>
>>> Do you happen to know if neocities could host such a server?  If so, do 
>>> we have any Documentation/Knowledge that might help us "make it so"?
>>>
>>> On Sunday, May 2, 2021 at 9:23:08 AM UTC-4 cj.v...@gmail.com wrote:
>>>
>>>> G'day Anders,
>>>>
>>>> Yup, sure did.  Very cool.
>>>>
>>>> Serverless sql.js would be more my cup of tea, but sqlite solution with 
>>>> server might make for a pretty decent plan B, 
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> On Sunday, May 2, 2021 at 8:39:53 AM UTC-3 Anjar wrote:
>>>>
>>>>> @cj.v did you see this thread 
>>>>> https://groups.google.com/g/tiddlywiki/c/zcgAdcms0zM on php+sqlite? 
>>>>> Requires a server though
>>>>>
>>>>> Best,
>>>>> Anders
>>>>> lørdag 1. mai 2021 kl. 23:15:10 UTC+2 skrev brian@gmail.com:
>>>>>
>>>>>> https://btheado.github.io/tw-widget-tutorial/ - this is another 
>>>>>> resource. It is focused specifically on widgets and doesn't cover any of 
>>>>>> the other integration points mentioned by Jeremy. When I wrote it, I ran 
>>>>>> out of steam by the time I got to the third-party javascript integration 
>>>>>> and so there isn't much there to help answer Charlie's original 
>>>>>> question. 
>>>>>> But there are a few example libraries integrated there.
>>>>>>
>>>>>> For the tutorial, I use the innerwiki widget which makes it into a 
>>>>>> live playground even for the javascript. You can modify the javascript 
>>>>>> tiddlers in the outer wiki and see immediate updates in the innerwikis. 
>>>>>> In 
>>>>>> fact, I developed the entire tutorial inside the browser. If you learn 
>>>>>> well 
>>>>>> by making small modifications to already working code, then it should 
>>>>>> suit 
>>>>>> you well.
>>>>>>
>>>>>> On Sat, May 1, 2021 at 3:16 PM PMario  wrote:
>>>>>>
>>>>>>> On Saturday, May 1, 2021 at 7:31:35 PM UTC+2 Mark S. wrote:
>>>>>>>
>>>>>>> But if I want to use JS in TW, I'm reduced to maybe two paragraphs 
>>>>>>>> of explanatory material. The only documentation I ever found was by 
>>>>>>>> (?) 
>>>>>>>> Chris Hunt, which pages have now disappeared except on archive. The 
>>>>>>>> code 
>>>>>>>> examples no longer match existing core.
>>>>>>>>
>>>>>>>
>>>>>>> https://tiddlywiki.com/dev/ is still a very good overview about how 
>>>>>>> TW is built.
>>>>>>>  
>>>>>>>
>>>>>>>> After 5 years, it would really be great to have a bit of 
>>>>>>>> documentation for those of us who understand JS but need some 
>>>>>>>> hand-holding 
>>>>>>>> for the TW-JS gap.
>>>>>>>>
>>>>>>>
>>>>>>> There are some early TW hangouts, that discuss the internal 
>>>>>>> structure in detail. 
>>>>>>> Especially No 10 https://www.youtube.com/watch?v=o70TtNIe-L4 which 
>>>>>>> is 2h core design and code only. 
>>>>>>>
>>>>>>> have fun!
>>>>>>> mario
>>>>>>>
>>>>>>> -- 
>>>>>>> You received this message because you are subscribed to the Google 
>>>>>>> Groups "TiddlyWiki" group.
>>>>>>> To unsubscribe from this group and stop receiving emails from it, 
>>>>>>> send an email to tiddlywiki+...@googlegroups.com.
>>>>>>> To view this discussion on the web visit 
>>>>>>> https://groups.google.com/d/msgid/tiddlywiki/1bb2059c-4a77-430c-bdb9-e3b052e2b028n%40googlegroups.com
>>>>>>>  
>>>>>>> <https://groups.google.com/d/msgid/tiddlywiki/1bb2059c-4a77-430c-bdb9-e3b052e2b028n%40googlegroups.com?utm_medium=email_source=footer>
>>>>>>> .
>>>>>>>
>>>>>>

-- 
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/967bfa7f-af1b-4595-9d51-294dd36953f1n%40googlegroups.com.

[tw5] Re: Is there any way of using entire latex syntax inside TiddyWiki?

[Anjar]

Hi,

I don't think there is any way to render a full latex document by 
javascript (or is there? https://github.com/kisonecat/web2js); you may have 
to actually run latex somehow, for example through php: 
https://github.com/scarfboy/phplatex There is a js library for rendering 
tikz that may be useful https://github.com/kisonecat/tikzjax

If making charts is more important than using latex, you can have a look at 
this 
short thread 
 about 
Charts.css  (although pie charts are not currently 
supported)

Best,
Anders

mandag 3. mai 2021 kl. 00:25:51 UTC+2 skrev muynars...@gmail.com:

> I know that with the KaTex Plugin I can partially use LaTex syntax by 
> adding $$ at the beginning of the phrase like:
>
> $$\displaystyle f(x) = \int_{-\infty}^\infty\hat f(\xi)\,e^{2 \pi i \xi 
> x}\,d\xi$$
>
> However, I'd like to put the entire LaTex syntax on my tiddlers like the 
> following:
>
> ```latex
> % Pie chart
> % Author: Robert Vollmert
> \documentclass{article}
>
> \usepackage{calc}
> \usepackage{ifthen}
> \usepackage{tikz}
> \begin{document}
> \newcommand{\slice}[4]{
>   \pgfmathparse{0.5*#1+0.5*#2}
>   \let\midangle\pgfmathresult
>
>   % slice
>   \draw[thick,fill=black!10] (0,0) -- (#1:1) arc (#1:#2:1) -- cycle;
>
>   % outer label
>   \node[label=\midangle:#4] at (\midangle:1) {};
>
>   % inner label
>   \pgfmathparse{min((#2-#1-10)/110*(-0.3),0)}
>   \let\temp\pgfmathresult
>   \pgfmathparse{max(\temp,-0.5) + 0.8}
>   \let\innerpos\pgfmathresult
>   \node at (\midangle:\innerpos) {#3};
> }
>
> \begin{tikzpicture}[scale=3]
>
> \newcounter{a}
> \newcounter{b}
> \foreach \p/\t in {20/type A, 4/type B, 11/type C,
>49/type D, 16/other}
>   {
> \setcounter{a}{\value{b}}
> \addtocounter{b}{\p}
> \slice{\thea/100*360}
>   {\theb/100*360}
>   {\p\%}{\t}
>   }
>
> \end{tikzpicture}
>
> \end{document}
> ```
>
> This is a pie chart made in LaTex language. Is there any way of making 
> TiddlyWiki show the result of what I write like that? Just by using the 
> same syntax that I use for choosing syntax? Or is there an alternative way 
> to reach this same goal?
>

-- 
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/88eb98bd-270e-465a-ba4c-3fe0d89aeb63n%40googlegroups.com.

Re: [tw5] What plugins do you use to write?

[Anjar]

Hi Rika,

It may not be what you want, but a tiddlywiki more customized for longer 
texts can be found here: https://andjar.github.io/TW5-longtext/

You can choose to have two story rivers; writing to the left and previewing 
to the right, or you can have other stuff to the right (figures, 
references...). Or if you simply want to focus on the writing, you can 
close the toddlers to the right (and just click "Preview" to open the 
preview again). In addition, you have the plainrev plugin to take care of 
revisions (each time you click "SAVE")

Best,
Anders
fredag 23. april 2021 kl. 07:47:51 UTC+2 skrev bmad...@gmail.com:

> I made this plugin to be able to write long form in TW easily: 
> https://adithya-badidey.github.io/TW5-codemirror-plus/
> Along with this, I keep a small cheatsheet of shortcuts and formatting 
> symbols.
>
>
> On Thursday, April 22, 2021 at 10:38:08 AM UTC-6 Javier Rojas wrote:
>
>> On Thu, Apr 22, 2021 at 09:28:28AM -0700, Rika Sukenik wrote:
>> > I'm starting to write more long form in Tiddlywiki and I'd like an easy 
>> way 
>> > to bold, highlight, and add quotes. I'd love to hear what tool writers 
>> like 
>> > to use for writing. Thanks!
>>
>> I wanted to use a proper editor to edit the text in textareas, and was
>> really happy to find about
>> https://addons.mozilla.org/en-Us/firefox/addon/firenvim/ , which embeds
>> an nvim instance in any textarea in your browser, including of course
>> the edit field for tiddlers in tiddlywiki. Since nvim is quite
>> extensible, that fills my needs, although I admit vim/nvim is not
>> everybody's text editor of choice.
>>
>> Another approach is
>> https://addons.mozilla.org/en-Us/firefox/addon/ghosttext/ , which will
>> let you edit the contents of textareas in an external text editor of
>> your choice; I've also used that one, and I like it, but I prefer the
>> "embedded" approach of firenvim better.
>>
>>

-- 
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/a7fa568a-38ac-4aec-80d2-195d8189f61an%40googlegroups.com.

Re: [tw5] Looking for reading material: using javascript libraries in TiddlyWiki

[Anjar]

@cj.v did you see this thread 
https://groups.google.com/g/tiddlywiki/c/zcgAdcms0zM on php+sqlite? 
Requires a server though

Best,
Anders
lørdag 1. mai 2021 kl. 23:15:10 UTC+2 skrev brian@gmail.com:

> https://btheado.github.io/tw-widget-tutorial/ - this is another resource. 
> It is focused specifically on widgets and doesn't cover any of the other 
> integration points mentioned by Jeremy. When I wrote it, I ran out of steam 
> by the time I got to the third-party javascript integration and so there 
> isn't much there to help answer Charlie's original question. But there are 
> a few example libraries integrated there.
>
> For the tutorial, I use the innerwiki widget which makes it into a live 
> playground even for the javascript. You can modify the javascript tiddlers 
> in the outer wiki and see immediate updates in the innerwikis. In fact, I 
> developed the entire tutorial inside the browser. If you learn well by 
> making small modifications to already working code, then it should suit you 
> well.
>
> On Sat, May 1, 2021 at 3:16 PM PMario  wrote:
>
>> On Saturday, May 1, 2021 at 7:31:35 PM UTC+2 Mark S. wrote:
>>
>> But if I want to use JS in TW, I'm reduced to maybe two paragraphs of 
>>> explanatory material. The only documentation I ever found was by (?) Chris 
>>> Hunt, which pages have now disappeared except on archive. The code examples 
>>> no longer match existing core.
>>>
>>
>> https://tiddlywiki.com/dev/ is still a very good overview about how TW 
>> is built.
>>  
>>
>>> After 5 years, it would really be great to have a bit of documentation 
>>> for those of us who understand JS but need some hand-holding for the TW-JS 
>>> gap.
>>>
>>
>> There are some early TW hangouts, that discuss the internal structure in 
>> detail. 
>> Especially No 10 https://www.youtube.com/watch?v=o70TtNIe-L4 which is 2h 
>> core design and code only. 
>>
>> have fun!
>> mario
>>
>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "TiddlyWiki" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to tiddlywiki+...@googlegroups.com.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/tiddlywiki/1bb2059c-4a77-430c-bdb9-e3b052e2b028n%40googlegroups.com
>>  
>> 
>> .
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/938df43e-43a9-4fc9-9a93-c5a4c1fee52dn%40googlegroups.com.

[tw5] Re: Display parent tiddler's name alongside the child

[Anjar]

It's certainly possible. Are there some characteristics of the parents? Eg, 
do they all have titles starting with "Project" or are they tagged 
"Project"?

Best,
Anders

fredag 30. april 2021 kl. 10:07:15 UTC+2 skrev passingby:

> If I have Project tiddlers as parents and Tasks as children tagged by the 
> parent's name:
> Project-1
>   Task1
>   Task2
>   Task3
> Project-2
>  Task4
>  Task5
>
> How do I create a list like this:
>
> Task1 - Project1
> Task2 - Project1
> .
> Task4 - Project2
>
> In other words, when I iterate through the list of Tasks, I wish to 
> display the Project's name alongside. Is it possible? The only link between 
> the project and the task is that the task is tagged with the project's 
> name. So the logic generating the list has to look backwards somehow.
>

-- 
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/b9567e20-dc98-4697-ab37-f8d2b6ab08a4n%40googlegroups.com.

[tw5] Re: Modifying the body with ViewTemplate

[Anjar]

Maybe it is possible to have  <$details> in one tiddler and   in 
another tiddler and use list-before/after to manipulate the position of the 
two?

Best,
Anders

torsdag 29. april 2021 kl. 20:57:39 UTC+2 skrev Stobot:

> Hello all,
>
> I'm making sure there's not a better way to do this... I want to have 
> tiddlers with certain tags have their body wrapped with the <$details> 
> widget to keep the tiddlers short. 
>
> I know I can ADD things to the body by adding ViewTemplate tags as 
> outlined:
> https://groups.google.com/g/tiddlywiki/c/Jg-nmLk-yxs/m/yGricD4sBwAJ
>
> I know that I can HIDE things in the normal ViewTemplate by using CSS as 
> Eric showed:
> https://groups.google.com/g/tiddlywiki/c/K6uHR4XtJ0o/m/MNxAhRxQAgAJ
>
> But I can't see how that would help what I want to do. Instead I've just 
> hacked the actual $:/core/ui/ViewTemplate/body - which I know I don't want 
> to do...
>
> \define use-details()
> <$details summary="Notes">
> <$transclude>
>
> <$transclude tiddler="$:/language/MissingTiddler/Hint"/>
>
> 
> 
> \end
> \define no-details()
> <$transclude>
>
> <$transclude tiddler="$:/language/MissingTiddler/Hint"/>
>
> 
> \end
>
> <$reveal tag="div" class="tc-tiddler-body" type="nomatch" 
> stateTitle=<> text="hide" retain="yes" animate="yes">
>
> <$list filter="[all[current]!has[plugin-type]!field:hide-body[yes]]">
>
> <$list filter="[all[current]tag[Tasks]] [all[current]tag[Meetings]] 
> [all[current]tag[Projects]] [all[current]tag[Debriefs]]" 
> emptyMessage=<> variable="X">
> <>
> 
>
> 
>
> 
>

-- 
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/76fcd188-4af0-4bd8-9294-e8103ce30552n%40googlegroups.com.

Re: [tw5] Simple php/sqlite3 adaptor

[Anjar]

@Mohammad currently, I haven't copied that part of the tw-receiver script 
yet because having to edit a PHP is not very user friendly, it seems much 
better to have the password saved in the database so that you can actually 
set it and change it directly from the tiddlywiki. 

It's probably also better to collect everything in a single PHP-file that 
can both load and save the tiddlywiki; eg. if there is no sqlite files 
already existing -> download and load an empty tiddlywiki with a customized 
tw-receiver tiddler; if a single sqlite file exist, load it; if multiple 
sqlite files exist, show a menu.

Best,
Anders

tirsdag 27. april 2021 kl. 05:55:13 UTC+2 skrev Mohammad:

> Andres,
>  Does this need the same configuration as tw-receiver?
>  Is there any need to set a password also for sqlit3?
>
> I could not find the installation? 
>
>
> Best wishes
> Mohammad
>
>
> On Sun, Apr 25, 2021 at 6:54 PM Anjar  wrote:
>
>> Hi,
>>
>> I've started on a very simple php/sqlite3 backbone for tiddlywiki: 
>> https://github.com/andjar/TW-sqlite3/tree/main
>>
>> The main feature is perhaps that revisions are kept in the database 
>> (deleted tiddlers and edits). The tiddlers are saved to the sqlite file in 
>> three tables; tiddlers, tiddlertext, and fields. The tiddlers are assigned 
>> a UUID at first save. If the tiddler is deleted, the tiddler table will set 
>> the tiddler status to DELETED. If the text or any field is changed, the new 
>> value is added as a new row and the former version set to OUTDATED (or 
>> DELETED if the field is deleted)
>>
>> Best,
>> Anders
>>
>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "TiddlyWiki" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to tiddlywiki+...@googlegroups.com.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/tiddlywiki/bb2c6b4c-e3fb-4a81-8bea-cd429d7bd142n%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/tiddlywiki/bb2c6b4c-e3fb-4a81-8bea-cd429d7bd142n%40googlegroups.com?utm_medium=email_source=footer>
>> .
>>
>

-- 
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/6d4630b4-74ec-43fe-b1fa-0bd6040ebd48n%40googlegroups.com.

[tw5] Re: Simple php/sqlite3 adaptor

[Anjar]

Interesting thoughts, Tones! Authentication and security are important 
topics, but also daunting and a bit scary

I guess you can do many of the same things with node.js as with PHP, but it 
seems like an interesting space to explore; for example using imap 
functionality to sync to email, using get to build specific tiddlywikis 
depending on parameters or having the tiddlers as separate files similar to 
node.js

Best,
Anders

mandag 26. april 2021 kl. 03:01:53 UTC+2 skrev TW Tones:

> Anjar,
>
> This is something I have wanted for ages, I am keen to get in on my cpanel 
> hosting platform.
>
> One thought is to use a wordpress site and use this to control the 
> authentication etc... but write to the maria/sql db, perhaps adding user to 
> the database.
>
> Even if we only allowed one user at a time, wordpress could allow 
> checkout, from within its security model. Thus permitting serial (not 
> parallel) editing. It could be very easy to host tiddlywikis inside 
> wordpress/php sites. This would allow team collaboration and more on a 
> per-wiki basis without node.js solutions on the internet/intranet.
>
> Regards
> Tones
>
> On Monday, 26 April 2021 at 02:37:44 UTC+10 Anjar wrote:
>
>> I guess both local and remote will work, but I use apache2 locally on a 
>> Chromebook. I'm not competent enough to implement robust security features, 
>> so one should take care if used with a remote server:)
>>
>> Great, thanks!
>>
>> søndag 25. april 2021 kl. 16:34:33 UTC+2 skrev Mark S.:
>>
>>> That looks interesting. Is the server in your local browser or remote? 
>>>
>>> Added to tiddlywikilinks .
>>>
>>> On Sunday, April 25, 2021 at 7:24:26 AM UTC-7 Anjar wrote:
>>>
>>>> Hi,
>>>>
>>>> I've started on a very simple php/sqlite3 backbone for tiddlywiki: 
>>>> https://github.com/andjar/TW-sqlite3/tree/main
>>>>
>>>> The main feature is perhaps that revisions are kept in the database 
>>>> (deleted tiddlers and edits). The tiddlers are saved to the sqlite file in 
>>>> three tables; tiddlers, tiddlertext, and fields. The tiddlers are assigned 
>>>> a UUID at first save. If the tiddler is deleted, the tiddler table will 
>>>> set 
>>>> the tiddler status to DELETED. If the text or any field is changed, the 
>>>> new 
>>>> value is added as a new row and the former version set to OUTDATED (or 
>>>> DELETED if the field is deleted)
>>>>
>>>> Best,
>>>> Anders
>>>>
>>>

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/dafe427b-b81a-4519-be71-a55ee69da761n%40googlegroups.com.

Re: [tw5] Re: TW-Scripts A Community Resource For All Users

[Anjar]

This is beautiful, Mohammad, thank you for curating, refining, and 
documenting these scripts! A very powerful resource!

Best,
Anders
mandag 26. april 2021 kl. 17:12:08 UTC+2 skrev Mohammad:

> @Odin
> Thank you! To contribute: the simple way to open TW-Script, from the 
> sidebar click on create a new solutio and fill it the fields and email to 
> me!
> the hard way, add contents and send PRs.
>
> @Ray
> Thank you , Hope you find it helpful.
>
>
>
>
> Best wishes
> Mohammad
>
>
> On Mon, Apr 26, 2021 at 10:58 AM Odin  wrote:
>
>> Hi Mohammed,
>>
>> I wish I could star TW-Scripts  a million times, because I used it many 
>> times when I am trying to make something in TiddlyWiki. It is a very 
>> helpful resource for sure!
>>
>> I see you are looking for contributors. Can you give an example how 
>> people can contribute? Say, someone has written a solution/script, how 
>> would like them to add it to the wiki?
>>
>> Op maandag 26 april 2021 om 08:05:06 UTC+2 schreef Mohammad:
>>
>>> There is a new update out there!
>>>
>>> A new Explorer tab in the sidebar (the idea from Soren) has been added 
>>> to simply search in solutions, keywords and responders!
>>> Uglify plugin used to reduce the size considerably! Field search from 
>>> Mario used!
>>>
>>> It needs polishing and finishing the 90 remaining tasks ;-) but very 
>>> useful!
>>> The old version is there and can be downloaded as before 
>>> https://github.com/kookma/TW-Scripts/releases/tag/5.1.21
>>>
>>> Page: https://kookma.github.io/TW-Scripts/
>>> Github code: https://github.com/kookma/TW-Scripts
>>>
>>>
>>> Funny facts:
>>> 1. The plan was to have a weekly update (now it has got yearly update 
>>> with many unfinished tasks)
>>> 2. The plan was to have many contributors (it had one contributor, then 
>>> two and now has half ;-)
>>> 3. It was thought it will get millions of stars in GitHub ;-) :) :), it 
>>> has 22 stars (better than no star!!)
>>>
>>> Best wishes
>>> Mohammad
>>>
>>> On Monday, November 16, 2020 at 9:04:36 AM UTC+3:30 Mohammad wrote:
>>>
 TW-Scripts is one of the most comprehensive collection of solutions 
 including codes, macros, stylesheets, tips and tricks for Tiddlywiki 5.

 While it has not been updated for a while, but it is there with a lot 
 of answers to your questions specially for those who have recently started 
 Tiddlywiki.


 Page: https://kookma.github.io/TW-Scripts/
 Github code: https://github.com/kookma/TW-Scripts


 I hopefully update it as I get some free time!
 If you like it star it at https://github.com/kookma/TW-Scripts

 Best wishes
 Mohammad

>>> -- 
>>
> You received this message because you are subscribed to the Google Groups 
>> "TiddlyWiki" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to tiddlywiki+...@googlegroups.com.
>>
> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/tiddlywiki/800dab54-9af0-4964-a22b-2e0a86759c92n%40googlegroups.com
>>  
>> 
>> .
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/fea77e99-3c5b-4aa8-8503-3e7e82271fd4n%40googlegroups.com.

[tw5] Re: A tour through my Zettelkasten

[Anjar]

This is amazing, Soren, thank you for sharing both the technical part and 
your interesting thoughts! I thought your actual name was Søren Bjørnstad, 
so I'm happy to have been corrected:)

Best,
Anders
søndag 25. april 2021 kl. 19:08:19 UTC+2 skrev ludwa6:

> Thanks @Odin for the pointer, but as i am not writing any academic papers 
> these days, and am already struggling with conflicting plugins, i'll have 
> to take a pass on "BibTeX importer" for now.
>
> For example: Dave G's "BookToolsSidebarAddon" tags each new entry as 
> "source", while Soren's Zettlekasten tags each new entry as "Source"...  So 
> now, tags being case-sensitive,  i have two different sets of sources, each 
> of which is referenced by a different bibliography feature (NB: i suspected 
> this might be the case, which is why i haven't brought BookTools into 
> Zettelkasten; i tested this by importing a few tiddlers tagged by BookTools 
> in another instance).
>
> Based on Soren's video tutorial, it looks like that has all the 
> affordances i need for managing Sources & Bibliographies, if only i could 
> get the latest skeleton version to work like the demo, but -as mentioned 
> above- this is an issue for me ATM.
> On Sunday, April 25, 2021 at 1:17:06 PM UTC+1 Odin wrote:
>
>> @ludwa6
>>
>> The Refnotes  plugin is best used 
>> in combination with the BibTeX importer 
>>  from 
>> the official plugin library. With this plugin, you can import BibTeX files 
>> that contain the information to reference. Every imported BibTeX is 
>> transformed into a tiddler that will show up in the bibliographies list.
>>
>> Mohammed included the "Process new Bibtex entries" button to give all 
>> BibTex-tiddlers a tag, and to transform uppercases to lowercase. I think 
>> this is to make them all the same for easier reference and filtering.
>> Op zondag 25 april 2021 om 11:59:33 UTC+2 schreef ludwa6:
>>
>>> Have just discovered that the "Process new Bibtex entries" feature i 
>>> mentioned in last post is actually a function of the "Refnotes" plugin [1] 
>>> -nothing to do with your Zettelkasten version, @Soren. Sorry to have 
>>> confused the issue!
>>>
>>> Still: i would very much like to know how to use the Sources and 
>>> Bibliographies that you have built into your Zettelkasten @Soren, because 
>>> it appears quite elegant in its simplicity, per your demo.
>>>
>>> [1] Regarding Refnotes: i installed this plugin because i wanted the 
>>> footnotes feature -another example of elegant simplicity- which i want to 
>>> keep external links listed at bottom of tiddler, to avoid comingling them 
>>> with the internal links that typically pepper my body texts... But since i 
>>> don't use its other features, i got used to ignoring all that stuff nested 
>>> under "Bibliography" tab, until now.  I've got some housecleaning to do 
>>> here, obviously, once i get this workflow working! 
>>>
>>> On Saturday, April 24, 2021 at 6:25:28 PM UTC+1 ludwa6 wrote:
>>>
 Building my instance off this template, i'm now trying to develop a few 
 topical Bibliographies, each with a list of Sources, but it's not working 
 the way you show in the video, @Soren.

 When i click the "Sources" tool, it opens up a "New Source" tiddler 
 that contains only the following set of fields by default; the 
 "Bibliography" field that appears at top of the list in your video at 
 min.24'54" does not show up in mine -neither by default nor in the 
 dropdown 
 list of Field Names with which i might customise the tiddler (tho i 
 suppose 
 this should be done at the level of a View Template, right)?

 Also: the "Bibliography" tab in SideBar appears rather enigmatic for 
 the new user of this skeleton Zettelkasten, who has no Bibliography as of 
 yet, no bibtex entries to "Process," and no clue as to how to make one.  I 
 tried using the Search box in that widget, using pulldown param "Author" 
 to 
 search for the Source i created using the "New Source" tool, but it does 
 not appear... And neither does it appear in the table on SourceList 
 tiddler 
 tho -being created via New Source tool- it is of course properly tagged.

 Of course: i could implement the "Reading List" feature that i built in 
 another instance, following your earlier video tutorial 
  -which works 
 great- but i'm trying to use this Zettelkasten instance as-is, without 
 introducing any new code.  To that end: am i missing something, or is 
 something missing from the this version, i wonder?

 /walt

 On Saturday, April 17, 2021 at 6:06:29 PM UTC+1 Soren Bjornstad wrote:

> The public version lacks some functionality that is important for 
> editing and has a bunch of settings changed that are a bit of a pain to 
> 

[tw5] Re: Simple php/sqlite3 adaptor

[Anjar]

I guess both local and remote will work, but I use apache2 locally on a 
Chromebook. I'm not competent enough to implement robust security features, 
so one should take care if used with a remote server:)

Great, thanks!

søndag 25. april 2021 kl. 16:34:33 UTC+2 skrev Mark S.:

> That looks interesting. Is the server in your local browser or remote? 
>
> Added to tiddlywikilinks .
>
> On Sunday, April 25, 2021 at 7:24:26 AM UTC-7 Anjar wrote:
>
>> Hi,
>>
>> I've started on a very simple php/sqlite3 backbone for tiddlywiki: 
>> https://github.com/andjar/TW-sqlite3/tree/main
>>
>> The main feature is perhaps that revisions are kept in the database 
>> (deleted tiddlers and edits). The tiddlers are saved to the sqlite file in 
>> three tables; tiddlers, tiddlertext, and fields. The tiddlers are assigned 
>> a UUID at first save. If the tiddler is deleted, the tiddler table will set 
>> the tiddler status to DELETED. If the text or any field is changed, the new 
>> value is added as a new row and the former version set to OUTDATED (or 
>> DELETED if the field is deleted)
>>
>> Best,
>> Anders
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/2f140e26-6014-41e2-b035-cdc42639c8ebn%40googlegroups.com.

[tw5] Simple php/sqlite3 adaptor

[Anjar]

Hi,

I've started on a very simple php/sqlite3 backbone for 
tiddlywiki: https://github.com/andjar/TW-sqlite3/tree/main

The main feature is perhaps that revisions are kept in the database 
(deleted tiddlers and edits). The tiddlers are saved to the sqlite file in 
three tables; tiddlers, tiddlertext, and fields. The tiddlers are assigned 
a UUID at first save. If the tiddler is deleted, the tiddler table will set 
the tiddler status to DELETED. If the text or any field is changed, the new 
value is added as a new row and the former version set to OUTDATED (or 
DELETED if the field is deleted)

Best,
Anders

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/bb2c6b4c-e3fb-4a81-8bea-cd429d7bd142n%40googlegroups.com.

Re: [tw5] Re: Display tags in Tiddlers

[Anjar]

Hi,

Okay, I guess you have a list that produces that list of tiddlers, so just 
add <$list filter="[all[current]tags[]]"><> in 
that list, after the code for the drop-list

Best,
Anders

torsdag 22. april 2021 kl. 02:53:15 UTC+2 skrev mohamed...@hotmail.com:

> Thanks Anders 
>
> Close enough!
>
> so i have this tiddler that lists other tiddlers matching certain Tag 
> criteria , i also have some buttons and a drop list  , what i want is to 
> add next to the buttons and the drop list all tags associated with these 
> isted tiddlers 
>
> so this is how it looks like , i just need to add next to the droplists 
> all tags associated with the test 2 for example , and preferably in the 
> same pill format , hope this makes sense
> [image: Capture.PNG]
>
>
>
> [image: Capture2.PNG]
> On Wednesday, April 21, 2021 at 1:16:46 AM UTC+2 Anjar wrote:
>
>> Hi Mohamed,
>>
>> I'm not sure I fully understand your question, but here is an example 
>> that produce a table with tiddlers (by letter) to the left and the tags of 
>> the tiddler to the right; perhaps you wanted the opposite..?
>>
>> 
>> <$list filter="A B C D E F G H I J K L M N O P Q R S T U V W X Y Z">
>> 
>> <>
>> 
>> <$list filter="[ sortan[]prefix]">
>> 
>> <>
>> <$list 
>> filter="[titletags[]]"><>
>> 
>> 
>> 
>> 
>>
>> Best,
>> Anders
>>
>> mandag 19. april 2021 kl. 06:30:30 UTC+2 skrev mohamed.e...@vodafone.com:
>>
>>> Is it possible to display all associated tags with the listed tiddlers 
>>> next to them in the list?
>>>
>>> On Wednesday, April 7, 2021 at 2:29:41 PM UTC+2 Anjar wrote:
>>>
>>>> Hi,
>>>>
>>>> As you've discovered, seemingly simple problems can get wuite complex:) 
>>>> I agree with you that  is a nice solution, or you could wrap it in a 
>>>>  and have each element as a list item
>>>>
>>>> For now, I was unable to find a simply way to substring the titles; if 
>>>> there was, you could get the first letter of all titles, make them 
>>>> uppercase, remove duplicates and iterate through them with 
>>>> match:caseinsensitive or something. Maybe it'll be possible in the future!
>>>>
>>>> PS I forgot XYZ;)
>>>>
>>>>
>>>> Best,
>>>> Anders
>>>>
>>>> onsdag 7. april 2021 kl. 09:42:10 UTC+2 skrev jn.pierr...@gmail.com:
>>>>
>>>>>
>>>>> Nice solution. I tried it. It is case sensible. My code is not (it was 
>>>>> needed).
>>>>>
>>>>> I will try to merge your solution into mine to see what I could 
>>>>> achieve with two imbricated lists.
>>>>>
>>>>> Jean-Pierre
>>>>> Le mercredi 7 avril 2021 à 08:11:28 UTC+2, schlechter...@gmail.com a 
>>>>> écrit :
>>>>>
>>>>>> Thanks jn.pierr for your input - I'll check it later.
>>>>>> In the meantime I found a solution:
>>>>>>
>>>>>> 
>>>>>> <$list filter="A B C D E F G H I J K L M N O P R S T U V W Z">
>>>>>>
>>>>>> <><$list filter="[ 
>>>>>> sortan[]prefix]"> 
>>>>>>  <> <$view 
>>>>>> field="published" />  
>>>>>> **
>>>>>> 
>>>>>> 
>>>>>> 
>>>>>>
>>>>>> Stefan
>>>>>> jn.pierr...@gmail.com schrieb am Dienstag, 6. April 2021 um 21:11:10 
>>>>>> UTC+2:
>>>>>>
>>>>>>> As for listing letters for entries I have tghe following:
>>>>>>>
>>>>>>> \define all-initials()
>>>>>>> <$list filter="[tag[glossaire]]">
>>>>>>><$set name=1st value={{{ [all[current]split[]first[]] }}}>
>>>>>>>   <<1st>>
>>>>>>>
>>>>>>> 
>>>>>>> \end
>>>>>>>
>>>>>>> \define glossaryList()
>>>>>>> <$wikify name="all-letters" text=<>>
>>>>>>> <$list 
>>>>>>> filter="[uppercase[]split[É]join[E]split[]each:value[]!is[missing]]"
>>>>>>&

Re: [tw5] Re: Display tags in Tiddlers

[Anjar]

Hi Mohamed,

I'm not sure I fully understand your question, but here is an example that 
produce a table with tiddlers (by letter) to the left and the tags of the 
tiddler to the right; perhaps you wanted the opposite..?


<$list filter="A B C D E F G H I J K L M N O P Q R S T U V W X Y Z">

<>

<$list filter="[ sortan[]prefix]">

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





Best,
Anders

mandag 19. april 2021 kl. 06:30:30 UTC+2 skrev mohamed.e...@vodafone.com:

> Is it possible to display all associated tags with the listed tiddlers 
> next to them in the list?
>
> On Wednesday, April 7, 2021 at 2:29:41 PM UTC+2 Anjar wrote:
>
>> Hi,
>>
>> As you've discovered, seemingly simple problems can get wuite complex:) I 
>> agree with you that  is a nice solution, or you could wrap it in a 
>>  and have each element as a list item
>>
>> For now, I was unable to find a simply way to substring the titles; if 
>> there was, you could get the first letter of all titles, make them 
>> uppercase, remove duplicates and iterate through them with 
>> match:caseinsensitive or something. Maybe it'll be possible in the future!
>>
>> PS I forgot XYZ;)
>>
>>
>> Best,
>> Anders
>>
>> onsdag 7. april 2021 kl. 09:42:10 UTC+2 skrev jn.pierr...@gmail.com:
>>
>>>
>>> Nice solution. I tried it. It is case sensible. My code is not (it was 
>>> needed).
>>>
>>> I will try to merge your solution into mine to see what I could achieve 
>>> with two imbricated lists.
>>>
>>> Jean-Pierre
>>> Le mercredi 7 avril 2021 à 08:11:28 UTC+2, schlechter...@gmail.com a 
>>> écrit :
>>>
>>>> Thanks jn.pierr for your input - I'll check it later.
>>>> In the meantime I found a solution:
>>>>
>>>> 
>>>> <$list filter="A B C D E F G H I J K L M N O P R S T U V W Z">
>>>>
>>>> <><$list filter="[ 
>>>> sortan[]prefix]"> 
>>>>  <> <$view 
>>>> field="published" />  
>>>> **
>>>> 
>>>> 
>>>> 
>>>>
>>>> Stefan
>>>> jn.pierr...@gmail.com schrieb am Dienstag, 6. April 2021 um 21:11:10 
>>>> UTC+2:
>>>>
>>>>> As for listing letters for entries I have tghe following:
>>>>>
>>>>> \define all-initials()
>>>>> <$list filter="[tag[glossaire]]">
>>>>><$set name=1st value={{{ [all[current]split[]first[]] }}}>
>>>>>   <<1st>>
>>>>>
>>>>> 
>>>>> \end
>>>>>
>>>>> \define glossaryList()
>>>>> <$wikify name="all-letters" text=<>>
>>>>> <$list 
>>>>> filter="[uppercase[]split[É]join[E]split[]each:value[]!is[missing]]"
>>>>>  
>>>>> variable="letter">
>>>>>   <$link to=<>/>
>>>>> 
>>>>>
>>>>> <$list 
>>>>> filter="[uppercase[]split[É]join[E]split[]each:value[]!is[missing]]"
>>>>>  
>>>>> variable="letter">
>>>>> <$link to=<>/>
>>>>> <$set name="entries" filter="[addprefix[{{]addsuffix[}}]]">
>>>>> <>
>>>>> 
>>>>> 
>>>>> 
>>>>> \end
>>>>>
>>>>> added twist: make É and E the same entry. letters not used are not 
>>>>> seen. This example is with a "glossaire" tag, you would use "people" 
>>>>> instead or make it a variable of all-initials macro. the macro to be used 
>>>>> is glossaryList (no argument).
>>>>>
>>>>> You would have to adapt it to your needs and language perhaps.
>>>>>
>>>>> note: I have created letterr tiddlers "A"', "B"', "C" etc before hand. 
>>>>> I have not yet found out how to create them on purpose (and delete them 
>>>>> on 
>>>>> purpose too). But they all have the same content (a call to another 
>>>>> macro). 
>>>>> Some are not used, that's it.
>>>>> Le mardi 6 avril 2021 à 17:59:12 UTC+2, schlechter...@gmail.com a 
>>>>> écrit :
>>>>>
>>>>>> He

[tw5] Re: Forms for adding sources: Looking for advice on how to structure the data

[Anjar]

Hi Si, 

Thank you for clarification; however, I think the approach is still valid 
and demonstrated how it works, and with minor adjustments you can have 
field templates across source types;

(1) Make tiddlers with
- title starting with "$:/template",
- a field tiddlertype, for example tiddlertype: book,
- a field standardtext, for example standardtext: {{||$:/view/book}}, and
- required (empty) fields, for example booktitle and genre

(2) Make
- title starting with "$:/fieldtemplate", and
- text with how the field should be edited, eg.
-- A tiddler $:/fieldtemplate/booktitle with text: Title: <$edit-text 
field="booktitle" />
-- A tiddler $:/fieldtemplate/genre with text: Genre: <$select 
field="genre">HorrorPoetryScreenplay

(3) The add/edit tiddler can be
\define tiddlername() {{!!tiddlertype}}: <>
\define fieldtiddler() $:/fieldtemplate/$(currentFieldTiddler)$

<$list filter="[title[$:/temp/edit]!has[text]]">
<$list filter="[prefix[$:/template]]">
<$button>
<$wikify name=newtiddlername text=<> >
<$action-createtiddler $basetitle=<> 
text={{!!standardtext}} tiddlertype={{!!tiddlertype}} />
<$action-setfield $tiddler="$:/temp/edit" text=<> />

Create {{!!tiddlertype}} Tiddler



<$list filter="[title[$:/temp/edit]has[text]get[text]]" 
variable="edittiddler">
<$set name=tiddlertype filter="[titleget[tiddlertype]]">
<$list 
filter="[prefix[$:/template]tiddlertypefields:exclude[list 
title text tags created modified]]" variable="currentFieldTiddler">
<$tiddler tiddler=<> >
<$transclude tiddler=<> mode="block"/>



<$button>
<$action-deletetiddler $tiddler="$:/temp/edit"/>
Ok



Now, the form is populated with the corresponding fieldtemplates derived 
from the fields in the tiddler template. If the same field name is used in 
another tiddler template, the same field template is used

I provide a working example so that you, but most importantly others who 
perhaps is searching for similar solutions, can test and play around

Best,
Anders

fredag 16. april 2021 kl. 13:18:39 UTC+2 skrev si:

> @Anders The disadvantage of your approach is that you have to manually 
> create a form for every type of source, many of which will share fields 
> with one another. The reason I asked about the best way to associate 
> source-types with their required fields is to avoid this problem. If you 
> know which fields you want for a particular source-type, it should be 
> possible to automatically generate a form/table for adding new sources. 
> Just to be clear I wasn't asking for help on how to actually generate the 
> forms, just on the best way to associate source-types with their required 
> fields.
>
> @Sjaak Your point did occur to me, though I am not sure that I will 
> personally need any different data-entry-methods. I think it would be 
> possible to add the information about how the data for a field should be 
> entered within the tiddler that represents the field itself. For example 
> "Book" could in some way be associated with a tiddler representing the 
> field "format". Then the "format" tiddler could have its own field 
> containing something like 
> <$select>PaperbackHardback. 
> This should give you enough information to generate forms with custom 
> data-entry-methods, and apply them to any source-type without having to 
> re-write any code.
>
> On Thursday, 15 April 2021 at 23:40:59 UTC+1 Anjar wrote:
>
>> Hei Sjaak,
>>
>> I think a similar approach can be useful;
>>
>> (1) Make tiddlers with
>> - title starting with "$:/template",
>> - a field tiddlertype, for example tiddlertype: book, and
>> - a field standardtext, for example standardtext: {{||$:/view/book}}
>>
>> (2) This time, the template contains the form you want to use, for 
>> example, $:/template/book can contain
>> |Composer: |<$edit-text field="composer" /> |
>> |Title: |<$edit-text field="musictitle" /> |
>> |Genre: |<$select 
>> field="genre">HorrorPoetryScreenplay
>>  
>> |
>>
>> (3) Make a new tiddler with the content:
>> \define tiddlername() {{!!tiddlertype}}: <> >>
>>
>> <$list filter="[title[$:/temp/edit]!has[text]]">
>> <$list filter="[prefix[$:/template]]">
>> <$button>
>> <$wikify name=newtiddlername text=<> >
>> <$action-createtiddler $basetitle=<> 
>> tiddlertype={{!!tiddlertype}} text={{!!standardtext}} />
>> <$action-setfield $tiddler="$:/temp/edit"

[tw5] Re: Forms for adding sources: Looking for advice on how to structure the data

[Anjar]

Hei Sjaak,

I think a similar approach can be useful;

(1) Make tiddlers with
- title starting with "$:/template",
- a field tiddlertype, for example tiddlertype: book, and
- a field standardtext, for example standardtext: {{||$:/view/book}}

(2) This time, the template contains the form you want to use, for example, 
$:/template/book can contain
|Composer: |<$edit-text field="composer" /> |
|Title: |<$edit-text field="musictitle" /> |
|Genre: |<$select 
field="genre">HorrorPoetryScreenplay
 
|

(3) Make a new tiddler with the content:
\define tiddlername() {{!!tiddlertype}}: <>

<$list filter="[title[$:/temp/edit]!has[text]]">
<$list filter="[prefix[$:/template]]">
<$button>
<$wikify name=newtiddlername text=<> >
<$action-createtiddler $basetitle=<> 
tiddlertype={{!!tiddlertype}} text={{!!standardtext}} />
<$action-setfield $tiddler="$:/temp/edit" text=<> />

Create {{!!tiddlertype}} Tiddler



<$list filter="[title[$:/temp/edit]has[text]get[text]]">
<$tiddler tiddler=<> >
<$set name=edittitle 
filter="[prefix[$:/template]tiddlertype{!!tiddlertype}]">
<$transclude tiddler=<> mode="block"/>


<$button>
<$action-deletetiddler $tiddler="$:/temp/edit"/>
Ok



The latter tiddler will be your interface and new tiddlers are added in the 
background. They will have the standardtext as text, and you edit them 
directly from the interface tiddler using the form from the template tiddler

Best,
Anders

torsdag 15. april 2021 kl. 20:55:29 UTC+2 skrev sjaakad...@ziggo.nl:

> Hi Si,
>
> I have been thinking about an approach like yours but have not implemented 
> anything yet. It seems important to me that some fields may be of a 
> different kind than just text to be entered. Like choosing from a list of 
> options (with f.i. the select widget or radio widget). 
> My 2 cts.
>
> Greetings,
> Sjaak
>
> On Thursday, April 15, 2021 at 4:27:48 PM UTC+2 Anjar wrote:
>
>> Hi Si,
>>
>> Have a look at this post: 
>> https://groups.google.com/g/tiddlywiki/c/Q3vU6tnPffI/m/WNguU1p6BwAJ
>>
>> It's about using premade templates to create new tiddlers; you can of 
>> course add a form if you prefer that, instead of editing the new tiddler 
>> directly
>>
>> Best,
>> Anders
>>
>> torsdag 15. april 2021 kl. 16:06:52 UTC+2 skrev si:
>>
>>> @Springer Thanks for your reply.
>>>
>>> >>> The lovely thing is that you can filter on a tag (or any other 
>>> filter condition), to see a column for each of the fields you care about 
>>> for that tag (or filter condition), with a row for each tiddler that fits 
>>> the condition (and the ability to "clone" new rows into existence).
>>>
>>> How do you tell TiddlyWiki which fields to associate with each 
>>> reference-type? So for example you were to add a tiddler with the tag 
>>> "Book", you would want your table to give you the option to add fields like 
>>> "author", "title" etc. If you had a tiddler tagged "Movie" you might want 
>>> "director", "year" etc. My question is about the best way to associate a 
>>> particular type of source with the particular fields that it requires.
>>> On Wednesday, 14 April 2021 at 21:10:07 UTC+1 springer wrote:
>>>
>>>> Si, I highly recommend checking out all the RefNotes resources (active 
>>>> here recently, contributed by Mohammad). 
>>>>
>>>> My own approach is to use a DYNAMIC TABLE (Mohammad's Shiraz) for each 
>>>> reference-type. The lovely thing is that you can filter on a tag (or any 
>>>> other filter condition), to see a column for each of the fields you care 
>>>> about for that tag (or filter condition), with a row for each tiddler that 
>>>> fits the condition (and the ability to "clone" new rows into existence). 
>>>> Then you don't have a separate challenge of generating forms. Unless you 
>>>> really want to. ;)
>>>>
>>>> -Springer
>>>> On Wednesday, April 14, 2021 at 3:03:02 PM UTC-4 si wrote:
>>>>
>>>>> I use TiddlyWiki to manage sources (books, movies etc), and I want to 
>>>>> create an easy way to add tiddlers for individual sources.
>>>>>
>>>>> I have decided to add tiddlers that represent a "source-type", and 
>>>>> then use it to generate a form that allows me to enter metadata for a new 
>>>>> sou

[tw5] Re: Forms for adding sources: Looking for advice on how to structure the data

[Anjar]

Hi Si,

Have a look at this post: 
https://groups.google.com/g/tiddlywiki/c/Q3vU6tnPffI/m/WNguU1p6BwAJ

It's about using premade templates to create new tiddlers; you can of 
course add a form if you prefer that, instead of editing the new tiddler 
directly

Best,
Anders

torsdag 15. april 2021 kl. 16:06:52 UTC+2 skrev si:

> @Springer Thanks for your reply.
>
> >>> The lovely thing is that you can filter on a tag (or any other filter 
> condition), to see a column for each of the fields you care about for that 
> tag (or filter condition), with a row for each tiddler that fits the 
> condition (and the ability to "clone" new rows into existence).
>
> How do you tell TiddlyWiki which fields to associate with each 
> reference-type? So for example you were to add a tiddler with the tag 
> "Book", you would want your table to give you the option to add fields like 
> "author", "title" etc. If you had a tiddler tagged "Movie" you might want 
> "director", "year" etc. My question is about the best way to associate a 
> particular type of source with the particular fields that it requires.
> On Wednesday, 14 April 2021 at 21:10:07 UTC+1 springer wrote:
>
>> Si, I highly recommend checking out all the RefNotes resources (active 
>> here recently, contributed by Mohammad). 
>>
>> My own approach is to use a DYNAMIC TABLE (Mohammad's Shiraz) for each 
>> reference-type. The lovely thing is that you can filter on a tag (or any 
>> other filter condition), to see a column for each of the fields you care 
>> about for that tag (or filter condition), with a row for each tiddler that 
>> fits the condition (and the ability to "clone" new rows into existence). 
>> Then you don't have a separate challenge of generating forms. Unless you 
>> really want to. ;)
>>
>> -Springer
>> On Wednesday, April 14, 2021 at 3:03:02 PM UTC-4 si wrote:
>>
>>> I use TiddlyWiki to manage sources (books, movies etc), and I want to 
>>> create an easy way to add tiddlers for individual sources.
>>>
>>> I have decided to add tiddlers that represent a "source-type", and then 
>>> use it to generate a form that allows me to enter metadata for a new 
>>> source. For example I might have a source type "Book", which is used to 
>>> generate a form like this:
>>>
>>> Title: ...
>>> Author: ...
>>> Year: ...
>>>
>>> While "Movie" might have a form like this:
>>>
>>> Title: ...
>>> Director: ...
>>> Producer: ...
>>>
>>> Obviously I need to associate the required metadata-fields with their 
>>> source-type. I can think of two ways to do this:
>>>
>>>- Add a field to each tiddler type called "required-fields" which 
>>>lists the required metadata-fields.
>>>- Create separate tiddlers for each possible metadata-field, then 
>>>tag them with any source-type that requires them.
>>>
>>> It's not obvious to me that there is any functional difference between 
>>> these two options, but if I make a bad choice it will be difficult to 
>>> change down the line. So my question is: *Is there a reason that one of 
>>> these approaches is better than the other?*
>>>
>>> Thanks in advance for you help.
>>>
>>

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/b28d442d-c285-4fce-b8f8-5ad267d7b8e7n%40googlegroups.com.

[tw5] Re: Show user field on each Tiddler

[Anjar]

Hi,

To move it to the right, wrap it in a div (you may want to play with the 
padding)

<$list filter="[all[current]has:field[published]]">
{{!!published}}
 

And to bring it to the top, add a field called "list-before" and set the 
value to "$:/core/ui/ViewTemplate/body"

Best,
Anders
torsdag 8. april 2021 kl. 19:20:58 UTC+2 skrev schlechter...@gmail.com:

> Hello Anjar,
>
> thanks - this works :-)
> And how do I get the field to to right top?
> [image: Image.png]
>
> Thanks
> Stefan
>
> Anjar schrieb am Donnerstag, 8. April 2021 um 16:13:29 UTC+2:
>
>> Hi Stefan,
>>
>> Try removing the space inside the filter; i.e.
>>
>> <$list filter="[all[current]has:field[published]]">
>> {{!!published}}
>>  
>>
>> Best, 
>> Anders
>>
>> torsdag 8. april 2021 kl. 15:18:35 UTC+2 skrev schlechter...@gmail.com:
>>
>>> Hello Odin,
>>>
>>> Thanks for your tip - but it's not working.
>>> What I'm doing wrong?
>>> [image: published_nok.png]
>>> Thanks
>>> Stefan
>>> Odin schrieb am Mittwoch, 7. April 2021 um 21:43:27 UTC+2:
>>>
>>>> Hi!
>>>>
>>>> This can be achieved with the $:/tags/ViewTemplate tag. Make a tiddler 
>>>> tagged with '$:/tags/ViewTemplate'. This will make the contents of this 
>>>> tiddler appear on any tiddler in your wiki. Then copy the following inside 
>>>> the tiddler:
>>>>
>>>> <$list filter="[all[current]has:field[published] ]"> 
>>>> {{!!published}}
>>>>  
>>>>
>>>> The list acts like an if statement. If the current tiddler you are 
>>>> looking at has the field published, it will show the contents of the 
>>>> published field.
>>>> You can adjust the position of the contents with list-after and 
>>>> list-before fields.
>>>>
>>>> Hope that helps!
>>>> Op woensdag 7 april 2021 om 21:22:20 UTC+2 schreef 
>>>> schlechter...@gmail.com:
>>>>
>>>>>
>>>>> Hello,
>>>>>
>>>>> in every new Tiddler I add the field "published" - which will contain 
>>>>> an individual date:
>>>>> [image: published.png]
>>>>> (plublished date <> created date <> modified date)
>>>>>
>>>>> How can this be done, that on every Tiddler this field will be shown 
>>>>> under Toolbar like: [image: field_displayed_on_right_side.png]
>>>>> Thanks for feedback
>>>>>
>>>>> Stefan
>>>>>
>>>>>

-- 
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/ed6ce896-180b-4b33-b15c-7b10dc93c48cn%40googlegroups.com.

[tw5] Re: Show user field on each Tiddler

[Anjar]

Hi Stefan,

Try removing the space inside the filter; i.e.

<$list filter="[all[current]has:field[published]]">
{{!!published}}
 

Best, 
Anders

torsdag 8. april 2021 kl. 15:18:35 UTC+2 skrev schlechter...@gmail.com:

> Hello Odin,
>
> Thanks for your tip - but it's not working.
> What I'm doing wrong?
> [image: published_nok.png]
> Thanks
> Stefan
> Odin schrieb am Mittwoch, 7. April 2021 um 21:43:27 UTC+2:
>
>> Hi!
>>
>> This can be achieved with the $:/tags/ViewTemplate tag. Make a tiddler 
>> tagged with '$:/tags/ViewTemplate'. This will make the contents of this 
>> tiddler appear on any tiddler in your wiki. Then copy the following inside 
>> the tiddler:
>>
>> <$list filter="[all[current]has:field[published] ]"> 
>> {{!!published}}
>>  
>>
>> The list acts like an if statement. If the current tiddler you are 
>> looking at has the field published, it will show the contents of the 
>> published field.
>> You can adjust the position of the contents with list-after and 
>> list-before fields.
>>
>> Hope that helps!
>> Op woensdag 7 april 2021 om 21:22:20 UTC+2 schreef 
>> schlechter...@gmail.com:
>>
>>>
>>> Hello,
>>>
>>> in every new Tiddler I add the field "published" - which will contain an 
>>> individual date:
>>> [image: published.png]
>>> (plublished date <> created date <> modified date)
>>>
>>> How can this be done, that on every Tiddler this field will be shown 
>>> under Toolbar like: [image: field_displayed_on_right_side.png]
>>> Thanks for feedback
>>>
>>> Stefan
>>>
>>>

-- 
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/d846de12-7bf3-4680-875b-625b78efaf44n%40googlegroups.com.

Re: [tw5] Re: Display tags in Tiddlers

[Anjar]

Hi,

As you've discovered, seemingly simple problems can get wuite complex:) I 
agree with you that  is a nice solution, or you could wrap it in a 
 and have each element as a list item

For now, I was unable to find a simply way to substring the titles; if 
there was, you could get the first letter of all titles, make them 
uppercase, remove duplicates and iterate through them with 
match:caseinsensitive or something. Maybe it'll be possible in the future!

PS I forgot XYZ;)


Best,
Anders

onsdag 7. april 2021 kl. 09:42:10 UTC+2 skrev jn.pierr...@gmail.com:

>
> Nice solution. I tried it. It is case sensible. My code is not (it was 
> needed).
>
> I will try to merge your solution into mine to see what I could achieve 
> with two imbricated lists.
>
> Jean-Pierre
> Le mercredi 7 avril 2021 à 08:11:28 UTC+2, schlechter...@gmail.com a 
> écrit :
>
>> Thanks jn.pierr for your input - I'll check it later.
>> In the meantime I found a solution:
>>
>> 
>> <$list filter="A B C D E F G H I J K L M N O P R S T U V W Z">
>>
>> <><$list filter="[ 
>> sortan[]prefix]"> 
>>  <> <$view field="published" 
>> />  
>> **
>> 
>> 
>> 
>>
>> Stefan
>> jn.pierr...@gmail.com schrieb am Dienstag, 6. April 2021 um 21:11:10 
>> UTC+2:
>>
>>> As for listing letters for entries I have tghe following:
>>>
>>> \define all-initials()
>>> <$list filter="[tag[glossaire]]">
>>><$set name=1st value={{{ [all[current]split[]first[]] }}}>
>>>   <<1st>>
>>>
>>> 
>>> \end
>>>
>>> \define glossaryList()
>>> <$wikify name="all-letters" text=<>>
>>> <$list 
>>> filter="[uppercase[]split[É]join[E]split[]each:value[]!is[missing]]"
>>>  
>>> variable="letter">
>>>   <$link to=<>/>
>>> 
>>>
>>> <$list 
>>> filter="[uppercase[]split[É]join[E]split[]each:value[]!is[missing]]"
>>>  
>>> variable="letter">
>>> <$link to=<>/>
>>> <$set name="entries" filter="[addprefix[{{]addsuffix[}}]]">
>>> <>
>>> 
>>> 
>>> 
>>> \end
>>>
>>> added twist: make É and E the same entry. letters not used are not seen. 
>>> This example is with a "glossaire" tag, you would use "people" instead or 
>>> make it a variable of all-initials macro. the macro to be used 
>>> is glossaryList (no argument).
>>>
>>> You would have to adapt it to your needs and language perhaps.
>>>
>>> note: I have created letterr tiddlers "A"', "B"', "C" etc before hand. I 
>>> have not yet found out how to create them on purpose (and delete them on 
>>> purpose too). But they all have the same content (a call to another macro). 
>>> Some are not used, that's it.
>>> Le mardi 6 avril 2021 à 17:59:12 UTC+2, schlechter...@gmail.com a 
>>> écrit :
>>>
>>>> Hello Anjar,
>>>>
>>>> I've adapted your example to generate a list of all my Tiddlers + 
>>>> "published" field (= date):
>>>>
>>>> <$list 
>>>> filter="A B C D E F G H I J K L M N O P Q R S T U V 
>>>> W"><><$list filter="[ 
>>>> sortan[]prefix]">   
>>>> <> <$view field="published" />  
>>>>
>>>> Is there a way to get an output list with only one Tiddler-title per 
>>>> line?
>>>>
>>>> Thanks for feedback
>>>> Stefan
>>>>
>>>> Anjar schrieb am Montag, 5. April 2021 um 22:25:39 UTC+2:
>>>>
>>>>> Hi,
>>>>>
>>>>> Absolutely, here is a quick example:
>>>>>
>>>>> <$list 
>>>>> filter="A B C D E F G H I J K L M N O P Q R S T U V 
>>>>> W"><><$list 
>>>>> filter="[tag[People]sort[title]prefix]"> <> 
>>>>> 
>>>>>
>>>>> The div is just to get three columns. The first list loops through all 
>>>>> the letters and print each letter (<>) as header. For 
>>>>> each 
>>>>> letter, you use the same list as before, but add a filter to only keep 
>>>>> titles starting on (pr

Re: [tw5] Re: Display tags in Tiddlers

[Anjar]

Hi,

Absolutely, here is a quick example:

<$list 
filter="A B C D E F G H I J K L M N O P Q R S T U V 
W"><><$list 
filter="[tag[People]sort[title]prefix]"> <> 


The div is just to get three columns. The first list loops through all the 
letters and print each letter (<>) as header. For each 
letter, you use the same list as before, but add a filter to only keep 
titles starting on (prefix) the given letter (note that we have to use 
 inside filters)

Best,
Anders

mandag 5. april 2021 kl. 21:11:35 UTC+2 skrev isd196...@gmail.com:

> I have one final question, relating to the list function itself: Is it 
> possible to split the list alphabetically? So that all people whose names 
> begin with A, B, C etc, can be placed in separate lists, despite all being 
> in the same Tag group?
>
> Many thanks
>
> JK
>
> On Sun, 4 Apr 2021 at 19:08, Jax Kovak  wrote:
>
>> Eric, thanks so much! I wasn't sure about the short form of the list tag 
>> being used like that. Excellent! I have my list! Many thanks!
>>
>> Kind regards
>>
>> JK
>>
>>
>> On Sun, 4 Apr 2021 at 18:09, Eric Shulman  wrote:
>>
>>> On Sunday, April 4, 2021 at 9:46:38 AM UTC-7 isd196...@gmail.com wrote:
>>>
 Hey PMario, thanks for that, but I'm confused on how to use this. 
 Currently I can use 
 <$list filter="[tag[People]sort[title]]"/>
 to get a list of the People in the People Tag group, but I can't see 
 how to add the <> to it so that each item is listed as a Tag. 
 Could you clarify please?

>>>
>>> By ending the $list with /> you are using the "short-form" of the widget 
>>> which, by default, outputs the titles of the matching tiddlers, as links.  
>>> To display other output (e.g., the title as a tag pill) you need to use the 
>>> full <$list>... syntax, where the content is the <> macro, 
>>> like this:
>>>
>>> <$list filter="[tag[People]sort[title]]"> <> 
>>>
>>> Note that inside the body of the $list widget, the value of 
>>> currentTiddler is set to the title of each matching tiddler and the <> 
>>> macro defaults to showing the "currentTiddler" as a tag pill.
>>>
>>> enjoy,
>>> -e
>>>
>>> -- 
>>> 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/uAM0RDmpfrE/unsubscribe.
>>> To unsubscribe from this group and all its topics, send an email to 
>>> tiddlywiki+...@googlegroups.com.
>>> To view this discussion on the web visit 
>>> https://groups.google.com/d/msgid/tiddlywiki/0882f2c6-49b1-49a2-87c0-e6f953e3599fn%40googlegroups.com
>>>  
>>> 
>>> .
>>>
>>

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/84370da8-1ee0-4ad1-b818-5d08c981d733n%40googlegroups.com.

Re: [tw5] Re: [Help?] List the links and backlinks of the target tiddler in a sidebar tiddler

[Anjar]

Thanks David - you're right, it was made especially for you, inspired by 
the problem you presented and the  L+BL:)
onsdag 31. mars 2021 kl. 03:16:55 UTC+2 skrev David Gifford:

> Wow, I don't think I had seen Sidelinks, Anjar! It's not in the toolmap. I 
> will both play with this and add it to the toolmap. Thanks a bunch.
>
>
>
>
> On Tue, Mar 30, 2021 at 7:04 PM Anjar  wrote:
>
>> Hi David, 
>>
>> Very interesting! It somehow reminded me of sidenotes 
>> <https://groups.google.com/g/tiddlywiki/c/QNZLtqecbIU/m/T__843mBBAAJ>, 
>> which are easily combined with details: a simple demo: 
>> https://andjar.github.io/tiddlytext/sidelink.html Just a thought! The 
>> macro is simple:
>>
>> \define sidelink(trgt, lbl)
>> <$link to=$trgt$>$lbl$> ="sidenote">$lbl$<$transclude 
>> tiddler=$trgt$>
>> \end
>>
>> 
>> .comment:hover .sidenote {
>> background-color: yellow;
>> }
>>
>> .sidenote,
>> .marginnote {
>> float: right;
>> clear: right;
>> margin-right: -50%;
>> width: 40%;
>> margin-top: 0.3rem;
>> margin-bottom: 0;
>> line-height: 1.3;
>> vertical-align: baseline;
>> position: relative;
>> }
>> 
>>
>> Best,
>> Anders
>>
>> tirsdag 30. mars 2021 kl. 23:50:30 UTC+2 skrev David Gifford:
>>
>>> Hi all
>>>
>>> First, thanks to Saq and si for their ideas. (I saw Si's post too late, 
>>> but will play around with the hotzone idea later. Sounds like a good other 
>>> way of doing this)
>>>
>>> I got my links+backlinks set up to work as far as I need it to. Check it 
>>> out at:
>>>
>>> https://giffmex.org/experiments/l+bl.html
>>>
>>> If anyone would like to make this their own, adapt it, clean it up, 
>>> package it as a plugin, host it on GitHub, I would be most pleased. I got 
>>> it to work for me, and I wanted to share the idea rather than hoard it, but 
>>> I am not really excited about doing any remaining work on it or maintaining 
>>> it. 
>>>
>>>
>>> On Tuesday, March 30, 2021 at 12:28:24 PM UTC-6 David Gifford wrote:
>>>
>>>> Hi all
>>>>
>>>> Yet another crazy hair-brained idea of mine.
>>>>
>>>> Use case: you are reading a tiddler that has a lot of links to it. You 
>>>> want to see the context of a link, but you don't want to leave your place 
>>>> in the current tiddler. Also, you don't want modal popups.
>>>>
>>>> My idea: a tiddler tagged either $:/tags/SideBar (or 
>>>> $:/tags/SideBarSegment, if one is using the Customizer plugin) that lists 
>>>> the title and transcludes the text field of the hard links in, and the 
>>>> backlinks to, the "target tiddler" (i.e., the tiddler that shows up after 
>>>> the hashtab in the browser bar). That way you keep your tiddler open and 
>>>> in 
>>>> place, but can see a scrollable list in the sidebar with the title and 
>>>> text 
>>>> of all the links and backlinks.
>>>>
>>>> Here is an example of the look and functionality I am imagining: 
>>>> https://giffmex.org/experiments/l+bl.html
>>>>
>>>> At the very least, if someone could tell me how to parse "target 
>>>> tiddler" in a list filter, I could experiment on my own. 
>>>>
>>>> Alternate idea: A plugin that shows a small icon on hovering near a 
>>>> link in a tiddler, and when you click on the icon, the title and text of 
>>>> the linked tiddler appears in a sidebar tab or sidebar segment, and any 
>>>> tiddler that was there previoulsy in that sidebar viewing area is removed.
>>>>
>>>> Obviously either of these ideas would require a wide screen and a wide 
>>>> setup for the sidebar. But it would be a nice alternative to the 
>>>> two-column 
>>>> approach of the Stories plugin for Stroll. It would also mean that the 
>>>> viewtemplate approach for viewing backlinks (again, Stroll) would be less 
>>>> necessary. Side by side viewing of tiddlers is better than scrolling to 
>>>> the 
>>>> bottom of the target tiddler to see what the backlinks are.
>>>>
>>>> Thanks in advance for any feedback, help, snippets or links. Blessings!
>>>>
>>>>
>>>> -- 
>> 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/IVMObMnrk0s/unsubscribe.
>> To unsubscribe from this group and all its topics, send an email to 
>> tiddlywiki+...@googlegroups.com.
>>
> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/tiddlywiki/7d648deb-5ced-4adf-abde-20684ade8a1bn%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/tiddlywiki/7d648deb-5ced-4adf-abde-20684ade8a1bn%40googlegroups.com?utm_medium=email_source=footer>
>> .
>>
>

-- 
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/8c928d65-435a-4640-b474-03a705945cb2n%40googlegroups.com.

[tw5] Re: [Help?] List the links and backlinks of the target tiddler in a sidebar tiddler

[Anjar]

Hi David, 

Very interesting! It somehow reminded me of sidenotes 
, 
which are easily combined with details: a simple demo: 
https://andjar.github.io/tiddlytext/sidelink.html Just a thought! The macro 
is simple:

\define sidelink(trgt, lbl)
<$link to=$trgt$>$lbl$$lbl$<$transclude 
tiddler=$trgt$>
\end


.comment:hover .sidenote {
background-color: yellow;
}

.sidenote,
.marginnote {
float: right;
clear: right;
margin-right: -50%;
width: 40%;
margin-top: 0.3rem;
margin-bottom: 0;
line-height: 1.3;
vertical-align: baseline;
position: relative;
}


Best,
Anders

tirsdag 30. mars 2021 kl. 23:50:30 UTC+2 skrev David Gifford:

> Hi all
>
> First, thanks to Saq and si for their ideas. (I saw Si's post too late, 
> but will play around with the hotzone idea later. Sounds like a good other 
> way of doing this)
>
> I got my links+backlinks set up to work as far as I need it to. Check it 
> out at:
>
> https://giffmex.org/experiments/l+bl.html
>
> If anyone would like to make this their own, adapt it, clean it up, 
> package it as a plugin, host it on GitHub, I would be most pleased. I got 
> it to work for me, and I wanted to share the idea rather than hoard it, but 
> I am not really excited about doing any remaining work on it or maintaining 
> it. 
>
>
> On Tuesday, March 30, 2021 at 12:28:24 PM UTC-6 David Gifford wrote:
>
>> Hi all
>>
>> Yet another crazy hair-brained idea of mine.
>>
>> Use case: you are reading a tiddler that has a lot of links to it. You 
>> want to see the context of a link, but you don't want to leave your place 
>> in the current tiddler. Also, you don't want modal popups.
>>
>> My idea: a tiddler tagged either $:/tags/SideBar (or 
>> $:/tags/SideBarSegment, if one is using the Customizer plugin) that lists 
>> the title and transcludes the text field of the hard links in, and the 
>> backlinks to, the "target tiddler" (i.e., the tiddler that shows up after 
>> the hashtab in the browser bar). That way you keep your tiddler open and in 
>> place, but can see a scrollable list in the sidebar with the title and text 
>> of all the links and backlinks.
>>
>> Here is an example of the look and functionality I am imagining: 
>> https://giffmex.org/experiments/l+bl.html
>>
>> At the very least, if someone could tell me how to parse "target tiddler" 
>> in a list filter, I could experiment on my own. 
>>
>> Alternate idea: A plugin that shows a small icon on hovering near a link 
>> in a tiddler, and when you click on the icon, the title and text of the 
>> linked tiddler appears in a sidebar tab or sidebar segment, and any tiddler 
>> that was there previoulsy in that sidebar viewing area is removed.
>>
>> Obviously either of these ideas would require a wide screen and a wide 
>> setup for the sidebar. But it would be a nice alternative to the two-column 
>> approach of the Stories plugin for Stroll. It would also mean that the 
>> viewtemplate approach for viewing backlinks (again, Stroll) would be less 
>> necessary. Side by side viewing of tiddlers is better than scrolling to the 
>> bottom of the target tiddler to see what the backlinks are.
>>
>> Thanks in advance for any feedback, help, snippets or links. Blessings!
>>
>>
>>

-- 
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/7d648deb-5ced-4adf-abde-20684ade8a1bn%40googlegroups.com.

[tw5] Re: Creating custom Tiddler frameworks with fields

[Anjar]

Hi Florian,

I am not sure I understood exactly what you mean by defining categories via 
field. Is this what you imagine: A menu with various tiddler types, when 
clicking the button for "Quote", you create a quote tiddler with predefined 
fields and content?

Here is a suggestion: (1) Make template tiddlers with title starting with 
"$:/template", for example $:/template/quote. To these template tiddlers, 
(2) add fields contents, and (3) a field called tiddlertype with the name 
of the template, eg. tiddlertype: Quote

Now, (4) add this to a separte tiddler:

\define tiddlername() {{!!tiddlertype}}: <>

<$list filter="[prefix[$:/template]]">
<$button>
<$wikify name=newtiddlername text=<> >
<$action-createtiddler $basetitle=<> 
$template=<> />
<$action-navigate $to=<> />
<$action-sendmessage $message="tm-edit-tiddler" $param=<>/>

Create {{!!tiddlertype}} Tiddler



This code will generate a button for each of you templates. When you click 
the button, a new tiddler is created from the corresponding template and 
opened in edit mode. The new tiddler will get a title like "Quote: 
2021-03-30 14:30:00" and have the fields and contents of $:/template/quote

Best,
Anders

tirsdag 30. mars 2021 kl. 12:03:47 UTC+2 skrev flohit...@googlemail.com:

> yes i want to define several tiddler categories via fields (that i need to 
> define, too) and be able to create them out of a menu (like i can create 
> journals, but those are not defined by fields, right)
>
> Soren Bjornstad schrieb am Dienstag, 30. März 2021 um 00:36:16 UTC+2:
>
>> Hi Florian,
>>
>> I'm not sure I'm understanding what you're asking for – when you say you 
>> want to be able to "create custom tiddler templates defined by custom 
>> fields," do you mean you want TiddlyWiki templates to appear on tiddlers 
>> depending on the contents of a field? Or that you want an easier way to 
>> create tiddlers that start with particular fields? Do you need a custom 
>> interface for editing the different types of tiddlers?
>>
>> TiddlyWiki can do all of that for sure, but they're very different things!
>>
>> I recently did a screencast  
>> that 
>> might clarify some of this if you have an hour to burn.
>>
>> On Monday, March 29, 2021 at 4:24:57 PM UTC-5 flohit...@googlemail.com 
>> wrote:
>>
>>> *I don't really find how I could do that
>>>
>>> Florian Felix schrieb am Montag, 29. März 2021 um 23:24:20 UTC+2:
>>>
 Hey, 
 so I am thinking of several usecases where I would like to be able to 
 create custom Tiddler templates, defined by custom fields, but i don't 
 really find where i could do that? 

 For example I want a reference system that could be a bit more complex 
 with some interdependencies, and i think managing this via links and tags 
 would clutter the user interface and defining templates could help for 
 automating this. at least i 

 I see a quote, scan it via OCR or copy it , then I can open a new 
 "quote" tiddler (Or I just want to write a note) . It gives me the option 
 to insert an author/person, and a source. There are multiple options for 
 sources like website, book ...
 I have an author/person as well as a "sources" overview where I can add 
 details to sources or new ones. For author/person the quotes and notes 
 from 
 different sources are automatically transcluded. the sources overview is 
 structured into the different types. when I click on a singular source, 
 all 
 quotes and notes appear, and maybe a review (if its written). if its a 
 book, I can quickly add image, preferabbly link it to my inventaire.io 
 account. 
 If it's a webpage / file document I might want to link it with my 
 zotero library.  (these integratoins obviously are for the future, but 
 should be held in mind)

 How can I approach this? Is this even plausible way? :)



-- 
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/7714da9c-c628-4c43-b61f-5a61c2fec34en%40googlegroups.com.

Re: [tw5] MetaTiddly: Collaborative data charting for meta-analysis

[Anjar]

@Mohamad: I have entered them manually. To my knowledge, there is no 
standardized format for sharing research findings yet, except tables in PDF 
files. It is possible that csv import could be useful, but at the moment I 
think it is too complicated.

The most important features here I think are the nesting of tiddlers, a 
relatively straight-forward interface that doesn't require knowledge of 
tiddlywiki, and the possibility to add or remove properties. The next step, 
I think, will be better/custom json export

Best,
Anders

mandag 29. mars 2021 kl. 19:19:45 UTC+2 skrev Mohammad:

> Andres,
>  question: did you enter the data manually or you use any tool to do that?
>
> Best wishes
> Mohammad
>
>
> On Mon, Mar 29, 2021 at 6:21 PM Anjar  wrote:
>
>> Hi all,
>>
>> I just started on a small literature review and wanted a tool for 
>> charting findings of the studies. Further, I wanted others to be able to 
>> contribute with their findings, and github + tiddlywiki seemed perfect.
>>
>> The result: https://andjar.github.io/CyPreg/
>>
>> Measurements are nested within result, nested within population, nested 
>> within study. In addition, statistical tests can connect two or more 
>> measurements.
>>
>> I share this because I was unable to find better options for managing a 
>> collaborative database in github (utilizing pull and merge); tiddlywiki is 
>> perfect since it embeds presentation, storing and editing in a single file!
>>
>>
>> Hope you are all healthy and safe!
>>
>> Best,
>> Anders
>>
>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "TiddlyWiki" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to tiddlywiki+...@googlegroups.com.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/tiddlywiki/510d0bb0-892b-4fce-935c-b470c1af2d4bn%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/tiddlywiki/510d0bb0-892b-4fce-935c-b470c1af2d4bn%40googlegroups.com?utm_medium=email_source=footer>
>> .
>>
>

-- 
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/56b0cbcc-45a0-4822-a00d-e7d1533a322en%40googlegroups.com.

[tw5] MetaTiddly: Collaborative data charting for meta-analysis

[Anjar]

Hi all,

I just started on a small literature review and wanted a tool for charting 
findings of the studies. Further, I wanted others to be able to contribute 
with their findings, and github + tiddlywiki seemed perfect.

The result: https://andjar.github.io/CyPreg/

Measurements are nested within result, nested within population, nested 
within study. In addition, statistical tests can connect two or more 
measurements.

I share this because I was unable to find better options for managing a 
collaborative database in github (utilizing pull and merge); tiddlywiki is 
perfect since it embeds presentation, storing and editing in a single file!


Hope you are all healthy and safe!

Best,
Anders

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/510d0bb0-892b-4fce-935c-b470c1af2d4bn%40googlegroups.com.

[tw5] Charts.CSS

[Anjar]

Hi all,

I just discovered the CSS data visualization framework 
charts.css: https://chartscss.org/ In short, you just add CSS to a table 
and get a chart out of it. I know there already exist charting frameworks 
for tiddlywiki, but charts.css looks very nice and simple

A small working example:

```
\define barchart(vals)
<$list filter="[[$vals$]split[;]]" variable 
="var">
<$set filter="[split[]allbefore[,]join[]]" name="lab"><$set 
filter="[split[]allafter[,]join[]]" name="val">
 <>  >>


\end

\define st() --size:$(val)$;

https://cdn.jsdelivr.net/npm/charts.css/dist/charts.min.css;>


#bar-example-10 {
  height: 200px;
  max-width: 300px;
  margin: 0 auto;
}


<>
```

I hope you are all healthy and safe!

Best regards,
Anders

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/99cac81f-43b6-4f28-9bb6-7b61fe7d9153n%40googlegroups.com.

[tw5] Re: Tufte-like sidenotes: generate random ids

[Anjar]

Hi,

Good question! I think it would be difficult, but I am not very skilled in 
javascript, so it may be possible. An alternative is installing a plugin 
that let you double click the tiddler to edit it [1] and 
replace <$transclude tiddler=$txt$ > with $txt$ in the comment macro. Then 
you can simply write <> and avoid creating a new 
tiddler for each comment

[1] https://danielorodriguez.com/TW5-2click2edit/

Best,
Anders

fredag 29. januar 2021 kl. 21:56:58 UTC+1 skrev ceri...@gmail.com:

> Anders,
>
> Thanks for the quick reply.
>
> Is there a way to have a button that when pressed would enable the 
> sidenote to be created, at a desired place in the tiddler, without having to
> manually edit the tiddler?
>
> Thx
>
> On Friday, January 29, 2021 at 3:50:48 AM UTC-5 Anjar wrote:
>
>> Hi,
>>
>> Thanks for showing interest! In the demo, sidenotes are separate 
>> tiddlers, and to add them just use the macro <> "title_of_tiddler_to_show_on_the_side">>
>>
>> Best,
>> Anders
>>
>> fredag 29. januar 2021 kl. 02:09:20 UTC+1 skrev ceri...@gmail.com:
>>
>>> Anders,
>>>
>>> Thanks for the demo. From the demo I cannot see how to add a sidenote to 
>>> the tiddler.
>>> How would that be done?
>>>
>>> Thx
>>>
>>> On Tuesday, November 3, 2020 at 6:28:16 PM UTC-5 Anjar wrote:
>>>
>>>> Hi all!
>>>>
>>>> Some of you may be familiar with Edward Tufte (
>>>> https://edwardtufte.github.io/tufte-css/), and I think his sidenote 
>>>> approach can be useful in TiddlyWiki as well if one wants to add comments 
>>>> to the contents of a tiddler. I tried to make a simple macro which work 
>>>> fairly well, but to make a new number for each comment, I need to generate 
>>>> a unique ID for it. Is this possible or do I need another approach? For 
>>>> example, I added highlighting on hover which may reduce the need for 
>>>> unique 
>>>> identifiers., but it would still be nice for say printing. 
>>>>
>>>> \define comment(txt)
>>>> >>> class="margin-toggle sidenote-number">
>>>> 
>>>> >>> id="sn-demo"
>>>> class="margin-toggle"/>$txt$
>>>> \end
>>>>
>>>> 
>>>> .comment:hover .sidenote {
>>>> background-color: yellow;
>>>> }
>>>>
>>>> input.margin-toggle {
>>>> display: none;
>>>> }
>>>>
>>>> label.sidenote-number {
>>>> display: inline;
>>>> }
>>>>
>>>> label.margin-toggle:not(.sidenote-number) {
>>>> display: none;
>>>> }
>>>>
>>>> .sidenote,
>>>> .marginnote {
>>>> float: right;
>>>> clear: right;
>>>> margin-right: -60%;
>>>> width: 50%;
>>>> margin-top: 0.3rem;
>>>> margin-bottom: 0;
>>>> font-size: 1.1rem;
>>>> line-height: 1.3;
>>>> vertical-align: baseline;
>>>> position: relative;
>>>> }
>>>>
>>>> .sidenote-number {
>>>> counter-increment: sidenote-counter;
>>>> }
>>>>
>>>> .sidenote-number:after,
>>>> .sidenote:before {
>>>> font-family: et-book-roman-old-style;
>>>> position: relative;
>>>> vertical-align: baseline;
>>>> }
>>>>
>>>> .sidenote-number:after {
>>>> content: counter(sidenote-counter);
>>>> font-size: 1rem;
>>>> top: -0.5rem;
>>>> left: 0.1rem;
>>>> }
>>>>
>>>> .sidenote:before {
>>>> content: counter(sidenote-counter) " ";
>>>> font-size: 1rem;
>>>> top: -0.5rem;
>>>> }
>>>> 
>>>>
>>>> This<> is an<> 
>>>> example<>
>>>>
>>>>
>>>> Best,
>>>> Anders
>>>>
>>>

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/30d05285-99a2-44c7-ad0d-cb35127eccf2n%40googlegroups.com.

[tw5] Re: Tufte-like sidenotes: generate random ids

[Anjar]

Hi,

Thanks for showing interest! In the demo, sidenotes are separate tiddlers, 
and to add them just use the macro <>

Best,
Anders

fredag 29. januar 2021 kl. 02:09:20 UTC+1 skrev ceri...@gmail.com:

> Anders,
>
> Thanks for the demo. From the demo I cannot see how to add a sidenote to 
> the tiddler.
> How would that be done?
>
> Thx
>
> On Tuesday, November 3, 2020 at 6:28:16 PM UTC-5 Anjar wrote:
>
>> Hi all!
>>
>> Some of you may be familiar with Edward Tufte (
>> https://edwardtufte.github.io/tufte-css/), and I think his sidenote 
>> approach can be useful in TiddlyWiki as well if one wants to add comments 
>> to the contents of a tiddler. I tried to make a simple macro which work 
>> fairly well, but to make a new number for each comment, I need to generate 
>> a unique ID for it. Is this possible or do I need another approach? For 
>> example, I added highlighting on hover which may reduce the need for unique 
>> identifiers., but it would still be nice for say printing. 
>>
>> \define comment(txt)
>> > class="margin-toggle sidenote-number">
>> 
>> > id="sn-demo"
>> class="margin-toggle"/>$txt$
>> \end
>>
>> 
>> .comment:hover .sidenote {
>> background-color: yellow;
>> }
>>
>> input.margin-toggle {
>> display: none;
>> }
>>
>> label.sidenote-number {
>> display: inline;
>> }
>>
>> label.margin-toggle:not(.sidenote-number) {
>> display: none;
>> }
>>
>> .sidenote,
>> .marginnote {
>> float: right;
>> clear: right;
>> margin-right: -60%;
>> width: 50%;
>> margin-top: 0.3rem;
>> margin-bottom: 0;
>> font-size: 1.1rem;
>> line-height: 1.3;
>> vertical-align: baseline;
>> position: relative;
>> }
>>
>> .sidenote-number {
>> counter-increment: sidenote-counter;
>> }
>>
>> .sidenote-number:after,
>> .sidenote:before {
>> font-family: et-book-roman-old-style;
>> position: relative;
>> vertical-align: baseline;
>> }
>>
>> .sidenote-number:after {
>> content: counter(sidenote-counter);
>> font-size: 1rem;
>> top: -0.5rem;
>> left: 0.1rem;
>> }
>>
>> .sidenote:before {
>> content: counter(sidenote-counter) " ";
>> font-size: 1rem;
>> top: -0.5rem;
>> }
>> 
>>
>> This<> is an<> 
>> example<>
>>
>>
>> Best,
>> Anders
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/2e741e95-2c12-416b-922e-f65494a6dc8dn%40googlegroups.com.

[tw5] Re: TiddlyTime - a simple event logger

[Anjar]

Hi,

@Eric - thanks for the suggestions, it is very impressive, but I found it a 
bit too complex for this simple usecase. Sorry for the overlapping naming, 
maybe I'll change it to avoid confusion

@Mohammad - thanks for the feedback, I agree. I've added an "Advanced 
settings" section where you can invert the table shown below. At the 
moment, it doesn't affect the copied or downloaded output.

@Mark - thanks, it's so great that you keep that toolmap alive!

I've updated the wiki, but the download as csv will still give the wrong 
times. However, copy to clipboard is working better.

Best,
Anders

mandag 25. januar 2021 kl. 21:06:58 UTC+1 skrev Mark S.:

> Added to the tiddlywiki toolmap 
> <https://dynalist.io/d/zUP-nIWu2FFoXH-oM7L7d9DM#z=KD7kUsUIFmx3Us0teMLUILMI>
> .
>
> On Monday, January 25, 2021 at 4:50:11 AM UTC-8 Anjar wrote:
>
>> Hi,
>>
>> I was looking for a simple, crossplatform event logger for use in the 
>> field, but had some troubles finding a good solution, so I made a quick and 
>> simple implementation with tiddlywiki.
>>
>> However, when exporting to CSV, I was hoping to get the time stamp, but 
>> there is an offset (timezone related?). Can I change the template used for 
>> the datefields when exporting to CSV, or is the easiest to create a new 
>> field?
>>
>>
>> Demo: https://andjar.github.io/TiddlyTime/index.html
>> Source: https://github.com/andjar/TiddlyTime
>>
>>
>> Best,
>> Anders
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/9b07205c-a26f-46fc-8830-71a6d165daadn%40googlegroups.com.

[tw5] TiddlyTime - a simple event logger

[Anjar]

Hi,

I was looking for a simple, crossplatform event logger for use in the 
field, but had some troubles finding a good solution, so I made a quick and 
simple implementation with tiddlywiki.

However, when exporting to CSV, I was hoping to get the time stamp, but 
there is an offset (timezone related?). Can I change the template used for 
the datefields when exporting to CSV, or is the easiest to create a new 
field?


Demo: https://andjar.github.io/TiddlyTime/index.html
Source: https://github.com/andjar/TiddlyTime


Best,
Anders

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/67528751-0757-4376-a6c0-20feb440459en%40googlegroups.com.

[tw5] Re: TiddlyMenu

[Anjar]

Hi,

Thanks for the feedback! I have added the doubleclick2edit plugin as 
suggested by TiddlyTweeter and added a checkbox in the sidebar ("Show 
shortcuts") and if you check it, you will get an add tiddler button fixed 
in the lower right corner!

Best,
Anders

onsdag 20. januar 2021 kl. 15:57:06 UTC+1 skrev j.te...@gmail.com:

> Hi Anjar,
>
> Real cool stuff...definitely will come in handy for one of my wikis.
> A small suggestion...it would be cool if one would be able to add
> tiddlers on the fly via button. Overall nice!
>
> Best regards,
> Julio
>
> On Wednesday, January 20, 2021 at 9:35:48 AM UTC-5 TiddlyTweeter wrote:
>
>> IF you want to maintain minimalism yet make them editable you might look 
>> to Danielo's "Double Click to Edit" plugin.
>>
>>
>> https://danielorodriguez.com/TW5-2click2edit/#%24%3A%2Fplugins%2Fdanielo515%2F2click2edit
>>
>> Best wishes
>> TT
>>
>> On Tuesday, 19 January 2021 at 15:32:09 UTC+1 Anjar wrote:
>>
>>> Hi all,
>>>
>>> I just made a minimalistic setup for a "menu landing page"; home is just 
>>> a grid with menu items that takes you to a full width tiddler. The menu 
>>> items are simply tiddlers tagged with "Menu" where the title becomes the 
>>> link text
>>>
>>> Demo: http://andjar.github.io/TiddlyMenu
>>> Code: https://github.com/andjar/TiddlyMenu
>>>
>>>
>>> Best,
>>> Anders
>>>
>>

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/09d8b127-1efe-415f-89d1-7c1047119538n%40googlegroups.com.

Re: [tw5] TiddlyMenu

[Anjar]

Hi and thanks:)

At the moment,  tiddlers can be added from the sidebar (tag it with Menu to 
make it an element on the front page), and the tiddler manager has a 
shortcut there and can be used to edit the tiddlers. I know it's a bit 
unpractical but it makes the viewing easy - so maybe I'll add an 
alternative page layout for the "administrator" to use

Best,
Anders

onsdag 20. januar 2021 kl. 09:57:51 UTC+1 skrev Mohammad:

> Hi Andres,
>  That's lovely. How do you add new items? It seems the edit button is 
> hidden.
>
>
> Best wishes
> Mohammad
>
>
> On Tue, Jan 19, 2021 at 6:02 PM Anjar  wrote:
>
>> Hi all,
>>
>> I just made a minimalistic setup for a "menu landing page"; home is just 
>> a grid with menu items that takes you to a full width tiddler. The menu 
>> items are simply tiddlers tagged with "Menu" where the title becomes the 
>> link text
>>
>> Demo: http://andjar.github.io/TiddlyMenu
>> Code: https://github.com/andjar/TiddlyMenu
>>
>>
>> Best,
>> Anders
>>
>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "TiddlyWiki" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to tiddlywiki+...@googlegroups.com.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/tiddlywiki/c90d9e19-096c-43bd-950e-b2c2ca134080n%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/tiddlywiki/c90d9e19-096c-43bd-950e-b2c2ca134080n%40googlegroups.com?utm_medium=email_source=footer>
>> .
>>
>

-- 
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/84fd86a0-5af9-48c5-afbb-fdc5d4f8edc0n%40googlegroups.com.

[tw5] TiddlyMenu

[Anjar]

Hi all,

I just made a minimalistic setup for a "menu landing page"; home is just a 
grid with menu items that takes you to a full width tiddler. The menu items 
are simply tiddlers tagged with "Menu" where the title becomes the link text

Demo: http://andjar.github.io/TiddlyMenu
Code: https://github.com/andjar/TiddlyMenu


Best,
Anders

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/c90d9e19-096c-43bd-950e-b2c2ca134080n%40googlegroups.com.

[tw5] Re: Streams 0.2 preview

[Anjar]

Thank you, Saq, this is amazing! If you feel for it: Hacker News 
(https://news.ycombinator.com/) is a great place to get constructive 
feedback (they have a "Show HN" prefix) - and it would be a nice place to 
promote TiddlyWiki more too!

Best,
Anders

lørdag 9. januar 2021 kl. 23:07:10 UTC+1 skrev si:

> This is great Saq. I've been playing with it mostly on Tiddloid (on a 
> cheap Samsung). I'm amazed by how many great improvements you have made, 
> and now super-excited for the next release. Streams is looking better than 
> most 'conventional' apps.
>
> I have included several quibbles below, but only because it's hopefully 
> more helpful to you than just saying that everything is great. My overall 
> response, however, is overwhelmingly positive.
>
> Here are my thoughts (mostly relating to the mobile UX):
>
>- Overall the mobile experience is way smoother. Drag and drop didn't 
>work for me before, now it works reliably. The area to tap in order to 
> drag 
>and drop seems suitably large - I'm not finding that I have to re-tap to 
>find the right spot.
>- It feels like I have to hold down a little longer that I would 
>expect before the node becomes draggable. I know you wouldn't want it to 
>happen too quickly so as not to interfere with scrolling, but to me it 
> just 
>feels too long. It's hard to say for sure without trying it for a longer 
>period, but I think it impacts the UX enough that it would probably 
> prevent 
>me from bothering to use drag at all on mobile.
>- It's hard to judge, but double tapping to enter edit-mode seems to 
>have less of a delay than in the current stable version. It's still got a 
>delay, but I guess this could have something to do with my cheap phone. 
>- I have found that whenever I double tap to close edit mode on mobile 
>I end up highlighting some text. In most cases this doesn't actually 
> affect 
>the function, but I do find it mildly stressful.
>- Double tapping to the left of the text to works well, though 
>currently I don't instinctively do this. It also feels like it would be 
>more natural as a single rather than a double tap.
>- Swiping to open the context menu is super-useful. Currently it seems 
>that if a context menu is already open, switching to a context menu on a 
>different node requires two steps: tapping to close the menu, then swiping 
>to open a new one. I think it would be more natural if swiping on a 
>separate node did both of these things at once.
>- I tried the swipe-to-indent setting and found that it worked well, 
>and the lack of visual feedback/ability to undo doesn't strike me as a 
>massive problem. However I would probably not use this feature personally 
>as I feel that the context menu option is more useful.
>- The reduced indent level looks nicer in my opinion. The streams look 
>more like they are part of the tiddler, if that makes any sense.
>- The new control panel is super-sexy. I could easily tell what all 
>the settings did.
>- One thing that bothered me about the current release is that I would 
>occasionally create new nodes from tiddlers that already had titles like 
>"tiddler/timestamp" and end up with lots of tiddlers called 
>"tiddler/timestamp/timestamp/timestamp" etc. With the new control panel I 
>was able to change the title template to my own custom macro that ignores 
>any already existing timestamps when generating new titles. I wonder if 
>this should be the default behaviour? Here is the macro that I used:
>   - \define new-streams-title()
>   <$vars timestamp=<> >
>   <$list filter="[!regexp[^.*/\d{17}$]]">
>   {{{ [addsuffix[/]addsuffix] }}}
>   
>   <$list filter="[regexp[^.*/\d{17}$]]">
>   {{{ [splitbefore[/]addsuffix] }}}
>   
>   
>   \end
>- The last point doesn't relate directly to the new features, but I 
>might as well mention it here. I frequently find myself opening a tiddler 
>and seeing that I have a bunch of nodes left in edit mode, which I have to 
>toggle one at a time. It would be nice I think to have a way either for 
>nodes to be set to read-mode automatically (maybe triggered by opening the 
>tiddler for a node, or closing the streams tiddler), or an option to just 
>set all nodes to read-only in batch.
>
> Ok so now I realise that I have written a whole essay. Sorry. Thanks again 
> for Streams, it's a super-plugin.
> On Friday, 8 January 2021 at 18:14:53 UTC saq.i...@gmail.com wrote:
>
>> This is a preview of an experimental branch of Streams intended to 
>> explore optimizations and new ideas. Not all of these changes will make it 
>> to the final released version, depending on user feedback.
>>
>> Specifically, I am interested in feedback from regular users of Streams 
>> who can compare these new changes to the stable released version.
>> 

[tw5] Re: RemNote

[Anjar]

Thanks for the heads up! A plugin for PDF annotations sounds useful for 
TiddlyWiki too - say a tiddler per comment - it doesn't seem to complicated 
either, see https://github.com/rvasoya/PDFAnnotation


Best,
Anders

lørdag 9. januar 2021 kl. 18:16:48 UTC+1 skrev arunnn...@gmail.com:

> Remnote is getting launched in product hunt on January 13th. Remnote 
> launched a pro version two days back with subscription plans. Highlight of 
> the latest update is inbuilt pdf annotation. For details check out this 
> page.
> Remnote update page 
> On Friday, November 6, 2020 at 10:35:35 AM UTC+5:30 Mohammad wrote:
>
>> Is RemNote inspired by Tiddlywiki or is a Tiddlywiki customized edition?
>>
>> See
>>
>> https://www.remnote.io/document/sfmopXEDNmphepu48
>> https://www.remnote.io/
>>
>>
>> As Kebi stated, his TiddlyResearch is inspired from RemNote. The 
>> similarity is amazing
>>
>> --Mohammad
>>
>

-- 
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/bf654217-e1a9-4123-8319-ca3f52fe6daan%40googlegroups.com.

[tw5] Re: Minimalistic "single tiddler view" for short texts etc

[Anjar]

Hi Mohammad,

Thank you for noticing, it should be available again now! For 
backup: https://andjar.github.io/tiddlytext/ 
or https://github.com/andjar/tiddlytext

Anders

torsdag 10. desember 2020 kl. 07:07:53 UTC+1 skrev Mohammad:

> Hi Anjar,
>  I cannot download the demo! Would you mind to take a look
>
> --Mohammad
>
> On Saturday, May 2, 2020 at 9:26:13 PM UTC+4:30 Anjar wrote:
>
>> Hi @Petruschka,
>>
>> The easiest way to use it, is to download the demo 
>> <https://ewy.no/tiddlytext.html>, open the sidebar (from the home 
>> tiddler) and delete the two example collections by hitting the Xs. Maybe 
>> it'll become a plugin one day if there is time:)
>>
>

-- 
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/42ec151d-6f6d-4ad8-b75e-3b04b133096cn%40googlegroups.com.

[tw5] Re: Smart quotes in TiddlyWiki

[Anjar]

Hi again Soren,

It may not be the most elegant solution, but import the two attached 
tiddlers (you may have to remove the .txt ending) to your tiddlywiki and 
reload it. Then all you "test" will be replaced by  “test” (the difference 
is hard to spot with the default font though). Actually, you can choose any 
character or string to replace the quotes with in $:/me/smartquote.css. 
However, we add them by using ::before and ::after in css, so you will not 
be able to select or copy the quotes themselves..

Best,
Anders

mandag 7. desember 2020 kl. 22:19:29 UTC+1 skrev Anjar:

> Hi,
>
> I think you can use the parser to create your own shorthand notation, eg. 
> to render ;;test;; as “curly quotes”, or you can probably also use a parser 
> rule to replace straight quotes as well (altough I don't know if you risk 
> quotes within code being replaced as well). See 
> https://groups.google.com/g/tiddlywiki/c/IN46zvv4nCw
>
> You can probably 
> use $:/core/modules/parsers/wikiparser/rules/emphasis/superscript.js for 
> inspiration (to "encapsule" something):
>
> exports.init = function(parser) {
> this.parser = parser;
> // Regexp to match
> this.matchRegExp = /\^\^/mg;
> };
>
> exports.parse = function() {
> // Move past the match
> this.parser.pos = this.matchRegExp.lastIndex;
>
> // Parse the run including the terminator
> var tree = this.parser.parseInlineRun(/\^\^/mg,{eatTerminator: true});
>
> // Return the classed span
> return [{
> type: "element",
> tag: "sup",
> children: tree
> }];
> };
>
> in combination with $:/core/modules/parsers/wikiparser/rules/dash.js (to 
> replace the shorthand/straight quotes with a HTML entity):
>
> exports.init = function(parser) {
> this.parser = parser;
> // Regexp to match
> this.matchRegExp = /-{2,3}(?!-)/mg;
> };
>
> exports.parse = function() {
> // Move past the match
> this.parser.pos = this.matchRegExp.lastIndex;
> var dash = this.match[0].length === 2 ? "" : "";
> return [{
> type: "entity",
> entity: dash
> }];
> };
>
>
> Best,
> Anders
> mandag 7. desember 2020 kl. 20:50:18 UTC+1 skrev coda coder:
>
>> FWIW, I use AutoHotKey. I've wired up Ctrl+' and Ctrl+Shift+' to issue 
>> curlies “like this”
>>
>> ;Pretty quotes
>> ^':: SendInput “
>> ^+':: SendInput ”
>>
>> On a US DT keyboard, at least, they're conveniently located. On UK 
>> keyboards I know they're not so convenient. Android... no idea.
>>
>> On Sunday, December 6, 2020 at 8:01:51 PM UTC-6 Soren Bjornstad wrote:
>>
>>> I'm starting to get sick of using a four-button compose-key sequence to 
>>> get “curly quotes” in my tiddlers. Has anyone thought about or tried 
>>> integrating a library like smartquotes.js 
>>> <https://github.com/kellym/smartquotes.js> into TiddlyWiki to 
>>> automatically curl "straight quotes" in output? TiddlyWiki automatically 
>>> upgrades hyphens to dashes, and if anything straight quotes are an even 
>>> more egregious typographical mistake, so it feels like something TiddlyWiki 
>>> should handle for me.
>>>
>>> I don't believe CodeMirror has any options related to upgrading the 
>>> characters on insertion, but I do use CodeMirror so that would be an 
>>> acceptable way 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 view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/4fc29de8-3aa6-4b2d-96bb-fd5c7f8a8c92n%40googlegroups.com.
created: 20201209220621567
modified: 20201209221722731
module-type: wikirule
tags: 
title: $:/core/modules/parsers/wikiparser/rules/emphasis/quote.js
type: application/javascript

/*\
title: $:/core/modules/parsers/wikiparser/rules/emphasis/quote.js
type: application/javascript
module-type: wikirule

\*/
(function(){

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

exports.name = "smartquote";
exports.types = {inline: true};

exports.init = function(parser) {
this.parser = parser;
// Regexp to match
this.matchRegExp = /\"/mg;
};

exports.parse = function() {
// Move past the match
this.parser.pos = this.matchRegExp.lastIndex;

// Parse the run including the terminator
var tree = this.parser.parseInlineRun(/\"/mg,{eatTerminator: true});

// Return the classed span
return [{
type: "element",
tag: "sq",
children: tree
}];
};

})();created: 20201209221723715
modified: 2020120911930
tags: $:/tags/Stylesheet
title: $:/me/smartquote.css
type: text/css

sq::before { 
  content: "“";
}

sq::after { 
  content: "”";
}

[tw5] Re: Smart quotes in TiddlyWiki

[Anjar]

Hi,

I think you can use the parser to create your own shorthand notation, eg. 
to render ;;test;; as “curly quotes”, or you can probably also use a parser 
rule to replace straight quotes as well (altough I don't know if you risk 
quotes within code being replaced as well). See 
https://groups.google.com/g/tiddlywiki/c/IN46zvv4nCw

You can probably 
use $:/core/modules/parsers/wikiparser/rules/emphasis/superscript.js for 
inspiration (to "encapsule" something):

exports.init = function(parser) {
this.parser = parser;
// Regexp to match
this.matchRegExp = /\^\^/mg;
};

exports.parse = function() {
// Move past the match
this.parser.pos = this.matchRegExp.lastIndex;

// Parse the run including the terminator
var tree = this.parser.parseInlineRun(/\^\^/mg,{eatTerminator: true});

// Return the classed span
return [{
type: "element",
tag: "sup",
children: tree
}];
};

in combination with $:/core/modules/parsers/wikiparser/rules/dash.js (to 
replace the shorthand/straight quotes with a HTML entity):

exports.init = function(parser) {
this.parser = parser;
// Regexp to match
this.matchRegExp = /-{2,3}(?!-)/mg;
};

exports.parse = function() {
// Move past the match
this.parser.pos = this.matchRegExp.lastIndex;
var dash = this.match[0].length === 2 ? "" : "";
return [{
type: "entity",
entity: dash
}];
};


Best,
Anders
mandag 7. desember 2020 kl. 20:50:18 UTC+1 skrev coda coder:

> FWIW, I use AutoHotKey. I've wired up Ctrl+' and Ctrl+Shift+' to issue 
> curlies “like this”
>
> ;Pretty quotes
> ^':: SendInput “
> ^+':: SendInput ”
>
> On a US DT keyboard, at least, they're conveniently located. On UK 
> keyboards I know they're not so convenient. Android... no idea.
>
> On Sunday, December 6, 2020 at 8:01:51 PM UTC-6 Soren Bjornstad wrote:
>
>> I'm starting to get sick of using a four-button compose-key sequence to 
>> get “curly quotes” in my tiddlers. Has anyone thought about or tried 
>> integrating a library like smartquotes.js 
>>  into TiddlyWiki to 
>> automatically curl "straight quotes" in output? TiddlyWiki automatically 
>> upgrades hyphens to dashes, and if anything straight quotes are an even 
>> more egregious typographical mistake, so it feels like something TiddlyWiki 
>> should handle for me.
>>
>> I don't believe CodeMirror has any options related to upgrading the 
>> characters on insertion, but I do use CodeMirror so that would be an 
>> acceptable way 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 view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/ba25748e-e6e8-4c35-a4a6-487b91036dcbn%40googlegroups.com.

[tw5] Parsing arrows from shorthand

[Anjar]

Hi all,

To improve my workflow a bit, I used the the dash-parser as template to 
replace ->, -^, -. and -< with →, ↑,  ↓ and ←, respectively. Just sharing 
in case it could be useful for others!

Best,
Anders

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/649528a9-1354-4a54-9a57-2f127bd5019cn%40googlegroups.com.
created: 20201207140832569
modified: 20201207143705685
module-type: wikirule
tags: 
title: $:/core/modules/parsers/wikiparser/rules/arrows.js
type: application/javascript

/*\
title: $:/core/modules/parsers/wikiparser/rules/arrows.js
type: application/javascript
module-type: wikirule

Wiki text inline rule for arrows. For example:

```
-^
-.
->
-<
```

\*/
(function(){

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

exports.name = "arrow";
exports.types = {inline: true};

exports.init = function(parser) {
this.parser = parser;
// Regexp to match
this.matchRegExp = /-{1}[\<\^\>\.]{1}/mg;
};

exports.parse = function() {
// Move past the match
this.parser.pos = this.matchRegExp.lastIndex;
var arrow;
switch(this.match[0].slice(-1)){
case ">": 
arrow = "";
break;
case "<": 
arrow = "";
break;
case ".": 
arrow = "";
break;
case "^": 
arrow = "";
break;
}
return [{
type: "entity",
entity: arrow
}];
};

})();

[tw5] Re: [theme] Presenting "Mono" theme

[Anjar]

JD - I think your theme is amazing! It is so fun to work with and it is so 
easy to make things look great!

A small suggestion (which I guess would apply to tiddlywiki in general, not 
just the mono theme) from me is to enhance the print css a little:) After 
some fiddling, I find this nice:

@media print {
@page {
  size: A4;
  margin: 2cm;
}
.tc-sidebar-scrollable, .tc-topbar, .tc-tiddler-controls{
  display: none !important;
}
.tc-titlebar, .tc-tiddler-title{
  position: static;
  top: 0mm;
}
h2.tc-title{
  font-size: xx-large !important;
}
.tc-story-river{
  display: block;
  margin-top: 0mm;
}
.tc-tiddler-frame{
  background-color: white;
  display: block;
}
.tc-tiddler-body{
  page-break-after: always;
}
}


Best,
Anders

lørdag 1. august 2020 kl. 03:14:59 UTC+2 skrev JD:

> Oh wow, thanks for the compliments TT, this is making me want to speed up 
> my update process more and delay some new TW projects (ahaha!)
>
> I'll look into it! 
>
> -jd
>
>
> On Saturday, August 1, 2020 at 5:01:47 AM UTC+9, TiddlyTweeter wrote:
>>
>> Ciao JD
>>
>> Replying as of Late July 2020.
>>
>> I'd like to suggest you make a "Plugin Library" for all your themes. Why? 
>> Because its obvious they are widely appreciated and used. Because having a 
>> single install point makes that efficient. Better for users. Easier for you 
>> to maintain & distribute canonical versions.
>>
>> Best wishes
>> TT
>>
>> On Monday, 4 February 2019 00:08:01 UTC+1, JD wrote:
>>>
>>> Hello everyone,
>>>
>>> JD here, offering a kind of stark theme that incorporates my most 
>>> personal needs for a writing interface:
>>>
>>> [x] Sidebar to the <- left
>>> [x] Built-in mobile layout
>>> [x] Centered story river (when sidebar is closed)
>>> [x] Sidebar segments visibility toggler at Control Panel 
>>> [x] TopLeftBar buttons visibility toggler at Control Panel 
>>> [x] EmptyStoryMessage template
>>> [x] Splashcreen template
>>> [x] TiddlerFrame style
>>> [x] AdvancedSearch tabs on TopRightBar searchbar
>>> [x] TopRightBar searchbar you can create a tiddler from like NTFS or NTFS19
>>> [x] Font scroller button
>>> [x] Day/night palete switcher button
>>>
>>>
>>> *Here is the main conceit of the mobile UI:*
>>>
>>> The main change has been to TopBarLeft and TopBarRight. They are still 
>>> separated, but are now contained in a wrapper, like this:
>>>
>>>
>>> 
>>> 
>>> (items tagged $:/tags/TopLeftBar)
>>> 
>>> 
>>> (items tagged $:/tags/TopRightBar)
>>> 
>>> 
>>>
>>>
>>> On desktop, the wrapper, tc-topbar, is by default arranged in a row... 
>>> but on mobile it has this: flex-wrap: wrap;... so if tc-topbar-left has 
>>> width: 
>>> 100%;, tc-topbar-right will automatically be stacked below it.
>>>
>>>
>>> By combining the left and right topbars, the special class 
>>> tc-adjust-top-of-scroll is now incorporated to both 
>>> the TopBarLeft and TopBarRight templates. This is especially useful for 
>>> mobile UI.
>>>
>>>
>>> I might extract just this bit into the next iteration of 
>>> my MobilePlugin, albeit it will only be for TW5.1.19 and above.
>>>
>>>
>>> You can try it out, and install from here:
>>>
>>>
>>> http://j.d.mono.tiddlyspot.com/
>>>
>>>
>>> A future update would be this:
>>>
>>>
>>> [ ] hoverable buttons <- for next update
>>>
>>> [ ] hoverable topbar on desktop <- for next update
>>>
>>>  and some other stuff I'm forgetting right now
>>>
>>>
>>> I've been using this with BTC's app, and it works so nice so I'm sharing 
>>> this with you all :D
>>>
>>>
>>> -jd
>>>
>>>
>>> P.S.: 
>>>
>>>
>>> Shoutout to BTC and his amazing development! I love it and it's great 
>>> with an automatic GoogleDrive android->desktop syncer
>>>
>>>
>>> Thank you everyone for the inspiration!
>>>
>>>
>>>

-- 
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/587b4790-4044-410b-a0d1-bf2309288775n%40googlegroups.com.

[tw5] Re: Private and public tiddlers in single-file wiki with tw-receiver

[Anjar]

Thank you for sharing your thoughts! Including php in the tiddlywiki itself 
was an intriguing idea

Another idea that comes to mind is to detect if the tiddlywiki has been 
changed since you opened it and merge the to files instead of overwriting. 
I guess it should be trivial to make the tw-receiver script compare the 
versions and make new tiddlers with a specific tag where there is conflic, 
and then we can use a plugin in the wiki to compare the conflicts when they 
exist

Anders
mandag 23. november 2020 kl. 07:06:00 UTC+1 skrev TW Tones:

> Anders, 
> I am interested in the idea you suggest and have explored this space 
> before.
>
> Some quick notes;
>
>- You can use the separate local storage plugin to do the reverse, 
>keep the public on disk and the private in memory
>   - Providing a way to export/save the local storage.
>- You can separately encrypt tiddlers.
>- A solution could be built on top of multiple wikis with a variation 
>in permissions for functional reasons and name based files.
>- HTML can be published in tiddlywiki but operate on a PHP host, ie 
>has other file dependencies like javascript and PHP.
>
>
> Tones
>
> On Sunday, 22 November 2020 at 15:51:35 UTC+11 digit...@gmail.com wrote:
>
>> I absolutely love tw-receiver it is so incredibly useful.  This looks 
>> really interesting I will definitely give it a try.  There are so many php 
>> enabled hosts out there I hope folks will look further into this method of 
>> hosting and saving as they look for alternatives to tiddlyspot.
>>
>> On Friday, November 20, 2020 at 8:59:08 AM UTC-5 Anjar wrote:
>>
>>> Hi all, 
>>>
>>> I know there has been some discussions on how to manage to have both 
>>> public and private tiddlers, so here is my take on the problem:
>>>
>>> If we use tw-receiver as the saving mechanism, we can post-process the 
>>> html file after saving with PHP. The most brutal form would be to simply add
>>>
>>> // make a public version
>>>   $doc = new DOMDocument();
>>>   $doc->loadHTML(file_get_contents($destinationfile));
>>>   $selector = new DOMXPath($doc);
>>>   
>>>   // search for private tiddlers
>>>   $result = $selector->query('//div[contains(@tags, "Private")]');
>>>   
>>>   // loop through all private tiddlers
>>>   $titletext = array();
>>>   foreach($result as $item) {
>>>   $titletext[] = $item->getAttribute("title"); //save the title 
>>> for later
>>>   $item->parentNode->removeChild($item); // remove the tiddler
>>>   }
>>>   $str_doc = $doc->saveHTML(); // convert to string
>>>   $str_doc = str_replace($titletext, '%%%', $str_doc); // remove all 
>>> mentions of the private tiddler
>>>   $doc->loadHTML($str_doc); //convert back
>>>   $doc->saveHTMLFile("./public.html"); // save public version
>>>
>>> to tw-receiver-server.php (see https://github.com/andjar/tw-receiver). 
>>> This would create a third output file called public.html and remove all the 
>>> tiddlers tagged with Private and also replace all mentions of it with %%% 
>>> (tags, text, links, field etc.). I will try to refine it so that a private 
>>> tiddler called "link" would not mess up all the html link attributes and so 
>>> on. Maybe it would be enough to replace in-text links only (and the 
>>> occurence in the tiddler list in the beginning of the html)?
>>>
>>> So one can have an admin wiki protected by basic http auth with drafts 
>>> and so on, and each time one saves, the public version is updated as well. 
>>> Then it may be useful to have the tw-receiver password hard coded so that 
>>> one authentication is enough
>>>
>>> Best,
>>> Anders
>>>
>>

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/b1658aa2-4767-4415-bfd8-1420d651894bn%40googlegroups.com.

[tw5] Private and public tiddlers in single-file wiki with tw-receiver

[Anjar]

Hi all, 

I know there has been some discussions on how to manage to have both public 
and private tiddlers, so here is my take on the problem:

If we use tw-receiver as the saving mechanism, we can post-process the html 
file after saving with PHP. The most brutal form would be to simply add

// make a public version
  $doc = new DOMDocument();
  $doc->loadHTML(file_get_contents($destinationfile));
  $selector = new DOMXPath($doc);
  
  // search for private tiddlers
  $result = $selector->query('//div[contains(@tags, "Private")]');
  
  // loop through all private tiddlers
  $titletext = array();
  foreach($result as $item) {
  $titletext[] = $item->getAttribute("title"); //save the title for 
later
  $item->parentNode->removeChild($item); // remove the tiddler
  }
  $str_doc = $doc->saveHTML(); // convert to string
  $str_doc = str_replace($titletext, '%%%', $str_doc); // remove all 
mentions of the private tiddler
  $doc->loadHTML($str_doc); //convert back
  $doc->saveHTMLFile("./public.html"); // save public version

to tw-receiver-server.php (see https://github.com/andjar/tw-receiver). This 
would create a third output file called public.html and remove all the 
tiddlers tagged with Private and also replace all mentions of it with %%% 
(tags, text, links, field etc.). I will try to refine it so that a private 
tiddler called "link" would not mess up all the html link attributes and so 
on. Maybe it would be enough to replace in-text links only (and the 
occurence in the tiddler list in the beginning of the html)?

So one can have an admin wiki protected by basic http auth with drafts and 
so on, and each time one saves, the public version is updated as well. Then 
it may be useful to have the tw-receiver password hard coded so that one 
authentication is enough

Best,
Anders

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/f31d2d90-29f6-49bc-80e6-f2d4163d10fen%40googlegroups.com.

[tw5] Re: Use _canonical_uri to embed an external plain text file?

[Anjar]

Hi TT,

I'm not sure I follow your thoughts. For example, I have an online 
tiddlywiki for sheet music and since some of the scores are in public 
domain and others not, I separate them and protect the latter with 
htaccess. That way I can still make a tiddler for it and tag it etc. and 
embed the pdf with _canonical_uri and application/pdf, but restrict access 
to myself only.

Similarly, I guess it would be trivial to have a html/php form embedded in 
tiddlywiki from a protected folder that creates "protected tiddlers" in an 
otherwise public tiddlywiki, which at least I think expands the usability 
of tiddlywiki, especially if it becomes possible to load those external 
files at start and treat them as ordinary tiddlers. Just a thought:)

Best,
Anders

mandag 9. november 2020 kl. 18:17:08 UTC+1 skrev TiddlyTweeter:

> Ciao Anjar
>
> ... you can have some content public but also put some content in a 
>> subfolder protected by htaccess and include it in the tiddlywiki. Works 
>> perfectly for pfs etc
>>
>
> Right. Though that is nothing to do with TW, or changes anything you do in 
> it.
>
> The only TW bit I can see is you COULD use the Bob version to 
> create/delete  any needed .htaccess files on-the-fly.
>
> Thoughts
> TT
>

-- 
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/63210bcf-d3fe-411a-86ae-a5eeb587a927n%40googlegroups.com.

[tw5] Re: Use _canonical_uri to embed an external plain text file?

[Anjar]

Hi,

I'm rather interested in this as well as it may be a way of implementing 
access control through htaccess; you can have some content public but also 
put some content in a subfolder protected by htaccess and include it in the 
tiddlywiki. Works perfectly for pfs etc.

Best,
Anders

mandag 9. november 2020 kl. 15:21:16 UTC+1 skrev si:

> Hi Joshua, thanks for your reply.
>
> I tried out your suggestion for node.js and although the tiddlers for the 
> text-files do get created, the text still won't display.
>
> I created the file "tiddlers/text-files/tiddlywiki.files" as you 
> described, and put the file "Text file.txt" into the same directory.
>
> Here is the contents of "tiddlywiki.files":
>
> {
> "directories": [
> {
> "path": "",
> "filesRegExp": "^.*\\.txt$",
> "isTiddlerFile": false,
> "fields": {
> "title": {"source": "basename-uri-decoded"},
> "created": {"source": "created"},
> "modified": {"source": "modified"},
> "type": "text/plain",
> "tags": ["$:/tags/AttachedFile"],
> "text": "",
> "_canonical_uri": {"source": "filename", "prefix": ""}
> }
> }
> ]
> }
>
>
> The result is that a tiddler for "Text file" does appear in my wiki, but 
> still no text is displayed. See here .
>
> I also tried the same thing but with PDFs and still the content would not 
> display.
>
> Any idea what I'm doing wrong?
>
>
> On Monday, 9 November 2020 04:44:49 UTC, Joshua Fontany wrote:
>>
>> This is possible if you are running your wiki on Node.js. If it is a 
>> single-file standalone HTML wiki your best bet is to import the text files 
>> by drag'n'drop.
>>
>> If you are running on Node.js, you can use a "tiddlywiki.files" file 
>> (documentation 
>> here ), to include a 
>> whole folder full of files at once into tiddlywiki. The config file defines 
>> the other "meta-data fields" like "type", etc. The folder in question has 
>> to be inside said wiki's "tiddlers" folder (where "tiddlers is parallel to 
>> a "tiddlywiki.info" config file). Your structure would be similar to:
>>
>> WikiDir
>> |- "tiddlywiki.info" (json file for wiki config)
>> |- "tiddlers" dir
>> |- "text-files" dir
>> |- "tiddlywiki.files" (json file for text-file import 
>> config)
>> |-  all the files to import 
>> |- "other" dirs (in the "tiddlers" dir)
>> |- tiddlers.tid(s) (text tiddlers in the "tiddlers" dir)  
>> |- "files" dir (outside "tidders" to serve images and such)
>>
>>
>>
>> On Sunday, November 8, 2020 at 5:34:46 PM UTC-8 TW Tones wrote:
>>
>>> Si,
>>>
>>> Understood. I have tried to encourage others with more knowledge on this 
>>> to help us make such included content interact more within tiddlywiki. I 
>>> understand the problem may relate to the object being included in the 
>>> standard DOM, but tiddlywiki manages its own DOM tree to preform all it's 
>>> magic.
>>>
>>> keep in mind I am not expert here.
>>>
>>> A higher level of interaction with html and the standard DOM including 
>>> between the DOM and Tiddlywikis own one would be nice, For example an 
>>> action that will populate a local tiddler with the content displayed by the 
>>> object.
>>>
>>> I have actually installed full featured html pages within tiddlywiki, 
>>> and by providing the additional files, css and scripts in the same 
>>> directory as the single file tiddlywiki, have got them working. So I am 
>>> confident we can create ways to interact with external resources.
>>>
>>> Simply being able to save the output of something like;
>>> >> "file:///C:\Data\batches\networkcheck.txt"> 
>>> into a tiddler, variable or on wikification would be great.
>>>
>>> However you would be applying dynannotate to a copy.
>>>
>>> Regards
>>> Tones
>>>
>>>
>>> On Sunday, 8 November 2020 23:58:58 UTC+11, si wrote:

 Hi Tones,

 The HTML object method does display the file, but I can't add 
 annotations to with dynannotate.I realize I was not clear about what I 
 wanted to use the file for in my original post.

 I'm trying to get the text file to display just as though it were a 
 plain text tiddler stored in the wiki. I know I won't be able to edit it 
 from the wiki, but I was hoping that I would be able to add annotations 
 with dynannotate.

 On Friday, 6 November 2020 22:11:40 UTC, TW Tones wrote:
>
> Si,
>
> Have you tried the html object tag?
>
> I have a newtworkcheck batch that I launch from a TiddlyDesktop wiki, 
> that returns the result in a text file.
>
>
>  "file:///C:\Data\batches\runnetworkcheck.cmd" > Go
>
> <$button set="Networkcheck!!last-refresh" setTo=<> >
> Refresh {{Networkcheck!!last-refresh}}
> 
>
> 

[tw5] Re: HOWTO: Upload files/images to cloud storage automatically

[Anjar]

Hi,

Haven't tested it, but it may be possible to add an iframe pointing to 
dropbox, for example in the sidebar? Tag a tiddler with 
$:/tags/SideBarSegment and add

http://dropbox.com; width="100%" height="300px" 
style="border:none;">


Seems like dropbox doesn't like it, but maybe one can fix it somehow

Best,
Anders

onsdag 4. november 2020 kl. 00:29:11 UTC+1 skrev TW Tones:

> Carlos,
>
> I would imagine you can just get Drop box to sync the folder you are using 
> that you want uploaded and it happens in the background. 
>
> Perhaps search the forum and tiddlywiki.com for "dropbox".
>
> Tones
>
>
> On Tuesday, 3 November 2020 13:52:41 UTC+11, Carlos R wrote:
>>
>>
>> I am using nodejs version and I want a way to automatically upload files 
>> to a cloud storage service such as dropbox. Has anyone attempted this? I 
>> like to take screen shots with my notes and it's a bit cumbersome to have 
>> to manually link files/images.
>>
>> 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/f0326444-5fa7-4c7c-8f2f-bb1c888c0848n%40googlegroups.com.

[tw5] Tufte-like sidenotes: generate random ids

[Anjar]

Hi all!

Some of you may be familiar with Edward Tufte 
(https://edwardtufte.github.io/tufte-css/), and I think his sidenote 
approach can be useful in TiddlyWiki as well if one wants to add comments 
to the contents of a tiddler. I tried to make a simple macro which work 
fairly well, but to make a new number for each comment, I need to generate 
a unique ID for it. Is this possible or do I need another approach? For 
example, I added highlighting on hover which may reduce the need for unique 
identifiers., but it would still be nice for say printing. 

\define comment(txt)


$txt$
\end


.comment:hover .sidenote {
background-color: yellow;
}

input.margin-toggle {
display: none;
}

label.sidenote-number {
display: inline;
}

label.margin-toggle:not(.sidenote-number) {
display: none;
}

.sidenote,
.marginnote {
float: right;
clear: right;
margin-right: -60%;
width: 50%;
margin-top: 0.3rem;
margin-bottom: 0;
font-size: 1.1rem;
line-height: 1.3;
vertical-align: baseline;
position: relative;
}

.sidenote-number {
counter-increment: sidenote-counter;
}

.sidenote-number:after,
.sidenote:before {
font-family: et-book-roman-old-style;
position: relative;
vertical-align: baseline;
}

.sidenote-number:after {
content: counter(sidenote-counter);
font-size: 1rem;
top: -0.5rem;
left: 0.1rem;
}

.sidenote:before {
content: counter(sidenote-counter) " ";
font-size: 1rem;
top: -0.5rem;
}


This<> is an<> example<>


Best,
Anders

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/fa230aa6-304a-4ad5-816a-8aa7c443eab4n%40googlegroups.com.

[tw5] Re: New Plugin tw-receiver saves wiki to PHP

[Anjar]

Hi!

I was experimenting a bit, and is the stale overwrite protection feature 
still working? When I tested with the tw open in two tabs, A and B, then 
saved A first with one change, and added another change to B, then only the 
latest saved change was kept (i.e. A was overwritten)

Best,
Anders

torsdag 12. mars 2020 kl. 02:40:05 UTC+1 skrev TW Tones:

> Sendwheel,
>
> A most useful and working method, on a very common platform.
>
> All I dream of now is being able to save other files to the same server 
> platform, eg a users comments, or proposed changes.
>
> Regards
> Tony
>
>
> On Thursday, March 12, 2020 at 12:07:17 PM UTC+11, sendwheel wrote:
>>
>> Still maintained and still used. Glad to see new faces using the plugin.
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/819e82c2-ecad-4d6f-9d80-a9a1683b16e4n%40googlegroups.com.

[tw5] Re: [Plugin] TWCrossLinks

[Anjar]

Sorry for the delay: Thanks for the update, Tony! It's a very interesting 
idea!


Best,
Anders 

mandag 22. juni 2020 kl. 02:59:37 UTC+2 skrev TW Tones:

> Anjar,
>
> No time to finish publishing something, but this similar to a recent ideal 
> I am developing called "autonomous-fields". 
>
> Basically a single tiddler, by the name of the fieldname, with the view 
> template tag, which displays its own value in tiddlers that use it.
>
> Keep an eye out for it.
>
> Regards
> Tony
>
>
> On Wednesday, June 3, 2020 at 4:22:26 PM UTC+10, Anjar wrote:
>>
>> Hi,
>>
>> Another idea; maybe it could be useful to generalize from keywords and 
>> tags to custom/all fields? Say I have a tiddler about a book, then I add an 
>> author field, and the tiddler about the author automatically gets a tab 
>> called "Author" referencing the book tiddler
>>
>> Best,
>> Anders
>>
>>

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/4b76edb6-f761-4c67-ac12-edf894544920n%40googlegroups.com.

[tw5] Re: [Plugin] Daily Notes - Interstitial Journaling plugin TiddilyWiki

[Anjar]

Hi Tony,

Yes, that's right. The macro I used as example already filters for the 
hashtags, but does not render /todo as checkboxes, but I guess there is a 
template for that? Another example can be extracting external links (I 
often use the DailynNote for simple bookmarking), with http;

\define listNotes(txt:"")
<$list filter="[!title{!!title}tag[DailyNotes]search:text[$txt$]reverse[]]" 
>

!! {{!!title}}
<$list filter="[titleget[text]splitregexp[]regexp[(?i)$txt$]join[]]"  variable=note>
<>


\end

<>



Best,
Anders

torsdag 4. juni 2020 12.59.51 UTC+2 skrev Tony K følgende:
>
> Thanks for the reply
>
> let me make sure I understood correctly
>
> today you already can add #ProjectX before and entry right ? so you would 
> want to get a way to list (for example) all entries for #projectA ?? did i 
> get it right?
>
> for todo I started added todo on the previous version and just enhanced it 
> in this one. give /todo a test and tell me how it goes 
>
> Cheers
>
> On Thursday, June 4, 2020 at 1:54:37 PM UTC+3, Anjar wrote:
>>
>> I feel like a spoiled child throwing out requests:) But it's incredibly 
>> nice how you and other plugin developers interact with the community - it's 
>> gold!
>>
>> In this case I was thinking about tagging my entries; say #projectA, 
>> #projectB; and then list entries by day in the corresponding projects with 
>> that macro (which s too simple, in a perfect world it would also support 
>> the todo elements). Then I have one single place to empty my brain and also 
>> a single tiddler summarising my day and the possibility to extract only 
>> project entries, which is perfect for me:)
>>
>> Best,
>> Anders
>>
>> torsdag 4. juni 2020 12.29.06 UTC+2 skrev Tony K følgende:
>>>
>>> Thank you Anjar
>>>
>>> I am really enjoying your suggestion on my plugins and thanks for that. 
>>>
>>> can you please share a case scenario for this suggestion please ?
>>>
>>> On Friday, May 29, 2020 at 12:14:48 AM UTC+3, Anjar wrote:
>>>>
>>>> Very nice plugin, Tony! Just wanted to share this simple macro for 
>>>> listing all the entries containing the word "filterword"
>>>>
>>>> \define listNotes(txt:"")
>>>> <$list 
>>>> filter="[!title{!!title}tag[DailyNotes]search:text[$txt$]reverse[]]" >
>>>>
>>>> !! {{!!title}}
>>>> <$list filter="[titleget[text]splitregexp[>>> />]regexp[(?i)$txt$]join[]]"  variable=note>
>>>> <>
>>>> 
>>>> 
>>>> \end
>>>>
>>>> <>
>>>>
>>>>
>>>>
>>>>
>>>> Best,
>>>> Anders
>>>>
>>>> søndag 17. mai 2020 17.53.27 UTC+2 skrev Tony K følgende:
>>>>>
>>>>> fixed
>>>>> thanks for letting me know
>>>>>
>>>>> On Sunday, May 17, 2020 at 5:22:52 PM UTC+3, Riz wrote:
>>>>>>
>>>>>> Hi, links to demo seems dead?
>>>>>
>>>>>

-- 
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/43d674aa-659d-4f2a-afb7-291544a669d4%40googlegroups.com.

[tw5] Re: [Plugin] Daily Notes - Interstitial Journaling plugin TiddilyWiki

[Anjar]

I feel like a spoiled child throwing out requests:) But it's incredibly 
nice how you and other plugin developers interact with the community - it's 
gold!

In this case I was thinking about tagging my entries; say #projectA, 
#projectB; and then list entries by day in the corresponding projects with 
that macro (which s too simple, in a perfect world it would also support 
the todo elements). Then I have one single place to empty my brain and also 
a single tiddler summarising my day and the possibility to extract only 
project entries, which is perfect for me:)

Best,
Anders

torsdag 4. juni 2020 12.29.06 UTC+2 skrev Tony K følgende:
>
> Thank you Anjar
>
> I am really enjoying your suggestion on my plugins and thanks for that. 
>
> can you please share a case scenario for this suggestion please ?
>
> On Friday, May 29, 2020 at 12:14:48 AM UTC+3, Anjar wrote:
>>
>> Very nice plugin, Tony! Just wanted to share this simple macro for 
>> listing all the entries containing the word "filterword"
>>
>> \define listNotes(txt:"")
>> <$list 
>> filter="[!title{!!title}tag[DailyNotes]search:text[$txt$]reverse[]]" >
>>
>> !! {{!!title}}
>> <$list filter="[titleget[text]splitregexp[> />]regexp[(?i)$txt$]join[]]"  variable=note>
>> <>
>> 
>> 
>> \end
>>
>> <>
>>
>>
>>
>>
>> Best,
>> Anders
>>
>> søndag 17. mai 2020 17.53.27 UTC+2 skrev Tony K følgende:
>>>
>>> fixed
>>> thanks for letting me know
>>>
>>> On Sunday, May 17, 2020 at 5:22:52 PM UTC+3, Riz wrote:
>>>>
>>>> Hi, links to demo seems dead?
>>>
>>>

-- 
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/19ec9458-8a23-45d7-801b-814bbfe23cf3%40googlegroups.com.

[tw5] Re: [Plugin] TWCrossLinks

[Anjar]

Hi,

Another idea; maybe it could be useful to generalize from keywords and tags to 
custom/all fields? Say I have a tiddler about a book, then I add an author 
field, and the tiddler about the author automatically gets a tab called 
"Author" referencing the book tiddler

Best,
Anders

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/4867c41b-63ae-485b-b9ad-64fcd9dfdc1f%40googlegroups.com.

[tw5] Re: [Plugin] Daily Notes - Interstitial Journaling plugin TiddilyWiki

[Anjar]

Very nice plugin, Tony! Just wanted to share this simple macro for listing 
all the entries containing the word "filterword"

\define listNotes(txt:"")
<$set name=filter1 value="[!title{!!title}tag[DailyNotes]search:text[$txt$]
reverse[]]" >
<$list filter=<> >
<$set name=filter2 value="[titleget[text]splitregexp[]regexp[(?i)$txt$]join[]]">

!! {{!!title}}
<$list filter=<>  variable=note>
<>




\end

<>




Best,
Anders

søndag 17. mai 2020 17.53.27 UTC+2 skrev Tony K følgende:
>
> fixed
> thanks for letting me know
>
> On Sunday, May 17, 2020 at 5:22:52 PM UTC+3, Riz wrote:
>>
>> Hi, links to demo seems dead?
>
>

-- 
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/320edbb7-aa9c-4617-b760-2553f3188e62%40googlegroups.com.

[tw5] Re: [Plugin] TWCrossLinks

[Anjar]

Sure! And I agree, since DailyNotes uses the title format -mm-dd 
already, it will fit nicely. Maybe even as a separate tab "Reminders" 
similar to Backlinks and Keywords (that's why I thought it could be nice 
for TWCrossLinks)? But I imagine it can be integrated nicely into the 
DailyNotes log-format also!

Best,
Anders

tirsdag 26. mai 2020 06.30.51 UTC+2 skrev Tony K følgende:
>
> Hi Anders
>
> I do like your suggestion a lot but I think it fits more into DailyNotes 
> than in TWCrossLinks
>
> do you use DailyNotes? It will be a great addition to it if you don't mind 
> me using it
>
> On Tuesday, May 26, 2020 at 2:18:16 AM UTC+3, Anjar wrote:
>>
>> Thanks Tony for this wonderful plugin! 
>>
>>
>> I was taking some notes today and realising it would be nice to have some 
>> way to handle reoccurence in some; birthdays, important dates and so on. 
>> Maybe it could be possible to add regular expression to keywords in some 
>> way? Eg. if I just 01 add as keyword, it will show up on all my journal 
>> tiddlers the first each month; if I add the keyword 02-01 it will show only 
>> every February 1.; using 2022-02-01 will add it to the keyword list 
>> February 1. in 2022 (but the latter will already happen if I call the 
>> journal tiddler 2022-02-01). Just a thought! 
>>
>> Edit: I guess some of you know better ways, but I think this may work: 
>>
>>
>> \define test() 
>> <$list filter="[{!!title}split[-]]" variable="t"><$set name=l 
>> filter="[length[]]" >(<>|[0]{<>})  
>> \end 
>>
>> <$wikify name=outr text=<> mode=inline> 
>> <$set name=out filter="[trim[]split[ ]join[-]]"> 
>> <]">> 
>>  
>>  
>>
>> where -00-01 is the first of each month; -01-00 is every day each 
>> January and so on 
>>
>> Best, 
>> Anders 
>>
>>
>> mandag 25. mai 2020 10.26.24 UTC+2 skrev Tony K følgende: 
>> Hello SizzlinSJ yes I did because now tabs are dynamically hidden when 
>> they are empty, so I couldn't see how to fit a default tab in all that 
>>
>> On Monday, May 25, 2020 at 10:10:17 AM UTC+3, SizzlinSJ wrote: 
>> It's late but, did you remove 'Select which Tab you want to be open by 
>> Default' option in update v1.20. Any reason for 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 view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/45e3de12-f005-481f-afc6-c57b97f05726%40googlegroups.com.

[tw5] Re: [Plugin] TWCrossLinks

[Anjar]

Thanks Tony for this wonderful plugin!

I was taking some notes today and realising it would be nice to have some 
way to handle reoccurence in some; birthdays, important dates and so on. 
Maybe it could be possible to add regular expression to keywords in some 
way? Eg. if I just 01 add as keyword, it will show up on all my journal 
tiddlers the first each month; if I add the keyword 02-01 it will show only 
every February 1.; using 2022-02-01 will add it to the keyword list 
February 1. in 2022 (but the latter will already happen if I call the 
journal tiddler 2022-02-01). Just a thought!

Best,
Anders


mandag 25. mai 2020 10.26.24 UTC+2 skrev Tony K følgende:
>
> Hello SizzlinSJ yes I did because now tabs are dynamically hidden when 
> they are empty, so I couldn't see how to fit a default tab in all that
>
> On Monday, May 25, 2020 at 10:10:17 AM UTC+3, SizzlinSJ wrote:
>>
>> It's late but, did you remove 'Select which Tab you want to be open by 
>> Default' option in update v1.20. Any reason for 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 view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/dc98f74e-adab-48bf-bce4-0c006bcfed07%40googlegroups.com.

[tw5] Using store.php without username/password

[Anjar]

For reference, I think the easiest is to use tw-receiver 
(https://github.com/sendwheel/tw-receiver) and hardcode the secret key on line 
38 in tw-receiver-handler-comp.js. Then all you need is having 
tw-receiver-server.php and the wiki in the same folder, and it works beautifully

-- 
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/ed6d0909-2712-4eff-b889-076f8eb583c7%40googlegroups.com.

[tw5] Re: Preview: keyboard driven draggable bullets

[Anjar]

Looks awesome! Keep us updated!

Best,
Anders

onsdag 20. mai 2020 23.44.31 UTC+2 skrev Saq Imtiaz følgende:
>
> When I'm under the weather I tend to prototype. Spent some time reworking 
> code from my eternally in progress task manager in an attempt to make it 
> more general purpose, as a bullet list note taking tool that may be of 
> utility to others. 
>
>
> https://drive.google.com/file/d/1SB06s13tj8P3cC2UewnfzXf08UQ7jwYK/view?usp=drivesdk
>
>
> https://drive.google.com/file/d/1SLESm6OIfHsScwYePGOs5ce3o3wpQ0CO/view?usp=drivesdk
>
> - everything except the dragging is keyboard driven
> - each bullet is a separate tiddler. Lots of different pros and cons to 
> this approach, but was ideal for a task manager.
> - this is all in wikitext, no extra JS.
>
>  Will post the file in the near future, a bit more clean up needed. Don't 
> expect a final product, but rather a pattern to follow that would hopefully 
> help anyone wanting to implement similar workflow. 
>
> Cheers,
> Saq
>
>

-- 
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/d977ab26-c627-489f-8364-6b0f060f8c91%40googlegroups.com.

[tw5] Re: [Question] Can the refnotes plugin be used to make A.P.A. style reference?

[Anjar]

I agree @TT, that would be useful! Combine this with some way to export to 
pandoc-ready markdown with citations and we are close to a real alternative 
for academic writing

Best,
Anders

tirsdag 12. mai 2020 11.53.08 UTC+2 skrev TiddlyTweeter følgende:
>
> Ciao Odin,
>
> Interesting thread!
>
> Flexible citation styling is a real world issue for academic writing.
>
> In my own case, for instance, I work in humanities and social science 
> where APA & Chicago are often needed. It don't want have to hack that. Just 
> switch on per document basis.
>
> *Ideally one should be able to switch between the major citation styles in 
> TW*. I think its slowly coming.
>
> Your post is important because it succinctly presents the issues in a 
> concrete way.
>
> An issue is the more esoteric citations. For instance "grey literature" or 
> "intermittent journals". Its complex to cope with all variations.
>
> YET, for my use, just getting styling working for *the main cases *is 
> good enough to work with --- and likely most writers most of the time.
>
> The variant styling solution are likely toggleable between a "click" for a 
> good TW programmer?
>
> Side thoughts
> TT
>
> On Monday, 11 May 2020 12:32:30 UTC+2, Odin Jorna wrote:
>>
>> It seems that the https://kookma.github.io/Refnotes/ refnotes plugin 
>> uses another type of reference style than the A.P.A. style that I am used 
>> (or supposed to use) to.
>> It is possible to use this plugin to create A.P.A. style reference? It 
>> uses this format: Author, A., & Author, B. (year). *Title of book.* 
>> Publisher. 
>> or Author, A., & Author, B. (year). Title of article. *Journal Title*, 
>> *Volume*(Issue), page range. DOI for scientific articles.
>>
>> So the example reference in the plugin: N.E. Amadeo and M.A. Laborde, 
>> Hydrogen 
>> Production From The Low-Temperature Water-Gas Shift Reaction: Kinetics And 
>> Simulation Of The Industrial Reactor,*International Journal of Hydrogen 
>> Energy*, *1995*.
>>
>> would look something like this: N.E. Amadeo and M.A. Laborde. (1995) 
>> Hydrogen 
>> Production From The Low-Temperature Water-Gas Shift Reaction: Kinetics And 
>> Simulation Of The Industrial Reactor,*International Journal of Hydrogen 
>> Energy*, *Volume*(Issue), page range. DOI
>>
>> The in text reference would be: (Amadeo & Laborde, 1995) instead of :  
>> [Amadoe-1995]
>> 
>>  
>>
>> Is there a way to change the formatting in the plugin code?
>>
>

-- 
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/6416cbe6-2d2c-461b-a1db-eeb4d2d6a5ec%40googlegroups.com.

[tw5] Re: [Question] Can the refnotes plugin be used to make A.P.A. style reference?

[Anjar]

Hi Odin,

Good question! First I thought this was controlled by the class parameter, 
but I was wrong. I think the easiest would be to add another macro 
in $:/plugins/kookma/refnotes/macro/bibtex/showrefs:

\define showrefsAPA(filter:"[]", title:"Empty", 
class:"ref-list")
<$reveal tag="div" type="nomatch" default="Empty" text=<<__title__>> >
$title$

<$wikify name="mylist" text="""
<$list filter=<<__filter__>> >
<$macrocall $name="find-refs" tid=<> />

""">

<$list filter="[enlistsort[]]" variable="myListItem">

<$macrocall $name=*"custom_output"* p=<> />



\end


and then call <>. Or, if you have already 
used the showrefs macro, you could simply insert the highlighted part into 
the existing showrefs macro and remove "output-journal-article" on that 
line. Or you can simply replace the output-journal-article macro defined 
in $:/plugins/kookma/refnotes/macro/bibtex/showrefs with the custom_putput 
macro and rename it. So many options:) Please let me know if it was hard to 
follow or you have questions!

Best, 
Anders

mandag 11. mai 2020 17.54.28 UTC+2 skrev Odin Jorna følgende:
>
> Thank you so much for helping me out. Would you use instead of < title:"References">>, <> in your example, 
> to make a reference list with the new ordering?
>
> Op maandag 11 mei 2020 14:48:04 UTC+2 schreef Anjar:
>>
>> Hi Odin,
>>
>> Have a look at the tiddler 
>> $:/plugins/kookma/refnotes/macro/bibtex/showrefs. You can make your own 
>> output style there, and fiddle with things as you want; this will move the 
>> year and add DOI and page range.
>>
>> \define custom_output(p)
>> <$wikify name=p2 text=<<__p__>> >
>> <$set name="curtid" tiddler=<> field="title" emptyValue="RefNotFound">
>> <$reveal type="nomatch" default="RefNotFound" text=<> >
>> <$view field="bibtex-author" tiddler=<>/> *(<$view 
>> field="bibtex-year" tiddler=<>/>)*, <$view field="bibtex-title" 
>> tiddler=<>/>,<$view field="bibtex-journal" 
>> tiddler=<>/>, *<$view field="bibtex-pages" 
>> tiddler=<>/>. DOI **<$view field="bibtex-doi" 
>> tiddler=<>/>*. 
>> 
>> <$reveal type="match" default="RefNotFound" text=<> >
>> Reference $p$ NOT FOUND. Check your 
>> input.
>> 
>> 
>> \end
>>
>> The in-text formatting is governed 
>> by $:/plugins/kookma/refnotes/macro/bibtex/ref; this will give you (author, 
>> year)
>>
>> \define ref(tid)
>> <$set name="ref-tid" tiddler=<<__tid__>> field="title" 
>> emptyValue="RefNotFound">
>> 
>> <$reveal type="match" default=<> text="RefNotFound">
>> <$link overrideClass="link-refcls">
>> [<$view tiddler=<<__tid__>> field="title"/>]
>> 
>> Warning: Reference Not 
>> Found.Click to create it:<>
>> 
>> <$reveal type="nomatch" default=<> text="RefNotFound">*(<$view 
>> tiddler=<<__tid__>> field="bibtex-author"/>, <$view tiddler=<<__tid__>> 
>> field="bibtex-year"/>)*
>> 
>> <$macrocall $name="displayref-onhover" refTid=<> />
>> 
>> 
>> 
>> 
>> \end
>>
>>
>>
>>
>>
>> Best,
>> Anders
>> mandag 11. mai 2020 12.32.30 UTC+2 skrev Odin Jorna følgende:
>>>
>>> It seems that the https://kookma.github.io/Refnotes/ refnotes plugin 
>>> uses another type of reference style than the A.P.A. style that I am used 
>>> (or supposed to use) to.
>>> It is possible to use this plugin to create A.P.A. style reference? It 
>>> uses this format: Author, A., & Author, B. (year). *Title of book.* 
>>> Publisher. 
>>> or Author, A., & Author, B. (year). Title of article. *Journal Title*, 
>>> *Volume*(Issue), page range. DOI for scientific articles.
>>>
>>> So the example reference in the plugin: N.E. Amadeo and M.A. Laborde, 
>>> Hydrogen 
>>> Production From The Low-Temperature Water-Gas Shift Reaction: Kinetics And 
>>> Simulation Of The Industrial Reactor,*International Journal of Hydrogen 
>>> Energy*, *1995*.
>>>
>>> would look something like this: N.E. Amadeo and M.A. Laborde. (1995) 
>>> Hydrogen 
>>> Production From The Low-Temperature Water-Gas Shift Reaction: Kinetics And 
>>> Simulation Of The Industrial Reactor,*International Journal of Hydrogen 
>>> Energy*, *Volume*(Issue), page range. DOI
>>>
>>> The in text reference would be: (Amadeo & Laborde, 1995) instead of :  
>>> [Amadoe-1995]
>>> <https://kookma.github.io/Refnotes/#AMADEO1995949>
>>>  
>>>
>>> Is there a way to change the formatting in the plugin code?
>>>
>>

-- 
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/3ddcbc82-1ad1-45b5-8f07-c7a0284cfac8%40googlegroups.com.

[tw5] Re: [Question] Can the refnotes plugin be used to make A.P.A. style reference?

[Anjar]

Hi Odin,

Have a look at the tiddler 
$:/plugins/kookma/refnotes/macro/bibtex/showrefs. You can make your own 
output style there, and fiddle with things as you want; this will move the 
year and add DOI and page range.

\define custom_output(p)
<$wikify name=p2 text=<<__p__>> >
<$set name="curtid" tiddler=<> field="title" emptyValue="RefNotFound">
<$reveal type="nomatch" default="RefNotFound" text=<> >
<$view field="bibtex-author" tiddler=<>/> *(<$view 
field="bibtex-year" tiddler=<>/>)*, <$view field="bibtex-title" 
tiddler=<>/>,<$view field="bibtex-journal" 
tiddler=<>/>, <$view field="bibtex-pages" tiddler=<>/>. 
DOI <$view field="bibtex-doi" tiddler=<>/>. 

<$reveal type="match" default="RefNotFound" text=<> >
Reference $p$ NOT FOUND. Check your 
input.


\end

The in-text formatting is governed 
by $:/plugins/kookma/refnotes/macro/bibtex/ref; this will give you (author, 
year)

\define ref(tid)
<$set name="ref-tid" tiddler=<<__tid__>> field="title" emptyValue="RefNotFound">

<$reveal type="match" default=<> text="RefNotFound">
<$link overrideClass="link-refcls">
[<$view tiddler=<<__tid__>> field="title"/>]

Warning: Reference Not 
Found.Click to create it:<>

<$reveal type="nomatch" default=<> text="RefNotFound">*(<$view 
tiddler=<<__tid__>> field="bibtex-author"/>, <$view tiddler=<<__tid__>> 
field="bibtex-year"/>)*

<$macrocall $name="displayref-onhover" refTid=<> />




\end





Best,
Anders
mandag 11. mai 2020 12.32.30 UTC+2 skrev Odin Jorna følgende:
>
> It seems that the https://kookma.github.io/Refnotes/ refnotes plugin uses 
> another type of reference style than the A.P.A. style that I am used (or 
> supposed to use) to.
> It is possible to use this plugin to create A.P.A. style reference? It 
> uses this format: Author, A., & Author, B. (year). *Title of book.* 
> Publisher. 
> or Author, A., & Author, B. (year). Title of article. *Journal Title*, 
> *Volume*(Issue), page range. DOI for scientific articles.
>
> So the example reference in the plugin: N.E. Amadeo and M.A. Laborde, 
> Hydrogen 
> Production From The Low-Temperature Water-Gas Shift Reaction: Kinetics And 
> Simulation Of The Industrial Reactor,*International Journal of Hydrogen 
> Energy*, *1995*.
>
> would look something like this: N.E. Amadeo and M.A. Laborde. (1995) Hydrogen 
> Production From The Low-Temperature Water-Gas Shift Reaction: Kinetics And 
> Simulation Of The Industrial Reactor,*International Journal of Hydrogen 
> Energy*, *Volume*(Issue), page range. DOI
>
> The in text reference would be: (Amadeo & Laborde, 1995) instead of :  
> [Amadoe-1995]
> 
>  
>
> Is there a way to change the formatting in the plugin code?
>

-- 
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/5a0f1768-34ba-456d-b3ba-63bf4bf1ce0e%40googlegroups.com.

[tw5] Context plugin makes static export crash

[Anjar]

Hi,

I am trying to do an export to static pages using the context plugin, the 
JSZip plugin and the export button of Anne-Laure Le Cunff 
. I have made a 
tiddler $:/blinks with
<$set name="bterm" value=<> >
<$list filter="[backlinks[]sort[title]limit[250]]">
{{!!title||$:/core/ui/ListItemTemplate}}
<$context term=<> />



and added this


`<$tiddler tiddler=<> >
<$view tiddler="$:/blinks" format="htmlwikified"/>
`


below  in $:/core/templates/static.tiddler.html. The 
export now crashes with Internal JavaScript Error, yielding "Uncaught 
TypeError: span.cloneNode is not a function". I don't know javascript well 
enough to figure out if this is a simple bug or a more major problem? What 
do you think? It seems to be related to the view widget


Best,
Anders

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/2828d938-9b97-44ac-87e9-a67e842d2a29%40googlegroups.com.

[tw5] Using store.php without username/password

[Anjar]

Hi,

I wondered if it is possible to use store.php without having to enter 
username and password? I often hide my tiddlywiki using .htaccess, and it 
would be easier to share access if I only had to make another user for 
htaccess instead of giving instructions on how to enter the configuration 
page etc. or make a specific login tiddler. I imagine having a folder on my 
server with a .htaccess, store.php and several single-file tiddlywikis that 
just save themselves, and to make a new tiddlywiki, just change the 
filename that store.php saves to (to duplicate the original).

A related question; is there any specific reason that the store.php is 
buried away instead of being hosted on tiddlywiki.com with a direct link? 
Alternatively, it would be pretty simple to make a tiddler that can 
autogenerate a store.php for copy-paste where you can add usernames and 
passwords with a small form (to make it easier to get started)? 

Best,
Anders

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/9a9b125e-0054-478a-83b1-ef4a2e36630b%40googlegroups.com.

[tw5] Re: Interstitial Journaling in TiddlyWiki

[Anjar]

Hi,

It's not as sophisticated as the log solution, but having a simple tiddler 
like the one below will create tiddlers with timestamp as title when 
hitting enter and supports inline tagging using hashtags; etc. writing 
"This is a #test with tags" and hitting will add a tiddler and tag it with 
"test" (and "$:/tags/item" for easy filtering)


\define additem()
<$action-listops $tiddler="$:/temp" 
$tags="[enlist{$:/temp!!text}lowercase[]removeprefix[#]]" />
<$action-listops $tiddler="$:/temp" $tags="+[append{$:/temp!!tags}] 
$:/tags/item" />
<$action-createtiddler $basetitle=<> 
text={{$:/temp!!text}} tags={{$:/temp!!tags}} />
<$action-setfield $tiddler="$:/temp" text="" tags="" />
\end

<$keyboard key="enter" actions=<>>
<$edit-text tiddler="$:/temp" tag="input" default="" />


<$list filter="[tag[$:/tags/item]]">

* {{!!text}}



Best,
Anders


søndag 26. april 2020 07.35.59 UTC+2 skrev Scott Kingery følgende:
>
> An article by Anne-Laure Le Cunff titled Interstitial journaling: 
> combining notes, to-do & time tracking - Ness Labs 
>  introduced me to the 
> concept. She wrote, "the basic idea of interstitial journaling is to write 
> a few lines every time you take a break, and to track the exact time you 
> are taking these notes."
>
> I liked the idea and thought I might be able to cobble together an 
> interesting tool for it using TIddlyWiki. Lots of great plugins and code 
> from Tiddlyblink make it not too hard. The main concept is being able to 
> add a new journal entry with as few barriers as possible.
>
> If it sounds interesting, have a look here: 
> https://techlifeweb.com/tiddlywiki/dailynotes.html
>
>
> Scott
>

-- 
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/1c5699a5-3de0-442a-a5ee-adb2c8c98047%40googlegroups.com.

[tw5] Re: Stroll: last call for experimenting

[Anjar]

Hi,

Brilliant work David! This may be the wrong thread and it may have been 
elaborated by others elsewhere or implemented more efficiently, so forgive 
me, but just had this thought related to roam; often tiddlers will be very 
short when they are capturing a single thought. Having a tiddler like the 
one below will give you a simple text field where you write a line of text 
and hit enter, and it is added as a tiddler but only displayed as a list 
item. And you can use # for tagging inline; eg. writing "This is a #test 
with a tag" will add the tag "test". It will save quite a few clicks in a 
day!

\define additem()
<$action-listops $tiddler="$:/temp" 
$tags="[enlist{$:/temp!!text}lowercase[]removeprefix[#]]" />
<$action-listops $tiddler="$:/temp" $tags="+[append{$:/temp!!tags}] 
$:/tags/item" />
<$action-createtiddler $basetitle=<> 
text={{$:/temp!!text}} tags={{$:/temp!!tags}} />
<$action-setfield $tiddler="$:/temp" text="" tags="" />
\end

<$keyboard key="enter" actions=<>>
<$edit-text tiddler="$:/temp" tag="input" default="" />


<$list filter="[tag[$:/tags/item]]">

* {{!!text}}


Best,
Anders

lørdag 2. mai 2020 21.19.53 UTC+2 skrev David Gifford følgende:
>
> Hi everyone
>
> I finally got around to updating Stroll (replacement for my TiddlyBlink). 
> I think it is just about ready. Here is the link:
>
> https://giffmex.org/experiments/stroll.experiment.html
>
> Play with it until you find its flaws. Be merciless. Make it bleed. Then 
> let me know what needs bandaging or amputating. You have one week.
>
> 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 view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/f9b81e6c-d77b-41ed-93fa-db6a02b3bc41%40googlegroups.com.

[tw5] Re: Minimalistic "single tiddler view" for short texts etc

[Anjar]

Hi @Petruschka,

The easiest way to use it, is to download the demo 
<https://ewy.no/tiddlytext.html>, open the sidebar (from the home tiddler) 
and delete the two example collections by hitting the Xs. Maybe it'll 
become a plugin one day if there is time:)

I'm not sure I understand the second part of your question. At the moment, 
all non-system tags (not starting with $:/) are considered as collections, 
and the slides need a tag (you can give it more than one tag, but it will 
mess up the pagination) and a page field (and optionally a texttitle and a 
subtitle field). These are added automatically if you use the newtext (the 
+-button) form.

Generally, it is possible to change the theme conditionally when tiddlers 
have a specific tag I think, but it is not implemented here

Please let me know if I misunderstood your question.

Best,
Anders

lørdag 2. mai 2020 10.47.57 UTC+2 skrev Petruschka følgende:
>
> Hello Anjar,
> I am a bit lost atm. What is the best way to use it/import your great 
> theme and use it only on dedicated tagged tiddlers so only those will show 
> up like in your demo? 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 view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/2d3f0b1d-c8cf-44cd-b410-101424988058%40googlegroups.com.

[tw5] Re: Enable Links To Missing Tiddlers

[Anjar]

Hi!

Have a look at this thread: 
https://groups.google.com/forum/m/#!search/create$20missing$20tiddler/tiddlywiki/xo-kICZZEcg

The suggested solution was made by @BurningTreeC:

"Place the following at the bottom of the "save-tiddler-actions" macro in the 
$:/core/ui/EditTemplate Tiddler :

<$list filter="[all[current]links[]is[missing]]">
<$action-createtiddler $basetitle=<>/>
"

And @MarkS specifies where it should be put:

"At the top of $:/core/ui/EditTemplate there is a macro, "actions". Put the 
text at the bottom of the macro, just before "\end""


Best,
Anders

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/1323e51a-32a8-429d-a8a3-1260475d17a4%40googlegroups.com.

[tw5] Re: Minimalistic "single tiddler view" for short texts etc

[Anjar]

Thanks! I tried different things, but after thinking a bit, maybe pure CSS 
is the simplest?


.savebutton{
position: fixed;
font-size: 40px;
bottom: 10%;
right: 0;
margin: 5%;
}
.savebutton svg {
display: none;
}
.savebutton body.tc-dirty span.tc-dirty-indicator, body.tc-dirty 
span.tc-dirty-indicator svg {
display: block;
}



{{$:/core/ui/Buttons/save-wiki}}



Best,
Anders

fredag 1. mai 2020 00.37.54 UTC+2 skrev TonyM følgende:
>
> Anjar,
>
> If you installed a trash bin plugin the delete would actually only be a 
> change if that helps. 
>
> This may not solve your deletes issue but there is a macro you may be 
> interested in https://tiddlywiki.com/#changecount%20Macro%20(Examples)
> It works for each tiddler title and counts the number of changes, in this 
> session.
>
> Regards
> Tony
>
> On Friday, 1 May 2020 06:40:10 UTC+10, Anjar wrote:
>>
>> I agree with you, @Julio, except that tiddlywiki is already gold;)
>>
>> The site <http://ewy.no/tiddlytext.html> is updated with the sidebar 
>> being context-related and the save button appearing when you add new 
>> tiddlers. To do the latter, I use the haschanged[] filter operator, but 
>> this dosn't work when one deletes a tiddler. Is there a better way than 
>> haschanged[] for detecting that changes has been made?
>>
>>
>> Anders
>>
>>
>>
>> torsdag 30. april 2020 17.38.21 UTC+2 skrev Julio Peña følgende:
>>>
>>> In my opinion we are all "alchemists" when it comes to Tiddlywiki. :))
>>>
>>> Regards,
>>> Julio
>>>
>>> On Thursday, April 30, 2020 at 7:22:07 AM UTC-4, Ste Wilson wrote:
>>>>
>>>> Wow!.  Why am I still surprised at the different shapes people hammer 
>>>> TiddlyWiki into? Very Zen!
>>>>
>>>

-- 
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/797973d2-ad5c-44b0-b262-640c29d0b36c%40googlegroups.com.

[tw5] Re: Minimalistic "single tiddler view" for short texts etc

[Anjar]

I agree with you, @Julio, except that tiddlywiki is already gold;)

The site  is updated with the sidebar being 
context-related and the save button appearing when you add new tiddlers. To 
do the latter, I use the haschanged[] filter operator, but this dosn't work 
when one deletes a tiddler. Is there a better way than haschanged[] for 
detecting that changes has been made?


Anders



torsdag 30. april 2020 17.38.21 UTC+2 skrev Julio Peña følgende:
>
> In my opinion we are all "alchemists" when it comes to Tiddlywiki. :))
>
> Regards,
> Julio
>
> On Thursday, April 30, 2020 at 7:22:07 AM UTC-4, Ste Wilson wrote:
>>
>> Wow!.  Why am I still surprised at the different shapes people hammer 
>> TiddlyWiki into? Very Zen!
>>
>

-- 
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/c416f75b-87b5-47bb-9362-ebc73dc16721%40googlegroups.com.

[tw5] Re: Minimalistic "single tiddler view" for short texts etc

[Anjar]

Hi,

Thanks for the links, the page of Nicolas Petton seems really amazing, will 
use some time to explore it!

I have updated the demo <https://ewy.no/tiddlytext.html> with an edit 
window in the siebar (having the redered story and an edit mode side by 
side feels quite intuitive) and removed the second step!


Anders  

onsdag 29. april 2020 21.13.14 UTC+2 skrev Mohammad følgende:
>
> Anjar,
>  You can use the below code for automatic page numbering!
>   https://groups.google.com/d/msg/tiddlywiki/cdtKsC9VEmc/fMT1LKxYBQAJ
>
>   To reorder slide and organize them under a tag as I said tagpil can be 
> used
>
>  As I understand your structure is like this
>
>   Topic1  (a tiddler)
> pages --> all tiddlers tagged with  topic1
>   
>   Topic2  (a tiddler)
> pages --> all tiddlers tagged with  topic2
>
>  
>

-- 
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/2c61707a-8cfb-49a7-aa48-d9ec00531511%40googlegroups.com.

[tw5] Re: Minimalistic "single tiddler view" for short texts etc

[Anjar]

Hi Mohammad, thanks for the comments!

I used dates as titles because these are unique and hidden, whereas the 
displayed title is another field (texttitle) - this was to make it possible 
to have several tiddlers with the same title. Alternatively, a header could 
have been used instead of any titles, but I think it can be useful with a 
specific field

The simplest way to edit tiddlers is to use the tiddler manager, I think, 
but it is indeed tiresome. Maybe I should put a check box to hide/show the 
edit button in the sidebar? Or even better - have the tiddler already open 
in edit mode in the sidebar?

I tried to edit the edittemplate to use the texttitle field as title, but 
couldn't figure it out. And I thought the simple form would be user 
friendly as you don't have to think about fields showing in different ways 
(the title is separated from the text which is again separated from the 
other fields). Could the solution be to continue using a custom form, but 
integrating the full editor instead of a simple text area, and then skip 
step 2?


Best,
Anders

onsdag 29. april 2020 20.31.01 UTC+2 skrev Mohammad følgende:
>
> Anjar,
>
> Few comments
>
>  Why slides are added in two steps? 1) click on + button  and then click 
> Add text 2) Now edit tiddler and save?
>   If A tiddler was saved with typos and one wishes to edit it how it is 
> possible?
>Why date is used as tiddler title?
>
> --Mohammad
>
> On Wednesday, April 29, 2020 at 9:18:40 PM UTC+4:30, Anjar wrote:
>>
>> @TiddlyTweeter: Thanks! Good point about the home button! Removed it as a 
>> tile and had the add button change to a home when relevant!
>>
>> Also, removed the page field to use the count of existing pages instead
>>
>> Best
>> Anders
>>
>> onsdag 29. april 2020 17.13.04 UTC+2 skrev TiddlyTweeter følgende:
>>>
>>> Anjar wrote:
>>>>
>>>> Have updated the site <https://ewy.no/tiddlytext.html> with a small 
>>>> add new text button to the lower right on the home page, and using an 
>>>> actual tag field to get suggestions. Next step will be to remove the 
>>>> system 
>>>> tags from the suggestion list and enhance the mobile experience by having 
>>>> responsive font size and maybe swipe previous/next using the hammer widget!
>>>>
>>>
>>> Very nice, focused, minimalism. Good presentation medium.
>>>
>>> Re the CSS for the number boxes at bottom ... I'm not sure letting them 
>>> stretch so wide is a good approach? It particularly looks odd on "Home" 
>>> button moving about. Might be better anchored left?
>>>
>>> Just thoughts. Overall Its neat! :-)
>>>
>>> Best wishes
>>> TT
>>>
>>

-- 
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/61b69690-5c22-497e-8b5b-d5bc4647530a%40googlegroups.com.

[tw5] Re: TiddlyWiki API/IFTTT help

[Anjar]

Hi Tom!

It's great that you have found tiddlywiki useful! About your question; I 
haven't tried this, but such an integration is a nice idea! How complex a 
setup would you be comfortable with? Searching this google group brings up 
some approaches; some worked 

 
on a way to use google sheets as a backend for TW, saving and loading 
tiddlers from sheets. I guess the most customizable way would be to use the 
node.js edition and have some external scripts create the .tid files 

.

Triggering actions from tiddlywiki can maybe be done using webhooks?


Best,
Anders

onsdag 29. april 2020 10.06.45 UTC+2 skrev Tom følgende:
>
> Hi All
> Just got started on using Tiddlywiki and have started to make it super 
> useful for my personal usage. 
> I am looking to make it a note-taking hub for everything and with that in 
> mind I am looking to move away from my IFTTTs of importing information from 
> Alexa lists, starred emails and spotify favourites into the likes of 
> Evernote/OneNote/Excel but instead importing the information into 
> TiddlyWiki (Tiddlywiki being the That part of IFTTT).
> I have also been using Beeminder to keep me on track with work such as 
> daily note taking and journalling with entries to an excel updating the 
> beeminder program (Tiddlywiki would the the This of IFTTT).
> If anyone can tell me how to use tiddly with IFTTT or the API in super 
> simple terms it would be appreciated.
> If I need to elaborate further let me know.
> Many Thanks
> Tom
>

-- 
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/870de42d-2ffa-44a9-ba7d-3631c085552d%40googlegroups.com.

[tw5] Re: Minimalistic "single tiddler view" for short texts etc

[Anjar]

@TiddlyTweeter: Thanks! Good point about the home button! Removed it as a 
tile and had the add button change to a home when relevant!

Also, removed the page field to use the count of existing pages instead

Best
Anders

onsdag 29. april 2020 17.13.04 UTC+2 skrev TiddlyTweeter følgende:
>
> Anjar wrote:
>>
>> Have updated the site <https://ewy.no/tiddlytext.html> with a small add 
>> new text button to the lower right on the home page, and using an actual 
>> tag field to get suggestions. Next step will be to remove the system tags 
>> from the suggestion list and enhance the mobile experience by having 
>> responsive font size and maybe swipe previous/next using the hammer widget!
>>
>
> Very nice, focused, minimalism. Good presentation medium.
>
> Re the CSS for the number boxes at bottom ... I'm not sure letting them 
> stretch so wide is a good approach? It particularly looks odd on "Home" 
> button moving about. Might be better anchored left?
>
> Just thoughts. Overall Its neat! :-)
>
> Best wishes
> TT
>

-- 
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/5458052c-ab5b-4d48-b387-1c785bc4244e%40googlegroups.com.

[tw5] Re: Minimalistic "single tiddler view" for short texts etc

[Anjar]

Have updated the site <https://ewy.no/tiddlytext.html> with a small add new 
text button to the lower right on the home page, and using an actual tag 
field to get suggestions. Next step will be to remove the system tags from 
the suggestion list and enhance the mobile experience by having responsive 
font size and maybe swipe previous/next using the hammer widget!

@Riz: Thanks, that was a nice explanation, and the fix is perfect

@Mohammad: Thanks for the encouragement. I had a look at them and felt they 
were a bit complex

@Tony: Thanks for the suggestion. Yeah, it is a bit cumbersome. Made 
another button to reset a field


Best,
Anders


tirsdag 28. april 2020 09.09.17 UTC+2 skrev Riz følgende:
>
> Hi Anjar
> Checked out your site. That is a really cool. 
>
> The bug regarding undefined tiddler opening. The problem is 
> "tm-close-other-tiddlers". This is basically telling tiddlywiki to "close 
> all other tiddlers in the storylist" but me. In turn tiddlywiki asks - who 
> is this "me"? Your tiddler replies with "$:/FooterTiddler". Now tiddlywiki 
> has a dilemma. SInce FooterTiddler is a pagetemplate, it is not present in 
> the storylist. But the message said close all but me in the storylist. 
>
> A corrected button for you is
>
> <$button class="tc-btn-invisible tc-tiddlylink">
> <$action-setfield $tiddler="$:/StoryList" list="" />
> <$action-navigate $to="Home" />
> <$action-setfield $tiddler="$:/FooterTiddler" opentag="" />
> 
> Home
> 
> 
>
> Which clears the storylist aka closes all tiddlers.
>

-- 
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/c370f745-49e6-4f1f-ae5c-898092dfd8f0%40googlegroups.com.

[tw5] Minimalistic "single tiddler view" for short texts etc

[Anjar]

Hi all,

After Jerome made me aware of the nice introductory page 
https://tiddlywiki.com/prerelease/editions/introduction/ I tweaked it a bit 
with the intention to show short texts such as poems, but I guess other 
media would work as well. Demo: https://ewy.no/tiddlytext.html

There is a Add text form in the sidebar. You can have duplicated titles. 
The page field is used for the navigation bar at the bottom and the 
next-buttons. The footer is scrollable on small screens, but the active 
grid box may be out of sight. Is it possible to "bring it back" into focus 
using css?

However, there is an annoying bug: When hitting the Home in the footer, two 
tiddlers open: the Home and undefined. Does anyone know why that happens? 
The link is made by

<$button class="tc-btn-invisible tc-tiddlylink">
<$action-sendmessage $message="tm-close-other-tiddlers" />
<$action-navigate $to="Home" />
<$action-setfield $tiddler="$:/FooterTiddler" opentag="" />

Home



where the opentag field in $:/FooterTiddler holds the opened collection 
name, and Home is the home 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 view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/e33d4e6d-002b-4f52-b181-3cc0429c80cc%40googlegroups.com.

[tw5] Re: [Use case] TiddlyWiki as exam database

[Anjar]

An exciting thought, Tony! This specific example is more of a static 
database with exercises otherwise provided as plain PDFs, without tags or 
the possibility to hide the answers

I have contemplated about making some sort of "generator" in tiddlywiki to 
practise and meorising normal ranges and scoring systems; i. e. a template 
where sort of-random numbers are filled in and you provide a score or 
checks which are abnormal. Not exactly what you describe, but those kinds 
of things need a lot of practise, and I can imagine tiddlywiki as a 
suitable framework.


Best,
Anders

mandag 27. april 2020 06.03.22 UTC+2 skrev TonyM følgende:
>
> Anjar,
>
> Your welcome. Keep in mind tiddlywiki would also be good at adaptive tests 
> where a tests questions alters according to the answers given. An area of 
> weakness would have more questions, and students thus learn more.
>
> Regards
> Tony
>
> On Monday, April 27, 2020 at 1:22:44 PM UTC+10, Anjar wrote:
>>
>> Thanks, Tony, will fix! I think the supporting and engaged community 
>> (such as your help right now) is one of the biggest strengths of tiddlywiki!
>>
>> Anders
>>
>> mandag 27. april 2020 03.00.45 UTC+2 skrev TonyM følgende:
>>>
>>> Anjar,
>>>
>>> Thanks for Sharing. My full appreciation is limited by the fact I only 
>>> speak english. But it looks good.
>>>
>>> *I Little Suggestion to try;*
>>> Control Panel > Appearance > SideBar Layout set to *Fluid Story, Fixed 
>>> SideBar*
>>> Control Panel > Appearance > SideBar Width (At the bottom) set to 
>>> *600px*.
>>>
>>> *Now desktop users have even better use of their screen space.*
>>>
>>> Regards
>>> Tony
>>>
>>> On Monday, April 27, 2020 at 8:12:09 AM UTC+10, Anjar wrote:
>>>>
>>>> Hi all,
>>>>
>>>> I just wanted to share an example of using TiddlyWiki as a database for 
>>>> exam essays: http://ununderstandable.com It is pretty basic (but still 
>>>> a bit pretty, I think;))
>>>>
>>>> The table in the sidebar allows you to click on a subject, a year, or 
>>>> the intersection between them to open the corresponding exercises. Answers 
>>>> and guidelines for scoring are hidden by default, but can be shown either 
>>>> by hitting the unfold all button in the sidebar or on the subtitles. I 
>>>> thought many would like to have the exercises on paper, so I modified the 
>>>> printing stylesheet a bit.
>>>>
>>>> There is also a form for adding new exercises in the sidebar.
>>>>
>>>

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/9338559d-0447-4fec-bcfc-eb7dd889ac3b%40googlegroups.com.

[tw5] Re: Consider renaming TiddlyWiki

[Anjar]

Hi,

I couldn't see it being suggested, but a temporary solution may be to use a 
another shortform than TW(5); say "Tidwi" as in *Tid*dly*Wi*ki for example; 
when reaching out; it may be less charged (importnt for the first 
impression) and we can still link it to all existing ressources by 
specifying that "TiddlyWiki (short: Tidwi) is blablabla" and so on

Best,
Anders

mandag 2. mars 2020 14.08.23 UTC+1 skrev bimlas følgende:
>
> Continuation of the 
> https://groups.google.com/forum/#!topic/tiddlywiki/MKVwkEmCimQ thread.
>
> In a nutshell: TiddlyWiki is gaining popularity because it appears in more 
> articles and podcasts, but most of the time they smile at its name, so it 
> doesn't seem to be taken seriously (although at the end of the test they 
> usually praise the software itself). The name TiddlyWiki may hinder its 
> distribution, so we should consider renaming 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 view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/8f78db9f-60c9-438a-a73e-4f9b1dd54d2e%40googlegroups.com.

Re: [tw5] Redesign of TiddlyWiki

[Anjar]

Wow @Jeremy, it is the first time I see the 
https://tiddlywiki.com/editions/introduction/ 
;
 
hide furniture is really nice; do you know if there is any versions 
compatible with newer tiddlywiki versions? Tried to use it for some poems 
with fade instead of zoom and a sticky footer; https://ewy.no/Joakim.html; 
but the page was quite heavy (> 7 mb!) (sorry for being offtopic)

Best,
Anders

lørdag 25. april 2020 14.19.06 UTC+2 skrev Jeremy Ruston følgende:
>
> Hi Edgaras
>
> Welcome, your offer is much appreciated. I liked the work in  TW revamp 
> v0.01 
> 
>  and 
> look forward to you exploring your vision further. Your thoughts on 
> progressively revealing complexity are particularly interesting.
>
> As others have pointed out, it’s likely to be less constraining to aim for 
> an alternate theme rather than replacing the current default “Snow 
> White”/“Vanilla” theme. TiddlyWiki themes are switchable so users can 
> choose the theme that is best suited for a particular activity or audience, 
> so it isn’t necessary to duplicate all of the functionality available in 
> the default theme.
>
> Having said that, the default theme can’t entirely go away for reasons of 
> backwards compatibility, and so any ideas for improving it would be 
> welcome. It’s a much less enticing brief because of the complexities 
> involved in that need for backwards compatibility, but it could make a big 
> impact.
>
>
>1. The navigation when clicking links. Do you find it useful that 
>tiddles are opening as a vertical stack? I find it kind of confusing, and 
>not really helpful when you have increasingly large stack. I would like to 
>explore alternative interactions:
>- Swapping the tiddle with a new one, but keeping the breadcrumbs on 
>   top (if possible?) and giving < and > navigation, back and forward in 
> time 
>   where you've been.
>   - Stacking tiddle when opening into tabs, so you can switch then by 
>   clicking or keyboard shortcut.
>
> TiddlyWiki uses the term “storyview” to refer to the way that tiddlers are 
> displayed and navigated. The default linear sequence of tiddlers is called 
> “classic”. The core also ships with “zoomin” and “pop”. Zoomin displays a 
> single tiddler at a time with a transition animation as links are clicked 
> (see https://tiddlywiki.com/editions/introduction/ for an example). “Pop” 
> is the same as “classic” but with a different transition animation.
>
> Additional storyviews are available via plugins. For example, the official 
> library includes a “stacked” storyview that displays tiddlers as a 
> perspective stack of cards (see illustration below).
>
> None of that is to invalidate your ideas, more to show that this is an 
> area where there are a lot of possibilities that we have yet to explore, 
> and that we have a framework that simplifies that exploration.
>
>
>1. Editing mode. How can we make the editing more fluent with viewing. 
>It distances you from just writing if you have to click edit and save 
>everytime. You should be able to navigate text with keyboard or just click 
>anywhere in text right away and start editing. Saving should happen 
>automatically (to local storage). All the text-type formatting could be 
>hidden, unless it's relevant for the selected word or sentence. This will 
>reduce visual clutter. Check the simplicity of text editing in *Typora* 
>!
>
> The difference between editing and view mode is hard to hide away. In 
> TiddlyWiki we have very dynamic markup (like transclusions) where there has 
> to be a way to switch between editing/viewing the markup and its results.
>
> In my work for clients I have developed a WYSIWYG editor for TiddlyWiki 
> but it’s really only suitable for very limited use cases, where users are 
> only typing regular text and formatting, and not using any dynamic markup. 
> It’s based on Quill.js which seems to be popular but I find it very clunky 
> to use, particularly making links. One of the goals of TiddlyWiki is to 
> make linking be part of the punctuation of writing.
>
> You are not the first to mention that saving should happen automatically 
> to local storage. We’ve had much discussion about that here and it’s proved 
> more controversial than I would have expected, but the fact is that local 
> storage is treated like a purgeable cache by browsers, and cannot be 
> trusted to retain valuable user data.
>
> Anyhow, not to be pessimistic, I think there’s a lot we could do to 
> improve the editing experience, but I don’t think there’s a whole lot of 
> low hanging fruit without significant development within the core. The 
> simple goal of being able to click 

[tw5] Re: [Use case] TiddlyWiki as exam database

[Anjar]

Thanks, Tony, will fix! I think the supporting and engaged community (such 
as your help right now) is one of the biggest strengths of tiddlywiki!

Anders

mandag 27. april 2020 03.00.45 UTC+2 skrev TonyM følgende:
>
> Anjar,
>
> Thanks for Sharing. My full appreciation is limited by the fact I only 
> speak english. But it looks good.
>
> *I Little Suggestion to try;*
> Control Panel > Appearance > SideBar Layout set to *Fluid Story, Fixed 
> SideBar*
> Control Panel > Appearance > SideBar Width (At the bottom) set to *600px*.
>
> *Now desktop users have even better use of their screen space.*
>
> Regards
> Tony
>
> On Monday, April 27, 2020 at 8:12:09 AM UTC+10, Anjar wrote:
>>
>> Hi all,
>>
>> I just wanted to share an example of using TiddlyWiki as a database for 
>> exam essays: http://ununderstandable.com It is pretty basic (but still a 
>> bit pretty, I think;))
>>
>> The table in the sidebar allows you to click on a subject, a year, or the 
>> intersection between them to open the corresponding exercises. Answers and 
>> guidelines for scoring are hidden by default, but can be shown either by 
>> hitting the unfold all button in the sidebar or on the subtitles. I thought 
>> many would like to have the exercises on paper, so I modified the printing 
>> stylesheet a bit.
>>
>> There is also a form for adding new exercises in the sidebar.
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/fa230f7d-b997-4037-9dc4-821815f27acb%40googlegroups.com.