date:20200913

Folks,

Inspired elsewhere, I had this idea, and wonder if some of you are familiar 
with techniques that may help build a  "Tiddler title generator"

   - Has anyone worked out a way to use heuristics from the text in a 
   tiddler, to come up with a *caption or title *that reflects the content?
   - If we could generate suggested unique titles from the content and 
   other values that would be Fab
   - Users could modify the suggestion before committing
   - It would reduce the cognitive load when capturing pieces of data in 
   tiddlers.

For example perhaps the tiddler or its parents has particular tags, 
keywords or categories perhaps we could some how find larger words in the 
text and combine them to generate a possible name for a child tiddler?

This could be boosted by allowing the tiddler author to highlight words 
within the text that are representative of the tiddler and as a result may 
be of use in a title.


   - A Popup could provide half a dozen possible titles and you can click 
   one or enter the final title.
   - Some would be simple like "parent tiddler + N", 
   - others could be "child of parent tiddler N" or A
   - Yet smarter ones may suggest "Parent (keywords)"
   - or other heuristically sources values


Advanced

   - In the title selection dialogue we could also add features to prompt 
   the user to provide relevant tags categories or keywords.
   - In effect supporting the author of a tiddler to make use of standard 
   or existing methods based on what the know about the information at time of 
   creation.


Regards
Tony

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

[tw5] Re: [Tiddly Research] Public release

Kebi,

Lovely work. I Notice at the bottom 
of https://kebifurai.github.io/TiddlyResearch/#Tiddly%20Research

The Streams tiddlers are listed.

   - Did you know if you give those tiddlers "caption"s, they will display 
   the caption not the convoluted number?

This has inspired me to ask,

   - Has anyone worked out a way to use heuristics from the text in a 
   tiddler, to come up with a caption or title that reflects the content?
   - If we could generate suggested unique titles from the content that 
   would be Fab

Regards
Tony

On Monday, 14 September 2020 12:47:58 UTC+10, kebi wrote:
>
> *New v1.2 update!* https://github.com/kebifurai/TiddlyResearch/releases
>
>
> How to update from v1.1:
>
>- Open your current wiki
>- Click on the "Export all" button situated on the topbar and export 
>all your tiddlers in JSON format
>- Download the new version and open it
>- Import all your tiddlers by drag and dropping the file generated 
>from step n.2
>
> Changelog:
>
>- Fixed major glitch in tiddlyresearch-reference plugin
>- tiddlyresearch-reference now uses better filters
>- Added a new level of referencing "transclusions"
>- You can now transclude entire tiddlers and its nodes
>- Added breadcrumbs in the preview viewTemplate
>- The default search filter now ignores images text body (to avoid 
>freezes)
>- New color for external links (green)
>- Added a new macro "current-time"
>- ContextPlugin now supports asian languages
>- Changed the default tiddler tags to ".tiddler" and ".daily-tiddler" 
>(to avoid overwriting them)
>- Fixed CSS styling to solve some Krystal/Notebook theme glitches
>- Plugin re-organization and code clean-up
>- Added Tutorial GIFs
>
>

-- 
You received this message because you are subscribed to the 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/2c2959b3-43cc-4b12-b4c5-6bfd3767f64eo%40googlegroups.com.

[tw5] Re: New TiddlyTools time feature: "inline EditDate control"

Eric,

Once again thanks for taking this to a complete solution.

I found a method to create a very simple date picker  attached, that 
returns a tiddlywiki serial number date, drop it on a wiki and put the 
following in a tiddler
simple-date: <>
<>
<>
Start-date: <>

Its not finished but I think you will like the mechanism I am making use of 
\define select-date(fieldname)
<$set name=date-field value="$fieldname$" emptyValue="date-field">
<$edit-text tiddler="$:/temp/date" type=date tag="input" /> 
<$list filter="[{$:/temp/date}!is[blank]]" variable=nul>
   <$button tooltip={{{ [[$fieldname$]addprefix[Set ]addsuffix[ to selected 
date]] }}} actions=<> >
  <$list filter="[all[current]has]" emptyMessage="Set" 
variable=nul>Reset
 


\end
Using the 

   - type=date tag="input" on the edit-text widget
   - Saving the the result to a temp field
  - I need to make this temp tiddler qualified by the fieldname, to 
  stop simultaneous popups
   - Converting the temp field to tiddlywiki date serial (Noon used)

Similar options may exist for time

I expect I will publish this for users not buying into your full date 
solution, to simply improve date picking.

Question

   - It requires a set button, have you another way to trigger the actions, 
   after selecting a date in the popup I can use?


*But I will add your, facility is very usable.*

Dreaming

   - I wonder if there is any javascript that allows one to set a time by 
   dragging the hands on a clock, or on a list like google calendars?

*Love you work, really, really.*

Regards
Tones


On Monday, 14 September 2020 13:14:03 UTC+10, Eric Shulman wrote:
>
> http://tiddlytools.com/timer.html#TiddlyTools%2FTimer%2FEditDate
>
> Introduction
>
> The edit-date macro provides a user interface that combines the features 
> of a text input (<$edit-text> widget) with "edit-in-place" 
> (save/cancel/delete) buttons and a popup monthly calendar. This allows you 
> to enter custom text or select and format a date from the calendar.
>
> Parameters
>
> The macro supports a subset of the parameters allowed by the <$edit-text>
>  widget:
> Parameter Description
> tiddler The tiddler in which to save the input (default=<>
> )
> field The field in which to save the input (default=date)
> format The TiddlyWiki Date Format  used 
> to store a date selected from the calendar (default=/0MM/0DD)
> default text to be used when the target field doesn't exist
> placeholder text to display when the target field is empty 
> (default="select or enter a date")
> size The size of the input field in characters (default=20)
> focus Set to "yes" or "true" to automatically focus the input after 
> creation
> class A CSS class to be assigned to the generated HTML editing element
>
> Notes
>
>
>- Use <> to embed a date input field in 
>tiddler content.
>- Unlike the <$edit-text> widget, the <> macro allows you 
>to input values that are stored in the current tiddler.
>- When the field receives the input focus, a set of "edit-in-place" 
>buttons and a monthly calendar are displayed.
>
>
>- [checkmark] saves changes to the field value. [X] cancels changes to 
>the field value. [trashcan] deletes the field value.
>
>
>- [<<] displays the previous month. [>>] displays the next month.
>
>
>- Click a date to set the edit field contents using the indicated 
> TiddlyWiki 
>Date Format codes .
>- You can override the default date format (/0MM/0DD) by entering 
>a new format directly in the calendar popup.
>- Note: if TiddlyTools/Timer/Calendar 
> is 
>not installed, the calendar popup is not displayed.
>
>
> 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/f4d60483-505b-4267-bec7-9356f2cd5cc8o%40googlegroups.com.


date-tools.json
Description: application/json

[tw5] Re: Question about Refrences and Macros

Luke,

As I understand it when a link is inside a define it becomes a macro and 
thus is not considered a link, the macro is "interpreted" then rendered and 
the result could be anything. I think this is why, perhaps by design, such 
links do not appear. Macros are also often defined elsewhere and 
tagged $:/tags/Macro, and perhaps you do not want those tiddlers listed.

However if you tag a tiddler containing the following with $:/
tags/ViewTemplate
<$list filter="[all[current]list[text]]">

You will see the reference is detected, only if the macro is actually used.

Of course we can also write a solution that searches all tiddlers and and 
finds in the string is in the text (including in a macro definition)
<$list filter="[all[tiddlers]contains:text[HelloThere]]">

The advantage being it finds items with or without the Square braces, eg 
camel case
But may bring up other hits?

However if you use a carefully crafted a search you can always find all 
such links in or outside the define statements, after all all you want is 
to list tiddlers containing "[[searchvalue]]"

There are tricks available to concatenate a search string with characters 
that are illegal in filters or wikitext.

Regards
Tony

On Monday, 14 September 2020 06:15:30 UTC+10, Huntsfromshadow wrote:
>
> Question about Reference List and Macros.
>
> I have the following Setup.
>
> 1 - Tiddler 1 that has some random Text.
> 2 - Tiddler 2 that has [[Tiddler 1]] in it.
>
> Tiddler 1 shows that Tiddler 2 refrences it (and thus isn't on the Orphan 
> list).
>
> If I replace the text in Tiddler 2 with
> \define testme()
> [[Tiddler 1]]
> \end
>
> <>
>
> Tiddler 1 doesn't show any refrences to it (and thus is in the Orphan 
> List).
>
>
> Is this expected? Anyway to have the macro still report as a refrence?
>
> Thanks
> -Luke
>
>

-- 
You received this message because you are subscribed to the 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/08f07463-a6ed-4b91-8b58-8e4175707ccfo%40googlegroups.com.

[tw5] New TiddlyTools time feature: "inline EditDate control"

2020-09-13 Thread Eric Shulman

http://tiddlytools.com/timer.html#TiddlyTools%2FTimer%2FEditDate

Introduction

The edit-date macro provides a user interface that combines the features of 
a text input (<$edit-text> widget) with "edit-in-place" 
(save/cancel/delete) buttons and a popup monthly calendar. This allows you 
to enter custom text or select and format a date from the calendar.

Parameters

The macro supports a subset of the parameters allowed by the <$edit-text>
 widget:
Parameter Description
tiddler The tiddler in which to save the input (default=<>)
field The field in which to save the input (default=date)
format The TiddlyWiki Date Format  used 
to store a date selected from the calendar (default=/0MM/0DD)
default text to be used when the target field doesn't exist
placeholder text to display when the target field is empty (default="select 
or enter a date")
size The size of the input field in characters (default=20)
focus Set to "yes" or "true" to automatically focus the input after creation
class A CSS class to be assigned to the generated HTML editing element

Notes


   - Use <> to embed a date input field in 
   tiddler content.
   - Unlike the <$edit-text> widget, the <> macro allows you to 
   input values that are stored in the current tiddler.
   - When the field receives the input focus, a set of "edit-in-place" 
   buttons and a monthly calendar are displayed.


   - [checkmark] saves changes to the field value. [X] cancels changes to 
   the field value. [trashcan] deletes the field value.


   - [<<] displays the previous month. [>>] displays the next month.


   - Click a date to set the edit field contents using the indicated TiddlyWiki 
   Date Format codes .
   - You can override the default date format (/0MM/0DD) by entering a 
   new format directly in the calendar popup.
   - Note: if TiddlyTools/Timer/Calendar 
    is 
   not installed, the calendar popup is not displayed.


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/f2f9d9ed-da1a-4f1a-ad4b-192b1da682d9o%40googlegroups.com.

[tw5] Re: [Tiddly Research] Public release

2020-09-13 Thread kebi

 

*New v1.2 update!* https://github.com/kebifurai/TiddlyResearch/releases


How to update from v1.1:

   - Open your current wiki
   - Click on the "Export all" button situated on the topbar and export all 
   your tiddlers in JSON format
   - Download the new version and open it
   - Import all your tiddlers by drag and dropping the file generated from 
   step n.2

Changelog:

   - Fixed major glitch in tiddlyresearch-reference plugin
   - tiddlyresearch-reference now uses better filters
   - Added a new level of referencing "transclusions"
   - You can now transclude entire tiddlers and its nodes
   - Added breadcrumbs in the preview viewTemplate
   - The default search filter now ignores images text body (to avoid 
   freezes)
   - New color for external links (green)
   - Added a new macro "current-time"
   - ContextPlugin now supports asian languages
   - Changed the default tiddler tags to ".tiddler" and ".daily-tiddler" 
   (to avoid overwriting them)
   - Fixed CSS styling to solve some Krystal/Notebook theme glitches
   - Plugin re-organization and code clean-up
   - Added Tutorial GIFs

-- 
You received this message because you are subscribed to the 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/901f234f-7857-4d32-9865-bf311d1ea2aco%40googlegroups.com.

[tw5] Re: A TiddlyWiki "TODO organization/reminder" approach

Charlie,

Thanks for sharing. It is a somewhat novel approach. 

With a lot of focus recently on references and back-links we are seeing 
people make use of these a lot.

Sharing such code patterns are really good for the community, thanks.

Tones

On Monday, 14 September 2020 09:13:45 UTC+10, Charlie Veniot wrote:
>
> G’day,
>
> I needed a way to remind myself of “TODO” tasks in regards to my 
> dual-purpose “Product Reviews” and “Urban Off Gridding for Laypersons” 
> TiddlyWiki 
> 
> .
>
> My approach:
>
>- 
>
>In whatever tiddler requiring something I need to do, I add (in the 
>text of the tiddler) a [[TODO]] link along with notes related to the thing 
>I need to do
>- 
>
>When I’ve completed the thing I needed to do, I just edit the tiddler 
>and get rid of the [[TODO]] link and the related notes.
>- 
>   
>   I don’t need a “record” of the thing being done
>   - 
>
>To remind me of what I need to do …
>- 
>   
>   The sidebar displays a fairly noticeable TODO section (a “TODO” 
>   DetailsWidget containing the list of tiddlers that have [[TODO]] links)
>   - 
>   
>   When there are no tiddlers referencing [[TODO]], then the sidebar's 
>   TODO section "disappears" *(reappearing next time a [[TODO]] link 
>   gets created in some tiddler)*
>   
>
> Please find below 5 screenshots of related things to look for in my 
> TiddlyWiki 
> 
> .
>
> Cheers !
>
>
> TODO section in the sidebar (collapsed)
>
> [image: TheTodoInTheSidebarCollapsed.png]
>
>
>
> TODO section in the sidebar (expanded)
>
> [image: TheTodoInTheSidebarExpanded.png]
>
>
>
> The filter that creates the TODO section if there are any TODO’s
>
> [image: CustomTiddlywikiTitleTop.png]
>
>
>
> The TODO tiddler
>
> [image: TheTodoTiddler.png]
>
>
>
> A sample TODO (TODO reference and related notes)
>
> [image: TodoReference.png]
>
>
>
>
>

-- 
You received this message because you are subscribed to the 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/74bbc00a-befc-419d-be1d-b3f017ccbc6fo%40googlegroups.com.

Re: [tw5] Re: a transclusion inconcistency

Bob,

When reading the documentation on tiddlywiki.com the intention is for the 
content to be displayed in the view template.

Editing the tiddler exposed the documentation macros 

<<.operator-example 1 "[[23]add[19]]">>

This is calling the .operator-example and is not itself documented for the 
reader.

As a community we are always looking for help enhancing the documentation, 
but a lot of members have documented a lot elsewhere. It is quite easy to 
submit simple documentation updates on tiddlywiki.com if you have a github 
account.

As for filters the information is all there, technically, and yes not in 
one place, but the application and extensibility means further 
documentation is necessary to empower users. There are many resources 
around. Most recent is some of Mohammad's work, look for his library of 
plugins, the first port of call is possibly the community links on 
tiddlywiki.com and Davids TiddlyWiki Toolmap  


Yes, we have a distance to go, but fast innovation can cause a drag in 
documentation.

Regards
Tony

On Monday, 14 September 2020 11:54:09 UTC+10, Dr. Bob Jansen wrote:
>
> Eric, 
>
> thanks for your reply and it does make sense. However, as an old-timer 
> XML guy, leaving out the close tags is 'difficult'. Also it makes for an 
> exception and I abhore exceptions to markups cause experience shows 
> exceptions breed exceptions which in turn breed 
>
> A final comment, the documentation of TiddlyWiki is all over the place. 
> As a newbie, I find it difficult to find answers to my issues. The 
> examples don't always make sense especially those that are coded to a 
> macro, like <<.operator-example 1 "[[23]add[19]]">> in the Add Examples 
> tiddler. This does not help me work out the syntax or use of an item. 
> The writer assumes the reader is familiar with things and is looking for 
> a refresh. Where does one look for the .operator-example tiddler, search 
> doesn't find it? 
>
> This is especially true for documentation about filters. From what I 
> have gleaned so far, filters are the concept that makes things work and 
> as such an important central concept that I would expect similarly sized 
> and detailed documentation with lots and lots of examples. 
>
> I am not trying to be negative but positive, for future newbies 
>
> bobj 
>
> -- 
>  
> Dr Bob Jansen 
> 122 Cameron St, Rockdale NSW 2216, Australia 
> Ph (Korea): +82 10-4494-0328 
> Ph (Australia) +61 414 297 448 
> Resume: http://au.linkedin.com/in/bobjan 
> Skype: bobjtls 
> KakaoTalk: bobjtls 
> http://cultconv.com 
>
> In line with the Australian anti-spam legislation, if you wish to receive 
> no further email from me, please send me an email with the subject "No 
> Spam" 
>
>

-- 
You received this message because you are subscribed to the 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/b5a9d166-536c-4c7d-8edf-913fc33bfd76o%40googlegroups.com.

[tw5] Re: How To: altering TiddlyWiki appearance based on context (URL parameters at StartUp, and via radio buttons after StartUp)

Seeing how I may should eventually remember that sleeping at night is a 
thing a short answer for now, but I will return with a longer answer and 
possible examples later.

The solution was mostly to keep it within the current framework and not 
changing too much around. For a more centralised approach to the whole 
system tags and or fields will probably get a more prominent role, both for 
minimizing code duplication as well as dropping a reliance on titles.
For instance the Content and Title tiddler could call the same macro with 
their type - content and title respectively in this case - and the macro 
filters for a tiddler with two fields: one named tiddler-type matching what 
was send to the macro and the other named context matching the context 
currently in your purpose field. Since this match is made via the two 
fields the title also doesn't matter. This tiddler or more correctly its 
title is returned to the tiddler which then transcludes the result.

I will write a more concrete example when my brain isn't on standby but 
actually working again, but I hope that this may give you some idea already.

On Monday, 14 September 2020 02:58:31 UTC+2, Charlie Veniot wrote:
>
> That looks A-1 to do on one tiddler needing to decide what content to show 
> based on context, but how to do that once so that it can be used for a 
> plethora of tiddlers that show different content based on context?
>
> I would not want to put that kind of code on each of my 
> multi-context-handling tiddlers.
>
> For that code to exist generically once, I imagine each 
> multi-context-tiddler would need some kind of macro call like:  
> < Tiddler Name">>
>
> Aside from not doing that myself (for lack of macro and filter knowledge), 
> I didn't want to go there because I often get tripped up setting these 
> things up to not get screwed up every time I change tiddler titles (which I 
> do repeatedly trying to get titles juust right.)
>
> Thoughts?  (i.e. how to do that so that both "Contents" tiddler and 
> "Title" tiddler can call some macro that does what your code does, but 
> works generically for every tiddler that needs it?)
>
> On Sunday, September 13, 2020 at 9:22:13 PM UTC-3, Felicia Crow wrote:
>>
>> Charlie,
>>
>> so first things first here is my version. This specific code would go 
>> into Content, but it would look nearly the same with the other tiddlers. 
>>
>
>> <$set name="purpose" filter="[[Alternate TiddlyWiki 
>> Purposes]get[purpose]]">
>> <$list filter="[match[ProductReviews]]">
>> {{Contents (Product Reviews)}}
>> 
>> <$list filter="[match[OffGridding]]">
>> {{Contents (Urban Off Gridding)}}
>> 
>> 
>>
>> As for the explanation:
>>
>>- The filter within set gets the current value of the purpose field 
>>that is in the tiddler with the title Alternate TiddlyWiki Purposes.
>>- The filter in the list widget takes whatever was saved in set and 
>>compares it to the parameter in match. If it matches the list widgets 
>>content will be rendered.
>>
>>
>> The code in itself does pretty much the same as your two transclusion 
>> templates just in one place, so I think it mostly comes down to personal 
>> preference where you check what actually needs to be rendered.
>>
>> The only thing I could think of what this solution currently does better 
>> is being more failsafe in its execusion. The way the transclusion tiddlers 
>> in your version are written they only look for fields named purpose which 
>> contains their respective value, so when one adds a field purpose to 
>> another tiddler and gives it the opposite value both versions will be 
>> rendered at the same time. Since this is a wiki only edited by you this 
>> probably won't happen, just realized it when I looked once more at your 
>> templates while I wrote down my version.
>>
>> Felicia
>>
>>
>> On Monday, 14 September 2020 01:23:18 UTC+2, Charlie Veniot wrote:
>>>
>>> G'day Felicia,
>>>
>>> Sure, I'd love to see how you'd go about it.  
>>>
>>> Since there are always multiple ways of doing things, if you have the 
>>> time: quick thoughts on advantages/disadvantages of both for a quick back 
>>> and forth about them?  Might be a pretty short back and forth: I don't have 
>>> enough know-how to pickout the "pitfalls" (or "trappings") of various 
>>> approaches?
>>>
>>> That aside: I'm kind of proud to have figured out a little something 
>>> about filters in my last post 
>>> .
>>>
>>> On Sunday, September 13, 2020 at 6:03:04 PM UTC-3, Felicia Crow wrote:

 Hi Charlie,

 yes that was what I meant. I always find it interesting to learn the 
 thought process behind someones solution, since it often gives a different 
 perspective on things that I would not have considered before, leads to 
 learning something new or both. So when I saw a solution I would not have 
 thought of myself I was curious how this came to be.

 I sadly don't

Re: [tw5] Re: a transclusion inconcistency

2020-09-13 Thread Dr. Bob Jansen

Eric,

thanks for your reply and it does make sense. However, as an old-timer
XML guy, leaving out the close tags is 'difficult'. Also it makes for an
exception and I abhore exceptions to markups cause experience shows
exceptions breed exceptions which in turn breed

A final comment, the documentation of TiddlyWiki is all over the place.
As a newbie, I find it difficult to find answers to my issues. The
examples don't always make sense especially those that are coded to a
macro, like <<.operator-example 1 "[[23]add[19]]">> in the Add Examples
tiddler. This does not help me work out the syntax or use of an item.
The writer assumes the reader is familiar with things and is looking for
a refresh. Where does one look for the .operator-example tiddler, search
doesn't find it?

This is especially true for documentation about filters. From what I
have gleaned so far, filters are the concept that makes things work and
as such an important central concept that I would expect similarly sized
and detailed documentation with lots and lots of examples.

I am not trying to be negative but positive, for future newbies

bobj

Dr Bob Jansen
122 Cameron St, Rockdale NSW 2216, Australia
Ph (Korea): +82 10-4494-0328
Ph (Australia) +61 414 297 448
Resume: http://au.linkedin.com/in/bobjan
Skype: bobjtls
KakaoTalk: bobjtls
http://cultconv.com

In line with the Australian anti-spam legislation, if you wish to receive no further
email from me, please send me an email with the subject "No Spam"

--
You received this message because you are subscribed to the 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/beef734d-7e7c-88dc-a875-dd89908562e5%40gmail.com.

[tw5] Re: Proof of Concept: Dynamic Global Variables

Mat et al

Just to clarify where this came from first, then I will explain why.

First, Felicia, thanks so much for this, I was confident yu would work on 
this and happy to wait, in part because I think you say the gap yourself. I 
will review and reply in more detail soon.

For the last few years I have committed to tiddlywiki as a platform I 
intend to publish in, provide solutions and use as a business tool, as well 
as the joy of a collaborative community. As was the case earlier in my life 
when I aim to become expert in something, it takes time, because of the way 
I learn, very conceptually, concise and complete but via creative 
exploration, but once I know something well, it is usually very deeply. 
Apart from my working life in IT this has included, MS-DOS, Windows, Basic, 
Cobol, Evolution, Climate Change, Photography, WebSite Development, 
Sustainability and now tiddlywiki. 

