subject:"\[tw5\] Re\: Preview\: keyboard driven draggable bullets"

By 'what a goon' I was of course referring to snowgoon...

On Tuesday, June 23, 2020 at 4:53:09 PM UTC-5 David Gifford wrote:

> What a goon. :-)
>
> But seriously, thanks for the good news, and I will await further news!
>
>
>
>
>
> On Tue, Jun 23, 2020 at 2:31 PM Saq Imtiaz  wrote:
>
>> @Dave snowgoon replied and it looks like he wants to merge it. But he 
>> also mentioned that he is a bit busy and also doesn't have too much 
>> experience with pull requests and hasn't worked with his TW development for 
>> a while... so it may take some time.
>>
>> https://github.com/snowgoon88/TW5-extendedit/pull/17
>>
>>  I will try to remember to drop a note here once it gets merged.
>>
>> On Tuesday, June 23, 2020 at 9:12:19 PM UTC+2, David Gifford wrote:
>>>
>>> Hi Saq
>>>
>>> In mid-June you mentioned a pull request to make the comptext plugin 
>>> compatible. Will you let us know here if that happens? Autocomplete would 
>>> be a big help in making this a lightning fast tool. I have avoided this 
>>> thread / using Streams for a long while, to focus on other things during a 
>>> very busy season. But I can see this being really handy for contacts, on 
>>> hand info, to do lists, etc. 
>>>
>>> On Wednesday, May 20, 2020 at 4:44:31 PM UTC-5 saq.i...@gmail.com wrote:
>>>
 Edited (09/06/2020)
 This is in active development. Back up your wiki regularly.

 Demo:
 https://saqimtiaz.github.io/sq-tw/streams.html

 *Code:*
 https://github.com/saqimtiaz/streams

 ---

 When I'm under the weather I tend to prototype. Spent some time 
 reworking code from my eternally in progress task manager in an attempt to 
 make it more general purpose, as a bullet list note taking tool that may 
 be 
 of utility to others. 


 https://drive.google.com/file/d/1SB06s13tj8P3cC2UewnfzXf08UQ7jwYK/view?usp=drivesdk


 https://drive.google.com/file/d/1SLESm6OIfHsScwYePGOs5ce3o3wpQ0CO/view?usp=drivesdk

 - everything except the dragging is keyboard driven
 - each bullet is a separate tiddler. Lots of different pros and cons to 
 this approach, but was ideal for a task manager.
 - this is all in wikitext, no extra JS.

  Will post the file in the near future, a bit more clean up needed. 
 Don't expect a final product, but rather a pattern to follow that would 
 hopefully help anyone wanting to implement similar workflow. 

 Cheers,
 Saq



 -- 
>> You received this message because you are subscribed to a topic in the 
>> Google Groups "TiddlyWiki" group.
>> To unsubscribe from this topic, visit 
>> https://groups.google.com/d/topic/tiddlywiki/KeVDndcnY0g/unsubscribe.
>> To unsubscribe from this group and all its topics, send an email to 
>> tiddlywiki+...@googlegroups.com.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/tiddlywiki/7662f4a8-4570-4c18-a3af-f917a1efdf69o%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/479dd14f-42db-4550-a1e7-767d72973c5dn%40googlegroups.com.

[tw5] Re: Preview: keyboard driven draggable bullets

Here is an idea for a feature, as if you didn't have enough to think about!

On the menu, you could have an option to copy the title of the tiddler to 
the clipboard. That way you can paste it elsewhere and transcludify it.

You have an option for clicking shift and dragging it, to copy it, but that 
wasn't working for me, and also it requires having both tiddlers open 
beforehand. By copying it to clipboard, you can add it to as many tiddlers 
as you want, by opening them and pasting. Just a thought.

On Wednesday, May 20, 2020 at 4:44:31 PM UTC-5 saq.i...@gmail.com wrote:

> Edited (09/06/2020)
> This is in active development. Back up your wiki regularly.
>
> Demo:
> https://saqimtiaz.github.io/sq-tw/streams.html
>
> *Code:*
> https://github.com/saqimtiaz/streams
>
> ---
>
> When I'm under the weather I tend to prototype. Spent some time reworking 
> code from my eternally in progress task manager in an attempt to make it 
> more general purpose, as a bullet list note taking tool that may be of 
> utility to others. 
>
>
> https://drive.google.com/file/d/1SB06s13tj8P3cC2UewnfzXf08UQ7jwYK/view?usp=drivesdk
>
>
> https://drive.google.com/file/d/1SLESm6OIfHsScwYePGOs5ce3o3wpQ0CO/view?usp=drivesdk
>
> - everything except the dragging is keyboard driven
> - each bullet is a separate tiddler. Lots of different pros and cons to 
> this approach, but was ideal for a task manager.
> - this is all in wikitext, no extra JS.
>
>  Will post the file in the near future, a bit more clean up needed. Don't 
> expect a final product, but rather a pattern to follow that would hopefully 
> help anyone wanting to implement similar workflow. 
>
> Cheers,
> Saq
>
>
>
>

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

Re: [tw5] Re: Preview: keyboard driven draggable bullets

What a goon. :-)

But seriously, thanks for the good news, and I will await further news!





On Tue, Jun 23, 2020 at 2:31 PM Saq Imtiaz  wrote:

> @Dave snowgoon replied and it looks like he wants to merge it. But he also
> mentioned that he is a bit busy and also doesn't have too much experience
> with pull requests and hasn't worked with his TW development for a while...
> so it may take some time.
>
> https://github.com/snowgoon88/TW5-extendedit/pull/17
>
>  I will try to remember to drop a note here once it gets merged.
>
> On Tuesday, June 23, 2020 at 9:12:19 PM UTC+2, David Gifford wrote:
>>
>> Hi Saq
>>
>> In mid-June you mentioned a pull request to make the comptext plugin
>> compatible. Will you let us know here if that happens? Autocomplete would
>> be a big help in making this a lightning fast tool. I have avoided this
>> thread / using Streams for a long while, to focus on other things during a
>> very busy season. But I can see this being really handy for contacts, on
>> hand info, to do lists, etc.
>>
>> On Wednesday, May 20, 2020 at 4:44:31 PM UTC-5 saq.i...@gmail.com wrote:
>>
>>> Edited (09/06/2020)
>>> This is in active development. Back up your wiki regularly.
>>>
>>> Demo:
>>> https://saqimtiaz.github.io/sq-tw/streams.html
>>>
>>> *Code:*
>>> https://github.com/saqimtiaz/streams
>>>
>>> ---
>>>
>>> When I'm under the weather I tend to prototype. Spent some time
>>> reworking code from my eternally in progress task manager in an attempt to
>>> make it more general purpose, as a bullet list note taking tool that may be
>>> of utility to others.
>>>
>>>
>>> https://drive.google.com/file/d/1SB06s13tj8P3cC2UewnfzXf08UQ7jwYK/view?usp=drivesdk
>>>
>>>
>>> https://drive.google.com/file/d/1SLESm6OIfHsScwYePGOs5ce3o3wpQ0CO/view?usp=drivesdk
>>>
>>> - everything except the dragging is keyboard driven
>>> - each bullet is a separate tiddler. Lots of different pros and cons to
>>> this approach, but was ideal for a task manager.
>>> - this is all in wikitext, no extra JS.
>>>
>>>  Will post the file in the near future, a bit more clean up needed.
>>> Don't expect a final product, but rather a pattern to follow that would
>>> hopefully help anyone wanting to implement similar workflow.
>>>
>>> Cheers,
>>> Saq
>>>
>>>
>>>
>>> --
> You received this message because you are subscribed to a topic in the
> Google Groups "TiddlyWiki" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/tiddlywiki/KeVDndcnY0g/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/7662f4a8-4570-4c18-a3af-f917a1efdf69o%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/CANE%3DBFJ5EWYT7okxARBLn9BkHA8q3qLWSm7ASMcyWxK5MnF_EQ%40mail.gmail.com.

[tw5] Re: Preview: keyboard driven draggable bullets


>
>
>
> Also I've tried to install your modified edit-comptext (the one you linked 
> on snowgoon's GitHub for demo purposes) : once I setup the 
> $:/config/EditorTypeMappings/text/vnd.tiddlywiki to `text` instead of 
> `comptext`, I still have auto-completion in editor view, but not in Streams 
> (i mean that when I'm editing text in a Streams tree, I don't have 
> auto-completion). I don't know if it's the normal behavior with the current 
> implementation (i figure it's not), just wanted to let you know.
>

That integration is currently disabled because:
a) no one should be using a modified and patched version of a plugin that 
will likely clash with future updates.
b) after I made that pull request I realized the key handling for the two 
plugins will likely clash and I have not had the time to investigate yet. 

-- 
You received this message because you are subscribed to the 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/d2b221e1-9dab-4eea-8a76-1d4a2418d549o%40googlegroups.com.

[tw5] Re: Preview: keyboard driven draggable bullets

2020-06-23 Thread _Phi / hpx1

yes I was referring to drag-n-dropping non-streams tiddlers in a tree, and 
I can confirm the broken behavior with the latest version of stream.

Also I've tried to install your modified edit-comptext (the one you linked 
on snowgoon's GitHub for demo purposes) : once I setup the 
$:/config/EditorTypeMappings/text/vnd.tiddlywiki to `text` instead of 
`comptext`, I still have auto-completion in editor view, but not in Streams 
(i mean that when I'm editing text in a Streams tree, I don't have 
auto-completion). I don't know if it's the normal behavior with the current 
implementation (i figure it's not), just wanted to let you know.

thanks again for the great plugin, cheers.

On Tuesday, June 23, 2020 at 8:33:34 PM UTC+2, Saq Imtiaz wrote:
>
> Can you confirm that just dragging and dropping in isn't working? 
>
> That feature was there since the start. If it isn't working now let me 
> know, there must have been a regression when I did the big refactoring a 
> while back. 
>
> On Tuesday, June 23, 2020 at 7:50:30 PM UTC+2, _Phi / hpx1 wrote:
>>
>> is there a way to insert an existing tiddler (one that is not part of any 
>> stream) into an existing stream by drag-n-dropping it in the tree ? I 
>> currently edit the child list/parent list of the tiddlers manually, but I 
>> guess there is a better way.
>>
>

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

[tw5] Re: Preview: keyboard driven draggable bullets

@Dave snowgoon replied and it looks like he wants to merge it. But he also 
mentioned that he is a bit busy and also doesn't have too much experience 
with pull requests and hasn't worked with his TW development for a while... 
so it may take some time.

https://github.com/snowgoon88/TW5-extendedit/pull/17

 I will try to remember to drop a note here once it gets merged.

On Tuesday, June 23, 2020 at 9:12:19 PM UTC+2, David Gifford wrote:
>
> Hi Saq
>
> In mid-June you mentioned a pull request to make the comptext plugin 
> compatible. Will you let us know here if that happens? Autocomplete would 
> be a big help in making this a lightning fast tool. I have avoided this 
> thread / using Streams for a long while, to focus on other things during a 
> very busy season. But I can see this being really handy for contacts, on 
> hand info, to do lists, etc. 
>
> On Wednesday, May 20, 2020 at 4:44:31 PM UTC-5 saq.i...@gmail.com wrote:
>
>> Edited (09/06/2020)
>> This is in active development. Back up your wiki regularly.
>>
>> Demo:
>> https://saqimtiaz.github.io/sq-tw/streams.html
>>
>> *Code:*
>> https://github.com/saqimtiaz/streams
>>
>> ---
>>
>> When I'm under the weather I tend to prototype. Spent some time reworking 
>> code from my eternally in progress task manager in an attempt to make it 
>> more general purpose, as a bullet list note taking tool that may be of 
>> utility to others. 
>>
>>
>> https://drive.google.com/file/d/1SB06s13tj8P3cC2UewnfzXf08UQ7jwYK/view?usp=drivesdk
>>
>>
>> https://drive.google.com/file/d/1SLESm6OIfHsScwYePGOs5ce3o3wpQ0CO/view?usp=drivesdk
>>
>> - everything except the dragging is keyboard driven
>> - each bullet is a separate tiddler. Lots of different pros and cons to 
>> this approach, but was ideal for a task manager.
>> - this is all in wikitext, no extra JS.
>>
>>  Will post the file in the near future, a bit more clean up needed. Don't 
>> expect a final product, but rather a pattern to follow that would hopefully 
>> help anyone wanting to implement similar workflow. 
>>
>> Cheers,
>> Saq
>>
>>
>>
>>

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

[tw5] Re: Preview: keyboard driven draggable bullets

Yes dragging in non-Stream tiddlers was supported from the start. So if it 
doesn't work now it regressed in the refactoring. 

Issues like this is why I am delaying further work on this until I have the 
time to do it properly.

On Tuesday, June 23, 2020 at 9:00:14 PM UTC+2, OGNSYA wrote:
>
> I think he meant dragging in "non-Stream" tiddlers.
>
> This is also something I miss in Stream. Alongside the option to have a 
> node appear in multiple different places, not just as a transclusion.
>
> On Tuesday, June 23, 2020 at 7:33:34 PM UTC+1, Saq Imtiaz wrote:
>>
>> Can you confirm that just dragging and dropping in isn't working? 
>>
>> That feature was there since the start. If it isn't working now let me 
>> know, there must have been a regression when I did the big refactoring a 
>> while back. 
>>
>> On Tuesday, June 23, 2020 at 7:50:30 PM UTC+2, _Phi / hpx1 wrote:
>>>
>>> is there a way to insert an existing tiddler (one that is not part of 
>>> any stream) into an existing stream by drag-n-dropping it in the tree ? I 
>>> currently edit the child list/parent list of the tiddlers manually, but I 
>>> guess there is a better way.
>>>
>>

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

[tw5] Re: Preview: keyboard driven draggable bullets

Hi Saq

In mid-June you mentioned a pull request to make the comptext plugin 
compatible. Will you let us know here if that happens? Autocomplete would 
be a big help in making this a lightning fast tool. I have avoided this 
thread / using Streams for a long while, to focus on other things during a 
very busy season. But I can see this being really handy for contacts, on 
hand info, to do lists, etc. 

On Wednesday, May 20, 2020 at 4:44:31 PM UTC-5 saq.i...@gmail.com wrote:

> Edited (09/06/2020)
> This is in active development. Back up your wiki regularly.
>
> Demo:
> https://saqimtiaz.github.io/sq-tw/streams.html
>
> *Code:*
> https://github.com/saqimtiaz/streams
>
> ---
>
> When I'm under the weather I tend to prototype. Spent some time reworking 
> code from my eternally in progress task manager in an attempt to make it 
> more general purpose, as a bullet list note taking tool that may be of 
> utility to others. 
>
>
> https://drive.google.com/file/d/1SB06s13tj8P3cC2UewnfzXf08UQ7jwYK/view?usp=drivesdk
>
>
> https://drive.google.com/file/d/1SLESm6OIfHsScwYePGOs5ce3o3wpQ0CO/view?usp=drivesdk
>
> - everything except the dragging is keyboard driven
> - each bullet is a separate tiddler. Lots of different pros and cons to 
> this approach, but was ideal for a task manager.
> - this is all in wikitext, no extra JS.
>
>  Will post the file in the near future, a bit more clean up needed. Don't 
> expect a final product, but rather a pattern to follow that would hopefully 
> help anyone wanting to implement similar workflow. 
>
> Cheers,
> Saq
>
>
>
>

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

[tw5] Re: Preview: keyboard driven draggable bullets

2020-06-23 Thread OGNSYA

I think he meant dragging in "non-Stream" tiddlers.

This is also something I miss in Stream. Alongside the option to have a 
node appear in multiple different places, not just as a transclusion.

On Tuesday, June 23, 2020 at 7:33:34 PM UTC+1, Saq Imtiaz wrote:
>
> Can you confirm that just dragging and dropping in isn't working? 
>
> That feature was there since the start. If it isn't working now let me 
> know, there must have been a regression when I did the big refactoring a 
> while back. 
>
> On Tuesday, June 23, 2020 at 7:50:30 PM UTC+2, _Phi / hpx1 wrote:
>>
>> is there a way to insert an existing tiddler (one that is not part of any 
>> stream) into an existing stream by drag-n-dropping it in the tree ? I 
>> currently edit the child list/parent list of the tiddlers manually, but I 
>> guess there is a better way.
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/2f8643d0-333c-42fd-93f0-8ae2c454172eo%40googlegroups.com.

[tw5] Re: Preview: keyboard driven draggable bullets

Can you confirm that just dragging and dropping in isn't working? 

That feature was there since the start. If it isn't working now let me 
know, there must have been a regression when I did the big refactoring a 
while back. 

On Tuesday, June 23, 2020 at 7:50:30 PM UTC+2, _Phi / hpx1 wrote:
>
> is there a way to insert an existing tiddler (one that is not part of any 
> stream) into an existing stream by drag-n-dropping it in the tree ? I 
> currently edit the child list/parent list of the tiddlers manually, but I 
> guess there is a better way.
>

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

[tw5] Re: Preview: keyboard driven draggable bullets

2020-06-23 Thread _Phi / hpx1

is there a way to insert an existing tiddler (one that is not part of any 
stream) into an existing stream by drag-n-dropping it in the tree ? I 
currently edit the child list/parent list of the tiddlers manually, but I 
guess there is a better way.

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

[tw5] Re: Preview: keyboard driven draggable bullets

2020-06-23 Thread Cyrill

Sorry, dont notice your suggestion...
works perfectly and fits to my needs !! 


Am Dienstag, 23. Juni 2020 12:09:06 UTC+2 schrieb Saq Imtiaz:
>
> @Cyrill sounds like you haven't installed Relink plugin as suggested in 
> the installation notes
>
> On Tuesday, June 23, 2020 at 10:47:28 AM UTC+2, Cyrill wrote:
>>
>> Hey Saq Imtiaz,
>>
>> tx for your answer, 
>>
>> but when you rename the created tiddlers, they get lost in the wished 
>> tree/slider/structure...
>> so via the caption field, only the showed name (in the tabs of side bars) 
>> could be different than the title.
>>
>> Regards
>>
>> Am Samstag, 20. Juni 2020 08:20:02 UTC+2 schrieb Saq Imtiaz:
>>>
>>> @Cyrill: I am not sure I follow your question. The plugin has nothing to 
>>> do with the SideBar.
>>>
>>> If you are unhappy with the title of generated tiddlers, you can just 
>>> rename them.
>>>
>>> On Thursday, June 18, 2020 at 2:16:15 PM UTC+2, Cyrill wrote:

 Hey Saq Imtiaz,

 like to start working with your plugin. I tested the caption field to 
 modify the visual title in SideBar, but it seem not to be integrated now. 
 Is there hope to get is next time ?

 Kind regards

 Am Dienstag, 16. Juni 2020 17:17:51 UTC+2 schrieb Saq Imtiaz:
>
> I've pushed an update that should address that bug. I suspect we will 
> find a few more of these until I get the chance to do a comprehensive 
> code 
> review, one is really needed after the major refactoring I did to rename 
> fields.
>
> Saq
>
> On Tuesday, June 16, 2020 at 4:54:02 PM UTC+2, OGNSYA wrote:
>>
>> I just tested again in your demo 
>>  and it actually 
>> happens there too.
>> Please see image attached.
>> CTRL+down doesn't work for going from node A to A1 or from B to B1 
>> (it works for all other operations).
>> Let me know if you can't reproduce it, or if you want me to do any 
>> further tests
>>
>>
>> On Tuesday, June 16, 2020 at 2:39:06 PM UTC+1, Saq Imtiaz wrote:
>>>
>>> @OGNSYA in order to try to investigate that potential bug I will 
>>> need either:
>>>
>>>- specific steps to re-create that bug in my demo
>>>OR
>>>- a file in which I can see that bug
>>>
>>> Is that problem happening in all streams? Or only in one specific 
>>> tiddler?
>>>
>>>
>>>
>>> On Tuesday, June 16, 2020 at 12:40:42 PM UTC+2, OGNSYA wrote:

 Thanks Saq.

 *Here's a very specific bug I'm getting *, which doesn't happen in 
 your website (my setup is TiddlyDesktop, with Stroll). 
 Navigating using CTRL+Down doesn't work when the next item is a 
 child (ie. indented).
 Otherwise everything else works (including CTRL+Down when the next 
 item is a parent).

 *And a suggestion/request*: when breaking a node in two, by 
 pressing ENTER, could the caret (the text cursor) be moved to the 
 *start* of the new node (instead of to the end)? To me that would 
 be the most intuitive. It would be particularly helpful when manually 
 breaking up longer texts.

 On Sunday, June 14, 2020 at 3:52:13 PM UTC+1, Saq Imtiaz wrote:
>
> I've pushed an update that fixes the bug with drag and drop. It's 
> something that crept in when I recently refactored to change field 
> names 
> and plugin name.
>
> I've had a few things come up that will limit the time I have 
> available to work on this in the short term. So for now, I am 
> focusing on 
> bug reports only.
>
>  Will revisit other feedback once I am able to. In the meantime 
> please feel free to keep the feedback coming.
> Cheers,
>
> Saq
>
> On Sunday, June 14, 2020 at 11:43:41 AM UTC+2, OGNSYA wrote:
>>
>> @Saq, thanks for addressing all our questions!
>>
>> *Single-click edit*: Got it! I didn't realize external links 
>> couldn't be clicked. I thought they'd behave the same as [[internal 
>> links]], which could be clicked in the initial (single-click) 
>> version of 
>> your plugin. I didn't know there was this distinction. (Maybe offer 
>> users a 
>> single-click option, which requires CTRL-click for links?)
>>
>> *Autocomplete*: I also ran into the autocomplete issue with 
>> edit-comptext. Thank you for the pull request 
>>
>> *Direct editing*: In my previous email I suggest: *"Have you 
>> considered structuring it so that text can be directly edited at any 
>> level 
>> (ie., without needing to go into Edit mode)? Currently you can only 
>> edit 
>> child notes directly, but not the content of

