from:"springer"

Jeremy and all,

I've played around with the updated prerelease file, starting by importing 
all the tiddlers from the "broken" version. So far, saves on github are 
going fine.

Only one (!) major glitch. If you name a field with a double-angle-bracket 
expression (Who would do such a thing?!), Shiraz gets confused. (Probably 
other tools would get confused too, but Shiraz is the thing I've been 
testing.)

For one proof-of-concept, I created a little ViewTemplate footer that 
provides a dynamic table overview of any tiddlers that use the current 
tiddler's title as a (non-empty) field name.

I do see some minor glitches with ViewTemplates (contents not looking as 
they should, conditional filters not behaving as they should), but it's 
possible my own limited trouble-shooting skills are to blame. It's also 
possible that some interaction with one or more <> is to blame.

If anyone wants to play around see here: 
https://springerspandrel.github.io/tw/new-json-tw-experiment.html

-Springer
On Thursday, July 22, 2021 at 11:57:34 AM UTC-4 jeremy...@gmail.com wrote:

>
> On 21 Jul 2021, at 21:11, Saq Imtiaz  wrote:
>
> I believe this check for field names is the cause:
>
>
> https://github.com/Jermolene/TiddlyWiki5/blob/d455072f13dd00955ae82d62d2d6e44581bdba9e/boot/boot.js#L1606
>
>
> Thanks for your help with this, the problem with fields with spaces in 
> their names has been resolved here:
>
>
> https://github.com/Jermolene/TiddlyWiki5/commit/19fd5ca5f26f798742e411453b30ad467b101a50
>
> The update will be live at https://tiddlywiki.com/prerelease shortly,
>
> Best wishes
>
> Jeremy
>

-- 
You received this message because you are subscribed to the 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/f46c2fae-b8e0-4571-b325-6930295224cfn%40googlegroups.com.

[tw5] Re: Seeking general feedback on Grok TiddlyWiki

Soren,

I think I'm part of the target audience for Grok TiddlyWiki, despite being 
a long-time user. I have never given myself a systematic approach, and have 
instead always learned whatever bits I need to solve this or that 
problem-at-hand. I'm grateful for your learning tool, and am slowly working 
through it (systematically including nearly all exercises through Chapter 
Four, with skimming and selective reading past that, as I've had less time 
to devote recently). 

The organization seems helpful to me, though like many dabblers I have 
depth in some areas you call "advanced" and deficits in some basics. A few 
early portions feel too elementary for me, but I've worked through them 
anyway, partly to make sure I absorb technical terminology better (where I 
know how to do X but not what the ingredients are called), and partly 
because I am frequently surprised, even in early chapters, by what Tones 
calls the occasional "easter egg" of discovering a new thing.

I did have one frustrating rabbit-hole experience with the RubberDucking 
exercise, but it was anomalous (I was working on a clone of your book, 
which contained an error you have since fixed. On my version, you hadn't 
yet compensated for how you tucked various components into shadows. I 
"fixed" the exercise filter's punctuation correctly, but it still showed 
nothing. My Rubber Duck was not at all helpful until it suggested that I 
dial up the book at your url, where "Eureka!" the actual exercise prompt 
was different. I could email you the details, but it's not of general 
interest.)

I'm pretty sure my skills are improving, especially if I think half of a 
skill is having the right *concepts* for one's skills, and a cogent 
understanding of their scope and limits.

One thing I specifically appreciate is that a search for "boolean" on your 
book brought me to a helpful discussion. I had tried in vain to find 
"boolean" on tiddlywiki.com (where it appears only incidentally around 
"then" and else") and on https://tobibeer.github.io/tw/filters/  ... (Not 
getting any helpful hits at these two spots did make me feel pretty crazy!) 
Finding a direct discussion of how boolean operations need to be 
approached, for filters, is the kind of thing many users might appreciate. 
(Note: I'd add words like "conjunction" and "disjunction" to your 
discussion, to aid searchability. The word "or" is of course unhelpfully 
too short -- with too many false positives -- for those who bring logical 
concepts to TiddlyWiki but aren't yet oriented to its operators.)

-Springer
On Wednesday, July 21, 2021 at 9:56:56 AM UTC-4 Soren Bjornstad wrote:

> Hi everyone,
>
> I know quite a few people on here have been reading at least some of my 
> book Grok TiddlyWiki <https://groktiddlywiki.com/read/>. While I've 
> gotten quite a bit of specific feedback submitted through the built-in 
> feedback mechanism, I've been coming up short on overall impressions and 
> significance beyond "thanks so much for this book." If you've looked at the 
> book and you have a few moments, I'd love to know what you think. For 
> instance:
>
>- Is the book organized effectively?
>- What parts have you read/worked through?
>- How have you been using the book? Have you done some of the 
>exercises and flashcards? Do they work? (I'm particularly interested in 
>this question because I'd love to iterate and build more resources like 
>this one in the future.)
>- How have your TiddlyWiki skills improved, if they have?
>- Any other thoughts?
>
> If there's anything you don't want to share publicly, feel free to email 
> it directly to me at contact (at) sorenbjornstad.com.
>
> Much appreciated,
> Soren
>

-- 
You received this message because you are subscribed to the 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/d684dabc-0b58-41c0-b6c2-0fe6a86c0813n%40googlegroups.com.

[tw5] Re: Getting relink to prevent obsolete permalinks

Tones,

This again is a place where different users may have different needs. I 
love the fact that if I share a permalink, the #TiddlerTitle at the end is 
not an indecipherable UID, but something recognizable and meaningful to the 
recipient (and even to myself, going back into my emails and recognizing 
what I shared). 

And as much as you may "choose my tiddler names well enough when needed so 
they need not change in future",  renaming a tiddler is not always a matter 
of realizing that you failed to have foresight the first time around. (My 
reason for invoking the Bombay to Mumbai change -- or Bruce to Caitlin if 
you prefer -- is that the world *about* which we take and share notes does 
not always cater to our desire for stability. ;)

I do realize that even without changing relink, we could mitigate obsolete 
permalinks (when we are aware of them) by setting up a ViewTemplate that 
works with a "formerly" field (or maybe just with a alias and aliases 
field), to transclude or redirect when the old permalink lands on an 
obsolete tiddler. 

-Springer
On Wednesday, July 21, 2021 at 9:17:10 PM UTC-4 TW Tones wrote:

> Springer et al,
>
> Forgive me for repeating myself, although a lot of interesting ideas, I 
> believe these to be *non-problems.* 
>
> A simple solution is available here. an Example would be an alternate 
> button to simple permalinks, I think someone else used a share icon. When 
> clicking this on a given tiddler, it would assign a next number to a field 
> in the tiddler (basically issuing a unique value field - not a UID or 
> serial or GUID) then use this field/number to uniquely identify the tiddler 
> shared, so it does not matter if it's title is renamed. Then generate a url 
> that instead searches for any (but only one) tiddler with that field value.
>
> If *anyone asks* I will build this share button soon.
>
> That is if someone wants to publish a robust permalink for a tiddler who's 
> title may change they use a built for purpose alternative to permalinks. 
> Perhaps the existing name permalinks is misleading, perhaps they should be 
> impermalinks.
>
> Here is a working example
> a tiddler with the "permalink" field=1
> the url wiki-url.html#:[permalink[1]] 
> In the wiki Open target this 
> can be dragged to bookmarks/favourites
>
> However I personally choose my tiddler names well enough when needed so 
> they need not change in future, and if I am publishing a link somewhere it 
> is to access specific content. the link has a purpose, and once someone has 
> the link the purpose is fixed in time and should always honour its original 
> share.
>
> A version of the above method where the link filter 
> is [has[permalink]last[]] will always link to the largest permalink value, 
> so one is sharing a link to the latest permalink tiddler or post.
>
> Another supportive trick is to hide the field from the editor with a 
> tiddler of the form $:/config/EditTemplateFields/Visibility/fieldname 
> eg $:/config/EditTemplateFields/Visibility/permalink with a value of hide
> thus once set you have to go out of your way to alter the permalink value, 
> that is its more permanent.
>
> Further developments (optional reading)
>
>- Since the addition of the unused title operator, it is possible 
>(more to the point easier) to use this to generate a unique and 
> incremented 
>tiddler title and serial number. 
>- Rather than shadow tiddlers I am using this not only to generate a 
>tiddler Serial Number (TSN) but a "ghost tiddler" that follows any tiddler 
>and provides a way to save metadata for any tiddler or field there in 
>(regardless of the title)
>- My only issues left are 
>   - Finding a way to generate/assign such TSN and Ghost tiddler in 
>   bulk.
>   - rebuild a parallel solution - system serial number, to assign a 
>   serial number to core and shadow tiddlers without touching them
>- Actually I have found you need only assign serial number where to 
>need them, say for these permalinks or compound tiddlers, that is with 
>subtiddlers that use the serial number for the parent rather than the 
> title 
>or a tag.
>
> Regards
> Tones
>
> On Thursday, 22 July 2021 at 06:50:01 UTC+10 springer wrote:
>
>> About obsolete permalinks: 
>>
>> Surely a variant of the relink plugin could help maintain bread-crumbs 
>> for obsolete links:
>>
>> Whenever relink does its thing, have it offer to create a 
>> dictionary-tiddler entry pairing old-name and new-name; then have a 
>> filter-condition ViewTemplate element show up at the bottom of old-name 
>> tiddlers, where the new-name tiddler is transcluded (or linked-to) --

Re: [tw5] I broke the json pre-release :|

Tones and Mario,

For public-facing projects, being able to name tiddlers with natural 
language expressions (including spaces) has been essential, and it seems 
much of the expanded power of fields in 5.2.0 will come from scanning for 
matches between field names and tiddler titles. 

(Emojis and such may seem trivial, but certain specialized unicode 
characters like Σ, plus expressions in two-byte languages like 字, are 
surely going to be leveraged by a significant user base as well.)

So, as much as it may seem logical to stick to CamelCase titles and 
a-z_special.string fieldnames for certain users, it seems the 
flexible-field-names horse is going to be galloping out of the barn as soon 
as the new version is available.

Might we figure out some way to test the compatibility of existing plugins 
(such as Shiraz) more systematically than by trial and error?

-Springer

On Thursday, July 22, 2021 at 12:24:46 AM UTC-4 TW Tones wrote:

> Mario,
>
> I am glad someone concurs. For me with my de facto standards and the new 
> freedom, if a field name looks like a tiddler title it possibly is.
>
> Do you think many ancient and / or unsupported plugins will break?,. if 
> they use fields even extensively the issue will only be if they are used 
> against new fieldname standards. And until now at least we tended to honour 
> any values if not fieldnames.
>
> I will be honest though few if any system tiddlers I create have spaces or 
> quotes of any kind. even tags are usually single text strings, and I do 
> think I will stick to this, as it simplifies code. but yes, use it when the 
> exception makes sense.
>
> I have not yet considered what we may achieve by having field names that 
> can be wikified into something else, but again I personally intend to 
> proceed with caution. Perhaps the documentation can give some advice to 
> this effect, for example currently the fieldname restrictions help us when 
> generating csv files and if field names (and values) contain spaces, or 
> commas and quotes this may no longer be true. The documentation should 
> continue to list the previous limited naming standards as well. 
>
> I must say I also have de facto naming standards for titles even although 
> they are quite flexible, in fact most that I code follow a simple and 
> limited range. I like to leave the flexibility for when its needed. The one 
> exception is when a title is also textual content like a sentence or 
> paragraph.
>
> Regards
> Tones
> On Thursday, 22 July 2021 at 13:56:18 UTC+10 PMario wrote:
>
>> On Thursday, July 22, 2021 at 3:24:54 AM UTC+2 TW Tones wrote:
>>  
>>
>>> However am I the only one who still intends to keep field names to a 
>>> defacto naming standard such as i-am-afield no caps or spaces? so It is 
>>> easy for me to tell field names apart from text and titles!
>>>
>>
>> No -- you are not.
>>  
>>
>>> Of course I look forward to naming fields using tiddler titles (and the 
>>> value a relationship type etc..). and to contain special prefixes or 
>>> suffixes such as "-link" or (link)  but as a rule I would like a little 
>>> structure and naming rules. 
>>>
>>
>> You wrote, you want to have tiddler titles as field names. So your 
>> field-rules have to be the same or a superset of your title rules. I would 
>> be surprised, if "no caps or spaces" is one of them. 
>>  
>>
>>> This always helps retain a degree of simplicity when managing lots of 
>>> complexity.
>>>
>>
>> Oh it will be funny, to deal with all the support requests here in the 
>> group, because some ancient and / or unsupported plugins will break. ... 
>> I'm not even sure, what my own plugins will do with "spaces" in field 
>> names. ...  I will have to check that. 
>>
>> have fun!
>> mario
>>
>

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

[tw5] Re: RFC: Building a macro solution for top-to-botton

2021-07-21 Thread springer

Tones,

I look forward to checking out the focus tiddler tool. Does it already 
exist in some public form? (If so, sorry I missed it.)

I agree that there are lots of different workflows that might call for 
variations / different priorities.

-Springer



On Monday, July 19, 2021 at 8:04:21 PM UTC-4 TW Tones wrote:

> Springer,
>
> Thanks for that insight. I built a separate tool called focus tiddler ie 
> the tiddler with user focus, it included something like Erics History tab, 
> but also as I mentioned in the original post allow us "navigate to the last 
> opened or edited tiddler". In my (as yet unpublished) focus tiddler 
> solution (not that I was proposing here) I had a viewToolbar button (could 
> be in edit as well) to override the last opened or edited tiddler, that is 
> make any tiddler in the story the focused tiddler. Your feed back makes me 
> ask if perhaps allow selecting secondary tiddler as say the "focused work 
> tiddler" and that what ever the navigation activity "the last opened or 
> edited tiddler", that it would be easy to return to the "focused work 
> tiddler". ie the one where one is taking notes or reading to manage your 
> work flow (eg syllabus or class notes).
>
> I too use the classic story view as a rule, finding the others 
> frustrating, as a result I know little about their use. 
>
> My learnings from your reply include
>
>- Your desire to go back - I will look at incorporating that.
>   - the history tab helps here.
>   - I wonder the best way to select the tiddler to go back to (not 
>   just the last)
>- Getting keyboard shortcuts for any navigational component )inc top 
>and bottom story and sidebar)
>   - I would like to add a keyboard short cut to wikitext buttons I 
>   define - not sure how yet.
>- Would it be important to reopen a  "focused work tiddler" if closed?
>   - Then you could close all, display something then return.
>- Perhaps use a modifier to a shortcut to open/reopen a  "focused work 
>tiddler" for edit, 
>
> In closing, my focused tiddler method will go some way to meeting your 
> requirement, using the history tab will help even further, but you need 
> that tab displayed on the sidebar. The history tab is refreshed each Wiki 
> session (reload), this is something to do before a "class or presentation" 
> because you can easily return to a tiddler you opened during the session, 
> the list is limited to those you have opened or edited which is helpful.
>
> Regards
> Tones
>
> On Tuesday, 20 July 2021 at 06:03:12 UTC+10 springer wrote:
>
>> Tones,
>>
>> For "top to bottom": The most useful navigational add-ins, for my 
>> use-cases, are keyboard-driven. When desired tiddlers are scrolled out of 
>> view *and* this feels like an especially distracting obstacle (say, because 
>> I'm teaching, and wish to resume the prior discussion after jumping to a 
>> tangent), having to coordinate with the cursor is half the battle. 
>>
>> For various reasons, the "classic" story view (rather than pop or zoomin) 
>> is what I usually choose... but I wonder whether it would be possible to 
>> get the best of both worlds: allow multiple tiddlers in the story view, but 
>> "go back" to most recently active place in the story-river (other open 
>> tiddler in which most recent click happened if possible, or most recently 
>> opened from sidebar if not) when I close something? That's probably beyond 
>> what you're developing, but just one related hankering.
>>
>> -Springer
>>
>> On Monday, July 19, 2021 at 9:44:22 AM UTC-4 TW Tones wrote:
>>
>>>
>>> Folks,
>>>
>>> I just wanted to share that as I happen to be under a "stay at home" 
>>> order in Sydney because of a covid-19 D strain outbreak, I have being 
>>> focusing on some tiddlywiki tools development. I have one large project, 
>>> but while working on that it spawns a lot of little tools, born from the 
>>> innovation and my experience using tiddlywiki a lot, that tiddlywiki always 
>>> inspires in me.
>>>
>>> I thought I would issue an RFC or "request for comment" on my little 
>>> project called "top to bottom"
>>>
>>> I am designing a set of tools so you can easily navigate from the top to 
>>> bottom, also bottom to top, of the story with a single click, also to the 
>>> top of the side bar if you have a long one. It also uses a little trick to 
>>> ensure the last tiddler (especially if little) appears at the top of the 
&

[tw5] Re: RFC: Building a macro solution for top-to-botton

2021-07-21 Thread springer

Eric,

Wow, having the history in the toolbar (without needing sidebar open) is 
likely to do most of what I need, though it's still mouse-driven. I could 
even imagine making a variant that *closes* the current tiddler while 
returning to some prior tiddler. So I'm likely to include it in 
presentation-oriented solutions, where it's important to minimize those 
fumbling moments, however brief, of scrolling and muttering "So... as we 
were saying just a moment ago ..." To some extent, the "jump" menu (stashed 
up near sidebar-collapse button) was filling this gap for me, though it 
only includes open tiddlers, and sometimes I waver over whether or not I 
had actually closed some tidbit that we suddenly need to re-visit. 

