date:20210519

I love Tiddlywiki because of its unique community!


On Thu, Jan 7, 2021 at 9:09 PM TiddlyTweeter 
wrote:

> Whether it is my Memex machine or a full Xememex I can't forget her.
>
> --
> 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/e1d79f56-05ef-48d2-8789-dd203ce51d93n%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/CAAV1gMCNAsMBU3_%3DcEYdTN5sFcZcYX8PCJZ1-f_RL8KB%3DWwxAw%40mail.gmail.com.

[tw5] Re: I love TiddlyWiki because...

2021-05-19 Thread Suzanne McHale

Also meant to add that the TW community is very helpful and friendly!

On Thursday, May 20, 2021 at 2:40:43 PM UTC+10 Suzanne McHale wrote:

> I have tried other wikis over the years, but TW is the one I keep coming 
> back to! I am not a programmer, but have managed to puzzle out a few 
> operations for my own use. Makes me feel a little accomplished. I do like 
> to use TW in its most basic and convenient format - a single file in the 
> browser - and hope it will remain usable like this for a long time yet.
>
> On Wednesday, May 19, 2021 at 6:05:11 PM UTC+10 bimlas wrote:
>
>> TiddlyWiki is the second most flexible format / tool after plain text, 
>> it’s like a self-contained Unix-like system.
>
>

-- 
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/aa51dca0-aefe-406d-a63b-d9c0976d6001n%40googlegroups.com.

[tw5] Re: I love TiddlyWiki because...

2021-05-19 Thread Suzanne McHale

I have tried other wikis over the years, but TW is the one I keep coming 
back to! I am not a programmer, but have managed to puzzle out a few 
operations for my own use. Makes me feel a little accomplished. I do like 
to use TW in its most basic and convenient format - a single file in the 
browser - and hope it will remain usable like this for a long time yet.

On Wednesday, May 19, 2021 at 6:05:11 PM UTC+10 bimlas wrote:

> TiddlyWiki is the second most flexible format / tool after plain text, 
> it’s like a self-contained Unix-like system.

-- 
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/40d548d0-22b3-4a74-94a0-c46513bbce70n%40googlegroups.com.

Re: [tw5] UX experiment - editor tools / autocomplete / Streams

Hi Saq,

This is very exciting! I also love the
https://github.com/Jermolene/TiddlyWiki5/pull/5699#issuecomment-844464079
(Drag and drop images in the editor to import and insert)
I think you are making an Smart Editor!

With curiosity I follow this!


Best wishes
Mohammad


On Wed, May 19, 2021 at 11:57 PM Saq Imtiaz  wrote:

> It's another round of an hour's worth of distracted conference call
> experiments from today.
>
> This is an idea I've had for quite some time in various contexts: a UX for
> triggering actions in Streams like converting a node into a "to do" item
> with a checkbox, an autocomplete solution for links to tiddlers etc.
>
> The menu is triggered by typing / which isn't very apparent in the video.
> The menu contents themselves are just re-using core UI components, as 60
> minutes only go so far. :)
>
> I'd like to pursue this if I can find the time. However if anyone feels
> inspired by the idea and wants to run with it that would be fantastic! At
> the heart of it all is the keyboard-driven-input macro.
>
> 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/bdbb3e36-114d-47c9-8371-3f403c09c854n%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/CAAV1gMAReTyurM08K%3DxXpvpH_QTuDxTkb5JJXRs6Y3xpAEy-hg%40mail.gmail.com.

Re: [tw5] Re: Shiraz 2.3.1 new update supports Node Explorer (bidirectional links)

On Thu, May 20, 2021 at 1:25 AM si  wrote:

> Great stuff, thanks Mohammad. I will have to spend some time playing with
> column templates to see how they work.
>
> Unrelated question: Is there a way to change the orientation of dynamic
> table? I.e. list the fields as rows instead of columns.
>
Yes! Thereis a solution by  pubmania   here: https://git
hub.com/kookma/TW-Shiraz/issues/8#issuecomment-652531084

[image: image.png]




> On Wednesday, 19 May 2021 at 19:43:32 UTC+1 Mohammad wrote:
>
>> A Node Explorer is a dynamic table that appears at the bottom of the
>> current tiddler, displaying links, backlinks and tagging of that
>> tiddler. This is based on the Zettelkasten method
>> recently implemented in
>> Tiddlywiki by Soren Bjornstad (see
>> https://zettelkasten.sorenbjornstad.com/)
>>
>> The new update of Shiraz 2.3.1 adds a new template to its collection of
>> dynamic table templates, let's use it for creating a Node Explorer to show
>> links/backlinks/tagging of current tiddler.
>> For details see
>> https://kookma.github.io/TW-Shiraz/#Tutorial%20Advanced%20Node%20Explorer
>> You can also use details/slider macro in Shiraz to hide the Node Explorer
>> on demand!
>>
>>
>> *Code and demo*
>>
>>
>>- Demo: https://kookma.github.io/TW-Shiraz
>>- Code: https://github.com/kookma/TW-Shiraz
>>
>>
>> It is highly recommended to backup your data before trying any new
>> plugin! Do it before installing shiraz.
>>
>>
>> If you like Shiraz star it at  https://github.com/kookma/TW-Shiraz
>>
>>
>> [image: img_174_chrome.png]
>>
> --
> You received this message because you are subscribed to the Google Groups
> "TiddlyWiki" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to tiddlywiki+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/tiddlywiki/54e5cbcc-b0d3-439a-af54-02e11055a704n%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/CAAV1gMCbGQx6XP4-AtHPviZAkVBMEvyZF0YQRK%3D8-rrgiS6bHw%40mail.gmail.com.

Re: [tw5] Re: UX experiment - editor tools / autocomplete / Streams

2021-05-19 Thread msameen99

This is amazing Saq, I was looking for a similar functionality to add a
title to a "list field" inside the current edited tiddler.
for example,  consider the "related-to" field, it'll be very useful while
editing a tiddler to quickly append a title related to it before loosing my
train of thoughts.
I think this function will be similar to your adding tags functionality.

I was  VERY excited while watching your video

On Thu, 20 May 2021, 00:23 TW Tones,  wrote:

> Saq,
>
> Looking at your demo does make me think of other text fields being enabled
> in the same way.
>
> However of more importance with your idea, in some ways, is like when
> using streams, when editing an item, having access to add tag or other
> actions can obviate the need to have buttons and other UI space consuming
> elements, whilst allowing information to be entered.
>
> The custom markup work with pmario is another way, we mush ensure they can
> work together.
>
> Could one cause the same to occur on existing text?
>
> Regards
> Tony
>
> On Thursday, 20 May 2021 at 05:30:55 UTC+10 Saq Imtiaz wrote:
>
>> Here is a Google drive hosted version of the video so you don't need to
>> download it:
>>
>>
>> https://drive.google.com/file/d/1ZuXRh3ZHF2tglGakaYq0gh4kBQDibB_m/view?usp=sharing
>>
>> On Wednesday, May 19, 2021 at 9:27:55 PM UTC+2 Saq Imtiaz wrote:
>>
>>> It's another round of an hour's worth of distracted conference call
>>> experiments from today.
>>>
>>> This is an idea I've had for quite some time in various contexts: a UX
>>> for triggering actions in Streams like converting a node into a "to do"
>>> item with a checkbox, an autocomplete solution for links to tiddlers etc.
>>>
>>> The menu is triggered by typing / which isn't very apparent in the
>>> video. The menu contents themselves are just re-using core UI components,
>>> as 60 minutes only go so far. :)
>>>
>>> I'd like to pursue this if I can find the time. However if anyone feels
>>> inspired by the idea and wants to run with it that would be fantastic! At
>>> the heart of it all is the keyboard-driven-input macro.
>>>
>>> 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/50990bf5-1c00-4e40-be9d-1e51e663b9abn%40googlegroups.com
> 
> .
>

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

[tw5] Re: [RFC] Sponsored development of tiddlywiki tools and solutions?

Sorry transclude as such  {{||$:/PSaT/images/color-swatch}} to apply to 
current tiddler.

On Thursday, 20 May 2021 at 11:15:09 UTC+10 TW Tones wrote:

> For example,
>
> Find attached a "SVG image" tiddler, import it
>
> Transclude it in your viewTemplate or tiddler and if the current tiddler 
> has a color value it will display a "swatch" of that color. The value in 
> the color field will be displayed on mouse over.
>
> To polish and publish this it would also have;
>
>- A button that works in the toolbars, and selective click to  pick 
>color
>- A button on which if you drop a color name or number it will update 
>the color field of the current tiddler
>- A Set of draggable named color swatches in a side bar tab
>
> Extended tools would allow the search and selection from thousands of 
> named colors.
>
>
>- Would you consider a donation to make this happen?
>- What accountability for donations would you expect?
>
>
> Regards
> Tones
> On Thursday, 20 May 2021 at 10:22:43 UTC+10 TW Tones wrote:
>
>> Folks,
>>
>> A lot of contributors here are deserving of reward for their efforts. As 
>> a result I do make one off or continuing patreon donations to a few in our 
>> community.
>>
>> The discussion of money can be difficult but I would like to hear your 
>> considered thoughts.
>>
>> In my own circumstances I am currently unemployed, If I take a full time 
>> job, I will have far less time for TiddlyWiki, although I hope to use it in 
>> my job.
>>
>> As you may be aware I already try and contribute a lot to the community 
>> and as a result of developing  super user or designer skills I have 
>> designed many tools and features for tiddlywiki. Basically I have a library 
>> of many dozens of tools, however I have not being able to justify the time 
>> to polish and publish them. Many of my tools are designed to fill gaps that 
>> arise, as I develop larger tiddlywiki solutions, mostly for my self.
>>
>> What I would like your feedback on both as users and developers is the 
>> possibility of some of us (especially myself) being able to attract some 
>> sponsorship to get the job done. Here are my thoughts;
>>
>>- Provide a patreon or similar channel for regular donations to 
>>sponsor my time producing such open source solutions.
>>- Provide a requests channel, so people can submit a request for a 
>>solution.
>>- Provide a list of tools you can choose to sponsor for earlier 
>>release through donations which also act as an upvote.
>>- Finally offer a private method to commission work.
>>
>> Given my belief in Open source I  would continue to contribute much for 
>> free, especially contributions to the forums. Any work funded by 
>> sponsorship or donations would be made freely available to the community. 
>> Only specific and private commissions may not, although components may be.
>>
>> *Some possible issues*
>> One issue for me is even if people value such a service to request or 
>> bring forward particular solutions, ultimately I will still need to depend 
>> on the generosity of others when I need help in the forums. I do still have 
>> a few areas of weakness. Whilst I can see circumstances when donations may 
>> permit me to commission others I don't expect this would be so common, 
>> unless my earnings are sufficient to cover this. Perhaps I can grant 
>> contributors credit in my own "shop" for thanks.
>>
>> Equity for people such as Jeremy and other developers needs to be 
>> addressed. Can we find a way to encourage more contributions to those such 
>> as Jeremy, Mario and Eric without the community becoming an "only if funded 
>> model". Of course if people are in a position to give their time freely we 
>> want to encourage this to continue.
>>
>> If I am going to do this I need to start in a hurry, so I do not want to 
>> add anything unnecessary to the "critical path" but perhaps we could have a 
>> shared "shop".
>>
>> Yours with trepidation and sincerity.
>> Tones
>>
>

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

[tw5] Re: [RFC] Sponsored development of tiddlywiki tools and solutions?

For example,

Find attached a "SVG image" tiddler, import it

Transclude it in your viewTemplate or tiddler and if the current tiddler 
has a color value it will display a "swatch" of that color. The value in 
the color field will be displayed on mouse over.

