[tw5] Simpel dictionary

[wolfi wolfe]

Hello, I'm new to tiddlywiki and wondering how to make a simple dictionary .

Also I'm using tiddlywiki for studying languages  and would be happy with a 
word bank with translations. 

-- 
You received this message because you are subscribed to the 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/a84de684-ab81-4fd0-a0a0-6c3916feeb6cn%40googlegroups.com.

[tw5] Re: Imminent release of v5.1.23

[TW Tones]

My Mistake, Its the default :)

On Monday, 21 December 2020 at 18:21:11 UTC+11 TW Tones wrote:

> Observation
>
> The Tiddler  Named Filter Run Prefix 
>  in the 
> pre-release names a prefix of *OR *which I believe is not currently 
> implemented?
>
> Tones
>
> On Wednesday, 9 December 2020 at 14:49:19 UTC+11 TW Tones wrote:
>
>> Folks,
>>
>> Exploring the pre-release I can see the reduce operator is an advance, 
>> however these are my personal observations so far.
>>
>> I understand the reduce operator has its origin in bigdata and other 
>> terminology, but it seems to me the documentation and examples is 
>> insufficient to realise its full potential for all audiences.
>>
>>- I may not be too smart, but neither am I a dummy, but the 
>>documentation is seriously hard to read.
>>- Some of these features such as the index and accumulator would be 
>>nice in a regular filter, if they were available in the result of a list 
>>widget for example
>>
>> The reduce operator runs a subfilter for each input title, passing the 
>> result of the previous subfilter run as a variable. The initial value of 
>> the accumulator can optionally be specified. It returns the result of the 
>> final subfilter run.  
>>
>>
>> *The reduce operator runs a subfilter for each input title,  *
>> input-run > [reduce] ?
>>
>> *passing the result of the previous subfilter run as a variable   *
>> *()*
>> We should use quotes here "*previous subfilter run"  as it needs this *
>>
>> In my words!
>> *The subFilter is applied to each title in the input, each iteration off 
>> the subFilter can access the variable () ie; "access the 
>> result of the previous iteration" . ie  stores the result of 
>> the last subFilter. Thus if you use the add operator add to 
>> the subFilter you can sum all values.*
>>
>> *The following variables are available within the subfilter:   
>>   and  ONLY and  varies with 
>> each title.*
>> * The variables ,  and   are available if you 
>> need these values to be part of your subfilter calculations.*
>>
>> *There is only ever one output from the reduce operator! *
>> *The last value determined is the output of the reduce operator, as a 
>> result all subfilters would be expected to include an operation with the 
>>  variable (eg add, multiply, divide etc..)*
>>
>> Regards
>> Tones
>> On Monday, 30 November 2020 at 22:36:42 UTC+11 jeremy...@gmail.com wrote:
>>
>>> I’m hoping that we’ll be able to release v5.1.23 of TiddlyWiki towards 
>>> the end of this week. There’s some discussion over on GitHub about the last 
>>> few loose ends to be tied up:
>>>
>>> https://github.com/Jermolene/TiddlyWiki5/issues/5130
>>>
>>> The most important call to action is for developers of plugins and 
>>> adaptations to take this opportunity to verify that the new release doesn’t 
>>> break anything.
>>>
>>> The second call to action is for as many people as possible to put the 
>>> new release through it’s paces by performing a test upgrade of the wikis 
>>> that are important to them. Don’t switch over to the new version yet, of 
>>> course.
>>>
>>> You can upgrade single file wikis here:
>>>
>>> https://tiddlywiki.com/prerelease/upgrade.html
>>>
>>> This is a really quite a massive release, with over 160 new features 
>>> listed in the release note. (I am working on improvements to the 
>>> presentation of the release note, it’s a bit of a wall of text right now).
>>>
>>> https://tiddlywiki.com/prerelease/
>>>
>>> Just to mention a handful of new features that I’m particularly excited 
>>> about:
>>>
>>> * Keyboard support for the main core dropdowns: search, new tag, tiddler 
>>> type, new field, and the “link” button in the editor toolbar
>>> * The beginnings of support for switchable page templates (referred to 
>>> as layouts), which will give us a route to introduce a more modern 
>>> alternative layout
>>> * The ability to rename tiddlers during the import process (and to 
>>> easily see which incoming tiddlers will overwrite existing tiddlers)
>>> * Many new filter operators that together make the TiddlyWiki filter 
>>> language significantly more powerful and expressive
>>> * Improvements to the “tm-scroll” message making it possible to scroll 
>>> to positions within a tiddler
>>> * Via the JSZip plugin, the ability to dynamically create ZIP files, 
>>> giving us the ability to create static sites in the browser
>>> * New <$action-log> and <$log> widgets to aid debugging
>>>
>>> There are many, many bug fixes and other improvements too.
>>>
>>> As ever, I’m profoundly grateful to all the contributors who have pulled 
>>> together to make this such an exciting release. You can see here how much 
>>> activity there’s been since v5.1.22:
>>>
>>>
>>> https://github.com/Jermolene/TiddlyWiki5/graphs/contributors?from=2020-04-16=2020-11-30=c
>>>
>>> My own contribution graph (below) shows nicely how this release covers 
>>> my illness 

[tw5] Re: Imminent release of v5.1.23

[TW Tones]

Observation

The Tiddler  Named Filter Run Prefix 
 in the 
pre-release names a prefix of *OR *which I believe is not currently 
implemented?

Tones

On Wednesday, 9 December 2020 at 14:49:19 UTC+11 TW Tones wrote:

> Folks,
>
> Exploring the pre-release I can see the reduce operator is an advance, 
> however these are my personal observations so far.
>
> I understand the reduce operator has its origin in bigdata and other 
> terminology, but it seems to me the documentation and examples is 
> insufficient to realise its full potential for all audiences.
>
>- I may not be too smart, but neither am I a dummy, but the 
>documentation is seriously hard to read.
>- Some of these features such as the index and accumulator would be 
>nice in a regular filter, if they were available in the result of a list 
>widget for example
>
> The reduce operator runs a subfilter for each input title, passing the 
> result of the previous subfilter run as a variable. The initial value of 
> the accumulator can optionally be specified. It returns the result of the 
> final subfilter run.  
>
>
> *The reduce operator runs a subfilter for each input title,  *
> input-run > [reduce] ?
>
> *passing the result of the previous subfilter run as a variable   *
> *()*
> We should use quotes here "*previous subfilter run"  as it needs this *
>
> In my words!
> *The subFilter is applied to each title in the input, each iteration off 
> the subFilter can access the variable () ie; "access the 
> result of the previous iteration" . ie  stores the result of 
> the last subFilter. Thus if you use the add operator add to 
> the subFilter you can sum all values.*
>
> *The following variables are available within the subfilter:   
>   and  ONLY and  varies with 
> each title.*
> * The variables ,  and   are available if you 
> need these values to be part of your subfilter calculations.*
>
> *There is only ever one output from the reduce operator! *
> *The last value determined is the output of the reduce operator, as a 
> result all subfilters would be expected to include an operation with the 
>  variable (eg add, multiply, divide etc..)*
>
> Regards
> Tones
> On Monday, 30 November 2020 at 22:36:42 UTC+11 jeremy...@gmail.com wrote:
>
>> I’m hoping that we’ll be able to release v5.1.23 of TiddlyWiki towards 
>> the end of this week. There’s some discussion over on GitHub about the last 
>> few loose ends to be tied up:
>>
>> https://github.com/Jermolene/TiddlyWiki5/issues/5130
>>
>> The most important call to action is for developers of plugins and 
>> adaptations to take this opportunity to verify that the new release doesn’t 
>> break anything.
>>
>> The second call to action is for as many people as possible to put the 
>> new release through it’s paces by performing a test upgrade of the wikis 
>> that are important to them. Don’t switch over to the new version yet, of 
>> course.
>>
>> You can upgrade single file wikis here:
>>
>> https://tiddlywiki.com/prerelease/upgrade.html
>>
>> This is a really quite a massive release, with over 160 new features 
>> listed in the release note. (I am working on improvements to the 
>> presentation of the release note, it’s a bit of a wall of text right now).
>>
>> https://tiddlywiki.com/prerelease/
>>
>> Just to mention a handful of new features that I’m particularly excited 
>> about:
>>
>> * Keyboard support for the main core dropdowns: search, new tag, tiddler 
>> type, new field, and the “link” button in the editor toolbar
>> * The beginnings of support for switchable page templates (referred to as 
>> layouts), which will give us a route to introduce a more modern alternative 
>> layout
>> * The ability to rename tiddlers during the import process (and to easily 
>> see which incoming tiddlers will overwrite existing tiddlers)
>> * Many new filter operators that together make the TiddlyWiki filter 
>> language significantly more powerful and expressive
>> * Improvements to the “tm-scroll” message making it possible to scroll to 
>> positions within a tiddler
>> * Via the JSZip plugin, the ability to dynamically create ZIP files, 
>> giving us the ability to create static sites in the browser
>> * New <$action-log> and <$log> widgets to aid debugging
>>
>> There are many, many bug fixes and other improvements too.
>>
>> As ever, I’m profoundly grateful to all the contributors who have pulled 
>> together to make this such an exciting release. You can see here how much 
>> activity there’s been since v5.1.22:
>>
>>
>> https://github.com/Jermolene/TiddlyWiki5/graphs/contributors?from=2020-04-16=2020-11-30=c
>>
>> My own contribution graph (below) shows nicely how this release covers my 
>> illness and recovery from COVID, and undoubtedly a strange and painful time 
>> for all of us. I couldn’t be more pleased that this community has thrived, 
>> and seems to be working together so well at the moment.
>>
>> Please 

