date:20200706

[tw5] Re: Code simplification Challenge - a smart config values select

2020-07-06 Thread Felicia Crow

Hi Tony,

sorry for not answering yesterday, but my migraine apparently now gets also 
triggered by smaller changes in weather.

Thanks for the reminder of the size parameter! Somehow I was so convinced 
at the time that it had to be something with width and found nothing except 
for css changes that I used a textarea for the bigger size.
The whole it has to be width was probably while I also overread it in the 
documentation.

To your test, can you elaborate on what you think is not right? I tried 
both versions in the same wiki and they gave me the same result.

Regards,
Felicia

On Sunday, 5 July 2020 03:38:32 UTC+2, TW Tones wrote:
>
> Felicia,
>
> Great work. 
>
> I am happy to do more challenges, I hope others also support this idea, 
> and they are welcome to do it themselves.
>
> In chrome I downloaded your json to a scratch area, went to tiddlywiki.com, 
> dragged the file and dropped it in tiddlywiki.com and tested it. I added 
> enable disable to the value config values. It works and it reuses the 
> select statements reducing the amount of code required.
>
> The edit pairs could be changed to 
> Edit Pairs: <$edit-text tiddler="$:/smartConfig/config/pairs" field="text" 
> tag=input size=80/>
>
> I used this small test opn your example and mine
> <$list filter="[prefix[$:/config/]]">
> <>
> 
> Something is not right.
>
> Regards
> Tony
>
>
>
>
>
> On Sunday, July 5, 2020 at 6:52:41 AM UTC+10, Felicia Crow wrote:
>>
>> Hi,
>>
>> First personally I would love for challenges like these to become a thing 
>> since not only do I get to learn things I normally would not necessarily 
>> need for myself and second I think it would be interesting to see different 
>> approaches to the same challenge.
>>
>> Second here is my solution for the basic challenge:
>>
>> *How the macro works:*
>>
>>- The Macro is still called with tiddlername and fieldname with the 
>>same defaults.
>>- The outermost list widgets check if currentValue is empty or not 
>>and react accordingly
>>- If there is no currentValue the first select will be created with 
>>all values currently defined in the corresponding config tiddler.
>>   - The config tiddler to use is defined in the configTiddler 
>>   variable to make it easier to change the tiddler. Currently the only 
>> hard 
>>   coded part is that the pairs have to be in the text field.
>>- If there is a currentValue - or a value was chosen in the first 
>>select - then the second select will be created only showing the 
>>corresponding pair. E.g.: If the current value is 'yes' only the options 
>>'yes' and 'no' are available.
>>   - For now the value pair has to be defined in the config tiddler 
>>   for this to work. In the version for the extended challenge I 
>> hopefully 
>>   manage to have a way to create a field on setting the initial value 
>> that 
>>   will keep the respective pair within the tiddler itself.
>>   
>> *How to extend the macro*
>>
>>- Simply add another pair/set of options to the config separated at 
>>least by ';' for the pair and by at least one space for each option.
>>- Only caveat for now is each value in a pair/set has to be a single 
>>word/string without spaces.
>>
>> *Macro*
>> \define smart-configure(tiddlername fieldname:"fieldname")
>> <$set name=configTiddler value="$:/smartConfig/config/pairs">
>> <$set name=tiddlername value="$tiddlername$" emptyValue=<> >> >
>> <$set name=currentValue value={{{ [get[$fieldname$]trim[]] 
>> }}}>
>> tiddlername=<>, fieldname=$fieldname$, currentValue=<<
>> currentValue>>
>>
>> <$list filter="[is[blank]]" variable=nul>
>> Select initial value:
>> <$select tiddler=<> field="$fieldname$" default=<<
>> currentValue>> >
>>   <$list filter='[get[text]split[;]!is[blank]join[ ]]'>
>>  <$list filter="[split[ ]!is[blank]]"> 
>>>><$view field='title'/>
>>  
>>   
>> 
>> 
>>
>> <$list filter="[!is[blank]]" variable=nul>
>> <$list filter="[get[text]split[;]trim[]!is[blank]] 
>> +[search]">
>> <$select tiddler=<> field="$fieldname$" default=<<
>> currentValue>> >
>>   <$list filter="[split[ ]]"> 
>> >><$view field='title'/>
>>   
>> 
>> 
>> 
>>
>> 
>> 
>> 
>> \end
>>
>> *Configuration*
>> yes no; show hide; true false; left right; top bottom
>>
>> The attached version of the macro tiddler includes a text edit widget to 
>> quickly edit the config tiddler and two examples to see both states of the 
>> macro.
>> The import and tiddlers work on empty.html, tiddlywiki.com and the 
>> playground .
>>
>> For now I will leave it at that, but will look into the extended 
>> challenge within the next days since it has some very interesting points to 
>> solve.
>>
>> Regards,
>> Felicia
>>
>

