@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 <saq....@gmail.com <javascript:>>
> 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 <saq....@gmail.com> 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. <<streams>>
>>>>
>>>> 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
>>>>
>>>> <https://groups.google.com/d/msgid/tiddlywiki/279a024d-a805-4fce-a75f-7419c225b141%40googlegroups.com?utm_medium=email&utm_source=footer>
>>>> .
>>>>
>>> --
>> 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 <javascript:>.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/tiddlywiki/c1589c4b-5efc-4344-a87d-cc269bbd6a7d%40googlegroups.com
>>
>> <https://groups.google.com/d/msgid/tiddlywiki/c1589c4b-5efc-4344-a87d-cc269bbd6a7d%40googlegroups.com?utm_medium=email&utm_source=footer>
>> .
>>
>
--
You received this message because you are subscribed to the Google Groups
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/tiddlywiki/c6470e0f-ba98-4f5e-8506-9a044b230946%40googlegroups.com.