Because I consider TiddlyWiki a platform and a future backbone to much of 
what I do, and being a frustrated app developer, my focus on tiddlywiki is 
pushing its limits, finding its flaws, identifying its gaps. With a deep 
understanding of procedural languages there is a class of things I would 
like to do (no doubt others) in tiddlywiki that it can't. Every month or so 
we the community tend to break another barrier expanding tiddlywikis 
possibilities down many paths. Off line I have the result of thousands of 
hours of development and exploration, documentation etc...  mostly which I 
currently share via the forum as needed.

Now perhaps this explains why I am sometimes a pain in the neck to some of 
my tiddlywiki colleagues, I am always looking to identify gaps and fill 
them. Thanks to many we continue to do so. Some very exciting stuff is 
about to come from work with Mario, as is often the case, but this time I 
has a role.

*The following is from a programmers perspective*
The specific Gap Felicia has worked to resolve is one I identified early, 
and I now have some workarounds, this "problem" means you can NOT count (or 
accumulate) a number of different things, using a number of widgets or 
accumulate over time without having a trigger, like a button to commit it 
to storage, in a tiddler or field. Each time you *define a variable* it in 
effect becomes a new variable in the current context. That is within 
tiddlywiki variables are fleeting definitions, although they must always be 
defined (eg: macro, set vars), so they they are always redefined. That is 
variables in tiddlywiki do not behave like variables in most programming 
languages, especially when you try and make them global, accessible outside 
one tiddler or loop etc.. and yet be able to be saved without a trigger. 

   - global variables are possible, but they are "static global variables" 
   without a trigger to commit them.
   - If you are forced to commit them with an action you force the user to 
   know what they are doing.

This kind of thing is strait forward in any computer language, including 
javascript but it has not being "surfaced" until now in tiddlywiki.

I am very excited about Felicia's work.

Feel free to question, further, even challenge my assumptions, it all about 
learning and developing tiddlywiki.

Regards Tony/TW Tones

On Monday, 14 September 2020 05:32:33 UTC+10, Mat wrote:
>
> @Felicia
>
> Thank you for this! I can believe it will be useful ... but I'm wondering 
> why I didn't need it thus far. Are there cases that usually can't be 
> accomplished, or with much difficulty, that your creation solves better? 
> (Maybe I should ask Tony) I also imagine it's one of those things that were 
> at one time, early on, decided against for some secuity reasons - anybody 
> knows?
>
>
> <:-)
>

-- 
You received this message because you are subscribed to the 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/54d5dd44-0844-4d03-81f8-9dd63ace0177o%40googlegroups.com.

Re: [tw5] Re: a transclusion inconcistency

2020-09-13 Thread Eric Shulman

On Sunday, September 13, 2020 at 5:12:06 PM UTC-7, Bob Jansen wrote:
>
> Eric & Tones,
> I do not know how to close the wikify tags as Tones has recommended. I 
> have two tags as there are two variables I need.
>
> Code:
> <$wikify name="theuniqueid" text={{$:/TLS/uniqueid}}>
> <$wikify name="theartworkurl" text={{$:/TLS/artworkurl}}>
> ...
>
If I add  as the last line of the code then the display 
> of the tiddler changes to
>
Add New artwork 
>

You've left out the "$" in the close widget!  Thus:

> If I leave out the  then the display looks as it should and the 
> code does work.
>

This is a convenient side-effect of reaching the end of the tiddler 
definition.  Any unclosed widgets are *automatically* assumed to end when 
there's no more tiddler content.
Thus, for this specific use-case, leaving off the  
"looks as it should and the code does work".

Note that the "unclosed widget" handling also applies to the end of macro 
definitions even when they are not the end of the tiddler definition.  
Thus, if I write:

\define someMacro()
<$vars v1="..." >
<$vars v2="..." >
<$vars v3="..." >
... rest of macro here ...
\end
...more tiddler content here...

I can simply omit the close  and everything is 
still happy.  Strictly speaking, this is not "proper" syntax, since every 
widget it meant have a matching "close widget" or at use the 'shortform' 
where the widget itself ends with "/>" (as in <$action-setfield  />).  
Nonetheless, it can be VERY convenient.  For example, in 
http://tiddlytools.com/timer.html#TiddlyTools%2FTimer%2FClocks, 
the clock_adjustForTimezone() macro starts with **34** lines of <$vars> and 
<$set> widgets that do a series of complex calculations and assignments 
followed by just two lines containing <$list>... widgets.  It would 
be ridiculously inconvenient to then have to include another 34 lines of 
matching  and  at the end of the macro definition.

Note: This "omit the matching close <$widget>" technique only works when 
the opening widgets are in the outermost level of the macro syntax.  For 
example, if I have some code like this:
\define someMacro()
<$vars v1="...">
<$reveal ...>
   <$vars v2="..."
   ... something here ...

... some more stuff here ...
\end

I *must* use the  *inside* the <$reveal>... to match the 
opening <$vars v2="...">, since it isn't at the end of the entire macro.  
However, I *can* still omit the  that would match the *first* 
<$vars v1="...">, since that *is* at the end of the macro.  In general, I 
recommend using proper "close widget" syntax most of the time, except for 
some of the specific instances I've just described.  This avoids any 
headaches that can occur if you happen to add just one extra line of code 
at the end of a macro, only to find that all your previously unclosed 
widgets now need to be properly matched.

I hope this all makes sense to you and doesn't confuse things even more!

-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/327cd7e7-e38c-41f1-86d9-181cc81bee0eo%40googlegroups.com.

[tw5] Re: How To: altering TiddlyWiki appearance based on context (URL parameters at StartUp, and via radio buttons after StartUp)

That looks A-1 to do on one tiddler needing to decide what content to show 
based on context, but how to do that once so that it can be used for a 
plethora of tiddlers that show different content based on context?

I would not want to put that kind of code on each of my 
multi-context-handling tiddlers.

For that code to exist generically once, I imagine each 
multi-context-tiddler would need some kind of macro call like:  
<>

Aside from not doing that myself (for lack of macro and filter knowledge), 
I didn't want to go there because I often get tripped up setting these 
things up to not get screwed up every time I change tiddler titles (which I 
do repeatedly trying to get titles juust right.)

Thoughts?  (i.e. how to do that so that both "Contents" tiddler and "Title" 
tiddler can call some macro that does what your code does, but works 
generically for every tiddler that needs it?)

On Sunday, September 13, 2020 at 9:22:13 PM UTC-3, Felicia Crow wrote:
>
> Charlie,
>
> so first things first here is my version. This specific code would go into 
> Content, but it would look nearly the same with the other tiddlers. 
>

> <$set name="purpose" filter="[[Alternate TiddlyWiki 
> Purposes]get[purpose]]">
> <$list filter="[match[ProductReviews]]">
> {{Contents (Product Reviews)}}
> 
> <$list filter="[match[OffGridding]]">
> {{Contents (Urban Off Gridding)}}
> 
> 
>
> As for the explanation:
>
>- The filter within set gets the current value of the purpose field 
>that is in the tiddler with the title Alternate TiddlyWiki Purposes.
>- The filter in the list widget takes whatever was saved in set and 
>compares it to the parameter in match. If it matches the list widgets 
>content will be rendered.
>
>
> The code in itself does pretty much the same as your two transclusion 
> templates just in one place, so I think it mostly comes down to personal 
> preference where you check what actually needs to be rendered.
>
> The only thing I could think of what this solution currently does better 
> is being more failsafe in its execusion. The way the transclusion tiddlers 
> in your version are written they only look for fields named purpose which 
> contains their respective value, so when one adds a field purpose to 
> another tiddler and gives it the opposite value both versions will be 
> rendered at the same time. Since this is a wiki only edited by you this 
> probably won't happen, just realized it when I looked once more at your 
> templates while I wrote down my version.
>
> Felicia
>
>
> On Monday, 14 September 2020 01:23:18 UTC+2, Charlie Veniot wrote:
>>
>> G'day Felicia,
>>
>> Sure, I'd love to see how you'd go about it.  
>>
>> Since there are always multiple ways of doing things, if you have the 
>> time: quick thoughts on advantages/disadvantages of both for a quick back 
>> and forth about them?  Might be a pretty short back and forth: I don't have 
>> enough know-how to pickout the "pitfalls" (or "trappings") of various 
>> approaches?
>>
>> That aside: I'm kind of proud to have figured out a little something 
>> about filters in my last post 
>> .
>>
>> On Sunday, September 13, 2020 at 6:03:04 PM UTC-3, Felicia Crow wrote:
>>>
>>> Hi Charlie,
>>>
>>> yes that was what I meant. I always find it interesting to learn the 
>>> thought process behind someones solution, since it often gives a different 
>>> perspective on things that I would not have considered before, leads to 
>>> learning something new or both. So when I saw a solution I would not have 
>>> thought of myself I was curious how this came to be.
>>>
>>> I sadly don't have any real tips for learning filters as it is one of 
>>> the things my brain was actually willing to learn at least the basics quite 
>>> quickly, but if you want I could write up the solution I had in mind so 
>>> that you can play around with it, if this would be something that interests 
>>> you/could help you.
>>>
>>> And to add something useful to the babbling at the top: A short 
>>> excursion about the difference between non-javascript and javascript macros 
>>> at least as far as I learned it - definitely not an expert.
>>>
>>>
>>>- Javascript macros are loaded in with everything else javascript 
>>>before any processing happens as this is so to speak the engine on which 
>>>everything runs, so yes a javascript macro is already loaded in when the 
>>>startup actions are run.
>>>- Non-javascript macros one the other hand exist at first only 
>>>within the tiddler they where defined in. So for example if you have a 
>>>tiddler containing the definition for a macro called get-context you 
>>> would 
>>>only be able to use this macro in the same tiddler. This is where then 
>>> the 
>>>import pragma and tag $:/tags/Macro come in. Import is used as you have 
>>>done to allow use of a specific macro in the tiddler it was imported to. 
>>>The tag

[tw5] Re: How To: altering TiddlyWiki appearance based on context (URL parameters at StartUp, and via radio buttons after StartUp)

G'day Tones,

First: a shack in the Australian bush.  I can't imagine a better off-grid 
image.  Of course, being French-Acadian, I'm a total romantic...

Second: I've always believed that no matter how silly an "offering" (I like 
to think of myself as lobbing slightly off-key stuff), sometimes the 
silliest of things bring up the bestest a-ha-who-woulda-thunk goodies.  
Although I'm a pooped puppy, I do believe I totally get where you are 
going, and I rather like what you're thinking (to look at me and my home, 
nobody would think I'm a fiend of tidiness, but when it comes to 
information and programming code, I slowly love to tidy the poop out of 
that.)

Cheers !