[tw5] Re: Preview: keyboard driven draggable bullets

@Cyrill sounds like you haven't installed Relink plugin as suggested in the 
installation notes

On Tuesday, June 23, 2020 at 10:47:28 AM UTC+2, Cyrill wrote:
>
> Hey Saq Imtiaz,
>
> tx for your answer, 
>
> but when you rename the created tiddlers, they get lost in the wished 
> tree/slider/structure...
> so via the caption field, only the showed name (in the tabs of side bars) 
> could be different than the title.
>
> Regards
>
> Am Samstag, 20. Juni 2020 08:20:02 UTC+2 schrieb Saq Imtiaz:
>>
>> @Cyrill: I am not sure I follow your question. The plugin has nothing to 
>> do with the SideBar.
>>
>> If you are unhappy with the title of generated tiddlers, you can just 
>> rename them.
>>
>> On Thursday, June 18, 2020 at 2:16:15 PM UTC+2, Cyrill wrote:
>>>
>>> Hey Saq Imtiaz,
>>>
>>> like to start working with your plugin. I tested the caption field to 
>>> modify the visual title in SideBar, but it seem not to be integrated now. 
>>> Is there hope to get is next time ?
>>>
>>> Kind regards
>>>
>>> Am Dienstag, 16. Juni 2020 17:17:51 UTC+2 schrieb Saq Imtiaz:

 I've pushed an update that should address that bug. I suspect we will 
 find a few more of these until I get the chance to do a comprehensive code 
 review, one is really needed after the major refactoring I did to rename 
 fields.

 Saq

 On Tuesday, June 16, 2020 at 4:54:02 PM UTC+2, OGNSYA wrote:
>
> I just tested again in your demo 
>  and it actually 
> happens there too.
> Please see image attached.
> CTRL+down doesn't work for going from node A to A1 or from B to B1 (it 
> works for all other operations).
> Let me know if you can't reproduce it, or if you want me to do any 
> further tests
>
>
> On Tuesday, June 16, 2020 at 2:39:06 PM UTC+1, Saq Imtiaz wrote:
>>
>> @OGNSYA in order to try to investigate that potential bug I will need 
>> either:
>>
>>- specific steps to re-create that bug in my demo
>>OR
>>- a file in which I can see that bug
>>
>> Is that problem happening in all streams? Or only in one specific 
>> tiddler?
>>
>>
>>
>> On Tuesday, June 16, 2020 at 12:40:42 PM UTC+2, OGNSYA wrote:
>>>
>>> Thanks Saq.
>>>
>>> *Here's a very specific bug I'm getting *, which doesn't happen in 
>>> your website (my setup is TiddlyDesktop, with Stroll). 
>>> Navigating using CTRL+Down doesn't work when the next item is a 
>>> child (ie. indented).
>>> Otherwise everything else works (including CTRL+Down when the next 
>>> item is a parent).
>>>
>>> *And a suggestion/request*: when breaking a node in two, by 
>>> pressing ENTER, could the caret (the text cursor) be moved to the 
>>> *start* of the new node (instead of to the end)? To me that would 
>>> be the most intuitive. It would be particularly helpful when manually 
>>> breaking up longer texts.
>>>
>>> On Sunday, June 14, 2020 at 3:52:13 PM UTC+1, Saq Imtiaz wrote:

 I've pushed an update that fixes the bug with drag and drop. It's 
 something that crept in when I recently refactored to change field 
 names 
 and plugin name.

 I've had a few things come up that will limit the time I have 
 available to work on this in the short term. So for now, I am focusing 
 on 
 bug reports only.

  Will revisit other feedback once I am able to. In the meantime 
 please feel free to keep the feedback coming.
 Cheers,

 Saq

 On Sunday, June 14, 2020 at 11:43:41 AM UTC+2, OGNSYA wrote:
>
> @Saq, thanks for addressing all our questions!
>
> *Single-click edit*: Got it! I didn't realize external links 
> couldn't be clicked. I thought they'd behave the same as [[internal 
> links]], which could be clicked in the initial (single-click) version 
> of 
> your plugin. I didn't know there was this distinction. (Maybe offer 
> users a 
> single-click option, which requires CTRL-click for links?)
>
> *Autocomplete*: I also ran into the autocomplete issue with 
> edit-comptext. Thank you for the pull request 
>
> *Direct editing*: In my previous email I suggest: *"Have you 
> considered structuring it so that text can be directly edited at any 
> level 
> (ie., without needing to go into Edit mode)? Currently you can only 
> edit 
> child notes directly, but not the content of the node itself. This 
> would 
> make the editing experience consistent in all levels of hierarchy"*
> To be clear, I don't refer to WYSIWYG here. This would be just to 
> keep the experience consistent for the end user.
>
>

[tw5] Re: Preview: keyboard driven draggable bullets

2020-06-23 Thread Cyrill

Hey Saq Imtiaz,

tx for your answer, 

but when you rename the created tiddlers, they get lost in the wished 
tree/slider/structure...
so via the caption field, only the showed name (in the tabs of side bars) 
could be different than the title.

Regards

Am Samstag, 20. Juni 2020 08:20:02 UTC+2 schrieb Saq Imtiaz:
>
> @Cyrill: I am not sure I follow your question. The plugin has nothing to 
> do with the SideBar.
>
> If you are unhappy with the title of generated tiddlers, you can just 
> rename them.
>
> On Thursday, June 18, 2020 at 2:16:15 PM UTC+2, Cyrill wrote:
>>
>> Hey Saq Imtiaz,
>>
>> like to start working with your plugin. I tested the caption field to 
>> modify the visual title in SideBar, but it seem not to be integrated now. 
>> Is there hope to get is next time ?
>>
>> Kind regards
>>
>> Am Dienstag, 16. Juni 2020 17:17:51 UTC+2 schrieb Saq Imtiaz:
>>>
>>> I've pushed an update that should address that bug. I suspect we will 
>>> find a few more of these until I get the chance to do a comprehensive code 
>>> review, one is really needed after the major refactoring I did to rename 
>>> fields.
>>>
>>> Saq
>>>
>>> On Tuesday, June 16, 2020 at 4:54:02 PM UTC+2, OGNSYA wrote:

 I just tested again in your demo 
  and it actually 
 happens there too.
 Please see image attached.
 CTRL+down doesn't work for going from node A to A1 or from B to B1 (it 
 works for all other operations).
 Let me know if you can't reproduce it, or if you want me to do any 
 further tests

 On Tuesday, June 16, 2020 at 2:39:06 PM UTC+1, Saq Imtiaz wrote:
>
> @OGNSYA in order to try to investigate that potential bug I will need 
> either:
>
>- specific steps to re-create that bug in my demo
>OR
>- a file in which I can see that bug
>
> Is that problem happening in all streams? Or only in one specific 
> tiddler?
>
>
>
> On Tuesday, June 16, 2020 at 12:40:42 PM UTC+2, OGNSYA wrote:
>>
>> Thanks Saq.
>>
>> *Here's a very specific bug I'm getting *, which doesn't happen in 
>> your website (my setup is TiddlyDesktop, with Stroll). 
>> Navigating using CTRL+Down doesn't work when the next item is a child 
>> (ie. indented).
>> Otherwise everything else works (including CTRL+Down when the next 
>> item is a parent).
>>
>> *And a suggestion/request*: when breaking a node in two, by pressing 
>> ENTER, could the caret (the text cursor) be moved to the *start* of 
>> the new node (instead of to the end)? To me that would be the most 
>> intuitive. It would be particularly helpful when manually breaking up 
>> longer texts.
>>
>> On Sunday, June 14, 2020 at 3:52:13 PM UTC+1, Saq Imtiaz wrote:
>>>
>>> I've pushed an update that fixes the bug with drag and drop. It's 
>>> something that crept in when I recently refactored to change field 
>>> names 
>>> and plugin name.
>>>
>>> I've had a few things come up that will limit the time I have 
>>> available to work on this in the short term. So for now, I am focusing 
>>> on 
>>> bug reports only.
>>>
>>>  Will revisit other feedback once I am able to. In the meantime 
>>> please feel free to keep the feedback coming.
>>> Cheers,
>>>
>>> Saq
>>>
>>> On Sunday, June 14, 2020 at 11:43:41 AM UTC+2, OGNSYA wrote:

 @Saq, thanks for addressing all our questions!

 *Single-click edit*: Got it! I didn't realize external links 
 couldn't be clicked. I thought they'd behave the same as [[internal 
 links]], which could be clicked in the initial (single-click) version 
 of 
 your plugin. I didn't know there was this distinction. (Maybe offer 
 users a 
 single-click option, which requires CTRL-click for links?)

 *Autocomplete*: I also ran into the autocomplete issue with 
 edit-comptext. Thank you for the pull request 

 *Direct editing*: In my previous email I suggest: *"Have you 
 considered structuring it so that text can be directly edited at any 
 level 
 (ie., without needing to go into Edit mode)? Currently you can only 
 edit 
 child notes directly, but not the content of the node itself. This 
 would 
 make the editing experience consistent in all levels of hierarchy"*
 To be clear, I don't refer to WYSIWYG here. This would be just to 
 keep the experience consistent for the end user.

 *Possible bug?*: I didn't see any reference to this anywhere, so I 
 thought I'd mention. I'm not able to CTRL or SHIFT drag a bullet (ie., 
 Copy 
 or Transclude) to another tiddler (nothing happens). I can only drag 
 it 
 directly - ie., Move.

[tw5] Re: Preview: keyboard driven draggable bullets

2020-06-20 Thread _Phi / hpx1

Coming from Dynalist, I was considering Roam, then RemNote, eventually 
installed Obsidian... but now I'm moving everything back to TW5 + Streams ! 
Thanks for the great plugin !


-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/f42cfbae-a387-44b2-972b-1d55a19ba973o%40googlegroups.com.

[tw5] Re: Preview: keyboard driven draggable bullets

2020-06-20 Thread Glenn McLelland

Thanks Saq,

My thoughts are just rough suggestions.  Feel free to discard or include 
anything that is helpful. You won't hurt my feelings.

About the searching... maybe an alternative idea is to just add a checkbox 
under the search input or above the search results that says "Show stream items 
in search".  If the box is not checked the stream items would be hidden.

Thanks again for sharing your work!

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/a1e6c0e2-55f9-406a-9440-378a4bfca09co%40googlegroups.com.

[tw5] Re: Preview: keyboard driven draggable bullets

2020-06-20 Thread Ankit Mittal

"Regarding a button to create new stream tiddlers, that was the original 
workflow. It proved unsatisfactory because:
- either a tiddler should open in edit mode, which means the user needs to give 
it a name and save it before he can start adding notes via the streams 
interface, OR
- the tiddler opens in viewing mode with an arbitrary title. The user can start 
adding notes via streams right away, but will need to edit the tiddler the 
usual way and rename it."

For above conundrum, I have a thought although I dont know how easy or 
difficult it is to implement. 

What if the click of button opens a modal prompting the user to provide the 
name of the tiddler. This name is then captured for creation of the new tiddler.

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/494932a2-59cf-4152-9fda-717e64527920o%40googlegroups.com.

[tw5] Re: Preview: keyboard driven draggable bullets

2020-06-20 Thread Saq Imtiaz

Glenn: I am taking a short break from further work on this plugin while I 
attend to a few other things. However all feedback is being noted and will 
be addressed.

Regarding both search and the process of creating a stream tiddler, you 
have identified two of the key areas in which I was hoping for feedback and 
ideas when I first posted this demo. So there are no good answers here yet, 
especially with search, so ideas are welcome. 

Bimlas has some thoughts on how to use his Kin filter for searches. Once I 
resume work on this I may ask him to take a crack at it if he has the time.

Regarding a button to create new stream tiddlers, that was the original 
workflow. It proved unsatisfactory because:
- either a tiddler should open in edit mode, which means the user needs to 
give it a name and save it before he can start adding notes via the streams 
interface, OR
- the tiddler opens in viewing mode with an arbitrary title. The user can 
start adding notes via streams right away, but will need to edit the 
tiddler the usual way and rename it.

I realize the current implementation isn't ideal either. 

So once again, ideas welcome. Particularly if they are achievable using 
core TW widgets.
It is my intention for this plugin to serve as a reference plugin for this 
kind of workflow that non-developers can also tweak and adapt, so I am 
trying to avoid writing custom JavaScript, even though that would make 
development easier for me personally.

Cheers,
Saq

On Tuesday, June 16, 2020 at 7:07:04 PM UTC+2, Glenn McLelland wrote:
>
> Love this new plugin, great job Saq!
>
> Few suggestions/questions:
>
> 1. Would it be possible to hit the Escape key to cancel the focus of 
> stream item?  You said earlier that you couldn't make it where you could 
> click away to remove the focus, maybe hitting the Escape key would be 
> alternate solution?
>
> 2. Is it possible to hide the stream items from searches?  In your example 
> site, if I search for "Roadmap", I will see lots of search results.  I'm 
> not sure if this is possible since they are separate tiddlers?  You could 
> prefix them with $:/ to hide them, but I'm not sure how you would search 
> the content of each stream item?
>
> 3. Maybe you could create a new hierarchical tiddler button similar to how 
> the Markdown plugin does?  Some people may only want to use the Streams 
> feature on certain types of tiddlers like a "Streams" tiddler or 
> "Hierarchical tiddler?"
>
> [image: new-button.jpg]
>
>
> A small icon like this may work:
>
> [image: hierarchy icon at DuckDuckGo 2020-06-16 12-03-46.jpg]
>
> or
>
> [image: fontawesome.jpg]
>
>
>
>
> Could you make the bullet hit target bigger when you hover over a bullet?  
> Similar to workflowy.com?  When you hover a bullet, it shows a larger 
> circle around the bullet making it easier to click.
>
> [image: workflowy.jpg]
> Kind regards,
> Glenn
>

-- 
You received this message because you are subscribed to the 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/66814120-4929-4aca-aab5-2637c30cd854o%40googlegroups.com.

[tw5] Re: Preview: keyboard driven draggable bullets

2020-06-20 Thread Saq Imtiaz

@Cyrill: I am not sure I follow your question. The plugin has nothing to do 
with the SideBar.

If you are unhappy with the title of generated tiddlers, you can just 
rename them.

On Thursday, June 18, 2020 at 2:16:15 PM UTC+2, Cyrill wrote:
>
> Hey Saq Imtiaz,
>
> like to start working with your plugin. I tested the caption field to 
> modify the visual title in SideBar, but it seem not to be integrated now. 
> Is there hope to get is next time ?
>
> Kind regards
>
> Am Dienstag, 16. Juni 2020 17:17:51 UTC+2 schrieb Saq Imtiaz:
>>
>> I've pushed an update that should address that bug. I suspect we will 
>> find a few more of these until I get the chance to do a comprehensive code 
>> review, one is really needed after the major refactoring I did to rename 
>> fields.
>>
>> Saq
>>
>> On Tuesday, June 16, 2020 at 4:54:02 PM UTC+2, OGNSYA wrote:
>>>
>>> I just tested again in your demo 
>>>  and it actually 
>>> happens there too.
>>> Please see image attached.
>>> CTRL+down doesn't work for going from node A to A1 or from B to B1 (it 
>>> works for all other operations).
>>> Let me know if you can't reproduce it, or if you want me to do any 
>>> further tests
>>>
>>>
>>> On Tuesday, June 16, 2020 at 2:39:06 PM UTC+1, Saq Imtiaz wrote:

 @OGNSYA in order to try to investigate that potential bug I will need 
 either:

- specific steps to re-create that bug in my demo
OR
- a file in which I can see that bug

 Is that problem happening in all streams? Or only in one specific 
 tiddler?



 On Tuesday, June 16, 2020 at 12:40:42 PM UTC+2, OGNSYA wrote:
>
> Thanks Saq.
>
> *Here's a very specific bug I'm getting *, which doesn't happen in 
> your website (my setup is TiddlyDesktop, with Stroll). 
> Navigating using CTRL+Down doesn't work when the next item is a child 
> (ie. indented).
> Otherwise everything else works (including CTRL+Down when the next 
> item is a parent).
>
> *And a suggestion/request*: when breaking a node in two, by pressing 
> ENTER, could the caret (the text cursor) be moved to the *start* of 
> the new node (instead of to the end)? To me that would be the most 
> intuitive. It would be particularly helpful when manually breaking up 
> longer texts.
>
> On Sunday, June 14, 2020 at 3:52:13 PM UTC+1, Saq Imtiaz wrote:
>>
>> I've pushed an update that fixes the bug with drag and drop. It's 
>> something that crept in when I recently refactored to change field names 
>> and plugin name.
>>
>> I've had a few things come up that will limit the time I have 
>> available to work on this in the short term. So for now, I am focusing 
>> on 
>> bug reports only.
>>
>>  Will revisit other feedback once I am able to. In the meantime 
>> please feel free to keep the feedback coming.
>> Cheers,
>>
>> Saq
>>
>> On Sunday, June 14, 2020 at 11:43:41 AM UTC+2, OGNSYA wrote:
>>>
>>> @Saq, thanks for addressing all our questions!
>>>
>>> *Single-click edit*: Got it! I didn't realize external links 
>>> couldn't be clicked. I thought they'd behave the same as [[internal 
>>> links]], which could be clicked in the initial (single-click) version 
>>> of 
>>> your plugin. I didn't know there was this distinction. (Maybe offer 
>>> users a 
>>> single-click option, which requires CTRL-click for links?)
>>>
>>> *Autocomplete*: I also ran into the autocomplete issue with 
>>> edit-comptext. Thank you for the pull request 
>>>
>>> *Direct editing*: In my previous email I suggest: *"Have you 
>>> considered structuring it so that text can be directly edited at any 
>>> level 
>>> (ie., without needing to go into Edit mode)? Currently you can only 
>>> edit 
>>> child notes directly, but not the content of the node itself. This 
>>> would 
>>> make the editing experience consistent in all levels of hierarchy"*
>>> To be clear, I don't refer to WYSIWYG here. This would be just to 
>>> keep the experience consistent for the end user.
>>>
>>> *Possible bug?*: I didn't see any reference to this anywhere, so I 
>>> thought I'd mention. I'm not able to CTRL or SHIFT drag a bullet (ie., 
>>> Copy 
>>> or Transclude) to another tiddler (nothing happens). I can only drag it 
>>> directly - ie., Move. 
>>>
>>> Thanks! Streams is currently my favorite way to edit TW
>>>
>>>
>>> On Saturday, June 13, 2020 at 6:06:31 AM UTC+1, Saq Imtiaz wrote:

 Regarding title autocomplete via the edit-comptext plugin, the 
 problem is that it replaces the default editor with another. Since 
 Streams 
 also makes tweaks to the editor, it makes it difficult to combine the 
 two.

 I've re-written

[tw5] Re: Preview: keyboard driven draggable bullets

2020-06-18 Thread Cyrill

Hey Saq Imtiaz,

like to start working with your plugin. I tested the caption field to 
modify the visual title in SideBar, but it seem not to be integrated now. 
Is there hope to get is next time ?

Kind regards

Am Dienstag, 16. Juni 2020 17:17:51 UTC+2 schrieb Saq Imtiaz:
>
> I've pushed an update that should address that bug. I suspect we will find 
> a few more of these until I get the chance to do a comprehensive code 
> review, one is really needed after the major refactoring I did to rename 
> fields.
>
> Saq
>
> On Tuesday, June 16, 2020 at 4:54:02 PM UTC+2, OGNSYA wrote:
>>
>> I just tested again in your demo 
>>  and it actually happens 
>> there too.
>> Please see image attached.
>> CTRL+down doesn't work for going from node A to A1 or from B to B1 (it 
>> works for all other operations).
>> Let me know if you can't reproduce it, or if you want me to do any 
>> further tests
>>
>>
>> On Tuesday, June 16, 2020 at 2:39:06 PM UTC+1, Saq Imtiaz wrote:
>>>
>>> @OGNSYA in order to try to investigate that potential bug I will need 
>>> either:
>>>
>>>- specific steps to re-create that bug in my demo
>>>OR
>>>- a file in which I can see that bug
>>>
>>> Is that problem happening in all streams? Or only in one specific 
>>> tiddler?
>>>
>>>
>>>
>>> On Tuesday, June 16, 2020 at 12:40:42 PM UTC+2, OGNSYA wrote:

 Thanks Saq.

 *Here's a very specific bug I'm getting *, which doesn't happen in 
 your website (my setup is TiddlyDesktop, with Stroll). 
 Navigating using CTRL+Down doesn't work when the next item is a child 
 (ie. indented).
 Otherwise everything else works (including CTRL+Down when the next item 
 is a parent).

 *And a suggestion/request*: when breaking a node in two, by pressing 
 ENTER, could the caret (the text cursor) be moved to the *start* of 
 the new node (instead of to the end)? To me that would be the most 
 intuitive. It would be particularly helpful when manually breaking up 
 longer texts.

 On Sunday, June 14, 2020 at 3:52:13 PM UTC+1, Saq Imtiaz wrote:
>
> I've pushed an update that fixes the bug with drag and drop. It's 
> something that crept in when I recently refactored to change field names 
> and plugin name.
>
> I've had a few things come up that will limit the time I have 
> available to work on this in the short term. So for now, I am focusing on 
> bug reports only.
>
>  Will revisit other feedback once I am able to. In the meantime please 
> feel free to keep the feedback coming.
> Cheers,
>
> Saq
>
> On Sunday, June 14, 2020 at 11:43:41 AM UTC+2, OGNSYA wrote:
>>
>> @Saq, thanks for addressing all our questions!
>>
>> *Single-click edit*: Got it! I didn't realize external links 
>> couldn't be clicked. I thought they'd behave the same as [[internal 
>> links]], which could be clicked in the initial (single-click) version of 
>> your plugin. I didn't know there was this distinction. (Maybe offer 
>> users a 
>> single-click option, which requires CTRL-click for links?)
>>
>> *Autocomplete*: I also ran into the autocomplete issue with 
>> edit-comptext. Thank you for the pull request 
>>
>> *Direct editing*: In my previous email I suggest: *"Have you 
>> considered structuring it so that text can be directly edited at any 
>> level 
>> (ie., without needing to go into Edit mode)? Currently you can only edit 
>> child notes directly, but not the content of the node itself. This would 
>> make the editing experience consistent in all levels of hierarchy"*
>> To be clear, I don't refer to WYSIWYG here. This would be just to 
>> keep the experience consistent for the end user.
>>
>> *Possible bug?*: I didn't see any reference to this anywhere, so I 
>> thought I'd mention. I'm not able to CTRL or SHIFT drag a bullet (ie., 
>> Copy 
>> or Transclude) to another tiddler (nothing happens). I can only drag it 
>> directly - ie., Move. 
>>
>> Thanks! Streams is currently my favorite way to edit TW
>>
>>
>> On Saturday, June 13, 2020 at 6:06:31 AM UTC+1, Saq Imtiaz wrote:
>>>
>>> Regarding title autocomplete via the edit-comptext plugin, the 
>>> problem is that it replaces the default editor with another. Since 
>>> Streams 
>>> also makes tweaks to the editor, it makes it difficult to combine the 
>>> two.
>>>
>>> I've re-written parts of the edit-comptext plugin to tweak the core 
>>> editor and add the same autocomplete features to it instead of creating 
>>> a 
>>> new editor. If these changes get merged by the developer, anyone with 
>>> that 
>>> plugin installed with automatically have title autocomplete in Streams.
>>> Pull request: https://github.com/snowgoon88/TW5-extendedit/pull/17
>>>

[tw5] Re: Preview: keyboard driven draggable bullets

2020-06-17 Thread Glenn McLelland

I'm pretty sure I tested the Escape key before I posted.  Looks like it 
works correctly now!

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/c97010e0-40f9-412f-9e51-15100f740ef4o%40googlegroups.com.

[tw5] Re: Preview: keyboard driven draggable bullets

2020-06-17 Thread OGNSYA

For 1: ESC should work to cancel focus on a node.

Did you try it in the demo site? 


On Tuesday, June 16, 2020 at 6:07:04 PM UTC+1, Glenn McLelland wrote:
>
> Love this new plugin, great job Saq!
>
> Few suggestions/questions:
>
> 1. Would it be possible to hit the Escape key to cancel the focus of 
> stream item?  You said earlier that you couldn't make it where you could 
> click away to remove the focus, maybe hitting the Escape key would be 
> alternate solution?
>
> 2. Is it possible to hide the stream items from searches?  In your example 
> site, if I search for "Roadmap", I will see lots of search results.  I'm 
> not sure if this is possible since they are separate tiddlers?  You could 
> prefix them with $:/ to hide them, but I'm not sure how you would search 
> the content of each stream item?
>
> 3. Maybe you could create a new hierarchical tiddler button similar to how 
> the Markdown plugin does?  Some people may only want to use the Streams 
> feature on certain types of tiddlers like a "Streams" tiddler or 
> "Hierarchical tiddler?"
>
> [image: new-button.jpg]
>
>
> A small icon like this may work:
>
> [image: hierarchy icon at DuckDuckGo 2020-06-16 12-03-46.jpg]
>
> or
>
> [image: fontawesome.jpg]
>
>
>
>
> Could you make the bullet hit target bigger when you hover over a bullet?  
> Similar to workflowy.com?  When you hover a bullet, it shows a larger 
> circle around the bullet making it easier to click.
>
> [image: workflowy.jpg]
> Kind regards,
> Glenn
>

-- 
You received this message because you are subscribed to the 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/92371909-2526-4e2b-84ca-247f4ec7af3bo%40googlegroups.com.

[tw5] Re: Preview: keyboard driven draggable bullets

2020-06-16 Thread Glenn McLelland

Love this new plugin, great job Saq!

Few suggestions/questions:

1. Would it be possible to hit the Escape key to cancel the focus of stream 
item?  You said earlier that you couldn't make it where you could click 
away to remove the focus, maybe hitting the Escape key would be alternate 
solution?

2. Is it possible to hide the stream items from searches?  In your example 
site, if I search for "Roadmap", I will see lots of search results.  I'm 
not sure if this is possible since they are separate tiddlers?  You could 
prefix them with $:/ to hide them, but I'm not sure how you would search 
the content of each stream item?

3. Maybe you could create a new hierarchical tiddler button similar to how 
the Markdown plugin does?  Some people may only want to use the Streams 
feature on certain types of tiddlers like a "Streams" tiddler or 
"Hierarchical tiddler?"

[image: new-button.jpg]


A small icon like this may work:

[image: hierarchy icon at DuckDuckGo 2020-06-16 12-03-46.jpg]

or

[image: fontawesome.jpg]




Could you make the bullet hit target bigger when you hover over a bullet?  
Similar to workflowy.com?  When you hover a bullet, it shows a larger 
circle around the bullet making it easier to click.

[image: workflowy.jpg]
Kind regards,
Glenn

On Thursday, June 11, 2020 at 10:20:44 AM UTC-5, Raghu Veer S wrote:
>
> Hi Saq, 
>
> Thanks for the response. No worries, I understand the difficulties 
> involved.  :)
>
> As for the usecase, I just thought that easy indentation would be crucial 
> to a hierarchical outlining plugin like this, at least that is something 
> that I have been finding useful with Roam and Dynalist as I used to use 
> them extensively for research purposes along with other operations like the 
> ones you have mentioned. I was looking for a more local first OSS tool, 
> which is where I thought TiddlyWiki with the plugin ecosystem shined with 
> plugins like yours. Anyway, these were more like a feature request than a 
> feedback, so don't be bothered with it. I am still enjoying the tool. :)
>
> On Thursday, June 11, 2020 at 6:52:37 PM UTC+5:30, Saq Imtiaz wrote:
>>
>> Replies to some of the feedback below:
>>
>> *Single-click to edit:* will not be offered as an option unless we can 
>> find a reliable way of doing so while still allowing users to click on 
>> external links, and copy text as a selection, without inadvertently 
>> triggering editing.
>>
>> *Modal approach to editing:* I have no idea what this means. Modals have 
>> a very specific meaning in TW. As explained earlier, this is not an attempt 
>> at at WYSIWYG editor. As is the norm in TW, there is a separation between 
>> viewing content and editing it. If someone implements a WYSIWYG editor for 
>> wikitext, you could easily use that within Streams. Implementing one within 
>> Streams is far outside the scope of this plugin. Having to specifically 
>> decide to edit a different tiddler is not only necessary, but intentional 
>> from a design point of view. 
>>
>> *Backspace, arrow up/down behavior:* with the default widgets we have 
>> available in TW, complex and conditional handling of keys is simply not 
>> possible. For instance, enabling backspace at the beginning of some text to 
>> combine that node with the previous one, would disable the backspace key 
>> for all other usage in the editor. The keystroke is trapped by the widget, 
>> there is no means to conditionally pass it through for the default 
>> behavior. 
>>
>> So implementing this kind of behavior would require a custom JavaScript 
>> plugin, and even then the behavior wont be quite as requested as once 
>> again, this isn't WYSIWYG. While I could write such a plugin, I am 
>> realistic that I would not have the time to support and maintain it. 
>> Therefore my focus is on using core widgets and community plugins, and only 
>> writing JavaScript when absolutely essential or trivial. If someone wants 
>> to take a crack at a more elaborate plugin for handling key bindings, I 
>> will be happy to provide input and guidance, and make use of it in Streams.
>>
>> *Performance: *I am probably not the best placed to comment on 
>> performance. I have a wiki with 6000 tiddlers that runs fine, but I use 
>> very little in terms of complex list filters and backlinks, tags etc. 
>> Others may be better placed to advise on this.
>>
>> *Personally I see three kinds of situations in which I would use this as 
>> is today:*
>> - for longer text that benefits from structure, order and hierarchy. 
>> Writing an essay, or project documentation. In this case each tiddler would 
>> be a paragraph or longer. So you would not end up with more tiddlers than 
>> you normally would, you just get a more convenient workflow for the writing 
>> process and dividing your writing into tiddlers as you go.
>> - for short pieces of text that are somewhat transient in nature, e.g 
>> task lists. You delete or archive them as they are completed. The Roadmap 
>> tiddler in the

[tw5] Re: Preview: keyboard driven draggable bullets

2020-06-16 Thread OGNSYA

Thanks! Yeah that was quite a minor one. Didn't bother me much. I just 
thought I'd report it since I found it.

On Tuesday, June 16, 2020 at 4:17:51 PM UTC+1, Saq Imtiaz wrote:
>
> I've pushed an update that should address that bug. I suspect we will find 
> a few more of these until I get the chance to do a comprehensive code 
> review, one is really needed after the major refactoring I did to rename 
> fields.
>
> Saq
>
> On Tuesday, June 16, 2020 at 4:54:02 PM UTC+2, OGNSYA wrote:
>>
>> I just tested again in your demo 
>>  and it actually happens 
>> there too.
>> Please see image attached.
>> CTRL+down doesn't work for going from node A to A1 or from B to B1 (it 
>> works for all other operations).
>> Let me know if you can't reproduce it, or if you want me to do any 
>> further tests
>>
>>
>> On Tuesday, June 16, 2020 at 2:39:06 PM UTC+1, Saq Imtiaz wrote:
>>>
>>> @OGNSYA in order to try to investigate that potential bug I will need 
>>> either:
>>>
>>>- specific steps to re-create that bug in my demo
>>>OR
>>>- a file in which I can see that bug
>>>
>>> Is that problem happening in all streams? Or only in one specific 
>>> tiddler?
>>>
>>>
>>>
>>> On Tuesday, June 16, 2020 at 12:40:42 PM UTC+2, OGNSYA wrote:

 Thanks Saq.

 *Here's a very specific bug I'm getting *, which doesn't happen in 
 your website (my setup is TiddlyDesktop, with Stroll). 
 Navigating using CTRL+Down doesn't work when the next item is a child 
 (ie. indented).
 Otherwise everything else works (including CTRL+Down when the next item 
 is a parent).

 *And a suggestion/request*: when breaking a node in two, by pressing 
 ENTER, could the caret (the text cursor) be moved to the *start* of 
 the new node (instead of to the end)? To me that would be the most 
 intuitive. It would be particularly helpful when manually breaking up 
 longer texts.

 On Sunday, June 14, 2020 at 3:52:13 PM UTC+1, Saq Imtiaz wrote:
>
> I've pushed an update that fixes the bug with drag and drop. It's 
> something that crept in when I recently refactored to change field names 
> and plugin name.
>
> I've had a few things come up that will limit the time I have 
> available to work on this in the short term. So for now, I am focusing on 
> bug reports only.
>
>  Will revisit other feedback once I am able to. In the meantime please 
> feel free to keep the feedback coming.
> Cheers,
>
> Saq
>
> On Sunday, June 14, 2020 at 11:43:41 AM UTC+2, OGNSYA wrote:
>>
>> @Saq, thanks for addressing all our questions!
>>
>> *Single-click edit*: Got it! I didn't realize external links 
>> couldn't be clicked. I thought they'd behave the same as [[internal 
>> links]], which could be clicked in the initial (single-click) version of 
>> your plugin. I didn't know there was this distinction. (Maybe offer 
>> users a 
>> single-click option, which requires CTRL-click for links?)
>>
>> *Autocomplete*: I also ran into the autocomplete issue with 
>> edit-comptext. Thank you for the pull request 
>>
>> *Direct editing*: In my previous email I suggest: *"Have you 
>> considered structuring it so that text can be directly edited at any 
>> level 
>> (ie., without needing to go into Edit mode)? Currently you can only edit 
>> child notes directly, but not the content of the node itself. This would 
>> make the editing experience consistent in all levels of hierarchy"*
>> To be clear, I don't refer to WYSIWYG here. This would be just to 
>> keep the experience consistent for the end user.
>>
>> *Possible bug?*: I didn't see any reference to this anywhere, so I 
>> thought I'd mention. I'm not able to CTRL or SHIFT drag a bullet (ie., 
>> Copy 
>> or Transclude) to another tiddler (nothing happens). I can only drag it 
>> directly - ie., Move. 
>>
>> Thanks! Streams is currently my favorite way to edit TW
>>
>>
>> On Saturday, June 13, 2020 at 6:06:31 AM UTC+1, Saq Imtiaz wrote:
>>>
>>> Regarding title autocomplete via the edit-comptext plugin, the 
>>> problem is that it replaces the default editor with another. Since 
>>> Streams 
>>> also makes tweaks to the editor, it makes it difficult to combine the 
>>> two.
>>>
>>> I've re-written parts of the edit-comptext plugin to tweak the core 
>>> editor and add the same autocomplete features to it instead of creating 
>>> a 
>>> new editor. If these changes get merged by the developer, anyone with 
>>> that 
>>> plugin installed with automatically have title autocomplete in Streams.
>>> Pull request: https://github.com/snowgoon88/TW5-extendedit/pull/17
>>>
>>> If anyone is having issues with node duplication after drag and 
>>> drop, please ensure

[tw5] Re: Preview: keyboard driven draggable bullets

2020-06-16 Thread Saq Imtiaz

I've pushed an update that should address that bug. I suspect we will find 
a few more of these until I get the chance to do a comprehensive code 
review, one is really needed after the major refactoring I did to rename 
fields.

Saq

On Tuesday, June 16, 2020 at 4:54:02 PM UTC+2, OGNSYA wrote:
>
> I just tested again in your demo 
>  and it actually happens 
> there too.
> Please see image attached.
> CTRL+down doesn't work for going from node A to A1 or from B to B1 (it 
> works for all other operations).
> Let me know if you can't reproduce it, or if you want me to do any further 
> tests
>
>
> On Tuesday, June 16, 2020 at 2:39:06 PM UTC+1, Saq Imtiaz wrote:
>>
>> @OGNSYA in order to try to investigate that potential bug I will need 
>> either:
>>
>>- specific steps to re-create that bug in my demo
>>OR
>>- a file in which I can see that bug
>>
>> Is that problem happening in all streams? Or only in one specific tiddler?
>>
>>
>>
>> On Tuesday, June 16, 2020 at 12:40:42 PM UTC+2, OGNSYA wrote:
>>>
>>> Thanks Saq.
>>>
>>> *Here's a very specific bug I'm getting *, which doesn't happen in your 
>>> website (my setup is TiddlyDesktop, with Stroll). 
>>> Navigating using CTRL+Down doesn't work when the next item is a child 
>>> (ie. indented).
>>> Otherwise everything else works (including CTRL+Down when the next item 
>>> is a parent).
>>>
>>> *And a suggestion/request*: when breaking a node in two, by pressing 
>>> ENTER, could the caret (the text cursor) be moved to the *start* of the 
>>> new node (instead of to the end)? To me that would be the most intuitive. 
>>> It would be particularly helpful when manually breaking up longer texts.
>>>
>>> On Sunday, June 14, 2020 at 3:52:13 PM UTC+1, Saq Imtiaz wrote:

 I've pushed an update that fixes the bug with drag and drop. It's 
 something that crept in when I recently refactored to change field names 
 and plugin name.

 I've had a few things come up that will limit the time I have available 
 to work on this in the short term. So for now, I am focusing on bug 
 reports 
 only.

  Will revisit other feedback once I am able to. In the meantime please 
 feel free to keep the feedback coming.
 Cheers,

 Saq

 On Sunday, June 14, 2020 at 11:43:41 AM UTC+2, OGNSYA wrote:
>
> @Saq, thanks for addressing all our questions!
>
> *Single-click edit*: Got it! I didn't realize external links couldn't 
> be clicked. I thought they'd behave the same as [[internal links]], which 
> could be clicked in the initial (single-click) version of your plugin. I 
> didn't know there was this distinction. (Maybe offer users a single-click 
> option, which requires CTRL-click for links?)
>
> *Autocomplete*: I also ran into the autocomplete issue with 
> edit-comptext. Thank you for the pull request 
>
> *Direct editing*: In my previous email I suggest: *"Have you 
> considered structuring it so that text can be directly edited at any 
> level 
> (ie., without needing to go into Edit mode)? Currently you can only edit 
> child notes directly, but not the content of the node itself. This would 
> make the editing experience consistent in all levels of hierarchy"*
> To be clear, I don't refer to WYSIWYG here. This would be just to keep 
> the experience consistent for the end user.
>
> *Possible bug?*: I didn't see any reference to this anywhere, so I 
> thought I'd mention. I'm not able to CTRL or SHIFT drag a bullet (ie., 
> Copy 
> or Transclude) to another tiddler (nothing happens). I can only drag it 
> directly - ie., Move. 
>
> Thanks! Streams is currently my favorite way to edit TW
>
>
> On Saturday, June 13, 2020 at 6:06:31 AM UTC+1, Saq Imtiaz wrote:
>>
>> Regarding title autocomplete via the edit-comptext plugin, the 
>> problem is that it replaces the default editor with another. Since 
>> Streams 
>> also makes tweaks to the editor, it makes it difficult to combine the 
>> two.
>>
>> I've re-written parts of the edit-comptext plugin to tweak the core 
>> editor and add the same autocomplete features to it instead of creating 
>> a 
>> new editor. If these changes get merged by the developer, anyone with 
>> that 
>> plugin installed with automatically have title autocomplete in Streams.
>> Pull request: https://github.com/snowgoon88/TW5-extendedit/pull/17
>>
>> If anyone is having issues with node duplication after drag and drop, 
>> please ensure that you have the latest version of Streams. There was a 
>> bug 
>> fix related to this some days ago.
>>
>> 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

[tw5] Re: Preview: keyboard driven draggable bullets

2020-06-16 Thread OGNSYA

I just tested again in your demo 
 and it actually happens 
there too.
Please see image attached.
CTRL+down doesn't work for going from node A to A1 or from B to B1 (it 
works for all other operations).
Let me know if you can't reproduce it, or if you want me to do any further 
tests