[tw5] Re: A How To: Dynamic Hiding/Showing elements on my resume tiddlywiki

[TW Tones]

Charlie,

Nice approach *"To keep things simple, I hide TiddlyWiki things when the 
sidebar is hidden, and show those TiddlyWiki things when the sidebar is 
displayed"*
 Thanks for sharing.
Tones
On Monday, 21 December 2020 at 13:02:27 UTC+11 Charlie Veniot wrote:

> My Résumé à la TiddlyWiki  
> *(very 
> early design stage)*
>
> G'day all,
>
> As I try to figure out how I want my resume to show for mere mortals 
> whilst still having access to all TiddlyWiki things, I figured I'd share 
> design so far in case there are any bits of interest to anyone.
>
> Features:
>
>- TonGerner's  Left Menu 
>- For "summary" info
>- TobiasBeer's HideSideBarOnStartup 
>
>- Mere mortals just looking at my résumé don't need to see the sidebar
>
> Upon opening the TiddlyWiki, it just shows a left side bar and one tiddler 
> that will have everything résumé transcluded into it.
>
> To make this all look like any kind of website and make it print nicely (a 
> lot of work to be done re printing), I've done a bit of trickery to hide 
> TiddlyWiki things in the tiddler.
>
> To keep things simple, I hide TiddlyWiki things when the sidebar is 
> hidden, and show those TiddlyWiki things when the sidebar is displayed.
>
> In the $:/core/ui/ViewTemplate/title and $:/core/ui/ViewTemplate/subtitle, 
> here are some snippets of code that are part of the magic:
>
> <$vars vhide={{{[[$:/state/sidebar]get[text]]+[match[no]] display:none; 
> +[replace[no]]}}}>
>
> For anything I want hidden/shown, I add a "style=<>" to whatever 
> HTML element.
>
> Example:  >>
>
> For your convenience, I've added a couple of screenshots below: what you 
> see when you first open the TiddlyWiki, and then what you see when you 
> unhide the sidebar.
>
> Cheers !
>
> [image: Screenshot 2020-12-20 at 9.17.56 PM.png]
>
> [image: Screenshot 2020-12-20 at 9.17.40 PM.png]
>
>
>
>
>
>
>
>

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

Re: [tw5] Wikitext monospace block oddity

[Michael Wiktowy]

I just did the same thing (downloaded the attachment and viewed in Firefox 
on Linux) and either removing the second  (which Saq identfied as the 
culprit) or putting a blank line between it and the subsequent  seemed 
to solve the inline vs. block rendering of the tiddler:




...

```
from django.urls import include, path
```