To polish and publish this it would also have;

   - A button that works in the toolbars, and selective click to  pick color
   - A button on which if you drop a color name or number it will update 
   the color field of the current tiddler
   - A Set of draggable named color swatches in a side bar tab

Extended tools would allow the search and selection from thousands of named 
colors.


   - Would you consider a donation to make this happen?
   - What accountability for donations would you expect?


Regards
Tones
On Thursday, 20 May 2021 at 10:22:43 UTC+10 TW Tones wrote:

> Folks,
>
> A lot of contributors here are deserving of reward for their efforts. As a 
> result I do make one off or continuing patreon donations to a few in our 
> community.
>
> The discussion of money can be difficult but I would like to hear your 
> considered thoughts.
>
> In my own circumstances I am currently unemployed, If I take a full time 
> job, I will have far less time for TiddlyWiki, although I hope to use it in 
> my job.
>
> As you may be aware I already try and contribute a lot to the community 
> and as a result of developing  super user or designer skills I have 
> designed many tools and features for tiddlywiki. Basically I have a library 
> of many dozens of tools, however I have not being able to justify the time 
> to polish and publish them. Many of my tools are designed to fill gaps that 
> arise, as I develop larger tiddlywiki solutions, mostly for my self.
>
> What I would like your feedback on both as users and developers is the 
> possibility of some of us (especially myself) being able to attract some 
> sponsorship to get the job done. Here are my thoughts;
>
>- Provide a patreon or similar channel for regular donations to 
>sponsor my time producing such open source solutions.
>- Provide a requests channel, so people can submit a request for a 
>solution.
>- Provide a list of tools you can choose to sponsor for earlier 
>release through donations which also act as an upvote.
>- Finally offer a private method to commission work.
>
> Given my belief in Open source I  would continue to contribute much for 
> free, especially contributions to the forums. Any work funded by 
> sponsorship or donations would be made freely available to the community. 
> Only specific and private commissions may not, although components may be.
>
> *Some possible issues*
> One issue for me is even if people value such a service to request or 
> bring forward particular solutions, ultimately I will still need to depend 
> on the generosity of others when I need help in the forums. I do still have 
> a few areas of weakness. Whilst I can see circumstances when donations may 
> permit me to commission others I don't expect this would be so common, 
> unless my earnings are sufficient to cover this. Perhaps I can grant 
> contributors credit in my own "shop" for thanks.
>
> Equity for people such as Jeremy and other developers needs to be 
> addressed. Can we find a way to encourage more contributions to those such 
> as Jeremy, Mario and Eric without the community becoming an "only if funded 
> model". Of course if people are in a position to give their time freely we 
> want to encourage this to continue.
>
> If I am going to do this I need to start in a hurry, so I do not want to 
> add anything unnecessary to the "critical path" but perhaps we could have a 
> shared "shop".
>
> Yours with trepidation and sincerity.
> Tones
>

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/1c6829fd-09a7-44af-b0fd-2b2922f511cen%40googlegroups.com.


color-swatch-svg.json
Description: application/json

[tw5] [RFC] Sponsored development of tiddlywiki tools and solutions?

Folks,

A lot of contributors here are deserving of reward for their efforts. As a
result I do make one off or continuing patreon donations to a few in our
community.

The discussion of money can be difficult but I would like to hear your
considered thoughts.

In my own circumstances I am currently unemployed, If I take a full time
job, I will have far less time for TiddlyWiki, although I hope to use it in
my job.

As you may be aware I already try and contribute a lot to the community and
as a result of developing super user or designer skills I have designed
many tools and features for tiddlywiki. Basically I have a library of many
dozens of tools, however I have not being able to justify the time to
polish and publish them. Many of my tools are designed to fill gaps that
arise, as I develop larger tiddlywiki solutions, mostly for my self.

What I would like your feedback on both as users and developers is the
possibility of some of us (especially myself) being able to attract some
sponsorship to get the job done. Here are my thoughts;

- Provide a patreon or similar channel for regular donations to sponsor
my time producing such open source solutions.
- Provide a requests channel, so people can submit a request for a
solution.
- Provide a list of tools you can choose to sponsor for earlier release
through donations which also act as an upvote.
- Finally offer a private method to commission work.

Given my belief in Open source I would continue to contribute much for
free, especially contributions to the forums. Any work funded by
sponsorship or donations would be made freely available to the community.
Only specific and private commissions may not, although components may be.

*Some possible issues*
One issue for me is even if people value such a service to request or bring
forward particular solutions, ultimately I will still need to depend on the
generosity of others when I need help in the forums. I do still have a few
areas of weakness. Whilst I can see circumstances when donations may permit
me to commission others I don't expect this would be so common, unless my
earnings are sufficient to cover this. Perhaps I can grant contributors
credit in my own "shop" for thanks.

Equity for people such as Jeremy and other developers needs to be
addressed. Can we find a way to encourage more contributions to those such
as Jeremy, Mario and Eric without the community becoming an "only if funded
model". Of course if people are in a position to give their time freely we
want to encourage this to continue.

If I am going to do this I need to start in a hurry, so I do not want to
add anything unnecessary to the "critical path" but perhaps we could have a
shared "shop".

Yours with trepidation and sincerity.
Tones

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

[tw5] Re: What's not good with many viewtemplates?

Mat,

As is often the case I think it depends on how you implement it. In one 
solution I built I had a dozen object different object-type tiddlers, and 
each of these had there own view and edit templates. However the view 
template only took the current tiddlers object-template field, obtained the 
object name and added a prefix eg $:/objects/viewTemplates/objectname and 
transcluded that.

Therefor the bulk of which was used to display the view template was only 
transcluded on demand.

I saw no performance issues.

Regards
Tones

On Wednesday, 19 May 2021 at 23:15:25 UTC+10 Mat wrote:

> I've heard cautions against using many viewtemplates, for performance 
> reasons.
>
> But what, *specifically*, causes the poorer performance from this?
>
> For example, it doesn't make sense that it would be to locate the 
> templates because it is still only one search trough *all *tiddlers 
> regardless if the filter finds one template or a hundred (...right?)
>
> So is it rather what the viewtemplate shows that can be a problem? E.g if 
> a viewtemplate has a lot of nested lists? ...but in that case, one such 
> viewtemplate could be worse than 10 simpler viewtemplates so it would not 
> warrant caution from using many viewtemplates *per se*.
>
> Or is the problem if there are *many open* tiddlers? Beacuse each of them 
> shows all viewtemplates? So it is "N open tiddlers" times "M number of 
> templates". But then the templates only deserves half the blame.
>
> Does the caution change when one uses "conditional viewtemplates", i.e 
> viewtemplates with a wrapping listwidget like
>   ... 
> ?
>
> In summary: What is the actual problem with many viewtemplates?
>
> Thanks!
>
> <:-)
>

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

Re: [tw5] [Help] Color them icons and buttons.

Heree is a simple example of how quickly coloring a button is confounded

\define colour() #f00
<$button>
addsuffix[;]] 
}}}>{{$:/core/images/spiral}}


in a tiddler tagged $:/tags/ViewToolbar all custom color is lost.

Tones

On Wednesday, 19 May 2021 at 22:58:25 UTC+10 TW Tones wrote:

> Jeremy,
>
> I am not sure how to achieve what I want from your tips, I will research 
> further.
>
> I want to define a button in a macro, then place that macro, including a 
> color name parameter in a tiddler, if that tiddler is tagged 
> *$:/tags/ViewToolbar* I can ensure the color is used.
>
> However it appears the process of putting a button into the viewTemplate 
> results in any such color being ignored.
>
> If makes sense to me if all buttons could have the following variables 
> that are used if available, a new hack?
>
>- color-filter - color the button according to the filter eg 
>[all[current]status[go]then[green]]
>- display-filter - only display the button if the filter returns any 
>result eg; [all[current]tag[todo]] 
>
> The idea of passing a display filter, allows conditional display of 
> buttons.
>
> Tones
>
> On Wednesday, 19 May 2021 at 22:15:07 UTC+10 Jeremy Ruston wrote:
>
>> Hi Tones
>>
>> I haven’t read the whole thread, but if you’re asking how to 
>> programmatically colour a button, in general you can use the style property 
>> to set a fill colour:
>>
>> \define colour() #f00
>>
>> addsuffix[;]] 
>> }}}>{{$:/core/images/spiral}}
>>
>> In the case of the editor toolbars, the icon is usually specified by an 
>> “icon” field that doesn’t allow a colour to be set. But if you set the 
>> “custom-icon” field to “yes”, then you can render the icon 
>> programmatically. See these two examples in the core:
>>
>>
>> https://github.com/Jermolene/TiddlyWiki5/blob/master/core/ui/EditorToolbar/editor-height.tid
>>
>>
>> https://github.com/Jermolene/TiddlyWiki5/blob/master/core/ui/EditorToolbar/preview.tid
>>
>> Best wishes
>>
>> Jeremy
>>
>>
>> On 18 May 2021, at 23:46, TW Tones  wrote:
>>
>> Álvaro,
>>
>> Thanks - I am now getting closer to a full understanding of this. In this 
>> case I have the color value available in a variable or field value, I 
>> wanted to find a way to pass the color to the button display 
>> "programaticaly".
>>
>>- It supports my suspicion that button css is not as hackable as you 
>>would expect from tiddlywiki, making this a harder than average to 
>>customise this aspect of the User Interface, while making use of the CSS 
>> to 
>>define a button in the view toolbar (and elsewhere)
>>
>>
>> Ideally the tiddlywiki designer can just supply a hex or named color, 
>> rather than a need to define a range of classes (colors).
>>
>> Perhaps there is an argument that the tiddlywiki toolbar buttons css need 
>> to be change to permit a programaticaly set color to be provided 
>> (optionally). 
>>
>> Álvaro, can you think of a way to open this to user customisation? I 
>> think it is important enough to consider some changes. 
>>
>> Regards
>> Tones
>>
>> On Wednesday, 19 May 2021 at 03:25:50 UTC+10 Álvaro wrote:
>>
>>> The svg has two styles, one the inherited fron inline style in span and 
>>> "direct rules" (*.tc-tiddler-controls button svg* ). When you apply 
>>> direct rules the inherited rules are gone (they are overwritten by 
>>> direct). You can see it in the inspector of your browser, "fill:red" is 
>>> strikethrough.
>>>
>>> You need add inline style in svg or add new class, for example in button.
>>> button.icon-blue svg{fill:blue;}
>>>
>>> and use it like
>>> ...
>>> <$button message="tm-add-tag" param="$tag$" tooltip="Toggle $tag$"  
>>> class="tc-btn-invisible icon-blue">
>>> <$transclude tiddler="$:/PSaT/check-tag/button/checked-icon" />
>>> 
>>> ...
>>>
>>> Then you don't need wikify and you have a reusable style for the icon in 
>>> buttons. You can change/add class dynamically to button like tiddlywiki 
>>> does with varible and filter in *$:/core/ui/ViewTemplate/title*
>>> El martes, 18 de mayo de 2021 a las 17:33:21 UTC+2, TW Tones escribió:
>>>
 Álvaro
 Thanks for you help

 So the fill in the css is forcing the button to  "fill: #cc;"

 The problem is I want to display it with a color provided to a macro 
 and use it instead. Meaning the button have multiple colors depending on 
 the value provided.

 This is the macro I want to display a colored button.

 \define check-tag-button(tag:"select" color:"blue" 
 display-filter:"[all[current]is[tiddler]]" )
 \whitespace trim
 <$list filter="$display-filter$" variable=display>
 <$wikify name=style text="""fill: $color$;""">
 <$fieldmangler>
<$list filter="[all[current]!tag[$tag$]]" variable=has-tag>
 <$button message="tm-add-tag" param="$tag$" tooltip="Toggle 
 $tag$"  class="tc-btn-invisible">
  > ><$transclude 
 tiddler="$:/PSaT/check-tag/button/unchecked-icon" />