-Springer

On Monday, July 19, 2021 at 5:05:37 PM UTC-4 Eric Shulman wrote:

> On Monday, July 19, 2021 at 1:03:12 PM UTC-7 springer wrote:
>
>> I wonder whether it would be possible to get the best of both worlds: 
>> allow multiple tiddlers in the story view, but "go back" to most recently 
>> active place in the story-river (other open tiddler in which most recent 
>> click happened if possible, or most recently opened from sidebar if not) 
>>
>
> Give this a try:
> http://tiddlytools.com/InsideTW/#TiddlyTools%2FHistory
> which adds a "History" command button to the tiddler toolbar.
>
> To install, just grab the tiddler's title, then drag-and drop it into your 
> document.  Although the interaction doesn't exactly match your wish list 
> (it uses a popup dialog and has no keyboard control... yet), it *does* make 
> it much easier to jump around in the Story view without having to manually 
> scroll back to where you were.  There's also these two extra toolbar 
> buttons that bypass the the popup dialog and simply navigate to the 
> corresponding tiddler with just one click.
> http://tiddlytools.com/InsideTW/#TiddlyTools%2FHistory%2FPrevious
> http://tiddlytools.com/InsideTW/#TiddlyTools%2FHistory%2FNext
>
> 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/e1b13113-edc5-4ab4-9b0a-208b7fb0a817n%40googlegroups.com.

[tw5] Getting relink to prevent obsolete permalinks

2021-07-21 Thread springer

About obsolete permalinks: 

Surely a variant of the relink plugin could help maintain bread-crumbs for 
obsolete links:

Whenever relink does its thing, have it offer to create a 
dictionary-tiddler entry pairing old-name and new-name; then have a 
filter-condition ViewTemplate element show up at the bottom of old-name 
tiddlers, where the new-name tiddler is transcluded (or linked-to) -- 
perhaps pre-pending a note explaining that the old "Bombay" is now called 
"Mumbai"...

At first, I was worried about the case where I change tiddler title from 
"Bombay" to "Mumbai" and then later generate a different one called 
"Bombay" -- but there, too, I might be interested in seeing such a 
ViewTemplate addition! After all, if I ever had shared a permalink to 
#Bombay, some signposts around the changing namescape could be useful!

-Springer

On Tuesday, July 20, 2021 at 9:09:07 AM UTC-4 cj.v...@gmail.com wrote:

> This is such an awesome thread.
>
> On Tuesday, July 20, 2021 at 9:04:07 AM UTC-3 Soren Bjornstad wrote:
>
>> *Walt,* the thing that bugs me most about the “immutable title/ID” idea 
>> is that unless your notes are also going to be immutable, the *content* of 
>> a note can still change so much as to make the reference not effective 
>> anymore. So I don't see much point in bothering, as long as you can avoid 
>> having links break. Presumably the thing you were looking for won't move so 
>> far away from the updated note that you'll be unable to find it, anyway 
>> (probably not more than one link away).
>>
>>
> Hence why I have an awful lot of love for relink.  I would have a rough 
> time without it.  No broken (internal links) with Relink.
>  
>
>> It is a good point on external links breaking, though. It would be cool 
>> if you could set up redirects within TW, so that you could at least have an 
>> incoming link to an old title go somewhere somewhat relevant. I guess you 
>> could just leave the old title with a link to the new one, but without an 
>> obvious way to distinguish redirect tiddlers from other tiddlers, they 
>> would probably get in your way and make you think they were the “real” 
>> tiddlers all the time.
>>
>>
> Link rot.  Redirects is a possibility.  I much prefer UID fields and 
> providing links to a Tiddler in some TiddlyWiki with a "UID" reference.  
> (related thread: A Prototype of UID's for stable permalinks 
> <https://groups.google.com/g/tiddlywiki/c/l2Mwu3pOAXw/m/fuvWrwpDBwAJ>)
>
> So if I want to provide folk with a link to a specific tiddler in some 
> TiddlyWiki, in a way that allows me to change the tiddler title willy-nilly 
> without breaking the link, I would give folk this:
>
>  
> https://tiddlywiki-programming.neocities.org/CJ_TiddlyWikiProgramming.html#:[uid[2]]
>  
> <https://tiddlywiki-programming.neocities.org/CJ_TiddlyWikiProgramming.html#:[uid[2]]>
>
> For some reason, I prefer this than setting up redirects.  
>
>

-- 
You received this message because you are subscribed to the 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/c4a1eeb4-d9db-4766-ae18-67dc82a0dbc7n%40googlegroups.com.

[tw5] Re: Two problems with macro: displaying and refreshing

2021-07-20 Thread springer

Misterel,

I am *not* the expert; others could probably write the code you need in 60 
seconds. But since nobody else has answered, and understanding your task 
and its problems demands some time and attention, I'll offer one nudge to 
start...

It seems you want your macro to count (and then display one summary line 
for) each of the CURRENT tiddler's fields that start with ref_ -- Is that 
correct?

Instead, your macro is counting (and then displaying one summary line for) 
every field in your whole wiki that begins with ref_

Try pasting your code (with the variable filled in) and this alternate 
code, into your Exercice1 tiddler. Your code yields 5, because the whole 
project had five ref_ fields; but beginning your filter with [all[current] 
gets you the number you want.

First segment of your existing macro's code (specifying the prefix):
<$set name="fieldCount" filter="[fields[]prefix[ref_]count[]]">
<$text text={{{ [match[0]then[Pas de ]else] }}} />
<$text text={{{ [!match[1]then[sources :]else[source :]] }}} />


Better:
<$set name="fieldCount" filter="[all[current]fields[]prefix[ref_]count[]]">
<$text text={{{ [match[0]then[Pas de ]else] }}} />
<$text text={{{ [!match[1]then[sources :]else[source :]]  }}} />


All I'm doing here is the technique in https://groktiddlywiki.com/read/

That is: breaking down a complex problem into smaller bits, and getting 
your macro to count right *before* trying to set it up in the ViewTemplate 
with an additional variable for the prefix and an additional condition for 
displaysource[yes].  

Alas, I need to switch to other tasks, but I hope you're on the road to 
getting the behavior you need.

-Springer

On Monday, July 19, 2021 at 11:08:53 AM UTC-4 Misterel85 wrote:

> Hi,
> I'm back to work on a TiddlyWiki to manage my collection of drama 
> exercises, but I came across 2 problems with displaying their sources and 
> refreshing that display.
>
> Problem #1:
>
> My 'exercises' tiddlers all refer to a 'SourceDisplay' macro to show the 
> sources.
> If I use a field to trigger the macro to show or hide the sources, they 
> appear in 'Exercise1' tiddler, but not in 'Exercise2'. If I paste 
> <> in the text field of each of the Exercise 
> tiddlers, it works fine.
> I suppose something like 'qualify' might solve the trick, but I don't know 
> how to use it. Perhaps any of you has a better solution to suggest anyway, 
> but I can make do with copying-pasting the macro call.
>
> Problem #2 (more serious to me):
> I changed the contents and title of tiddler "source1" to a more realistic 
> name ('Dramaction' here) and contents and updated the the fields 
> accordingly.
>
> I made 4 dummy source tiddlers. When I deleted the 'ref_source1' field in 
> 'Exercise1' and replaced it with a 'ref_dramaction' field, I also noticed 
> that there were now 4 sources in the list instead of 3. One line is blank, 
> which I suppose is the ghost of 'source1', without any data, of course, 
> since that content doesn't exist any more. It's as if old 'source1' data 
> wasn't purged, or TW still expected that content to exist alongside the new 
> 'dramaction' content. It also happens every time I delete one of those 
> fields.
>
> Also, when I delete the 'ref_source1' field in 'Exercise2', the list of 
> sources gets updated in 'Exercise1', but not in Exercise2, which showed the 
> same problem as in the previous paragraph.
>
> Thanks in advance for your help.
>
>
> Here is the link to a MWE you can download, to see what I mean:
>
>
> https://u.pcloud.link/publink/show?code=XZmdnCXZmtUJk3s4tCfxvYwlXQmYnXrL8RJV
>
> And below is the macro I am talking about:
>
> ```
> \define SourceDisplay(prefix:"")
> <$set name="fieldCount" filter="[fields[]prefix[$prefix$]count[]]">
> <$text text={{{ [match[0]then[Pas de ]else] }}} />
> <$text text={{{ [!match[1]then[sources :]else[source :]]  }}} 
> />
> 
> 
> 
> <$list filter="[fields[]prefix[$prefix$]sort[title]]" variable="fieldName">
> 
> <$transclude field=<>/>
> 
> 
> 
> 
> \end
> ```
>
>

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

[tw5] Re: RFC: Building a macro solution for top-to-botton

2021-07-19 Thread springer

Tones,

For "top to bottom": The most useful navigational add-ins, for my 
use-cases, are keyboard-driven. When desired tiddlers are scrolled out of 
view *and* this feels like an especially distracting obstacle (say, because 
I'm teaching, and wish to resume the prior discussion after jumping to a 
tangent), having to coordinate with the cursor is half the battle. 

For various reasons, the "classic" story view (rather than pop or zoomin) 
is what I usually choose... but I wonder whether it would be possible to 
get the best of both worlds: allow multiple tiddlers in the story view, but 
"go back" to most recently active place in the story-river (other open 
tiddler in which most recent click happened if possible, or most recently 
opened from sidebar if not) when I close something? That's probably beyond 
what you're developing, but just one related hankering.

-Springer

On Monday, July 19, 2021 at 9:44:22 AM UTC-4 TW Tones wrote:

>
> Folks,
>
> I just wanted to share that as I happen to be under a "stay at home" order 
> in Sydney because of a covid-19 D strain outbreak, I have being focusing on 
> some tiddlywiki tools development. I have one large project, but while 
> working on that it spawns a lot of little tools, born from the innovation 
> and my experience using tiddlywiki a lot, that tiddlywiki always inspires 
> in me.
>
> I thought I would issue an RFC or "request for comment" on my little 
> project called "top to bottom"
>
> I am designing a set of tools so you can easily navigate from the top to 
> bottom, also bottom to top, of the story with a single click, also to the 
> top of the side bar if you have a long one. It also uses a little trick to 
> ensure the last tiddler (especially if little) appears at the top of the 
> page if you navigate to it (rather than appearing at the bottom with 
> previous tiddler above it.
>
> These seem trivial but they can improve your work flow and navigation 
> speed if you have a number of tiddlers open.
>
> However this is where the request for comment comes in, can you suggest 
> any related features I could include so the macros are even more useful and 
> fit into the title top-to-bottom.
>
> Please let me know if you have a desire for other related features
>
> Finally shall I include the ability to navigate to the last opened or 
> edited tiddler no matter where is is in the story.
>
> Post script, I would love some help generating a library in which to 
> publish my tools, I have perhaps hundreds, I have not yet published.
>
> Regards
> Tones/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/a63d81f6-fec8-47ea-b512-bac7baa35b6fn%40googlegroups.com.

Re: [tw5] Artwork for v5.2.0

2021-07-19 Thread springer

Jeremy and all,

Although I haven't done any further design work, I did replace the existing 
green "tw-mask" graphic with a variant sitting on my desktop that 
represents my "lightest and leanest" graphic attempt, coming in at 10K, and 
pasted below. For what it's worth, I see 20 candidates, rather than 18, 
though some are fairly redundant. I'm happy to tweak the gallery site 
(https://tw-logo-contest.tiddlyhost.com/) to display only your winnowed 
batch on the HelloThere tiddler, assuming everyone's ok with that proposal. 

-Springer



[image: mask-tw-flat.png]

On Monday, July 19, 2021 at 8:11:12 AM UTC-4 jeremy...@gmail.com wrote:

> As is the way of these things, it took a little longer to get v5.2.0 ready 
> for release, but now I think we’re ready to run the voting part of the 
> competition, and close the competition to new submissions.
>
> Thank you to everyone who has entered. The results are impressive, and the 
> discussion here has been interesting, and I hope will bear fruit in other 
> projects in the future.
>
> There are currently 18 entries listed at 
> https://tw-logo-contest.tiddlyhost.com, a lot more than we’ve had before.
>
> In some cases we’ve got some very similar variants which risks splitting 
> the vote for a design.
>
> So, unless anybody has a better suggestion, I will choose my preferred 
> variant of each design as I prepare the voting form.
>
> Best wishes
>
> Jeremy
>
>
> On 2 Jul 2021, at 01:45, TW Tones  wrote:
>
> All especially those with competition entries,
>
> *Love all this work, wish I had these image design skills. *Whatever wins 
> it would be nice to collect the final submissions (and previous ones) as 
> collateral people building a wiki could use, on there home tiddler, as 
> icons, favicons (sometimes), Wiki or tiddler backgrounds, or images 
> especially when demonstrating a feature of that release.
>
> When you drag and drop a tiddler to a valid location you see a mouse 
> pointer and a little box with a plus, on my browsers at least. Perhaps 
> stamping your design with this would promote the drag features of the new 
> version. I suggest a different color just to stop people confusing with 
> their own mouse pointer.
>
> Regards
> Tones
>
>
> On Wednesday, 30 June 2021 at 07:30:50 UTC+10 james.w@gmail.com wrote:
>
>> I meant @springer, not whoever skinner is :)
>>
>> On Tuesday, 29 June 2021 at 22:29:33 UTC+1 James Anderson wrote:
>>
>>> Hi Frank,
>>>
>>> I asked skinner to remove the alts, I was just playing on the same idea 
>>> and didn't want to flood the list of choices.
>>>
>>> Thanks,
>>> James
>>>
>>> On Tuesday, 29 June 2021 at 21:03:12 UTC+1 f.brunsb...@gmail.com wrote:
>>>
>>>> Dear all,
>>>>
>>>> *@springer: *
>>>> Really cool your last picture ... and now in RGB style like the picture 
>>>> of James "chroma-b-alt.png"... By the way, 
>>>> I'm missing some pictures on tw-logo-contest.tiddlyhost.com What's 
>>>> going on?
>>>>
>>>> *@James.W: *Have I mentioned that I like your RGB series? I also like 
>>>> the spirit of "emoji-field-title.png". 
>>>> There might be more hints of new features swimming in the background ...
>>>>
>>>>
>>>> My favourites so far are (excluding my pictures) and without ranking:
>>>>
>>>>- 3D twisted version white.png (springer)
>>>>- dark-fields.png (springer)
>>>>- json-file-icon-semi-alpha.png (Mohammad)
>>>>- chroma-b-alt.png (James W)
>>>>- emoji-field-title.png (James W)
>>>>
>>>> and even if its shine is slowly fading:
>>>>
>>>>- iamdar-1.png (IAmDarthMole)
>>>>
>>>>
>>>> I agree with Jeremy, perhaps such a contest would be useful for an 
>>>> advertising banner. For a simple release number, the effort is great, 
>>>> because unfortunately it will soon be replaced again. An advertising 
>>>> banner, if without a number, can at least be used for longer.
>>>>
>>>> A fixed scheme (e.g. logo on the left side, release number on the right 
>>>> side, colours fixed in advance) and ... instead an advertising banner on 
>>>> "HelloThere" in the background? I would, I like that.
>>>>
>>>> Here for this competition I would have liked something like an end 
>>>> date, a deadline. Perhaps also a maximum number of inputs.
>>>> As I see it, the many beautif

Re: [tw5] I broke the json pre-release :|

2021-07-16 Thread springer

Since I need to be away for a while, and in case it's helpful, here's a 
link to the entire json segment (copied from "inspect" tool from crash 
window):

https://www.dropbox.com/s/8h1nb4z3npl6odj/json-store-from-crash.json?dl=0

Oddly, I can drag this whole json file onto the official pre-release, and 
apart from duplications and plugin version-conflicts, I see no errors on 
import preview, and import seems to work fine. 

But of course I'm not saving to github from there... 

Tapping out for now...

-Springer


On Friday, July 16, 2021 at 12:37:26 PM UTC-4 springer wrote:

> No red screen! Just "poof" no tiddlywiki interface.
>
> But here's one clue: I tried exporting a json set of tiddlers from the 
> non-crash "early" version (which you can load at url above), and THAT json 
> export file, when re-imported, yields an error that suggests the dynamic 
> table's json entry didn't get proper "closure" (the error is "between" that 
> one and the next tiddler in the json list).
>
> So, it may be safe to assume, for now, that something about Shiraz's 
> dynamic tables needs updating. Which of course would be in some ways 
> surprising if it weren't so, since it was built within the old assumptions 
> about how fields can be named.
>
> Also, I *do* have a window with the failed file "loaded" (white screen). 
> So I could use "inspect" to get at the json list...
>
> [image: From Clipboard.jpg]
>
>
>
> On Friday, July 16, 2021 at 12:30:19 PM UTC-4 jeremy...@gmail.com wrote:
>
>> Hi Springer 
>>
>> Was it a "red screen of embarrassment" crash? It would certainly be 
>> helpful to pin it down if we can. 
>>
>> > I'd also welcome tips on how to get github to actually download files 
>> from the history (When I try, I just get html within a new browser tab). 
>>
>> It's a bit convoluted: first, click on the three dots at the top right of 
>> the file in the commit listing: 
>>
>>

-- 
You received this message because you are subscribed to the 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/3087a5cf-0fb6-4cad-8563-a1fb46409e22n%40googlegroups.com.

Re: [tw5] I broke the json pre-release :|

2021-07-16 Thread springer

No red screen! Just "poof" no tiddlywiki interface.

But here's one clue: I tried exporting a json set of tiddlers from the 
non-crash "early" version (which you can load at url above), and THAT json 
export file, when re-imported, yields an error that suggests the dynamic 
table's json entry didn't get proper "closure" (the error is "between" that 
one and the next tiddler in the json list).

So, it may be safe to assume, for now, that something about Shiraz's 
dynamic tables needs updating. Which of course would be in some ways 
surprising if it weren't so, since it was built within the old assumptions 
about how fields can be named.

Also, I *do* have a window with the failed file "loaded" (white screen). So 
I could use "inspect" to get at the json list...

[image: From Clipboard.jpg]

On Friday, July 16, 2021 at 12:30:19 PM UTC-4 jeremy...@gmail.com wrote:

> Hi Springer
>
> Was it a "red screen of embarrassment" crash? It would certainly be 
> helpful to pin it down if we can.
>
> > I'd also welcome tips on how to get github to actually download files 
> from the history (When I try, I just get html within a new browser tab).
>
> It's a bit convoluted: first, click on the three dots at the top right of 
> the file in the commit listing:
>
>

-- 
You received this message because you are subscribed to the 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/3626aa39-a57e-4683-868b-e518e531078fn%40googlegroups.com.

[tw5] I broke the json pre-release :|

2021-07-16 Thread springer

Jeremy and all: I "broke" the pre-release this morning, recklessly pushing 
the limits with field-names (saving on github).

Alas, it's not easy for me to reconstruct what the last straw was. I don't 
know how to restore (to the most recent non-broken version) with github, so 
as to retrace the most recent steps. (What's public-facing, now, is now a 
very early state that I restored from Chrome, where I had opened it up 
prior to digging in much: 
https://springerspandrel.github.io/tw/new-json-tw-experiment.html)

Here's the github history url: 
https://github.com/springerspandrel/tw/commits/c5a8c5807f22eb35cec72baf9b5a496a1d7a67ac/new-json-tw-experiment.html

My best quick reconstruction: 

1. I had begun by pushing the boundaries with field-names (Japanese words 
(yay!); emoji; names with spaces and eventually getting bold with special 
code-like strings). I switched from Chrome to Safari to observe some of the 
ways that the browsers differ in how/whether they display emoji (such as ⁉️ 
<https://springerspandrel.github.io/tw/new-json-tw-experiment.html#%E2%81%89%EF%B8%8F>
)

2. I spent a while tinkering with getting Shiraz dynamic tables to show a 
row for each non-system field, then making each field-name into a tiddler 
by filling in its caption column and various other silly field parameters, 
like a ★★★☆☆ rating column. (I discovered Shiraz can apparently can also 
render columns not only for emojis and such, but also for field names with 
spaces, if you just put [[field name]] in double-brackets). All was 
behaving well, and saves were surprisingly fast...

3. I had moved on to trying to define a macro to expand within Shiraz, to 
get Shiraz to work with the string 
$(whatever-this-tiddlers-non-system-fields-are)$ as column set... (I had 
pulled in a tobibeer code about exercise-values to reverse-engineer, so any 
version with the string "exercise" is close to when it crashed).

It was while I was tinkering with that macro-variable tiddler (and perhaps 
with a stray keystroke I unwittingly committed the tiddler and triggered a 
save?) that the whole thing crashed. Somehow with one keystroke  the 
browser window blinked to white, and all attempts to reload yielded a 
completely blank screen (until I over-wrote with the much earlier version 
from other browser).

So, as Jeremy says, the pre-release is not for vital projects yet. ;)  

I'm happy to "help" by trying to break it again, but since I'm not sure 
what went wrong, I'll take a break until someone else has some insight. If 
I need to do anything at github to help others see "under the bonnet" ;) , 
I'm happy to do that. I'd also welcome tips on how to get github to 
actually download files from the history (When I try, I just get html 
within a new browser tab).

-Springer

On Wednesday, July 14, 2021 at 7:35:46 AM UTC-4 jeremy...@gmail.com wrote:

> It doesn’t sound very exciting, but the new JSON-based store area has now 
> been merged into the prerelease.
>
> https://tiddlywiki.com/prerelease/
>
> This is the big change that has prompted us moving from v5.1.23 to v5.2.0. 
> It brings one major benefit to all users of TiddlyWIki: the characters used 
> in field names are now unrestricted, making it possible to use fieldnames 
> like "My^Field” or “☃️”.
>
> While that is an important change that we hope will lead to the 
> development of interesting new techniques for working with data in 
> TiddlyWiki, the biggest risk of this change is that it is not fully 
> backwards compatible.
>
> That is to say that *any tools that work directly with TiddlyWiki files 
> will no longer work as expected, and need updating to understand the new 
> format*.
>
> The new format is documented here:
>
>
> https://tiddlywiki.com/prerelease/dev/#Data%20Storage%20in%20Single%20File%20TiddlyWiki
>
> We have tried to anticipate the problems that this change might cause, for 
> example working with Simon Baird to fix TiddlyHost ready for the change. 
> You can follow the technical discussions here:
>
> https://github.com/Jermolene/TiddlyWiki5/pull/5708
>
> But now we need everyone’s help to try the new version, to help us 
> identify any incompatibilities before the final release.
>
> Please try the prerelease with as many different saving mechanisms and 
> server backends as possible. You can report any problems here, or by 
> opening a new ticket on GitHub.
>
> For me personally this feels like a big milestone. TW5 has used the same 
> DIV-based tiddler store area since the very beginning in 2011, having 
> directly inherited it from TiddlyWiki Classic. I reused the old format to 
> give TW5 compatibility with the ecosystem of tools around TiddlyWiki 
> Classic. Now that the TW5 ecosystem is so much bigger, it makes sense to 
> move to a store area format that has fewer restrictions

[tw5] Re: Thinking through a plugin and the excise dropdown

2021-07-15 Thread springer

David,

I'm playing with using the existing excise button with "macro" option 
(specifying your det macro), and I'm not yet seeing how your complaint 
about extra  tags works. That is, I'm getting results that look just 
like your more baroque macrocalls. 

In other words, editing the home outline tiddler at your site, if I replace

<$macrocall $name=det tid="Failures of commentaries"/>

with

<>

I see no difference in how the result displays, either collapsed or 
expanded. Could you clarify what the problem is?

-Springer

On Wednesday, July 14, 2021 at 9:19:47 AM UTC-4 David Gifford wrote:

>
> Hi everyone
>
> Yesterday I teased a modest macro that has the capability of turning 
> TiddlyWiki into an outliner. 
> https://groups.google.com/g/tiddlywiki/c/gCp5ONBxFXg (first half)
>
> I am thinking about packaging it as a plugin called Subsume, but one item 
> seems to call for attention.
>
> If I could add this macro as a new option for the excise dropdown, not as 
> a macro but as a macrocall, that would allow users to excise text and turn 
> it into a link/slider in the present tiddler instead of transcluding it or 
> linking it.
>
> But two things hold me back:
> 1. After playing with the excise dropdown tiddler for a while I am still 
> not sure how it works or how to add another dropdown option to it.
> 2. Even if I knew how to do that, this would mean that my plugin would 
> need to change some core tiddlers. And this would make it un-future-proof.
>
> What chance is there of eventually having the excise dropdown be as easy 
> to add options to via tags, as, say, the pagecontrol buttons and sidebar 
> tabs? Maybe my macrocall is not the only way people might want to customize 
> excising.
>
> And, does anyone know how to tweak the excise set of tiddlers as it stands 
> so that I could insert a named macrocall of the tiddler instead of a 
> transclusion, macro or link?
>
> (In case any of you are wondering, I need macrocall instead of a normal 
> macro to avoid the  that causes extra spacing above and below macros)
>
> Blessings, Dave
>

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

[tw5] Re: Thinking through a plugin and the excise dropdown

2021-07-15 Thread springer

David,

Yes, I did see that your edit-mode [det] button would take the selected 
text and treat it as the name of the tiddler (the one to be displayed 
within the details "pocket"). This is ideal for the situation where the 
other tiddler already exists. For my writing and editing process, by 
contrast, I'm almost always finding that the thing I want to tuck into a 
details "pocket" is initially right there in the same tiddler. 

In fact, prior to seeing your solution, I had been looking forward to 
trying to reverse-engineer a variant of the excise button that dovetails 
with telmiger's details widget (rather than transcluding or linking), 
though I would be terribly slow at the work.

And despite being very fond of telmiger's details plugin with all of its 
css flexibility, I do see advantages in your model, including the elegance 
of typing (and reading) <>, plus the subtle built-in 
asterisk-link to go straight to the tiddler in question. 

Still, one other feature/option that may be of interest (based on spending 
lots of time working with <$details> widgets, which allows summary to be 
specified as a parameter): ability to prefer the caption (or some other 
specifiable field), as the preferred summary text, defaulting to title only 
if caption is unavailable. 

On your site, this tweaked variant seems to get the macro to show caption 
(as summary) if it exists, and to default to title if not:

\relink det tid
\define det(tid:"") <$transclude tiddler="$tid$" 
field="caption"><$view tiddler="$tid$" 
field="title"/><$link 
to="$tid$">*<$transclude tiddler="$tid$" field="text" 
mode="block"/>

-Springer

[Sorry for blinking you all with a post-delete-repost; I found a small typo 
in the macro, which should be fixed now.]
On Wednesday, July 14, 2021 at 9:37:43 AM UTC-4 David Gifford wrote:

> So that's why I couldn't post a reply, you had just deleted your post! 
> Here is what I was replying: 
>
> Hi springer,
>
> 1. I don't know if I updated the teaser version, but in the main file I am 
> tinkering with, selecting text and clicking the ted button does wrap the 
> text.
>
> 2. I literally just posted a question about having ted (which I am 
> planning to call Subsume) be another option the excise button dropdown. 
> Then saw your post.
>
> 3. I agree that is cleaner in EDIT to have it be double angle brackets. 
> But that forces double spacing, and I think it is much cleaner and flexible 
> in VIEW mode to allow users to have them singlespaced. And I doubt Jeremy 
> would allow tweaking to macros to eliminate the  that is the culprit 
> here. It would not be backwards compatible and could cause all kinds of 
> problems. I could have a second button to render it as double angle 
> brackets , I suppose. You CAN currently invoke it with  double angle 
> brackets by typing it.
>
> Dave
>
> On Wednesday, July 14, 2021 at 8:29:35 AM UTC-5 springer wrote:
>
>> David,
>>
>> I'm so sorry to have just replied on your OTHER thread, requesting this 
>> very development, before reading this one! I'll go delete that, and put the 
>> guts of that message below...
>>
>> I'm thinking of a variant on "excise selected text into a new tiddler" 
>> that could take selected text, port it to a new tiddler (prompting for 
>> title, or defaulting to first line), and leave a corresponding details 
>> macro neatly in place of where the excised text is? This would be 
>> tremendously helpful in editing "overgrown" tiddlers (or paragraph 
>> sequences pasted in from elsewhere) and bringing a project closer to the 
>> ideal of tiddlers-as-smallest-useful-bits.
>>
>> For what it's worth, I'm with Saq in hoping to invoke it with <> "Component Idea">> -- much better for readability, sharing with newbies, 
>> etc., and would hope for the editor button to work that way as well.
>>
>> I wish I had time to tinker with these things myself so that I could 
>> offer tribute in the form of useful work, rather than chiming in as a 
>> backseat driver!
>>
>> -Springer
>>
>> On Wednesday, July 14, 2021 at 9:19:47 AM UTC-4 David Gifford wrote:
>>
>>>
>>> Hi everyone
>>>
>>> Yesterday I teased a modest macro that has the capability of turning 
>>> TiddlyWiki into an outliner. 
>>> https://groups.google.com/g/tiddlywiki/c/gCp5ONBxFXg (first half)
>>>
>>> I am thinking about packaging it as a plugin called Subsume, but one 
>>> item seems to call for attention.
>>>
>>> If I could add this macro as a new option for the excise dropdown, not 
>

[tw5] Re: Thinking through a plugin and the excise dropdown

2021-07-15 Thread springer

David,

Yes, I did see that your edit-mode [det] button would take the selected 
text and treat it as the name of the tiddler (the one to be displayed 
within the details "pocket"). This is ideal for the situation where the 
other tiddler already exists. For my writing and editing process, by 
contrast, I'm almost always finding that the thing I want to tuck into a 
details "pocket" is initially right there in the same tiddler. 

In fact, prior to seeing your solution, I had been looking forward to 
trying to reverse-engineer a variant of the excise button that dovetails 
with telmiger's details widget (rather than transcluding or linking), 
though I would be terribly slow at the work.

And despite being very fond of telmiger's details plugin with all of its 
css flexibility, I do see advantages in your model, including the elegance 
of typing (and reading) <>.

Still, one other feature/option that may be of interest (based on spending 
lots of time working with <$details> widgets, which allows summary to be 
specified as a parameter): ability to prefer the caption (or some other 
specifiable field), as the preferred summary text, defaulting to title only 
if caption is unavailable. 

On your site, this tweaked variant seems to get the macro to show caption 
(as summary) if it exists, and to default to title if not:

\relink det tid
\define det(tid:"") <$transclude tiddler="$tid$" 
field="caption"> <$view tiddler="$tid$" field="title"> 
<$link to="$tid$">*<$transclude tiddler="$tid$" field="text" 
mode="block"/>

-Springer

On Wednesday, July 14, 2021 at 9:37:43 AM UTC-4 David Gifford wrote:

> So that's why I couldn't post a reply, you had just deleted your post! 
> Here is what I was replying: 
>
> Hi springer,
>
> 1. I don't know if I updated the teaser version, but in the main file I am 
> tinkering with, selecting text and clicking the ted button does wrap the 
> text.
>
> 2. I literally just posted a question about having ted (which I am 
> planning to call Subsume) be another option the excise button dropdown. 
> Then saw your post.
>
> 3. I agree that is cleaner in EDIT to have it be double angle brackets. 
> But that forces double spacing, and I think it is much cleaner and flexible 
> in VIEW mode to allow users to have them singlespaced. And I doubt Jeremy 
> would allow tweaking to macros to eliminate the  that is the culprit 
> here. It would not be backwards compatible and could cause all kinds of 
> problems. I could have a second button to render it as double angle 
> brackets , I suppose. You CAN currently invoke it with  double angle 
> brackets by typing it.
>
> Dave
>
> On Wednesday, July 14, 2021 at 8:29:35 AM UTC-5 springer wrote:
>
>> David,
>>
>> I'm so sorry to have just replied on your OTHER thread, requesting this 
>> very development, before reading this one! I'll go delete that, and put the 
>> guts of that message below...
>>
>> I'm thinking of a variant on "excise selected text into a new tiddler" 
>> that could take selected text, port it to a new tiddler (prompting for 
>> title, or defaulting to first line), and leave a corresponding details 
>> macro neatly in place of where the excised text is? This would be 
>> tremendously helpful in editing "overgrown" tiddlers (or paragraph 
>> sequences pasted in from elsewhere) and bringing a project closer to the 
>> ideal of tiddlers-as-smallest-useful-bits.
>>
>> For what it's worth, I'm with Saq in hoping to invoke it with <> "Component Idea">> -- much better for readability, sharing with newbies, 
>> etc., and would hope for the editor button to work that way as well.
>>
>> I wish I had time to tinker with these things myself so that I could 
>> offer tribute in the form of useful work, rather than chiming in as a 
>> backseat driver!
>>
>> -Springer
>>
>> On Wednesday, July 14, 2021 at 9:19:47 AM UTC-4 David Gifford wrote:
>>
>>>
>>> Hi everyone
>>>
>>> Yesterday I teased a modest macro that has the capability of turning 
>>> TiddlyWiki into an outliner. 
>>> https://groups.google.com/g/tiddlywiki/c/gCp5ONBxFXg (first half)
>>>
>>> I am thinking about packaging it as a plugin called Subsume, but one 
>>> item seems to call for attention.
>>>
>>> If I could add this macro as a new option for the excise dropdown, not 
>>> as a macro but as a macrocall, that would allow users to excise text and 
>>> turn it into a link/slider in the present tiddler instead of transcluding 
>>> it or

[tw5] Re: Thinking through a plugin and the excise dropdown

2021-07-14 Thread springer

David,

I'm so sorry to have just replied on your OTHER thread, requesting this 
very development, before reading this one! I'll go delete that, and put the 
guts of that message below...

I'm thinking of a variant on "excise selected text into a new tiddler" that 
could take selected text, port it to a new tiddler (prompting for title, or 
defaulting to first line), and leave a corresponding details macro neatly 
in place of where the excised text is? This would be tremendously helpful 
in editing "overgrown" tiddlers (or paragraph sequences pasted in from 
elsewhere) and bringing a project closer to the ideal of 
tiddlers-as-smallest-useful-bits.

For what it's worth, I'm with Saq in hoping to invoke it with <> -- much better for readability, sharing with newbies, 
etc., and would hope for the editor button to work that way as well.

I wish I had time to tinker with these things myself so that I could offer 
tribute in the form of useful work, rather than chiming in as a backseat 
driver!

-Springer

On Wednesday, July 14, 2021 at 9:19:47 AM UTC-4 David Gifford wrote:

>
> Hi everyone
>
> Yesterday I teased a modest macro that has the capability of turning 
> TiddlyWiki into an outliner. 
> https://groups.google.com/g/tiddlywiki/c/gCp5ONBxFXg (first half)
>
> I am thinking about packaging it as a plugin called Subsume, but one item 
> seems to call for attention.
>
> If I could add this macro as a new option for the excise dropdown, not as 
> a macro but as a macrocall, that would allow users to excise text and turn 
> it into a link/slider in the present tiddler instead of transcluding it or 
> linking it.
>
> But two things hold me back:
> 1. After playing with the excise dropdown tiddler for a while I am still 
> not sure how it works or how to add another dropdown option to it.
> 2. Even if I knew how to do that, this would mean that my plugin would 
> need to change some core tiddlers. And this would make it un-future-proof.
>
> What chance is there of eventually having the excise dropdown be as easy 
> to add options to via tags, as, say, the pagecontrol buttons and sidebar 
> tabs? Maybe my macrocall is not the only way people might want to customize 
> excising.
>
> And, does anyone know how to tweak the excise set of tiddlers as it stands 
> so that I could insert a named macrocall of the tiddler instead of a 
> transclusion, macro or link?
>
> (In case any of you are wondering, I need macrocall instead of a normal 
> macro to avoid the  that causes extra spacing above and below macros)
>
> Blessings, Dave
>

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

[tw5] Re: Teaser of my macros

2021-07-14 Thread springer

Dave,

Thanks for sharing this! I see you have set up an editor button for det, 
and I wonder if it could be "smarter" in connection with selected text ... 

I'm thinking of a variant on "excise selected text into a new tiddler" that 
could take selected text, port it to a new tiddler (prompting for title, or 
defaulting to first line), and leave a corresponding details macro neatly 
in place of where the excised text is? This would be tremendously helpful 
in editing "overgrown" tiddlers (or paragraph sequences pasted in from 
elsewhere) and bringing a project closer to the ideal of 
tiddlers-as-smallest-useful-bits.

For what it's worth, I'm with Saq in hoping to invoke it with <> -- much better for readability, sharing with newbies, 
etc., and would hope for the editor button to work that way as well.

I wish I had time to tinker with these things myself so that I could offer 
tribute in the form of useful work, rather than chiming in as a backseat 
driver!

-Springer

On Tuesday, July 13, 2021 at 12:08:39 AM UTC-4 David Gifford wrote:

> Hi everyone
>
> I have been asking for help a few times, and you all were very helpful. 
> Here is the end result, shared as a silent video with notes in the 
> description.
>
> https://www.youtube.com/watch?v=Uk7MSQjaiuo
>
> In a nutshell, it is a macro I called 'det' that creates a details element 
> slider + link (asterisk) based on the tiddler title. These can be nested 
> kind of like Dynalist, so when you open one detail slider, if there are 
> more under that, you can open those sliders as well like a giant outline. 
> And the links are there to open at any level. I tweaked the edit-comptext 
> plugin with Saq's help, and so there is a way to autocomplete to create a 
> det macrocall around an existing tiddler title.
>
> I also uploaded an example file so you can test it out and offer feedback: 
> https://giffmex.org/experiments/det.teaser.html
>
> Maybe at some later point when I have used it for a while I will make it 
> available as a plugin. But for now it is just for inspiration for you and 
> feedback for me.
>
> Thank you for all of your help! I hope you enjoy it. Blessings, Dave
>
>
>

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

Re: [tw5] Re: Artwork for v5.2.0

2021-06-29 Thread springer

With a tip of the hat to IAmDarthMole, I've been thinking for a while that 
one logo-version that *deserves* to exist is a version that takes that json 
mobius image posing as a zero, and makes it fit in seamlessly with the 
other numbers. 

I like that anyone who knows about the JSON logo will "get it" but others 
will just see a 3D-typography effect, plus drag-and-drop. As a flat png, it 
comes in at 19K, less than I feared for a fancy set of bezier curves and 
gradients.

I hope IAmDarthMole takes this as a constructive collaboration! I'm happy 
to split the pile of prize money. :P

-Springer

[image: 3D twisted version white.png]

On Tuesday, June 15, 2021 at 1:34:57 PM UTC-4 iamdar...@gmail.com wrote:

> Here a third attempt, *less* small things. Hopefully those that remain 
> won't be *too* obscure/hard to see. I wasn't able to really think of any 
> other way to show "drag and drop"
>
> Author: IAmDarthMole
> Name: Drag n Drop JSON
>
> [image: Logo3.png]
>
> On Tuesday, June 15, 2021 at 1:11:31 PM UTC-4 TiddlyTweeter wrote:
>
>>  jeremy...@gmail.com wrote:
>>
>>> ... I think there is too much textual content in many of the entries. 
>>> Creating new slogans/taglines for TiddlyWiki is not part of the brief, and 
>>> just takes up a lot of space. The artwork is designed to break the flow of 
>>> a generally text-heavy site; packing more text into images makes things 
>>> worse. The text that needs to be there is "v5.2.0". 
>>>
>>
>> Totally agree. BUT, also 'v5.2.0'  is a kind of "jump" isn't it? What is 
>> I mean is, its slightly potentially more newish, hence the number?
>> A word slogan/flag pointing to that might not be so bad?
>>
>> Just thoughts
>> TT
>>
>

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

[tw5] Re: Discussion: Tiddler titles for sources

Si,

Field name usage for bibliographic data is also a "live" problem for me. 

I've recently gravitated toward approaching the title field with 
author-date brevity, as is used in interlinear citation: *Beauvoir 1962* 
(or *Beauvoir 1962b* in the rare case of multiple sources published from 
same year).

This pattern is easy to type, not terribly difficult to remember, and 
generally steers clear of confusion for my purposes.

On the other hand, if you like using the off-the-shelf sidebar search 
function (as I do, especially if I publish for students), that may give you 
a reason to stick with a longer concatenation: if the title field holds 
*Beauvoir, 
Ethics of Ambiguity (1962)* you can always easily find it even if you only 
remember that the source has "ambiguity" in it. ;) 

Either way, then I end up modifying various templates (including the 
sidebar tabs) to show the caption field. Usually this will hold a version 
of the author surname plus full primary title (omitting subtitle), *but* I 
have the freedom to custom-abbreviate titles that are inconveniently long. 
It's convenient to build filters that fetch one field value *if* it exists, 
and to pull from a default field if not.)