On Sunday, September 13, 2020 at 8:49:26 PM UTC-3, TW Tones wrote:
>
> Charlie,
>
> I saw in some of your code the use of tiddler named "Contents (Urban Off 
> Gridding)"
>
>- First - I have a shack in the Australian bush that's off grid, 
>sustainability is one of my interests.
>- A Quick test revealed (tiddlernames) seem quite secure in filters 
>and other places like transclusions.
>
> I am just mentioning this because it has led me to a solution I have being 
> looking for. Simple one word system tiddlers.
>
> Let me explain, although don't worry if you don't follow, I just wanted to 
> thank you for inspiring me.
>
>
>- If you want to transclude a "system tiddler" that does not otherwise 
>appear in searches it must have the prefix $:/ and then it must be in 
>keeping with existing naming.
>- If you want to include system tiddlers css, templates etc the need 
>to have this prefix and just don't look so good
>- For example I I has a function "greatFunction" you would need to 
>reference it as {{$:/myfunctions/greatFunction}} or 
>{$:/myfunctions/greatFunction} in filters
>- That is the simple names are no longer available to use.
>
> The thought you gave me is
>
>- I could name a tiddler like this (greatFunction) 
>- Exclude titles beginning and ending in () from the standard search 
>(Thus they are somewhat hidden from the user)
>- Then you could reference it as {{(greatFunction)}} or 
>{(greatFunction)} in filters etc... 
>- It is also then easy to name objects that are more readable 
>{{(task-template)}} that are like system tiddlers.
>- Note: this would not impact your use "Contents (Urban Off Gridding)" 
>because it does not begin and end ( )
>
> Conclusion
>
>- Cleaner code
>- Easier to help users select from a list of optional views or 
>templates
>- Easier as designer
>- More real language like.
>- A whole new names space
>
> Regards
> Tones
>
> On Monday, 14 September 2020 09:23:18 UTC+10, Charlie Veniot wrote:
>>
>> G'day Felicia,
>>
>> Sure, I'd love to see how you'd go about it.  
>>
>> Since there are always multiple ways of doing things, if you have the 
>> time: quick thoughts on advantages/disadvantages of both for a quick back 
>> and forth about them?  Might be a pretty short back and forth: I don't have 
>> enough know-how to pickout the "pitfalls" (or "trappings") of various 
>> approaches?
>>
>> That aside: I'm kind of proud to have figured out a little something 
>> about filters in my last post 
>> .
>>
>> On Sunday, September 13, 2020 at 6:03:04 PM UTC-3, Felicia Crow wrote:
>>>
>>> Hi Charlie,
>>>
>>> yes that was what I meant. I always find it interesting to learn the 
>>> thought process behind someones solution, since it often gives a different 
>>> perspective on things that I would not have considered before, leads to 
>>> learning something new or both. So when I saw a solution I would not have 
>>> thought of myself I was curious how this came to be.
>>>
>>> I sadly don't have any real tips for learning filters as it is one of 
>>> the things my brain was actually willing to learn at least the basics quite 
>>> quickly, but if you want I could write up the solution I had in mind so 
>>> that you can play around with it, if this would be something that interests 
>>> you/could help you.
>>>
>>> And to add something useful to the babbling at the top: A short 
>>> excursion about the difference between non-javascript and javascript macros 
>>> at least as far as I learned it - definitely not an expert.
>>>
>>>
>>>- Javascript macros are loaded in with everything else javascript 
>>>before any processing happens as this is so to speak the engine on which 
>>>everything runs, so yes a javascript macro is already loaded in when the 
>>>startup actions are run.
>>>- Non-javascript macros one the other hand exist at first only 
>>>within the tiddler they where defined in. So for example if you have a 
>>>tiddler containing the definition for a macro called get-context you 
>>> would 
>>>only be able to use this macro in the same tiddler. This is where then 
>>> the 
>>>import pragma and tag $:/tags/Macro come in.

[tw5] Re: A TiddlyWiki "TODO organization/reminder" approach

Hi,

since you linked so nicely from our other discussion to here I decided to 
leave my thoughts on this project where it is relevant.

I have to say I find the whole system very interesting, especially using 
hard links to one tiddler to pull everything together.

May have to borrow the idea and see if I can incorporate it in my edit-text 
widget todo list for when the todos are specific to certain tiddlers 
instead of more general things.

Cheers,
Felicia

On Monday, 14 September 2020 01:13:45 UTC+2, Charlie Veniot wrote:
>
> G’day,
>
> I needed a way to remind myself of “TODO” tasks in regards to my 
> dual-purpose “Product Reviews” and “Urban Off Gridding for Laypersons” 
> TiddlyWiki 
> 
> .
>
> My approach:
>
>- 
>
>In whatever tiddler requiring something I need to do, I add (in the 
>text of the tiddler) a [[TODO]] link along with notes related to the thing 
>I need to do
>- 
>
>When I’ve completed the thing I needed to do, I just edit the tiddler 
>and get rid of the [[TODO]] link and the related notes.
>- 
>   
>   I don’t need a “record” of the thing being done
>   - 
>
>To remind me of what I need to do …
>- 
>   
>   The sidebar displays a fairly noticeable TODO section (a “TODO” 
>   DetailsWidget containing the list of tiddlers that have [[TODO]] links)
>   - 
>   
>   When there are no tiddlers referencing [[TODO]], then the sidebar's 
>   TODO section "disappears" *(reappearing next time a [[TODO]] link 
>   gets created in some tiddler)*
>   
>
> Please find below 5 screenshots of related things to look for in my 
> TiddlyWiki 
> 
> .
>
> Cheers !
>
>
> TODO section in the sidebar (collapsed)
>
> [image: TheTodoInTheSidebarCollapsed.png]
>
>
>
> TODO section in the sidebar (expanded)
>
> [image: TheTodoInTheSidebarExpanded.png]
>
>
>
> The filter that creates the TODO section if there are any TODO’s
>
> [image: CustomTiddlywikiTitleTop.png]
>
>
>
> The TODO tiddler
>
> [image: TheTodoTiddler.png]
>
>
>
> A sample TODO (TODO reference and related notes)
>
> [image: TodoReference.png]
>
>
>
>
>

-- 
You received this message because you are subscribed to the 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/0a44fb9b-9116-4442-acd2-866cc4bbcc39o%40googlegroups.com.

[tw5] Re: How To: altering TiddlyWiki appearance based on context (URL parameters at StartUp, and via radio buttons after StartUp)

Charlie,

so first things first here is my version. This specific code would go into 
Content, but it would look nearly the same with the other tiddlers:

<$set name="purpose" filter="[[Alternate TiddlyWiki Purposes]get[purpose]]">
<$list filter="[match[ProductReviews]]">
{{Contents (Product Reviews)}}

<$list filter="[match[OffGridding]]">
{{Contents (Urban Off Gridding)}}



As for the explanation:

   - The filter within set gets the current value of the purpose field that 
   is in the tiddler with the title Alternate TiddlyWiki Purposes.
   - The filter in the list widget takes whatever was saved in set and 
   compares it to the parameter in match. If it matches the list widgets 
   content will be rendered.


The code in itself does pretty much the same as your two transclusion 
templates just in one place, so I think it mostly comes down to personal 
preference where you check what actually needs to be rendered.

The only thing I could think of what this solution currently does better is 
being more failsafe in its execusion. The way the transclusion tiddlers in 
your version are written they only look for fields named purpose which 
contains their respective value, so when one adds a field purpose to 
another tiddler and gives it the opposite value both versions will be 
rendered at the same time. Since this is a wiki only edited by you this 
probably won't happen, just realized it when I looked once more at your 
templates while I wrote down my version.

Felicia


On Monday, 14 September 2020 01:23:18 UTC+2, Charlie Veniot wrote:
>
> G'day Felicia,
>
> Sure, I'd love to see how you'd go about it.  
>
> Since there are always multiple ways of doing things, if you have the 
> time: quick thoughts on advantages/disadvantages of both for a quick back 
> and forth about them?  Might be a pretty short back and forth: I don't have 
> enough know-how to pickout the "pitfalls" (or "trappings") of various 
> approaches?
>
> That aside: I'm kind of proud to have figured out a little something about 
> filters in my last post 
> .
>
> On Sunday, September 13, 2020 at 6:03:04 PM UTC-3, Felicia Crow wrote:
>>
>> Hi Charlie,
>>
>> yes that was what I meant. I always find it interesting to learn the 
>> thought process behind someones solution, since it often gives a different 
>> perspective on things that I would not have considered before, leads to 
>> learning something new or both. So when I saw a solution I would not have 
>> thought of myself I was curious how this came to be.
>>
>> I sadly don't have any real tips for learning filters as it is one of the 
>> things my brain was actually willing to learn at least the basics quite 
>> quickly, but if you want I could write up the solution I had in mind so 
>> that you can play around with it, if this would be something that interests 
>> you/could help you.
>>
>> And to add something useful to the babbling at the top: A short excursion 
>> about the difference between non-javascript and javascript macros at least 
>> as far as I learned it - definitely not an expert.
>>
>>
>>- Javascript macros are loaded in with everything else javascript 
>>before any processing happens as this is so to speak the engine on which 
>>everything runs, so yes a javascript macro is already loaded in when the 
>>startup actions are run.
>>- Non-javascript macros one the other hand exist at first only within 
>>the tiddler they where defined in. So for example if you have a tiddler 
>>containing the definition for a macro called get-context you would only 
>> be 
>>able to use this macro in the same tiddler. This is where then the import 
>>pragma and tag $:/tags/Macro come in. Import is used as you have done to 
>>allow use of a specific macro in the tiddler it was imported to. The tag 
>>$:/tags/Macro on the other hand allows you to mark the macro as global so 
>>that you can use it where ever you want without having to specifically 
>>import it each time. This is were the exception you reference comes in. 
>>Since the startup actions run before the tagged macros are processed to 
>>make them globally available you need to import non-javascript macros 
>> even 
>>if they are properly tagged.
>>
>>
>> Hope you can take away at least something from this and it wasn't too 
>> confusing.
>>
>> Happy Sunday for you as well.
>>
>>
>>
>> On Sunday, 13 September 2020 20:47:35 UTC+2, Charlie Veniot wrote:
>>>
>>> G'day Felicia,
>>>
>>> Hi Charlie,

 love the concept and very impressiv what you managed to put together, 
 thank you for sharing.

>>>
>>> Thank-you!  Of course, let's keep in mind that, in martial arts terms, 
>>> I'm not quite a TiddlyWiki yellow belt yet, so I'm sure there are many 
>>> things that could be improved !
>>>  
>>>

 If you don't mind asking, is there a specific reason for placing the 
 decision for what to

Re: [tw5] Re: a transclusion inconcistency

2020-09-13 Thread Bob Jansen

Eric & Tones,

I do not know how to close the wikify tags as Tones has recommended. I have 
two tags as there are two variables I need.

Code:
<$wikify name="theuniqueid" text={{$:/TLS/uniqueid}}>
<$wikify name="theartworkurl" text={{$:/TLS/artworkurl}}>

''Artwork unique ID: <>''

Artwork title: <$edit-text tiddler="$:/TLS/new-title" tag="input" 
default=""/>

Type: <$edit-text tiddler="$:/TLS/artwork-type" tag="input" default=""/>

Medium: <$edit-text tiddler="$:/TLS/medium" tag="input" default=""/>

Size: <$edit-text tiddler="$:/TLS/size" tag="input" default=""/>

Year created: <$edit-text tiddler="$:/TLS/year-created" tag="input" 
default=""/>

Number in edition: <$edit-text tiddler="$:/TLS/number-in-edition" 
tag="input" default=""/>

Submitted to exhibition: <$edit-text 
tiddler="$:/TLS/artwork-submitted-to-exhibition" tag="input" default=""/>

---

Purchased by: <$edit-text tiddler="$:/TLS/purchased-by" tag="input" 
default=""/>

Date purchased: <$edit-text tiddler="$:/TLS/date-purchased" tag="input" 
default=""/>

Price: <$edit-text tiddler="$:/TLS/price" tag="input" default=""/>

Status: <$edit-text tiddler="$:/TLS/status" tag="input" default=""/>

<$button>
<$action-setfield $tiddler="$:/TLS/incremental" text={{{ 
[{$:/TLS/incremental}add[1]] }}}/>
<$action-createtiddler 
 $basetitle={{$:/TLS/new-title}} 
 $template="Artwork Template" 
 tags="Artworks" 
 $overwrite="yes" 
 artwork_id=<>
 artwork_url=<> 
 artwork_numberinedition={{$:/TLS/number-in-edition}} 
 artwork_price={{$:/TLS/price}} 
 artwork_status={{$:/TLS/status}} 
 artwork_yearofcreation={{$:/TLS/year-created}} 
 purchased_by={{$:/TLS/purchased-by}} 
 artwork_medium={{$:/TLS/medium}} 
 artwork_size={{$:/TLS/size}} 
 artwork_price={{$:/TLS/price}} 
 artwork_status={{$:/TLS/status}} 
 date_purchased={{$:/TLS/date-purchased}}
 artwork_type={{$:/TLS/artwork-type}}

 artwork_submitted_to_exhibition={{$:/TLS/artwork-submitted-to-exhibition}}