On Tuesday, June 16, 2020 at 2:39:06 PM UTC+1, Saq Imtiaz wrote:
>
> @OGNSYA in order to try to investigate that potential bug I will need 
> either:
>
>- specific steps to re-create that bug in my demo
>OR
>- a file in which I can see that bug
>
> Is that problem happening in all streams? Or only in one specific tiddler?
>
>
>
> On Tuesday, June 16, 2020 at 12:40:42 PM UTC+2, OGNSYA wrote:
>>
>> Thanks Saq.
>>
>> *Here's a very specific bug I'm getting *, which doesn't happen in your 
>> website (my setup is TiddlyDesktop, with Stroll). 
>> Navigating using CTRL+Down doesn't work when the next item is a child 
>> (ie. indented).
>> Otherwise everything else works (including CTRL+Down when the next item 
>> is a parent).
>>
>> *And a suggestion/request*: when breaking a node in two, by pressing 
>> ENTER, could the caret (the text cursor) be moved to the *start* of the 
>> new node (instead of to the end)? To me that would be the most intuitive. 
>> It would be particularly helpful when manually breaking up longer texts.
>>
>> On Sunday, June 14, 2020 at 3:52:13 PM UTC+1, Saq Imtiaz wrote:
>>>
>>> I've pushed an update that fixes the bug with drag and drop. It's 
>>> something that crept in when I recently refactored to change field names 
>>> and plugin name.
>>>
>>> I've had a few things come up that will limit the time I have available 
>>> to work on this in the short term. So for now, I am focusing on bug reports 
>>> only.
>>>
>>>  Will revisit other feedback once I am able to. In the meantime please 
>>> feel free to keep the feedback coming.
>>> Cheers,
>>>
>>> Saq
>>>
>>> On Sunday, June 14, 2020 at 11:43:41 AM UTC+2, OGNSYA wrote:

 @Saq, thanks for addressing all our questions!

 *Single-click edit*: Got it! I didn't realize external links couldn't 
 be clicked. I thought they'd behave the same as [[internal links]], which 
 could be clicked in the initial (single-click) version of your plugin. I 
 didn't know there was this distinction. (Maybe offer users a single-click 
 option, which requires CTRL-click for links?)

 *Autocomplete*: I also ran into the autocomplete issue with 
 edit-comptext. Thank you for the pull request 

 *Direct editing*: In my previous email I suggest: *"Have you 
 considered structuring it so that text can be directly edited at any level 
 (ie., without needing to go into Edit mode)? Currently you can only edit 
 child notes directly, but not the content of the node itself. This would 
 make the editing experience consistent in all levels of hierarchy"*
 To be clear, I don't refer to WYSIWYG here. This would be just to keep 
 the experience consistent for the end user.

 *Possible bug?*: I didn't see any reference to this anywhere, so I 
 thought I'd mention. I'm not able to CTRL or SHIFT drag a bullet (ie., 
 Copy 
 or Transclude) to another tiddler (nothing happens). I can only drag it 
 directly - ie., Move. 

 Thanks! Streams is currently my favorite way to edit TW

 On Saturday, June 13, 2020 at 6:06:31 AM UTC+1, Saq Imtiaz wrote:
>
> Regarding title autocomplete via the edit-comptext plugin, the problem 
> is that it replaces the default editor with another. Since Streams also 
> makes tweaks to the editor, it makes it difficult to combine the two.
>
> I've re-written parts of the edit-comptext plugin to tweak the core 
> editor and add the same autocomplete features to it instead of creating a 
> new editor. If these changes get merged by the developer, anyone with 
> that 
> plugin installed with automatically have title autocomplete in Streams.
> Pull request: https://github.com/snowgoon88/TW5-extendedit/pull/17
>
> If anyone is having issues with node duplication after drag and drop, 
> please ensure that you have the latest version of Streams. There was a 
> bug 
> fix related to this some days ago.
>
> 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/fbcef1f1-db26-4379-990d-106ef3b384ebo%40googlegroups.com.

[tw5] Re: Preview: keyboard driven draggable bullets

2020-06-16 Thread Saq Imtiaz

@OGNSYA in order to try to investigate that potential bug I will need 
either:

   - specific steps to re-create that bug in my demo
   OR
   - a file in which I can see that bug

Is that problem happening in all streams? Or only in one specific tiddler?



On Tuesday, June 16, 2020 at 12:40:42 PM UTC+2, OGNSYA wrote:
>
> Thanks Saq.
>
> *Here's a very specific bug I'm getting *, which doesn't happen in your 
> website (my setup is TiddlyDesktop, with Stroll). 
> Navigating using CTRL+Down doesn't work when the next item is a child (ie. 
> indented).
> Otherwise everything else works (including CTRL+Down when the next item is 
> a parent).
>
> *And a suggestion/request*: when breaking a node in two, by pressing 
> ENTER, could the caret (the text cursor) be moved to the *start* of the 
> new node (instead of to the end)? To me that would be the most intuitive. 
> It would be particularly helpful when manually breaking up longer texts.
>
> On Sunday, June 14, 2020 at 3:52:13 PM UTC+1, Saq Imtiaz wrote:
>>
>> I've pushed an update that fixes the bug with drag and drop. It's 
>> something that crept in when I recently refactored to change field names 
>> and plugin name.
>>
>> I've had a few things come up that will limit the time I have available 
>> to work on this in the short term. So for now, I am focusing on bug reports 
>> only.
>>
>>  Will revisit other feedback once I am able to. In the meantime please 
>> feel free to keep the feedback coming.
>> Cheers,
>>
>> Saq
>>
>> On Sunday, June 14, 2020 at 11:43:41 AM UTC+2, OGNSYA wrote:
>>>
>>> @Saq, thanks for addressing all our questions!
>>>
>>> *Single-click edit*: Got it! I didn't realize external links couldn't 
>>> be clicked. I thought they'd behave the same as [[internal links]], which 
>>> could be clicked in the initial (single-click) version of your plugin. I 
>>> didn't know there was this distinction. (Maybe offer users a single-click 
>>> option, which requires CTRL-click for links?)
>>>
>>> *Autocomplete*: I also ran into the autocomplete issue with 
>>> edit-comptext. Thank you for the pull request 
>>>
>>> *Direct editing*: In my previous email I suggest: *"Have you considered 
>>> structuring it so that text can be directly edited at any level (ie., 
>>> without needing to go into Edit mode)? Currently you can only edit child 
>>> notes directly, but not the content of the node itself. This would make the 
>>> editing experience consistent in all levels of hierarchy"*
>>> To be clear, I don't refer to WYSIWYG here. This would be just to keep 
>>> the experience consistent for the end user.
>>>
>>> *Possible bug?*: I didn't see any reference to this anywhere, so I 
>>> thought I'd mention. I'm not able to CTRL or SHIFT drag a bullet (ie., Copy 
>>> or Transclude) to another tiddler (nothing happens). I can only drag it 
>>> directly - ie., Move. 
>>>
>>> Thanks! Streams is currently my favorite way to edit TW
>>>
>>>
>>> On Saturday, June 13, 2020 at 6:06:31 AM UTC+1, Saq Imtiaz wrote:

 Regarding title autocomplete via the edit-comptext plugin, the problem 
 is that it replaces the default editor with another. Since Streams also 
 makes tweaks to the editor, it makes it difficult to combine the two.

 I've re-written parts of the edit-comptext plugin to tweak the core 
 editor and add the same autocomplete features to it instead of creating a 
 new editor. If these changes get merged by the developer, anyone with that 
 plugin installed with automatically have title autocomplete in Streams.
 Pull request: https://github.com/snowgoon88/TW5-extendedit/pull/17

 If anyone is having issues with node duplication after drag and drop, 
 please ensure that you have the latest version of Streams. There was a bug 
 fix related to this some days ago.

 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/c0f96932-d5f6-4cdb-8106-dc875fc176c8o%40googlegroups.com.

[tw5] Re: Preview: keyboard driven draggable bullets

2020-06-16 Thread OGNSYA

Thanks Saq.

*Here's a very specific bug I'm getting *, which doesn't happen in your 
website (my setup is TiddlyDesktop, with Stroll). 
Navigating using CTRL+Down doesn't work when the next item is a child (ie. 
indented).
Otherwise everything else works (including CTRL+Down when the next item is 
a parent).

*And a suggestion/request*: when breaking a node in two, by pressing ENTER, 
could the caret (the text cursor) be moved to the *start* of the new node 
(instead of to the end)? To me that would be the most intuitive. It would 
be particularly helpful when manually breaking up longer texts.

On Sunday, June 14, 2020 at 3:52:13 PM UTC+1, Saq Imtiaz wrote:
>
> I've pushed an update that fixes the bug with drag and drop. It's 
> something that crept in when I recently refactored to change field names 
> and plugin name.
>
> I've had a few things come up that will limit the time I have available to 
> work on this in the short term. So for now, I am focusing on bug reports 
> only.
>
>  Will revisit other feedback once I am able to. In the meantime please 
> feel free to keep the feedback coming.
> Cheers,
>
> Saq
>
> On Sunday, June 14, 2020 at 11:43:41 AM UTC+2, OGNSYA wrote:
>>
>> @Saq, thanks for addressing all our questions!
>>
>> *Single-click edit*: Got it! I didn't realize external links couldn't be 
>> clicked. I thought they'd behave the same as [[internal links]], which 
>> could be clicked in the initial (single-click) version of your plugin. I 
>> didn't know there was this distinction. (Maybe offer users a single-click 
>> option, which requires CTRL-click for links?)
>>
>> *Autocomplete*: I also ran into the autocomplete issue with 
>> edit-comptext. Thank you for the pull request 
>>
>> *Direct editing*: In my previous email I suggest: *"Have you considered 
>> structuring it so that text can be directly edited at any level (ie., 
>> without needing to go into Edit mode)? Currently you can only edit child 
>> notes directly, but not the content of the node itself. This would make the 
>> editing experience consistent in all levels of hierarchy"*
>> To be clear, I don't refer to WYSIWYG here. This would be just to keep 
>> the experience consistent for the end user.
>>
>> *Possible bug?*: I didn't see any reference to this anywhere, so I 
>> thought I'd mention. I'm not able to CTRL or SHIFT drag a bullet (ie., Copy 
>> or Transclude) to another tiddler (nothing happens). I can only drag it 
>> directly - ie., Move. 
>>
>> Thanks! Streams is currently my favorite way to edit TW
>>
>>
>> On Saturday, June 13, 2020 at 6:06:31 AM UTC+1, Saq Imtiaz wrote:
>>>
>>> Regarding title autocomplete via the edit-comptext plugin, the problem 
>>> is that it replaces the default editor with another. Since Streams also 
>>> makes tweaks to the editor, it makes it difficult to combine the two.
>>>
>>> I've re-written parts of the edit-comptext plugin to tweak the core 
>>> editor and add the same autocomplete features to it instead of creating a 
>>> new editor. If these changes get merged by the developer, anyone with that 
>>> plugin installed with automatically have title autocomplete in Streams.
>>> Pull request: https://github.com/snowgoon88/TW5-extendedit/pull/17
>>>
>>> If anyone is having issues with node duplication after drag and drop, 
>>> please ensure that you have the latest version of Streams. There was a bug 
>>> fix related to this some days ago.
>>>
>>> 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/99ec2fb7-a914-457e-9015-5a1e0d4b8550o%40googlegroups.com.

[tw5] Re: Preview: keyboard driven draggable bullets

2020-06-14 Thread Saq Imtiaz

I've pushed an update that fixes the bug with drag and drop. It's something 
that crept in when I recently refactored to change field names and plugin 
name.

I've had a few things come up that will limit the time I have available to 
work on this in the short term. So for now, I am focusing on bug reports 
only.

 Will revisit other feedback once I am able to. In the meantime please feel 
free to keep the feedback coming.
Cheers,

Saq

On Sunday, June 14, 2020 at 11:43:41 AM UTC+2, OGNSYA wrote:
>
> @Saq, thanks for addressing all our questions!
>
> *Single-click edit*: Got it! I didn't realize external links couldn't be 
> clicked. I thought they'd behave the same as [[internal links]], which 
> could be clicked in the initial (single-click) version of your plugin. I 
> didn't know there was this distinction. (Maybe offer users a single-click 
> option, which requires CTRL-click for links?)
>
> *Autocomplete*: I also ran into the autocomplete issue with 
> edit-comptext. Thank you for the pull request 
>
> *Direct editing*: In my previous email I suggest: *"Have you considered 
> structuring it so that text can be directly edited at any level (ie., 
> without needing to go into Edit mode)? Currently you can only edit child 
> notes directly, but not the content of the node itself. This would make the 
> editing experience consistent in all levels of hierarchy"*
> To be clear, I don't refer to WYSIWYG here. This would be just to keep the 
> experience consistent for the end user.
>
> *Possible bug?*: I didn't see any reference to this anywhere, so I 
> thought I'd mention. I'm not able to CTRL or SHIFT drag a bullet (ie., Copy 
> or Transclude) to another tiddler (nothing happens). I can only drag it 
> directly - ie., Move. 
>
> Thanks! Streams is currently my favorite way to edit TW
>
>
> On Saturday, June 13, 2020 at 6:06:31 AM UTC+1, Saq Imtiaz wrote:
>>
>> Regarding title autocomplete via the edit-comptext plugin, the problem is 
>> that it replaces the default editor with another. Since Streams also makes 
>> tweaks to the editor, it makes it difficult to combine the two.
>>
>> I've re-written parts of the edit-comptext plugin to tweak the core 
>> editor and add the same autocomplete features to it instead of creating a 
>> new editor. If these changes get merged by the developer, anyone with that 
>> plugin installed with automatically have title autocomplete in Streams.
>> Pull request: https://github.com/snowgoon88/TW5-extendedit/pull/17
>>
>> If anyone is having issues with node duplication after drag and drop, 
>> please ensure that you have the latest version of Streams. There was a bug 
>> fix related to this some days ago.
>>
>> 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/9d993140-0088-473a-8f75-a8e0a662a340o%40googlegroups.com.

[tw5] Re: Preview: keyboard driven draggable bullets

2020-06-14 Thread OGNSYA

@Saq, thanks for addressing all our questions!

*Single-click edit*: Got it! I didn't realize external links couldn't be 
clicked. I thought they'd behave the same as [[internal links]], which 
could be clicked in the initial (single-click) version of your plugin. I 
didn't know there was this distinction. (Maybe offer users a single-click 
option, which requires CTRL-click for links?)

*Autocomplete*: I also ran into the autocomplete issue with edit-comptext. 
Thank you for the pull request 

*Direct editing*: In my previous email I suggest: *"Have you considered 
structuring it so that text can be directly edited at any level (ie., 
without needing to go into Edit mode)? Currently you can only edit child 
notes directly, but not the content of the node itself. This would make the 
editing experience consistent in all levels of hierarchy"*
To be clear, I don't refer to WYSIWYG here. This would be just to keep the 
experience consistent for the end user.

*Possible bug?*: I didn't see any reference to this anywhere, so I thought 
I'd mention. I'm not able to CTRL or SHIFT drag a bullet (ie., Copy or 
Transclude) to another tiddler (nothing happens). I can only drag it 
directly - ie., Move. 

Thanks! Streams is currently my favorite way to edit TW

On Saturday, June 13, 2020 at 6:06:31 AM UTC+1, Saq Imtiaz wrote:
>
> Regarding title autocomplete via the edit-comptext plugin, the problem is 
> that it replaces the default editor with another. Since Streams also makes 
> tweaks to the editor, it makes it difficult to combine the two.
>
> I've re-written parts of the edit-comptext plugin to tweak the core editor 
> and add the same autocomplete features to it instead of creating a new 
> editor. If these changes get merged by the developer, anyone with that 
> plugin installed with automatically have title autocomplete in Streams.
> Pull request: https://github.com/snowgoon88/TW5-extendedit/pull/17
>
> If anyone is having issues with node duplication after drag and drop, 
> please ensure that you have the latest version of Streams. There was a bug 
> fix related to this some days ago.
>
> 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/64b575d0-7a2e-4cb1-8923-21658d911d73o%40googlegroups.com.

[tw5] Re: Preview: keyboard driven draggable bullets

2020-06-12 Thread Saq Imtiaz

Regarding title autocomplete via the edit-comptext plugin, the problem is 
that it replaces the default editor with another. Since Streams also makes 
tweaks to the editor, it makes it difficult to combine the two.

I've re-written parts of the edit-comptext plugin to tweak the core editor 
and add the same autocomplete features to it instead of creating a new 
editor. If these changes get merged by the developer, anyone with that 
plugin installed with automatically have title autocomplete in Streams.
Pull request: https://github.com/snowgoon88/TW5-extendedit/pull/17

If anyone is having issues with node duplication after drag and drop, 
please ensure that you have the latest version of Streams. There was a bug 
fix related to this some days ago.

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/28cd077a-6a02-4a15-b54d-d83836012251o%40googlegroups.com.

[tw5] Re: Preview: keyboard driven draggable bullets

Sorry for bothering again, but the editcomp plugin (the plugin that 
autocompletes title when you type [[) does not seem to be working when 
editing inside the node/bullet. But it is working fine when editing inside 
a standalone tiddler. Is there a way to get it work inside the node too? 

On Thursday, June 11, 2020 at 9:43:51 PM UTC+5:30, Saq Imtiaz wrote:
>
>
>
> On Thursday, June 11, 2020 at 5:58:32 PM UTC+2, Raghu Veer S wrote:
>>
>> Btw here is another thing I observed, I thought it was counter-intuitive 
>> to what I was expecting to happen, so just wanted to know if this was the 
>> desired effect:
>>
>
> Essentially, yes. The mismatch with expectations is due to expecting the 
> behavior one would expect in say MS Word or a WYSIWYG editor.  Pressing 
> Enter does not "push the parent node down". Rather what is happening here 
> is that:
>
> - since the caret is not at the end of the text, this is interpreted as an 
> attempt to split the text into two nodes.
> - everything after the caret is moved to a new node created after the 
> current one, children stay with the current node.
> - this was in response to a user request to be able to press enter in the 
> middle of a chunk of text and divide it into separate nodes. If it proves 
> counter-intuitive, it might be dropped. 
>
> It may also be possible to consider having the caret at the start of the 
> text as a special use case with different handling similar to what you 
> expected, i.e. insert a new node before the current one. However before 
> adding more complexity I want to make sure this behavior dependent on caret 
> position is going to stable enough to keep this feature in.
>
> Apart from this exceptional scenario when the caret is not at the end of 
> the text, the behavior in general when pressing enter is that the node 
> being edited is saved, and a new subsequent node is created.
>
>

-- 
You received this message because you are subscribed to the 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/50212ff5-1368-4695-a72c-ca59499c700co%40googlegroups.com.

[tw5] Re: Preview: keyboard driven draggable bullets

2020-06-11 Thread Saq Imtiaz

On Thursday, June 11, 2020 at 5:58:32 PM UTC+2, Raghu Veer S wrote:
>
> Btw here is another thing I observed, I thought it was counter-intuitive 
> to what I was expecting to happen, so just wanted to know if this was the 
> desired effect:
>

Essentially, yes. The mismatch with expectations is due to expecting the 
behavior one would expect in say MS Word or a WYSIWYG editor.  Pressing 
Enter does not "push the parent node down". Rather what is happening here 
is that:

- since the caret is not at the end of the text, this is interpreted as an 
attempt to split the text into two nodes.
- everything after the caret is moved to a new node created after the 
current one, children stay with the current node.
- this was in response to a user request to be able to press enter in the 
middle of a chunk of text and divide it into separate nodes. If it proves 
counter-intuitive, it might be dropped. 

It may also be possible to consider having the caret at the start of the 
text as a special use case with different handling similar to what you 
expected, i.e. insert a new node before the current one. However before 
adding more complexity I want to make sure this behavior dependent on caret 
position is going to stable enough to keep this feature in.

Apart from this exceptional scenario when the caret is not at the end of 
the text, the behavior in general when pressing enter is that the node 
being edited is saved, and a new subsequent node is created.

-- 
You received this message because you are subscribed to the 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/8444e297-c0f4-474a-93bf-67fab3882172o%40googlegroups.com.

[tw5] Re: Preview: keyboard driven draggable bullets

Thanks for the response Tony. That is definitely reassuring. :)

On Thursday, June 11, 2020 at 6:54:58 PM UTC+5:30, TW Tones wrote:
>
> Raghu
>
>
>>- I also had a question regarding this: Since every bullet is a 
>>separate tiddler, can it negatively affect the performance of my wiki, if 
>> I 
>>create lots of short bullets?
>>
>> No need to worry unless you are in the 10's of thousands of  "lots of 
> short bullets", and then if you do we have a lot of optimisation options. 
> In the last year or so I worked on a dictionary wiki to translate between 
> two languages and we got a 66,000 word vocabulary where words were tiddlers 
> working fine, 
>
> Try typing that.
>
> Regards
> Tony
>
>>

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/97e9f22e-82cf-40f2-b811-9cf09f37bb60o%40googlegroups.com.

[tw5] Re: Preview: keyboard driven draggable bullets

Hi Saq, 

Thanks for the response. No worries, I understand the difficulties 
involved.  :)

As for the usecase, I just thought that easy indentation would be crucial 
to a hierarchical outlining plugin like this, at least that is something 
that I have been finding useful with Roam and Dynalist as I used to use 
them extensively for research purposes along with other operations like the 
ones you have mentioned. I was looking for a more local first OSS tool, 
which is where I though TiddlyWiki with the plugin ecosystem shined with 
plugins like yours. Anyway, these were more like a feature request than a 
feedback, so don't be bothered with it. I am still enjoying the tool. :)