It's awkward that the fieldname "title" is not really workable for the full 
title of the bibliographic source, since I like to use intuitive field 
names. Using fieldnames like bibtex-title bibtex-year (etc) works ok when 
field names are all hidden under the hood and handled through automated 
imports and forms, etc. But they're a nuisance to type repeatedly, and 
(worse for my purposes) they are bulky, and this becomes a problem in 
dynamic tables (which auto-sizes columns so that the bibtex-year column is 
twice as wide as the data needs).

I actually wonder whether there already is -- or could be -- something like 
an efficient sub-forum for people who are using TiddlyWiki in an extensive 
way for bibliographic purposes. It's not always easy to go searching 
through the google groups for relevant past posts, and I know there have 
been a ton of them. There's great benefit to converging on conventions 
together, since that way plugins, specialized ViewTemplates, macros (etc.) 
can be shared easily.

-Springer
On Monday, June 28, 2021 at 12:51:05 PM UTC-4 Si wrote:

> Hi all,
>
> I've been rethinking how I should name tiddlers that represent sources, 
> and I'm interested in hearing the thoughts of other TiddlyWiki users.
>
> By sources I mean books, articles, movies etc. The crucial point here is 
> that I am talking about things that have an 'official' name.
>
> Currently I use the 'official' title of the source, plus any extra 
> information required to make it unique. For example:
>
> Books: The Fellowship of the Ring - J.R.R. Tolkien
> Movies: The Lord of the Rings: The Fellowship of the Ring (2001)
> Articles: The Role of Deliberate Practice in the Acquisition of Expert 
> Performance (1993)
>
> In addition to this I might use a caption which displays a truncated 
> version of the title when I cite the source in another tiddler, for example 
> Ericsson-1993 or DeliberatePractice1993. 
>
> I was browsing Soren's Zettelkasten 
> <https://zettelkasten.sorenbjornstad.com/> and I noticed that he does 
> things the opposite way around. He gives (usually) short CamelCase titles 
> and relies on the caption field for the official name.
>
> I have been thinking about this and two possible advantages occur to me:
>
>- Shorter titles are quicker to type when linking from other tiddlers.
>- More importantly, perhaps they are easier to remember, or 'lock 
>onto'? For example I will probably more easily be able to pull 
>"DeliberatePractice1993" from my brain than I would "The Role of 
> Deliberate 
>Practice..." This relates to titles functioning like APIs 
><https://notes.andymatuschak.org/Evergreen_note_titles_are_like_APIs>.
>
> Possible disadvantages:
>
>- They are likely harder to generate automatically from source 
>metadata. This may not be a disadvantage, as perhaps there is a benefit to 
>thinking up titles yourself.
>- Even when coming up with titles yourself, it may be tricky to figure 
>out a succinct way to represent sources with very long and complex titles, 
>for example these scientific papers 
>
> <https://www.natureindex.com/news-blog/five-most-popular-scientific-papers-of-january-twenty-twenty-altmetrics>
>.
>
> Anyway this is a fairly open ended post, but I'm wondering how people 
> approach naming sources in TiddlyWiki?
> How do you name source tiddlers, and why?
> Do you prefer to use 'official' names or to come up with your own?
>
> Please be free to comment with any thoughts you have relating this topic, 
> no

Re: [tw5] Re: Artwork for v5.2.0

Jeremy,

I think your diagnosis is spot on: we have a collective surplus of 
enthusiastic creative energy from folks who would like to contribute to 
making TiddlyWiki intuitive, visible, and attractive. 

Those of us who have a deeper toolkit/skillset for graphics than for coding 
are especially eager to step up when there's a call for graphic design. The 
result is a level of detail-wrangling over a banner image that has a 
relatively limited role.

Something like a set of public ads would be a more substantive project. 
Presumably there should be at least something like thematic and stylistic 
coherence (which helps people recognize multiple ads as being about the 
same thing), but there are many possible ways to develop such coherence.

-Springer

On Monday, June 28, 2021 at 11:10:18 AM UTC-4 jeremy...@gmail.com wrote:

> Hi Springer
>
> One thing I find myself thinking when I look at the entries is that the 
> new release banner is a frustratingly constrained canvas for the creativity 
> that we see here. The purpose of the new release banner is just to brand 
> each released version, so that visitors to tiddlywiki.com can see the 
> version number at a glance in the splash screen and "HelloThere". So 
> really, the only requirement is that it displays the version number 
> clearly, and is visually distinctive from previous banners.
>
> Nonetheless, I think we'll continue to need a new release banner for each 
> version, but I wonder if we might have the bandwidth for another, ongoing 
> competition that gives contributors a bit more to get their teeth into. 
> Instead of posters, perhaps the designs could be banner advertisements of a 
> specified size: we could have fun imagining how we would advertise 
> TiddlyWiki in big media outlets like the New York Times, Instagram, Reddit 
> or Wired.
>
> We could also host the banner ads on tiddlywiki.com in such a way that 
> anyone who wanted to could add an iframe to their site to add a rotating 
> gallery of TiddlyWiki advertisements. (We would obviously do that without 
> any tracking).
>
> Best wishes
>
> Jeremy
>
> --
> Jeremy Ruston
> jer...@jermolene.com
> https://jermolene.com
>
> On 28 Jun 2021, at 15:53, springer  wrote:
>
> 
>
> Dear all,
>
> The gallery <https://tw-logo-contest.tiddlyhost.com/> is now up to date 
> including James' latest submission with emoji. Of course, multi-submission 
> authors will need to winnow our offerings. 
>
> I'd love to hear more feedback in the spirit of what Télumire offered over 
> the weekend. 
>
> For what it's worth, the images chosen for version banners, up to now, are 
> remarkably heterogeneous -- there's no history of sticking to the fonts 
> used on tiddlywiki.com, nor to any particular palette, and even the 
> TiddlyWiki name was never part of the banner image until 5.1.23 (and 
> invoking a precedent for not using masks seems odd given the heterogeneity 
> of version banners, though I respect individual aesthetic reactions). If 
> there's some emerging consensus around any of these points, then I think 
> we'd all welcome reflections on such things.
>
> There's a delicate balance, in this open-source world between 
> volunteer/amateur enthusiasm and expertise. I love the spirit of this 
> banner image competition, and yet I also recognize that designers (such as 
> Duarte Farrajota Ramos, who won the poster competition 
> <https://tiddlywiki.com/poster/>) really do bring skills to the challenge 
> of communicating clearly and efficiently through images.
>
> In this spirit, it's worth reflecting further on the audience for this 
> (and other) TiddlyWiki imagery and publicity. Are we looking for images 
> that will feel accessible to those who know little about TiddlyWiki and its 
> innards, or are we aiming primarily to communicate with those who already 
> recognize JSON or curly brackets as familiar reference-points? 
>
> Both the puzzle-piece logo of 5.1.22 and the modular shape in Atro's 
> 5.1.23 image presuppose no programming-literacy. The JSON file-icon gesture 
> in Mohammad's entry seems to be at the other end of the spectrum: it surely 
> speaks clearly and elegantly to many users who are at home in code, but 
> perhaps at the risk of intimidating someone who is browsing for a free, 
> flexible, publishable and future-proof alternative to bloatware like 
> evernote, and who would be only slowly tempted to peek under the hood (or 
> "bonnet" for you Brits;) ).  
>
> What do you all think?
>
> -Springer
>
> On Saturday, June 26, 2021 at 11:45:11 AM UTC-4 Télumire wrote:
>
>> Hi everyone, here's my honest feedback, I hope it will be useful :
>>
>> springer 
>> <https://groups.google.com/g/t

Re: [tw5] Re: Artwork for v5.2.0

Dear all,

The gallery <https://tw-logo-contest.tiddlyhost.com/> is now up to date 
including James' latest submission with emoji. Of course, multi-submission 
authors will need to winnow our offerings. 

I'd love to hear more feedback in the spirit of what Télumire offered over 
the weekend. 

For what it's worth, the images chosen for version banners, up to now, are 
remarkably heterogeneous -- there's no history of sticking to the fonts 
used on tiddlywiki.com, nor to any particular palette, and even the 
TiddlyWiki name was never part of the banner image until 5.1.23 (and 
invoking a precedent for not using masks seems odd given the heterogeneity 
of version banners, though I respect individual aesthetic reactions). If 
there's some emerging consensus around any of these points, then I think 
we'd all welcome reflections on such things.

There's a delicate balance, in this open-source world between 
volunteer/amateur enthusiasm and expertise. I love the spirit of this 
banner image competition, and yet I also recognize that designers (such as 
Duarte Farrajota Ramos, who won the poster competition 
<https://tiddlywiki.com/poster/>) really do bring skills to the challenge 
of communicating clearly and efficiently through images.

In this spirit, it's worth reflecting further on the audience for this (and 
other) TiddlyWiki imagery and publicity. Are we looking for images that 
will feel accessible to those who know little about TiddlyWiki and its 
innards, or are we aiming primarily to communicate with those who already 
recognize JSON or curly brackets as familiar reference-points? 

Both the puzzle-piece logo of 5.1.22 and the modular shape in Atro's 5.1.23 
image presuppose no programming-literacy. The JSON file-icon gesture in 
Mohammad's entry seems to be at the other end of the spectrum: it surely 
speaks clearly and elegantly to many users who are at home in code, but 
perhaps at the risk of intimidating someone who is browsing for a free, 
flexible, publishable and future-proof alternative to bloatware like 
evernote, and who would be only slowly tempted to peek under the hood (or 
"bonnet" for you Brits;) ).  

What do you all think?

-Springer

On Saturday, June 26, 2021 at 11:45:11 AM UTC-4 Télumire wrote:

> Hi everyone, here's my honest feedback, I hope it will be useful :
>
> springer 
> <https://groups.google.com/g/tiddlywiki/c/eccIEHZoxsI/m/jQ1dPEyKAwAJ> : 
> love the simplicity of it. ... Color wise, I think it would be best to use 
> the color palette of the vanilla TW... the font you used too... looks like 
> it's not the default font used by TW. ... I personally don't like the 
> masked versions. This makes the logo trapped into a shape, while all the 
> previous splash screens (that I know of) were either rectangular or open. 
> ...
>
>>
>>>

-- 
You received this message because you are subscribed to the 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/2a2c04a5-4276-4544-bd68-fadf307b1b89n%40googlegroups.com.

Re: [tw5] Artwork for v5.2.0

Mohammad,

Thanks! Let me know, of course, if you'd prefer any tweaks to color, 
opacity, etc., or font choices within the icon part.

-Springer


On Sunday, June 27, 2021 at 11:27:52 PM UTC-4 Mohammad wrote:

> Springer,
>
>  Many thanks! Your mockup is now great! I appreciate all your efforts both 
> for this mockup and also for hosting the competition art works!
>  Kudos gos to you!
>
>
> Best wishes
> Mohammad
>
>
> On Sun, Jun 27, 2021 at 9:32 PM springer  wrote:
>
>> I've tweaked a *bit* more, and added Mohammad's submission to our gallery 
>> at:
>>
>> https://tw-logo-contest.tiddlyhost.com/
>>
>> -Springer
>>
>> On Sunday, June 27, 2021 at 12:49:06 PM UTC-4 springer wrote:
>>
>>> Hi all, I had an exchange with Mohammad about the actual graphic file, 
>>> to which he does not have access.
>>>
>>> But the work was based on his own sketches, and it's not too hard to 
>>> replicate after discovering that the font is open-source Saira (google 
>>> font), apart from the curly brackets, whose font isn't yet clear to me. So 
>>> here's a rough mockup of Mohammad's design, though I admit I haven't 
>>> obsessed about replicating all the details:
>>>
>>> [image: Mohammad's JSON logo mockup.png]
>>>
>>> On Saturday, June 26, 2021 at 1:56:58 PM UTC-4 Mohammad wrote:
>>>
>>>> Just to have a little fun in this competition!
>>>>
>>>> These are my designs, but I'm not sure if they are suitable for the new 
>>>> release logo! 
>>>>
>>>> [image: image.png]
>>>>
>>>>
>>>>
>>>> [image: img_342_chrome.png]
>>>>
>>>>
>>>> and also!
>>>>
>>>> [image: img_341_chrome.png]
>>>>
>>>>
>>>>
>>>>
>>>> Best wishes
>>>> Mohammad
>>>>
>>>>
>>>> On Sun, Jun 13, 2021 at 3:44 PM Jeremy Ruston  
>>>> wrote:
>>>>
>>>>> This is to announce our regular competition for the artwork for the 
>>>>> next release of TiddlyWiki 5. The next release is planned to be called 
>>>>> v5.2.0, which requires a little explanation.
>>>>>
>>>>> We've bumped the minor version number because of a single very 
>>>>> important change: for the first time in a decade, we're changing the 
>>>>> format 
>>>>> used to encode tiddlers into the HTML file.
>>>>>
>>>>> The new format is based on JSON, making it much easier to develop 
>>>>> tools that produce or consume TW5 standalone HTML files. While there is 
>>>>> some limited backwards compatibility, the developers of many existing 
>>>>> tools 
>>>>> will need to make modifications to keep things working with v5.2.0.
>>>>>
>>>>> Hence the version number change: it's intended to make every developer 
>>>>> ask "Gosh, what could have changed to warrant such a big jump", and helps 
>>>>> us to make sure that the news of the change is promulgated as widely and 
>>>>> prominently as possible.
>>>>>
>>>>> The change also brings one big improvement for all users: field names 
>>>>> now have no restrictions on which characters can be used, and are 
>>>>> case-sensitive so that "MyField" is a valid fieldname, and refers to a 
>>>>> different field than "myfield" (just like tiddler titles). Finally, we 
>>>>> can 
>>>>> have fields called "⛄️".
>>>>>
>>>>> These changes will be merged shortly, but in the meantime can be 
>>>>> inspected here:
>>>>>
>>>>> https://github.com/Jermolene/TiddlyWiki5/pull/5708
>>>>>
>>>>> So, with that, back to the artwork competition. The task is to design 
>>>>> the banner image that is shown on the splash screen and within the 
>>>>> opening 
>>>>> HelloThere tiddler. It is traditional for the artwork to reflect some of 
>>>>> the changes in the new version.
>>>>>
>>>>> The rules for the competition are:
>>>>>
>>>>> * The version number (with the correct punctuation) must be clear and 
>>>>> readable even when the banner is shown at a reduced size
>>>>> * The image must be a PNG, JPEG

Re: [tw5] Artwork for v5.2.0

2021-06-27 Thread springer

I've tweaked a *bit* more, and added Mohammad's submission to our gallery 
at:

https://tw-logo-contest.tiddlyhost.com/

-Springer

On Sunday, June 27, 2021 at 12:49:06 PM UTC-4 springer wrote:

> Hi all, I had an exchange with Mohammad about the actual graphic file, to 
> which he does not have access.
>
> But the work was based on his own sketches, and it's not too hard to 
> replicate after discovering that the font is open-source Saira (google 
> font), apart from the curly brackets, whose font isn't yet clear to me. So 
> here's a rough mockup of Mohammad's design, though I admit I haven't 
> obsessed about replicating all the details:
>
> [image: Mohammad's JSON logo mockup.png]
>
> On Saturday, June 26, 2021 at 1:56:58 PM UTC-4 Mohammad wrote:
>
>> Just to have a little fun in this competition!
>>
>> These are my designs, but I'm not sure if they are suitable for the new 
>> release logo! 
>>
>> [image: image.png]
>>
>>
>>
>> [image: img_342_chrome.png]
>>
>>
>> and also!
>>
>> [image: img_341_chrome.png]
>>
>>
>>
>>
>> Best wishes
>> Mohammad
>>
>>
>> On Sun, Jun 13, 2021 at 3:44 PM Jeremy Ruston  
>> wrote:
>>
>>> This is to announce our regular competition for the artwork for the next 
>>> release of TiddlyWiki 5. The next release is planned to be called v5.2.0, 
>>> which requires a little explanation.
>>>
>>> We've bumped the minor version number because of a single very important 
>>> change: for the first time in a decade, we're changing the format used to 
>>> encode tiddlers into the HTML file.
>>>
>>> The new format is based on JSON, making it much easier to develop tools 
>>> that produce or consume TW5 standalone HTML files. While there is some 
>>> limited backwards compatibility, the developers of many existing tools will 
>>> need to make modifications to keep things working with v5.2.0.
>>>
>>> Hence the version number change: it's intended to make every developer 
>>> ask "Gosh, what could have changed to warrant such a big jump", and helps 
>>> us to make sure that the news of the change is promulgated as widely and 
>>> prominently as possible.
>>>
>>> The change also brings one big improvement for all users: field names 
>>> now have no restrictions on which characters can be used, and are 
>>> case-sensitive so that "MyField" is a valid fieldname, and refers to a 
>>> different field than "myfield" (just like tiddler titles). Finally, we can 
>>> have fields called "⛄️".
>>>
>>> These changes will be merged shortly, but in the meantime can be 
>>> inspected here:
>>>
>>> https://github.com/Jermolene/TiddlyWiki5/pull/5708
>>>
>>> So, with that, back to the artwork competition. The task is to design 
>>> the banner image that is shown on the splash screen and within the opening 
>>> HelloThere tiddler. It is traditional for the artwork to reflect some of 
>>> the changes in the new version.
>>>
>>> The rules for the competition are:
>>>
>>> * The version number (with the correct punctuation) must be clear and 
>>> readable even when the banner is shown at a reduced size
>>> * The image must be a PNG, JPEG or SVG of exactly 560x315 pixels
>>> * The bottom 46 pixels will be obscured by the banner text “What’s new 
>>> in 5.2.0” when it is displayed within HelloThere
>>> * Feel free to enter an updated version of artwork that was a runner-up 
>>> in a previous competition
>>> * Reply to this message with your entry, or any questions
>>>
>>> Here are the posts about previous artwork competitions:
>>>
>>> v5.1.23 - 
>>> https://groups.google.com/g/tiddlywiki/c/cTgPWl8b_9c/m/VtrMFHBGAwAJ
>>> v5.1.22 - 
>>> https://groups.google.com/g/tiddlywiki/c/rYrja18_SfQ/m/JAklPfjfAwAJ
>>> v5.1.21 - 
>>> https://groups.google.com/g/tiddlywiki/c/l47ZZzWdDb8/m/6s0p_3QeCgAJ
>>>
>>> If you’ve got a great idea for the banner image, but don’t have the 
>>> skills to produce finished artwork, do feel free to share your ideas in 
>>> case somebody else would like to work on the artwork.
>>>
>>> The competition will be open for a week, at which point if there is more 
>>> than one submission I’ll set up a Google Form for voting.
>>>
>>> Best wishes and many thanks,
>>>
>>> Jeremy
>>>
>>> --

Re: [tw5] Artwork for v5.2.0

2021-06-27 Thread springer

Hi all, I had an exchange with Mohammad about the actual graphic file, to 
which he does not have access.

But the work was based on his own sketches, and it's not too hard to 
replicate after discovering that the font is open-source Saira (google 
font), apart from the curly brackets, whose font isn't yet clear to me. So 
here's a rough mockup of Mohammad's design, though I admit I haven't 
obsessed about replicating all the details:

[image: Mohammad's JSON logo mockup.png]

On Saturday, June 26, 2021 at 1:56:58 PM UTC-4 Mohammad wrote:

> Just to have a little fun in this competition!
>
> These are my designs, but I'm not sure if they are suitable for the new 
> release logo! 
>
> [image: image.png]
>
>
>
> [image: img_342_chrome.png]
>
>
> and also!
>
> [image: img_341_chrome.png]
>
>
>
>
> Best wishes
> Mohammad
>
>
> On Sun, Jun 13, 2021 at 3:44 PM Jeremy Ruston  wrote:
>
>> This is to announce our regular competition for the artwork for the next 
>> release of TiddlyWiki 5. The next release is planned to be called v5.2.0, 
>> which requires a little explanation.
>>
>> We've bumped the minor version number because of a single very important 
>> change: for the first time in a decade, we're changing the format used to 
>> encode tiddlers into the HTML file.
>>
>> The new format is based on JSON, making it much easier to develop tools 
>> that produce or consume TW5 standalone HTML files. While there is some 
>> limited backwards compatibility, the developers of many existing tools will 
>> need to make modifications to keep things working with v5.2.0.
>>
>> Hence the version number change: it's intended to make every developer 
>> ask "Gosh, what could have changed to warrant such a big jump", and helps 
>> us to make sure that the news of the change is promulgated as widely and 
>> prominently as possible.
>>
>> The change also brings one big improvement for all users: field names now 
>> have no restrictions on which characters can be used, and are 
>> case-sensitive so that "MyField" is a valid fieldname, and refers to a 
>> different field than "myfield" (just like tiddler titles). Finally, we can 
>> have fields called "⛄️".
>>
>> These changes will be merged shortly, but in the meantime can be 
>> inspected here:
>>
>> https://github.com/Jermolene/TiddlyWiki5/pull/5708
>>
>> So, with that, back to the artwork competition. The task is to design the 
>> banner image that is shown on the splash screen and within the opening 
>> HelloThere tiddler. It is traditional for the artwork to reflect some of 
>> the changes in the new version.
>>
>> The rules for the competition are:
>>
>> * The version number (with the correct punctuation) must be clear and 
>> readable even when the banner is shown at a reduced size
>> * The image must be a PNG, JPEG or SVG of exactly 560x315 pixels
>> * The bottom 46 pixels will be obscured by the banner text “What’s new in 
>> 5.2.0” when it is displayed within HelloThere
>> * Feel free to enter an updated version of artwork that was a runner-up 
>> in a previous competition
>> * Reply to this message with your entry, or any questions
>>
>> Here are the posts about previous artwork competitions:
>>
>> v5.1.23 - 
>> https://groups.google.com/g/tiddlywiki/c/cTgPWl8b_9c/m/VtrMFHBGAwAJ
>> v5.1.22 - 
>> https://groups.google.com/g/tiddlywiki/c/rYrja18_SfQ/m/JAklPfjfAwAJ
>> v5.1.21 - 
>> https://groups.google.com/g/tiddlywiki/c/l47ZZzWdDb8/m/6s0p_3QeCgAJ
>>
>> If you’ve got a great idea for the banner image, but don’t have the 
>> skills to produce finished artwork, do feel free to share your ideas in 
>> case somebody else would like to work on the artwork.
>>
>> The competition will be open for a week, at which point if there is more 
>> than one submission I’ll set up a Google Form for voting.
>>
>> Best wishes and many thanks,
>>
>> Jeremy
>>
>> --
>> Jeremy Ruston
>> jer...@jermolene.com
>> https://jermolene.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+...@googlegroups.com.
>>
> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/tiddlywiki/41EF749B-8AC8-412E-BE59-BBFCE7164340%40gmail.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/9d4a1f3b-e8df-4871-87ee-0fa9636d3b31n%40googlegroups.com.

Re: [tw5] Re: Artwork for v5.2.0

2021-06-25 Thread springer

Hello all,

Based on helpful feedback from Josiah, I further tweaked the masked-tw 
image:

[image: fields-arial.png]

Some considerations shaping this submission: 

keeping filesize down (just under 28K as png w alpha; 14K as flat jpg), 
staying visually "digestible" even at small size (while not overlapping the 
caption-banner), gesturing towards one exciting new feature (opening up of 
fieldname options). If our collective impulse is to celebrate 
drag-and-drop, then I'd offer up the "minimal oval" design instead, which 
includes both feature-gestures. 

I'm not sure how to think about color scheme; it's clearly possible to take 
nearly any design and adjust to nearly any palette. 

If I were a wizard with svg, I'd try making a version that pulls colors 
from the active palette. Even if that's not necessary for the official 
version-release image, given its role at tiddlywiki.com, we all might enjoy 
a tw image that "rolls" with changes in the palette. (Someone —telmiger? — 
shared an svg tool that allowed pulling svg details from fields -- that was 
lots of fun to play with!)

-Springer

On Thursday, June 24, 2021 at 5:18:19 AM UTC-4 TiddlyTweeter wrote:

> Ciao springer
>
> Yeah. It is interesting. I saw it as an arrow and only later saw it as the 
> bottom of "W". :-)
>
> Visually the issue is is you had a band at the bottom that abuts the 
> letters that creates a fictive impression. 
> A small gap under the letters before the bottom-band would likely solve 
> the issue too?
>
> Just a comment
> TT
>
> On Tuesday, 22 June 2021 at 00:00:13 UTC+2 springer wrote:
>
>> TT, it did sot occur to me that the mask on the tv letters could look 
>> like an arrow. Below is a variant that shifts that effect: (at the expense 
>> of somewhat irregular letter-forms)...
>>
>> -Springer
>>
>> [image: dusk-field-alt.png],
>>
>> On Monday, June 21, 2021 at 10:51:07 AM UTC-4 TiddlyTweeter wrote:
>>
>>> springer wrote:
>>>
>>>> Since it's been a week, it may be worth seeing where things stand with 
>>>> graphic options:
>>>>
>>>> https://tw-logo-contest.tiddlyhost.com/
>>>>
>>>
>>> Small comment  on your gallery of 4 ...
>>>
>>> Best
>>> TT
>>>
>>>  [image: Screenshot 2021-06-21 164635.jpg]
>>>
>>

-- 
You received this message because you are subscribed to the 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/b36c4098-71bc-49b6-bf91-fb0aa2a9a416n%40googlegroups.com.

Re: [tw5] Re: Artwork for v5.2.0

2021-06-21 Thread springer

TT, it did sot occur to me that the mask on the tv letters could look like 
an arrow. Below is a variant that shifts that effect: (at the expense of 
somewhat irregular letter-forms)...

-Springer

[image: dusk-field-alt.png],

On Monday, June 21, 2021 at 10:51:07 AM UTC-4 TiddlyTweeter wrote:

> springer wrote:
>
>> Since it's been a week, it may be worth seeing where things stand with 
>> graphic options:
>>
>> https://tw-logo-contest.tiddlyhost.com/
>>
>
> Small comment  on your gallery of 4 ...
>
> Best
> TT
>
>  [image: Screenshot 2021-06-21 164635.jpg]
>

-- 
You received this message because you are subscribed to the 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/739210fb-b460-41cf-8495-0c36362d3523n%40googlegroups.com.

[tw5] Leveraging ViewTemplate in "Missing" tiddlers

2021-06-18 Thread springer

This simple strategy may be obvious to savvy folks, but it felt like magic
when I hammered it out, so it's worth a shout-out for novice-intermediate
folks:

When a whole category of tiddlers would function just to serve as hubs for
related info, don't bother to create the tiddlers. :)

Instead, set up a ViewTemplate element that serves up the related info. In
my case, I populate the custom ViewTemplate with a dynamic table from
Shiraz, but you could use any kind of filtered list of links, etc.
Ideally, you want to set up a filter condition so that content displays
only where needed. (You could even have some default info display exactly
when the tiddler does not exist -- but in a way that revolves around
whether and how its title appears in other tiddlers' fields -- and
evaporate as soon as the tiddler is created.)

I just implemented a variation on this strategy at the logo-contest site,
as an easy demo. Entries for Frank B (such as this one
<https://tw-logo-contest.tiddlyhost.com/#entw5.png>) show a subtitle with
//Frank B// (from author field) in italics. So, clicking the link might
seem useless... BUT, if you click on that "Missing" tiddler link, you'll
get a table with all of Frank B's entries. :)

The template element (which I'm sure could be more streamlined) is
here: https://tw-logo-contest.tiddlyhost.com/#%24%3A%2Ftable-if-author

Sure, it would not have been much trouble to create a tiddler for each of
the five authors, tag each one (say, as "author"), and then have a
tag-based ViewTemplate. That's what I used to do. But making a filter
condition that draws on mentions within other tiddlers' fields means you
don't have to create the tiddlers at all.

Real tried-and-true use case at scale: When I had 32 students, each needing
access to a table of exactly those tiddlers that mentioned their initials
in the "list" field, I set up a conditionally-displayed template filtering
on "[all[current]listed[]]+[has[§]]" (where § is a not-exactly-legal-yet
field-name that I snuck in through Shiraz's dynamic-tables back door; this
field is present only on the assignment-oriented tiddlers that list student
initials). I could then tell each student: Just add a hashtag with your
initials (#JK, or whatever) to our regular URL, and you'll see a summary of
your assignment info.

Two further modifications I made were blanking out the
$:/language/MissingTiddler/Hint (to reduce distraction), and editing
Shiraz's dtables macro definition, near the beginning, to: emptyMessage:"" (so
that I don't have to be so careful about ensuring the filter condition is
narrow enough).

While writing this up, I noticed that a more general solution is available
through modifying shadow tiddlers $:/core/ui/MissingTemplate or even
$:/language/MissingTiddler/Hint ... But my approach lets you recognize
specific niches for Missing tiddlers (those whose names appear in the
author field, those whose titles are listed in tiddlers with § field,
etc.), and to set up different default presentations for each.

Cheers!

-Springer

--
You received this message because you are subscribed to the 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/3836c9f8-7d35-49a4-a6de-dd38d1de1ed4n%40googlegroups.com.

Re: [tw5] Re: Artwork for v5.2.0

Brian, done!

On Thursday, June 17, 2021 at 8:14:15 PM UTC-4 Brian Radspinner wrote:

> springer, if you could replace my first two attempts with the below 
> smaller-sized version, I'd appreciate it.[image: v5.2.0_banner_brian.png]
>
> On Thursday, June 17, 2021 at 4:26:25 PM UTC-7 springer wrote:
>
>> Frank, and all,
>>
>> My own sense is that your last entry is the most compelling of your set 
>> (and is probably the post to which IAmDarthMole is replying), followed by 
>> your #2. 
>>
>> Out of IAmDarthMole's submissions, I think (as Frank did, apparently) 
>> that the first one (Assorted Swedish Tiddlers) has the most coherence.
>>
>> I also love James' RGB image, though it's a bit crowded out to the edges. 
>> James, if you would pull everything in just a bit to give the content 
>> breathing room, I think it would be a good contender!
>>
>> Out of Brian's submissions, I think the second captures something of the 
>> drag-and-drop cues better than the first. For some reason, though, the 
>> filesize is very large (on both submissions). So I think it would be a 
>> better contender if the same idea could fit into a leaner file.
>>
>> In my more recent attempts I've been stepping away from including the 
>> full "TiddlyWiki" label since (1) including that text is a bit redundant in 
>> its use-context, and was not part of the version-number images prior to 
>> 5.1.23, and (2) even if TiddlyWiki isn't ready to rebrand *now*, it's 
>> possible that the conversation will be at a different place by the time we 
>> approach the *next* revision... I'm agnostic about what should happen, but 
>> I suppose it might be a strong point for a version's graphic banner just to 
>> focus on the version number along with whatever feature-hints can show up 
>> without getting too busy.
>>
>> -Springer
>> On Thursday, June 17, 2021 at 4:32:41 PM UTC-4 f.brunsb...@gmail.com 
>> wrote:
>>
>>> Hi to all artwork fans,
>>>
>>> I can support what springer writes. But perhaps we should already agree 
>>> on a few pictures where changes make sense.
>>>
>>> My three favourites so far are (excluding my pictures - these are the 
>>> best anyway), here without a ranking:
>>>
>>>- iamdar-1.png (IAmDarthMole)
>>>- dark-fields.png (springer)
>>>- 名称未設定.png (James W)
>>>
>>> have a nice night, Frank
>>>
>>> PS: @IAmDarthMole: Thanks for the pat on the back but which picture? 
>>> springer schrieb am Donnerstag, 17. Juni 2021 um 05:09:40 UTC+2:
>>>
>>>> Entries -- including through this most recent one submitted by James -- 
>>>> are all posted for easy comparison at 
>>>>
>>>> https://tw-logo-contest.tiddlyhost.com/
>>>>
>>>> Currently I haven't removed any entries except where authors have 
>>>> withdrawn them or indicated that one image is to replace another. So, 
>>>> Frank 
>>>> B currently has 5 entries, and others have 1-3 each. 
>>>>
>>>> If anyone has requests in the next couple days (such as "I'd love to 
>>>> see a variation on this with xyz font or xyz colors), I would be happy to 
>>>> give it a go (and am guessing the same holds for many of us who enjoy this 
>>>> kind of tinkering).
>>>>
>>>> -Springer
>>>> On Wednesday, June 16, 2021 at 6:26:59 PM UTC-4 james.w@gmail.com 
>>>> wrote:
>>>>
>>>>> something really basic:
>>>>>
>>>>> [image: キャプチャ.PNG]
>>>>>
>>>>> [image: 名称未設定.png]
>>>>>
>>>>> something about breaking things apart and putting them back together :)
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> On Wednesday, 16 June 2021 at 22:22:18 UTC+1 f.brunsb...@gmail.com 
>>>>> wrote:
>>>>>
>>>>>> Hi,
>>>>>>
>>>>>> I have something more...
>>>>>> [image: entw5.png]
>>>>>>
>>>>>> TiddlyTweeter schrieb am Mittwoch, 16. Juni 2021 um 00:10:22 UTC+2:
>>>>>>
>>>>>>>  iamdar...@gmail.com wrote:
>>>>>>>
>>>>>>>> Ok, modified 3rd attempt ...
>>>>>>>
>>>>>>>
>>>>>>>> Author: IAmDarthMole
>>>>>>>> Name: Drag n Drop JSON LG
>>>>>>>>
>>>>>>>> [image: Logo4.png]
>>>>>>>>
>>>>>>>
>>>>>>> I PERSONALLY THINK that is neat and semantic.
>>>>>>> It kinda grasps that 5.2.0 up is a change.
>>>>>>> Just saying, TT 
>>>>>>>
>>>>>>

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

[tw5] Re: empty.html should start with a "Centered story, fixed sidebar" setting.

Soren and all,

The idea of asymmetrical edit/preview panes is appealing!

In some cases, the edit window should be relatively wide (where markup 
source is longer than rendered result), but in other cases, the preview 
actually requires much *more* space than the edit box (because of 
transclusions, dynamic tables, etc.). 

I wonder how hard it would be to make the column gutter moveable, and/or to 
get the preview to recognize (with some quick-and-dirty approximation) what 
kind of ratio might be suitable.

-Springer

On Tuesday, June 15, 2021 at 10:44:00 PM UTC-4 Soren Bjornstad wrote:

> While we're discussing story river layouts, I've been playing with the 
> following odd-looking but surprisingly functional layout for a couple of 
> days, in an attempt to make optimal use of the 24" monitors where I do most 
> of my editing:
>
> [image: widening.png]
>
> As you can see, the story river is centered, but tiddlers get wider when 
> you go into edit mode, so there's additional space for a side-by-side 
> preview when editing but lines don't get too long to comfortably read when 
> viewing. I also changed the division between the editor and the preview to 
> 70/30 instead of 50/50, which usually gets the paragraphs on the left and 
> right to almost exactly line up, rather than the wikitext rapidly getting 
> longer than the preview (a smaller difference like 60/40 might be a better 
> compromise if you edit with a lot of images or transclusions).
>
> CSS on top of the default theme and fluid-fixed layout:
>
> div.tc-tiddler-frame { max-width: 60em; margin-left: auto; margin-right: 
> auto; }
> div.tc-tiddler-edit-frame { max-width: 90em; margin-left: auto; 
> margin-right: auto; }
> div.tc-tiddler-body { max-width: 50em; margin: auto; }
> .tc-tiddler-frame .tc-tiddler-preview .tc-edit-texteditor { width: 69%; }
> div.tc-tiddler-preview-preview { width: 29%; }
>
> Still in alpha stages, and probably much too odd to implement in core, but 
> maybe interesting to somebody. :-)
>
> On Tuesday, June 15, 2021 at 4:39:02 PM UTC-5 f.brunsb...@gmail.com wrote:
>
>> Hi Mario, we just had the pleasure, but others are welcome to read my 
>> opinion as well.
>>
>> Not a bad idea as far as it goes. Better than the original alignment of 
>> the empty.html.
>> But I would like to see another variant "All centered". Of course, both 
>> side by side but shown together in the center. 
>> [image: Eg_centered.png]
>>
>> PMario schrieb am Dienstag, 15. Juni 2021 um 21:28:21 UTC+2:
>>
>>>
>>> Hi folks, 
>>> According to the feedback from empty.html should start with 
>>> "fluid-fixed" layout 
>>> <https://groups.google.com/g/tiddlywiki/c/m0XycQ8DrI0/m/2A3qssqDAQAJ> I 
>>> did create a new setting in the ControlPanel : Appearance : Theeme Tweaks
>>>
>>>  - Centered story, fixed sidebar
>>>
>>> If the option is set, the metrics elements, that can't be used are 
>>> "grayd out". 
>>>
>>> The PR is at: https://github.com/Jermolene/TiddlyWiki5/pull/5800
>>>
>>> [image: centered-fixed-01.gif]
>>>
>>> Feedback is welcome.
>>> -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/4039f88b-d9df-4935-86d7-4ac3504848edn%40googlegroups.com.

Re: [tw5] Re: Artwork for v5.2.0

Frank, and all,

My own sense is that your last entry is the most compelling of your set 
(and is probably the post to which IAmDarthMole is replying), followed by 
your #2. 

Out of IAmDarthMole's submissions, I think (as Frank did, apparently) that 
the first one (Assorted Swedish Tiddlers) has the most coherence.

I also love James' RGB image, though it's a bit crowded out to the edges. 
James, if you would pull everything in just a bit to give the content 
breathing room, I think it would be a good contender!

Out of Brian's submissions, I think the second captures something of the 
drag-and-drop cues better than the first. For some reason, though, the 
filesize is very large (on both submissions). So I think it would be a 
better contender if the same idea could fit into a leaner file.

In my more recent attempts I've been stepping away from including the full 
"TiddlyWiki" label since (1) including that text is a bit redundant in its 
use-context, and was not part of the version-number images prior to 5.1.23, 
and (2) even if TiddlyWiki isn't ready to rebrand *now*, it's possible that 
the conversation will be at a different place by the time we approach the 
*next* revision... I'm agnostic about what should happen, but I suppose it 
might be a strong point for a version's graphic banner just to focus on the 
version number along with whatever feature-hints can show up without 
getting too busy.

-Springer
On Thursday, June 17, 2021 at 4:32:41 PM UTC-4 f.brunsb...@gmail.com wrote:

> Hi to all artwork fans,
>
> I can support what springer writes. But perhaps we should already agree on 
> a few pictures where changes make sense.
>
> My three favourites so far are (excluding my pictures - these are the best 
> anyway), here without a ranking:
>
>- iamdar-1.png (IAmDarthMole)
>- dark-fields.png (springer)
>- 名称未設定.png (James W)
>
> have a nice night, Frank
>
> PS: @IAmDarthMole: Thanks for the pat on the back but which picture? 
> springer schrieb am Donnerstag, 17. Juni 2021 um 05:09:40 UTC+2:
>
>> Entries -- including through this most recent one submitted by James -- 
>> are all posted for easy comparison at 
>>
>> https://tw-logo-contest.tiddlyhost.com/
>>
>> Currently I haven't removed any entries except where authors have 
>> withdrawn them or indicated that one image is to replace another. So, Frank 
>> B currently has 5 entries, and others have 1-3 each. 
>>
>> If anyone has requests in the next couple days (such as "I'd love to see 
>> a variation on this with xyz font or xyz colors), I would be happy to give 
>> it a go (and am guessing the same holds for many of us who enjoy this kind 
>> of tinkering).
>>
>> -Springer
>> On Wednesday, June 16, 2021 at 6:26:59 PM UTC-4 james.w@gmail.com 
>> wrote:
>>
>>> something really basic:
>>>
>>> [image: キャプチャ.PNG]
>>>
>>> [image: 名称未設定.png]
>>>
>>> something about breaking things apart and putting them back together :)
>>>
>>>
>>>
>>>
>>>
>>>
>>> On Wednesday, 16 June 2021 at 22:22:18 UTC+1 f.brunsb...@gmail.com 
>>> wrote:
>>>
>>>> Hi,
>>>>
>>>> I have something more...
>>>> [image: entw5.png]
>>>>
>>>> TiddlyTweeter schrieb am Mittwoch, 16. Juni 2021 um 00:10:22 UTC+2:
>>>>
>>>>>  iamdar...@gmail.com wrote:
>>>>>
>>>>>> Ok, modified 3rd attempt ...
>>>>>
>>>>>
>>>>>> Author: IAmDarthMole
>>>>>> Name: Drag n Drop JSON LG
>>>>>>
>>>>>> [image: Logo4.png]
>>>>>>
>>>>>
>>>>> I PERSONALLY THINK that is neat and semantic.
>>>>> It kinda grasps that 5.2.0 up is a change.
>>>>> Just saying, TT 
>>>>>
>>>>

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

Re: [tw5] Re: Unrestricted field names... an implied use case

Jeremy and all,

I too am *very* excited about this, especially given my dependence on 
dynamic tables. 

First, a small confession: I've already been using short special-character 
fieldnames for a while, sneaking around the protection by setting them up 
as column names in Shiraz dynamic tables, and then editing those tables. 
One use: column headings like § and @ that allow for compact and intuitive 
presentation, when the column data tends to be single-digit. But this is a 
superficial cheat (since these have been old-fashioned property-like 
fields).

More importantly, isn't this v5.2.0 step a path to more powerful 
(multi-dimensional) relational data, or at least virtual pivot-table 
behavior? 

Suppose a use-case that involves spread-sheet-like relation between 
tiddlers (rows) and fields (columns), where the field-names tend to have 
their own tiddlers (which until now we've named in the constrained way) 

Starting wth v5.2.0, can't field names can serve better as the intersection 
(cell) of these two dimensions? Values at the intersection should be more 
readily accessed via either axis of the table, so that what appears in 
Tiddler A, field F, also *could* be referenced easily within tiddler F 
(That is, F can be set up with filters to draw info from all tiddlers that 
use F as a field name). 

I imagine the intersectional-field-data housed remotely (on the other 
"axis") could be rendered like virtual fields (within a filter-condition 
ViewTemplate)... and it may even be possible to reach through and edit the 
remote intersection-field directly.

For true pivot-table purposes, a plugin could flag or help correct 
discrepancies between A's F-value and F's A-value, no?Obviously, this would 
have to be an optional feature, or one that hangs on some further 
condition, since some uses might call for A's F-value to differ from F's 
A-value -- especially on legacy projects built without intersectional power 
in mind.

I welcome corrections or clarifications from those who actually understand 
the guts of TW5!

-Springer
On Thursday, June 17, 2021 at 5:54:02 AM UTC-4 jeremy...@gmail.com wrote:

> One thing to bear in mind is that the core has always supported 
> unrestricted fieldnames for almost all operations. The primary thing that's 
> changing now is that the switch to the JSON store area allows us to 
> guarantee that arbitrary fieldnames will be respected over a 
> save-and-reload cycle. The secondary thing is the removal of the very weak 
> protections against creating fieldnames containing arbitrary characters.
>
> Perhaps there a relatively small number of usecases for complex 
> fieldnames, but some of those use cases are powerful and so seem important. 
> But even in the absence of important use cases, a very important benefit is 
> that unrestricted fieldnames make TiddlyWiki significantly simpler to 
> explain. Every little arbitrary restriction or caveat adds to the 
> conceptual load for people learning TiddlyWiki.
>
> For me, one of the most important consequences is that we can encode 
> variable name/value pairs as fields. For example, in the new publishing 
> framework that is under development we represent a publishing job as a 
> configuration tiddler that specifies the template to be used, the filter 
> identifying the tiddlers to be output, and a collection of variables to be 
> provided to the rendering. The variables are expressed as fields named 
> "var-foo", where "foo" is the name of the variable, and the field value is 
> the value for the variable.
>
> It's a simple and flexible approach that wouldn't be possible without 
> loosening the restrictions on field names.
>
> Best wishes
>
> Jeremy
>
> --
> Jeremy Ruston
> jer...@jermolene.com
> https://jermolene.com
>
> On 17 Jun 2021, at 10:42, Mohammad Rahmani  wrote:
>
> Like Mario, for me it is not clear what will be the benefit to have such 
> liberty in naming fields!
> I think Tiddlywiki is growing organically! Sometimes you need to see good 
> and consistent logic to be able to write better code to understand and 
> maintain!
> So, while I am not against the new feature in TW 5.2.0 but I really like 
> it, we are going toward a more consistent, easier to learn and easier to 
> maintain grammar and syntax!
>
>
>
> Best wishes
> Mohammad
>
>
> On Thu, Jun 17, 2021 at 11:27 AM PMario  wrote:
>
>> Let me be more specific eg:
>>
>> >So, the field values could be a relationship between the current tiddler 
>> and those other tiddlers. For example:
>> >
>> >title: Adam
>> >Barbara:mother
>> >Caesar:father
>> >David:friend
>>
>> You mentioned that having upper-case letters in the field names can help 
>> to solve the "relationship

Re: [tw5] Re: Artwork for v5.2.0

2021-06-16 Thread springer

Entries -- including through this most recent one submitted by James -- are 
all posted for easy comparison at 

https://tw-logo-contest.tiddlyhost.com/

Currently I haven't removed any entries except where authors have withdrawn 
them or indicated that one image is to replace another. So, Frank B 
currently has 5 entries, and others have 1-3 each. 

If anyone has requests in the next couple days (such as "I'd love to see a 
variation on this with xyz font or xyz colors), I would be happy to give it 
a go (and am guessing the same holds for many of us who enjoy this kind of 
tinkering).

-Springer
On Wednesday, June 16, 2021 at 6:26:59 PM UTC-4 james.w@gmail.com wrote:

> something really basic:
>
> [image: キャプチャ.PNG]
>
> [image: 名称未設定.png]
>
> something about breaking things apart and putting them back together :)
>
>
>
>
>
>
> On Wednesday, 16 June 2021 at 22:22:18 UTC+1 f.brunsb...@gmail.com wrote:
>
>> Hi,
>>
>> I have something more...
>> [image: entw5.png]
>>
>> TiddlyTweeter schrieb am Mittwoch, 16. Juni 2021 um 00:10:22 UTC+2:
>>
>>>  iamdar...@gmail.com wrote:
>>>
>>>> Ok, modified 3rd attempt ...
>>>
>>>
>>>> Author: IAmDarthMole
>>>> Name: Drag n Drop JSON LG
>>>>
>>>> [image: Logo4.png]
>>>>
>>>
>>> I PERSONALLY THINK that is neat and semantic.
>>> It kinda grasps that 5.2.0 up is a change.
>>> Just saying, TT 
>>>
>>

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

Re: [tw5] Re: Artwork for v5.2.0

2021-06-15 Thread springer

Mohamed,

My reply to you is a bit late here... I wanted to acknowledge your thoughts 
about adding more graphic hints. In accord with Jeremy's note (posted since 
your message here), I've moved toward minimizing complexity as much as 
possible while hinting at both drag-and-drop and flexible field names. So, 
the hand-cursor has become my compromise for an easily-recognizable 
drag-and-drop clue that doesn't add much to the color palette and 
doesn't feel noisy at small scale.