[tw5] Re: UX experiment - editor tools / autocomplete / Streams

Saq,

Looking at your demo does make me think of other text fields being enabled 
in the same way.

However of more importance with your idea, in some ways, is like when using 
streams, when editing an item, having access to add tag or other actions 
can obviate the need to have buttons and other UI space consuming elements, 
whilst allowing information to be entered.

The custom markup work with pmario is another way, we mush ensure they can 
work together.

Could one cause the same to occur on existing text?

Regards
Tony

On Thursday, 20 May 2021 at 05:30:55 UTC+10 Saq Imtiaz wrote:

> Here is a Google drive hosted version of the video so you don't need to 
> download it:
>
>
> https://drive.google.com/file/d/1ZuXRh3ZHF2tglGakaYq0gh4kBQDibB_m/view?usp=sharing
>
> On Wednesday, May 19, 2021 at 9:27:55 PM UTC+2 Saq Imtiaz wrote:
>
>> It's another round of an hour's worth of distracted conference call 
>> experiments from today.
>>
>> This is an idea I've had for quite some time in various contexts: a UX 
>> for triggering actions in Streams like converting a node into a "to do" 
>> item with a checkbox, an autocomplete solution for links to tiddlers etc.
>>
>> The menu is triggered by typing / which isn't very apparent in the video. 
>> The menu contents themselves are just re-using core UI components, as 60 
>> minutes only go so far. :)
>>
>> I'd like to pursue this if I can find the time. However if anyone feels 
>> inspired by the idea and wants to run with it that would be fantastic! At 
>> the heart of it all is the keyboard-driven-input macro.
>>
>> 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/50990bf5-1c00-4e40-be9d-1e51e663b9abn%40googlegroups.com.

Re: [tw5] Re: German documentation / deutsche Dokumentation

2021-05-19 Thread PMario

Hi,
Was wir unbedingt noch erweitern müssen, sind die restlichen Filter 
Operatoren und wenn's geht die Beispiele.
Außerdem müssen wir und für Filter und die Widget Parameter etwas einfallen 
lassen, damit wir schnell erkennen können, wenn sich da etwas verändert 
hat. ... Ansonsten laufen die "Referenz Beschreibungen" schnell 
auseinander, was dann zu Problemen bei den Anwendern führt. 

Ich hab da schon eine Idee. 

-mario


-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/96ca0dec-1a02-4214-8519-dfe23969cd52n%40googlegroups.com.

Re: [tw5] Re: German documentation / deutsche Dokumentation

2021-05-19 Thread PMario

On Wednesday, May 19, 2021 at 9:37:43 PM UTC+2 f.brunsb...@gmail.com wrote:

super ich freu mich. Wegen deinen Anmerkungen hätte ich auch noch ein paar 
> Sätze.
> Mit den Links zu "*den englischen original Tiddlern*" meinst Du sicher 
> das wikidokulink-Macro oder? Das ist mir leider erst etwas spät eingefallen 
> sonst hättte ich das schon eher überall eingebaut, zumindest da wo es mir 
> wichtig erscheint.
>

Ja ... Ich hab das erst nach meinem post gesehen :) ... Ich dachte eher an 
die "tiddler info-section" unter dem Erweitert tab. ... Aber als "footer" 
gefällt es mir besser, da es viel mehr ins Auge springt. 

> Apropos spät, das mit den "$:/editions/tw5.com/macros" ist mir erst nach 
> dem Upgrade auf die aktuellste Version aufgefallen. Wie gesagt war das mit 
> dem Weitergeben gar nicht so gedacht :-)
>

Kein Problem. Ich hab's eingebaut. ... 

> Die viele der ursprünglichen Macro-Namen habe ich aber übernommen. Das 
> dürfte nicht so das Problem sein. 
> Außerdem bedeutet das ja nicht das Du alles machen sollst. Ich kann das ja 
> ebenso erledigen.
>

Ja wäre schön, wenn uns auch noch andere helfen!

> Meinen Danbo kannst Du gerne auf GitHub "verfügbar" machen. Brauchs Du 
> dafür irgend was von mir? 
>

Nein.

> Alternativ kann ich diesen auch auf Wikipedia bzw. auf Wikimedia.Commons 
> hochladen.
> Andererseits brauchen wir ja nicht zwangsläufig nicht dieses Bild und auch 
> mein dazugehöriges Macro war ja nur für den Eigenbedarf.
>

Kein Problem. .. 

> Die SVG's hast du bearbeitet? Wie? Womit? Ich habe die in Inkscape 
> erstellt und 'ne Weile rumprobiert bis es save angezeigt wurde.
>

:) .. Inkscape ist gut. Ich verwende "Speichern Unter : Optimiertes SVG" 
wenn ich für TW exportiere. Das entfernt dann viel XML overhead. 
https://jakearchibald.github.io/svgomg/ ... mit default Einstellungen, 
reicht meistens aus für 30-50% ... 
Dann noch mit VS-Code html - beautify ... damit man es wider lesen kann. :)

> Wie gesagt ich kann das auch so umbauen das es passt. Lass uns darüber 
> reden wie das aussehen soll. Ich möchte ungern weitermachen, wenn es danach 
> doch wieder umgebaut werden muss.
>

Die filter Operatoren gingen relative schnell. Ich musste nur den Tabellen 
"header" entfernen und das TW5-com operator-template aktivieren. Ging 
schneller als ich dachte. 

> Schöne Grüße Frank
>
> *PS: Ach und schreib kurz wenn es soweit ist.*
>

Was am meisten Zeit brauchte, ist die Tiddler in die richtigen 
Verzeichnisse zu verschieben. ... Ich hatte vergessen dass ein Import von 
einem File-Wiki keine Pfad-infos mit hat. ... Wird alles unter 
xxx/tiddlers/ gespeichert. 

Ich hab jetzt eine $:/config/FileSystemPaths Konfiguration erstellt, die 
die neuen Tiddler über "tags" besser sortieren sollte. ... Muss noch 
verbessert werden. Aber für den Start sollte es reichen. 

Welche OS verwendest Du? ... Ich kann eine Beschreibung oder ein Video 
zusammen stellen, das zeigt wie man mit nodejs und GitHub arbeiten kann. 
... Dann werden die neuen tiddler hoffentlich gleich im richtigen 
Verzeichnis erstellt. 

Habe eben einen "Draft PullRequest" erstellt. 
https://github.com/Jermolene/TiddlyWiki5/pull/5703 ... 495 files verändert. 
Echt gute Arbeit! ;)
Die neue Struktur ist hier zu sehen: 
https://github.com/pmario/TiddlyWiki5/tree/german-translation/editions/de-AT/tiddlers

-mario

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/77f30f24-eada-449f-9f89-51569b77a46en%40googlegroups.com.

[tw5] Re: UX experiment - editor tools / autocomplete / Streams

 

> Yes, that sounds spot-on! But your demo in this thread also has some form 
> of "at-caret-position" - is this some totally other implementation?
>

It is code from the beginnings of a PR to add this ability to the core. 
However, there is need to discuss some technical implementation details 
first 

 before 
I can proceed.

-- 
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/7c6e0274-7b85-4d24-b022-186b963d5d19n%40googlegroups.com.

[tw5] Re: UX experiment - editor tools / autocomplete / Streams

2021-05-19 Thread Mat

Saq Imtiaz wrote:

> Once we get this 
>  implemented 
> it will open up a lot of possibilities for exploration.
>

Yes, that sounds spot-on! But your demo in this thread also has some form 
of "at-caret-position" - is this some totally other implementation?
Hope you have a lot of boring conference calls ;-)

<:-)

-- 
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/55ce52d2-5492-44d7-994f-05b89b5edeadn%40googlegroups.com.

[tw5] Re: UX experiment - editor tools / autocomplete / Streams

@Matt definitely some similarities but somewhat different goals than 
EditorMagic.

EditorMagic was about guessing what the user was typing and trying to offer 
help to autocomplete that.
This prototype is about having a single shortcut to trigger a menu, which 
can be extended via tags etc, which offers different commands you can 
invoke. All usable via the keyboard alone, naturally.

Since the primary use case in my mind was Streams, for things like adding 
tags and converting to different node types,  this approach makes more 
sense since there wouldn't be anything to autocomplete. However I have 
spent all of one distracted hour on this, so if I do get to work on it 
further not sure what direction it will take. :) 

Once we get this  
implemented it will open up a lot of possibilities for exploration.

Cheers,
Saq

On Wednesday, May 19, 2021 at 10:41:02 PM UTC+2 Mat wrote:

> Oh cools stuff! You know I'm really excited about this (ref the 
> EditorMagic  thing we worked on some 
> months ago before TiddlySpot shut down). Does this version of yours allow 
> the user to add custom triggers for custom "popup-templates"?
>
> <:-)
>
> On Wednesday, May 19, 2021 at 9:30:55 PM UTC+2 Saq Imtiaz wrote:
>
>> Here is a Google drive hosted version of the video so you don't need to 
>> download it:
>>
>>
>> https://drive.google.com/file/d/1ZuXRh3ZHF2tglGakaYq0gh4kBQDibB_m/view?usp=sharing
>>
>> On Wednesday, May 19, 2021 at 9:27:55 PM UTC+2 Saq Imtiaz wrote:
>>
>>> It's another round of an hour's worth of distracted conference call 
>>> experiments from today.
>>>
>>> This is an idea I've had for quite some time in various contexts: a UX 
>>> for triggering actions in Streams like converting a node into a "to do" 
>>> item with a checkbox, an autocomplete solution for links to tiddlers etc.
>>>
>>> The menu is triggered by typing / which isn't very apparent in the 
>>> video. The menu contents themselves are just re-using core UI components, 
>>> as 60 minutes only go so far. :)
>>>
>>> I'd like to pursue this if I can find the time. However if anyone feels 
>>> inspired by the idea and wants to run with it that would be fantastic! At 
>>> the heart of it all is the keyboard-driven-input macro.
>>>
>>> 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/d05c21df-895c-4eb4-9274-7faba14225a4n%40googlegroups.com.

[tw5] Re: Shiraz 2.3.1 new update supports Node Explorer (bidirectional links)

2021-05-19 Thread si

Great stuff, thanks Mohammad. I will have to spend some time playing with 
column templates to see how they work.

Unrelated question: Is there a way to change the orientation of dynamic 
table? I.e. list the fields as rows instead of columns.

On Wednesday, 19 May 2021 at 19:43:32 UTC+1 Mohammad wrote:

> A Node Explorer is a dynamic table that appears at the bottom of the 
> current tiddler, displaying links, backlinks and tagging of that tiddler. 
> This is based on the Zettelkasten method  
> recently implemented in 
> Tiddlywiki by Soren Bjornstad (see 
> https://zettelkasten.sorenbjornstad.com/)
>
> The new update of Shiraz 2.3.1 adds a new template to its collection of 
> dynamic table templates, let's use it for creating a Node Explorer to show 
> links/backlinks/tagging of current tiddler.
> For details see 
> https://kookma.github.io/TW-Shiraz/#Tutorial%20Advanced%20Node%20Explorer
> You can also use details/slider macro in Shiraz to hide the Node Explorer 
> on demand!
>
>
> *Code and demo*
>
>
>- Demo: https://kookma.github.io/TW-Shiraz
>- Code: https://github.com/kookma/TW-Shiraz
>
>
> It is highly recommended to backup your data before trying any new plugin! 
> Do it before installing shiraz.
>
>
> If you like Shiraz star it at  https://github.com/kookma/TW-Shiraz
>
>
> [image: img_174_chrome.png]
>

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/54e5cbcc-b0d3-439a-af54-02e11055a704n%40googlegroups.com.

[tw5] Re: UX experiment - editor tools / autocomplete / Streams

2021-05-19 Thread Mat

Oh cools stuff! You know I'm really excited about this (ref the EditorMagic 
 thing we worked on some months ago 
before TiddlySpot shut down). Does this version of yours allow the user to 
add custom triggers for custom "popup-templates"?