It was not a space after the first ``` like I suspected but that has the 
same effect of confusing the monospace markup.

Alternatively you can roll with the inline rendering tendencies and use two 
less backticks:



...

``from django.urls import include, path
``

/Mike

On Sunday, December 20, 2020 at 5:20:41 PM UTC-4 dgle...@gmail.com wrote:

> I appreciate the thought!
>
> However you will find browser rendering engines ignore errors like these 
> no matter where they appear.That has been my experience writing pages, but 
> I checked to make sure I wasn't blowing smoke. I downloaded the file 
> attached for Jeremy, then removed the unterminated  tag without it 
> having any effect on the monospace block issue. You can even have a start 
> and closing tag that still doesn't display if the tags fail to terminate in 
> the same order they were defined.
>
> I can't swear IE might be effected, but it won't keep me up at night.
>
> On Sat, Dec 19, 2020 at 6:28 PM Saq Imtiaz  wrote:
>
>> I think the culprit is an unterminated  tag on line 7.
>>
>> On Saturday, December 19, 2020 at 9:17:46 PM UTC+1 dgle...@gmail.com 
>> wrote:
>>
>>> @Mohamed Amin
>>>
>>> That works as well, but as in all my previous tiddlers as tw5 wikitext, 
>>> I was highlighting the blocks text and using the button in  the editor to 
>>> mark it as monotext. It was using ```block``` without problems. Since the 
>>> result was showing a single backtick as part of the block and all the text 
>>> below it, I had played with it and discovered `` would work.
>>>
>>> When an editor starts displaying different formatting behavior using the 
>>> defaults and no changes, that gets me nervous. Imagine if that occurred to 
>>> you while writing up a peer review with it's strict formatting. It would be 
>>> disturbing. It's like creating a HTML page  displayed differently from 
>>> previous HTML pages using the same browser.
>>>
>>> It's not like scouring code for hours, spotting nothing, have a peer 
>>> review it to discover a variable, function or class had a capitol letter 
>>> instead of lower case. That has happened often enough to me it's 
>>> embarrassing :-) 
>>>
>>> On Saturday, December 19, 2020 at 2:47:27 PM UTC-5 Mohamed Amin wrote:
>>>
 Try to use only 2 backtick instead of 3 around your special text

 On Sat, 19 Dec 2020, 21:34 Jeremy Ruston,  wrote:

> Hi Douglas could you kindly share the entire text? Or an expurgated 
> version if necessary. As you say, it looks like the block mode formatting 
> has gone awry but I need to see the whole thing to see what's going on.
>
> Many thanks,
>
> Jeremy
>
> --
> Jeremy Ruston
> jer...@jermolene.com
> https://jermolene.com
>
> On 19 Dec 2020, at 16:53, Douglas Glenn  wrote:
>
> The monospace functionality has worked as expected in previous 
> tiddlers. This particular tiddler is an exception. I have cut the text 
> and 
> copied it to Atom, looked for any hidden characters. Didn't find any so I 
> copied the text and used the insert as plain text option (in KDE) and the 
> the issue still exists with the monotext block.
>
> 
>
> Any ideas what may be causing the issue? 
>
> Suggestions?
>
> -- 
> You received this message because you 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/5eafcec9-aaa3-489a-b95e-0a97e717e003n%40googlegroups.com
>  
> 
> .
> 
>
> -- 
> You received this message because you are subscribed to the Google 
> Groups "TiddlyWiki" group.
> To unsubscribe from this group and stop receiving emails from it, send 
> an email to tiddlywiki+...@googlegroups.com.
>
 To view this discussion on the web visit 
> https://groups.google.com/d/msgid/tiddlywiki/55CBEA40-89B4-4858-B58C-1676E3F048C3%40gmail.com
>  
> 
> .
>
 -- 
>>
> You received this message because you are subscribed to a topic in the 
>> Google Groups "TiddlyWiki" group.
>> To unsubscribe from this topic, visit 
>> https://groups.google.com/d/topic/tiddlywiki/ysm-M_teeUQ/unsubscribe.
>> To 

Re: [tw5] Wikitext monospace block oddity

[Doug Glenn]

I appreciate the thought!

However you will find browser rendering engines ignore errors like these no
matter where they appear.That has been my experience writing pages, but I
checked to make sure I wasn't blowing smoke. I downloaded the file attached
for Jeremy, then removed the unterminated  tag without it having any
effect on the monospace block issue. You can even have a start and closing
tag that still doesn't display if the tags fail to terminate in the same
order they were defined.

I can't swear IE might be effected, but it won't keep me up at night.

On Sat, Dec 19, 2020 at 6:28 PM Saq Imtiaz  wrote:

> I think the culprit is an unterminated  tag on line 7.
>
> On Saturday, December 19, 2020 at 9:17:46 PM UTC+1 dgle...@gmail.com
> wrote:
>
>> @Mohamed Amin
>>
>> That works as well, but as in all my previous tiddlers as tw5 wikitext, I
>> was highlighting the blocks text and using the button in  the editor to
>> mark it as monotext. It was using ```block``` without problems. Since the
>> result was showing a single backtick as part of the block and all the text
>> below it, I had played with it and discovered `` would work.
>>
>> When an editor starts displaying different formatting behavior using the
>> defaults and no changes, that gets me nervous. Imagine if that occurred to
>> you while writing up a peer review with it's strict formatting. It would be
>> disturbing. It's like creating a HTML page  displayed differently from
>> previous HTML pages using the same browser.
>>
>> It's not like scouring code for hours, spotting nothing, have a peer
>> review it to discover a variable, function or class had a capitol letter
>> instead of lower case. That has happened often enough to me it's
>> embarrassing :-)
>>
>> On Saturday, December 19, 2020 at 2:47:27 PM UTC-5 Mohamed Amin wrote:
>>
>>> Try to use only 2 backtick instead of 3 around your special text
>>>
>>> On Sat, 19 Dec 2020, 21:34 Jeremy Ruston,  wrote:
>>>
 Hi Douglas could you kindly share the entire text? Or an expurgated
 version if necessary. As you say, it looks like the block mode formatting
 has gone awry but I need to see the whole thing to see what's going on.

 Many thanks,

 Jeremy

 --
 Jeremy Ruston
 jer...@jermolene.com
 https://jermolene.com

 On 19 Dec 2020, at 16:53, Douglas Glenn  wrote:

 The monospace functionality has worked as expected in previous
 tiddlers. This particular tiddler is an exception. I have cut the text and
 copied it to Atom, looked for any hidden characters. Didn't find any so I
 copied the text and used the insert as plain text option (in KDE) and the
 the issue still exists with the monotext block.

 

 Any ideas what may be causing the issue?

 Suggestions?

 --
 You received this message because you 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/5eafcec9-aaa3-489a-b95e-0a97e717e003n%40googlegroups.com
 
 .
 

 --
 You received this message because you are subscribed to the Google
 Groups "TiddlyWiki" group.
 To unsubscribe from this group and stop receiving emails from it, send
 an email to tiddlywiki+...@googlegroups.com.

>>> To view this discussion on the web visit
 https://groups.google.com/d/msgid/tiddlywiki/55CBEA40-89B4-4858-B58C-1676E3F048C3%40gmail.com
 
 .

>>> --
> You received this message because you are subscribed to a topic in the
> Google Groups "TiddlyWiki" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/tiddlywiki/ysm-M_teeUQ/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> tiddlywiki+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/tiddlywiki/51c7f6d6-577b-44cf-ba07-9dc299053b81n%40googlegroups.com
> 
> .
>


-- 
Regards,
Doug

-- 
You received this message because you are subscribed to the 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/CAFSpLU8vOrAz06HEmQTAkP4exyLLtG-f38HZ86WefXJAAvR6zA%40mail.gmail.com.

[tw5] Re: Showing off: Muuri StoryView 0.2.0 Prerelease

[BurningTreeC]

@Ste,

> Was just wondering if the mobile view could be set to toggle between on 
and two coloumns? 

I'll think about this, maybe there's a way to do so

Ste schrieb am Sonntag, 20. Dezember 2020 um 17:51:57 UTC+1:

>
> Hi.  Was just wondering if the mobile view could be set to toggle between 
> on and two coloumns? 
> On Sunday, 20 December 2020 at 15:54:57 UTC BurningTreeC wrote:
>
>> @Saq,
>>
>> > what would be neat is if Muuri looked for a storyViewConfig tiddler 
>> attribute on the list widget, and if it didn't exist used a default value 
>> for the config tiddler.
>>
>> that would indeed be neat. should that storyViewConfig be a single 
>> tiddler (like a data tiddler) or a namespace?
>>
>> > Then a layout with multiple stories could just specify a 
>> storyViewConfig attribute for each extra stories list view, and if Muuri 
>> was used it would be able to use that configTiddler. This way a layout does 
>> not need to know if Muuri might be used, and installing Muuri would not 
>> necessitate editing shadow tiddlers.
>>
>> understood, yes that would be great...
>>
>> In the meantime I've updated the plugin so that also the dragHandle and 
>> the connectionSelector can be configured by a config tiddler
>>
>>
>>
>> saq.i...@gmail.com schrieb am Sonntag, 20. Dezember 2020 um 16:24:24 
>> UTC+1:
>>
>>> @BTC what would be neat is if Muuri looked for a storyViewConfig tiddler 
>>> attribute on the list widget, and if it didn't exist used a default value 
>>> for the config tiddler.
>>>
>>> Then a layout with multiple stories could just specify a storyViewConfig 
>>> attribute for each extra stories list view, and if Muuri was used it would 
>>> be able to use that configTiddler. This way a layout does not need to know 
>>> if Muuri might be used, and installing Muuri would not necessitate editing 
>>> shadow tiddlers.
>>>
>>> On Sunday, December 20, 2020 at 4:17:14 PM UTC+1 BurningTreeC wrote:
>>>
 @Saq, right now almost every configuration for the main muuri story 
 (the one in the story river) is done using a config tiddler. Only the 
 connection with another Grid must be done with an attribute on the list 
 widget. I could make that also configurable using a config tiddler

 saq.i...@gmail.com schrieb am Sonntag, 20. Dezember 2020 um 14:47:11 
 UTC+1:

> @BTC yeah there isn't an obvious solution that comes to mind but I 
> will think about it. 
>
> I considered a config tiddler that is determined by the name of the 
> storylist, but that would preclude two muuri with the same storylist.
>
> On Sunday, December 20, 2020 at 2:42:05 PM UTC+1 BurningTreeC wrote:
>
>> Hi Saq,
>>
>> > In principle I quite like that the storyview gets its 
>> attributes/settings from the ListWidget. In practice however this means 
>> having to edit shadow tiddlers. I am wondering if there is way around 
>> that...
>>
>> Yes that's the downside of it - I haven't found another way around it 
>> but I'm open for ideas
>>
>> best wishes
>>
>> saq.i...@gmail.com schrieb am Sonntag, 20. Dezember 2020 um 14:37:09 
>> UTC+1:
>>
>>> Looks good @BTC!
>>>
>>> Love the dragHandle support.
>>>
>>> In principle I quite like that the storyview gets its 
>>> attributes/settings from the ListWidget. In practice however this means 
>>> having to edit shadow tiddlers. I am wondering if there is way around 
>>> that...
>>>
>>> Cheers,
>>> Saq
>>>
>>> On Sunday, December 20, 2020 at 11:45:56 AM UTC+1 BurningTreeC wrote:
>>>

 Hi TiddlyWiki folks,

 I want to show you my Muuri StoryView plugin version 0.2.0 
 Prerelease.

 It contains various Bugfixes and can overall be considered more 
 stable

 New Feature:

- Drop Actions: actions triggered when dropping an item from 
one grid into another grid
   - the actionTiddler and modifier variables are available 
   within the action-string, containing the title of the dragged 
 item 
   respectively the modifier keys held while dragging

 Missing Feature:

- A configuration panel. I'm currently overhauling it.

 You play with it at https://burningtreec.github.io/tiddlywiki-muuri

 On the Demo page there's a Sidebar Grid where you can drop tiddlers 
 into. Holding shift while dragging adds a tag to that Tiddler. Holding 
 ctrl-shift while dragging shifts the Tiddler to edit mode.

 That's just a Demo of what can be built with the Muuri StoryView.

 If we think about it - having a Muuri StoryView in the main river 
 on the left and having one or two Grids in the SideBar with some 
 defined 
 dropActions makes the whole 

Re: [tw5] Showing off: Muuri StoryView 0.2.0 Prerelease

[BurningTreeC]

Thanks Mohammad, maybe it's coming for Christmas ;)

Mohammad schrieb am Sonntag, 20. Dezember 2020 um 19:35:26 UTC+1:

> Hi BTC,
>
>  Excellent job! Muuri 2.0 a Christmass gift ;-)
>
>
> Best wishes
> Mohammad
>
>
> On Sun, Dec 20, 2020 at 2:16 PM BurningTreeC  
> wrote:
>
>>
>> Hi TiddlyWiki folks,
>>
>> I want to show you my Muuri StoryView plugin version 0.2.0 Prerelease.
>>
>> It contains various Bugfixes and can overall be considered more stable
>>
>> New Feature:
>>
>>- Drop Actions: actions triggered when dropping an item from one grid 
>>into another grid
>>   - the actionTiddler and modifier variables are available within 
>>   the action-string, containing the title of the dragged item 
>> respectively 
>>   the modifier keys held while dragging
>>
>> Missing Feature:
>>
>>- A configuration panel. I'm currently overhauling it.
>>
>> You play with it at https://burningtreec.github.io/tiddlywiki-muuri
>>
>> On the Demo page there's a Sidebar Grid where you can drop tiddlers into. 
>> Holding shift while dragging adds a tag to that Tiddler. Holding ctrl-shift 
>> while dragging shifts the Tiddler to edit mode.
>>
>> That's just a Demo of what can be built with the Muuri StoryView.
>>
>> If we think about it - having a Muuri StoryView in the main river on the 
>> left and having one or two Grids in the SideBar with some defined 
>> dropActions makes the whole TiddlyWiki a Kanban on steroids :)
>>
>>
>> As always, I'm open for critics and ideas, just leave me a post
>>
>> all the best, BTC
>>
>> -- 
>> You received this message because you 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/8454e0f9-79b9-4954-a38d-c33fc8fb4008n%40googlegroups.com
>>  
>> 
>> .
>>
>

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

[tw5] Re: Showing off: Muuri StoryView 0.2.0 Prerelease

[BurningTreeC]

@Saq,

>Hmm. I think I've seen Jeremy mention wanting to eventually deprecate data 
tiddlers, and using individual tiddlers is the more TiddlyWiki way. So this 
would mean storyViewConfig would be a namespace. Alternatively you could 
use fields in the same tiddler for different parameters.

I think I'll go the namespace way. I've already started with it and it's 
indeed a better way to configure the storyview. Thanks for the tip!

best wishes

saq.i...@gmail.com schrieb am Sonntag, 20. Dezember 2020 um 18:39:20 UTC+1:

> @BTC
>  
>
>> that would indeed be neat. should that storyViewConfig be a single 
>> tiddler (like a data tiddler) or a namespace?
>>
>
> Hmm. I think I've seen Jeremy mention wanting to eventually deprecate data 
> tiddlers, and using individual tiddlers is the more TiddlyWiki way. So this 
> would mean storyViewConfig would be a namespace. Alternatively you could 
> use fields in the same tiddler for different parameters.
>

-- 
You received this message because you are subscribed to the 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/4de90814-48d6-4d4a-b255-13b532d70744n%40googlegroups.com.

[tw5] Disable parse rule within a template

[Soren Bjornstad]

Using the official KaTeX plugin, I am hoping for a way to disable KaTeX 
rendering in a tiddler when rendering that tiddler using a specific 
template.

Use case: I'm programmatically extracting HTML content from TiddlyWiki by 
using Node to render it through a template, but I want to preserve the math 
notation specifically as is because the target system already natively 
supports LaTeX within $$ delimiters. (If I don't do anything special to the 
math fragments, I get a corrupted version of the markup shown twice in my 
output!)

I see that KaTeX is implemented as an inline parse rule, `latex-parser`, 
but I don't want to turn that off globally, because I still want the markup 
to render normally when viewing the wiki, just not when extracting content 
from it. The `\rules except` pragma doesn't appear to disable the rule in 
tiddlers transcluded into a tiddler, only within that exact tiddler. Is 
there some other way to adjust the parse rules?

-- 
You received this message because you are subscribed to the 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/9a442ca8-81fd-4c0f-a106-aeb1d758dd58n%40googlegroups.com.

Re: [tw5] TiddlyWiki keeps offloading on iPhone and iPad: any solution?

[Jeremy Ruston]

Hi Ivan

This sounds like a Quine issue. iPad apps are apt to be unloaded in the 
background when memory is low, but I think it could also be related to the 
particular file provider you're using.  I'd suggest posting in the Quine Google 
Group:

https://groups.google.com/forum/#!forum/quine-app

Best wishes

Jeremy


--
Jeremy Ruston
jer...@jermolene.com
https://jermolene.com

> On 18 Dec 2020, at 06:54, IvanPsy  wrote:
> 
> Greetings,
> 
> I store TiddlyWiki on iCloud.
> Though the syncing works like a charm on iPad and iPhone (I use Quine 2), the 
> file keeps offloading from my device.
> I mean: each time I go back to my TiddlyWiki, I have to wait for the file to 
> be downloaded again Bedford being able to open it.
> So I can’t rely on TiddlyWiki for fast reference.
> 
> A scenario:
> I need a fast information stored on my TiddlyWiki, I open up the iPhone...but 
> I have to wait for the file to download.
> 
> It’s 24Mb right now, so it’s pretty fast (some seconds), but what happens 
> when the file gets bigger?
> I need for the file to stay at my disposal on my devices.
> 
> It keeps me from investing on TiddlyWiki.
> 
> Any solution or workaround?
> 
> 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/14671cbf-9ff3-4c5e-a631-43b24a05efccn%40googlegroups.com.

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/C0E9F1ED-CC62-41FF-96E3-88696DAFB1A2%40gmail.com.

Re: [tw5] Showing off: Muuri StoryView 0.2.0 Prerelease

[Mohammad Rahmani]

Hi BTC,

 Excellent job! Muuri 2.0 a Christmass gift ;-)


Best wishes
Mohammad


On Sun, Dec 20, 2020 at 2:16 PM BurningTreeC 
wrote:

>
> Hi TiddlyWiki folks,
>
> I want to show you my Muuri StoryView plugin version 0.2.0 Prerelease.
>
> It contains various Bugfixes and can overall be considered more stable
>
> New Feature:
>
>- Drop Actions: actions triggered when dropping an item from one grid
>into another grid
>   - the actionTiddler and modifier variables are available within the
>   action-string, containing the title of the dragged item respectively the
>   modifier keys held while dragging
>
> Missing Feature:
>
>- A configuration panel. I'm currently overhauling it.
>
> You play with it at https://burningtreec.github.io/tiddlywiki-muuri
>
> On the Demo page there's a Sidebar Grid where you can drop tiddlers into.
> Holding shift while dragging adds a tag to that Tiddler. Holding ctrl-shift
> while dragging shifts the Tiddler to edit mode.
>
> That's just a Demo of what can be built with the Muuri StoryView.
>
> If we think about it - having a Muuri StoryView in the main river on the
> left and having one or two Grids in the SideBar with some defined
> dropActions makes the whole TiddlyWiki a Kanban on steroids :)
>
>
> As always, I'm open for critics and ideas, just leave me a post
>
> all the best, BTC
>
> --
> You received this message because you are subscribed to the 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/8454e0f9-79b9-4954-a38d-c33fc8fb4008n%40googlegroups.com
> 
> .
>

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

[tw5] Re: Showing off: Muuri StoryView 0.2.0 Prerelease

[Saq Imtiaz]

@BTC
 

> that would indeed be neat. should that storyViewConfig be a single tiddler 
> (like a data tiddler) or a namespace?
>

Hmm. I think I've seen Jeremy mention wanting to eventually deprecate data 
tiddlers, and using individual tiddlers is the more TiddlyWiki way. So this 
would mean storyViewConfig would be a namespace. Alternatively you could 
use fields in the same tiddler for different parameters.

-- 
You received this message because you are subscribed to the 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/e4fd2753-8434-4e19-9aea-e86aea2dd324n%40googlegroups.com.

[tw5] Re: Showing off: Muuri StoryView 0.2.0 Prerelease

[Ste]

Hi.  Was just wondering if the mobile view could be set to toggle between 
on and two coloumns? 
On Sunday, 20 December 2020 at 15:54:57 UTC BurningTreeC wrote:

> @Saq,
>
> > what would be neat is if Muuri looked for a storyViewConfig tiddler 
> attribute on the list widget, and if it didn't exist used a default value 
> for the config tiddler.
>
> that would indeed be neat. should that storyViewConfig be a single tiddler 
> (like a data tiddler) or a namespace?
>
> > Then a layout with multiple stories could just specify a storyViewConfig 
> attribute for each extra stories list view, and if Muuri was used it would 
> be able to use that configTiddler. This way a layout does not need to know 
> if Muuri might be used, and installing Muuri would not necessitate editing 
> shadow tiddlers.
>
> understood, yes that would be great...
>
> In the meantime I've updated the plugin so that also the dragHandle and 
> the connectionSelector can be configured by a config tiddler
>
>
>
> saq.i...@gmail.com schrieb am Sonntag, 20. Dezember 2020 um 16:24:24 
> UTC+1:
>
>> @BTC what would be neat is if Muuri looked for a storyViewConfig tiddler 
>> attribute on the list widget, and if it didn't exist used a default value 
>> for the config tiddler.
>>
>> Then a layout with multiple stories could just specify a storyViewConfig 
>> attribute for each extra stories list view, and if Muuri was used it would 
>> be able to use that configTiddler. This way a layout does not need to know 
>> if Muuri might be used, and installing Muuri would not necessitate editing 
>> shadow tiddlers.
>>
>> On Sunday, December 20, 2020 at 4:17:14 PM UTC+1 BurningTreeC wrote:
>>
>>> @Saq, right now almost every configuration for the main muuri story (the 
>>> one in the story river) is done using a config tiddler. Only the connection 
>>> with another Grid must be done with an attribute on the list widget. I 
>>> could make that also configurable using a config tiddler
>>>
>>> saq.i...@gmail.com schrieb am Sonntag, 20. Dezember 2020 um 14:47:11 
>>> UTC+1:
>>>
 @BTC yeah there isn't an obvious solution that comes to mind but I will 
 think about it. 

 I considered a config tiddler that is determined by the name of the 
 storylist, but that would preclude two muuri with the same storylist.

 On Sunday, December 20, 2020 at 2:42:05 PM UTC+1 BurningTreeC wrote:

> Hi Saq,
>
> > In principle I quite like that the storyview gets its 
> attributes/settings from the ListWidget. In practice however this means 
> having to edit shadow tiddlers. I am wondering if there is way around 
> that...
>
> Yes that's the downside of it - I haven't found another way around it 
> but I'm open for ideas
>
> best wishes
>
> saq.i...@gmail.com schrieb am Sonntag, 20. Dezember 2020 um 14:37:09 
> UTC+1:
>
>> Looks good @BTC!
>>
>> Love the dragHandle support.
>>
>> In principle I quite like that the storyview gets its 
>> attributes/settings from the ListWidget. In practice however this means 
>> having to edit shadow tiddlers. I am wondering if there is way around 
>> that...
>>
>> Cheers,
>> Saq
>>
>> On Sunday, December 20, 2020 at 11:45:56 AM UTC+1 BurningTreeC wrote:
>>
>>>
>>> Hi TiddlyWiki folks,
>>>
>>> I want to show you my Muuri StoryView plugin version 0.2.0 
>>> Prerelease.
>>>
>>> It contains various Bugfixes and can overall be considered more 
>>> stable
>>>
>>> New Feature:
>>>
>>>- Drop Actions: actions triggered when dropping an item from one 
>>>grid into another grid
>>>   - the actionTiddler and modifier variables are available 
>>>   within the action-string, containing the title of the dragged 
>>> item 
>>>   respectively the modifier keys held while dragging
>>>
>>> Missing Feature:
>>>
>>>- A configuration panel. I'm currently overhauling it.
>>>
>>> You play with it at https://burningtreec.github.io/tiddlywiki-muuri
>>>
>>> On the Demo page there's a Sidebar Grid where you can drop tiddlers 
>>> into. Holding shift while dragging adds a tag to that Tiddler. Holding 
>>> ctrl-shift while dragging shifts the Tiddler to edit mode.
>>>
>>> That's just a Demo of what can be built with the Muuri StoryView.
>>>
>>> If we think about it - having a Muuri StoryView in the main river on 
>>> the left and having one or two Grids in the SideBar with some defined 
>>> dropActions makes the whole TiddlyWiki a Kanban on steroids :)
>>>
>>>
>>> As always, I'm open for critics and ideas, just leave me a post
>>>
>>> all the best, BTC
>>>
>>

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to 

[tw5] Re: Showing off: Muuri StoryView 0.2.0 Prerelease

[BurningTreeC]

@Saq,

> what would be neat is if Muuri looked for a storyViewConfig tiddler 
attribute on the list widget, and if it didn't exist used a default value 
for the config tiddler.

that would indeed be neat. should that storyViewConfig be a single tiddler 
(like a data tiddler) or a namespace?

> Then a layout with multiple stories could just specify a storyViewConfig 
attribute for each extra stories list view, and if Muuri was used it would 
be able to use that configTiddler. This way a layout does not need to know 
if Muuri might be used, and installing Muuri would not necessitate editing 
shadow tiddlers.

understood, yes that would be great...

In the meantime I've updated the plugin so that also the dragHandle and the 
connectionSelector can be configured by a config tiddler



saq.i...@gmail.com schrieb am Sonntag, 20. Dezember 2020 um 16:24:24 UTC+1:

> @BTC what would be neat is if Muuri looked for a storyViewConfig tiddler 
> attribute on the list widget, and if it didn't exist used a default value 
> for the config tiddler.
>
> Then a layout with multiple stories could just specify a storyViewConfig 
> attribute for each extra stories list view, and if Muuri was used it would 
> be able to use that configTiddler. This way a layout does not need to know 
> if Muuri might be used, and installing Muuri would not necessitate editing 
> shadow tiddlers.
>
> On Sunday, December 20, 2020 at 4:17:14 PM UTC+1 BurningTreeC wrote:
>
>> @Saq, right now almost every configuration for the main muuri story (the 
>> one in the story river) is done using a config tiddler. Only the connection 
>> with another Grid must be done with an attribute on the list widget. I 
>> could make that also configurable using a config tiddler
>>
>> saq.i...@gmail.com schrieb am Sonntag, 20. Dezember 2020 um 14:47:11 
>> UTC+1:
>>
>>> @BTC yeah there isn't an obvious solution that comes to mind but I will 
>>> think about it. 
>>>
>>> I considered a config tiddler that is determined by the name of the 
>>> storylist, but that would preclude two muuri with the same storylist.
>>>
>>> On Sunday, December 20, 2020 at 2:42:05 PM UTC+1 BurningTreeC wrote:
>>>
 Hi Saq,

 > In principle I quite like that the storyview gets its 
 attributes/settings from the ListWidget. In practice however this means 
 having to edit shadow tiddlers. I am wondering if there is way around 
 that...

 Yes that's the downside of it - I haven't found another way around it 
 but I'm open for ideas

 best wishes

 saq.i...@gmail.com schrieb am Sonntag, 20. Dezember 2020 um 14:37:09 
 UTC+1:

> Looks good @BTC!
>
> Love the dragHandle support.
>
> In principle I quite like that the storyview gets its 
> attributes/settings from the ListWidget. In practice however this means 
> having to edit shadow tiddlers. I am wondering if there is way around 
> that...
>
> Cheers,
> Saq
>
> On Sunday, December 20, 2020 at 11:45:56 AM UTC+1 BurningTreeC wrote:
>
>>
>> Hi TiddlyWiki folks,
>>
>> I want to show you my Muuri StoryView plugin version 0.2.0 Prerelease.
>>
>> It contains various Bugfixes and can overall be considered more stable
>>
>> New Feature:
>>
>>- Drop Actions: actions triggered when dropping an item from one 
>>grid into another grid
>>   - the actionTiddler and modifier variables are available 
>>   within the action-string, containing the title of the dragged item 
>>   respectively the modifier keys held while dragging
>>
>> Missing Feature:
>>
>>- A configuration panel. I'm currently overhauling it.
>>
>> You play with it at https://burningtreec.github.io/tiddlywiki-muuri
>>
>> On the Demo page there's a Sidebar Grid where you can drop tiddlers 
>> into. Holding shift while dragging adds a tag to that Tiddler. Holding 
>> ctrl-shift while dragging shifts the Tiddler to edit mode.
>>
>> That's just a Demo of what can be built with the Muuri StoryView.
>>
>> If we think about it - having a Muuri StoryView in the main river on 
>> the left and having one or two Grids in the SideBar with some defined 
>> dropActions makes the whole TiddlyWiki a Kanban on steroids :)
>>
>>
>> As always, I'm open for critics and ideas, just leave me a post
>>
>> all the best, BTC
>>
>

-- 
You received this message because you are subscribed to the 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/089e3a2b-51e9-49bb-91aa-13a75186abb1n%40googlegroups.com.

[tw5] Re: Showing off: Muuri StoryView 0.2.0 Prerelease

[BurningTreeC]

@Sylvain,

> Since you can also choose our storyview engine for this second column, 
it's sound perfect (but it's not ^-^', in my test play with Muuri change 
content from first colums).

If you use muuri in the second column of the stories plugin, you need to 
specify the storyList attribute to the list widget so that muuri doesn't 
change the default $:/StoryList. So if the second column lists 
"[list[$:/StoryList2]]" you need to add storyList="$:/StoryList2" to the 
list widget

best wishes

sil...@gmail.com schrieb am Sonntag, 20. Dezember 2020 um 16:18:11 UTC+1:

> Le dimanche 20 décembre 2020 à 14:47:02 UTC+1, BurningTreeC a écrit :
>
>> > Another reaction, I say to myself that I would like to be able to fix a 
>> column, the first one for example, and thus scroll through the other 
>> columns? This may not make sense, it's just a comment.
>>
>> Makes sense somehow... That reminds me of the Stroll plugin. But it's not 
>> currently possible out-of-the box with the Muuri plugin.
>>
>
> You're right, with Strories plugin, this is what I was in mind.
> https://github.com/saqimtiaz/sq-tw/blob/master/stories.html
>
> Since you can also choose our storyview engine for this second column, 
> it's sound perfect (but it's not ^-^', in my test play with Muuri change 
> content from first colums).
>
> Cheers,
> Sylvain
>

-- 
You received this message because you are subscribed to the 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/9d1d464e-aa81-4803-8b33-38af759e7e0an%40googlegroups.com.

[tw5] Re: Showing off: Muuri StoryView 0.2.0 Prerelease

[Saq Imtiaz]

@BTC what would be neat is if Muuri looked for a storyViewConfig tiddler 
attribute on the list widget, and if it didn't exist used a default value 
for the config tiddler.

Then a layout with multiple stories could just specify a storyViewConfig 
attribute for each extra stories list view, and if Muuri was used it would 
be able to use that configTiddler. This way a layout does not need to know 
if Muuri might be used, and installing Muuri would not necessitate editing 
shadow tiddlers.

On Sunday, December 20, 2020 at 4:17:14 PM UTC+1 BurningTreeC wrote:

> @Saq, right now almost every configuration for the main muuri story (the 
> one in the story river) is done using a config tiddler. Only the connection 
> with another Grid must be done with an attribute on the list widget. I 
> could make that also configurable using a config tiddler
>
> saq.i...@gmail.com schrieb am Sonntag, 20. Dezember 2020 um 14:47:11 
> UTC+1:
>
>> @BTC yeah there isn't an obvious solution that comes to mind but I will 
>> think about it. 
>>
>> I considered a config tiddler that is determined by the name of the 
>> storylist, but that would preclude two muuri with the same storylist.
>>
>> On Sunday, December 20, 2020 at 2:42:05 PM UTC+1 BurningTreeC wrote:
>>
>>> Hi Saq,
>>>
>>> > In principle I quite like that the storyview gets its 
>>> attributes/settings from the ListWidget. In practice however this means 
>>> having to edit shadow tiddlers. I am wondering if there is way around 
>>> that...
>>>
>>> Yes that's the downside of it - I haven't found another way around it 
>>> but I'm open for ideas
>>>
>>> best wishes
>>>
>>> saq.i...@gmail.com schrieb am Sonntag, 20. Dezember 2020 um 14:37:09 
>>> UTC+1:
>>>
 Looks good @BTC!

 Love the dragHandle support.

 In principle I quite like that the storyview gets its 
 attributes/settings from the ListWidget. In practice however this means 
 having to edit shadow tiddlers. I am wondering if there is way around 
 that...

 Cheers,
 Saq

 On Sunday, December 20, 2020 at 11:45:56 AM UTC+1 BurningTreeC wrote:

>
> Hi TiddlyWiki folks,
>
> I want to show you my Muuri StoryView plugin version 0.2.0 Prerelease.
>
> It contains various Bugfixes and can overall be considered more stable
>
> New Feature:
>
>- Drop Actions: actions triggered when dropping an item from one 
>grid into another grid
>   - the actionTiddler and modifier variables are available within 
>   the action-string, containing the title of the dragged item 
> respectively 
>   the modifier keys held while dragging
>
> Missing Feature:
>
>- A configuration panel. I'm currently overhauling it.
>
> You play with it at https://burningtreec.github.io/tiddlywiki-muuri
>
> On the Demo page there's a Sidebar Grid where you can drop tiddlers 
> into. Holding shift while dragging adds a tag to that Tiddler. Holding 
> ctrl-shift while dragging shifts the Tiddler to edit mode.
>
> That's just a Demo of what can be built with the Muuri StoryView.
>
> If we think about it - having a Muuri StoryView in the main river on 
> the left and having one or two Grids in the SideBar with some defined 
> dropActions makes the whole TiddlyWiki a Kanban on steroids :)
>
>
> As always, I'm open for critics and ideas, just leave me a post
>
> all the best, BTC
>


-- 
You received this message because you are subscribed to the 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/600837ac-daf5-4275-9c00-6bd1ab1d1c35n%40googlegroups.com.

[tw5] Re: Showing off: Muuri StoryView 0.2.0 Prerelease

[Sylvain Naudin]

Le dimanche 20 décembre 2020 à 14:47:02 UTC+1, BurningTreeC a écrit :

> > Another reaction, I say to myself that I would like to be able to fix a 
> column, the first one for example, and thus scroll through the other 
> columns? This may not make sense, it's just a comment.
>
> Makes sense somehow... That reminds me of the Stroll plugin. But it's not 
> currently possible out-of-the box with the Muuri plugin.
>

You're right, with Strories plugin, this is what I was in mind.
https://github.com/saqimtiaz/sq-tw/blob/master/stories.html

Since you can also choose our storyview engine for this second column, it's 
sound perfect (but it's not ^-^', in my test play with Muuri change content 
from first colums).

Cheers,
Sylvain

-- 
You received this message because you are subscribed to the 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/e689792a-1791-411d-9984-fb6a3744c689n%40googlegroups.com.

[tw5] Re: Showing off: Muuri StoryView 0.2.0 Prerelease

[BurningTreeC]

@Saq, right now almost every configuration for the main muuri story (the 
one in the story river) is done using a config tiddler. Only the connection 
with another Grid must be done with an attribute on the list widget. I 
could make that also configurable using a config tiddler

saq.i...@gmail.com schrieb am Sonntag, 20. Dezember 2020 um 14:47:11 UTC+1:

> @BTC yeah there isn't an obvious solution that comes to mind but I will 
> think about it. 
>
> I considered a config tiddler that is determined by the name of the 
> storylist, but that would preclude two muuri with the same storylist.
>
> On Sunday, December 20, 2020 at 2:42:05 PM UTC+1 BurningTreeC wrote:
>
>> Hi Saq,
>>
>> > In principle I quite like that the storyview gets its 
>> attributes/settings from the ListWidget. In practice however this means 
>> having to edit shadow tiddlers. I am wondering if there is way around 
>> that...
>>
>> Yes that's the downside of it - I haven't found another way around it but 
>> I'm open for ideas
>>
>> best wishes
>>
>> saq.i...@gmail.com schrieb am Sonntag, 20. Dezember 2020 um 14:37:09 
>> UTC+1:
>>
>>> Looks good @BTC!
>>>
>>> Love the dragHandle support.
>>>
>>> In principle I quite like that the storyview gets its 
>>> attributes/settings from the ListWidget. In practice however this means 
>>> having to edit shadow tiddlers. I am wondering if there is way around 
>>> that...
>>>
>>> Cheers,
>>> Saq
>>>
>>> On Sunday, December 20, 2020 at 11:45:56 AM UTC+1 BurningTreeC wrote:
>>>

 Hi TiddlyWiki folks,

 I want to show you my Muuri StoryView plugin version 0.2.0 Prerelease.

 It contains various Bugfixes and can overall be considered more stable

 New Feature:

- Drop Actions: actions triggered when dropping an item from one 
grid into another grid
   - the actionTiddler and modifier variables are available within 
   the action-string, containing the title of the dragged item 
 respectively 
   the modifier keys held while dragging

 Missing Feature:

- A configuration panel. I'm currently overhauling it.

 You play with it at https://burningtreec.github.io/tiddlywiki-muuri

 On the Demo page there's a Sidebar Grid where you can drop tiddlers 
 into. Holding shift while dragging adds a tag to that Tiddler. Holding 
 ctrl-shift while dragging shifts the Tiddler to edit mode.

 That's just a Demo of what can be built with the Muuri StoryView.

 If we think about it - having a Muuri StoryView in the main river on 
 the left and having one or two Grids in the SideBar with some defined 
 dropActions makes the whole TiddlyWiki a Kanban on steroids :)


 As always, I'm open for critics and ideas, just leave me a post

 all the best, BTC

>>>

-- 
You received this message because you are subscribed to the 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/adc758b7-8fc8-45ec-8514-105b7259f70fn%40googlegroups.com.

Re: [tw5] [Request] Mashup of list-search macro and "Search TiddlyWiki toolmap"

[David Gifford]

There it is! Thanks Mohammad!

On Saturday, December 19, 2020 at 10:45:37 PM UTC-6 Mohammad wrote:

> David,
> 1.  Goto https://github.com/saqimtiaz/sq-tw
> 2. Look for streams-tiddlytoolmap.html 
> 
>
> Best wishes
> Mohammad
>
>
> On Sun, Dec 20, 2020 at 4:41 AM David Gifford  wrote:
>
>> Hi Mohammad, thanks for the tip.
>>
>> Unfortunately, I couldn't find it at Saq's repo. Looking for it in there 
>> just reinforced how much I don't like GitHub. Nothing said toolmap, and 
>> searching for toolmap didn't turn up anything...If you have a more specific 
>> link, that would be great. Blessings.
>>
>> On Saturday, December 19, 2020 at 12:55:00 PM UTC-6 Mohammad wrote:
>>
>>> Hi David,
>>>  Great efforts, do you know Saq has an implementation of the whole 
>>> Toolmap in Tiddlywiki? Have a look at Saq GitHub repo.
>>>
>>> Best wishes
>>> Mohammad
>>>
>>>
>>> On Sat, Dec 19, 2020 at 8:21 PM David Gifford  wrote:
>>>

 Hi guys

 I really like Mohammad's "Search TiddlyWiki toolmap", which lets you 
 type a search string, then click a link to open that as a search in the 
 toolmap page in Dynalist.

- (
https://kookma.github.io/TW-Scripts/#Search%20Tiddlywiki%20Toolmap)

 But I also really like to see a list of options as I am searching, so I 
 don't have to pull terms out of my head. See my tweak of Tobias' 
 list-search macro, where the tiddlers get listed as links to external 
 websites.

- 

 https://giffmex.org/gifts/documenting.tw.html#List-Search%20with%20list%20items%20as%20external%20links

 I would like to mashup these two into the following, but every attempt 
 I tried failed. Too complicated for me at present. What I want to do is:

- Take notes in a Dynalist document.
- Organize by topic in Dynalist.
- Add the topics as tiddlers to a TiddlyWiki.
- Have a list-search macro that lists all the tiddlers and filters 
them as I type
- *so far so good, I have all of this. Now the part I don't know 
how to do:*
- adapt my custom "listitemtemplate" tiddler
- so that the tiddlers in the list-search search results 
- function as links to Dynalist searches for the tiddler titles.

 It seems like what the listitemtemplate tiddler needs is something like 
 the logic below:

 ---
 define (something) something
 end

  + https://dynalist.io/...#q='">  + >>> title> + <" /a>
 ---

 But: a) I don't know how to go about it, and b) maybe there is just a 
 better way to think about it than the logic above.

 I would appreciate any help! And I will document the answer in my 
 documenting.tw site for the greater good.

 Thanks and blessings.

 -- 
 You received this message because you are subscribed to the Google 
 Groups "TiddlyWiki" group.
 To unsubscribe from this group and stop receiving emails from it, send 
 an email to tiddlywiki+...@googlegroups.com.
 To view this discussion on the web visit 
 https://groups.google.com/d/msgid/tiddlywiki/09a9023f-822c-4390-82d6-30ba942613d9n%40googlegroups.com
  
 
 .

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

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

[tw5] Re: Showing off: Muuri StoryView 0.2.0 Prerelease

[Sylvain Naudin]

Le dimanche 20 décembre 2020 à 14:47:02 UTC+1, BurningTreeC a écrit :

> Set the tiddler "$:/config/muuri/storyview/align-right" to "no" and 
> tiddlers will be aligned from left to right.


Yes, this is what I was looking for :)
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/124c7f5d-cd8f-4aac-acf3-caf5a7d48219n%40googlegroups.com.

[tw5] Re: Showing off: Muuri StoryView 0.2.0 Prerelease

[Saq Imtiaz]

@BTC yeah there isn't an obvious solution that comes to mind but I will 
think about it. 

I considered a config tiddler that is determined by the name of the 
storylist, but that would preclude two muuri with the same storylist.

On Sunday, December 20, 2020 at 2:42:05 PM UTC+1 BurningTreeC wrote:

> Hi Saq,
>
> > In principle I quite like that the storyview gets its 
> attributes/settings from the ListWidget. In practice however this means 
> having to edit shadow tiddlers. I am wondering if there is way around 
> that...
>
> Yes that's the downside of it - I haven't found another way around it but 
> I'm open for ideas
>
> best wishes
>
> saq.i...@gmail.com schrieb am Sonntag, 20. Dezember 2020 um 14:37:09 
> UTC+1:
>
>> Looks good @BTC!
>>
>> Love the dragHandle support.
>>
>> In principle I quite like that the storyview gets its attributes/settings 
>> from the ListWidget. In practice however this means having to edit shadow 
>> tiddlers. I am wondering if there is way around that...
>>
>> Cheers,
>> Saq
>>
>> On Sunday, December 20, 2020 at 11:45:56 AM UTC+1 BurningTreeC wrote:
>>
>>>
>>> Hi TiddlyWiki folks,
>>>
>>> I want to show you my Muuri StoryView plugin version 0.2.0 Prerelease.
>>>
>>> It contains various Bugfixes and can overall be considered more stable
>>>
>>> New Feature:
>>>
>>>- Drop Actions: actions triggered when dropping an item from one 
>>>grid into another grid
>>>   - the actionTiddler and modifier variables are available within 
>>>   the action-string, containing the title of the dragged item 
>>> respectively 
>>>   the modifier keys held while dragging
>>>
>>> Missing Feature:
>>>
>>>- A configuration panel. I'm currently overhauling it.
>>>
>>> You play with it at https://burningtreec.github.io/tiddlywiki-muuri
>>>
>>> On the Demo page there's a Sidebar Grid where you can drop tiddlers 
>>> into. Holding shift while dragging adds a tag to that Tiddler. Holding 
>>> ctrl-shift while dragging shifts the Tiddler to edit mode.
>>>
>>> That's just a Demo of what can be built with the Muuri StoryView.
>>>
>>> If we think about it - having a Muuri StoryView in the main river on the 
>>> left and having one or two Grids in the SideBar with some defined 
>>> dropActions makes the whole TiddlyWiki a Kanban on steroids :)
>>>
>>>
>>> As always, I'm open for critics and ideas, just leave me a post
>>>
>>> all the best, BTC
>>>
>>

-- 
You received this message because you are subscribed to the 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/2beececb-4f26-4c89-9884-1777609754dan%40googlegroups.com.

[tw5] Re: Showing off: Muuri StoryView 0.2.0 Prerelease

[BurningTreeC]

Hi Sylvain,

Thank you! I like your minstyle theme a lot as well!

> So I was wondering if it is possible (or already the case) to occupy the 
space in the first column first and not the second, for example when there 
is only one tiddler?
That way if I open a second one, it will fit on the right.

If I understand you correctly, you mean the alignment of the tiddlers from 
right to left or left to right? If that's the case, there's a configuration 
option. Set the tiddler "$:/config/muuri/storyview/align-right" to "no" and 
tiddlers will be aligned from left to right.

> Another reaction, I say to myself that I would like to be able to fix a 
column, the first one for example, and thus scroll through the other 
columns? This may not make sense, it's just a comment.

Makes sense somehow... That reminds me of the Stroll plugin. But it's not 
currently possible out-of-the box with the Muuri plugin.

best whishes, BTC

sil...@gmail.com schrieb am Sonntag, 20. Dezember 2020 um 14:37:49 UTC+1:

> Hi BTC,
>
> This is great demo. Congrats and thanks for this great job.
> I put the plugin on my minstyle wiki that I'm currently building and it 
> fits pretty well.
>
> I have never really taken the time to use and study Muuri.
> So I was wondering if it is possible (or already the case) to occupy the 
> space in the first column first and not the second, for example when there 
> is only one tiddler?
> That way if I open a second one, it will fit on the right.
>
> Another reaction, I say to myself that I would like to be able to fix a 
> column, the first one for example, and thus scroll through the other 
> columns? This may not make sense, it's just a comment.
>
> Regards,
> Sylvain
>
>
> Le dimanche 20 décembre 2020 à 11:45:56 UTC+1, BurningTreeC a écrit :
>
>>
>> Hi TiddlyWiki folks,
>>
>> I want to show you my Muuri StoryView plugin version 0.2.0 Prerelease.
>>
>> It contains various Bugfixes and can overall be considered more stable
>>
>> New Feature:
>>
>>- Drop Actions: actions triggered when dropping an item from one grid 
>>into another grid
>>   - the actionTiddler and modifier variables are available within 
>>   the action-string, containing the title of the dragged item 
>> respectively 
>>   the modifier keys held while dragging
>>
>> Missing Feature:
>>
>>- A configuration panel. I'm currently overhauling it.
>>
>> You play with it at https://burningtreec.github.io/tiddlywiki-muuri
>>
>> On the Demo page there's a Sidebar Grid where you can drop tiddlers into. 
>> Holding shift while dragging adds a tag to that Tiddler. Holding ctrl-shift 
>> while dragging shifts the Tiddler to edit mode.
>>
>> That's just a Demo of what can be built with the Muuri StoryView.
>>
>> If we think about it - having a Muuri StoryView in the main river on the 
>> left and having one or two Grids in the SideBar with some defined 
>> dropActions makes the whole TiddlyWiki a Kanban on steroids :)
>>
>>
>> As always, I'm open for critics and ideas, just leave me a post
>>
>> all the best, BTC
>>
>

-- 
You received this message because you are subscribed to the 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/0f0ace73-accd-402d-8d4f-6f59a303ba74n%40googlegroups.com.

[tw5] Re: Showing off: Muuri StoryView 0.2.0 Prerelease

[BurningTreeC]

Hi Saq,

> In principle I quite like that the storyview gets its attributes/settings 
from the ListWidget. In practice however this means having to edit shadow 
tiddlers. I am wondering if there is way around that...

Yes that's the downside of it - I haven't found another way around it but 
I'm open for ideas

best wishes

saq.i...@gmail.com schrieb am Sonntag, 20. Dezember 2020 um 14:37:09 UTC+1:

> Looks good @BTC!
>
> Love the dragHandle support.
>
> In principle I quite like that the storyview gets its attributes/settings 
> from the ListWidget. In practice however this means having to edit shadow 
> tiddlers. I am wondering if there is way around that...
>
> Cheers,
> Saq
>
> On Sunday, December 20, 2020 at 11:45:56 AM UTC+1 BurningTreeC wrote:
>
>>
>> Hi TiddlyWiki folks,
>>
>> I want to show you my Muuri StoryView plugin version 0.2.0 Prerelease.
>>
>> It contains various Bugfixes and can overall be considered more stable
>>
>> New Feature:
>>
>>- Drop Actions: actions triggered when dropping an item from one grid 
>>into another grid
>>   - the actionTiddler and modifier variables are available within 
>>   the action-string, containing the title of the dragged item 
>> respectively 
>>   the modifier keys held while dragging
>>
>> Missing Feature:
>>
>>- A configuration panel. I'm currently overhauling it.
>>
>> You play with it at https://burningtreec.github.io/tiddlywiki-muuri
>>
>> On the Demo page there's a Sidebar Grid where you can drop tiddlers into. 
>> Holding shift while dragging adds a tag to that Tiddler. Holding ctrl-shift 
>> while dragging shifts the Tiddler to edit mode.
>>
>> That's just a Demo of what can be built with the Muuri StoryView.
>>
>> If we think about it - having a Muuri StoryView in the main river on the 
>> left and having one or two Grids in the SideBar with some defined 
>> dropActions makes the whole TiddlyWiki a Kanban on steroids :)
>>
>>
>> As always, I'm open for critics and ideas, just leave me a post
>>
>> all the best, BTC
>>
>

-- 
You received this message because you are subscribed to the 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/09f927df-4c1d-4301-9b28-cc1823c8c74bn%40googlegroups.com.

Re: [tw5] [Request] Mashup of list-search macro and "Search TiddlyWiki toolmap"

[Saq Imtiaz]

Here is the original post about 
it: https://groups.google.com/g/tiddlywiki/c/DRpjXlSfuVU/m/LODwdHWiCAAJ

Note that this was an experiment in OPML import, that I have since used as 
a demo for large streams when checking performance.

The soon to be released Streams 0.2 renders the toolmap (with all nodes 
expanded) over 3 times faster.

Cheers,
Saq

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

[tw5] Re: Showing off: Muuri StoryView 0.2.0 Prerelease

[Sylvain Naudin]

Hi BTC,

This is great demo. Congrats and thanks for this great job.
I put the plugin on my minstyle wiki that I'm currently building and it 
fits pretty well.

I have never really taken the time to use and study Muuri.
So I was wondering if it is possible (or already the case) to occupy the 
space in the first column first and not the second, for example when there 
is only one tiddler?
That way if I open a second one, it will fit on the right.

Another reaction, I say to myself that I would like to be able to fix a 
column, the first one for example, and thus scroll through the other 
columns? This may not make sense, it's just a comment.

Regards,
Sylvain


Le dimanche 20 décembre 2020 à 11:45:56 UTC+1, BurningTreeC a écrit :

>
> Hi TiddlyWiki folks,
>
> I want to show you my Muuri StoryView plugin version 0.2.0 Prerelease.
>
> It contains various Bugfixes and can overall be considered more stable
>
> New Feature:
>
>- Drop Actions: actions triggered when dropping an item from one grid 
>into another grid
>   - the actionTiddler and modifier variables are available within the 
>   action-string, containing the title of the dragged item respectively 
> the 
>   modifier keys held while dragging
>
> Missing Feature:
>
>- A configuration panel. I'm currently overhauling it.
>
> You play with it at https://burningtreec.github.io/tiddlywiki-muuri
>
> On the Demo page there's a Sidebar Grid where you can drop tiddlers into. 
> Holding shift while dragging adds a tag to that Tiddler. Holding ctrl-shift 
> while dragging shifts the Tiddler to edit mode.
>
> That's just a Demo of what can be built with the Muuri StoryView.
>
> If we think about it - having a Muuri StoryView in the main river on the 
> left and having one or two Grids in the SideBar with some defined 
> dropActions makes the whole TiddlyWiki a Kanban on steroids :)
>
>
> As always, I'm open for critics and ideas, just leave me a post
>
> all the best, BTC
>

-- 
You received this message because you are subscribed to the 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/d1528a4d-c0a2-4454-9293-f5f5c56a0fd2n%40googlegroups.com.

[tw5] Re: Showing off: Muuri StoryView 0.2.0 Prerelease

[Saq Imtiaz]

Looks good @BTC!

Love the dragHandle support.

In principle I quite like that the storyview gets its attributes/settings 
from the ListWidget. In practice however this means having to edit shadow 
tiddlers. I am wondering if there is way around that...

Cheers,
Saq

On Sunday, December 20, 2020 at 11:45:56 AM UTC+1 BurningTreeC wrote:

>
> Hi TiddlyWiki folks,
>
> I want to show you my Muuri StoryView plugin version 0.2.0 Prerelease.
>
> It contains various Bugfixes and can overall be considered more stable
>
> New Feature:
>
>- Drop Actions: actions triggered when dropping an item from one grid 
>into another grid
>   - the actionTiddler and modifier variables are available within the 
>   action-string, containing the title of the dragged item respectively 
> the 
>   modifier keys held while dragging
>
> Missing Feature:
>
>- A configuration panel. I'm currently overhauling it.
>
> You play with it at https://burningtreec.github.io/tiddlywiki-muuri
>
> On the Demo page there's a Sidebar Grid where you can drop tiddlers into. 
> Holding shift while dragging adds a tag to that Tiddler. Holding ctrl-shift 
> while dragging shifts the Tiddler to edit mode.
>
> That's just a Demo of what can be built with the Muuri StoryView.
>
> If we think about it - having a Muuri StoryView in the main river on the 
> left and having one or two Grids in the SideBar with some defined 
> dropActions makes the whole TiddlyWiki a Kanban on steroids :)
>
>
> As always, I'm open for critics and ideas, just leave me a post
>
> all the best, BTC
>

-- 
You received this message because you are subscribed to the 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/7ad1d86a-7614-4a6c-ad1d-8ea30ac6432cn%40googlegroups.com.

[tw5] Showing off: Muuri StoryView 0.2.0 Prerelease

[BurningTreeC]

Hi TiddlyWiki folks,

I want to show you my Muuri StoryView plugin version 0.2.0 Prerelease.

It contains various Bugfixes and can overall be considered more stable

New Feature:

   - Drop Actions: actions triggered when dropping an item from one grid 
   into another grid
  - the actionTiddler and modifier variables are available within the 
  action-string, containing the title of the dragged item respectively the 
  modifier keys held while dragging
   
Missing Feature:

   - A configuration panel. I'm currently overhauling it.
   
You play with it at https://burningtreec.github.io/tiddlywiki-muuri

On the Demo page there's a Sidebar Grid where you can drop tiddlers into. 
Holding shift while dragging adds a tag to that Tiddler. Holding ctrl-shift 
while dragging shifts the Tiddler to edit mode.

That's just a Demo of what can be built with the Muuri StoryView.

If we think about it - having a Muuri StoryView in the main river on the 
left and having one or two Grids in the SideBar with some defined 
dropActions makes the whole TiddlyWiki a Kanban on steroids :)


As always, I'm open for critics and ideas, just leave me a post

all the best, BTC

-- 
You received this message because you are subscribed to the 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/8454e0f9-79b9-4954-a38d-c33fc8fb4008n%40googlegroups.com.

[tw5] Re: WYSIWYG editor for TW5

[bluespire]

Hmm. Well it has to be some kind of user error. I switched my local path of 
the cloudflare one, and it loaded immediately. I'll play around with it.

On Sunday, December 20, 2020 at 1:58:48 AM UTC-6 bluespire wrote:

> I'm not sure what I'm doing wrong. I tried a couple of different browsers, 
> and it's still not loading. It has the text that it's trying to load, but 
> never does.
>
> On Friday, December 18, 2020 at 5:19:10 PM UTC-6 BJ wrote:
>
>> Hi Bluespire
>> The installation under node is the same as for a standalone tiddlywiki
>>
>> On Friday, December 18, 2020 at 9:04:54 PM UTC+1 bluespire wrote:
>>
>>> I'm running node. I'm having trouble getting Visual Editor to work. I 
>>> took all the tiddlers that were BJ's TW and exported them to .tids and 
>>> placed them in a plugins folder, and then modified the tiddler for the 
>>> path. It still doesn't load. Any ideas?
>>>
>>> On Saturday, June 27, 2020 at 2:19:50 PM UTC-5 Mark S. wrote:
>>>
 I used Birthe's instructions (the post prior to yours) and it worked 
 immediately.

 What is your setting for $:/plugin/bj/visualeditor/includelib ?
 Are you running single file or node?

 Don't forget that for plugins to work, your TW file has to be saved and 
 reloaded.

 Good luck!

 On Saturday, June 27, 2020 at 12:06:52 PM UTC-7, OGNSYA wrote:
>
> Is TW5 able to offer a wysiwyg editor at the moment?
>
> In this 2019  
> gh thread Jermolene suggests it could be doable, due to recent 
> developments.
>
> Other than that, the only solution I've found for this is CKEditor (in 
> this 2017 thread - which is why I'm reviving it). However, I followed the 
> steps above and it didn't work in my TW.  I get the message "loading 
> ckeditor" where the editor should be. I tried both - downloading the 
> latest 
> version in the ckeditor website, and using the online js library. Same 
> thing. 
>
> Anyone has/had any luck making wysiwyg work (with CK or anything else)?
>
> I understand that this is not a priority for many of TW hardcore 
> users, but for many of us it's very important.
> I'm not much of a coder, but could try making this work if I got some 
> pointers from more expert users...
>
>
> On Friday, May 5, 2017 at 3:01:47 AM UTC+1 strikke...@gmail.com wrote:
>
>> Goto http://bjtools.tiddlyspot.com 
>> . 
>> Drag the plugin to your own tiddlywiki. Save and refresh your TW. From 
>> the 
>> plugin tiddlers open $:/plugin/bj/visualeditor/includelib an insert the 
>> library:
>> https://cdnjs.cloudflare.com/ajax/libs/ckeditor/4.6.2/ckeditor.js
>>
>> When you want to use it you have to change the tiddlers type to 
>> text/x-htmlp. When the plugin is installed, you will find it in the 
>> selectbox.
>>
>>
>> Birthe
>>
>

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