On Thursday, June 11, 2020 at 6:52:37 PM UTC+5:30, Saq Imtiaz wrote:
>
> Replies to some of the feedback below:
>
> *Single-click to edit:* will not be offered as an option unless we can 
> find a reliable way of doing so while still allowing users to click on 
> external links, and copy text as a selection, without inadvertently 
> triggering editing.
>
> *Modal approach to editing:* I have no idea what this means. Modals have 
> a very specific meaning in TW. As explained earlier, this is not an attempt 
> at at WYSIWYG editor. As is the norm in TW, there is a separation between 
> viewing content and editing it. If someone implements a WYSIWYG editor for 
> wikitext, you could easily use that within Streams. Implementing one within 
> Streams is far outside the scope of this plugin. Having to specifically 
> decide to edit a different tiddler is not only necessary, but intentional 
> from a design point of view. 
>
> *Backspace, arrow up/down behavior:* with the default widgets we have 
> available in TW, complex and conditional handling of keys is simply not 
> possible. For instance, enabling backspace at the beginning of some text to 
> combine that node with the previous one, would disable the backspace key 
> for all other usage in the editor. The keystroke is trapped by the widget, 
> there is no means to conditionally pass it through for the default 
> behavior. 
>
> So implementing this kind of behavior would require a custom JavaScript 
> plugin, and even then the behavior wont be quite as requested as once 
> again, this isn't WYSIWYG. While I could write such a plugin, I am 
> realistic that I would not have the time to support and maintain it. 
> Therefore my focus is on using core widgets and community plugins, and only 
> writing JavaScript when absolutely essential or trivial. If someone wants 
> to take a crack at a more elaborate plugin for handling key bindings, I 
> will be happy to provide input and guidance, and make use of it in Streams.
>
> *Performance: *I am probably not the best placed to comment on 
> performance. I have a wiki with 6000 tiddlers that runs fine, but I use 
> very little in terms of complex list filters and backlinks, tags etc. 
> Others may be better placed to advise on this.
>
> *Personally I see three kinds of situations in which I would use this as 
> is today:*
> - for longer text that benefits from structure, order and hierarchy. 
> Writing an essay, or project documentation. In this case each tiddler would 
> be a paragraph or longer. So you would not end up with more tiddlers than 
> you normally would, you just get a more convenient workflow for the writing 
> process and dividing your writing into tiddlers as you go.
> - for short pieces of text that are somewhat transient in nature, e.g task 
> lists. You delete or archive them as they are completed. The Roadmap 
> tiddler in the demo is a good example of this.
> - to compose text that will require significant re-ordering etc while 
> writing, and then export it to a static/regular tiddler
>
> If you primarily using this to be able to easily indent/unindent text, 
> then you're using it for a purpose other than what it is designed for and 
> arguably would be better served by other tools.
>
> 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/2e902077-1e79-4d43-b0bc-0a64c7397d8do%40googlegroups.com.

[tw5] Re: Preview: keyboard driven draggable bullets

2020-06-11 Thread TW Tones

Raghu


>- I also had a question regarding this: Since every bullet is a 
>separate tiddler, can it negatively affect the performance of my wiki, if 
> I 
>create lots of short bullets?
>
> No need to worry unless you are in the 10's of thousands of  "lots of 
short bullets", and then if you do we have a lot of optimisation options. 
In the last year or so I worked on a dictionary wiki to translate between 
two languages and we got a 66,000 word vocabulary where words were tiddlers 
working fine, 

Try typing that.

Regards
Tony

>

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/7b36b36e-2acc-4710-84b1-74a7fb1f68a8o%40googlegroups.com.

[tw5] Re: Preview: keyboard driven draggable bullets

2020-06-11 Thread Saq Imtiaz

Replies to some of the feedback below:

*Single-click to edit:* will not be offered as an option unless we can find
a reliable way of doing so while still allowing users to click on external
links, and copy text as a selection, without inadvertently triggering
editing.

*Modal approach to editing:* I have no idea what this means. Modals have a
very specific meaning in TW. As explained earlier, this is not an attempt
at at WYSIWYG editor. As is the norm in TW, there is a separation between
viewing content and editing it. If someone implements a WYSIWYG editor for
wikitext, you could easily use that within Streams. Implementing one within
Streams is far outside the scope of this plugin. Having to specifically
decide to edit a different tiddler is not only necessary, but intentional
from a design point of view.

*Backspace, arrow up/down behavior:* with the default widgets we have
available in TW, complex and conditional handling of keys is simply not
possible. For instance, enabling backspace at the beginning of some text to
combine that node with the previous one, would disable the backspace key
for all other usage in the editor. The keystroke is trapped by the widget,
there is no means to conditionally pass it through for the default
behavior.

So implementing this kind of behavior would require a custom JavaScript
plugin, and even then the behavior wont be quite as requested as once
again, this isn't WYSIWYG. While I could write such a plugin, I am
realistic that I would not have the time to support and maintain it.
Therefore my focus is on using core widgets and community plugins, and only
writing JavaScript when absolutely essential or trivial. If someone wants
to take a crack at a more elaborate plugin for handling key bindings, I
will be happy to provide input and guidance, and make use of it in Streams.

*Performance: *I am probably not the best placed to comment on performance.
I have a wiki with 6000 tiddlers that runs fine, but I use very little in
terms of complex list filters and backlinks, tags etc. Others may be better
placed to advise on this.

*Personally I see three kinds of situations in which I would use this as is
today:*
- for longer text that benefits from structure, order and hierarchy.
Writing an essay, or project documentation. In this case each tiddler would
be a paragraph or longer. So you would not end up with more tiddlers than
you normally would, you just get a more convenient workflow for the writing
process and dividing your writing into tiddlers as you go.
- for short pieces of text that are somewhat transient in nature, e.g task
lists. You delete or archive them as they are completed. The Roadmap
tiddler in the demo is a good example of this.
- to compose text that will require significant re-ordering etc while
writing, and then export it to a static/regular tiddler

If you primarily using this to be able to easily indent/unindent text, then
you're using it for a purpose other than what it is designed for and
arguably would be better served by other tools.

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/da84b99e-67b3-4a59-987d-533e791535b7o%40googlegroups.com.

[tw5] Re: Preview: keyboard driven draggable bullets

+1ing OGNSYA here. I too have been using it for a couple of days now, and 
It is fantastic. I am starting to feel that this could become the normative 
way to use TW with a little bit of polish. Some UX tweaks that I feel would 
make the experience more fluid (at least for me) would be:


   -  Everything that OGYNSYA said - a) Single click to edit; b) Removing 
   the modal approach to editing nodes.
   - Allowing up arrow/down arrow to be used when the cursor is at the top 
   most/bottom most line of a node respectively  would make it easy to 
   navigate between nodes without having to use key combinations when not 
   necessary. Same with left arrow when the cursor is at the beginning of the 
   node and right for end of the node.
   - Pressing backspace when the cursor is at the beginning of the node 
   should delete the current node and append its content to the end of the 
   previous node. 
   

I don't know how difficult these are to accomplish, but I think this would 
make it more natural/intuitive to operate. 


   - I also had a question regarding this: Since everything bullet is a 
   separate tiddler, can it negatively affect the performance of my wiki, if I 
   create lots of short bullets?

All said, thanks for the plugin. It's really awesome. :)

On Thursday, June 11, 2020 at 3:05:55 PM UTC+5:30, OGNSYA wrote:
>
> Been testing it for a few days. Works great!
>
>
>- I'd rather click once to edit though, like it was before (instead of 
>needing to double-click). Do you plan on adding this as an option? If not, 
>can I customize this?
>
>
>- Have you considered structuring it so that text can be directly 
>edited at *any* level (ie., without needing to go into Edit mode)? 
>Currently you can only edit child notes directly, but not the content of 
>the node itself. This would make the editing experience consistent in all 
>levels of hierarchy (more similar to how Roam does it, for example).
>
>
> On Wednesday, May 20, 2020 at 10:44:31 PM UTC+1, Saq Imtiaz wrote:
>>
>> Edited (09/06/2020)
>> This is in active development. Back up your wiki regularly.
>>
>> Demo:
>> https://saqimtiaz.github.io/sq-tw/streams.html
>>
>> *Code:*
>> https://github.com/saqimtiaz/streams
>>
>> ---
>>
>> When I'm under the weather I tend to prototype. Spent some time reworking 
>> code from my eternally in progress task manager in an attempt to make it 
>> more general purpose, as a bullet list note taking tool that may be of 
>> utility to others. 
>>
>>
>> https://drive.google.com/file/d/1SB06s13tj8P3cC2UewnfzXf08UQ7jwYK/view?usp=drivesdk
>>
>>
>> https://drive.google.com/file/d/1SLESm6OIfHsScwYePGOs5ce3o3wpQ0CO/view?usp=drivesdk
>>
>> - everything except the dragging is keyboard driven
>> - each bullet is a separate tiddler. Lots of different pros and cons to 
>> this approach, but was ideal for a task manager.
>> - this is all in wikitext, no extra JS.
>>
>>  Will post the file in the near future, a bit more clean up needed. Don't 
>> expect a final product, but rather a pattern to follow that would hopefully 
>> help anyone wanting to implement similar workflow. 
>>
>> Cheers,
>> Saq
>>
>>
>>
>>

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

[tw5] Re: Preview: keyboard driven draggable bullets

2020-06-11 Thread OGNSYA

Been testing it for a few days. Works great!


   - I'd rather click once to edit though, like it was before (instead of 
   needing to double-click). Do you plan on adding this as an option? If not, 
   can I customize this?


   - Have you considered structuring it so that text can be directly edited 
   at *any* level (ie., without needing to go into Edit mode)? Currently 
   you can only edit child notes directly, but not the content of the node 
   itself. This would make the editing experience consistent in all levels of 
   hierarchy (more similar to how Roam does it, for example).


On Wednesday, May 20, 2020 at 10:44:31 PM UTC+1, Saq Imtiaz wrote:
>
> Edited (09/06/2020)
> This is in active development. Back up your wiki regularly.
>
> Demo:
> https://saqimtiaz.github.io/sq-tw/streams.html
>
> *Code:*
> https://github.com/saqimtiaz/streams
>
> ---
>
> When I'm under the weather I tend to prototype. Spent some time reworking 
> code from my eternally in progress task manager in an attempt to make it 
> more general purpose, as a bullet list note taking tool that may be of 
> utility to others. 
>
>
> https://drive.google.com/file/d/1SB06s13tj8P3cC2UewnfzXf08UQ7jwYK/view?usp=drivesdk
>
>
> https://drive.google.com/file/d/1SLESm6OIfHsScwYePGOs5ce3o3wpQ0CO/view?usp=drivesdk
>
> - everything except the dragging is keyboard driven
> - each bullet is a separate tiddler. Lots of different pros and cons to 
> this approach, but was ideal for a task manager.
> - this is all in wikitext, no extra JS.
>
>  Will post the file in the near future, a bit more clean up needed. Don't 
> expect a final product, but rather a pattern to follow that would hopefully 
> help anyone wanting to implement similar workflow. 
>
> Cheers,
> Saq
>
>
>
>

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

[tw5] Re: Preview: keyboard driven draggable bullets

2020-06-11 Thread Saq Imtiaz

Hi Thomas,

Thank you for the feedback, much appreciated.

*Keyboard shortcuts*: yes the intention is to have them in the Control 
Panel, though I am still pondering ways to separate them from other 
shortcuts visually to avoid clutter. The Control Panel lumps together all 
shortcuts: global, for editor formatting and local/application specific, 
which I think makes it a bit confusing for end-users. Ideally I would want 
a separate section or tab for all the keyboard shortcuts specific to this 
plugin. Also on my mind is optimizing a single keyboard widget to handle 
multiple shortcuts. Any suggestions would be very welcome.

*HTML structure: *I have intentionally avoided the use of a / 
elements for various reasons. Among them:
- the way the core droppable widgets work with nested structures and the 
associated difficulties with enabling/disabling drag and drop dependent on 
what is being dragged. Doing as much as possible with core widgets was a 
priority, as it means non-developers can replicate/adapt the work.
- each list item is a tiddler, and therefore can contain a variety of 
content. Using an  would limit what content can be in each list item.
- the visual representation as a list is only the current default and the 
idea is to make this customizable via templates, along with customizing 
what fields are shown from the list tiddlers. I welcome any alternative 
default styling ideas that diminish the association with an HTML list.
- it is far more expedient to create export options to various formats such 
as HTML lists, rather than try to make a nested  structure work 
flexibly with various content and the core drag and drop capabilities.

I find it more appropriate and helpful to think of a stream as a hierarchy 
of tiddlers, rather than a list generated from tiddlers.

Cheers,
Saq

On Thursday, June 11, 2020 at 12:05:25 AM UTC+2, Thomas Elmiger wrote:
>
> Hi Saq, 
>
> Finally I found the time to try this promising tool, thanks for making 
> this!
>
> Suggestions: 
>
>- Roadmap: Do you intend to move keyboard shortcuts to the existing 
>tab "Keyboard Shortcuts" in the Control Panel? That’s where I would like 
> to 
>find them and where multiple shortcuts per command are configurable.
>- HTML structure: As the result looks like a list, I would have 
>expected a nested  structure – that would have the advantage that 
>you can copy paste to e.g. Word and keep the structure.
>
> Just a first impression, I might try again later.
>
> Cheers and good night,
> Thomas
>

-- 
You received this message because you are subscribed to the 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/5143b05d-9aff-4c16-a124-40c8b02dcd2bo%40googlegroups.com.

[tw5] Re: Preview: keyboard driven draggable bullets

2020-06-10 Thread Thomas Elmiger

Hi Saq, 

Finally I found the time to try this promising tool, thanks for making this!

Suggestions: 

   - Roadmap: Do you intend to move keyboard shortcuts to the existing tab 
   "Keyboard Shortcuts" in the Control Panel? That’s where I would like to 
   find them and where multiple shortcuts per command are configurable.
   - HTML structure: As the result looks like a list, I would have expected 
   a nested  structure – that would have the advantage that you can 
   copy paste to e.g. Word and keep the structure.

Just a first impression, I might try again later.

Cheers and good night,
Thomas

-- 
You received this message because you are subscribed to the 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/bda1efd8-de46-4574-b461-ea971f7f71f5o%40googlegroups.com.

Re: [tw5] Re: Preview: keyboard driven draggable bullets

2020-06-10 Thread Pit.W.

Saq, great stuff.

This is what I call a "milestone-plugin", because I think it opens up a
completely new field of productivity.

Good for hi-speed brainstorming, outlining, initial drafting, bookwriting,

An it works with tidgraph and probably with the tocP macros. should be
easy to use it in tiddlymap as well.

Thanks a lot!

Pit.W

Am 10.06.2020 um 11:49 schrieb Saq Imtiaz:
@Raghu try grabbing the latest copy of the plugin, I just pushed a
small update that should resolve this.

https://saqimtiaz.github.io/sq-tw/streams.html

On Wednesday, June 10, 2020 at 11:30:07 AM UTC+2, Raghu Veer S wrote:

Hi Saq,

Really useful plugin. Thanks a lot.

I ran into a issue while using the plugin with a theme that I am
using. I am using a theme called Krystal with TiddlyBlink, the
problem is the bullets are showing up after the backlink/reference
sections instead of showing up inside the tiddler body. I know
this is probably a issue on the side of the theme, but how do I
position the bullets inside the tiddler body?

*See the attached image for reference:
*

On Wednesday, June 10, 2020 at 2:14:47 AM UTC+5:30, Saq Imtiaz wrote:

https://saqimtiaz.github.io/sq-tw/streams.html

Not many outward differences, but I've cleaned up the code a
fair bit and the *field names are now stable*. Which means
that if you starting using it now, you should be able to
upgrade to newer versions without much trouble. So I have
removed the warning about not using this.

One step closer to a beta release.

Prompted by @pmario mention of *mindmaps* etc, on a whim I've
added the TidGraph plugin and you can see what that would look
like here:
https://saqimtiaz.github.io/sq-tw/streams.html#Roadmap%20-%20graph

Please let me know:

* if you find any bugs, there have been a lot of code
changes so something may have crept in
* if there is more documentation that you think is needed
before a beta release. (Any help with documentation would
be most appreciated)

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/3ec850b7-e63c-49b0-8a64-54f1bbedc752o%40googlegroups.com
.

Ihre E-Mail-Postfächer sicher & zentral an einem Ort. Jetzt wechseln und alte
E-Mail-Adresse mitnehmen! https://www.eclipso.de

[tw5] Re: Preview: keyboard driven draggable bullets

2020-06-10 Thread Reet Pandher

Thanks for the quick response Saq. No worries please take your time.
Also a request regarding the css.. please try to make it like this 
one.
 
I was able to customize codemirror without any css knowledge because of how 
easy it was to read. I'm not sure if it is even possible to do it for your 
plugin but i'll throw it out there.
Thanks!!

On Wednesday, June 10, 2020 at 6:25:51 PM UTC+5:30, Saq Imtiaz wrote:
>
> @Reet thanks for the feedback. 
>
> Good news is that this is on the roadmap to attend to before a version 1.0 
> release. See the entry "Update css to respect color palette" on the 
> Roadmap. https://saqimtiaz.github.io/sq-tw/streams.html#Roadmap
> Though even then, with custom themes it will probably require some 
> tweaking of CSS to get things working to your liking.
>
> Bad news is that you are going to have to wait a bit for that to be 
> implemented. 
> Until then, your best bet will be to use the lighter color palette in that 
> theme.
>
>
>
> On Wednesday, June 10, 2020 at 2:40:10 PM UTC+2, Reet Pandher wrote:
>>
>> Hi Saq,
>>
>> Started using it in my test wiki just now and i encountered 2 visual 
>> bugs(?). I have customized my wiki color palette so i have changed 
>> background to black and foreground to white. 
>>
>>1. The moment i start typing in the new bullet tiddler the text box 
>>background turns from black to white. Attached images(1-5) for reference. 
>>2. Link to the source tiddler has black color so not very visible on 
>>my background (image 6)
>>3. Bullet point color is also black colored so not very visible on my 
>>background
>>
>> Also, any chance i can hide the *link to the source tiddler* i mentioned 
>> in point 2 or at least move it to the bottom?
>>
>> On Wednesday, June 10, 2020 at 2:14:47 AM UTC+5:30, Saq Imtiaz wrote:
>>>
>>> https://saqimtiaz.github.io/sq-tw/streams.html
>>>
>>> Not many outward differences, but I've cleaned up the code a fair bit 
>>> and the *field names are now stable*. Which means that if you starting 
>>> using it now, you should be able to upgrade to newer versions without much 
>>> trouble. So I have removed the warning about not using this. 
>>>
>>> One step closer to a beta release.
>>>
>>> Prompted by @pmario mention of *mindmaps* etc, on a whim I've added the 
>>> TidGraph plugin and you can see what that would look like here:
>>> https://saqimtiaz.github.io/sq-tw/streams.html#Roadmap%20-%20graph
>>>
>>> Please let me know:
>>>
>>>- if you find any bugs, there have been a lot of code changes so 
>>>something may have crept in
>>>- if there is more documentation that you think is needed before a 
>>>beta release. (Any help with documentation would be most appreciated)
>>>
>>> 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/3a51b821-fda8-4703-b9e2-0b4a6b14e0eao%40googlegroups.com.

[tw5] Re: Preview: keyboard driven draggable bullets

2020-06-10 Thread Saq Imtiaz

@Reet thanks for the feedback. 

Good news is that this is on the roadmap to attend to before a version 1.0 
release. See the entry "Update css to respect color palette" on the 
Roadmap. https://saqimtiaz.github.io/sq-tw/streams.html#Roadmap
Though even then, with custom themes it will probably require some tweaking 
of CSS to get things working to your liking.

Bad news is that you are going to have to wait a bit for that to be 
implemented. 
Until then, your best bet will be to use the lighter color palette in that 
theme.



On Wednesday, June 10, 2020 at 2:40:10 PM UTC+2, Reet Pandher wrote:
>
> Hi Saq,
>
> Started using it in my test wiki just now and i encountered 2 visual 
> bugs(?). I have customized my wiki color palette so i have changed 
> background to black and foreground to white. 
>
>1. The moment i start typing in the new bullet tiddler the text box 
>background turns from black to white. Attached images(1-5) for reference. 
>2. Link to the source tiddler has black color so not very visible on 
>my background (image 6)
>3. Bullet point color is also black colored so not very visible on my 
>background
>
> Also, any chance i can hide the *link to the source tiddler* i mentioned 
> in point 2 or at least move it to the bottom?
>
> On Wednesday, June 10, 2020 at 2:14:47 AM UTC+5:30, Saq Imtiaz wrote:
>>
>> https://saqimtiaz.github.io/sq-tw/streams.html
>>
>> Not many outward differences, but I've cleaned up the code a fair bit and 
>> the *field names are now stable*. Which means that if you starting using 
>> it now, you should be able to upgrade to newer versions without much 
>> trouble. So I have removed the warning about not using this. 
>>
>> One step closer to a beta release.
>>
>> Prompted by @pmario mention of *mindmaps* etc, on a whim I've added the 
>> TidGraph plugin and you can see what that would look like here:
>> https://saqimtiaz.github.io/sq-tw/streams.html#Roadmap%20-%20graph
>>
>> Please let me know:
>>
>>- if you find any bugs, there have been a lot of code changes so 
>>something may have crept in
>>- if there is more documentation that you think is needed before a 
>>beta release. (Any help with documentation would be most appreciated)
>>
>> 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/81c2228a-2c2a-4cff-acb4-fd737d70c018o%40googlegroups.com.

