@Saq
 

> Tests definitely imply it's the detection code. No visible difference when 
>> popup runs or doesn't run filters.
>>
> ...
> How about a filter that that just detects whether the fragment for 
> titlepicker has disallowed characters?
>

Hm, since it is always matched against existing strings (e.g titles) is 
that not enough? I mean the fragment "Editox" is as disallowed as e.g 
"Edito]]" , is it not? (But I have to admit this logic of mine it feels 
like I'm stepping back to how it was when before you stepped in when I 
couldn't tell where the end of the fragment was...)


>>>    - I am also unsure if we need this list anymore (after introducing 
>>>    em-itemfilter):
>>>    <$list 
>>>    
>>> filter="[<em-fragment>length[]add<before-length>add<trigger-length>match<selectionEnd>]"
>>>  
>>>    variable="_NULL" emptyMessage=<<em-checkNextTrigger>>>
>>>    ...
>>>
>>> No discernible difference in a side by side.
>>
>
> If you are sure about this, we can remove this list and the variables that 
> are there just for its sake.
>

As sure as my primitive test is, yes ;-) 


[...] forces the entire popup to redraw itself from scratch on every 
> keystroke, rather than say a title list that just updates itself. 


>  <$vars foo={{{ [{!!foo}] }}}>
> content
> </$vars>
>
> If the value of "foo" in the vars widget changes, the entire widget is 
> destroyed and re-created, which means so is everything inside it.
>
> If however you do something like the following, the list updates itself 
> instead of re-drawing from scratch. This is much faster:
> <$list filter=[prefix{!!fo}]>
> content
> </$list>
>

Are you saying filtered transclusion {{{...}}} is evaluated for each stroke 
but $list is not? That sounds like great but I also don't understand how 
that is possible since listwidgets do update when their filter changes.... 
don't they?

But, regardless, how the hey would I exchange the $vars for $list in the 
_Popup? There'd be big number of nested lists and... I just don't 
understand.

Here is one of several testing wikis where I have implemented what you say, 
except for this last vars--->list thing. 

http://editormagicny5.tiddlyspot.com/  

This is not the regular editormagic2 wiki where I try to keep the latest 
advancements that I show to you but the dabbles I made now are not ready 
for editormagic2 but it would be kind if you could take a look to see if I 
understood your points here above. BTW, I removed the keyboard shortcut in 
TitlePicker to not get distracted from this.

Thank you Saq :-)

<:-)

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWikiDev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywikidev/ce7b5b2c-216a-4b1e-a917-add5828857feo%40googlegroups.com.

Reply via email to