/>
<$action-deletetiddler $tiddler="$:/TLS/new-title" />
<$action-deletetiddler $tiddler="$:/TLS/medium" />
<$action-deletetiddler $tiddler="$:/TLS/size" />
<$action-deletetiddler $tiddler="$:/TLS/year-created" />
<$action-deletetiddler $tiddler="$:/TLS/number-in-edition" />
<$action-deletetiddler $tiddler="$:/TLS/purchased-by" />
<$action-deletetiddler $tiddler="$:/TLS/date-purchased" />
<$action-deletetiddler $tiddler="$:/TLS/price" />
<$action-deletetiddler $tiddler="$:/TLS/status" />
<$action-deletetiddler $tiddler="$:/TLS/artwork-type" />
<$action-deletetiddler $tiddler="$:/TLS/artwork-submitted-to-exhibition" />
Add new artwork


If I add  as the last line of the code then the display 
of the tiddler changes to

Add New artwork 

If I leave out the  then the display looks as it should and the 
code does work.

What should I do?

bobj
On Sunday, 13 September 2020 at 13:06:25 UTC+10 TW Tones wrote:

> Touched on here 
>
>- https://tiddlywiki.com/#Widgets%20in%20WikiText
>- https://tiddlywiki.com/#HTML%20in%20WikiText
>- https://tiddlywiki.com/#Transclusion%20and%20Substitution
>- https://tiddlywiki.com/#Transclusion%20in%20WikiText
>
> I searched tiddlywiki.com for "{{{" to get these results.
>
> Unfortunately the documentation is not totally consistent.
>
> Regards
> Tony
>
> On Sunday, 13 September 2020 12:43:14 UTC+10, Bob Jansen wrote:
>
>> Thanks Eric. By the way, where do all those brackets come from in the 
>> inline filter and where is all that documented when to use which and how 
>> many ?
>>
>> Bobj
>>
>> Dr. Bob Jansen
>> 122 Cameron St, Rockdale NSW 2216, Australia
>> Ph: +61 414 297 448 <+61%20414%20297%20448>
>> Skype: bobjtls
>>
>>
>> On 13 Sep 2020, at 12:12, Eric Shulman  wrote:
>>
>> On Saturday, September 12, 2020 at 6:12:12 PM UTC-7, Bob Jansen wrote:
>>>
>>> <$button>
>>> <$wikify name="theuniqueid" text={{$:/TLS/uniqueid}}>
>>> <$action-createtiddler $basetitle="$:/TLS/new-id" $overwrite="yes" />
>>> <$action-setfield $tiddler="$:/TLS/new-id" text={{$:/TLS/uniqueid}} 
>>> uniqueid=<> />
>>> 
>>> Add
>>> 
>>>
>>
>> This can also be done without using $wikify, by using an "inline filter", 
>> like this:
>> <$button> Add
>> <$vars id={{{ [{$:/TLS/idcode}addsuffix{$:/TLS/incremental}] }}}>
>> <$action-createtiddler $basetitle="$:/TLS/new-id" $overwrite="yes" />
>> <$action-setfield $tiddler="$:/TLS/new-id" text=<> uniqueid=<> />
>> 
>> 
>>
>> -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/8OIdMGfIV-A/unsubscribe.
>>
>> To unsubscribe from this group and all its topics, send an email to 
>> tiddl...@googlegroups.com.
>>
>>
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/tiddlywiki/f856baf6-18a7-41e0-a1d6-da474f7e1cd3o%40googlegroups.com
>>  
>>

[tw5] Re: How To: altering TiddlyWiki appearance based on context (URL parameters at StartUp, and via radio buttons after StartUp)

Charlie,

I saw in some of your code the use of tiddler named "Contents (Urban Off 
Gridding)"

   - First - I have a shack in the Australian bush that's off grid, 
   sustainability is one of my interests.
   - A Quick test revealed (tiddlernames) seem quite secure in filters and 
   other places like transclusions.

I am just mentioning this because it has led me to a solution I have being 
looking for. Simple one word system tiddlers.

Let me explain, although don't worry if you don't follow, I just wanted to 
thank you for inspiring me.


   - If you want to transclude a "system tiddler" that does not otherwise 
   appear in searches it must have the prefix $:/ and then it must be in 
   keeping with existing naming.
   - If you want to include system tiddlers css, templates etc the need to 
   have this prefix and just don't look so good
   - For example I I has a function "greatFunction" you would need to 
   reference it as {{$:/myfunctions/greatFunction}} or 
   {$:/myfunctions/greatFunction} in filters
   - That is the simple names are no longer available to use.

The thought you gave me is

   - I could name a tiddler like this (greatFunction) 
   - Exclude titles beginning and ending in () from the standard search 
   (Thus they are somewhat hidden from the user)
   - Then you could reference it as {{(greatFunction)}} or 
   {(greatFunction)} in filters etc... 
   - It is also then easy to name objects that are more readable 
   {{(task-template)}} that are like system tiddlers.
   - Note: this would not impact your use "Contents (Urban Off Gridding)" 
   because it does not begin and end ( )

Conclusion

   - Cleaner code
   - Easier to help users select from a list of optional views or templates
   - Easier as designer
   - More real language like.
   - A whole new names space

Regards
Tones

On Monday, 14 September 2020 09:23:18 UTC+10, Charlie Veniot wrote:
>
> G'day Felicia,
>
> Sure, I'd love to see how you'd go about it.  
>
> Since there are always multiple ways of doing things, if you have the 
> time: quick thoughts on advantages/disadvantages of both for a quick back 
> and forth about them?  Might be a pretty short back and forth: I don't have 
> enough know-how to pickout the "pitfalls" (or "trappings") of various 
> approaches?
>
> That aside: I'm kind of proud to have figured out a little something about 
> filters in my last post 
> .
>
> On Sunday, September 13, 2020 at 6:03:04 PM UTC-3, Felicia Crow wrote:
>>
>> Hi Charlie,
>>
>> yes that was what I meant. I always find it interesting to learn the 
>> thought process behind someones solution, since it often gives a different 
>> perspective on things that I would not have considered before, leads to 
>> learning something new or both. So when I saw a solution I would not have 
>> thought of myself I was curious how this came to be.
>>
>> I sadly don't have any real tips for learning filters as it is one of the 
>> things my brain was actually willing to learn at least the basics quite 
>> quickly, but if you want I could write up the solution I had in mind so 
>> that you can play around with it, if this would be something that interests 
>> you/could help you.
>>
>> And to add something useful to the babbling at the top: A short excursion 
>> about the difference between non-javascript and javascript macros at least 
>> as far as I learned it - definitely not an expert.
>>
>>
>>- Javascript macros are loaded in with everything else javascript 
>>before any processing happens as this is so to speak the engine on which 
>>everything runs, so yes a javascript macro is already loaded in when the 
>>startup actions are run.
>>- Non-javascript macros one the other hand exist at first only within 
>>the tiddler they where defined in. So for example if you have a tiddler 
>>containing the definition for a macro called get-context you would only 
>> be 
>>able to use this macro in the same tiddler. This is where then the import 
>>pragma and tag $:/tags/Macro come in. Import is used as you have done to 
>>allow use of a specific macro in the tiddler it was imported to. The tag 
>>$:/tags/Macro on the other hand allows you to mark the macro as global so 
>>that you can use it where ever you want without having to specifically 
>>import it each time. This is were the exception you reference comes in. 
>>Since the startup actions run before the tagged macros are processed to 
>>make them globally available you need to import non-javascript macros 
>> even 
>>if they are properly tagged.
>>
>>
>> Hope you can take away at least something from this and it wasn't too 
>> confusing.
>>
>> Happy Sunday for you as well.
>>
>>
>>
>> On Sunday, 13 September 2020 20:47:35 UTC+2, Charlie Veniot wrote:
>>>
>>> G'day Felicia,
>>>
>>> Hi Charlie,

 love the concept and very impressiv what you managed to put together,

Re: [tw5] Re: Question about Refrences and Macros

2020-09-13 Thread huntsfromshadow

Honestly, in the great scheme of things, it isn't that big of a deal.

I was just curious if this was a known issue, or if I was just doing
something wrong when I was returning the text back out of macros.

-Luke


On Sun, Sep 13, 2020 at 5:57 PM Felicia Crow  wrote:

> Hi,
>
> yes this is absolutely expected behaviour and a problem that pops up in
> this group from time to time.
>
> Tiddlywiki only recognizes hard links - everytime you use [[Link]]
> directly in the wikitext mostly - as references.
> Everything else - links coming from macros, variables, transclusions, etc.
> - is a so called soft link and not recognized.
>
> As for a solution: What would be your actual use case? There is no
> universial tiddlywiki recognizes soft links now solution, but maybe there
> can still be done something if it is clearer what you are trying to achieve.
> Although one thing I can answer now is that from most approaches I have
> seen the item that would reference tiddler 1 would still be the tiddler you
> defined the macro in - so in your case tiddler 2 - not the macro itself.
>
> Kind Regards,
> Felicia.
>
>
> On Sunday, 13 September 2020 22:15:30 UTC+2, Huntsfromshadow wrote:
>
>> Question about Reference List and Macros.
>>
>> I have the following Setup.
>>
>> 1 - Tiddler 1 that has some random Text.
>> 2 - Tiddler 2 that has [[Tiddler 1]] in it.
>>
>> Tiddler 1 shows that Tiddler 2 refrences it (and thus isn't on the Orphan
>> list).
>>
>> If I replace the text in Tiddler 2 with
>> \define testme()
>> [[Tiddler 1]]
>> \end
>>
>> <>
>>
>> Tiddler 1 doesn't show any refrences to it (and thus is in the Orphan
>> List).
>>
>>
>> Is this expected? Anyway to have the macro still report as a refrence?
>>
>> Thanks
>> -Luke
>>
>> --
> You received this message because you are subscribed to the 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/5fba5ed1-17f1-41aa-9945-5c641b5a8b49o%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/CA%2B55YnZ%2BAf3a2Qp8A-FDnPf%3DLjFDNoVeUCTOA4CAQ%3D0qXsq4-A%40mail.gmail.com.

[tw5] Re: [off topic] why do people want a static tiddlywiki?

Ste,

To me static means as others have said basically it is "unchanging". Thus 
it will not save changes to the server. The Author may regenerate and save 
change to the server manually, or in a somewhat automated way, which makes 
the site look like an interactive site.

To me there are only two clear and apparent advantages

   - As every tiddler is a separate independent html page each is open to 
   search engines.
  - On the standard static site, links are changed to load the next 
  static page
  - All content is generated and in a sense a snapshot created that 
  does not need rendering
   - If the wiki is large it has a load time some consider unacceptable, 
   despite being able to provide a startup splash screen
  - This may affect search engines indexing or not favouring tiddlywiki 
  sites, because load time is considered critical
   
My personal view is exporting to a static website is a sad waste of 
interactive features, 

   - stops the users benefiting from 
  - last state (eg marking something read) 
  - Customisation
  - History
  - and a lot more
   - Just makes tiddlywiki a static html site generator (great but limited)
   - Breaks tiddlywiki single file wiki model as every tiddler becomes its 
   own html page.

My solution would be

   - Export separate static tiddlers only as they change for upload to the 
   publishing site
   - Ensure their internal links point to the full wiki so any link from a 
   static page loads the full wiki
  - Or selectively by design
   - For very large sites consider a multi-wiki setup that is transparent 
   to the user.
   - If re-publishing tiddlers "posts and pages" elsewhere you can post the 
   URL to the static page, as a landing page, knowing they then enter the 
   interactive wiki if they have any further interactions.

I have not had time to do this yet, but will for my own business sites.