[tw5] Re: Preview: keyboard driven draggable bullets

2020-06-10 Thread Reet Pandher



> Yay, It worked. It worked when I followed the steps you mentioned, but not 
> when I had dragged just the plugin and had refreshed the wiki.
>

FYI plugin won't update via drag and drop if the version is either same or 
lower than the current one. You'll need to delete the existing one and then 
drag and drop the new one.

-- 
You received this message because you are subscribed to the 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/b4447585-9d85-44c5-8f38-a1f1b7e796e5o%40googlegroups.com.

[tw5] Re: Preview: keyboard driven draggable bullets

2020-06-10 Thread Raghu Veer S

It worked when I followed the steps you mentioned, but not when I had 
dragged just the plugin and had refreshed the wiki.
If you don't mind, may I know what exactly caused it to behave that way, so 
that I can fix things on my own in future if needed

Btw, thanks a lot for the quick response. Really appreciate it :)

On Wednesday, June 10, 2020 at 3:49:30 PM UTC+5:30, Saq Imtiaz wrote:
>
> @Raghu are you sure you saved the new plugin and refreshed the wiki?
>
> If that still doesn't work:
> - place the following in a new tiddler: <>
> - save it and view that tiddler, click the tag pill.
> - drag *$:/plugins/sq/streams/stream-view-template* to make sure it is 
> immediately after *$:/core/ui/ViewTemplate/body*
>
> On Wednesday, June 10, 2020 at 12:00:27 PM UTC+2, Raghu Veer S wrote:
>>
>> Saq, It still shows up at the bottom of the tiddler. (just like in the 
>> previous image)
>>
>> On Wednesday, June 10, 2020 at 3:19:56 PM UTC+5:30, Saq Imtiaz wrote:
>>>
>>> @Raghu try grabbing the latest copy of the plugin, I just pushed a small 
>>> update that should resolve this.
>>>
>>> https://saqimtiaz.github.io/sq-tw/streams.html
>>>
>>>
>>>
>>>
>>> On Wednesday, June 10, 2020 at 11:30:07 AM UTC+2, Raghu Veer S wrote:

 Hi Saq,

 Really useful plugin. Thanks a lot.

 I ran into a issue while using the plugin with a theme that I am using. 
 I am using a theme called Krystal with TiddlyBlink, the problem is the 
 bullets are showing up after the backlink/reference sections instead of 
 showing up inside the tiddler body. I know this is probably a issue on the 
 side of the theme, but how do I position the bullets inside the tiddler 
 body? 


 *See the attached image for reference: *

 On Wednesday, June 10, 2020 at 2:14:47 AM UTC+5:30, Saq Imtiaz wrote:
>
> https://saqimtiaz.github.io/sq-tw/streams.html
>
> Not many outward differences, but I've cleaned up the code a fair bit 
> and the *field names are now stable*. Which means that if you 
> starting using it now, you should be able to upgrade to newer versions 
> without much trouble. So I have removed the warning about not using this. 
>
> One step closer to a beta release.
>
> Prompted by @pmario mention of *mindmaps* etc, on a whim I've added 
> the TidGraph plugin and you can see what that would look like here:
> https://saqimtiaz.github.io/sq-tw/streams.html#Roadmap%20-%20graph
>
> Please let me know:
>
>- if you find any bugs, there have been a lot of code changes so 
>something may have crept in
>- if there is more documentation that you think is needed before a 
>beta release. (Any help with documentation would be most appreciated)
>
> 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/9f85969f-f900-4d30-8ec7-30a1843ccadao%40googlegroups.com.

[tw5] Re: Preview: keyboard driven draggable bullets

2020-06-10 Thread Saq Imtiaz

@Raghu are you sure you saved the new plugin and refreshed the wiki?

If that still doesn't work:
- place the following in a new tiddler: <>
- save it and view that tiddler, click the tag pill.
- drag *$:/plugins/sq/streams/stream-view-template* to make sure it is 
immediately after *$:/core/ui/ViewTemplate/body*

On Wednesday, June 10, 2020 at 12:00:27 PM UTC+2, Raghu Veer S wrote:
>
> Saq, It still shows up at the bottom of the tiddler. (just like in the 
> previous image)
>
> On Wednesday, June 10, 2020 at 3:19:56 PM UTC+5:30, Saq Imtiaz wrote:
>>
>> @Raghu try grabbing the latest copy of the plugin, I just pushed a small 
>> update that should resolve this.
>>
>> https://saqimtiaz.github.io/sq-tw/streams.html
>>
>>
>>
>>
>> On Wednesday, June 10, 2020 at 11:30:07 AM UTC+2, Raghu Veer S wrote:
>>>
>>> Hi Saq,
>>>
>>> Really useful plugin. Thanks a lot.
>>>
>>> I ran into a issue while using the plugin with a theme that I am using. 
>>> I am using a theme called Krystal with TiddlyBlink, the problem is the 
>>> bullets are showing up after the backlink/reference sections instead of 
>>> showing up inside the tiddler body. I know this is probably a issue on the 
>>> side of the theme, but how do I position the bullets inside the tiddler 
>>> body? 
>>>
>>>
>>> *See the attached image for reference: *
>>>
>>> On Wednesday, June 10, 2020 at 2:14:47 AM UTC+5:30, Saq Imtiaz wrote:

 https://saqimtiaz.github.io/sq-tw/streams.html

 Not many outward differences, but I've cleaned up the code a fair bit 
 and the *field names are now stable*. Which means that if you starting 
 using it now, you should be able to upgrade to newer versions without much 
 trouble. So I have removed the warning about not using this. 

 One step closer to a beta release.

 Prompted by @pmario mention of *mindmaps* etc, on a whim I've added 
 the TidGraph plugin and you can see what that would look like here:
 https://saqimtiaz.github.io/sq-tw/streams.html#Roadmap%20-%20graph

 Please let me know:

- if you find any bugs, there have been a lot of code changes so 
something may have crept in
- if there is more documentation that you think is needed before a 
beta release. (Any help with documentation would be most appreciated)

 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/e729fa2f-1458-496d-b745-99a017c5b921o%40googlegroups.com.

[tw5] Re: Preview: keyboard driven draggable bullets

2020-06-10 Thread Raghu Veer S

Saq, It still shows up at the bottom of the tiddler. (just like in the 
previous image)

On Wednesday, June 10, 2020 at 3:19:56 PM UTC+5:30, Saq Imtiaz wrote:
>
> @Raghu try grabbing the latest copy of the plugin, I just pushed a small 
> update that should resolve this.
>
> https://saqimtiaz.github.io/sq-tw/streams.html
>
>
>
>
> On Wednesday, June 10, 2020 at 11:30:07 AM UTC+2, Raghu Veer S wrote:
>>
>> Hi Saq,
>>
>> Really useful plugin. Thanks a lot.
>>
>> I ran into a issue while using the plugin with a theme that I am using. I 
>> am using a theme called Krystal with TiddlyBlink, the problem is the 
>> bullets are showing up after the backlink/reference sections instead of 
>> showing up inside the tiddler body. I know this is probably a issue on the 
>> side of the theme, but how do I position the bullets inside the tiddler 
>> body? 
>>
>>
>> *See the attached image for reference: *
>>
>> On Wednesday, June 10, 2020 at 2:14:47 AM UTC+5:30, Saq Imtiaz wrote:
>>>
>>> https://saqimtiaz.github.io/sq-tw/streams.html
>>>
>>> Not many outward differences, but I've cleaned up the code a fair bit 
>>> and the *field names are now stable*. Which means that if you starting 
>>> using it now, you should be able to upgrade to newer versions without much 
>>> trouble. So I have removed the warning about not using this. 
>>>
>>> One step closer to a beta release.
>>>
>>> Prompted by @pmario mention of *mindmaps* etc, on a whim I've added the 
>>> TidGraph plugin and you can see what that would look like here:
>>> https://saqimtiaz.github.io/sq-tw/streams.html#Roadmap%20-%20graph
>>>
>>> Please let me know:
>>>
>>>- if you find any bugs, there have been a lot of code changes so 
>>>something may have crept in
>>>- if there is more documentation that you think is needed before a 
>>>beta release. (Any help with documentation would be most appreciated)
>>>
>>> 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/d2ee0eeb-cec5-444d-822f-6781849b2df4o%40googlegroups.com.

[tw5] Re: Preview: keyboard driven draggable bullets

2020-06-10 Thread Saq Imtiaz

@Raghu try grabbing the latest copy of the plugin, I just pushed a small 
update that should resolve this.

https://saqimtiaz.github.io/sq-tw/streams.html




On Wednesday, June 10, 2020 at 11:30:07 AM UTC+2, Raghu Veer S wrote:
>
> Hi Saq,
>
> Really useful plugin. Thanks a lot.
>
> I ran into a issue while using the plugin with a theme that I am using. I 
> am using a theme called Krystal with TiddlyBlink, the problem is the 
> bullets are showing up after the backlink/reference sections instead of 
> showing up inside the tiddler body. I know this is probably a issue on the 
> side of the theme, but how do I position the bullets inside the tiddler 
> body? 
>
>
> *See the attached image for reference: *
>
> On Wednesday, June 10, 2020 at 2:14:47 AM UTC+5:30, Saq Imtiaz wrote:
>>
>> https://saqimtiaz.github.io/sq-tw/streams.html
>>
>> Not many outward differences, but I've cleaned up the code a fair bit and 
>> the *field names are now stable*. Which means that if you starting using 
>> it now, you should be able to upgrade to newer versions without much 
>> trouble. So I have removed the warning about not using this. 
>>
>> One step closer to a beta release.
>>
>> Prompted by @pmario mention of *mindmaps* etc, on a whim I've added the 
>> TidGraph plugin and you can see what that would look like here:
>> https://saqimtiaz.github.io/sq-tw/streams.html#Roadmap%20-%20graph
>>
>> Please let me know:
>>
>>- if you find any bugs, there have been a lot of code changes so 
>>something may have crept in
>>- if there is more documentation that you think is needed before a 
>>beta release. (Any help with documentation would be most appreciated)
>>
>> 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/3ec850b7-e63c-49b0-8a64-54f1bbedc752o%40googlegroups.com.

[tw5] Re: Preview: keyboard driven draggable bullets

2020-06-10 Thread Raghu Veer S

Hi Saq,

Really useful plugin. Thanks a lot.

I ran into a issue while using the plugin with a theme that I am using. I 
am using a theme called Krystal with TiddlyBlink, the problem is the 
bullets are showing up after the backlink/reference sections instead of 
showing up inside the tiddler body. I know this is probably a issue on the 
side of the theme, but how do I position the bullets inside the tiddler 
body? 


*See the attached image for reference: *

On Wednesday, June 10, 2020 at 2:14:47 AM UTC+5:30, Saq Imtiaz wrote:
>
> https://saqimtiaz.github.io/sq-tw/streams.html
>
> Not many outward differences, but I've cleaned up the code a fair bit and 
> the *field names are now stable*. Which means that if you starting using 
> it now, you should be able to upgrade to newer versions without much 
> trouble. So I have removed the warning about not using this. 
>
> One step closer to a beta release.
>
> Prompted by @pmario mention of *mindmaps* etc, on a whim I've added the 
> TidGraph plugin and you can see what that would look like here:
> https://saqimtiaz.github.io/sq-tw/streams.html#Roadmap%20-%20graph
>
> Please let me know:
>
>- if you find any bugs, there have been a lot of code changes so 
>something may have crept in
>- if there is more documentation that you think is needed before a 
>beta release. (Any help with documentation would be most appreciated)
>
> 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/c1de76f0-50db-494f-ad76-0db08adef187o%40googlegroups.com.

[tw5] Re: Preview: keyboard driven draggable bullets

2020-06-09 Thread Saq Imtiaz

https://saqimtiaz.github.io/sq-tw/streams.html

Not many outward differences, but I've cleaned up the code a fair bit and 
the *field names are now stable*. Which means that if you starting using it 
now, you should be able to upgrade to newer versions without much trouble. 
So I have removed the warning about not using this. 

One step closer to a beta release.

Prompted by @pmario mention of *mindmaps* etc, on a whim I've added the 
TidGraph plugin and you can see what that would look like here:
https://saqimtiaz.github.io/sq-tw/streams.html#Roadmap%20-%20graph

Please let me know:

   - if you find any bugs, there have been a lot of code changes so 
   something may have crept in
   - if there is more documentation that you think is needed before a beta 
   release. (Any help with documentation would be most appreciated)

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/d1b2086d-a1a5-455c-875e-703005c77067o%40googlegroups.com.

[tw5] Re: Preview: keyboard driven draggable bullets

2020-06-07 Thread Reet Pandher

Thanks for this Saq. But as someone who had requested for that feature i feel 
like you have already solved the renaming problem with the Alt+R shortcut and 
I'd like to say your implementation is most definitely better and cleaner.

-- 
You received this message because you are subscribed to the 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/86774952-9f3c-45df-9c2b-846dfd0d1443o%40googlegroups.com.

[tw5] Re: Preview: keyboard driven draggable bullets

2020-06-06 Thread Saq Imtiaz

One of the things I would like to emphasize is that, the entire workflow of 
Streams is built on fields and wikitext and re-usable widgets. There is no 
blackbox logic that is obscured from the user.

So don't be too hesitant to dive in and try to tweak/adapt things to your 
liking.

For example, there have been a few requests for the first line of text to 
be the title of new tiddlers. This can't currently be done as you type, but 
it would be easy to do so after the fact. It is no different from 
manipulating a bunch of tiddlers.

This code, placed in the demo, will create a button that renames all the 
child tiddlers of Roadmap, to use the first line of text as their titles.

\define rename-children()
<$list filter="[enlist{!!sq-bullets}]">
<>

<$wikify name="new-title" text={{{ 
[get[text]split[\n]first[]] }}}>
<$list filter="[!is[blank]]" variable="_NULL">
<$action-sendmessage $message="tm-rename-tiddler" from=<> 
to=<>/>


\end

<$set name="currentTiddler" value="Roadmap">
<$button>rename Roadmap
<$list filter="[has[sq-bullets]]">
<$list variable="count" filter="[enlist{!!sq-bullets}count[]!match[0]]">
<>





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/b840c4c7-79b5-45c2-845d-ad0bffee2f3bo%40googlegroups.com.

[tw5] Re: Preview: keyboard driven draggable bullets

2020-06-05 Thread TonyM

Saq,

In a reply here I mention stream(s) as a layer to support images "In the 
future" https://groups.google.com/d/msg/tiddlywiki/ipCEDNmrjJk/J8-GqTdMBQAJ

Regards
Tony

On Saturday, June 6, 2020 at 1:40:53 AM UTC+10, Saq Imtiaz wrote:
>
> The problem is one of implementation. Currently there is no clean and 
> flexible way of doing so.
>
> On Friday, June 5, 2020 at 5:36:13 PM UTC+2, SizzlinSJ wrote:
>>
>> Double click feels right so there are no accidental edits
>> I do like Reet's suggestion, 
>>
>>> Once we click outside the edit area it should close the edit area. It 
>>> would feel more natural. 
>>
>>

-- 
You received this message because you are subscribed to the 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/10e35878-5cf3-44be-abfc-22a7383aa26ao%40googlegroups.com.

[tw5] Re: Preview: keyboard driven draggable bullets

2020-06-05 Thread Saq Imtiaz

The problem is one of implementation. Currently there is no clean and 
flexible way of doing so.

On Friday, June 5, 2020 at 5:36:13 PM UTC+2, SizzlinSJ wrote:
>
> Double click feels right so there are no accidental edits
> I do like Reet's suggestion, 
>
>> Once we click outside the edit area it should close the edit area. It 
>> would feel more natural. 
>
>

-- 
You received this message because you are subscribed to the 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/5e7620f5-e274-4c7e-814b-4ea887a463c1o%40googlegroups.com.

[tw5] Re: Preview: keyboard driven draggable bullets

2020-06-05 Thread SizzlinSJ

Double click feels right so there are no accidental edits
I do like Reet's suggestion, 

> Once we click outside the edit area it should close the edit area. It 
> would feel more natural. 

-- 
You received this message because you are subscribed to the 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/aa24fb60-02e6-4b90-b076-be3491e416c3o%40googlegroups.com.

[tw5] Re: Preview: keyboard driven draggable bullets

2020-06-05 Thread OGNSYA

@Saq, it's an amazing plug-in! It does open many possibilities. I'll share 
my ideas about that independently in the future, as you suggested.

PS: I agree with both @Reets suggestions below!

On Friday, June 5, 2020 at 12:59:17 PM UTC+1, Reet Pandher wrote:
>
> This feels more natural and better. The previous version wouldn't let me 
> click the github link in the roadmap tiddler, it would just enter the edit 
> area.
>
>
> Also, small suggestions: 
> 1. I feel like visually it would look better to have a single line (maybe 
> spanning the complete tiddler?) show up instead of double when we create a 
> bullet.
> 2. Once we click outside the edit area it should close the edit area. It 
> would feel more natural.
>
> Thanks
>
> On Friday, June 5, 2020 at 4:17:23 PM UTC+5:30, Saq Imtiaz wrote:
>>
>> For evaluation: a version that requires double click to edit:
>>
>> https://saqimtiaz.github.io/sq-tw/bullets-dblclick.html
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/3a310085-a984-49c6-ba6f-24c08e35b32co%40googlegroups.com.

[tw5] Re: Preview: keyboard driven draggable bullets

2020-06-05 Thread Reet Pandher

This feels more natural and better. The previous version wouldn't let me 
click the github link in the roadmap tiddler, it would just enter the edit 
area.

Also, small suggestions: 
1. I feel like visually it would look better to have a single line (maybe 
spanning the complete tiddler?) show up instead of double when we create a 
bullet.
2. Once we click outside the edit area it should close the edit area. It 
would feel more natural.

Thanks

On Friday, June 5, 2020 at 4:17:23 PM UTC+5:30, Saq Imtiaz wrote:
>
> For evaluation: a version that requires double click to edit:
>
> https://saqimtiaz.github.io/sq-tw/bullets-dblclick.html
>

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/eda30db9-87a4-491e-87d1-5b60d5173889o%40googlegroups.com.

[tw5] Re: Preview: keyboard driven draggable bullets

2020-06-05 Thread Saq Imtiaz

For evaluation: a version that requires double click to edit:

https://saqimtiaz.github.io/sq-tw/bullets-dblclick.html

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

[tw5] Re: Preview: keyboard driven draggable bullets

2020-06-05 Thread PMario

On Thursday, June 4, 2020 at 3:51:32 PM UTC+2, Saq Imtiaz wrote:
>
> @pmario does the screenshot below illustrate what you refer to?
>

yes.

I did click the area and saw what happens. But at the moment I don't have 
an idea, how to solve the problem. 

May be disabling "bullet-list" wikitext identifier in the settings.  
That doesn't need any changes from your side.

Or define * at the beginning of the line as the "split regexp" ...

-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/8bb31f39-96b8-4d54-a123-7fa20eefccc9o%40googlegroups.com.

[tw5] Re: Preview: keyboard driven draggable bullets

2020-06-05 Thread Saq Imtiaz

Some small updates:
- changed shortcut for deleting a tiddler from Delete to Ctrl+Delete
- changed styling of "bullet" to distinguish it from regular unordered lists
- expanded the area in which you can right click to access the context menu

-- 
You received this message because you are subscribed to the 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/214dbf63-a5e9-4126-87ba-5bca5e842a19o%40googlegroups.com.

Re: [tw5] Re: Preview: keyboard driven draggable bullets

amen, Saq. Don't let anyone get you distracted, even me! I think we all
agree we love your original vision, and that we want to respect the limits
you have on your involvement. It's just that this kind of advance gets
one's imagination going wild, trying to see the possibilities. So just
'receive the feedback as data' but stay your own course.




On Thu, Jun 4, 2020 at 3:25 PM Saq Imtiaz  wrote:

> A point of clarification in response to some of the comments here, and
> some private messages I have received:
>
> Firstly, this is not an attempt at creating a WYSIWYG editor or mitigating
> the lack of one.
>
> I see the value in two areas:
> a) quickly and conveniently creating and manipulating a hierarchy of
> tiddlers (and let's not forget that a tiddler is far more than just its
> text field).
> b) writing in a way that allows you to uphold the Philosophy of Tiddlers
> but in a way that doesn't interrupt the flow of writing.
>
> For those wanting a WYSIWYG editor, your best bet at the moment is
> probably trying to get Prose Mirror working in TW and using Markdown.
>
> Primarily, this is about me sharing with the community the concept and
> technique behind a keyboard driven approach to a tiddler hierarchy, which I
> have been using myself for a couple of years. I will be very happy if
> others learn from it and spin off their own solutions. In fact I highly
> encourage you to do so, and will be happy to offer guidance if necessary.
> To be honest, it is pretty simple and there is nothing groundbreaking about
> it.
>
> I have also been questioned about my reluctance to release plugins and
> develop things further. For the record this isn't about not wanting to
> contribute to the community. Rather, I am being realistic about the level
> of involvement I will be able to maintain long term, given my other
> commitments.
>
> Cheers,
> Saq
>
> --
> 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/KeVDndcnY0g/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/5f697963-54c8-46da-8f0a-ad847f973ee1o%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/CANE%3DBFK-2Nf8xbRy%3D2w8gwintj%2B1g253h0%3DFJ25N_hi1heyoQQ%40mail.gmail.com.