Certainly, playing with graphics can be a fun rabbit-hole! But I confess I 
need to step away for a bit and get back to my day-job. :) 

-Springer

On Tuesday, June 15, 2021 at 2:37:38 AM UTC-4 Mohamed Amin wrote:

> Hi springer,
>
> I like your idea a lot, please find below another variation (just a draft 
> , change it as you like) it shows:
> - The emoji field names (as per Jeremy's first post)
> - Drag & Drop mentioned by Saq (text is from the release note)
> - JSON
>
> [image: Selection_15Jun2021_082439.png]
>
> On Monday, June 14, 2021 at 11:33:08 PM UTC+2 springer wrote:
>
>> Frank, I've added your designs to the collection at  
>> https://tw-logo-contest.tiddlyhost.com/
>>
>> If you'd like to add any descriptive titles, or author name beyond "Frank 
>> B", let me know.
>>
>> -Springer
>>
>> On Monday, June 14, 2021 at 5:21:11 PM UTC-4 f.brunsb...@gmail.com wrote:
>>
>>> I have four ideas. The first two classic square. The last two with 
>>> alternative borders. 
>>> But I think with a banner underneath the round variant does not look 
>>> good...
>>>
>>> [image: entw1.png] [image: entw2.png]  
>>> [image: entw4.png]  [image: entw3.png]
>>>
>>> mwik...@gmail.com schrieb am Montag, 14. Juni 2021 um 19:43:20 UTC+2:
>>>
>>>> Inspired by Mat, here are my "Dragon Drop" entries on the "field" of a 
>>>> shield : ] 
>>>>
>>>> I am no artist but it is fun to share and practice my Inkscape skills 
>>>> and hopefully inspire someone with more talent than me. SVGs are available 
>>>> to anyone who wants them.
>>>>
>>>> /Mike
>>>>
>>>> On Monday, June 14, 2021 at 10:28:41 AM UTC-3 Mat wrote:
>>>>
>>>>> Or perhaps a water drop and a fire-breathing giant reptile ("Dragon 
>>>>>> Drop")
>>>>>>
>>>>>
>>>>> Yeah! Or a dragon 
>>>>> <https://upload.wikimedia.org/wikipedia/commons/b/bc/Chinese_black_dragon.svg>spouting
>>>>>  
>>>>> water/drops! Just above the TiddlyWiki: 5.2.0 field thingy. That would 
>>>>> make 
>>>>> for a really cool and odd art work.
>>>>> *And it is even a super cool version name: "Dragon Drop"! *(even if, 
>>>>> admittedly, the drag'n drop we are discussing here is limited. It would 
>>>>> be 
>>>>> an even more suitable name for if tiddlers were freely movable)
>>>>>
>>>>> <:-)
>>>>>
>>>>>