Advanced ideas;

   - In a single wiki develop so we actually specify which links can go to 
   another static tiddler and which should open, which interactive wiki.
   - Provide a simple way to publish from one wiki, multiple interactive 
   wikis along with all static pages with URL customised for links to static 
   or interactive pages.
   - Provide support so if someone wants a link / bookmark they can choose 
   the static or interactive (Permalink).

I hope this helps

Regards
Tones

On Sunday, 13 September 2020 18:19:53 UTC+10, Ste wrote:
>
> Coming from a place of ignorance.. 
> Why are so many people keen to change tiddlywiki into a static site? What 
> are the advantages? 
> Is tiddlywiki not a static site? What's the difference? 

-- 
You received this message because you are subscribed to the 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/013f69d7-efa2-4120-8fe0-963e38529de4o%40googlegroups.com.

[tw5] Re: How To: altering TiddlyWiki appearance based on context (URL parameters at StartUp, and via radio buttons after StartUp)

G'day Felicia,

Sure, I'd love to see how you'd go about it.  

Since there are always multiple ways of doing things, if you have the time: 
quick thoughts on advantages/disadvantages of both for a quick back and 
forth about them?  Might be a pretty short back and forth: I don't have 
enough know-how to pickout the "pitfalls" (or "trappings") of various 
approaches?

That aside: I'm kind of proud to have figured out a little something about 
filters in my last post 
.

On Sunday, September 13, 2020 at 6:03:04 PM UTC-3, Felicia Crow wrote:
>
> Hi Charlie,
>
> yes that was what I meant. I always find it interesting to learn the 
> thought process behind someones solution, since it often gives a different 
> perspective on things that I would not have considered before, leads to 
> learning something new or both. So when I saw a solution I would not have 
> thought of myself I was curious how this came to be.
>
> I sadly don't have any real tips for learning filters as it is one of the 
> things my brain was actually willing to learn at least the basics quite 
> quickly, but if you want I could write up the solution I had in mind so 
> that you can play around with it, if this would be something that interests 
> you/could help you.
>
> And to add something useful to the babbling at the top: A short excursion 
> about the difference between non-javascript and javascript macros at least 
> as far as I learned it - definitely not an expert.
>
>
>- Javascript macros are loaded in with everything else javascript 
>before any processing happens as this is so to speak the engine on which 
>everything runs, so yes a javascript macro is already loaded in when the 
>startup actions are run.
>- Non-javascript macros one the other hand exist at first only within 
>the tiddler they where defined in. So for example if you have a tiddler 
>containing the definition for a macro called get-context you would only be 
>able to use this macro in the same tiddler. This is where then the import 
>pragma and tag $:/tags/Macro come in. Import is used as you have done to 
>allow use of a specific macro in the tiddler it was imported to. The tag 
>$:/tags/Macro on the other hand allows you to mark the macro as global so 
>that you can use it where ever you want without having to specifically 
>import it each time. This is were the exception you reference comes in. 
>Since the startup actions run before the tagged macros are processed to 
>make them globally available you need to import non-javascript macros even 
>if they are properly tagged.
>
>
> Hope you can take away at least something from this and it wasn't too 
> confusing.
>
> Happy Sunday for you as well.
>
>
>
> On Sunday, 13 September 2020 20:47:35 UTC+2, Charlie Veniot wrote:
>>
>> G'day Felicia,
>>
>> Hi Charlie,
>>>
>>> love the concept and very impressiv what you managed to put together, 
>>> thank you for sharing.
>>>
>>
>> Thank-you!  Of course, let's keep in mind that, in martial arts terms, 
>> I'm not quite a TiddlyWiki yellow belt yet, so I'm sure there are many 
>> things that could be improved !
>>  
>>
>>>
>>> If you don't mind asking, is there a specific reason for placing the 
>>> decision for what to transclude in the two templates themselves and always 
>>> calling both of them?
>>> Personally I would have put the decision in the root tiddler - e.g. 
>>> TiddlyWiki Title - via a match filter and only called what was needed, so I 
>>> wonder if there is something I am missing/not thinking about or if it is 
>>> just another case of multiple ways to achieve the same result.
>>>
>>
>> I suspect that you are talking about this way of deciding what to show 
>> based on context: {{TiddlyWiki Title 1||tPr}}{{TiddlyWiki Title 2||tOg}}
>>
>> I chose that way of doing things because I'm having a hard time wrapping 
>> my mind around filters, but I think I've got transclusion templates down 
>> pat.
>>
>> So I saw that mechanism as a quick (and non-cryptic) and easily 
>> repeatable method across the board, for example:
>>
>>- the "content" tiddler (included in my "navigation" tiddler that 
>>shows in the sidebar) has {{Contents (Product Reviews)||tPr}}{{Contents 
>>(Urban Off Gridding)||tOg}} to show different navigation links depending 
>> on 
>>context
>>- I may want to show other tiddlers different ways depending on 
>>context ...
>>
>>
>>
>>> Oh and one thing I noticed, just as an info: Since getstartupcontext is 
>>> a javascript macro you don't actually need to import it. Unlike normal 
>>> macros javascript macros are always global.
>>>
>>
>> Maybe I misunderstood something when I put that import there.  I thought 
>> that "StartupAction" tiddlers, because they are processed so early, didn't 
>> have access to any macros unless they are imported.  Does that just apply 
>> to non-javascript macros ?
>>  
>>
>>>
>>>

[tw5] Re: TiddlyWiki toolmap submissions

David,

I do not want to saturate the tools list 

   - but I discovered a simple way to provide a date picker that returns 
   the Tiddlywiki serial number.
   - Perhaps we need to Qualify some of the items on the tools links so 
   they can be differentiated. 

Regards
Tones

On Sunday, 13 September 2020 22:08:58 UTC+10, David Gifford wrote:
>
> I added both versions on one line of the toolmap, here: 
> https://dynalist.io/d/zUP-nIWu2FFoXH-oM7L7d9DM#z=KD7kUsUIFmx3Us0teMLUILMI
>
> Thanks for catching this! Happy to add overlooked items as people point 
> them out to me.
>
> On Sunday, September 13, 2020 at 6:25:16 AM UTC-5 strikke...@gmail.com 
> wrote:
>
>>  Tobias Beer mentions GSD5 and the datepicker, but the GSD5 wiki and the 
>> datepicker was created by Roma Hicks as far as I remember.
>> Link for the wiki with the datepicker http://gsd5.tiddlyspot.com/
>> A later version of the wiki can be found here: 
>> https://gitlab.com/gsd5-tiddlywiki
>>
>> Birthe
>>
>

-- 
You received this message because you are subscribed to the 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/b4b64831-abdc-4f10-be61-b9cf40789681o%40googlegroups.com.

[tw5] Incremental Search Behavior in TW5

2020-09-13 Thread Mark Kerrigan

Hello all

One of the things I find a constant performance issue on one of my larger 
TW5 files is search. I often have input lag when searching, part of this is 
because I'm using this TW on a computer with only 2 GB of RAM and there are 
1400+ tiddlers. I see I could change the "Hidden Setting: Search Minimum 
Length" to something higher, but this isn't quite the behavior I'm looking 
for.

What I would really like is to replicate the feature in TWC where there was 
an option to enable or disable Incremental Search. So instead of just 
typing 4 characters to start a search, no search would be performed until 
the enter key is pressed.

Maybe I'm missing something, but I am curious if it's possible to modify 
the default behavior.

Thank you
Mark Kerrigan

-- 
You received this message because you are subscribed to the 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/e538bf04-7717-4184-bebd-a50b777ef014o%40googlegroups.com.

[tw5] Re: Question about Refrences and Macros

Hi,

yes this is absolutely expected behaviour and a problem that pops up in 
this group from time to time.

Tiddlywiki only recognizes hard links - everytime you use [[Link]] directly 
in the wikitext mostly - as references.
Everything else - links coming from macros, variables, transclusions, etc. 
- is a so called soft link and not recognized.

As for a solution: What would be your actual use case? There is no 
universial tiddlywiki recognizes soft links now solution, but maybe there 
can still be done something if it is clearer what you are trying to achieve.
Although one thing I can answer now is that from most approaches I have 
seen the item that would reference tiddler 1 would still be the tiddler you 
defined the macro in - so in your case tiddler 2 - not the macro itself.

Kind Regards,
Felicia.

On Sunday, 13 September 2020 22:15:30 UTC+2, Huntsfromshadow wrote:

> Question about Reference List and Macros.
>
> I have the following Setup.
>
> 1 - Tiddler 1 that has some random Text.
> 2 - Tiddler 2 that has [[Tiddler 1]] in it.
>
> Tiddler 1 shows that Tiddler 2 refrences it (and thus isn't on the Orphan 
> list).
>
> If I replace the text in Tiddler 2 with
> \define testme()
> [[Tiddler 1]]
> \end
>
> <>
>
> Tiddler 1 doesn't show any refrences to it (and thus is in the Orphan 
> List).
>
>
> Is this expected? Anyway to have the macro still report as a refrence?
>
> Thanks
> -Luke
>
>

-- 
You received this message because you are subscribed to the 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/5fba5ed1-17f1-41aa-9945-5c641b5a8b49o%40googlegroups.com.

[tw5] Re: Proof of Concept: Dynamic Global Variables

Mario,
here is the link: 
https://groups.google.com/forum/#!msg/tiddlywiki/E32yX5RGv4A/AV0KSxvaAgAJ
It was actually not the original discussion that triggered it, but me 
providing a javascript solution to the problem and Tony then asking if 
something like this was possible now that I had gotten some understanding 
of using javascript in tiddlywiki. Looking back at it now it is interesting 
to see how far this thing has changed from its macro beginnings.

Mat,
this answer is definitely on Tony. I personally also have yet to find an 
actual need for it, but this would be the first time not having a use for a 
tool to stop me from at least trying to build it, when it sounds 
interesting.
As for security reasons I am not sure. Maybe it could also fall under the 
more trouble than it's worth category, seeing how easy it is to overwrite a 
variable with something that then could break things further down the line, 
while not necessarily finding much use that can't be solved in another way.

Kind Regards,
Felicia

-- 
You received this message because you are subscribed to the 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/050e239d-7585-4817-b634-c4ff492fa91ao%40googlegroups.com.

[tw5] Re: How To: altering TiddlyWiki appearance based on context (URL parameters at StartUp, and via radio buttons after StartUp)

Hi Charlie,

yes that was what I meant. I always find it interesting to learn the 
thought process behind someones solution, since it often gives a different 
perspective on things that I would not have considered before, leads to 
learning something new or both. So when I saw a solution I would not have 
thought of myself I was curious how this came to be.

I sadly don't have any real tips for learning filters as it is one of the 
things my brain was actually willing to learn at least the basics quite 
quickly, but if you want I could write up the solution I had in mind so 
that you can play around with it, if this would be something that interests 
you/could help you.

And to add something useful to the babbling at the top: A short excursion 
about the difference between non-javascript and javascript macros at least 
as far as I learned it - definitely not an expert.


   - Javascript macros are loaded in with everything else javascript before 
   any processing happens as this is so to speak the engine on which 
   everything runs, so yes a javascript macro is already loaded in when the 
   startup actions are run.
   - Non-javascript macros one the other hand exist at first only within 
   the tiddler they where defined in. So for example if you have a tiddler 
   containing the definition for a macro called get-context you would only be 
   able to use this macro in the same tiddler. This is where then the import 
   pragma and tag $:/tags/Macro come in. Import is used as you have done to 
   allow use of a specific macro in the tiddler it was imported to. The tag 
   $:/tags/Macro on the other hand allows you to mark the macro as global so 
   that you can use it where ever you want without having to specifically 
   import it each time. This is were the exception you reference comes in. 
   Since the startup actions run before the tagged macros are processed to 
   make them globally available you need to import non-javascript macros even 
   if they are properly tagged.
   

Hope you can take away at least something from this and it wasn't too 
confusing.

Happy Sunday for you as well.