[tw5] Re: Preview: keyboard driven draggable bullets

A point of clarification in response to some of the comments here, and some
private messages I have received:

Firstly, this is not an attempt at creating a WYSIWYG editor or mitigating
the lack of one.

I see the value in two areas:
a) quickly and conveniently creating and manipulating a hierarchy of
tiddlers (and let's not forget that a tiddler is far more than just its
text field).
b) writing in a way that allows you to uphold the Philosophy of Tiddlers
but in a way that doesn't interrupt the flow of writing.

For those wanting a WYSIWYG editor, your best bet at the moment is probably
trying to get Prose Mirror working in TW and using Markdown.

Primarily, this is about me sharing with the community the concept and
technique behind a keyboard driven approach to a tiddler hierarchy, which I
have been using myself for a couple of years. I will be very happy if
others learn from it and spin off their own solutions. In fact I highly
encourage you to do so, and will be happy to offer guidance if necessary.
To be honest, it is pretty simple and there is nothing groundbreaking about
it.

I have also been questioned about my reluctance to release plugins and
develop things further. For the record this isn't about not wanting to
contribute to the community. Rather, I am being realistic about the level
of involvement I will be able to maintain long term, given my other
commitments.

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/5f697963-54c8-46da-8f0a-ad847f973ee1o%40googlegroups.com.

Re: [tw5] Re: Preview: keyboard driven draggable bullets

2020-06-04 Thread OGNSYA

@Saq: Would be great to be able to simply click Create New Stream, and then 
just start typing (ie., the cursor would already be in place in the first 
tiddler).

There could be a text (in light grey) saying "Start typing..." there, just 
to prompt the user.

This new Stream tiddler could look completely empty to the user - 
practically a white box (except for the aforementioned prompt).

Hovering on it with the mouse would reveal the menus, as well as info such 
as date, time etc.
---
Like I mentioned before, this newly created Stream tiddler wouldn't even 
need to have a title (ie., a big text on top). If the user wants, they add 
it (as a tiddler in the stream; it would be one of the types). A tiddler's 
unique name (a property currently called "title" within TW) would always 
exist, and could be dynamically defined based on whatever makes more sense.

On Thursday, June 4, 2020 at 3:18:27 PM UTC+1, Saq Imtiaz wrote:
>
> @David: what would be the workflow?
>
> - a button to create a new stream tiddler
> - user clicks button
> - tiddler opens in edit mode, user gives it a title and saves
> - then the user sees the UI for streams?
>
> That's where I was early on in development and it is as simple as a button 
> with an action widget, but I find that user story to not be very compelling 
> or user friendly. Starting in edit mode, there is a realistic expectation 
> to be able to start writing your content. If we start in view mode, then 
> the user has to edit the tiddler later to rename it. 
>
> There is no reason why this can't be an alternative workflow that we 
> offer, but I welcome any suggestions that would make it more intuitive.
>
> Overall, the question of how the user gets started with a new "stream 
> tiddler" is one that I am not totally satisfied that we have a good answer 
> for yet.
> The options discussed:
> - via view template with a configurable filter
> - a new tiddler type (basically based on a field) via a button
> - a macro that users type into a tiddler where they want the streams 
> interface.
>
> Cheers,
> Saq
>
> On Thursday, June 4, 2020 at 3:47:41 PM UTC+2, David Gifford wrote:
>>
>> With regard to limiting to certain tiddlers, have you thought about 
>> creating this as a new tiddler type?
>>
>>
>>
>>
>> On Thu, Jun 4, 2020 at 8:43 AM Saq Imtiaz  wrote:
>>
>>>
>>>
>>> On Thursday, June 4, 2020 at 1:16:09 PM UTC+2, Tony K wrote:

 Saq once again this is wonderful

 is there an easy way to have it only on some tiddlers ? maybe a widget 
 <$bulletTiddler /> or something similar

>>>
>>> You can try 
>>> {{||$:/plugins/sq/bullets/bullet-list-template}} 
>>>
>>> I am not the biggest fan of having to add text to a tiddler body to 
>>> trigger the UI, so I haven't put a lot of thought in that direction. This 
>>> could easily be wrapped in an easier to type macro though. <>
>>>
>>> Also there is a filter you can use to control on which tiddlers the UI 
>>> to add bullets appears.
>>> $:/config/sq/bullets/bullet-enable-filter
>>>
>>> -- 
>>> 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/KeVDndcnY0g/unsubscribe.
>>> To unsubscribe from this group and all its topics, send an email to 
>>> tiddl...@googlegroups.com.
>>> To view this discussion on the web visit 
>>> https://groups.google.com/d/msgid/tiddlywiki/279a024d-a805-4fce-a75f-7419c225b141%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/33deeb6f-f7f5-48cc-af51-37bda284656f%40googlegroups.com.

Re: [tw5] Re: Preview: keyboard driven draggable bullets

Sorry to be unclear. Setting aside the idea of special tiddler types and
assuming all tiddlers have stream, I was referring to every new tiddler
button calling up a dialog to title the tiddler and create it in view mode.

And about tiddler types l was just indicating that it was a throwaway
comment on behalf of the other person's comment, not something I want or
have thought about. I understood the tone of your comment. Blessings.

On Thu, Jun 4, 2020, 9:52 AM Saq Imtiaz  wrote:

> @David to be clear, I didn't mean to come across as critical. It is a good
> question and a valid suggestion. I was just hoping you may have thought of
> something I hadn't in terms of streamlining it, since I have banged my head
> against this for a while now.
>
> One of the issues with a button to create a new streams tiddler is that
> surely there will be requests to turn an existing tiddler into a streams
> tiddler too... and I really don't want to go down the road of yet more
> tiddler toolbar buttons.
>
> I will continue to give it some thought. Please do keep suggestions coming.
>
> On Thursday, June 4, 2020 at 4:33:14 PM UTC+2, David Gifford wrote:
>>
>> Hi Saq
>>
>> Yeah, I am not invested in the tiddler type idea, just throwing it out as
>> a possible answer to the other person's question.
>>
>> Addressing what you mentioned: There are two basic ways to create a new
>> tiddler:
>>
>> 1. From a link, which opens it in view mode with a title. In this
>> scenario, the user can just jump in and write.
>> 2. From a new button, which opens it in edit mode without a title, and
>> creates the understandable temptation for the user to start writing in edit
>> mode.
>>
>> I see two possible options, maybe there are more, for getting around #2.
>>
>> 1. Some kind of hint in the edit template text  area: "Title your
>> tiddler, save changes, and start writing in view mode" Drawback: the eye
>> either overlooks and/or eventually gets used to the hint and forgets it.
>> But hopefully by then the habit has become ingrained.
>> 2. A dialogue box when hitting a new button: a place to title the
>> tiddler, and a 'create' button that creates the tiddler in view mode with
>> the title. Drawback: tiring for regular users to have to do an extra step
>> for every new tiddler. Possible workaround: a way for users to turn that
>> off.
>>
>>
>>
>>
>> On Thu, Jun 4, 2020 at 9:18 AM Saq Imtiaz  wrote:
>>
>>> @David: what would be the workflow?
>>>
>>> - a button to create a new stream tiddler
>>> - user clicks button
>>> - tiddler opens in edit mode, user gives it a title and saves
>>> - then the user sees the UI for streams?
>>>
>>> That's where I was early on in development and it is as simple as a
>>> button with an action widget, but I find that user story to not be very
>>> compelling or user friendly. Starting in edit mode, there is a realistic
>>> expectation to be able to start writing your content. If we start in view
>>> mode, then the user has to edit the tiddler later to rename it.
>>>
>>> There is no reason why this can't be an alternative workflow that we
>>> offer, but I welcome any suggestions that would make it more intuitive.
>>>
>>> Overall, the question of how the user gets started with a new "stream
>>> tiddler" is one that I am not totally satisfied that we have a good answer
>>> for yet.
>>> The options discussed:
>>> - via view template with a configurable filter
>>> - a new tiddler type (basically based on a field) via a button
>>> - a macro that users type into a tiddler where they want the streams
>>> interface.
>>>
>>> Cheers,
>>> Saq
>>>
>>> On Thursday, June 4, 2020 at 3:47:41 PM UTC+2, David Gifford wrote:

 With regard to limiting to certain tiddlers, have you thought about
 creating this as a new tiddler type?




 On Thu, Jun 4, 2020 at 8:43 AM Saq Imtiaz  wrote:

>
>
> On Thursday, June 4, 2020 at 1:16:09 PM UTC+2, Tony K wrote:
>>
>> Saq once again this is wonderful
>>
>> is there an easy way to have it only on some tiddlers ? maybe a
>> widget <$bulletTiddler /> or something similar
>>
>
> You can try
> {{||$:/plugins/sq/bullets/bullet-list-template}}
>
> I am not the biggest fan of having to add text to a tiddler body to
> trigger the UI, so I haven't put a lot of thought in that direction. This
> could easily be wrapped in an easier to type macro though. <>
>
> Also there is a filter you can use to control on which tiddlers the UI
> to add bullets appears.
> $:/config/sq/bullets/bullet-enable-filter
>
> --
> 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/KeVDndcnY0g/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> tiddl...@googlegroups.com.
> To view this discussion on the web

[tw5] Re: Preview: keyboard driven draggable bullets

2020-06-04 Thread OGNSYA


On Thursday, June 4, 2020 at 3:09:20 PM UTC+1, Saq Imtiaz wrote:
>
> @Ognsya thanks for the feedback, comments below:
>
>
>>- I wonder if an abandoned empty tiddler should be removed/deleted 
>>automatically? Would make it cleaner.
>>
>> Hitting "escape" in an empty tiddler already deletes it. Beyond that I 
> prefer to err on the side of not deleting data, too much room for 
> accidents. 
>

I understand. It's definitely not priority. It would just be a way to give 
non-keyboard users the same flexibility as keyboard users (allowing the 
user to change their mind after starting a new tiddler, but before writing 
anything). Currently you have ESC delete the tiddler only if it's empty (to 
make sure you're not deleting important stuff). So would be a similar 
check, but done once focus leaves the text field.
 

>
>>- There is no way to drag a child left (equivalent of SHIFT-TAB). In 
>>order to do that via dragging, one needs to move it elsewhere, then bring 
>>it back.
>>
>> There is, you need to drag it to the left and below its siblings. Which 
> is not the exact same behaviour as shift+tab granted, but what one 
> intuitively expects when dragging and dropping. A literal equivalent to tab 
> and shift-tab (indent and unindent) would need to be via the context menu.
>

You're right. Sorry for that. What I suggested makes no sense, unless in 
very specific use cases.
 

>  
>
>>
>>- The drag handle could be more noticeable. I suggest a subtle 
>>vertical handle, to the left of the tiddler (and with its height). It 
>> could 
>>be even hidden until user hovers over the tiddler.
>>
>> Agreed that the styling on the handle needs to change, especially as it 
> is identical to a regular unordered list. I welcome any design suggestions 
> that could be implemented either via css or free svg icons. The current 
> bullet is pure css/html.  
>

Cool. I'll suggest something in my mock-ups. Having a common universal 
handle also opens up the possibility for tiddlers of other types in a 
Stream (besides bullets), such as plain paragraph ones. I pasted in the end 
of this email examples from Wordpress and Notion (in both, I have the mouse 
on the handle - it doesn't show in the screenshot).


>>- The context menu for a tiddler is great. I'd suggest having it show 
>>on hover of the aforementioned handle (after a short delay), instead of 
>> on 
>>Right-Click
>>
>> I would consider that a usability regression, elements popping up close 
> to user content on hover often get in the way. I do agree though that the 
> drag handle needs some kind of on hover affordance that it has other 
> functionality to explore.
>

Yes, that's what I meant - some hover options for the handle (such as 
changing the tiddler's type, for example).
 

>  
>
>> Some suggestions for making editing feel more fluid and modern:
>>
>
> I appreciate all of these thoughts but the reality is that in order to be 
> implemented properly, they would require a WYSIWYG editor for wiki text, 
> which does not exist and is a far more significant and complex undertaking 
> than this plugin. If such an editor is created, it can easily be utilized 
> in this plugin.
>

I was thinking about this visual BJtools editor:
http://bjtools.tiddlyspot.com/#VisualEditorDemo

Is there any reason it can't be used?
 

> For your other ideas regarding TW UI, I suggest starting a new thread. It 
> may help to differentiate between ideas for a hard fork or rewrite of 
> TiddlyWiki, and improvements to the current product. The former offers more 
> flexibility but also considerably more effort to realize (if at all), 
> whereas the latter will require design suggestions to be informed by and 
> accompanied by a willingness to learn and understand the basic architecture 
> of TW in order to be truly useful. If in doubt, just ask.
>

Sure, makes sense! Once I have the mockups I'll share them in a new post.

Thanks! 


> Regards,
> 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/4f541305-20d9-4cb7-831e-3a3a923dc5b5%40googlegroups.com.

Re: [tw5] Re: Preview: keyboard driven draggable bullets

@David to be clear, I didn't mean to come across as critical. It is a good 
question and a valid suggestion. I was just hoping you may have thought of 
something I hadn't in terms of streamlining it, since I have banged my head 
against this for a while now.

One of the issues with a button to create a new streams tiddler is that 
surely there will be requests to turn an existing tiddler into a streams 
tiddler too... and I really don't want to go down the road of yet more 
tiddler toolbar buttons.

I will continue to give it some thought. Please do keep suggestions coming.

On Thursday, June 4, 2020 at 4:33:14 PM UTC+2, David Gifford wrote:
>
> Hi Saq
>
> Yeah, I am not invested in the tiddler type idea, just throwing it out as 
> a possible answer to the other person's question.
>
> Addressing what you mentioned: There are two basic ways to create a new 
> tiddler:
>
> 1. From a link, which opens it in view mode with a title. In this 
> scenario, the user can just jump in and write.
> 2. From a new button, which opens it in edit mode without a title, and 
> creates the understandable temptation for the user to start writing in edit 
> mode.
>
> I see two possible options, maybe there are more, for getting around #2.
>
> 1. Some kind of hint in the edit template text  area: "Title your tiddler, 
> save changes, and start writing in view mode" Drawback: the eye either 
> overlooks and/or eventually gets used to the hint and forgets it. But 
> hopefully by then the habit has become ingrained.
> 2. A dialogue box when hitting a new button: a place to title the tiddler, 
> and a 'create' button that creates the tiddler in view mode with the title. 
> Drawback: tiring for regular users to have to do an extra step for every 
> new tiddler. Possible workaround: a way for users to turn that off.
>
>
>
>
> On Thu, Jun 4, 2020 at 9:18 AM Saq Imtiaz > 
> wrote:
>
>> @David: what would be the workflow?
>>
>> - a button to create a new stream tiddler
>> - user clicks button
>> - tiddler opens in edit mode, user gives it a title and saves
>> - then the user sees the UI for streams?
>>
>> That's where I was early on in development and it is as simple as a 
>> button with an action widget, but I find that user story to not be very 
>> compelling or user friendly. Starting in edit mode, there is a realistic 
>> expectation to be able to start writing your content. If we start in view 
>> mode, then the user has to edit the tiddler later to rename it. 
>>
>> There is no reason why this can't be an alternative workflow that we 
>> offer, but I welcome any suggestions that would make it more intuitive.
>>
>> Overall, the question of how the user gets started with a new "stream 
>> tiddler" is one that I am not totally satisfied that we have a good answer 
>> for yet.
>> The options discussed:
>> - via view template with a configurable filter
>> - a new tiddler type (basically based on a field) via a button
>> - a macro that users type into a tiddler where they want the streams 
>> interface.
>>
>> Cheers,
>> Saq
>>
>> On Thursday, June 4, 2020 at 3:47:41 PM UTC+2, David Gifford wrote:
>>>
>>> With regard to limiting to certain tiddlers, have you thought about 
>>> creating this as a new tiddler type?
>>>
>>>
>>>
>>>
>>> On Thu, Jun 4, 2020 at 8:43 AM Saq Imtiaz  wrote:
>>>


 On Thursday, June 4, 2020 at 1:16:09 PM UTC+2, Tony K wrote:
>
> Saq once again this is wonderful
>
> is there an easy way to have it only on some tiddlers ? maybe a widget 
> <$bulletTiddler /> or something similar
>

 You can try 
 {{||$:/plugins/sq/bullets/bullet-list-template}} 

 I am not the biggest fan of having to add text to a tiddler body to 
 trigger the UI, so I haven't put a lot of thought in that direction. This 
 could easily be wrapped in an easier to type macro though. <>

 Also there is a filter you can use to control on which tiddlers the UI 
 to add bullets appears.
 $:/config/sq/bullets/bullet-enable-filter

 -- 
 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/KeVDndcnY0g/unsubscribe.
 To unsubscribe from this group and all its topics, send an email to 
 tiddl...@googlegroups.com.
 To view this discussion on the web visit 
 https://groups.google.com/d/msgid/tiddlywiki/279a024d-a805-4fce-a75f-7419c225b141%40googlegroups.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/KeVDndcnY0g/unsubscribe.
>> To unsubscribe from this group and all its topics, send an

Re: [tw5] Re: Preview: keyboard driven draggable bullets

Hi Saq

Yeah, I am not invested in the tiddler type idea, just throwing it out as a
possible answer to the other person's question.

Addressing what you mentioned: There are two basic ways to create a new
tiddler:

1. From a link, which opens it in view mode with a title. In this scenario,
the user can just jump in and write.
2. From a new button, which opens it in edit mode without a title, and
creates the understandable temptation for the user to start writing in edit
mode.

I see two possible options, maybe there are more, for getting around #2.

1. Some kind of hint in the edit template text  area: "Title your tiddler,
save changes, and start writing in view mode" Drawback: the eye either
overlooks and/or eventually gets used to the hint and forgets it. But
hopefully by then the habit has become ingrained.
2. A dialogue box when hitting a new button: a place to title the tiddler,
and a 'create' button that creates the tiddler in view mode with the title.
Drawback: tiring for regular users to have to do an extra step for every
new tiddler. Possible workaround: a way for users to turn that off.




On Thu, Jun 4, 2020 at 9:18 AM Saq Imtiaz  wrote:

> @David: what would be the workflow?
>
> - a button to create a new stream tiddler
> - user clicks button
> - tiddler opens in edit mode, user gives it a title and saves
> - then the user sees the UI for streams?
>
> That's where I was early on in development and it is as simple as a button
> with an action widget, but I find that user story to not be very compelling
> or user friendly. Starting in edit mode, there is a realistic expectation
> to be able to start writing your content. If we start in view mode, then
> the user has to edit the tiddler later to rename it.
>
> There is no reason why this can't be an alternative workflow that we
> offer, but I welcome any suggestions that would make it more intuitive.
>
> Overall, the question of how the user gets started with a new "stream
> tiddler" is one that I am not totally satisfied that we have a good answer
> for yet.
> The options discussed:
> - via view template with a configurable filter
> - a new tiddler type (basically based on a field) via a button
> - a macro that users type into a tiddler where they want the streams
> interface.
>
> Cheers,
> Saq
>
> On Thursday, June 4, 2020 at 3:47:41 PM UTC+2, David Gifford wrote:
>>
>> With regard to limiting to certain tiddlers, have you thought about
>> creating this as a new tiddler type?
>>
>>
>>
>>
>> On Thu, Jun 4, 2020 at 8:43 AM Saq Imtiaz  wrote:
>>
>>>
>>>
>>> On Thursday, June 4, 2020 at 1:16:09 PM UTC+2, Tony K wrote:

 Saq once again this is wonderful

 is there an easy way to have it only on some tiddlers ? maybe a widget
 <$bulletTiddler /> or something similar

>>>
>>> You can try
>>> {{||$:/plugins/sq/bullets/bullet-list-template}}
>>>
>>> I am not the biggest fan of having to add text to a tiddler body to
>>> trigger the UI, so I haven't put a lot of thought in that direction. This
>>> could easily be wrapped in an easier to type macro though. <>
>>>
>>> Also there is a filter you can use to control on which tiddlers the UI
>>> to add bullets appears.
>>> $:/config/sq/bullets/bullet-enable-filter
>>>
>>> --
>>> 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/KeVDndcnY0g/unsubscribe.
>>> To unsubscribe from this group and all its topics, send an email to
>>> tiddl...@googlegroups.com.
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/tiddlywiki/279a024d-a805-4fce-a75f-7419c225b141%40googlegroups.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/KeVDndcnY0g/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/c1589c4b-5efc-4344-a87d-cc269bbd6a7d%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/CANE%3DBFJ-xod%3D%2BpSPz1Xvum8A6Vo%3DuZ-Df0RnhUBgrvOYUoWPqg%40mail.gmail.com.

Re: [tw5] Re: Preview: keyboard driven draggable bullets

@David: what would be the workflow?

- a button to create a new stream tiddler
- user clicks button
- tiddler opens in edit mode, user gives it a title and saves
- then the user sees the UI for streams?

That's where I was early on in development and it is as simple as a button 
with an action widget, but I find that user story to not be very compelling 
or user friendly. Starting in edit mode, there is a realistic expectation 
to be able to start writing your content. If we start in view mode, then 
the user has to edit the tiddler later to rename it. 

There is no reason why this can't be an alternative workflow that we offer, 
but I welcome any suggestions that would make it more intuitive.

Overall, the question of how the user gets started with a new "stream 
tiddler" is one that I am not totally satisfied that we have a good answer 
for yet.
The options discussed:
- via view template with a configurable filter
- a new tiddler type (basically based on a field) via a button
- a macro that users type into a tiddler where they want the streams 
interface.

Cheers,
Saq

On Thursday, June 4, 2020 at 3:47:41 PM UTC+2, David Gifford wrote:
>
> With regard to limiting to certain tiddlers, have you thought about 
> creating this as a new tiddler type?
>
>
>
>
> On Thu, Jun 4, 2020 at 8:43 AM Saq Imtiaz > 
> wrote:
>
>>
>>
>> On Thursday, June 4, 2020 at 1:16:09 PM UTC+2, Tony K wrote:
>>>
>>> Saq once again this is wonderful
>>>
>>> is there an easy way to have it only on some tiddlers ? maybe a widget 
>>> <$bulletTiddler /> or something similar
>>>
>>
>> You can try 
>> {{||$:/plugins/sq/bullets/bullet-list-template}} 
>>
>> I am not the biggest fan of having to add text to a tiddler body to 
>> trigger the UI, so I haven't put a lot of thought in that direction. This 
>> could easily be wrapped in an easier to type macro though. <>
>>
>> Also there is a filter you can use to control on which tiddlers the UI to 
>> add bullets appears.
>> $:/config/sq/bullets/bullet-enable-filter
>>
>> -- 
>> 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/KeVDndcnY0g/unsubscribe.
>> To unsubscribe from this group and all its topics, send an email to 
>> tiddl...@googlegroups.com .
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/tiddlywiki/279a024d-a805-4fce-a75f-7419c225b141%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/c1589c4b-5efc-4344-a87d-cc269bbd6a7d%40googlegroups.com.

Re: [tw5] Re: Preview: keyboard driven draggable bullets

Just change it to a colored bullet. I nominate #56e.

On Thu, Jun 4, 2020 at 9:09 AM Saq Imtiaz  wrote:

> @Ognsya thanks for the feedback, comments below:
>
>
>>- I wonder if an abandoned empty tiddler should be removed/deleted
>>automatically? Would make it cleaner.
>>
>> Hitting "escape" in an empty tiddler already deletes it. Beyond that I
> prefer to err on the side of not deleting data, too much room for
> accidents.
>
>>
>>- There is no way to drag a child left (equivalent of SHIFT-TAB). In
>>order to do that via dragging, one needs to move it elsewhere, then bring
>>it back.
>>
>> There is, you need to drag it to the left and below its siblings. Which
> is not the exact same behaviour as shift+tab granted, but what one
> intuitively expects when dragging and dropping. A literal equivalent to tab
> and shift-tab (indent and unindent) would need to be via the context menu.
>
>
>>
>>- The drag handle could be more noticeable. I suggest a subtle
>>vertical handle, to the left of the tiddler (and with its height). It 
>> could
>>be even hidden until user hovers over the tiddler.
>>
>> Agreed that the styling on the handle needs to change, especially as it
> is identical to a regular unordered list. I welcome any design suggestions
> that could be implemented either via css or free svg icons. The current
> bullet is pure css/html.
>
>>
>>- The context menu for a tiddler is great. I'd suggest having it show
>>on hover of the aforementioned handle (after a short delay), instead of on
>>Right-Click
>>
>> I would consider that a usability regression, elements popping up close
> to user content on hover often get in the way. I do agree though that the
> drag handle needs some kind of on hover affordance that it has other
> functionality to explore.
>
>
>> Some suggestions for making editing feel more fluid and modern:
>>
>
> I appreciate all of these thoughts but the reality is that in order to be
> implemented properly, they would require a WYSIWYG editor for wiki text,
> which does not exist and is a far more significant and complex undertaking
> than this plugin. If such an editor is created, it can easily be utilized
> in this plugin.
>
> For your other ideas regarding TW UI, I suggest starting a new thread. It
> may help to differentiate between ideas for a hard fork or rewrite of
> TiddlyWiki, and improvements to the current product. The former offers more
> flexibility but also considerably more effort to realize (if at all),
> whereas the latter will require design suggestions to be informed by and
> accompanied by a willingness to learn and understand the basic architecture
> of TW in order to be truly useful. If in doubt, just ask.
>
> Regards,
> Saq
>
> --
> 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/KeVDndcnY0g/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/7da45eaa-fe87-4528-8954-01d179ff142b%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/CANE%3DBFKdLLwkmAoptBv%2Bze0x-BMJ3Yo-pgH%3DQWoLMLxa0koOuw%40mail.gmail.com.

[tw5] Re: Preview: keyboard driven draggable bullets

@Ognsya thanks for the feedback, comments below:


>- I wonder if an abandoned empty tiddler should be removed/deleted 
>automatically? Would make it cleaner.
>
> Hitting "escape" in an empty tiddler already deletes it. Beyond that I 
prefer to err on the side of not deleting data, too much room for 
accidents. 

>
>- There is no way to drag a child left (equivalent of SHIFT-TAB). In 
>order to do that via dragging, one needs to move it elsewhere, then bring 
>it back.
>
> There is, you need to drag it to the left and below its siblings. Which is 
not the exact same behaviour as shift+tab granted, but what one intuitively 
expects when dragging and dropping. A literal equivalent to tab and 
shift-tab (indent and unindent) would need to be via the context menu.
 

>
>- The drag handle could be more noticeable. I suggest a subtle 
>vertical handle, to the left of the tiddler (and with its height). It 
> could 
>be even hidden until user hovers over the tiddler.
>
> Agreed that the styling on the handle needs to change, especially as it is 
identical to a regular unordered list. I welcome any design suggestions 
that could be implemented either via css or free svg icons. The current 
bullet is pure css/html.  

>
>- The context menu for a tiddler is great. I'd suggest having it show 
>on hover of the aforementioned handle (after a short delay), instead of on 
>Right-Click
>
> I would consider that a usability regression, elements popping up close to 
user content on hover often get in the way. I do agree though that the drag 
handle needs some kind of on hover affordance that it has other 
functionality to explore.
 

> Some suggestions for making editing feel more fluid and modern:
>

I appreciate all of these thoughts but the reality is that in order to be 
implemented properly, they would require a WYSIWYG editor for wiki text, 
which does not exist and is a far more significant and complex undertaking 
than this plugin. If such an editor is created, it can easily be utilized 
in this plugin.

For your other ideas regarding TW UI, I suggest starting a new thread. It 
may help to differentiate between ideas for a hard fork or rewrite of 
TiddlyWiki, and improvements to the current product. The former offers more 
flexibility but also considerably more effort to realize (if at all), 
whereas the latter will require design suggestions to be informed by and 
accompanied by a willingness to learn and understand the basic architecture 
of TW in order to be truly useful. If in doubt, just ask.

Regards,
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/7da45eaa-fe87-4528-8954-01d179ff142b%40googlegroups.com.

[tw5] Re: Preview: keyboard driven draggable bullets

@pmario does the screenshot below illustrate what you refer to? I agree it 
looks odd. Two issues: a) its confusing whether its a draggable bullet or a 
regular one, (b) the extra padding/margins.