<:-)

On Wednesday, May 19, 2021 at 9:30:55 PM UTC+2 Saq Imtiaz wrote:

> Here is a Google drive hosted version of the video so you don't need to 
> download it:
>
>
> https://drive.google.com/file/d/1ZuXRh3ZHF2tglGakaYq0gh4kBQDibB_m/view?usp=sharing
>
> On Wednesday, May 19, 2021 at 9:27:55 PM UTC+2 Saq Imtiaz wrote:
>
>> It's another round of an hour's worth of distracted conference call 
>> experiments from today.
>>
>> This is an idea I've had for quite some time in various contexts: a UX 
>> for triggering actions in Streams like converting a node into a "to do" 
>> item with a checkbox, an autocomplete solution for links to tiddlers etc.
>>
>> The menu is triggered by typing / which isn't very apparent in the video. 
>> The menu contents themselves are just re-using core UI components, as 60 
>> minutes only go so far. :)
>>
>> I'd like to pursue this if I can find the time. However if anyone feels 
>> inspired by the idea and wants to run with it that would be fantastic! At 
>> the heart of it all is the keyboard-driven-input macro.
>>
>> 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/49f44fc2-ad4e-434c-a760-d00e71b294dcn%40googlegroups.com.

Re: [tw5] Re: German documentation / deutsche Dokumentation

2021-05-19 Thread Frank Bruns-Ballhausen

Hi Mario,

super ich freu mich. Wegen deinen Anmerkungen hätte ich auch noch ein paar 
Sätze.
Mit den Links zu "*den englischen original Tiddlern*" meinst Du sicher das 
wikidokulink-Macro oder? Das ist mir leider erst etwas spät eingefallen 
sonst hättte ich das schon eher überall eingebaut, zumindest da wo es mir 
wichtig erscheint.
Apropos spät, das mit den "$:/editions/tw5.com/macros" ist mir erst nach 
dem Upgrade auf die aktuellste Version aufgefallen. Wie gesagt war das mit 
dem Weitergeben gar nicht so gedacht :-)
Die viele der ursprünglichen Macro-Namen habe ich aber übernommen. Das 
dürfte nicht so das Problem sein. 
Außerdem bedeutet das ja nicht das Du alles machen sollst. Ich kann das ja 
ebenso erledigen.

Meinen Danbo kannst Du gerne auf GitHub "verfügbar" machen. Brauchs Du 
dafür irgend was von mir? 
Alternativ kann ich diesen auch auf Wikipedia bzw. auf Wikimedia.Commons 
hochladen.
Andererseits brauchen wir ja nicht zwangsläufig nicht dieses Bild und auch 
mein dazugehöriges Macro war ja nur für den Eigenbedarf.

Die SVG's hast du bearbeitet? Wie? Womit? Ich habe die in Inkscape erstellt 
und 'ne Weile rumprobiert bis es save angezeigt wurde.

Wie gesagt ich kann das auch so umbauen das es passt. Lass uns darüber 
reden wie das aussehen soll. Ich möchte ungern weitermachen, wenn es danach 
doch wieder umgebaut werden muss.

Schöne Grüße Frank

*PS: Ach und schreib kurz wenn es soweit ist.*

PMario schrieb am Mittwoch, 19. Mai 2021 um 17:46:34 UTC+2:

> Hi Frank, 
> Ich habe die Übersetzung eben importiert und kurz "drüber geschaut". Ich 
> werde mir jetzt alles mal genauer ansehen. ... 
>
> Die $:/_fbb/ ... SVGs habe ich gestern schon überarbeitet. Sind jetzt 50% 
> kleiner. 
>
> Das -- Danboo0070.png --  Bild müssen wir über GitHub verfügbar machen. 
> ... Bilder usw können nicht über "3rd party server" eingebunden werden. Zum 
> einen aus Rechtlichen-, zum anderen aus Sicherheitsgründen. 
>
> Du hättest die $:/editions/tw5.com/macros von TW importieren sollen. ... 
> Wir müssen sämtliche Operator docs ändern. ... Da ging wahrscheinlich super 
> viel Zeit rein. .. Schade.
>
> Ich denke das Konzept muss das gleiche bleiben, sonst wird eine Wartung 
> unmöglich. Beim Arbeiten mit den Änderungen ist mir auch aufgefallen, dass 
> links zu den englischen original Tiddlern sehr praktisch wären. Wird die 
> Wartung auch vereinfachen. 
>
> Ich werde (hoffentlich heute noch) eine vorläufige Version online stellen. 
>
> -mario
>

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

[tw5] Re: UX experiment - editor tools / autocomplete / Streams

Here is a Google drive hosted version of the video so you don't need to 
download it:

https://drive.google.com/file/d/1ZuXRh3ZHF2tglGakaYq0gh4kBQDibB_m/view?usp=sharing

On Wednesday, May 19, 2021 at 9:27:55 PM UTC+2 Saq Imtiaz wrote:

> It's another round of an hour's worth of distracted conference call 
> experiments from today.
>
> This is an idea I've had for quite some time in various contexts: a UX for 
> triggering actions in Streams like converting a node into a "to do" item 
> with a checkbox, an autocomplete solution for links to tiddlers etc.
>
> The menu is triggered by typing / which isn't very apparent in the video. 
> The menu contents themselves are just re-using core UI components, as 60 
> minutes only go so far. :)
>
> I'd like to pursue this if I can find the time. However if anyone feels 
> inspired by the idea and wants to run with it that would be fantastic! At 
> the heart of it all is the keyboard-driven-input macro.
>
> 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/8394de5c-0932-45dd-bd7c-2f894fdde35dn%40googlegroups.com.

[tw5] UX experiment - editor tools / autocomplete / Streams

It's another round of an hour's worth of distracted conference call 
experiments from today.

This is an idea I've had for quite some time in various contexts: a UX for 
triggering actions in Streams like converting a node into a "to do" item 
with a checkbox, an autocomplete solution for links to tiddlers etc.

The menu is triggered by typing / which isn't very apparent in the video. 
The menu contents themselves are just re-using core UI components, as 60 
minutes only go so far. :)

I'd like to pursue this if I can find the time. However if anyone feels 
inspired by the idea and wants to run with it that would be fantastic! At 
the heart of it all is the keyboard-driven-input macro.

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/bdbb3e36-114d-47c9-8371-3f403c09c854n%40googlegroups.com.


backslash.mp4
Description: video/mp4

Re: [tw5] Re: Shiraz plugin new release 2.3.0

2021-05-19 Thread Mohammad

Hi Pall,
 See new update of Shiraz. It supports linktype using a new column template!

Please see
https://groups.google.com/g/tiddlywiki/c/EcgXtikbjTg/m/ijUbu8q_AQAJ

On Saturday, May 15, 2021 at 2:30:28 AM UTC+4:30 psigu...@gmail.com wrote:

> Thanks, I've been reading the tutorial. There is a lot to take in and I 
> keep returning to it. The details widget is not the only thing I'm using so 
> far. I've found alerts to be useful for various emphasis and examples. Then 
> I've also put the dynamic tables into use. I'm for example experimenting 
> with some kind of reference explorer similar to the one in Soren Bronstad's 
> Zettelkasten (recent thread in this group), only using the Shiraz plugin 
> instead of TiddlyTables. I've not gotten to where I want to be with it yet 
> - for example I haven't figured out if or how it would be possible to have 
> a separate column to show the type of link (forward link, backlink vs 
> tagging) so I'm right having three separate tables right now in my 
> ViewTemplate at the bottom. (I guess anyone reading this who hasn't checked 
> out Soren Bronstad's video "A walk through my Zettelkasten" will have no 
> idea what I'm talking about here.)
>
> On Fri, 14 May 2021, 18:16 Mohammad Rahmani,  
> wrote:
>
>> Hi Pall,
>> Many people are reluctant to use plugins. Except for two plugins in 
>> Kookma, all plugins in kookma library are pure wikitext and do not use JS.
>>
>>
>> Shiraz is one of most powerful and useful plugins here, mimicking 
>> Bootstrap 4, one the most common CSS framework in web design nowadays!
>> Shiraz has safe classes of Bootstrap 4. Using Shiraz in Tiddlywiki you 
>> can make elegant web apps, seb page, static page , ... 
>>
>> To get more familiar with Shiraz features see the 
>> https://kookma.github.io/TW-Shiraz/#Shiraz%20Tutorial
>>
>> Some examples useful to be read
>>
>> - dynamic tables (e.g 
>> https://kookma.github.io/TW-Shiraz/#Tutorial%20Dynamic%20Tables)
>> - list-search (e.g 
>> https://kookma.github.io/TW-Shiraz/#Tutorial%20List%20and%20Search)
>> - images (e.g https://kookma.github.io/TW-Shiraz/#demo%2Fimage-overlay 
>> or https://kookma.github.io/TW-Shiraz/#demo%2Fimage-polaroid)
>> - tables https://kookma.github.io/TW-Shiraz/#Tutorial%20Tabels
>> -  cards
>> - badges
>> - buttons
>> - multi column story river
>> - multi column tiddlers
>> - sticky footer
>> - color palette switch 
>> - ...
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> On Fri, May 14, 2021 at 6:43 PM Pall Sigurdsson  
>> wrote:
>>
>>> Hi Mohammad,
>>> I added this to my personal TiddlyWiki in version 2.2.2 and was 
>>> impressed. I'm usually reluctant to import "packages" like this, which 
>>> might contain a lot of stuff I end up not using, but then I guess I'm not 
>>> using everything that's in the core either. The more I explore Shiraz I'm 
>>> finding it more and more useful.
>>> I upgraded the plugin to 2.3.0 yesterday and I'm trying out the changing 
>>> "Details on Demand" now. Great addition! Immediately useful. Thanks!
>>> Best regards,
>>> Pall
>>>
>>> On Tuesday, May 11, 2021 at 10:30:08 AM UTC+2 Mohammad wrote:
>>>
 Shiraz plugin has just got a new update!

 Shiraz is a small framework of stylesheets, templates and macros to 
 create stylish contents in Tiddlywiki. Shiraz has customized elements 
 like alerts, cards, panels, images, static tables, dynamic tables, badges, 
 texts, etc. Shiraz uses some modified CSS classes from Bootstrap 4.3.1.

 Code and demo

- Demo: https://kookma.github.io/TW-Shiraz
- Code: https://github.com/kookma/TW-Shiraz

 *It is highly recommended to backup your data before trying any new 
 plugin! Do it before installing shiraz*.
 Revision 2.3.0


- Date: [10th May 2021]
- [NEW] Palette switch on the page controls
- [NEW] Setting for default light and dark (or dim) palette (see 
Sidebar More Tab, Shiraz)
- [NEW] Slider macro accepts tiddler title as source (src) and 
extracts the text automatically
- [NEW] Details macro accepts tiddler title as source (src) and 
extracts the text automatically
- [FIXED] small type in card-image macro



 If you like it star it at https://github.com/kookma/TW-Shiraz



 Best wishes
 Mohammad

>>> -- 
>>> You received this message because you are subscribed to the Google 
>>> Groups "TiddlyWiki" group.
>>> To unsubscribe from this group and stop receiving emails from it, send 
>>> an email to tiddlywiki+...@googlegroups.com.
>>> To view this discussion on the web visit 
>>> https://groups.google.com/d/msgid/tiddlywiki/e55216fc-bfdd-4f89-8faf-b3aa6e74923an%40googlegroups.com
>>>  
>>> 
>>> .
>>>
>> -- 
>>
> You received this message because you are subscribed to a topic in the 
>> Google Groups

[tw5] Shiraz 2.3.1 new update supports Node Explorer (bidirectional links)

A Node Explorer is a dynamic table that appears at the bottom of the
current tiddler, displaying links, backlinks and tagging of that tiddler.
This is based on the Zettelkasten method
recently implemented in Tiddlywiki
by Soren Bjornstad (see https://zettelkasten.sorenbjornstad.com/)

The new update of Shiraz 2.3.1 adds a new template to its collection of
dynamic table templates, let's use it for creating a Node Explorer to show
links/backlinks/tagging of current tiddler.
For details see
https://kookma.github.io/TW-Shiraz/#Tutorial%20Advanced%20Node%20Explorer
You can also use details/slider macro in Shiraz to hide the Node Explorer
on demand!


*Code and demo*


   - Demo: https://kookma.github.io/TW-Shiraz
   - Code: https://github.com/kookma/TW-Shiraz


It is highly recommended to backup your data before trying any new plugin!
Do it before installing shiraz.


If you like Shiraz star it at  https://github.com/kookma/TW-Shiraz


[image: img_174_chrome.png]

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

[tw5] Re: Is Markdown in TiddlyWiki customizable?

2021-05-19 Thread Pekka

Hi PMario,

I apologize for my inaccurate use of terminology. I actually tried googling 
the proper term specifically to get it right, but managed to mess it up 
nevertheless.

I will take your advice and avoid hard coding styles. Thank you for the tip 
and all the help!

>From the examples I have seen, I am impressed! I believe that making text 
look more appealing will provide a little dopamine hit, which encourages 
reading the notes more often and makes creating the notes more fun. The 
green, yellow and pink background colors seem particularly appealing to me. 

Pekka

On Tuesday, May 18, 2021 at 1:44:08 PM UTC+3 PMario wrote:

> On Tuesday, May 18, 2021 at 7:31:15 AM UTC+2 Pekka wrote:
>
> For example, if I would type: ++ Custom block of text ++, then the HTML 
>> output would be Custom block of 
>> text, or wrapped in any other HTML blocks I choose. 
>>
>
> A configuration like this isn't very future prove. Hardcodeing styles 
> like: Custom block of text 
> ... should be a absolute last resort, if there is no other way. .. It will 
> limit you in the future. Trust me!
>
> You should use: Custom block of text and 
> create a tiddler with your "custom-styles" which is tagged: 
> $:/tags/Stylesheet
>
> title: my-custom-styles
> tags: $:/tags/Stylesheet 
>
> .myClass {
>   background-color: #fff;
> }
>
> This is much more flexible, if you need to change the color in the future. 
> .. You only need to change 1 CSS tiddler instead of every tiddler which 
> contains the hardcoded code. ... Even if the custom-markup plugin is used. 
>
> Just a thought.
> -mario
>
>

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

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

2021-05-19 Thread clutterstack

This is a beautiful piece of work. I think it will make a difference.

Cheers,
Chris

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

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

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/314f3839-d19b-4157-bea9-16a60a84a4d2n%40googlegroups.com.

Re: [tw5] Re: German documentation / deutsche Dokumentation

2021-05-19 Thread PMario

Hi Frank, 
Ich habe die Übersetzung eben importiert und kurz "drüber geschaut". Ich 
werde mir jetzt alles mal genauer ansehen. ... 

Die $:/_fbb/ ... SVGs habe ich gestern schon überarbeitet. Sind jetzt 50% 
kleiner. 

Das -- Danboo0070.png --  Bild müssen wir über GitHub verfügbar machen. ... 
Bilder usw können nicht über "3rd party server" eingebunden werden. Zum 
einen aus Rechtlichen-, zum anderen aus Sicherheitsgründen. 

Du hättest die $:/editions/tw5.com/macros von TW importieren sollen. ... 
Wir müssen sämtliche Operator docs ändern. ... Da ging wahrscheinlich super 
viel Zeit rein. .. Schade.

Ich denke das Konzept muss das gleiche bleiben, sonst wird eine Wartung 
unmöglich. Beim Arbeiten mit den Änderungen ist mir auch aufgefallen, dass 
links zu den englischen original Tiddlern sehr praktisch wären. Wird die 
Wartung auch vereinfachen. 

Ich werde (hoffentlich heute noch) eine vorläufige Version online stellen. 

-mario

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

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

2021-05-19 Thread Cs Molnar

I've been waiting so much for this book to go live! I've had the 
announcement open in a browser tab and refreshed it several times a day. :-)

I'm still at the beginning but I noticed that the story river is set to 
zoomin mode by default. However, in this context it might be hard for 
newcomers to understand what do you mean by „open” and „closed” tiddlers. I 
think it might be hard for them to differentiate between tiddlers they 
don't see because they haven't opened them or they don't see because the 
zoomin mode has hidden them, although they are technically  „open”. To tell 
the truth, in zoomin mode it is pretty useless to look at the "open" tab in 
the sidebar. The tiddlers on this tab are „open” but I can't see them. So 
for me they are still „closed”.

Thank you for including an „Outline” tiddler and a conventional, 
hierarchical Table of Contents. The official Tiddlywiki homepage is in dire 
need of such a feature. I won't rant on about that here but, in short, I'm 
convinced that Tiddlywiki is not suited for documenting itself. Or, for 
that matter, any technical product (software, user manuals, etc.).

Finally, I'm not sure if it's only me, but the internal links have the same 
color as the body text. This way I can easily miss that a text contains a 
link.   

Gordon a következőt írta (2021. május 18., kedd, 17:02:40 UTC+2):

> It is absolutely terrific! I've been nibbling around the edges of TW for 
> some time and thinking: "This is neat, I can probably use it to...ahh...do 
> stuff." Then, a while back, I read an article about Zettelkasten and 
> thought it would be fun to do that in TW but saw your version and was just 
> a bit overwhelmed. I checked out various YouTube videos but kept thinking 
> that there must be a better way to get started, and — ta-da! — here it is. 
> Thanks so much. It's just the approach I needed.
>
> On Tuesday, May 18, 2021 at 7:24:03 AM UTC-5 ndar...@gmail.com wrote:
>
>> Wow, this is great! Thanks for writing it. I was a day or two away from 
>> popping on the list, asking about a book or guide, and saying that I really 
>> needed one because the existing documentation is very overwhelming. And, 
>> well, here it is. :)
>> On 5/16/2021 9:43 AM, Soren Bjornstad wrote:
>>
>> I'm excited to announce that the first public edition of my TiddlyWiki 
>> textbook, *Grok TiddlyWiki*, is live at https://groktiddlywiki.com/read. 
>> *Grok 
>> TiddlyWiki* is (from the book) “a textbook that helps you build a deep, 
>> lasting understanding of and proficiency with TiddlyWiki through a 
>> combination of detailed explanations, practical exercises, 
>> and spaced-repetition reviews of prompts called *takeaways*.”
>>
>> I am hoping this book will fill in many of the gaps in TiddlyWiki's 
>> documentation / learning ecosystem – right now we have lots of beginner 
>> tutorials, and mostly good documentation for experts (with a few gaps), but 
>> almost nothing for people in between. GTW is what I wished I had when I was 
>> in that position: complete lessons on the features and idioms of TiddlyWiki 
>> needed to bring someone from beginner to expert.
>>
>> The book is free to read and CC BY-NC-ND licensed (you can redistribute 
>> it for noncommercial purposes). I am accepting donations 
>>  to support my continued work on GTW 
>> and other TiddlyWiki learning resources. I would also appreciate your help 
>> spreading the word about the book, e.g., on TW links sites, notes-related 
>> resources, or social media.
>>
>> A huge thanks to everyone from this community who provided feedback on 
>> the prerelease (see the acknowledgments section for details). Barring me 
>> getting run over by a bus, there will be updated editions in the future, so 
>> please keep the feedback and suggestions coming. -- 
>>
>> You received this message because you are subscribed to the Google Groups 
>> "TiddlyWiki" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to tiddlywiki+...@googlegroups.com.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/tiddlywiki/f6b21644-9b9e-45eb-b5a4-eec4e929a00bn%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/46e7cec6-6aa6-4e60-8e13-fc60ed7d0876n%40googlegroups.com.

[tw5] What's not good with many viewtemplates?

2021-05-19 Thread Mat

I've heard cautions against using many viewtemplates, for performance 
reasons.

But what, *specifically*, causes the poorer performance from this?

For example, it doesn't make sense that it would be to locate the templates 
because it is still only one search trough *all *tiddlers regardless if the 
filter finds one template or a hundred (...right?)

So is it rather what the viewtemplate shows that can be a problem? E.g if a 
viewtemplate has a lot of nested lists? ...but in that case, one such 
viewtemplate could be worse than 10 simpler viewtemplates so it would not 
warrant caution from using many viewtemplates *per se*.

Or is the problem if there are *many open* tiddlers? Beacuse each of them 
shows all viewtemplates? So it is "N open tiddlers" times "M number of 
templates". But then the templates only deserves half the blame.

Does the caution change when one uses "conditional viewtemplates", i.e 
viewtemplates with a wrapping listwidget like
  ... 
?

In summary: What is the actual problem with many viewtemplates?

Thanks!

<:-)

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/01b6e9c3-fc69-4007-8124-73a377515b6fn%40googlegroups.com.

Re: [tw5] [Help] Color them icons and buttons.

Jeremy,

I am not sure how to achieve what I want from your tips, I will research 
further.

I want to define a button in a macro, then place that macro, including a 
color name parameter in a tiddler, if that tiddler is tagged 
*$:/tags/ViewToolbar* I can ensure the color is used.

However it appears the process of putting a button into the viewTemplate 
results in any such color being ignored.

If makes sense to me if all buttons could have the following variables that 
are used if available, a new hack?

   - color-filter - color the button according to the filter eg 
   [all[current]status[go]then[green]]
   - display-filter - only display the button if the filter returns any 
   result eg; [all[current]tag[todo]] 

The idea of passing a display filter, allows conditional display of buttons.

Tones

On Wednesday, 19 May 2021 at 22:15:07 UTC+10 Jeremy Ruston wrote:

> Hi Tones
>
> I haven’t read the whole thread, but if you’re asking how to 
> programmatically colour a button, in general you can use the style property 
> to set a fill colour:
>
> \define colour() #f00
>
> addsuffix[;]] 
> }}}>{{$:/core/images/spiral}}
>
> In the case of the editor toolbars, the icon is usually specified by an 
> “icon” field that doesn’t allow a colour to be set. But if you set the 
> “custom-icon” field to “yes”, then you can render the icon 
> programmatically. See these two examples in the core:
>
>
> https://github.com/Jermolene/TiddlyWiki5/blob/master/core/ui/EditorToolbar/editor-height.tid
>
>
> https://github.com/Jermolene/TiddlyWiki5/blob/master/core/ui/EditorToolbar/preview.tid
>
> Best wishes
>
> Jeremy
>
>
> On 18 May 2021, at 23:46, TW Tones  wrote:
>
> Álvaro,
>
> Thanks - I am now getting closer to a full understanding of this. In this 
> case I have the color value available in a variable or field value, I 
> wanted to find a way to pass the color to the button display 
> "programaticaly".
>
>- It supports my suspicion that button css is not as hackable as you 
>would expect from tiddlywiki, making this a harder than average to 
>customise this aspect of the User Interface, while making use of the CSS 
> to 
>define a button in the view toolbar (and elsewhere)
>
>
> Ideally the tiddlywiki designer can just supply a hex or named color, 
> rather than a need to define a range of classes (colors).
>
> Perhaps there is an argument that the tiddlywiki toolbar buttons css need 
> to be change to permit a programaticaly set color to be provided 
> (optionally). 
>
> Álvaro, can you think of a way to open this to user customisation? I think 
> it is important enough to consider some changes. 
>
> Regards
> Tones
>
> On Wednesday, 19 May 2021 at 03:25:50 UTC+10 Álvaro wrote:
>
>> The svg has two styles, one the inherited fron inline style in span and 
>> "direct rules" (*.tc-tiddler-controls button svg* ). When you apply 
>> direct rules the inherited rules are gone (they are overwritten by 
>> direct). You can see it in the inspector of your browser, "fill:red" is 
>> strikethrough.
>>
>> You need add inline style in svg or add new class, for example in button.
>> button.icon-blue svg{fill:blue;}
>>
>> and use it like
>> ...
>> <$button message="tm-add-tag" param="$tag$" tooltip="Toggle $tag$"  
>> class="tc-btn-invisible icon-blue">
>> <$transclude tiddler="$:/PSaT/check-tag/button/checked-icon" />
>> 
>> ...
>>
>> Then you don't need wikify and you have a reusable style for the icon in 
>> buttons. You can change/add class dynamically to button like tiddlywiki 
>> does with varible and filter in *$:/core/ui/ViewTemplate/title*
>> El martes, 18 de mayo de 2021 a las 17:33:21 UTC+2, TW Tones escribió:
>>
>>> Álvaro
>>> Thanks for you help
>>>
>>> So the fill in the css is forcing the button to  "fill: #cc;"
>>>
>>> The problem is I want to display it with a color provided to a macro and 
>>> use it instead. Meaning the button have multiple colors depending on the 
>>> value provided.
>>>
>>> This is the macro I want to display a colored button.
>>>
>>> \define check-tag-button(tag:"select" color:"blue" 
>>> display-filter:"[all[current]is[tiddler]]" )
>>> \whitespace trim
>>> <$list filter="$display-filter$" variable=display>
>>> <$wikify name=style text="""fill: $color$;""">
>>> <$fieldmangler>
>>><$list filter="[all[current]!tag[$tag$]]" variable=has-tag>
>>> <$button message="tm-add-tag" param="$tag$" tooltip="Toggle 
>>> $tag$"  class="tc-btn-invisible">
>>>  > ><$transclude 
>>> tiddler="$:/PSaT/check-tag/button/unchecked-icon" /> 
>>> 
>>>   
>>><$list filter="[all[current]tag[$tag$]]" variable=not-tagged>
>>> <$button  message="tm-remove-tag" param="$tag$" tooltip="Toggle 
>>> OFF $tag$"  class="tc-btn-invisible">
>>>> ><$transclude 
>>> tiddler="$:/PSaT/check-tag/button/checked-icon" />
>>> 
>>>   
>>> 
>>> 
>>> 
>>> \end
>>> 
>>>
>>> Thanks
>>> Tones
>>>
>>>
>>> On Wednesday, 19 May 2021 at 00:31:04 UTC+10 Álvaro

