[tw5] Re: More Button ( using reveal ) need to make sticky when printing

2021-05-18 Thread Jon Light
After playing around with both the Details plugin 
 and my old implementation of a 
'more button' using reveal I noted the following

All comments relate to whether* 'soft paragraphs' *appear as intended - by 
this I mean paragraphs implemented only by use of carriage return in the 
standard Tiddlywiki editor and not by means of use of  which I 
regard as a pain to add manually - for instance if I cut and paste a page 
from a word processor. 

   1. The details plugin seems to be *sensitive to whether the first line 
   after the  tag is just an empty line ( carriage return only ) *- 
   if the first line contains text then subsequent 'soft paragraphs' are not 
   honoured and the text appears as one continuous 'string' - ie no 
   paragraphs.  I tried other types of text formatting and found that the same 
   thing occurred when using the quotes formatting  ( <<<  text <<< ).
   2. I wanted to use the summary feature *which only seems to work 
   properly if the  tag* *does appear on the first line 
   after the opening  tag* - *this seemed to be a barrier given 
   the point made in 1*.
   3. I then found in  http://tid.li/tw5/hacks.html#DetailsWidget that the 
   summary can appear as an attribute of the  tag ie <$details 
   summary="more">
   4. Everything then worked ok, I could leave a blank line ( carriage 
   return ) immediately after the opening  tag and still have a 
   custom summary using the attribute declaration instead.
   
I wondered if any aspects of the above were Firefox specific but then found 
the same thing happening on Chrome.

*I then went back to my old implementation of a 'more' button using reveal 
and found that actually the same limitations* regards first line appear 
there also, in fact I have long been used to adding additional carriage 
returns to text to ensure that soft paragraphs appear in the reveal, it has 
become an automatic 'non-thinking' thing, I just type or cut and paste my 
text, save, test and then add additional carriage returns where needed. 

The new observation is that the reveal method is also very sensitive to 
this first line condition - I noted for the first time that if the first 
line is not empty ( a carriage return ) then no matter how much I tried to 
break the text into soft paragraphs further into the text the whole thing 
remained one stuborn continuous bit of text with no paragraphs. The reason 
I had not noticed until now is simply that I had always added an empty line 
( carriage return ) at the start of my existing use of the reveal method.

So I am good and ready to carry on with the details plugin :-) but I 
thought it worth mentioning to others about this first line sensitivity in 
either implementation. 

In short it seems if you want either implementation of more and want 'soft 
paragraphs' then 

   - Leave the first line after the opening tag ( reveal or details ) blank 
   ( carriage return only )


   - If you want to use the summary feature of the details implementation 
   then use the attribute method

I think it is important to flag this for general awareness, it is not safe 
to assume that reveal or 'more' sections will be one paragraph and I cannot 
be the only one who would find adding  instead of the more 
convenient carriage return an imposition. 

Jon

On Tuesday, 18 May 2021 at 09:21:39 UTC+1 Jon Light wrote:

> @Tones
>
> Thanks! I was not aware of the details widget, looking at 
> http://tid.li/tw5/hacks.html#DetailsWidget is seems to be exactly what I 
> need.
>
> I don't mind running with the existing 'more' sections with new 'details' 
> sections - when I want to print a tiddler I will do the manual conversion 
> from reveal to details first.
>
> Thanks a lot for that one, I try for paperless but sometimes...
>
> Jon
>
>
> On Tuesday, 18 May 2021 at 02:05:24 UTC+1 TW Tones wrote:
>
>> A Quick possible solution.
>>
>> Rather than use reveal use a list widget to conditionally display your 
>> content, you can then use a more sophisticated filter to determine the 
>> state. so any local tiddler reveal setting can be overridden by another 
>> setting like $:/config/open-all-sliders yes/no, or even give each slider 
>> (you want to) a print mode setting ie in print mode show the following 
>> content regardless of the local state, then set a $:/config/print-mode = yes
>>
>> Another form of more is the html details element but to retain the 
>> open/closed with a toggle look for the details plugin that gives a $details 
>> widget.
>>
>> Tones
>>
>>
>> On Friday, 14 May 2021 at 21:53:14 UTC+10 jonligh...@gmail.com wrote:
>>
>>> Hi, 
>>>
>>> I have been using reveal for a 'more' button for tiddlers with a lot of 
>>> content to limit the vertical screen space they take.
>>>
>>> <$button class="" popup=<>>
>>> @@color:purple;
>>> more...
>>> @@
>>> 
>>>
>>> <$reveal type="nomatch" state=<> text="">
>>>
>>> text to reveal
>>>
>>> 
>>>
>>> It works just fine, I have it set up as 

[tw5] Re: More Button ( using reveal ) need to make sticky when printing

2021-05-18 Thread Jon Light
@Tones

Thanks! I was not aware of the details widget, looking at 
http://tid.li/tw5/hacks.html#DetailsWidget is seems to be exactly what I 
need.

I don't mind running with the existing 'more' sections with new 'details' 
sections - when I want to print a tiddler I will do the manual conversion 
from reveal to details first.

Thanks a lot for that one, I try for paperless but sometimes...

Jon


On Tuesday, 18 May 2021 at 02:05:24 UTC+1 TW Tones wrote:

> A Quick possible solution.
>
> Rather than use reveal use a list widget to conditionally display your 
> content, you can then use a more sophisticated filter to determine the 
> state. so any local tiddler reveal setting can be overridden by another 
> setting like $:/config/open-all-sliders yes/no, or even give each slider 
> (you want to) a print mode setting ie in print mode show the following 
> content regardless of the local state, then set a $:/config/print-mode = yes
>
> Another form of more is the html details element but to retain the 
> open/closed with a toggle look for the details plugin that gives a $details 
> widget.
>
> Tones
>
>
> On Friday, 14 May 2021 at 21:53:14 UTC+10 jonligh...@gmail.com wrote:
>
>> Hi, 
>>
>> I have been using reveal for a 'more' button for tiddlers with a lot of 
>> content to limit the vertical screen space they take.
>>
>> <$button class="" popup=<>>
>> @@color:purple;
>> more...
>> @@
>> 
>>
>> <$reveal type="nomatch" state=<> text="">
>>
>> text to reveal
>>
>> 
>>
>> It works just fine, I have it set up as a custom stamp so I can just 
>> select the section I want to hide and its done in a click or two.
>>
>> The only issue I have is when I try and use this with code designed to 
>> print a tiddler eg.
>>
>> https://groups.google.com/g/tiddlywiki/c/SYGksSEeNTA
>>
>> The problem is that if I click anywhere in a tiddler that has an open 
>> reveal (as above) then the reveal closes and of course it is necessary to 
>> click on a print icon in the tiddler to get a print-out - so my attempt to 
>> print closes the reveal and my print out shows it closed.
>>
>> The ideal situation would be to prevent clicks on the tiddler tool bars 
>> from closing the reveal, I find it very useful to click on the tiddler to 
>> close the reveal so it would be cool to maintain the current behaviour 
>> except when the click is on a tool icon but the general solution might be 
>> to only close when the click is on the more button that opened it in the 
>> first place.
>>
>> Another solution might be to have a sidebar option to toggle the behaviour
>>
>>- Click anywhere in tiddler to close
>>- Click on the more button to close
>>
>> This might be the best option of all because I have similar difficulties 
>> when I want to copy text from within a reveal section ( attempt to select 
>> text closes reveal ) currently I have go into edit more on the tiddler 
>> containing the reveal which contains the text I want to copy.
>>
>> I have tried using class 'tc-popup-keep' on the reveal but no experiments 
>> so far have resulted in a reveal that stays open when I click anywhere in 
>> the tiddler so I have yet to get past first base on this one. 
>>
>> thanks for any suggestions - Jon
>>
>>
>>
>>
>>
>>
>>

-- 
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/d9a92408-ecfc-44d0-adfb-4310a2682c05n%40googlegroups.com.


[tw5] Re: More Button ( using reveal ) need to make sticky when printing

2021-05-17 Thread TW Tones
A Quick possible solution.

Rather than use reveal use a list widget to conditionally display your 
content, you can then use a more sophisticated filter to determine the 
state. so any local tiddler reveal setting can be overridden by another 
setting like $:/config/open-all-sliders yes/no, or even give each slider 
(you want to) a print mode setting ie in print mode show the following 
content regardless of the local state, then set a $:/config/print-mode = yes

Another form of more is the html details element but to retain the 
open/closed with a toggle look for the details plugin that gives a $details 
widget.

Tones


On Friday, 14 May 2021 at 21:53:14 UTC+10 jonligh...@gmail.com wrote:

> Hi, 
>
> I have been using reveal for a 'more' button for tiddlers with a lot of 
> content to limit the vertical screen space they take.
>
> <$button class="" popup=<>>
> @@color:purple;
> more...
> @@
> 
>
> <$reveal type="nomatch" state=<> text="">
>
> text to reveal
>
> 
>
> It works just fine, I have it set up as a custom stamp so I can just 
> select the section I want to hide and its done in a click or two.
>
> The only issue I have is when I try and use this with code designed to 
> print a tiddler eg.
>
> https://groups.google.com/g/tiddlywiki/c/SYGksSEeNTA
>
> The problem is that if I click anywhere in a tiddler that has an open 
> reveal (as above) then the reveal closes and of course it is necessary to 
> click on a print icon in the tiddler to get a print-out - so my attempt to 
> print closes the reveal and my print out shows it closed.
>
> The ideal situation would be to prevent clicks on the tiddler tool bars 
> from closing the reveal, I find it very useful to click on the tiddler to 
> close the reveal so it would be cool to maintain the current behaviour 
> except when the click is on a tool icon but the general solution might be 
> to only close when the click is on the more button that opened it in the 
> first place.
>
> Another solution might be to have a sidebar option to toggle the behaviour
>
>- Click anywhere in tiddler to close
>- Click on the more button to close
>
> This might be the best option of all because I have similar difficulties 
> when I want to copy text from within a reveal section ( attempt to select 
> text closes reveal ) currently I have go into edit more on the tiddler 
> containing the reveal which contains the text I want to copy.
>
> I have tried using class 'tc-popup-keep' on the reveal but no experiments 
> so far have resulted in a reveal that stays open when I click anywhere in 
> the tiddler so I have yet to get past first base on this one. 
>
> thanks for any suggestions - Jon
>
>
>
>
>
>
>

-- 
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/7ee35623-c4a6-4269-aed6-384a414cbf23n%40googlegroups.com.