On Sunday, 13 September 2020 20:47:35 UTC+2, Charlie Veniot wrote:
>
> G'day Felicia,
>
> Hi Charlie,
>>
>> love the concept and very impressiv what you managed to put together, 
>> thank you for sharing.
>>
>
> Thank-you!  Of course, let's keep in mind that, in martial arts terms, I'm 
> not quite a TiddlyWiki yellow belt yet, so I'm sure there are many things 
> that could be improved !
>  
>
>>
>> If you don't mind asking, is there a specific reason for placing the 
>> decision for what to transclude in the two templates themselves and always 
>> calling both of them?
>> Personally I would have put the decision in the root tiddler - e.g. 
>> TiddlyWiki Title - via a match filter and only called what was needed, so I 
>> wonder if there is something I am missing/not thinking about or if it is 
>> just another case of multiple ways to achieve the same result.
>>
>
> I suspect that you are talking about this way of deciding what to show 
> based on context: {{TiddlyWiki Title 1||tPr}}{{TiddlyWiki Title 2||tOg}}
>
> I chose that way of doing things because I'm having a hard time wrapping 
> my mind around filters, but I think I've got transclusion templates down 
> pat.
>
> So I saw that mechanism as a quick (and non-cryptic) and easily repeatable 
> method across the board, for example:
>
>- the "content" tiddler (included in my "navigation" tiddler that 
>shows in the sidebar) has {{Contents (Product Reviews)||tPr}}{{Contents 
>(Urban Off Gridding)||tOg}} to show different navigation links depending 
> on 
>context
>- I may want to show other tiddlers different ways depending on 
>context ...
>
>
>
>> Oh and one thing I noticed, just as an info: Since getstartupcontext is a 
>> javascript macro you don't actually need to import it. Unlike normal macros 
>> javascript macros are always global.
>>
>
> Maybe I misunderstood something when I put that import there.  I thought 
> that "StartupAction" tiddlers, because they are processed so early, didn't 
> have access to any macros unless they are imported.  Does that just apply 
> to non-javascript macros ?
>  
>
>>
>> Kind Regards,
>> Felicia
>>
>
> Cheers, best regards, and Happy Sunday !
>  
>

-- 
You received this message because you are subscribed to the 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/15e8d240-7c8d-44cf-83f9-341563982ffbo%40googlegroups.com.

[tw5] Re: Cross-link multiple wikis

2020-09-13 Thread tony

>any "elegant" solution how to create links between tiddlers in different 
wikis.

tl;dr so far ... LocalSearchEngine 
 + 
iframe internal wiki(s) + dragging permalinks (or right click copy link 
address)

I've been ruminating over the same thing as performance has been degrading 
as my main wiki gets bloated in tiddler quantity (~3.5K count)

My issue is overloading with all tiddlers in one wiki; in my case: planning 
scheduling tiddlers (stuff i do) with note tiddlers (stuff i reference) + 
playing plugins

FWIW My even more lazy inelegant dirtier solution :-) 

I've been using Duarte's Local Search Engine 
 (LSE) 
method + InnerWiki + dragging permalinks 
 between wikis

   - Under chrome://settings/searchEngines my LSE is searchengine: 
   wikiserver; keyword: wiki; url:
   http://localhost:8080/myfolder/wiki.html#:[!is[system]search[%s]]
   - Easy and simple as: Ctrl-l to get address bar focus + wiki + searchterm
   - And/or drag and drop from InnerWiki [1]

The workflow reduced alot of cognitive friction when the wikis are housed 
in 1 folder as in TiddlyServer  
and LSEs can be assigned per wiki(s).  And really has changed the way i 
view wiki state with wiki.html as a more temporary pool collection versus a 
more permanent document/database/wiki/thing
I look forward to more simple and creative solutions from others! But for 
me, the hard part is semantic chunking of wikis which is not a technical 
issue :-\

Best,
tony

[1] Host your inner wiki (latest toy)
   
   - i dont use the InnerWikiPlugin 
     as it is over my 
   lazy head and too complicated for my setup, YMMV 
   - Create a new tiddler with the name of your wiki, say KnowledgeBase
   - add an iframe in the tiddler body text 
   - where src = the path to you wiki, KnowledgeBase.html
   - The rendered tiddler will have the InnerWiki and right-click on most 
   OS will allow for permalink copy to paste in the HostWiki, both absolute 
   and relative linking works or just drag and drop with Optionally display 
   tiddler titles as links 
    = yes
   - Formal clean up can come later...
   - absolute link: 
   
[ext[link|http://localhost:8080/KnowledgeBase.html#post%20solution%20for%20cross%20links]
   - relative link: 
   [ext[link|./KnowledgeBase.html#post%20solution%20for%20cross%20links]]
   - usually I just work and save in the InnerWiki directly 
   - What's crazy is the InnerWiki operates independently with direct 
   access but can open directly in another tab and i drag and drop 
   TiddlerLinks between the OuterWiki host and InnerWiki

On Sunday, September 13, 2020 at 3:29:22 AM UTC-7 Victor Dorneanu wrote:

> I don't know if this topic has been discussed somewhere else, but I'd like 
> to know if there is any "elegant" solution how to create links between 
> tiddlers in different wikis. 
>
> I've recently found Tobi Beer's quick'n'dirty solution 
>  which uses several macros to 
> have something like:
>
> <<. docs Documentation>>
>
> to link to a tiddler called "Documentation" in the "docs" wiki. If you 
> look at *$:/editions/docs *you'll see a "src" field where the location of 
> the wiki is specified (in that case docs.html). 
>
> I use the same approach for my personal Zettelkasten 
>  where I have:
>
> 1) one TW instance (single HTML file) for the knowledge base
> 2) one TW instance (single HTML file) for bibliography and sources (web 
> articles etc.)
>
> Are there any other ways to implement this? Thanks in advance. 
>
> KR, 
> Victor 
>

-- 
You received this message because you are subscribed to the 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/a5754c9c-f6ea-4dbd-8ae0-d3cecf525dfen%40googlegroups.com.

[tw5] Question about Refrences and Macros

2020-09-13 Thread Huntsfromshadow

Question about Reference List and Macros.

I have the following Setup.

1 - Tiddler 1 that has some random Text.
2 - Tiddler 2 that has [[Tiddler 1]] in it.

Tiddler 1 shows that Tiddler 2 refrences it (and thus isn't on the Orphan 
list).

If I replace the text in Tiddler 2 with
\define testme()
[[Tiddler 1]]
\end

<>

Tiddler 1 doesn't show any refrences to it (and thus is in the Orphan List).


Is this expected? Anyway to have the macro still report as a refrence?

Thanks
-Luke

-- 
You received this message because you are subscribed to the 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/e076a4ad-81a7-470c-943e-1fffc558cf76n%40googlegroups.com.

[tw5] Re: Change the transclusion view template

2020-09-13 Thread PMario

On Sunday, September 13, 2020 at 7:59:57 AM UTC+2, kebi wrote:
>
> Didn't know you could use templates with the transclusion function.
> My problems are now solved, thanks Mario!
>

Good :) Thx for the feedback.
-m

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/513d28ae-f63c-447f-9a71-63bea5b308feo%40googlegroups.com.

[tw5] Re: Dynamic css and transcluding

2020-09-13 Thread PMario

On Sunday, September 13, 2020 at 3:20:50 PM UTC+2, amreus wrote:
>
> Mario. This is the greatest example, thanks.
>

Cool that you liked it :) It's always a pleasure to see, that other users 
take those examples and use them in new ways!
 

> I've made a similar example here 
> 
> .
>

Thanks for sharing it! 
 

> In short this is customizing the view of a tiddler's fields via a 
> template, and applying a style based on the tiddler's tags. Elegant and 
> powerful  
>

That's right. TiddlyWiki offers a lot of powerful utilities. ... That's 
what I like!
 
-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/db720d80-7d94-4d2c-922a-cb6115c56597o%40googlegroups.com.

[tw5] Re: Proof of Concept: Dynamic Global Variables

2020-09-13 Thread Mat

@Felicia

Thank you for this! I can believe it will be useful ... but I'm wondering 
why I didn't need it thus far. Are there cases that usually can't be 
accomplished, or with much difficulty, that your creation solves better? 
(Maybe I should ask Tony) I also imagine it's one of those things that were 
at one time, early on, decided against for some secuity reasons - anybody 
knows?


<:-)

-- 
You received this message because you are subscribed to the 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/dc026f84-29b3-4d57-9f70-6bbd0b8a7eebo%40googlegroups.com.

[tw5] Re: Proof of Concept: Dynamic Global Variables

2020-09-13 Thread PMario

On Sunday, September 13, 2020 at 4:50:14 PM UTC+2, Felicia Crow wrote:

after Tony has asked about it in another thread and taking far longer than 
> planned 
>

Hi Felicia, 

Interesting! ... Can you provide a link to the initial discussion, that 
triggered this functionality?

-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/1ac70c22-23f8-46e0-b562-1a437291bbf6o%40googlegroups.com.

[tw5] Re: Proof of Concept: Dynamic Global Variables

Saq,
yes somewhat, just for now without the ability to set where it saves. I 
drew the comparsion to set since what it is at the end of the day is the 
set widget just with a change to where it saves the value.

The thing is I at first wanted a user defined save location, but through 
tests I learned that the function I use to write the indexes to the tiddler 
needs the tiddler it writes to to actually to exist. So I decided to finish 
a first working proof of concept and expand this type of functionality in 
later revisions since I have to implement a fall back that creates a 
tiddler if it isn't there or at least gives the user a clear message that 
the set failed, because of the tiddler not existing.

As for the the prefixed tiddlers you are right this was more a result from 
me wanting everything in one place during development.
Although I would wish there was $:/data as this is neither necessarily 
temporary - I do wish to keep a saved beyond closing the wiki possibility 
should someone find a way to find it useful - or a state in the way it is 
apparently normally used within tiddlywiki, but from the next iteration 
onwards I will move it to $:/state.

Thanks for looking over it and giving feedback.

Kind Regards,
Felicia

On Sunday, 13 September 2020 17:56:32 UTC+2, Saq Imtiaz wrote:
>
> Interesting implementation, thanks for sharing. 
>
> It's a bit like an action-setfield widget that doesn't need a trigger. 
>
> I've only had the most cursory look, but you could allow an optional 
> widget parameter that determines the storage tiddler, allowing restricting 
> scope where desired.
> Perhaps also consider using a $:/temp.. or $:/state... prefixed tiddler 
> for the storage.
>
> Cheers,
> Saq
>
> On Sunday, September 13, 2020 at 4:50:14 PM UTC+2, Felicia Crow wrote:
>>
>> Hi,
>>
>> after Tony has asked about it in another thread and taking far longer 
>> than planned - trying to reinvent the wheel is maybe not the best solution 
>> - I finally finished a first proof of concept for dynamic global variables.
>>
>> What this basically does is it adds a widget that works like set, just 
>> without the scope restrictions. So variables set with it can be used in the 
>> same tiddler further down or in another tiddler altogether.
>> I also added a custom filter operator to make it easier to access the 
>> variable values within a filter.
>>
>> The attached wiki contains basic examples for how to use the 
>> widget/operator, while the json is there to make it easier to import it 
>> into your own wikis.
>>
>> Usual Disclaimer: This is a very basic proof of concept not a finished 
>> plugin so while I am happy if people try it out and give feedback/develop 
>> it further I consider it very much use at your own risk.
>>
>> Kind Regards,
>> Felicia
>>
>

-- 
You received this message because you are subscribed to the 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/4560a830-b568-44ef-83ea-ed411357c6dco%40googlegroups.com.

[tw5] Re: How To: altering TiddlyWiki appearance based on context (URL parameters at StartUp, and via radio buttons after StartUp)

G'day Felicia,

Hi Charlie,
>
> love the concept and very impressiv what you managed to put together, 
> thank you for sharing.
>