I am not sure if we should be tweaking content CSS though
 

>
>>- If the snipit contains "*" on multiple lines (using shift-enter) 
>>they display like any other bullet "Nice"
>>
>> ... But if used in an indented element, it looks strange.
>
>
[image: Capture.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/dcde6847-f2c3-498a-bb4f-1ef5d16c2485%40googlegroups.com.

Re: [tw5] Re: Preview: keyboard driven draggable bullets

With regard to limiting to certain tiddlers, have you thought about
creating this as a new tiddler type?




On Thu, Jun 4, 2020 at 8:43 AM Saq Imtiaz  wrote:

>
>
> On Thursday, June 4, 2020 at 1:16:09 PM UTC+2, Tony K wrote:
>>
>> Saq once again this is wonderful
>>
>> is there an easy way to have it only on some tiddlers ? maybe a widget
>> <$bulletTiddler /> or something similar
>>
>
> You can try
> {{||$:/plugins/sq/bullets/bullet-list-template}}
>
> I am not the biggest fan of having to add text to a tiddler body to
> trigger the UI, so I haven't put a lot of thought in that direction. This
> could easily be wrapped in an easier to type macro though. <>
>
> Also there is a filter you can use to control on which tiddlers the UI to
> add bullets appears.
> $:/config/sq/bullets/bullet-enable-filter
>
> --
> 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/KeVDndcnY0g/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/279a024d-a805-4fce-a75f-7419c225b141%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/CANE%3DBF%2B2cR7-6qmo_GJ6HZSrzXqbA92tohdS23giSdzMLH7d9A%40mail.gmail.com.

[tw5] Re: Preview: keyboard driven draggable bullets

On Thursday, June 4, 2020 at 1:16:09 PM UTC+2, Tony K wrote:
>
> Saq once again this is wonderful
>
> is there an easy way to have it only on some tiddlers ? maybe a widget 
> <$bulletTiddler /> or something similar
>

You can try 
{{||$:/plugins/sq/bullets/bullet-list-template}} 

I am not the biggest fan of having to add text to a tiddler body to trigger 
the UI, so I haven't put a lot of thought in that direction. This could 
easily be wrapped in an easier to type macro though. <>

Also there is a filter you can use to control on which tiddlers the UI to 
add bullets appears.
$:/config/sq/bullets/bullet-enable-filter

-- 
You received this message because you are subscribed to the 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/279a024d-a805-4fce-a75f-7419c225b141%40googlegroups.com.

[tw5] Re: Preview: keyboard driven draggable bullets

@TonyM:

>
>- The east of changing the regexp of what to split on suits me, simply 
>changing to /n in some cases, even ".\n\n" 
>- What if I wanted to split on html tag, eg "
> The suggested workflow here is that you decide how to split things as you 
type, by hitting enter. The plugin is geared towards writing, not 
manipulating text, and I would like to try to keep it as focused and 
streamlined as possible. This basic support for splitting paragraphs exists 
because I added it to quickly get data in there when testing, and then left 
it in as it works for copy and pasting in bullet points from a regular 
tiddler. 

If you need to perform any more advanced text manipulation, this is the 
wrong tool for it. 


>- There are some similarities with Noto Writer of Marks also in 
>development, they both have great value
>
> I noticed that thread and mentioned early on that he might be able to 
re-use a lot of my code.. but I understand that there is a certain amount 
of satisfaction to doing it yourself, and not that easy to work with 
someone else's code, especially wikitext. He may have wanted go about 
things differently in terms of architecture as well. Anyway, that would be 
the more appropriate tool for the splitting use cases you mentioned above.
 

>
>- There is no where to click to stop any item from being in edit mode, 
>noticeable with the edit Toolbar especially
>
> Valid point. I noticed but ignored it since I always use the keyboard and 
just hit Escape. I'm open to suggestions that don't involve cluttering the 
UI with buttons.
 

>
>- A new bullet alignment is wrong, it is a little above, if you 
>include only a transclusion 
>
> could you please explain step by step how to reproduce this, and also 
provide a screenshot? I tried to add a bullet with just a transclusion to 
another tiddler, and it displayed as expected.

Thank you,
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/9315a20d-33e6-41a0-ac77-499b0bc4281e%40googlegroups.com.

[tw5] Re: Preview: keyboard driven draggable bullets

@OGNSYA I appreciate the feedback and will reply properly later. However I 
recommend that you move everything related to: "*Having the option of 
Stream being the default mode of creating/editing tiddlers in TW" *a new 
thread/topic.

This will both prevent your ideas from getting buried in an already very 
long thread, and avoid derailing this thread.

Cheers,
Saq

On Thursday, June 4, 2020 at 2:05:03 PM UTC+2, OGNSYA wrote:
>
> Saq: This looks great! Love the name Streams btw.
>
> A few general notes:
>
>- I wonder if an abandoned empty tiddler should be removed/deleted 
>automatically? Would make it cleaner.
>- There is no way to drag a child left (equivalent of SHIFT-TAB). In 
>order to do that via dragging, one needs to move it elsewhere, then bring 
>it back.
>- The drag handle could be more noticeable. I suggest a subtle 
>vertical handle, to the left of the tiddler (and with its height). It 
> could 
>be even hidden until user hovers over the tiddler.
>- The context menu for a tiddler is great. I'd suggest having it show 
>on hover of the aforementioned handle (after a short delay), instead of on 
>Right-Click
>
> Some suggestions for making editing feel more fluid and modern:
>
>- Having the new tiddler be initially single line (instead of two 
>lines), thus disrupting the layout less
>- Hiding the tiddler's text border
>- Show the formatting toolbar as a hover instead, in a more 
>minimal/modern format, and only once the user selects some text (or 
>right-cilcks on text)
>- Having the editor be WYSIWYG, which might...
>   - ...help to avoid having the content shift/change when user starts 
>   editing it.
>   - ...allow editing to start in the actual place the user clicked on 
>   the text.
>- Allow user to end editing by "clicking out" of a tiddler (equivalent 
>to ESC).
>
> This is very exciting. As I mentioned previously, I'd suggest having this 
> as the default editing experience for TW. It makes creating/editing 
> tiddlers a much more Stream(*wink*)lined experience!
>
> I'm currently in the process of creating a few mockups to demonstrate what 
> I mean.
>
> I don't want to clutter this up with more of my ramblings. But I'll add 
> below a summary of my ideas, in case anyone is interested (if anyone has 
> feedback on that, would be helpful!)
>
> ---
>
> *Having the option of Stream being the default mode of creating/editing 
> tiddlers in TW*
> The main idea is that every new tiddler with more than a paragraph (or 
> block) automatically becomes a multi-tiddler, with the paragraph tiddlers 
> existing as subtiddlers (of course, there could be an override for this in 
> special cases, such as when a user definitely doesn't want every paragraph 
> to be a tiddler). 
>
> The "bullet tiddler" (which you currently have implemented) would be only 
> one of the many types of tiddler. The others would basically be all other 
> paragraph-level formatting options, such as normal paragraph (which I think 
> should be the default one), quote and headers (h1, h2 etc.).
>
> Headers would allow the same kind of structuring that the current 
> bullet-tiddlers implementation does (ie., moving an h1 header tiddler moves 
> everything below it which has a lower header etc.), except for the 
> indenting, of course. (Stream would still behave the same way it does now, 
> by making Bullet hierarchy have priority over Headers-based hierarchy - 
> ie., it would allow any bullet, in any hierarchy level, to have a Header 
> based structure within it). 
>
> All of this could happen seamlessly to the user. Hitting ENTER during 
> editing creates a new tiddler with a type defined by its previous tiddlers 
> -  For example: if editing a bullet or paragraph tiddlers, keep the type; 
> if editing a header tiddler, change to paragraph.  Changing tiddler type 
> could be done via the hover context menu of the tiddler, or a shortcut 
> (maybe ALT-LEFT/RIGHT could cycle between: quote, bullet, paragraph 
> (default), h1, h2 etc.).
>
> Note how in this system all paragraph-level formatting (paragraph, quote, 
> h1, h2 etc) would be done via the tiddler context menu, leaving much less 
> formatting options for the text-level hover context menu (bolding a word or 
> sentence, for example).
>
> The title of a tiddler (as a big text on top) would actually be optional 
> in this system. It could be added as a tiddler on top (with a Title type, 
> above h1). A unique identifier for tiddlers would still exist (of course), 
> and it could still be the the title. But in absence of a title, it could 
> default to first letters of the tiddler. (note this would allow tiddlers 
> with same Titles - as big text on top).
>
> I realize the above leads to some challenges regarding how TW 
> organizes/names tiddlers. The above is just a high-level description.
>
> But I think referencing/linking/transclusion could continue working as it 
> does.

[tw5] Re: Preview: keyboard driven draggable bullets

2020-06-04 Thread OGNSYA

Saq: This looks great! Love the name Streams btw.

A few general notes:

   - I wonder if an abandoned empty tiddler should be removed/deleted 
   automatically? Would make it cleaner.
   - There is no way to drag a child left (equivalent of SHIFT-TAB). In 
   order to do that via dragging, one needs to move it elsewhere, then bring 
   it back.
   - The drag handle could be more noticeable. I suggest a subtle vertical 
   handle, to the left of the tiddler (and with its height). It could be even 
   hidden until user hovers over the tiddler.
   - The context menu for a tiddler is great. I'd suggest having it show on 
   hover of the aforementioned handle (after a short delay), instead of on 
   Right-Click

Some suggestions for making editing feel more fluid and modern:

   - Having the new tiddler be initially single line (instead of two 
   lines), thus disrupting the layout less
   - Hiding the tiddler's text border
   - Show the formatting toolbar as a hover instead, in a more 
   minimal/modern format, and only once the user selects some text (or 
   right-cilcks on text)
   - Having the editor be WYSIWYG, which might...
  - ...help to avoid having the content shift/change when user starts 
  editing it.
  - ...allow editing to start in the actual place the user clicked on 
  the text.
   - Allow user to end editing by "clicking out" of a tiddler (equivalent 
   to ESC).

This is very exciting. As I mentioned previously, I'd suggest having this 
as the default editing experience for TW. It makes creating/editing 
tiddlers a much more Stream(*wink*)lined experience!

I'm currently in the process of creating a few mockups to demonstrate what 
I mean.

I don't want to clutter this up with more of my ramblings. But I'll add 
below a summary of my ideas, in case anyone is interested (if anyone has 
feedback on that, would be helpful!)

---

*Having the option of Stream being the default mode of creating/editing 
tiddlers in TW*
The main idea is that every new tiddler with more than a paragraph (or 
block) automatically becomes a multi-tiddler, with the paragraph tiddlers 
existing as subtiddlers (of course, there could be an override for this in 
special cases, such as when a user definitely doesn't want every paragraph 
to be a tiddler). 

The "bullet tiddler" (which you currently have implemented) would be only 
one of the many types of tiddler. The others would basically be all other 
paragraph-level formatting options, such as normal paragraph (which I think 
should be the default one), quote and headers (h1, h2 etc.).

Headers would allow the same kind of structuring that the current 
bullet-tiddlers implementation does (ie., moving an h1 header tiddler moves 
everything below it which has a lower header etc.), except for the 
indenting, of course. (Stream would still behave the same way it does now, 
by making Bullet hierarchy have priority over Headers-based hierarchy - 
ie., it would allow any bullet, in any hierarchy level, to have a Header 
based structure within it). 

All of this could happen seamlessly to the user. Hitting ENTER during 
editing creates a new tiddler with a type defined by its previous tiddlers 
-  For example: if editing a bullet or paragraph tiddlers, keep the type; 
if editing a header tiddler, change to paragraph.  Changing tiddler type 
could be done via the hover context menu of the tiddler, or a shortcut 
(maybe ALT-LEFT/RIGHT could cycle between: quote, bullet, paragraph 
(default), h1, h2 etc.).

Note how in this system all paragraph-level formatting (paragraph, quote, 
h1, h2 etc) would be done via the tiddler context menu, leaving much less 
formatting options for the text-level hover context menu (bolding a word or 
sentence, for example).

The title of a tiddler (as a big text on top) would actually be optional in 
this system. It could be added as a tiddler on top (with a Title type, 
above h1). A unique identifier for tiddlers would still exist (of course), 
and it could still be the the title. But in absence of a title, it could 
default to first letters of the tiddler. (note this would allow tiddlers 
with same Titles - as big text on top).

I realize the above leads to some challenges regarding how TW 
organizes/names tiddlers. The above is just a high-level description.

But I think referencing/linking/transclusion could continue working as it 
does. Considering Hierarchy information is stored in a custom field, this 
doesn't mess with the tagging system. Only main difference (I think) would 
be that, whenever a tiddler is opened (or transcluded), they also bring in 
all of their subtiddlers.

That's what I have for now. As I mentioned, Im working on a mockup to make 
it easier to communicate all of this, so any feedback/ideas on that would 
be gretly appreciated! 

On Wednesday, June 3, 2020 at 5:56:39 PM UTC+1, Saq Imtiaz wrote:
>
> Updates:
>
>- Enabled keyboard shortcut keys for text formatting, like ctrl+b
>- Added a

[tw5] Re: Preview: keyboard driven draggable bullets