Re: [tw5] [Help] Color them icons and buttons.

2021-05-19 Thread Jeremy Ruston

Hi Tones

I haven’t read the whole thread, but if you’re asking how to programmatically 
colour a button, in general you can use the style property to set a fill colour:

\define colour() #f00

addsuffix[;]] 
}}}>{{$:/core/images/spiral}}

In the case of the editor toolbars, the icon is usually specified by an “icon” 
field that doesn’t allow a colour to be set. But if you set the “custom-icon” 
field to “yes”, then you can render the icon programmatically. See these two 
examples in the core:

https://github.com/Jermolene/TiddlyWiki5/blob/master/core/ui/EditorToolbar/editor-height.tid
 


https://github.com/Jermolene/TiddlyWiki5/blob/master/core/ui/EditorToolbar/preview.tid
 


Best wishes

Jeremy


> On 18 May 2021, at 23:46, TW Tones  wrote:
> 
> Álvaro,
> 
> Thanks - I am now getting closer to a full understanding of this. In this 
> case I have the color value available in a variable or field value, I wanted 
> to find a way to pass the color to the button display "programaticaly".
> It supports my suspicion that button css is not as hackable as you would 
> expect from tiddlywiki, making this a harder than average to customise this 
> aspect of the User Interface, while making use of the CSS to define a button 
> in the view toolbar (and elsewhere)
> 
> Ideally the tiddlywiki designer can just supply a hex or named color, rather 
> than a need to define a range of classes (colors).
> 
> Perhaps there is an argument that the tiddlywiki toolbar buttons css need to 
> be change to permit a programaticaly set color to be provided (optionally). 
> 
> Álvaro, can you think of a way to open this to user customisation? I think it 
> is important enough to consider some changes. 
> 
> Regards
> Tones
> 
> On Wednesday, 19 May 2021 at 03:25:50 UTC+10 Álvaro wrote:
> The svg has two styles, one the inherited fron inline style in span and 
> "direct rules" (.tc-tiddler-controls button svg ). When you apply direct 
> rules the inherited rules are gone (they are overwritten by direct). You can 
> see it in the inspector of your browser, "fill:red" is strikethrough.
> 
> You need add inline style in svg or add new class, for example in button.
> button.icon-blue svg{fill:blue;}
> 
> and use it like
> ...
> <$button message="tm-add-tag" param="$tag$" tooltip="Toggle $tag$"  
> class="tc-btn-invisible icon-blue">
> <$transclude tiddler="$:/PSaT/check-tag/button/checked-icon" />
> 
> ...
> 
> Then you don't need wikify and you have a reusable style for the icon in 
> buttons. You can change/add class dynamically to button like tiddlywiki does 
> with varible and filter in $:/core/ui/ViewTemplate/title
> El martes, 18 de mayo de 2021 a las 17:33:21 UTC+2, TW Tones escribió:
> Álvaro
> Thanks for you help
> 
> So the fill in the css is forcing the button to  "fill: #cc;"
> 
> The problem is I want to display it with a color provided to a macro and use 
> it instead. Meaning the button have multiple colors depending on the value 
> provided.
> 
> This is the macro I want to display a colored button.
> 
> \define check-tag-button(tag:"select" color:"blue" 
> display-filter:"[all[current]is[tiddler]]" )
> \whitespace trim
> <$list filter="$display-filter$" variable=display>
> <$wikify name=style text="""fill: $color$;""">
> <$fieldmangler>
><$list filter="[all[current]!tag[$tag$]]" variable=has-tag>
> <$button message="tm-add-tag" param="$tag$" tooltip="Toggle $tag$"  
> class="tc-btn-invisible">
>  > ><$transclude 
> tiddler="$:/PSaT/check-tag/button/unchecked-icon" /> 
> 
>   
><$list filter="[all[current]tag[$tag$]]" variable=not-tagged>
> <$button  message="tm-remove-tag" param="$tag$" tooltip="Toggle OFF 
> $tag$"  class="tc-btn-invisible">
>> ><$transclude 
> tiddler="$:/PSaT/check-tag/button/checked-icon" />
> 
>   
> 
> 
> 
> \end
> 
> 
> Thanks
> Tones
> 
> 
> On Wednesday, 19 May 2021 at 00:31:04 UTC+10 Álvaro wrote:
> When you put a button (with the svg) in the viewtoolbar, it take style from 
> here
> .tc-tiddler-controls button svg, .tc-tiddler-controls button img, .tc-search 
> button svg, .tc-search a svg {
> fill: #cc;
> }
> 
> You'll need add a class to the button
> 
> 
> El martes, 18 de mayo de 2021 a las 14:36:44 UTC+2, TW Tones escribió:
> Folks,
> 
> I have 2 svg icons from https://morosanuae.github.io/tw-icons/ 
> 
> 
> I have created a button inside a macro and have used a number of methods to 
> get the colored  result in a tiddler, however when I add the 
> $:/tags/ViewToolbar to a tiddler to get it into the view tool bar the color 
> disappears.
> 
> I want to use the same buttons again and again with only the tooltip, actions 
> and color changing. This save buttons and color coding is helpful.
>

[tw5] Re: [Help] Color them icons and buttons.

Another thought, what if buttons could be provided a color-filter to 
determine the color 
eg: [fieldname[go]then[green]]  [fieldname[stop]then[red]] 
If no color filter exists use the existing methods.

On Wednesday, 19 May 2021 at 22:06:17 UTC+10 TW Tones wrote:

> Álvaro & TT
>
> TT, if you know how can you tell me how to follow your suggestion in the 
> following case?
>
> Thanks for sticking with me on this Álvaro. It seems the issue is I want 
> to craft my own toolbar icons which continue to get displayed on the 
> viewtoolbar (and other other toolbars as required)  however with the 
> ability to programmatically change the color. Now I can totally build my 
> own button with all the features I desire, including programaticaly 
> determined colors, however it appears there is no mechaisium for me to make 
> these colors visible (and change) using the  $:/tags/ViewToolbar method to 
> display the button.
>
> The only options I can see are;
>
>1. If there is an as yet unidentified way to alter the colors on 
>additional buttons placed on the viewToolbar - not by actualy creating a 
>whole new button definition for each color of state.
>2. If someone can provide away to resolve the above, ideally without 
>too many core changes I would be happy.
>   1. Perhaps later such core changes could be added to tiddlywiki (ie 
>   introduce some additional hackability/customisability)
>3. One option may be to produce a new view toolbar, in addition to the 
>current one, on which these limitations have being removed, making use of 
>an available a variable to alter the colors programaticaly.
>
>
> The desired result;
>
>- In tiddlywiki much can be driven with one tag, however given a 
>tiddler without tags I would like a view Toolbar button, to check and 
>uncheck to add and remove a specific tag. I want to do this one or more 
>times and make it easier for others to do so as well.
>- To easily generate a new button, I am trying to build a macro that 
>can be called with a tagname and color (or get the color from the tags 
>color - see tag manager).This can also be used inline in a tiddler.
>- Such a macro would ideally be placed in a tiddler tagged with  
>$:/tags/ViewToolbar to generate the button.
>- The use case;
>   - Given how much can be done once a tiddler is given a specific 
>   tag, having a viewTemplate button that allows key tags to be applied 
> (the 
>   first time)  can then trigger other visible results or actions. eg 
> click to 
>   add the todo tag. This means the user, perhaps unfamiliar need not edit 
> the 
>   tiddler and add the tag manually.
>
>
>- In related uses of the same programmatic assigning of a color to a 
>button you could have;
>   - A check box to add a field or field/value combination, then 
>   display the same icon differently with color according to the value in 
> that 
>   field.
>   - A Button that may not do anything but display a color to indicate 
>   the state of something. eg New Done canceled archived.
>
> Side notes
>
>- One idea is to allow a tagname and color to be given as a variable 
>before transcluding a button.
>- I note the icon presented in front of the title sets the colour 
>using <$set name="foregroundColor" value={{!!color}}> in 
>$:/core/ui/ViewTemplate/title, I just need a button to respond to 
> <> 
>instead, which I can set.
>
>
> Thanks
> Tones
> On Wednesday, 19 May 2021 at 21:21:24 UTC+10 Álvaro wrote:
>
>> If the problem is in direct rule of svg ,that they are inside the tiddler 
>> controls, and it overwrite the inherited style. We can solve 
>> removing(/changing) de direct rule or declaration, or we solve playing with 
>> selector’s specificity, for example if we apply class or inline style in 
>> the svg tag.
>>
>> You have to think in "how many color am I going to add?" "Will i reuse 
>> them? Or will i going to add different color each time?". If you look in 
>> the CSS framework (tailwind, bootstrap,...), they have clases for a numbers 
>> of colors and then they are reused.
>>
>> The user customization is there. Yes, it is possible have a easier user 
>> customization but it requires a hard rework in the CSS.
>>
>>
>> P.S. I think that the following article could be helpful about these CSS 
>> "problems" 
>> https://www.smashingmagazine.com/2010/04/css-specificity-and-inheritance/
>> El miércoles, 19 de mayo de 2021 a las 0:46:25 UTC+2, TW Tones escribió:
>>
>>> Álvaro,
>>>
>>> Thanks - I am now getting closer to a full understanding of this. In 
>>> this case I have the color value available in a variable or field value, I 
>>> wanted to find a way to pass the color to the button display 
>>> "programaticaly".
>>>
>>>- It supports my suspicion that button css is not as hackable as you 
>>>would expect from tiddlywiki, making this a harder than average to 
>>>