-- 
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

[tw5] Re: EditorMagic - status update

2020-07-06 Thread TW Tones

Mat,

Not sure what you mean. It does support *invoking *macros and widgets (even 
> if we'd need some mechanism to collect all macro titles) and there is 
> support for stamping, e.g like is done in the HTMLtable example (test it by 
> typing  really isn't practical because you'd have to exchange every parameter 
> anyway, leaving only the \define and \end. As for widgets, it could stamp 
> some JS skeleton I guess but I don't know what that would encompass.
>

I was just wondering if you had considered it?, not extending features, 
just as is, you next paragraph describes what I was thinking. 
 

>
> BUT, regardless, *the idea is that the user can easily make his own popup 
> content!* The key feature is really to enable a popup at caret position 
> that can show any content based on what you just typed in the editor. I 
> added several examples that are "estimations" of what people will want, 
> mostly to demo the concept, but the hope is that once it's a plugin, the 
> community will come up with useful tools and other popup content.
>
>
I like this design approach.

Great Stuff
TW 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/de124225-b2c1-400b-8d16-0ce525f564a8o%40googlegroups.com.

[tw5] Re: When would I be missing the "new tiddler" + sign?

2020-07-06 Thread Saq Imtiaz

The login/readonly situation only happens when using authentication on 
node, which is not the default but is set up by the docker container you 
are using.

On Monday, July 6, 2020 at 11:33:16 AM UTC+2, Wpq wrote:
>
> Ah! Thank you! That was the reason. When I logged in I saw the "+" sign.
>
> While in hindsight this is obvious, it may be a good idea to add that 
> point to the "Getting stated" tiddler, as more may be searching for the "+".
>
> Thanks again for the help
>
> Le lundi 6 juillet 2020 à 11:25:42 UTC+2, saq.i...@gmail.com a écrit :
>
>> Have you logged in via http://127.0.0.1:8080/login-basic ?
>>
>>
>> On Monday, July 6, 2020 at 9:35:46 AM UTC+2, Wpq wrote:
>>>
>>> Hello everyone
>>>
>>> I just started to use TiddlyWiki by installing it in a docker container (
>>> https://hub.docker.com/r/vimagick/tiddlywiki).
>>>
>>> When going to the wiki page, I was greeted with the welcome page. Th 
>>> eproblem I have is that there is no "+" sign anywhere!
>>>
>>>
>>>
>>> What could be the reason for that?
>>>
>>

-- 
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/571e194a-3bc3-46d7-9b30-e0b3d5292a6fo%40googlegroups.com.

[tw5] Re: Preview Tiddler button and css

2020-07-06 Thread Felicia Crow

Oh two people one thought, although Saq definitely explained it better.

If scale is not important and it is just about sizing I played around a 
little and found this solution using flexbox:

\define preview(filter)

.preview-container{
  display: flex;
  flex-wrap: wrap;
  flex-direction: row;
  justify-content: flex-start;
}
.preview {
  width: 24%;
  max-height: 400px;
  border:1px solid blue;
  padding: 10px 10px 10px 10px;
  overflow: hidden;
  margin-right: 10px;
  margin-bottom: 10px;
}


<$set name=filter value="$filter$" emptyValue="[[$(currentTiddler)$]]" >

<$list filter=<> >
<$button to=<> tooltip={{{ [all[current]addprefix[Open: ]] 
}}} class="preview" tag="div">
<$link/>
<$transclude mode=block/>




\end


<>



I tested it on tiddlywiki.com in Firefox, Chrome and Edge, and on my own 
wiki on TiddlyDesktop and AndTidWiki. The only thing I noticed is that on 
mobile - probably due to the smaller screen size - there are only three 
previews in a row.

Also should you use this and want to have 400px in gerneral just change out 
max-height to height. I just found it worked better in an universal way 
seeing how for instance my tableofcontent tiddlers are often not very large 
and mostly used for sorting other tiddlers so the 400 was mostly empty 
space. In the same vein a min-height could be added depending on what you 
need.


On Monday, 6 July 2020 10:34:48 UTC+2, TW Tones wrote:
>
> Folks,
>
> If you place the following in a tiddler on tiddlywiki.com, you will see 
> it generates a preview of tiddlers with The TableOfContents tag.
>
> To get here I have begged, borrowed and stolen code. 
>
> The problem is I do not know how to remove the empty space between each 
> preview.
>
> Any advice and I would be grateful.
>
> \define preview(filter)
> 
> .preview {
> width:600px; 
> min-height:400px; max-height:400px;
> -webkit-transform:scale(.25);
> -ms-transform:scale(.5);
> transform:scale(.5,.5);
> -webkit-transform-origin:0 0; 
> -ms-transform-origin:0 0; 
> transform-origin:0 0; 
> border:1px solid blue;
> margin:0 0 0 0;
> padding: 10px 10px 10px 10px;
> overflow: hidden;
> }
> 
>
> <$set name=filter value="$filter$" emptyValue="[[$(currentTiddler)$]]" >
> 
> <$list filter=<> >
> <$button to=<> tooltip={{{ [all[current]addprefix[Open: ]] 
> }}} class="preview" tag="div">
> <$link/>
> <$transclude mode=block/>
> 
> 
> 
> 
> \end
>
>
> <>
>
>
> Of course when working I would move the styles to a stylesheet and macro 
> to a tiddler tagged macro.
>
> Regards
> TW 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/ab8d173f-c70d-4ff8-878f-a23ce764b978o%40googlegroups.com.

[tw5] Re: Preview Tiddler button and css

2020-07-06 Thread Saq Imtiaz

A quick fix that works for most use cases is to wrap your div in a wrapper 
div and give it the final height and width of the div being resized 
(original width x scale), as well as overflow: auto.

Something like

.mywrapper {
  width: 300px;
  height: 200px;
  overflow: hidden;
}

On Monday, July 6, 2020 at 11:39:23 AM UTC+2, Saq Imtiaz wrote:
>
> I haven't tested your code but I can guess what the problem is from your 
> CSS.
>
> When using transform:scale with CSS, the various block level elements are 
> rendered before being scaled. As such, they take up as much space as their 
> original size. There are various workarounds that work, depending on the 
> HTML structure. A search for something like "transform scale empty space" 
> should point you in the correct direction.
>
> On Monday, July 6, 2020 at 10:34:48 AM UTC+2, TW Tones wrote:
>>
>> Folks,
>>
>> If you place the following in a tiddler on tiddlywiki.com, you will see 
>> it generates a preview of tiddlers with The TableOfContents tag.
>>
>> To get here I have begged, borrowed and stolen code. 
>>
>> The problem is I do not know how to remove the empty space between each 
>> preview.
>>
>> Any advice and I would be grateful.
>>
>> \define preview(filter)
>> 
>> .preview {
>> width:600px; 
>> min-height:400px; max-height:400px;
>> -webkit-transform:scale(.25);
>> -ms-transform:scale(.5);
>> transform:scale(.5,.5);
>> -webkit-transform-origin:0 0; 
>> -ms-transform-origin:0 0; 
>> transform-origin:0 0; 
>> border:1px solid blue;
>> margin:0 0 0 0;
>> padding: 10px 10px 10px 10px;
>> overflow: hidden;
>> }
>> 
>>
>> <$set name=filter value="$filter$" emptyValue="[[$(currentTiddler)$]]" >
>> 
>> <$list filter=<> >
>> <$button to=<> tooltip={{{ [all[current]addprefix[Open: 
>> ]] }}} class="preview" tag="div">
>> <$link/>
>> <$transclude mode=block/>
>> 
>> 
>> 
>> 
>> \end
>>
>>
>> <>
>>
>>
>> Of course when working I would move the styles to a stylesheet and macro 
>> to a tiddler tagged macro.
>>
>> Regards
>> TW 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/30b8a195-99e4-4145-b08f-8cb0dc1f199fo%40googlegroups.com.

[tw5] Re: Notowritey - Outliner/editor for TW

2020-07-06 Thread TiddlyTweeter

TW Tones wrote:
>
> I think the view/copy the wiki text version may deserve a special button,
> one I wonder if we could make a generic one, or is it too tool specific?
>

Ciao Tones & Mark

I'd like to chip in on this. As far as I understand it there are *three*
"capture/snap" modes ...

1. HTML
2. PLAIN TEXT (no Wikitext captured)
3. WIKITEXT

All are useful to know about. All three Mark has given the code for, though
they are not "View Bar" buttons atm. HTML & WIKITEXT are in Noto. HTML &
PLAIN TEXT are in the modified export function. The WIKITEXT capture is
from, I think, concatenation of Tiddler "text" fields. HTML & PLAIN TEXT
from "render" levels? Yes?

As far as my understanding goes "capture" is of a named Tiddler. IF that
Tiddler also transcludes other Tiddlers that are auto included.

The approach is generic & generally useful, I think.

But I'm not sure Mark actually needs make a view bar button for it. In Noto
per se these three are invaluable for ..

- Backup
- Versioning out (e.g. posting HTML elsewhere)
- Leveraging Noto "SPLITOLOGY" (this particularly applies to the
WIKITEXT capture where you start afresh and re-split a different way)

And tools for all that exist for Noto.

Conclusion: Making View Bar buttons for this seems A Very Good Idea. But I
don't think Mark needs do that unless he feels a pressing need to.

Thoughts
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/0d35cdcc-6ff9-47b1-b693-83ab65478056o%40googlegroups.com.

59 matches

Mail list logo