[twdev] Re: [TWX] syntax for supertransclusion and filter evaluation

2018-10-01 Thread TonyM
The thing I would like to "transclude" the most is filters

So I may gave a complex or long filter to identify active tasks that are 
not closed, cancelled or archived and in a particular context current 
domain, project/client then transclude them

In a filter "[{active-tasks}{this-context}]

Something like this can already be done but I do not want the filters 
active-tasks appearing as regular tiddlers and in search results

I could use {$:/filter/this-context} however it quickly starts to loose its 
readability.

Perhaps a "name space" $:/transcludes such that $:/transcludes/this-context 
can be transcluded as {this-context} 

or even smarter

Perhaps a "name space" $:/transclude/filters such that 
$:/$:/transclude/filters/in-context creates a filter operator

"incontext[]" that can be negated "!incontext[]" and perhaps we can use 
suffix and content in some way

This would make it much easier to share filters, keep macros a lot clearer 
and help new users learn from existing ones.

Regards
Tony

On Tuesday, October 2, 2018 at 1:56:47 AM UTC+10, joearms wrote:
>
> It would be nice to add one more layer of indirection if necessary -- here 
> are some examples
>
> {{foo.jpg}} -- transclude an image
> {{foo.jpg | width:100, height:35}  -- translude a image with size
> {{TiddlerLink}} -- transclude a tiddler
> {{my_local_file.txt | type:text, start:200, stop:400}} transclude a 
> local file from lines 200 to 400
>
> The syntax {{File | arg1:..., arg2:...}} means translude File with some 
> arguments, and the meaning would depend
> upon the file type. As the number of arguments become large it becomes 
> very difficult to add them 'in line' - so
> we add a layer of indirection
>
>  {{MyTiddler.tr}} this means the translusion instructions will be 
> found in the Tiddler MyTiddler.tr -- these could be
> very long and complicated (for example contain SQL queries, entire scripts 
> in some programming language etc.)
>
> As an experiment I'm writing a pure stand-alone  transcluder that only 
> expands {{...}} items.
>
> It came as a nasty surprise to me that {{http://some_thing.html}} didn't 
> do what I expected :-)
>
> There's actually a very long philosophical discussion to be had about the 
> scope of transclusions - Jeremy's design
> for the tiddly wiki was to strictly adhere to what I call 'all in one' 
> ness - ie all the tiddlers you can refer to must be
> in the same physical and logical container - this is great for many 
> purposes since it ensures the TW will still be the same
> in many years time BUT ... I find myself wanting to break outside the 
> container.
>
> [http://]] does allow a breakout - when you click it. 
>
> {{http://}} could mean - "go and transcribe the contents of the 
> reference and cache the contents" but for how long - would remote 
> transclusions have a time to live? It would be very nice to transclude 
> tiddlers from somebody else's TW - but how would this work? Should a TW 
> have a public interface (ie certain tiddlers are tagged as public) and may 
> be remotely transcluded. 
>
>
>
> On Saturday, 29 September 2018 11:33:25 UTC+2, Mat wrote:
>>
>> For TWX (a potential, fantastical, future version of TW) I'm proposing 
>> some minor syntactical changes - assuming the overall TW syntax paradigm is 
>> at all still relevant then;
>>
>> {{{ ... }}} - instead of current filter evaluation, it is used to 
>> "transclude the transclusion". There are occasions where {{foo}} gives 
>> "bar" but what is needed is {{bar}}, so this super transclusion would do 
>> this. Thus, the swirly brackets are dedicated to transclusion matters.
>>
>>
>> [[[ ... ]]]  - this, instead, is for "filter evaluation". Thus, square 
>> brackets are dedicated to filter matters.
>>
>>
>> <:-)
>>
>>

-- 
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 tiddlywikidev+unsubscr...@googlegroups.com.
To post to this group, send email to tiddlywikidev@googlegroups.com.
Visit this group at https://groups.google.com/group/tiddlywikidev.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywikidev/6d4bb0d0-7eb4-4aa2-9df5-9f3540f83550%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [twdev] Deriving a TW

2018-10-01 Thread TonyM
joearms,

Try tiddlyclip which is going part of the way on your suggestions

https://github.com/buggyj/tiddlyclip

Regards
Tony

On Monday, October 1, 2018 at 12:31:57 AM UTC+10, joearms wrote:
>
> Thank you - great fun the play with - this seems to be an area which would 
> benefit from a
> lot of work. It would be nice to have some visual tool to select sections 
> of larger web pages
> and export the selections as wiki text with full annotations as to where 
> they came from.
>
> Basically a tool to create transclusions :-)
>
> Cheers
>
> /Joe
>
> On Sunday, 30 September 2018 15:29:44 UTC+2, Jeremy Ruston wrote:
>>
>> Hi Joe
>>
>> On 30 Sep 2018, at 09:24, joearms  wrote:
>>
>> h1 tags could be used to split HTML into tiddlers
>>
>>
>> You can use the “text-slicer” plugin for that (in the official plugin 
>> library). There’s a prebuilt version you can experiment with:
>>
>> https://tiddlywiki.com/prerelease/editions/text-slicer
>>
>> For example, I downloaded the HTML file 
>> https://en.wikipedia.org/wiki/TiddlyWiki and dragged it into wiki, 
>> importing it as a single tiddler in HTML format.
>>
>>
>> Then I clicked the “text slicer” button, and selected “one tiddler per 
>> paragraph in a linear thread”.
>>
>>
>> The resulting sliced up tiddlers are visible in a sidebar on the left, 
>> and you can open them by clicking on them. You can also export the sliced 
>> tiddlers using the advanced search tab.
>>
>> Best wishes
>>
>> Jeremy.
>>
>>

-- 
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 tiddlywikidev+unsubscr...@googlegroups.com.
To post to this group, send email to tiddlywikidev@googlegroups.com.
Visit this group at https://groups.google.com/group/tiddlywikidev.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywikidev/88962630-b1cd-48cb-9f80-8c0ef177fc34%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[twdev] Re: Big list of TWs

2018-10-01 Thread @TiddlyTweeter
Ciao Mohammad

It appears out of date because it is underused. Very few plugin writers 
sign up to it.

Josiah
 

-- 
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 tiddlywikidev+unsubscr...@googlegroups.com.
To post to this group, send email to tiddlywikidev@googlegroups.com.
Visit this group at https://groups.google.com/group/tiddlywikidev.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywikidev/6f9b8d83-e361-43ff-a493-e5cd1bc7ed9c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [twdev] Re: Big list of TWs

2018-10-01 Thread Thomas Elmiger
Mohammad,

The list is automated, it fetches updates e.g. from my plugin site – that
mechanism seems to work.
To add/remove solutions see contact page:
http://erwanm.github.io/tw-community-search/#Contact

Thomas

-- 
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 tiddlywikidev+unsubscr...@googlegroups.com.
To post to this group, send email to tiddlywikidev@googlegroups.com.
Visit this group at https://groups.google.com/group/tiddlywikidev.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywikidev/CALXLrTgDaKyub%3DQR6VK7%3DXqenrFiWp327t-g6eXWVD9wRw%2B53Q%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.


[twdev] Re: [TWX] syntax for supertransclusion and filter evaluation

2018-10-01 Thread joearms
It would be nice to add one more layer of indirection if necessary -- here 
are some examples

{{foo.jpg}} -- transclude an image
{{foo.jpg | width:100, height:35}  -- translude a image with size
{{TiddlerLink}} -- transclude a tiddler
{{my_local_file.txt | type:text, start:200, stop:400}} transclude a 
local file from lines 200 to 400

The syntax {{File | arg1:..., arg2:...}} means translude File with some 
arguments, and the meaning would depend
upon the file type. As the number of arguments become large it becomes very 
difficult to add them 'in line' - so
we add a layer of indirection

 {{MyTiddler.tr}} this means the translusion instructions will be found 
in the Tiddler MyTiddler.tr -- these could be
very long and complicated (for example contain SQL queries, entire scripts 
in some programming language etc.)

As an experiment I'm writing a pure stand-alone  transcluder that only 
expands {{...}} items.

It came as a nasty surprise to me that {{http://some_thing.html}} didn't do 
what I expected :-)

There's actually a very long philosophical discussion to be had about the 
scope of transclusions - Jeremy's design
for the tiddly wiki was to strictly adhere to what I call 'all in one' ness 
- ie all the tiddlers you can refer to must be
in the same physical and logical container - this is great for many 
purposes since it ensures the TW will still be the same
in many years time BUT ... I find myself wanting to break outside the 
container.

[http://]] does allow a breakout - when you click it. 

{{http://}} could mean - "go and transcribe the contents of the 
reference and cache the contents" but for how long - would remote 
transclusions have a time to live? It would be very nice to transclude 
tiddlers from somebody else's TW - but how would this work? Should a TW 
have a public interface (ie certain tiddlers are tagged as public) and may 
be remotely transcluded. 



On Saturday, 29 September 2018 11:33:25 UTC+2, Mat wrote:
>
> For TWX (a potential, fantastical, future version of TW) I'm proposing 
> some minor syntactical changes - assuming the overall TW syntax paradigm is 
> at all still relevant then;
>
> {{{ ... }}} - instead of current filter evaluation, it is used to 
> "transclude the transclusion". There are occasions where {{foo}} gives 
> "bar" but what is needed is {{bar}}, so this super transclusion would do 
> this. Thus, the swirly brackets are dedicated to transclusion matters.
>
>
> [[[ ... ]]]  - this, instead, is for "filter evaluation". Thus, square 
> brackets are dedicated to filter matters.
>
>
> <:-)
>
>

-- 
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 tiddlywikidev+unsubscr...@googlegroups.com.
To post to this group, send email to tiddlywikidev@googlegroups.com.
Visit this group at https://groups.google.com/group/tiddlywikidev.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywikidev/e4fae511-7a5b-41f1-b686-2df9554838b6%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[twdev] Re: Big list of TWs

2018-10-01 Thread Mohammad Rahmani
Thomas,
 Who does maintain this list? It seems it is outdated!

Mohammad

On Sunday, September 30, 2018 at 10:13:00 PM UTC+3:30, Thomas Elmiger wrote:
>
> Hey Joe
>
> Often overseen: https://tiddlywiki.com/#TWCommunitySearch
>
> Good luck! 
> Thomas 
>
>

-- 
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 tiddlywikidev+unsubscr...@googlegroups.com.
To post to this group, send email to tiddlywikidev@googlegroups.com.
Visit this group at https://groups.google.com/group/tiddlywikidev.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywikidev/0020419d-f5a4-4175-8c02-674d466079be%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.