[tw5] Re: Fission Demo Day

Thank you for the heads up Jeremy. I had seen this mentioned elsewhere but 
had confused it with next week's event.

On Wednesday, May 19, 2021 at 10:06:40 AM UTC+2 Jeremy Ruston wrote:

> I’ve been invited to do a brief demo of some new developments at tomorrows 
> Fission Demo Day. Everyone is welcome to join, details are here:
>
> https://lu.ma/13ez2zgs
>
> Boris Mann at Fission is doing a great job of bringing together the 
> communities around tools for thought. I’m enjoying seeing more of what 
> other people are doing in the field. With any luck, one of the tangible 
> outcomes of this meta-community might be improvements to interoperability 
> between tools.
>
> Best wishes
>
> Jeremy.
>
>

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

[tw5] Re: [Help] Color them icons and buttons.

Álvaro & TT

TT, if you know how can you tell me how to follow your suggestion in the 
following case?

Thanks for sticking with me on this Álvaro. It seems the issue is I want to 
craft my own toolbar icons which continue to get displayed on the 
viewtoolbar (and other other toolbars as required)  however with the 
ability to programmatically change the color. Now I can totally build my 
own button with all the features I desire, including programaticaly 
determined colors, however it appears there is no mechaisium for me to make 
these colors visible (and change) using the  $:/tags/ViewToolbar method to 
display the button.

The only options I can see are;

   1. If there is an as yet unidentified way to alter the colors on 
   additional buttons placed on the viewToolbar - not by actualy creating a 
   whole new button definition for each color of state.
   2. If someone can provide away to resolve the above, ideally without too 
   many core changes I would be happy.
  1. Perhaps later such core changes could be added to tiddlywiki (ie 
  introduce some additional hackability/customisability)
   3. One option may be to produce a new view toolbar, in addition to the 
   current one, on which these limitations have being removed, making use of 
   an available a variable to alter the colors programaticaly.


The desired result;

   - In tiddlywiki much can be driven with one tag, however given a tiddler 
   without tags I would like a view Toolbar button, to check and uncheck to 
   add and remove a specific tag. I want to do this one or more times and make 
   it easier for others to do so as well.
   - To easily generate a new button, I am trying to build a macro that can 
   be called with a tagname and color (or get the color from the tags color - 
   see tag manager).This can also be used inline in a tiddler.
   - Such a macro would ideally be placed in a tiddler tagged with  
   $:/tags/ViewToolbar to generate the button.
   - The use case;
  - Given how much can be done once a tiddler is given a specific tag, 
  having a viewTemplate button that allows key tags to be applied (the 
first 
  time)  can then trigger other visible results or actions. eg click to add 
  the todo tag. This means the user, perhaps unfamiliar need not edit the 
  tiddler and add the tag manually.
   

   - In related uses of the same programmatic assigning of a color to a 
   button you could have;
  - A check box to add a field or field/value combination, then display 
  the same icon differently with color according to the value in that field.
  - A Button that may not do anything but display a color to indicate 
  the state of something. eg New Done canceled archived.
   
Side notes

   - One idea is to allow a tagname and color to be given as a variable 
   before transcluding a button.
   - I note the icon presented in front of the title sets the colour using 
   <$set name="foregroundColor" value={{!!color}}> in 
   $:/core/ui/ViewTemplate/title, I just need a button to respond to <> 
   instead, which I can set.


Thanks
Tones
On Wednesday, 19 May 2021 at 21:21:24 UTC+10 Álvaro wrote:

> If the problem is in direct rule of svg ,that they are inside the tiddler 
> controls, and it overwrite the inherited style. We can solve 
> removing(/changing) de direct rule or declaration, or we solve playing with 
> selector’s specificity, for example if we apply class or inline style in 
> the svg tag.
>
> You have to think in "how many color am I going to add?" "Will i reuse 
> them? Or will i going to add different color each time?". If you look in 
> the CSS framework (tailwind, bootstrap,...), they have clases for a numbers 
> of colors and then they are reused.
>
> The user customization is there. Yes, it is possible have a easier user 
> customization but it requires a hard rework in the CSS.
>
>
> P.S. I think that the following article could be helpful about these CSS 
> "problems" 
> https://www.smashingmagazine.com/2010/04/css-specificity-and-inheritance/
> El miércoles, 19 de mayo de 2021 a las 0:46:25 UTC+2, TW Tones escribió:
>
>> Álvaro,
>>
>> Thanks - I am now getting closer to a full understanding of this. In this 
>> case I have the color value available in a variable or field value, I 
>> wanted to find a way to pass the color to the button display 
>> "programaticaly".
>>
>>- It supports my suspicion that button css is not as hackable as you 
>>would expect from tiddlywiki, making this a harder than average to 
>>customise this aspect of the User Interface, while making use of the CSS 
>> to 
>>define a button in the view toolbar (and elsewhere)
>>
>>
>> Ideally the tiddlywiki designer can just supply a hex or named color, 
>> rather than a need to define a range of classes (colors).
>>
>> Perhaps there is an argument that the tiddlywiki toolbar buttons css need 
>> to be change to permit a programaticaly set color to be provided 
>> (optionally).

[tw5] Re: [Help] Color them icons and buttons.

TW Tones wrote:

>
>- It supports my suspicion that button css is not as hackable as you 
>would expect from tiddlywiki, making this a harder than average to 
>customise this aspect of the User Interface, while making use of the CSS 
> to 
>define a button in the view toolbar (and elsewhere)
>
>
The issue is not TiddlyWiki classes it is merely CSS specificity. 
In situations where you need to apply definitive styling USE a hard-coded 
*style="css 
style code" * directive. That always overrides any class directives that 
otherwise apply. 
Its not entirely kosher on semantic markup, and PMario will tell me off for 
mentioning it, but it will work.

Over & out :-)
TT, x

-- 
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/27308d98-55dc-4fdb-94ab-35bde2968ad6n%40googlegroups.com.

[tw5] Re: [Help] Color them icons and buttons.

2021-05-19 Thread Álvaro

If the problem is in direct rule of svg ,that they are inside the tiddler 
controls, and it overwrite the inherited style. We can solve 
removing(/changing) de direct rule or declaration, or we solve playing with 
selector’s specificity, for example if we apply class or inline style in 
the svg tag.

You have to think in "how many color am I going to add?" "Will i reuse 
them? Or will i going to add different color each time?". If you look in 
the CSS framework (tailwind, bootstrap,...), they have clases for a numbers 
of colors and then they are reused.

The user customization is there. Yes, it is possible have a easier user 
customization but it requires a hard rework in the CSS.


P.S. I think that the following article could be helpful about these CSS 
"problems" 
https://www.smashingmagazine.com/2010/04/css-specificity-and-inheritance/
El miércoles, 19 de mayo de 2021 a las 0:46:25 UTC+2, TW Tones escribió:

> Álvaro,
>
> Thanks - I am now getting closer to a full understanding of this. In this 
> case I have the color value available in a variable or field value, I 
> wanted to find a way to pass the color to the button display 
> "programaticaly".
>
>- It supports my suspicion that button css is not as hackable as you 
>would expect from tiddlywiki, making this a harder than average to 
>customise this aspect of the User Interface, while making use of the CSS 
> to 
>define a button in the view toolbar (and elsewhere)
>
>
> Ideally the tiddlywiki designer can just supply a hex or named color, 
> rather than a need to define a range of classes (colors).
>
> Perhaps there is an argument that the tiddlywiki toolbar buttons css need 
> to be change to permit a programaticaly set color to be provided 
> (optionally). 
>
> Álvaro, can you think of a way to open this to user customisation? I think 
> it is important enough to consider some changes. 
>
> Regards
> Tones
>
> On Wednesday, 19 May 2021 at 03:25:50 UTC+10 Álvaro wrote:
>
>> The svg has two styles, one the inherited fron inline style in span and 
>> "direct rules" (*.tc-tiddler-controls button svg* ). When you apply 
>> direct rules the inherited rules are gone (they are overwritten by 
>> direct). You can see it in the inspector of your browser, "fill:red" is 
>> strikethrough.
>>
>> You need add inline style in svg or add new class, for example in button.
>> button.icon-blue svg{fill:blue;}
>>
>> and use it like
>> ...
>> <$button message="tm-add-tag" param="$tag$" tooltip="Toggle $tag$"  
>> class="tc-btn-invisible icon-blue">
>> <$transclude tiddler="$:/PSaT/check-tag/button/checked-icon" />
>> 
>> ...
>>
>> Then you don't need wikify and you have a reusable style for the icon in 
>> buttons. You can change/add class dynamically to button like tiddlywiki 
>> does with varible and filter in *$:/core/ui/ViewTemplate/title*
>> El martes, 18 de mayo de 2021 a las 17:33:21 UTC+2, TW Tones escribió:
>>
>>> Álvaro
>>> Thanks for you help
>>>
>>> So the fill in the css is forcing the button to  "fill: #cc;"
>>>
>>> The problem is I want to display it with a color provided to a macro and 
>>> use it instead. Meaning the button have multiple colors depending on the 
>>> value provided.
>>>
>>> This is the macro I want to display a colored button.
>>>
>>> \define check-tag-button(tag:"select" color:"blue" 
>>> display-filter:"[all[current]is[tiddler]]" )
>>> \whitespace trim
>>> <$list filter="$display-filter$" variable=display>
>>> <$wikify name=style text="""fill: $color$;""">
>>> <$fieldmangler>
>>><$list filter="[all[current]!tag[$tag$]]" variable=has-tag>
>>> <$button message="tm-add-tag" param="$tag$" tooltip="Toggle 
>>> $tag$"  class="tc-btn-invisible">
>>>  > ><$transclude 
>>> tiddler="$:/PSaT/check-tag/button/unchecked-icon" /> 
>>> 
>>>   
>>><$list filter="[all[current]tag[$tag$]]" variable=not-tagged>
>>> <$button  message="tm-remove-tag" param="$tag$" tooltip="Toggle 
>>> OFF $tag$"  class="tc-btn-invisible">
>>>> ><$transclude 
>>> tiddler="$:/PSaT/check-tag/button/checked-icon" />
>>> 
>>>   
>>> 
>>> 
>>> 
>>> \end
>>> 
>>>
>>> Thanks
>>> Tones
>>>
>>>
>>> On Wednesday, 19 May 2021 at 00:31:04 UTC+10 Álvaro wrote:
>>>
 When you put a button (with the svg) in the viewtoolbar, it take style 
 from here
 *.tc-tiddler-controls button svg*, .tc-tiddler-controls button img, 
 .tc-search button svg, .tc-search a svg {
 fill: #cc;
 }

 You'll need add a class to the button


 El martes, 18 de mayo de 2021 a las 14:36:44 UTC+2, TW Tones escribió:

> Folks,
>
> I have 2 svg icons from https://morosanuae.github.io/tw-icons/
>
> I have created a button inside a macro and have used a number of 
> methods to get the colored  result in a tiddler, however when I add 
> the $:/tags/ViewToolbar to a tiddler to get it into the view tool bar the 
> color disappears.
>
> I

[tw5] Re: Demystify drag-N-drop in Tiddlywiki

*TECHNICAL ISSUES ON D-N-D*

Whilst D-n-D is a lot better on browsers that it used to be *there can 
definitely still be issues* just getting it to work.
We need to understand these BETTER and solve them.