-- 
You received this message because you are subscribed to the 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/bfc8b046-64c4-4dce-831c-6d9cde55e558n%40googlegroups.com.

Re: [tw5] Re: Artwork for v5.2.0

2021-06-15 Thread springer

Jeremy and all,

Apologies for starting the trend by cramming something like a 
feature-slogan into a caption field!

In addition, I recall that reducing file size, of anything that's bound to 
be handled frequently by servers, is a good aim. In the "dynamic table of 
images" 
<https://tw-logo-contest.tiddlyhost.com/#dynamic%20table%20of%20images> you 
can see the file size for images.

I've removed my "busy" entries from the contest HelloThere tiddler 
<https://tw-logo-contest.tiddlyhost.com/#HelloThere>, and swapped in some 
more minimal ones, such as the one below (though I'm still troubleshooting 
why I'm not achieving smaller sizes in png versions):

-Springer

[image: hand-oval.png]

On Tuesday, June 15, 2021 at 3:47:53 AM UTC-4 jeremy...@gmail.com wrote:

> Thank you to everyone for the entries so far. I always enjoy these 
> competitions, and I appreciate the effort everyone puts into their designs. 
> And I love the spirit of cooperation and friendly competition.
>
> I would like to make a couple of small steers that might improve the 
> results:
>
> First, I think many of the entries are a bit too complex. Have a look at 
> tiddlywiki.com and check how small the artwork is displayed, particularly 
> on mobile: you'll see it in the splash screen, and in the HelloThere 
> tiddler. Many of the designs this time around have too much detail for an 
> icon of this size. Have a look at the other artwork badges to see how 
> simple they are in comparison to some of the entries here.
>
> Second, I think there is too much textual content in many of the entries. 
> Creating new slogans/taglines for TiddlyWiki is not part of the brief, and 
> just takes up a lot of space. The artwork is designed to break the flow of 
> a generally text-heavy site; packing more text into images makes things 
> worse. The text that needs to be there is "v5.2.0". Adding "TiddlyWiki" is 
> reasonable for the splash screen, but unnecessary within the HelloThere 
> tiddler, so I would recommend that if you include the word it be smaller 
> than the version number.
>
> Third, I would suggest being very careful with visual puns. While they can 
> be funny for the creator, they are often baffling for casual observers. 
> This is an inclusive, broad community, and so we should aim to communicate 
> clearly.
>
> The core of the brief is to make a visual representation of the new 
> release that includes the letters "v5.2.0". Next time, I'll take care to 
> raise these points in the original post. 
>
> Best wishes
>
> Jeremy
>
>
>
> --
> Jeremy Ruston
> jer...@jermolene.com
> https://jermolene.com
>
> On 15 Jun 2021, at 08:29, Jon  wrote:
>
> I agree with Mohammad about the name change at some point . Apart from the 
> wiki aspect, I think the diminutive associations of 'tiddly'  (and I know 
> this bit has been discussed before)  are also in opposition to the grand 
> scale of what TW can do.
>
> Regards
> Jon
>
> On Tuesday, 15 June 2021 at 07:57:21 UTC+1 Mohammad wrote:
>
>>
>>
>> On Mon, Jun 14, 2021 at 7:51 PM springer  wrote:
>>
>>> Mohammad,
>>
>>
>> Hi Springer,
>>
>> Many thanks for all your efforts!
>>
>> @all
>> WOW, very exciting! I am really happy to see such an active community! I 
>> love you TiddlyWiki!
>>
>> [image: image.png]
>>
>>
>> @Jeremy Ruston 
>> It would be great if you could decide on the name when you move from 5.1 
>> to 5.2
>> at least I suggest using TW, or TW Platform, or TW framework,  instead of 
>> Tiddlywiki! Tiddlywiki is MuCh MoRe ThAn a wiki!
>>
>> Best wishes
>> Mohammad
>>
>>
>>> All good suggestions! Though I usually don't embed images (and don't 
>>> think tiddlyhost has file directories for such), these images are small, 
>>> and presumably visitors would want to load them all anyway. So I've 
>>> embedded each entry so far, and also set up an overview of the final 
>>> entries from the 5.1.23 contest for inspiration and some sense of 
>>> continuity:
>>>
>>> https://tw-logo-contest.tiddlyhost.com/
>>>
>>> On Sunday, June 13, 2021 at 11:47:50 PM UTC-4 Mohammad wrote:
>>>
>>>> Hi Springer!
>>>>
>>>> I love your artwork! very nice!
>>>>
>>>> Minor comments:
>>>> 1. Why not host the image on 
>>>> https://tw-logo-contest.tiddlyhost.com/#unleash-your-fields and why 
>>>> use dropbox?
>>>> 2. I remember you have hosted artworks for 5.1.23, it is good to see 
>>>> them on https:/

Re: [tw5] Re: Artwork for v5.2.0

2021-06-14 Thread springer

Frank, I've added your designs to the collection at  
https://tw-logo-contest.tiddlyhost.com/

If you'd like to add any descriptive titles, or author name beyond "Frank 
B", let me know.

-Springer

On Monday, June 14, 2021 at 5:21:11 PM UTC-4 f.brunsb...@gmail.com wrote:

> I have four ideas. The first two classic square. The last two with 
> alternative borders. 
> But I think with a banner underneath the round variant does not look 
> good...
>
> [image: entw1.png] [image: entw2.png]  
> [image: entw4.png]  [image: entw3.png]
>
> mwik...@gmail.com schrieb am Montag, 14. Juni 2021 um 19:43:20 UTC+2:
>
>> Inspired by Mat, here are my "Dragon Drop" entries on the "field" of a 
>> shield : ] 
>>
>> I am no artist but it is fun to share and practice my Inkscape skills and 
>> hopefully inspire someone with more talent than me. SVGs are available to 
>> anyone who wants them.
>>
>> /Mike
>>
>> On Monday, June 14, 2021 at 10:28:41 AM UTC-3 Mat wrote:
>>
>>> Or perhaps a water drop and a fire-breathing giant reptile ("Dragon 
>>>> Drop")
>>>>
>>>
>>> Yeah! Or a dragon 
>>> <https://upload.wikimedia.org/wikipedia/commons/b/bc/Chinese_black_dragon.svg>spouting
>>>  
>>> water/drops! Just above the TiddlyWiki: 5.2.0 field thingy. That would make 
>>> for a really cool and odd art work.
>>> *And it is even a super cool version name: "Dragon Drop"! *(even if, 
>>> admittedly, the drag'n drop we are discussing here is limited. It would be 
>>> an even more suitable name for if tiddlers were freely movable)
>>>
>>> <:-)
>>>
>>>

-- 
You received this message because you are subscribed to the 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/24935351-fb65-4b7c-ae1c-8a669e55602bn%40googlegroups.com.

Re: [tw5] Re: Artwork for v5.2.0

2021-06-14 Thread springer

Mohammad,

All good suggestions! Though I usually don't embed images (and don't think 
tiddlyhost has file directories for such), these images are small, and 
presumably visitors would want to load them all anyway. So I've embedded 
each entry so far, and also set up an overview of the final entries from 
the 5.1.23 contest for inspiration and some sense of continuity:

https://tw-logo-contest.tiddlyhost.com/

On Sunday, June 13, 2021 at 11:47:50 PM UTC-4 Mohammad wrote:

> Hi Springer!
>
> I love your artwork! very nice!
>
> Minor comments:
> 1. Why not host the image on 
> https://tw-logo-contest.tiddlyhost.com/#unleash-your-fields and why use 
> dropbox?
> 2. I remember you have hosted artworks for 5.1.23, it is good to see them 
> on https://tw-logo-contest.tiddlyhost.com/#unleash-your-fields
> 3. It is good to have 
> https://tw-logo-contest.tiddlyhost.com/#unleash-your-fields for past and 
> future artworks competitions all in one place this not only archive all 
> previous efforts but also give ideas to other contributors
>
>
>
> Best wishes
> Mohammad
>
>>
>>

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

Re: [tw5] Re: Artwork for v5.2.0

2021-06-14 Thread springer

iamdar..., and all,

I'm sorry I don't know how to attribute an author name to your entries. 

For anyone who posts entries here, it would be helpful to include (1) how 
you'd ilke your authorname to appear, and (2) name of entry.

I'll try to keep an eye out and update the site with entries, as they're 
shared here, at https://tw-logo-contest.tiddlyhost.com/

-Springer

On Monday, June 14, 2021 at 2:02:10 AM UTC-4 iamdar...@gmail.com wrote:

> Here is another attempt based on what I read regarding a focus on fields.
>
> [image: Logo2.png]
>
> On Monday, June 14, 2021 at 12:43:30 AM UTC-4 Darth Mole wrote:
>
>> One of my attempts so far. Hope it isn't too off the mark!
>>
>> [image: Logo1.png]
>>
>> On Sunday, June 13, 2021 at 11:47:50 PM UTC-4 Mohammad wrote:
>>
>>> Hi Springer!
>>>
>>> I love your artwork! very nice!
>>>
>>> Minor comments:
>>> 1. Why not host the image on 
>>> https://tw-logo-contest.tiddlyhost.com/#unleash-your-fields and why use 
>>> dropbox?
>>> 2. I remember you have hosted artworks for 5.1.23, it is good to see 
>>> them on https://tw-logo-contest.tiddlyhost.com/#unleash-your-fields
>>> 3. It is good to have 
>>> https://tw-logo-contest.tiddlyhost.com/#unleash-your-fields for past 
>>> and future artworks competitions all in one place this not only archive all 
>>> previous efforts but also give ideas to other contributors
>>>
>>>
>>>
>>> Best wishes
>>> Mohammad
>>>
>>>
>>> On Mon, Jun 14, 2021 at 1:02 AM springer  wrote:
>>>
>>>> Here's a hasty concept-logo to kick things off, also visible at site: 
>>>> https://tw-logo-contest.tiddlyhost.com/#unleash-your-fields
>>>>
>>>> [image: unleash_your_fields.jpg]
>>>>
>>>> On Sunday, June 13, 2021 at 4:13:44 PM UTC-4 jeremy...@gmail.com wrote:
>>>>
>>>>> Hi Mat
>>>>>
>>>>> The artwork needs to show "v5.2.0" (including the "v"!), because there 
>>>>> will  be a "v5.2.1" at some point, potentially quite soon, and it's 
>>>>> important for everybody to be able to unambiguously distinguish the 
>>>>> versions. Stated another way, this is not version '5.2', this is version 
>>>>> '5.2.0'.
>>>>>
>>>>> I'd also say that perhaps designs based on the shapes of the letters 
>>>>> might be a bit generic. I think the opportunity is to try to capture what 
>>>>> is in the release, not just the string of numbers we use to refer to it.
>>>>>
>>>>> Best wishes
>>>>>
>>>>> Jeremy.
>>>>>
>>>>>
>>>>> --
>>>>> Jeremy Ruston
>>>>> jer...@jermolene.com
>>>>> https://jermolene.com
>>>>>
>>>>> On 13 Jun 2021, at 20:02, Mat  wrote:
>>>>>
>>>>> Oooh I just got two cool ideas! Anyone skilled, feel free to create:
>>>>>
>>>>> First depends on if it is OK with "5.2" (see my previous 
>>>>> question). Those two digits have a very similar shape! I think it should 
>>>>> be 
>>>>> possible to make some kind of mirror reflection to have one show the 
>>>>> other. 
>>>>>
>>>>> Second idea uses that new feature with freely named fields. So the 
>>>>> design idea is to simply make the string "TiddlyWiki 5.2.0" as a field! 
>>>>> E.g 
>>>>> the "TiddlyWiki 5" as the field name and the "2.0" as the field value. 
>>>>> Should the garbage can that deletes the field be next to it?... 
>>>>>
>>>>> <:-)
>>>>> On Sunday, June 13, 2021 at 8:08:15 PM UTC+2 Mat wrote:
>>>>>
>>>>>> Freely naming of fields will be fantastic! It will give fields a much 
>>>>>> more prominent position because they can be used directly as connections 
>>>>>> to 
>>>>>> actual tiddlers. Great progress!
>>>>>>
>>>>>> @Jeremy can the artwork treat the version number as 5.2 (i.e without 
>>>>>> .0 at end)? I don't have a particular idea but I imagine it will be 
>>>>>> easier 
>>>>>> to come up with ideas for fewer digits.
>>>>>>
>>>>>> <:-)
>>>>>>
>>>>>> On Sund

[tw5] Re: Removing Collapsible Arrow/Funcion from toc-tabbed-internal-nav

2021-06-13 Thread springer

If you don't want the hierarchical deep-dive that the toc macro offers, you 
could just use a set of tabs:

<>

(Here, you'll get one tab for each tiddler with the BigIdeas tag, with the 
one entitled StartHere displaying by default.)

-Springer
On Wednesday, June 9, 2021 at 12:47:37 AM UTC-4 iamdar...@gmail.com wrote:

> Hello!
>
> I'm currently in a love hate relationship with the 
> new toc-tabbed-internal-nav macro for my current project. 
>
> I'm not even sure if what I want to do is possible:
>
> Is there anyway to remove the > that appears next to the headers? 
>
> I only want the first level to show on the left of the two column window 
> that is generated by using the above macro. 
>
> Thank you!
>

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

Re: [tw5] Re: Artwork for v5.2.0

2021-06-13 Thread springer

Here's a hasty concept-logo to kick things off, also visible at 
site: https://tw-logo-contest.tiddlyhost.com/#unleash-your-fields

[image: unleash_your_fields.jpg]

On Sunday, June 13, 2021 at 4:13:44 PM UTC-4 jeremy...@gmail.com wrote:

> Hi Mat
>
> The artwork needs to show "v5.2.0" (including the "v"!), because there 
> will  be a "v5.2.1" at some point, potentially quite soon, and it's 
> important for everybody to be able to unambiguously distinguish the 
> versions. Stated another way, this is not version '5.2', this is version 
> '5.2.0'.
>
> I'd also say that perhaps designs based on the shapes of the letters might 
> be a bit generic. I think the opportunity is to try to capture what is in 
> the release, not just the string of numbers we use to refer to it.
>
> Best wishes
>
> Jeremy.
>
>
> --
> Jeremy Ruston
> jer...@jermolene.com
> https://jermolene.com
>
> On 13 Jun 2021, at 20:02, Mat  wrote:
>
> Oooh I just got two cool ideas! Anyone skilled, feel free to create:
>
> First depends on if it is OK with "5.2" (see my previous question). Those 
> two digits have a very similar shape! I think it should be possible to make 
> some kind of mirror reflection to have one show the other. 
>
> Second idea uses that new feature with freely named fields. So the design 
> idea is to simply make the string "TiddlyWiki 5.2.0" as a field! E.g the 
> "TiddlyWiki 5" as the field name and the "2.0" as the field value. Should 
> the garbage can that deletes the field be next to it?... 
>
> <:-)
> On Sunday, June 13, 2021 at 8:08:15 PM UTC+2 Mat wrote:
>
>> Freely naming of fields will be fantastic! It will give fields a much 
>> more prominent position because they can be used directly as connections to 
>> actual tiddlers. Great progress!
>>
>> @Jeremy can the artwork treat the version number as 5.2 (i.e without .0 
>> at end)? I don't have a particular idea but I imagine it will be easier to 
>> come up with ideas for fewer digits.
>>
>> <:-)
>>
>> On Sunday, June 13, 2021 at 1:14:17 PM UTC+2 Jeremy Ruston wrote:
>>
>>> This is to announce our regular competition for the artwork for the next 
>>> release of TiddlyWiki 5. The next release is planned to be called v5.2.0, 
>>> which requires a little explanation.
>>>
>>> We've bumped the minor version number because of a single very important 
>>> change: for the first time in a decade, we're changing the format used to 
>>> encode tiddlers into the HTML file.
>>>
>>> The new format is based on JSON, making it much easier to develop tools 
>>> that produce or consume TW5 standalone HTML files. While there is some 
>>> limited backwards compatibility, the developers of many existing tools will 
>>> need to make modifications to keep things working with v5.2.0.
>>>
>>> Hence the version number change: it's intended to make every developer 
>>> ask "Gosh, what could have changed to warrant such a big jump", and helps 
>>> us to make sure that the news of the change is promulgated as widely and 
>>> prominently as possible.
>>>
>>> The change also brings one big improvement for all users: field names 
>>> now have no restrictions on which characters can be used, and are 
>>> case-sensitive so that "MyField" is a valid fieldname, and refers to a 
>>> different field than "myfield" (just like tiddler titles). Finally, we can 
>>> have fields called "⛄️".
>>>
>>> These changes will be merged shortly, but in the meantime can be 
>>> inspected here:
>>>
>>> https://github.com/Jermolene/TiddlyWiki5/pull/5708
>>>
>>> So, with that, back to the artwork competition. The task is to design 
>>> the banner image that is shown on the splash screen and within the opening 
>>> HelloThere tiddler. It is traditional for the artwork to reflect some of 
>>> the changes in the new version.
>>>
>>> The rules for the competition are:
>>>
>>> * The version number (with the correct punctuation) must be clear and 
>>> readable even when the banner is shown at a reduced size
>>> * The image must be a PNG, JPEG or SVG of exactly 560x315 pixels
>>> * The bottom 46 pixels will be obscured by the banner text “What’s new 
>>> in 5.2.0” when it is displayed within HelloThere
>>> * Feel free to enter an updated version of artwork that was a runner-up 
>>> in a previous competition
>>> * Reply to this message with your entry, or any questions
>>>
>>> Here are the posts about previous artwork competitions:
>>>
>>> v5.1.23 - 
>>> https://groups.google.com/g/tiddlywiki/c/cTgPWl8b_9c/m/VtrMFHBGAwAJ
>>> v5.1.22 - 
>>> https://groups.google.com/g/tiddlywiki/c/rYrja18_SfQ/m/JAklPfjfAwAJ
>>> v5.1.21 - 
>>> https://groups.google.com/g/tiddlywiki/c/l47ZZzWdDb8/m/6s0p_3QeCgAJ
>>>
>>> If you’ve got a great idea for the banner image, but don’t have the 
>>> skills to produce finished artwork, do feel free to share your ideas in 
>>> case somebody else would like to work on the artwork.
>>>
>>> The competition will be open for a week, at which point if there is more 
>>> than one submission I’ll set up a Google

[tw5] Re: Artwork for v5.2.0

2021-06-13 Thread springer

Jeremy and all,

I'm happy to host all entries again, in an easy-to-compare (and change 
palettes, etc.) dedicated TW:

https://tw-logo-contest.tiddlyhost.com/

-Springer

On Sunday, June 13, 2021 at 7:14:17 AM UTC-4 jeremy...@gmail.com wrote:

> This is to announce our regular competition for the artwork for the next 
> release of TiddlyWiki 5. The next release is planned to be called v5.2.0, 
> which requires a little explanation.
>
> We've bumped the minor version number because of a single very important 
> change: for the first time in a decade, we're changing the format used to 
> encode tiddlers into the HTML file.
>
> The new format is based on JSON, making it much easier to develop tools 
> that produce or consume TW5 standalone HTML files. While there is some 
> limited backwards compatibility, the developers of many existing tools will 
> need to make modifications to keep things working with v5.2.0.
>
> Hence the version number change: it's intended to make every developer ask 
> "Gosh, what could have changed to warrant such a big jump", and helps us to 
> make sure that the news of the change is promulgated as widely and 
> prominently as possible.
>
> The change also brings one big improvement for all users: field names now 
> have no restrictions on which characters can be used, and are 
> case-sensitive so that "MyField" is a valid fieldname, and refers to a 
> different field than "myfield" (just like tiddler titles). Finally, we can 
> have fields called "⛄️".
>
> These changes will be merged shortly, but in the meantime can be inspected 
> here:
>
> https://github.com/Jermolene/TiddlyWiki5/pull/5708
>
> So, with that, back to the artwork competition. The task is to design the 
> banner image that is shown on the splash screen and within the opening 
> HelloThere tiddler. It is traditional for the artwork to reflect some of 
> the changes in the new version.
>
> The rules for the competition are:
>
> * The version number (with the correct punctuation) must be clear and 
> readable even when the banner is shown at a reduced size
> * The image must be a PNG, JPEG or SVG of exactly 560x315 pixels
> * The bottom 46 pixels will be obscured by the banner text “What’s new in 
> 5.2.0” when it is displayed within HelloThere
> * Feel free to enter an updated version of artwork that was a runner-up in 
> a previous competition
> * Reply to this message with your entry, or any questions
>
> Here are the posts about previous artwork competitions:
>
> v5.1.23 - 
> https://groups.google.com/g/tiddlywiki/c/cTgPWl8b_9c/m/VtrMFHBGAwAJ
> v5.1.22 - 
> https://groups.google.com/g/tiddlywiki/c/rYrja18_SfQ/m/JAklPfjfAwAJ
> v5.1.21 - 
> https://groups.google.com/g/tiddlywiki/c/l47ZZzWdDb8/m/6s0p_3QeCgAJ
>
> If you’ve got a great idea for the banner image, but don’t have the skills 
> to produce finished artwork, do feel free to share your ideas in case 
> somebody else would like to work on the artwork.
>
> The competition will be open for a week, at which point if there is more 
> than one submission I’ll set up a Google Form for voting.
>
> Best wishes and many thanks,
>
> Jeremy
>
> --
> Jeremy Ruston
> jer...@jermolene.com
> https://jermolene.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/c6b31171-60c5-4cb7-a0cd-3c9cd9707c6fn%40googlegroups.com.

[tw5] Re: Recent doesn't update except for imported tiddlers.

2021-05-31 Thread springer

Boazter, forgive me if you're already checked this, but: 

Any chance your timestamps got toggled to "off"? (To check: on the page 
tools dropdown, the "stopwatch" icon would be showing the "pause" symbol?) 

This would have the effect of making it seem that nothing had been modified.

-Springer
On Monday, May 31, 2021 at 3:38:59 PM UTC-4 Boazter wrote:

> Greetings, all,
>
> I have a wiki that I've been using for sometime and I never noticed that 
> it wasn't updating the "Recents" tab. I didn't need that tab for this 
> particular wiki before but have changed how I use it and now it would be 
> handy to be able to see the recents list. Oddly, there are a handful of 
> tiddlers in the list. They all appear to be ones that I've imported from 
> other wikis. I tried upgrading the wiki but that did not help. I tried 
> importing the timeline from another wiki. Nothing. I'm afraid to play 
> around too much with it for fear of breaking it further. Am I missing some 
> simple fix?
>
> Any insight would be appreciated.
>
> Thank you!
>

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

[tw5] Re: First edition of Grok TiddlyWiki (TW textbook) is live

2021-05-28 Thread springer

Wow, just coming up for air at the end of a very dense semester.

Soren, I'm looking forward to cruising around your very 
thoughtfully-designed site and converting countless bits of 
getting-it-good-enough-for-now (my hastily hacked appropriations of others' 
work) into proper grokking.

Awe and gratitude from my corner,
-Springer

On Sunday, May 16, 2021 at 10:43:44 AM UTC-4 Soren Bjornstad wrote:

> I'm excited to announce that the first public edition of my TiddlyWiki 
> textbook, *Grok TiddlyWiki*, is live at https://groktiddlywiki.com/read. 
> *Grok 
> TiddlyWiki* is (from the book) “a textbook that helps you build a deep, 
> lasting understanding of and proficiency with TiddlyWiki through a 
> combination of detailed explanations, practical exercises, 
> and spaced-repetition reviews of prompts called *takeaways*.”
>
> I am hoping this book will fill in many of the gaps in TiddlyWiki's 
> documentation / learning ecosystem – right now we have lots of beginner 
> tutorials, and mostly good documentation for experts (with a few gaps), but 
> almost nothing for people in between. GTW is what I wished I had when I was 
> in that position: complete lessons on the features and idioms of TiddlyWiki 
> needed to bring someone from beginner to expert.
>
> The book is free to read and CC BY-NC-ND licensed (you can redistribute it 
> for noncommercial purposes). I am accepting donations 
> <https://groktiddlywiki.com/donate/> to support my continued work on GTW 
> and other TiddlyWiki learning resources. I would also appreciate your help 
> spreading the word about the book, e.g., on TW links sites, notes-related 
> resources, or social media.
>
> A huge thanks to everyone from this community who provided feedback on the 
> prerelease (see the acknowledgments section for details). Barring me 
> getting run over by a bus, there will be updated editions in the future, so 
> please keep the feedback and suggestions coming.

-- 
You received this message because you are subscribed to the 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/00d403da-f4a1-462d-8d0c-f27d33b7895an%40googlegroups.com.

[tw5] Re: Question for long time TiddlyWiki users

2021-05-28 Thread springer

Reet, I never had any problem, even though I regularly used encryption on 
pretty large projects hosted at tiddlyspot.
-Springer

On Sunday, May 17, 2020 at 10:09:26 PM UTC-4 Reet Pandher wrote:

> Have you tried the encryption feature of the tiddlywiki?
> If yes then has it been reliable for you? Reliable as in Has it caused any 
> sort of corruption or loss of data even when you know your password? Does 
> it work properly even when you have large amounts of data stored in it? 
>
> Thanks!
>

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

[tw5] Re: Design trick discover classes and CSS in use?

2021-05-28 Thread springer

I'm afraid I just startled my neighbors with the sound of my jaw dropping 
after setting up the Internals html preview. ;)

Given how extensively I use telmiger's details widget to structure long 
stretches of text, and how often I just want to copy-export a bare-bones 
html that retains the drop-down details structure for quick navigation, 
this is a brilliantly helpful bit of advice. 

Thanks, Tony!

On Monday, May 24, 2021 at 8:20:21 PM UTC-4 TW Tones wrote:

> Folks,
>
> Many of you may know about using the Inspect in your browser development 
> tools to discover css and other details while designing a wiki. 
>
> I just discovered that Using the Core addon-plugin Internals allows you to 
> preview the html generated inside a tiddler and this allows you to see and 
> extract similar information for a given tiddlers content.
>
> It makes me think what if we provide some alternate tools to do the same 
> thing so we can see other elements of the whole page in rendered html as 
> insight. Not forcing people into inspect for such analysis would be helpful 
> to less experienced users. TiddlyWikis dynamic behaviours and multiple 
> stylesheets and plugins can make this quite complex so the more tools we 
> have the better.
>
>
>- What do you think?
>- Could you make something?
>
> It seems to me TiddlyWiki is capable of being its own "Software 
> development kit", and it would be useful if we can provision a few more 
> tools so people can stay within tiddlywiki. While largely self documenting 
> the complexity in the rendering of the final result suggest a little more 
> support there will help.
>
> Regards
> Tones
>
>

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

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

Si, I highly recommend checking out all the RefNotes resources (active here 
recently, contributed by Mohammad). 

My own approach is to use a DYNAMIC TABLE (Mohammad's Shiraz) for each 
reference-type. The lovely thing is that you can filter on a tag (or any 
other filter condition), to see a column for each of the fields you care 
about for that tag (or filter condition), with a row for each tiddler that 
fits the condition (and the ability to "clone" new rows into existence). 
Then you don't have a separate challenge of generating forms. Unless you 
really want to. ;)

-Springer
On Wednesday, April 14, 2021 at 3:03:02 PM UTC-4 si wrote:

> I use TiddlyWiki to manage sources (books, movies etc), and I want to 
> create an easy way to add tiddlers for individual sources.
>
> I have decided to add tiddlers that represent a "source-type", and then 
> use it to generate a form that allows me to enter metadata for a new 
> source. For example I might have a source type "Book", which is used to 
> generate a form like this:
>
> Title: ...
> Author: ...
> Year: ...
>
> While "Movie" might have a form like this:
>
> Title: ...
> Director: ...
> Producer: ...
>
> Obviously I need to associate the required metadata-fields with their 
> source-type. I can think of two ways to do this:
>
>- Add a field to each tiddler type called "required-fields" which 
>lists the required metadata-fields.
>- Create separate tiddlers for each possible metadata-field, then tag 
>them with any source-type that requires them.
>
> It's not obvious to me that there is any functional difference between 
> these two options, but if I make a bad choice it will be difficult to 
> change down the line. So my question is: *Is there a reason that one of 
> these approaches is better than the other?*
>
> Thanks in advance for you help.
>

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

[tw5] Re: freelinks alias-variant request, partial workaround

My particular use case is actually: 

- I have already populated the wiki with tiddlers for various keywords 
(definitions, "nodes" of likely connection among related items, etc.) 
- Seminar students paste in their reflective writing each week
- I also paste in excerpts from other authors (philosophical source texts)

With freelinks (set to look only for title-strings of tiddlers tagged 
"keyword"), all this pasted-in tiddler content renders "lit up" with links, 
even though there's no markup. But it annoyingly won't pull "ethical" to 
"ethics" etc.

The "magnetic" tiddlers (the ones to which I want links to pop up 
automatically) always have short names (usually one or two words); the 
variant names are also short.

-Springer
On Wednesday, April 14, 2021 at 3:48:40 PM UTC-4 PMario wrote:

> On Monday, April 12, 2021 at 1:34:13 AM UTC+2 springer wrote:
> ...
>
>> But for now, I'll share a very limited workaround, so that a freelink 
>> (virtual link) to *empiricism* (or at least, a functional equivalent) 
>> will display whenever tiddler text mentions empiric*ists* (for example).
>>
>
> Having a look at your OP it seems your freelink "titles" and your aliases 
> should be "short", since you use the caption field. Which is convenient for 
> shorter titles. 
>
> With short I mean 1 or 2 words and not whole sentences like eg: "TiddlyDrive 
> Add-on for Google Drive by Joshua Stubbs"
>
> About your workflow. 
>
>  - Someone copy pastes some content into a tiddler named: *empiricism* 
>  - The text isn't changed
>  - This user would also define some aliases eg: empiric*ists* 
> experimentation  
>
> Freelinks should also link to this tiddler of 1 of the aliases matches. 
> Right?
>
> -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/f1e3af75-c163-4d84-b538-fb55d5f44a87n%40googlegroups.com.

[tw5] Re: freelinks alias-variant request, partial workaround

PMario,

Indeed "ignore case" is great, and I was delighted when Jeremy confirmed 
the option would be added in. But between that (straightforward) and 
anticipating lots of typos (silly bush-whacking), there are plurals and 
other grammatical variants, essential name variants, etc.
On Wednesday, April 14, 2021 at 2:46:25 PM UTC-4 PMario wrote:

> On Monday, April 12, 2021 at 1:34:13 AM UTC+2 springer wrote:
>
> I continue to hope that freelinks will one day work seamlessly with an 
>> "aliases" or "title-variants" field... It's hard to imagine any person who 
>> finds freelinks useful but who wouldn't benefit from getting title-variants 
>> recognized without fuss.
>>
>
> You know, that freelinks plugin has setting for "Ignore case". So case 
> isn't important, but "typos" are ;)
>
> -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/672f5ea6-783d-4f3a-93ea-83ef9c21c855n%40googlegroups.com.

[tw5] Re: freelinks alias-variant request, partial workaround