Thank-you!  Of course, let's keep in mind that, in martial arts terms, I'm 
not quite a TiddlyWiki yellow belt yet, so I'm sure there are many things 
that could be improved !
 

>
> If you don't mind asking, is there a specific reason for placing the 
> decision for what to transclude in the two templates themselves and always 
> calling both of them?
> Personally I would have put the decision in the root tiddler - e.g. 
> TiddlyWiki Title - via a match filter and only called what was needed, so I 
> wonder if there is something I am missing/not thinking about or if it is 
> just another case of multiple ways to achieve the same result.
>

I suspect that you are talking about this way of deciding what to show 
based on context: {{TiddlyWiki Title 1||tPr}}{{TiddlyWiki Title 2||tOg}}

I chose that way of doing things because I'm having a hard time wrapping my 
mind around filters, but I think I've got transclusion templates down pat.

So I saw that mechanism as a quick (and non-cryptic) and easily repeatable 
method across the board, for example:

   - the "content" tiddler (included in my "navigation" tiddler that shows 
   in the sidebar) has {{Contents (Product Reviews)||tPr}}{{Contents (Urban 
   Off Gridding)||tOg}} to show different navigation links depending on context
   - I may want to show other tiddlers different ways depending on context 
   ...



> Oh and one thing I noticed, just as an info: Since getstartupcontext is a 
> javascript macro you don't actually need to import it. Unlike normal macros 
> javascript macros are always global.
>

Maybe I misunderstood something when I put that import there.  I thought 
that "StartupAction" tiddlers, because they are processed so early, didn't 
have access to any macros unless they are imported.  Does that just apply 
to non-javascript macros ?
 

>
> Kind Regards,
> Felicia
>

Cheers, best regards, and Happy Sunday !
 

-- 
You received this message because you are subscribed to the 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/0ca18771-5214-457c-ac67-952e4942241bn%40googlegroups.com.

[tw5] Re: Proof of Concept: Dynamic Global Variables

2020-09-13 Thread Saq Imtiaz

Interesting implementation, thanks for sharing. 

It's a bit like an action-setfield widget that doesn't need a trigger. 

I've only had the most cursory look, but you could allow an optional widget 
parameter that determines the storage tiddler, allowing restricting scope 
where desired.
Perhaps also consider using a $:/temp.. or $:/state... prefixed tiddler for 
the storage.

Cheers,
Saq

On Sunday, September 13, 2020 at 4:50:14 PM UTC+2, Felicia Crow wrote:
>
> Hi,
>
> after Tony has asked about it in another thread and taking far longer than 
> planned - trying to reinvent the wheel is maybe not the best solution - I 
> finally finished a first proof of concept for dynamic global variables.
>
> What this basically does is it adds a widget that works like set, just 
> without the scope restrictions. So variables set with it can be used in the 
> same tiddler further down or in another tiddler altogether.
> I also added a custom filter operator to make it easier to access the 
> variable values within a filter.
>
> The attached wiki contains basic examples for how to use the 
> widget/operator, while the json is there to make it easier to import it 
> into your own wikis.
>
> Usual Disclaimer: This is a very basic proof of concept not a finished 
> plugin so while I am happy if people try it out and give feedback/develop 
> it further I consider it very much use at your own risk.
>
> Kind Regards,
> Felicia
>

-- 
You received this message because you are subscribed to the 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/39e4c290-f70f-4caf-b64d-8498e17862e9o%40googlegroups.com.

[tw5] Re: Dynamic css and transcluding

2020-09-13 Thread amreus

Mario. This is the greatest example, thanks.

I've made a similar example here 

.

In short this is customizing the view of a tiddler's fields via a template, 
and applying a style based on the tiddler's tags. Elegant and powerful  

Internally I have been using the terms "inline template" or (borrowing from 
Ruby on Rails)  "partial" template because the template is showing just a 
part of the tiddler. I'm not sure if that's a helpful way to think of it.

But thanks again for the example.

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

Re: [tw5] Re: TW5 top toolbar 6.19 - Tagging in view mode broken

2020-09-13 Thread Cyneox

I've also tried first the plugin page.. On my Desktop system I've used
Firefox. On my smartphone I've tried Firefox, Ecosia browser and Chrome.
None of them worked.



On Sun, Sep 13, 2020, 13:53 Birthe C  wrote:

> As far as I can see  http://tw5toolbar.tiddlyspot.com/ is version 5.1.22
> and the toggle tagging button works there.
> It also works in my own wiki. Maybe you made other changes to your wiki?
>
> Birthe
>
> --
> 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/ar50CZXVHpA/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> tiddlywiki+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/tiddlywiki/34237db5-c2bb-4f56-a2e5-b77d0ab25e1bo%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/CAO%3DLbP7AWBK2gEY_aj_dqPyJD-_uTTUFCaJ9WjXHig7HBaGvug%40mail.gmail.com.

[tw5] Re: [off topic] why do people want a static tiddlywiki?

2020-09-13 Thread David Gifford

Static = flat webpage. If you want to go to another resource you leave the 
page. TiddlyWiki is not static in that it has tiddlers that can be opened 
and closed without leaving the page.

As bmad said, one plus is that flat webpages are easier for non-TiddlyWiki 
users to wrap their head around. A series of static pages functions like a 
typical wiki, like Wikipedia, without confusing new users.

And as bmad said, another benefit is for search engine optimization, so the 
content someone publishes has a chance of getting added to Google (and 
other search engine) search results.

On Sunday, September 13, 2020 at 3:19:53 AM UTC-5 Ste wrote:

> Coming from a place of ignorance.. 
> Why are so many people keen to change tiddlywiki into a static site? What 
> are the advantages? 
> Is tiddlywiki not a static site? What's the difference? 

-- 
You received this message because you are subscribed to the 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/b55af32b-fbc9-4fda-89f9-8aad77cd72f9n%40googlegroups.com.

[tw5] Re: TiddlyWiki toolmap submissions

2020-09-13 Thread David Gifford

I added both versions on one line of the toolmap, here: 
https://dynalist.io/d/zUP-nIWu2FFoXH-oM7L7d9DM#z=KD7kUsUIFmx3Us0teMLUILMI

Thanks for catching this! Happy to add overlooked items as people point 
them out to me.

On Sunday, September 13, 2020 at 6:25:16 AM UTC-5 strikke...@gmail.com 
wrote:

>  Tobias Beer mentions GSD5 and the datepicker, but the GSD5 wiki and the 
> datepicker was created by Roma Hicks as far as I remember.
> Link for the wiki with the datepicker http://gsd5.tiddlyspot.com/
> A later version of the wiki can be found here: 
> https://gitlab.com/gsd5-tiddlywiki
>
> Birthe
>

-- 
You received this message because you are subscribed to the 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/4b78beaf-7e1e-47f9-9a7a-275803eb7067n%40googlegroups.com.

[tw5] Re: TW5 top toolbar 6.19 - Tagging in view mode broken

2020-09-13 Thread Birthe C

As far as I can see  http://tw5toolbar.tiddlyspot.com/ is version 5.1.22 
and the toggle tagging button works there.
It also works in my own wiki. Maybe you made other changes to your wiki?

Birthe

-- 
You received this message because you are subscribed to the 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/34237db5-c2bb-4f56-a2e5-b77d0ab25e1bo%40googlegroups.com.

[tw5] Re: [Tiddly Research] Public release

2020-09-13 Thread SizzlinSJ


>
> I tried to do this before but I couldn't find a way to integrate the 
> context plugin (the one that Freelinks uses for highlighs) with the preview 
> tiddler plugin.
> Hopefully word highlightning will become a feature in tiddlywiki in the 
> future.
>
I tried installing this(attachment) version of freelinks and checked 
"Enable freelinking within tiddler view templates" option which seems to 
work. Being a non programmer I cant confirm if this is how the plugin is 
supposed to work and doesnt clash with other plugins.  

-- 
You received this message because you are subscribed to the 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/21b2c56a-1346-45b1-8096-14490fb65a82n%40googlegroups.com.


$__plugins_tiddlywiki_freelinks.json
Description: application/json

[tw5] Re: TiddlyWiki toolmap submissions

2020-09-13 Thread Birthe C

 Tobias Beer mentions GSD5 and the datepicker, but the GSD5 wiki and the 
datepicker was created by Roma Hicks as far as I remember.
Link for the wiki with the datepicker http://gsd5.tiddlyspot.com/
A later version of the wiki can be found here: 
https://gitlab.com/gsd5-tiddlywiki

Birthe

-- 
You received this message because you are subscribed to the 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/e81b762e-3c09-49b2-946a-90c10d375bb6o%40googlegroups.com.

[tw5] TW5 top toolbar 6.19 - Tagging in view mode broken

2020-09-13 Thread Victor Dorneanu

I'm using Ton Gerners top toolbar  which 
also enables tagging in view mode (by adding buttons to the view page). 
However this functionality doesn't work anymore (tested with TW 5.1.22). 

Any ideas? Thanks

Victor 

-- 
You received this message because you are subscribed to the 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/7a711ebf-231b-4ce5-87b0-2c99ed3d33fdn%40googlegroups.com.

[tw5] Cross-link multiple wikis

2020-09-13 Thread Victor Dorneanu

I don't know if this topic has been discussed somewhere else, but I'd like 
to know if there is any "elegant" solution how to create links between 
tiddlers in different wikis. 

I've recently found Tobi Beer's quick'n'dirty solution 
 which uses several macros to have 
something like:

<<. docs Documentation>>

to link to a tiddler called "Documentation" in the "docs" wiki. If you look 
at *$:/editions/docs *you'll see a "src" field where the location of the 
wiki is specified (in that case docs.html). 

I use the same approach for my personal Zettelkasten  
where I have:

1) one TW instance (single HTML file) for the knowledge base
2) one TW instance (single HTML file) for bibliography and sources (web 
articles etc.)

Are there any other ways to implement this? Thanks in advance. 

KR, 
Victor 

-- 
You received this message because you are subscribed to the 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/4d7e6c46-6c92-4135-bcfb-232f53668d57n%40googlegroups.com.

[tw5] Re: [off topic] why do people want a static tiddlywiki?

2020-09-13 Thread Adithya B

I use TW primarily as a note-taking Zettelkasten like device. It makes 
sense that I write my blogs here as well. And render it to a static site 
(https://adithyab.in/) whenever I feel like.

A traditional static site is more accessible for others and easier for 
search engines to access. TW is not a traditional static website. Its 
different. Ill leave that explanation to others.

On Sunday, September 13, 2020 at 1:49:53 PM UTC+5:30, Ste wrote:
>
> Coming from a place of ignorance.. 
> Why are so many people keen to change tiddlywiki into a static site? What 
> are the advantages? 
> Is tiddlywiki not a static site? What's the difference? 

-- 
You received this message because you are subscribed to the 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/b8ddb53a-004d-4f8f-9faa-9f9c42be6282o%40googlegroups.com.

[tw5] Re: TiddlyWiki toolmap submissions

2020-09-13 Thread amreus

Hi Dave,

Tobias Beer's GSD5 wiki has a datepicker 
 that can 
be dropped into a wiki.  The stylesheet must also be added.  I think it 
ought to be on the list.

-- 
You received this message because you are subscribed to the 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/a63816ea-054f-44ed-a1cc-8219067f9e5en%40googlegroups.com.

[tw5] Re: How many of you use core TiddlyWIki?

2020-09-13 Thread Birthe C

Me too. ;-)

On Sunday, September 13, 2020 at 10:35:31 AM UTC+2, Ste wrote:
>
> I just grab those plugins... Gotta catch em all.. 

-- 
You received this message because you are subscribed to the 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/932d5ede-57b8-44bd-a80f-6cc96c3717d3o%40googlegroups.com.

[tw5] Re: How To: altering TiddlyWiki appearance based on context (URL parameters at StartUp, and via radio buttons after StartUp)