*I STILL cannot get your examples to work on Firefox (latest).* I am 
unclear WHY? It is likely some setting in the config of the browser? I am 
not sure. 
Eventually I'll work it out. But it is not a good sign. A normal user 
expects stuff to just work.

D-n-D on mobile is very useful to have *(ALL students work on phones on 
their way to college :-). *Obviously, in a touch-screen-environment, with 
pages not showing tabs, is quite different than Desktop. 
TBH this needs to be thought into more! 
How can we make a smart-phone TW UI work optimally for D-n-D of links?

Side comments
TT

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

[tw5] Re: Demystify drag-N-drop in Tiddlywiki

*MISCELLANEOUS IDEAS ...*

Because of the potential of D-N-D to simplify common procedures I think it
worth reflecting of different aspect of integrating its UI ... Here are a
few ideas ...

1. Design a TW ONLY to collect links and tag and fill in any extra data.
EMBED that TW in an IFRAME in any wiki that occasionally needs to collect
links. The Design of the LINK-COLLECTOR Wiki uses CSS to maximise screen
estate so that once embedded it is easy to use in the host wiki. Provide
Export mechanism so that they collected links can be imported as needed
into the "host" wiki.
2. Design a macro of form: <> so that you can
easily create custom dropzones with special actions without needing
multiple macros.
3. Detect via the INFO mechanism (needs the official environment sniffer
plugin) whether the d-n-d is running on DESKTOP or on SMART-PHONE (auto
adjust behaviour/presentation to suit).
4. Consider IF, in design, an additional EDIT field slot is needed so
that you can ALSO cut and paste (this would feed into the same parsers
defined at [2]) as well as D-n-D.

Just thoughts!

--
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/c0222068-e322-44e8-9d98-fa46c94ca40an%40googlegroups.com.

[tw5] Re: Demystify drag-N-drop in Tiddlywiki

Ciao Mohammad

*I wanted to revisit the OP and reflect on what we learned so far ... *
Just my opinions ...


   - I think having a REVEAL after drop to show the input is very useful 
   for editing links.
   - It MIGHT, for the purposes of the OP (letting students collect 
   research bookmarks) that on REVEAL of the item to be added there is ALSO 
   option to ADD a second TAG ... So, for instance, if they were studying 
   cinema that could have both "Bookmark" AND ADD "Movie-Source" OR 
   "IMDB-title", according to need?
   - Finally, I also wonder if a simple entry field might need adding into 
   which to PASTE a full link/title (as I made with the bookmarklet example). 
   Those can't be dragged. But copy and paste, once the Bookmarklet has run, 
   is almost as fast. 


My idea here is ONE interface that uses the SAME underlying MINI-PARSER and 
TEMP tiddler so either method would work. In other words BOTH a Dropzone 
and a Field to paste into. Hope this is clear!

My thoughts so far :-)
Best wishes
TT


On Saturday, 8 May 2021 at 20:58:45 UTC+2 Mohammad wrote:

> While drag and drop is not a new feature in Tiddlywiki, but it is a bit 
> tricky to develop tools based on it.
> There are a lot of great use cases for it [1]. This feature has  recently 
> been improved [2] and there is still work in progress to address issues and 
> make it more powerful!
>
> I am working on a resource to demystify the drag-N-drop in Tiddlywiki lets 
> all users use and customize it in their development for different purposes!
>
> Please kindly share your scripts, tools, and examples for drag-N-drop in 
> Tiddlywiki. I will do 
>
>
> Best wishes
> Mohammad
>
>
> Ref
> [1] https://groups.google.com/g/tiddlywiki/c/dDMG3Ocb29s/m/J0hYKp0qBAAJ
> [2] https://groups.google.com/g/tiddlywiki/c/OR48TT_loB8/m/OY3LMOrDBAAJ
>
>

-- 
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/e2968279-edeb-477f-802d-7ea000dd30een%40googlegroups.com.

Re: [tw5] Re: Demystify drag-N-drop in Tiddlywiki

Ciao TW Tones

TW Tones wrote: ...

> First I am focusing on dragging anything and it "is or becomes a tiddler" 
> or something according to where you drop it, including a JSON tiddler and 
> plugins.
> Yes it depends on where you drop it.
>
> Just for context I am using the recent bucket, streams and Projectify and 
> dragging things all over the place. Bucket is a a holding space.
>
> ... however I am looking at parsing titles and generating nicer ones, 
> moving the old title into a tiddler field.
>

*Right! Needed in many cases.*

At the basic level A "dropzone" will launch a MINI-PARSER that facilitates 
that. 

As Mohammad's OP developed in this thread it got clearer that for capturing 
outside links, and maybe page content too,   then need some processing.

My point here is that its not so clear yet what exactly the process is. OR 
to what extent you need Purpose Specific Dropzones.

IMO I think its getting important to better differentiate specific aims.

For instance, in my own case, I am most interested in harvesting links from 
a limited number of sources to data dictionaries. 
An example is a student of CINEMA needs to always refer to IMDB.com as it 
is the de-facto canonical source for movie data.
SO, for those students, a dropzone purely for IMDB makes most sense. 

You get my point? 
I think defining end use purposes matters quite a lot in know what to build!

Best wishes
TT

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

Re: [tw5] [plugin] Navi cheatsheet: Export command line snippets directly to the shell

2021-05-19 Thread bimlas

Ste,

so...you can write something in a nodejs tiddlywiki and then it sends it to 
> navi and that becomes a command line shortcut sort of thing?


This is exactly it: you can keep the snippets among your notes, so you can 
give a more detailed explanation, and they will be categorized due to the 
structure and of your notes (table of contents, links, etc.). If, on the 
other hand, you need the code snippet on the command line, you don't have 
to search through your notes, just search for the right keywords in Navi.

Its advantage over running snippets in a separate Navi file is that there 
is no duplication: if you realize that you need to add another parameter to 
a command in a snippet, you only need to edit it in your notes, you don't 
have to do it in the Navi file as well.

-- 
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/917d5d70-df86-4ed0-be9b-12ddae01bed6n%40googlegroups.com.

Re: [tw5] Re: Demystify drag-N-drop in Tiddlywiki

Mohammad wrote ...

> If I have found free time, I will look in my collection of bookmarklets! I 
> think there are several solutions, one of them works with Node.JS and is 
> very similar to TiddlyClip!
>

Right! I certainly think that having a collection of *bookmarklets* for use 
alongside TW could be very useful. I think it is worth looking into as they 
can assemble data we need for TW linking that TW cannot itself do (for 
example getting the title of a page as well as its url). We could maybe go 
further and capture other data and page content too through bookmarklets?

Right also on TiddlyClip! I think there is a lot that can be learned, and 
maybe used, from it.

Best wishes
TT 

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/1117ecef-d70e-48b8-ace5-f55f672da4e0n%40googlegroups.com.

Re: [tw5] [plugin] Navi cheatsheet: Export command line snippets directly to the shell

2021-05-19 Thread Ste

so...you can write something in a nodejs tiddlywiki and then it sends it to 
navi and that becomes a command line shortcut sort of thing?
mind blown...

On Tuesday, 18 May 2021 at 05:35:07 UTC+1 Mohammad wrote:

> Ah lovely!
> Thank you Bimlas!
>
> Best wishes
> Mohammad
>
>
> On Mon, May 17, 2021 at 9:48 PM bimlas  wrote:
>
>> Invoke snippets and one-liners stored in Node.js TiddlyWiki directly from 
>> the command line.
>>
>> Navi  is an interactive cheatsheet 
>> tool for the command-line: it allows you to browse through cheatsheets 
>> (that you may write yourself or download from maintainers) and execute 
>> commands. This is a great way to replace aliases, one-liners and short 
>> scripts with a searchable "snippet database".
>>
>> Many keep these snippets in their own description of the related program. 
>> This plugin helps you to access the snippets in your notes directly from 
>> the command line using Navi.
>>
>> https://bimlas.gitlab.io/tw5-navi-cheatsheet/
>>
>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "TiddlyWiki" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to tiddlywiki+...@googlegroups.com.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/tiddlywiki/55372319-0a7f-4a59-ab19-cac9916a9b82n%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/b1d1d0d5-0dd1-4cd1-a064-d7887f903281n%40googlegroups.com.

[tw5] Re: I love TiddlyWiki because...

2021-05-19 Thread bimlas

TiddlyWiki is the second most flexible format / tool after plain text, it’s 
like a self-contained Unix-like system.

-- 
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/c5606e43-22e0-4d92-9d64-c4282c9ce9c1n%40googlegroups.com.

[tw5] Re: [Theme] Zacht - A clean and soft theme for TiddlyWiki

2021-05-19 Thread Odin

@Mohammad, Thank you for your comment!

@Soren, I hid the buttons because I don't really need to see them most of 
the time. When I do need them, they appear when hovering the general area 
where they should be. I also think that because the buttons don't really 
change (except when you add one yourself) I don't need the reminders of 
what options there are. I think the buttons can be visually cluttering, 
especially if you pin multiple buttons, so I like the aesthetic of them 
hidden. I like UI that gets out of the way when it is not needed.

The issue in your screenshot is an unintended side effect of the CSS that 
hides buttons. I hadn't noticed it yet, but I agree it would be better if 
those icons don't fade away while not hovering on the dropdown. I am not 
sure how I would disable it for just the dropdown though : /

Odin
Op woensdag 19 mei 2021 om 00:58:16 UTC+2 schreef Soren Bjornstad:

> Odin,
>
> I like the look of this! I particularly appreciate the improved whitespace 
> and toolbar design in the editor. I might have to look at replicating some 
> of that in my CodeMirror editor.
>
> Can I ask, what is the rationale behind hiding the buttons until you mouse 
> over them? To me it seems this mostly makes it harder to hit the button and 
> less obvious what options you have. Also, when I click on the more menu and 
> then move the mouse away from it, it does this, which I assume wasn't 
> intentional:
> [image: ksnip_20210518-175727.png]
>
>
> On Tuesday, May 18, 2021 at 2:23:10 PM UTC-5 Odin wrote:
>
>> Hello everyone!
>>
>> I am proud to share my latest creation: Zacht - a clean and soft theme 
>> for TiddlyWiki.  
>>
>> Zacht is the Dutch word for soft. With soft colors and roundings, I found 
>> it a fitting name. The theme also embeds two fonts that really adds a fresh 
>> look while staying true to the feel of the vanilla theme.
>>
>> The stylesheets are split up in small stylesheets to keep it easy to look 
>> up any CSS to change it to your likings even further.
>>
>> This was also the first time I worked with Node.js. So I am also hosting 
>> the individual files on GitHub for proper installation for those who use 
>> TiddlyWiki on Node.js. It was a fun project : )
>>
>> I hope this theme finds some use for someone. I am open to feedback, 
>> either in this thread or on GitHub. 
>> 
>>
>> Also, thanks to Saqimtiaz for the last-minute troubleshooting on discord!
>>
>> Kind regards,
>>
>> Odin
>>
>>

-- 
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/41119627-b891-4e2d-a0cf-985c3fd0a98cn%40googlegroups.com.

Re: [tw5] Streams 0.21 is now available

2021-05-19 Thread 謝佩琪

It's work!

Sorry that it is my first time to use macro, so I don't understand the 
feature in FAQs.

Thank you very much!

saq.i...@gmail.com 在 2021年5月19日 星期三下午3:02:22 [UTC+8] 的信中寫道：

>
>  
>
>> I hope a new feature that the report tiddler can still have bullet level
>
>
> There are a few options described in the documentation, you should be able 
> to find one that you can customize for your needs:
> https://saqimtiaz.github.io/streams/#Working%20with%20streams%20tiddlers 
>

-- 
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/f0d5d54a-939e-4978-93db-de8f32a37986n%40googlegroups.com.

Re: [tw5] Streams 0.21 is now available