[tw5] Re: [tw] Re: Navigating and transcluding Slices...Missing Features for the atomic concept:

2018-11-26 Thread Roger Ferrari 
Using Thomas solution together with the Smart TOC extension for chrome 
works just fine for me.

this is the 
extension: 
https://chrome.google.com/webstore/detail/smart-toc/lifgeihcfpkmmlfjbailfpfhbahhibba/related

it has a github page, unfortunately I am no coder/programmer I was trying 
to understand a way to get the piece of code to reproduce what the 
extension does but I just can't.

On Monday, March 27, 2017 at 9:04:36 PM UTC-3, Jan wrote:
>
> Hi Thomas, thanks a lot for this.
> I would prefer an Infobox in the Edit-Mode right below the TiddlerTitle.
> It would be best to include a warning wether the Tiddler is transcluded 
> from somewhere in order to avoid accidental confusions.
>
> ...but I also have thought of using your Plugin the other way round to 
> produce a slice-replacement. 
> A function extracting some marked piece of a specific Tiddler. Something 
> like Text to extract.
> This would also have the advantage that it would be immediately visible 
> that the slice is used elsewhere.
>
> Yours Jan
>
> Am 08.01.2017 um 01:07 schrieb Thomas Elmiger:
>
> Hi Jan
>
> The extract macro  offers a 
> new solution to this: 
>
>> -When you discover that the content you wish to change was transcluded, 
>> it takes some time to get to the real tiddler; in most cases I have to find 
>> and open with the searchbar.
>> It would be practical if transclusions were clickable Links in the 
>> edit-Mode. Could this be done with a template or plugin? 
>>
>  
> As you would expect, it can find all {{transclusions}} in curly style – 
> and with the new version (0.9.2) you can output them as a list of links. I 
> made a demo here: http://tid.li/tw5/hacks.html#Icon%20Test where it lists 
> all the images used. 
>
> I think such a list could be appended as a tab to the tiddler info panel … 
> or maybe you could make a conditional view template and append it to the 
> edit view. Of course you miss .
>
> Good luck and good night!
> Thomas
> -- 
> 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 post to this group, send email to tiddl...@googlegroups.com 
> .
> Visit this group at https://groups.google.com/group/tiddlywiki.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/tiddlywiki/d1593e2f-124f-419d-8922-3f4a98d00d8b%40googlegroups.com
>  
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>
>
>

-- 
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 post to this group, send email to tiddlywiki@googlegroups.com.
Visit this group at https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/e7fb2b70-77b1-4e60-b291-6a36f910bb04%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [tw] Re: Navigating and transcluding Slices...Missing Features for the atomic concept:

2017-03-27 Thread Jan 

Hi Thomas, thanks a lot for this.
I would prefer an Infobox in the Edit-Mode right below the TiddlerTitle.
It would be best to include a warning wether the Tiddler is transcluded 
from somewhere in order to avoid accidental confusions.


...but I also have thought of using your Plugin the other way round to 
produce a slice-replacement.
A function extracting some marked piece of a specific Tiddler. Something 
like Text to extract.
This would also have the advantage that it would be immediately visible 
that the slice is used elsewhere.


Yours Jan

Am 08.01.2017 um 01:07 schrieb Thomas Elmiger:

Hi Jan

The extract macro  
offers a new solution to this:


-When you discover that the content you wish to change was
transcluded, it takes some time to get to the real tiddler; in
most cases I have to find and open with the searchbar.
It would be practical if transclusions were clickable Links in the
edit-Mode. Could this be done with a template or plugin?

As you would expect, it can find all {{transclusions}} in curly style 
– and with the new version (0.9.2) you can output them as a list of 
links. I made a demo here: http://tid.li/tw5/hacks.html#Icon%20Test 
where it lists all the images used.


I think such a list could be appended as a tab to the tiddler info 
panel … or maybe you could make a conditional view template and append 
it to the edit view. Of course you miss .


Good luck and good night!
Thomas
--
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 post to this group, send email to tiddlywiki@googlegroups.com 
.

Visit this group at https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/d1593e2f-124f-419d-8922-3f4a98d00d8b%40googlegroups.com 
.

For more options, visit https://groups.google.com/d/optout.


--
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 post to this group, send email to tiddlywiki@googlegroups.com.
Visit this group at https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/587240AE.4010102%40googlemail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [tw] Re: Navigating and transcluding Slices...Missing Features for the atomic concept:

2017-01-09 Thread Jan 

Hi Thomas
That is great you just reinvented slices for TW5...and the best is: For 
one slice it even works without setting a number!
I would like it to set it to standart "inline", because block is easily 
done with return or .


Thanks so much!
Bye Jan

I'll have to be off for a week to fininsh some professional duties





Am 09.01.2017 um 19:33 schrieb Thomas Elmiger:

Hi Jan

Easy things first. Good idea ;–)

My current idea is also to use the extract-macro the other way
round...in order to build a sort of replacemanet for slices. Mark
a textpart ant then insert it somewhere else by means of the the
macro.

This is exactly what extact was made for.

It would be an idea to use the same mark-up for those slices as
for slides. Somethin like  text1   text2 
To find them it would be nice to have a macro that would look like
<>.

Ah – a simplified meta-macro (I just invented that word) like our ref 
macro. Of course this works. I made a demo on 
http://tid.li/tw5/numbers.html, see Chapter 2 Paragraph 1.1.


Code: http://tid.li/tw5/numbers.html#%24%3A%2F_telmiger%2Fslice

|
\define slice(tiddler,nr,mode:"block")
<$macrocall 
$name="extract"tiddler="""$tiddler$"""start=""end=""mode="$mode$"class="slice"/>

\end
|

I opted to add the mode parameter so you can change to inline mode if 
you like.


And I close the tag using the number Your slice. I am 
not sure yet that this is the final solution, maybe there is a 
standard HTML tag we could use and a custom param like slice="1">Slice content.


By the way, I think I smashed the bug that was preventing you from 
updating. I guess you have to add class="summary" (or class:"summary") 
to your existing macro calls.


I hope, this works for you. All the best!
Thomas
--
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 post to this group, send email to tiddlywiki@googlegroups.com 
.

Visit this group at https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/e2ff2f93-819d-42a1-a24e-c3c611e8950f%40googlegroups.com 
.

For more options, visit https://groups.google.com/d/optout.


--
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 post to this group, send email to tiddlywiki@googlegroups.com.
Visit this group at https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/58740120.5060901%40googlemail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [tw] Re: Navigating and transcluding Slices...Missing Features for the atomic concept:

2017-01-09 Thread Matthew Lauber 
Sweet.  Just assumed this was a quirk of the tiddler format and was set in 
stone.  Good to know there is a fix that's being considered.  It's actually 
one of the issues I ran into with TiddlyServer.  One of the people testing 
had a newline at the end of their author name, so every tiddler they saved 
was invalidly formatted.  Took me a while to figure that one out.

Matt

On Monday, January 9, 2017 at 9:44:52 AM UTC-5, Tobias Beer wrote:
>
> Hi Matt,
>
>  
>
>> As an FYI, I've actually done a lot of work with fields, and discovered 
>> that if you put a newline in a field on a tiddler, and export that tiddler 
>> to a ".tid" fle, it breaks the format of the ".tid" file. This is an issue 
>> if you ever intend to use the nodejs server, as it stores the files, behind 
>> the scenes, in ".tid" format.
>>
>
> While the solution recently suggested by Jeremy is not implemented yet, 
> there's an issue for that here:
>
> *#1947 tiddler format for multiline fields (esp. node.js)*
> https://github.com/Jermolene/TiddlyWiki5/issues/1947
>
> Best wishes,
>
> Tobias.
>

-- 
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 post to this group, send email to tiddlywiki@googlegroups.com.
Visit this group at https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/945db423-4b1c-47ae-adeb-a3bd835edd07%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [tw] Re: Navigating and transcluding Slices...Missing Features for the atomic concept:

2017-01-09 Thread Thomas Elmiger 
Hi Jan

Easy things first. Good idea ;–)

My current idea is also to use the extract-macro the other way round...in 
> order to build a sort of replacemanet for slices. Mark a textpart ant then 
> insert it somewhere else by means of the the macro.
>
This is exactly what extact was made for.
 

> It would be an idea to use the same mark-up for those slices as for 
> slides. Somethin like  text1   text2 
> To find them it would be nice to have a macro that would look like < "Tiddlername" 1>>.
>
Ah – a simplified meta-macro (I just invented that word) like our ref 
macro. Of course this works. I made a demo on 
http://tid.li/tw5/numbers.html, see Chapter 2 Paragraph 1.1.

Code: http://tid.li/tw5/numbers.html#%24%3A%2F_telmiger%2Fslice 

\define slice(tiddler,nr,mode:"block")
<$macrocall $name="extract" tiddler="""$tiddler$""" start="" end=
"" mode="$mode$" class="slice"/> 
\end

I opted to add the mode parameter so you can change to inline mode if you 
like. 

And I close the tag using the number Your slice. I am not 
sure yet that this is the final solution, maybe there is a standard HTML 
tag we could use and a custom param like Slice 
content. 

By the way, I think I smashed the bug that was preventing you from 
updating. I guess you have to add class="summary" (or class:"summary") to 
your existing macro calls.

I hope, this works for you. All the best!
Thomas

-- 
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 post to this group, send email to tiddlywiki@googlegroups.com.
Visit this group at https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/e2ff2f93-819d-42a1-a24e-c3c611e8950f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [tw] Re: Navigating and transcluding Slices...Missing Features for the atomic concept:

2017-01-09 Thread Tobias Beer 
Hi Matt,

 

> As an FYI, I've actually done a lot of work with fields, and discovered 
> that if you put a newline in a field on a tiddler, and export that tiddler 
> to a ".tid" fle, it breaks the format of the ".tid" file. This is an issue 
> if you ever intend to use the nodejs server, as it stores the files, behind 
> the scenes, in ".tid" format.
>

While the solution recently suggested by Jeremy is not implemented yet, 
there's an issue for that here:

*#1947 tiddler format for multiline fields (esp. node.js)*
https://github.com/Jermolene/TiddlyWiki5/issues/1947

Best wishes,

Tobias.

-- 
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 post to this group, send email to tiddlywiki@googlegroups.com.
Visit this group at https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/d5c34197-ee60-491d-9ee3-cae08d40b5d0%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [tw] Re: Navigating and transcluding Slices...Missing Features for the atomic concept:

2017-01-09 Thread Danielo Rodríguez 
That is definetively a bug. Is it reported? 

-- 
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 post to this group, send email to tiddlywiki@googlegroups.com.
Visit this group at https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/13926543-6a7f-4525-8e80-a76ccd1d1d92%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [tw] Re: Navigating and transcluding Slices...Missing Features for the atomic concept:

2017-01-09 Thread Matthew Lauber 
As an FYI, I've actually done a lot of work with fields, and discovered 
that if you put a newline in a field on a tiddler, and export that tiddler 
to a ".tid" fle, it breaks the format of the ".tid" file.  This is an issue 
if you ever intend to use the nodejs server, as it stores the files, behind 
the scenes, in ".tid" format.

Matt

On Wednesday, January 4, 2017 at 2:40:30 PM UTC-5, Danielo Rodríguez wrote:
>
>
>
> El viernes, 17 de junio de 2016, 19:39:02 (UTC+2), c pa escribió:
>>
>>
>> Oh right. I do all my editing from dashboards because all my tiddlers are 
>> structured. The concept is as follows:
>>
>> Analysis
>> 
>>
>> # Decide on a structure for your tiddlers
>> #* Example "Book" would have the following fields
>> #** Title
>> #** Authors
>> #** Publisher
>> #** My random ramblings
>> #** My Review
>> #** Plot synopsis
>> #** ISBN Number
>>
>> Discussion
>> =
>>
>> * My random ramblings is a good candidate for the text field
>> * My Review, and Plot synopsis are good candidates for slices
>> * The title of the book should be put in the caption field because two 
>> books can have the same title
>> * ISBN is unique for books so put that in the title filed (The name of 
>> the tiddler - must be unique)
>> * Authors can be multiple so this would be a list of authors populated 
>> from tiddlers tagged "author"
>> ** This requires a macro to populate it. 
>> ** You can use crazyListHere from cpashow.tiddlyspot.com 
>> ** As you might suspect from the name, my macro currently does all sorts 
>> of stuff in addition to populating a list
>> * Publisher is a text name populated using a select from tiddlers tagged 
>> "publisher"
>>
>> Code a template
>> =
>>
>
> I was thinking about  something very similar. We have all that we need 
> already on tiddlywiki. The rest is just a matter of how do you present the 
> information. Tiddlers have fields, so you can have as many fields as 
> sections you need. Then, the only thing you need is a view template to 
> transclude all the "_section/name" fields and a edit template to edit them 
> comfortable.
>
> Let me say *c pa* that I find your implementation brilliant. Thank you 
> for sharing.
>

-- 
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 post to this group, send email to tiddlywiki@googlegroups.com.
Visit this group at https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/4bc2f2a1-51f6-47f9-a742-f75851cec972%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [tw] Re: Navigating and transcluding Slices...Missing Features for the atomic concept:

2017-01-08 Thread Jan 

Hi Thomas,
I think a box below the Title in the editTemplate would be best for this 
purpose...and it would be good to show also in which tiddlers this 
tiddler is transcluded, in order to avoid breaking it's text up 
accidentally.


My current idea is also to use the extract-macro the other way 
round...in order to build a sort of replacemanet for slices. Mark a 
textpart ant then insert it somewhere else by means of the the macro.
It would be an idea to use the same mark-up for those slices as for 
slides. Somethin like  text1   text2 
To find them it would be nice to have a macro that would look like 
<>.

 Do you think that would work?

Yours Jan.





Am 08.01.2017 um 01:07 schrieb Thomas Elmiger:

Hi Jan

The extract macro  
offers a new solution to this:


-When you discover that the content you wish to change was
transcluded, it takes some time to get to the real tiddler; in
most cases I have to find and open with the searchbar.
It would be practical if transclusions were clickable Links in the
edit-Mode. Could this be done with a template or plugin?

As you would expect, it can find all {{transclusions}} in curly style 
– and with the new version (0.9.2) you can output them as a list of 
links. I made a demo here: http://tid.li/tw5/hacks.html#Icon%20Test 
where it lists all the images used.


I think such a list could be appended as a tab to the tiddler info 
panel … or maybe you could make a conditional view template and append 
it to the edit view. Of course you miss .


Good luck and good night!
Thomas
--
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 post to this group, send email to tiddlywiki@googlegroups.com 
.

Visit this group at https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/d1593e2f-124f-419d-8922-3f4a98d00d8b%40googlegroups.com 
.

For more options, visit https://groups.google.com/d/optout.


--
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 post to this group, send email to tiddlywiki@googlegroups.com.
Visit this group at https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/5872AF81.10906%40googlemail.com.
For more options, visit https://groups.google.com/d/optout.

[tw] Re: Navigating and transcluding Slices...Missing Features for the atomic concept:

2017-01-07 Thread Thomas Elmiger 
Hi Jan

The extract macro  offers a 
new solution to this: 

> -When you discover that the content you wish to change was transcluded, it 
> takes some time to get to the real tiddler; in most cases I have to find 
> and open with the searchbar.
> It would be practical if transclusions were clickable Links in the 
> edit-Mode. Could this be done with a template or plugin? 
>
 
As you would expect, it can find all {{transclusions}} in curly style – and 
with the new version (0.9.2) you can output them as a list of links. I made 
a demo here: http://tid.li/tw5/hacks.html#Icon%20Test where it lists all 
the images used. 

I think such a list could be appended as a tab to the tiddler info panel … 
or maybe you could make a conditional view template and append it to the 
edit view. Of course you miss .

Good luck and good night!
Thomas

-- 
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 post to this group, send email to tiddlywiki@googlegroups.com.
Visit this group at https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/d1593e2f-124f-419d-8922-3f4a98d00d8b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [tw] Re: Navigating and transcluding Slices...Missing Features for the atomic concept:

2017-01-04 Thread Danielo Rodríguez 


El viernes, 17 de junio de 2016, 19:39:02 (UTC+2), c pa escribió:
>
>
> Oh right. I do all my editing from dashboards because all my tiddlers are 
> structured. The concept is as follows:
>
> Analysis
> 
>
> # Decide on a structure for your tiddlers
> #* Example "Book" would have the following fields
> #** Title
> #** Authors
> #** Publisher
> #** My random ramblings
> #** My Review
> #** Plot synopsis
> #** ISBN Number
>
> Discussion
> =
>
> * My random ramblings is a good candidate for the text field
> * My Review, and Plot synopsis are good candidates for slices
> * The title of the book should be put in the caption field because two 
> books can have the same title
> * ISBN is unique for books so put that in the title filed (The name of the 
> tiddler - must be unique)
> * Authors can be multiple so this would be a list of authors populated 
> from tiddlers tagged "author"
> ** This requires a macro to populate it. 
> ** You can use crazyListHere from cpashow.tiddlyspot.com 
> ** As you might suspect from the name, my macro currently does all sorts 
> of stuff in addition to populating a list
> * Publisher is a text name populated using a select from tiddlers tagged 
> "publisher"
>
> Code a template
> =
>

I was thinking about  something very similar. We have all that we need 
already on tiddlywiki. The rest is just a matter of how do you present the 
information. Tiddlers have fields, so you can have as many fields as 
sections you need. Then, the only thing you need is a view template to 
transclude all the "_section/name" fields and a edit template to edit them 
comfortable.

Let me say *c pa* that I find your implementation brilliant. Thank you for 
sharing.

-- 
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 post to this group, send email to tiddlywiki@googlegroups.com.
Visit this group at https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/fb8a0d50-14e3-490c-8b68-eb08b506b842%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [tw] Re: Navigating and transcluding Slices...Missing Features for the atomic concept:

2017-01-04 Thread Dmitry Sokolov 
Regarding renaming tiddlers, it is not recommended on LikeInMind while 
technically possible.

In order to avoid dead links and lost connections, tiddlers are federated 
under a desired name. The content of the "old" tiddler is replaced with the 
link onto the "fresh" one. :)
Replacement of the obsolete links is done manually, when realised/needed. 
Ideally, a "garbage collector" would be great to have.

Just my 2 cents,
Dmitry

On Saturday, 11 June 2016 20:07:25 UTC+12, Jeremy Ruston wrote:
>
> Hi Jan
>
> Yet two my mind there is two missing features:
>>
>
> I'd acknowledge the impact of the issues you mention, but fixing them is 
> 1,000 times easier than introducing full support for slicing.
>  
>
>> -When you discover that the content you wish to change was transcluded, 
>> it takes some time to get to the real tiddler; in most cases I have to find 
>> and open with the searchbar.
>> It would be practical if transclusions were clickable Links in the 
>> edit-Mode. Could this be done with a template or plugin? 
>>
>
> My favoured approach to fix this is to introduce a mode that makes 
> transclusions visible, so that one can directly click on a link to open the 
> target tiddler.
>  
>
>> -It would be important to have better Security mechanisms against 
>> destroying links. Especially renaming tiddlers can have dangerous effects. 
>> It would be nice if users were shown a Modal informing about Links Lists 
>> and Transclusions for which the Tiddker has importance..
>>
>
> As discussed elsewhere, I'd favour support for automatically replacing 
> references to a tiddler when it is renamed.
>
> Best wishes
>
> Jeremy.
>
>  
>
>>
>> Regards Jan 
>>
>> In TWClassic when changing the Name of a Tag-Tiddler i was asked wheter I 
>> wished to change the tags to. 
>>
>> On Wed, Jun 8, 2016 at 3:40 PM, Jeremy Ruston > > wrote:
>>
>>> It’s clear that users want to be able to write/paste long passages of 
>>> text into a tiddler and then individually address sections (or 
>>> slices/chunks). In practice, I think that means that anything that one can 
>>> presently do to an entire tiddler needs to be possible with a slice: 
>>> transclusion, linking, searching, etc.
>>>
>>> That means that the system has to deal with two levels of granularity: 
>>> slices and entire tiddlers. Internally, everywhere that we manipulate 
>>> tiddlers we’d need to support slices too.
>>>
>>> In fact, slices would become the fundamental unit; an entire tiddler 
>>> would be a special case of a slice covering the entire tiddler.
>>>
>>> That’s where things get interesting: now we’ve redefined a slice to be a 
>>> tiddler (which is just what we call a fundamental discrete unit of content 
>>> in TiddlyWiki). Now, for performance reasons, we’d want to avoid repeatedly 
>>> scanning tiddlers to extract the slices; instead, we’d want to store the 
>>> individual slices separately so that we can efficiently address them as 
>>> needed.
>>>
>>> You can probably see where this goes: we’ve just ended up *renaming* 
>>> “tiddlers” to “slices”, and adding facilities to deal with sequences of 
>>> slices as discrete entities called “tiddlers”.
>>>
>>> That’s pretty much where we are today: it’s easy to combine several 
>>> tiddlers to make them appear to be a single tiddler: we use transclusion, 
>>> or macros based on transclusion like the TOC macro.
>>>
>>> We’ve still got the problem of dealing with long passages of text: 
>>> that’s where the text-slicer plugin comes in, showing one way that these 
>>> long texts can be split into chunks, and the chunks recombined in flexible 
>>> ways.
>>>
>>> So, my position isn’t ideological, nor am I wilfully ignoring feedback 
>>> from users. But I am asserting that from an engineering perspective it’s 
>>> cleaner and more efficient to be dealing with a single fundamental entity, 
>>> and to approach the original problem from the other end: by splitting and 
>>> recombining.
>>>
>>> Best wishes
>>>
>>> Jeremy
>>>
>>>
>>> On 8 Jun 2016, at 14:27, Jed Carty > 
>>> wrote:
>>>
>>> I am a bit stuck at the moment because while I don't want to discourage 
>>> any exploration into different ways of using TiddlyWiki there is a TW5 way 
>>> of doing what you are talking about, which is to use either more tiddlers 
>>> or fields which you then place wherever you want them using transclusions.
>>>
>>> Using templates you could have the anchor tag part of the transclusion 
>>> so you could navigate to a spot in an open tiddler. If you want to be able 
>>> to both open a tiddler and navigate to some spot in that tiddler than we 
>>> would need a more complex macro but it may be able to be done using only 
>>> wikitext and simple html. Or we may need to make an action widget that does 
>>> the same action as clicking on a normal link.
>>>
>>> -- 
>>> 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

[tw] Re: Navigating and transcluding Slices...Missing Features for the atomic concept:

2017-01-04 Thread Dmitry Sokolov 
In LikeInMind practice, transclusion is a very rare case. Transcluded 
tiddlers may change with time in the context of the hosting topic / main 
page. Those changes may conflict with the content of the topic / page they 
are transcluded to. Federation is highly recommended instead.

Both, transcluded and federated tiddlers must have back links to the source 
pages.
To avoid confusion, transcluded tiddlers are framed. Federated tiddlers 
have no formatting differences with the rest of the page they are pasted to.

I hope you find it helpful.
Cheers,
Dmitry

On Saturday, 11 June 2016 11:22:54 UTC+12, Jan wrote:
>
> Hi Jeremy
> The concept of an atomic datastructure sounds logic.
> Yet two my mind there is two missing features:
>
> -When you discover that the content you wish to change was transcluded, it 
> takes some time to get to the real tiddler; in most cases I have to find 
> and open with the searchbar.
> It would be practical if transclusions were clickable Links in the 
> edit-Mode. Could this be done with a template or plugin? 
>
> -It would be important to have better Security mechanisms against 
> destroying links. Especially renaming tiddlers can have dangerous effects. 
> It would be nice if users were shown a Modal informing about Links Lists 
> and Transclusions for which the Tiddker has importance..
>
> Regards Jan 
>
> In TWClassic when changing the Name of a Tag-Tiddler i was asked wheter I 
> wished to change the tags to. 
>
> On Wed, Jun 8, 2016 at 3:40 PM, Jeremy Ruston  > wrote:
>
>> It’s clear that users want to be able to write/paste long passages of 
>> text into a tiddler and then individually address sections (or 
>> slices/chunks). In practice, I think that means that anything that one can 
>> presently do to an entire tiddler needs to be possible with a slice: 
>> transclusion, linking, searching, etc.
>>
>> That means that the system has to deal with two levels of granularity: 
>> slices and entire tiddlers. Internally, everywhere that we manipulate 
>> tiddlers we’d need to support slices too.
>>
>> In fact, slices would become the fundamental unit; an entire tiddler 
>> would be a special case of a slice covering the entire tiddler.
>>
>> That’s where things get interesting: now we’ve redefined a slice to be a 
>> tiddler (which is just what we call a fundamental discrete unit of content 
>> in TiddlyWiki). Now, for performance reasons, we’d want to avoid repeatedly 
>> scanning tiddlers to extract the slices; instead, we’d want to store the 
>> individual slices separately so that we can efficiently address them as 
>> needed.
>>
>> You can probably see where this goes: we’ve just ended up *renaming* 
>> “tiddlers” to “slices”, and adding facilities to deal with sequences of 
>> slices as discrete entities called “tiddlers”.
>>
>> That’s pretty much where we are today: it’s easy to combine several 
>> tiddlers to make them appear to be a single tiddler: we use transclusion, 
>> or macros based on transclusion like the TOC macro.
>>
>> We’ve still got the problem of dealing with long passages of text: that’s 
>> where the text-slicer plugin comes in, showing one way that these long 
>> texts can be split into chunks, and the chunks recombined in flexible ways.
>>
>> So, my position isn’t ideological, nor am I wilfully ignoring feedback 
>> from users. But I am asserting that from an engineering perspective it’s 
>> cleaner and more efficient to be dealing with a single fundamental entity, 
>> and to approach the original problem from the other end: by splitting and 
>> recombining.
>>
>> Best wishes
>>
>> Jeremy
>>
>>
>> On 8 Jun 2016, at 14:27, Jed Carty > 
>> wrote:
>>
>> I am a bit stuck at the moment because while I don't want to discourage 
>> any exploration into different ways of using TiddlyWiki there is a TW5 way 
>> of doing what you are talking about, which is to use either more tiddlers 
>> or fields which you then place wherever you want them using transclusions.
>>
>> Using templates you could have the anchor tag part of the transclusion so 
>> you could navigate to a spot in an open tiddler. If you want to be able to 
>> both open a tiddler and navigate to some spot in that tiddler than we would 
>> need a more complex macro but it may be able to be done using only wikitext 
>> and simple html. Or we may need to make an action widget that does the same 
>> action as clicking on a normal link.
>>
>> -- 
>> 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 post to this group, send email to tiddl...@googlegroups.com 
>> .
>> Visit this group at https://groups.google.com/group/tiddlywiki.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/tiddlywiki/097acf29-8df9-45aa-8618-f9c4216a2226%40googlegroups.com
>>  
>>

Re: [tw] Re: Navigating and transcluding Slices...Missing Features for the atomic concept:

2016-06-17 Thread 'c pa' via TiddlyWiki 
>> Can you give an example of #3. I've never had luck calling a widget from 
inside a widget and I would like to know how it's done

Oh right. I do all my editing from dashboards because all my tiddlers are 
structured. The concept is as follows:

Analysis


# Decide on a structure for your tiddlers
#* Example "Book" would have the following fields
#** Title
#** Authors
#** Publisher
#** My random ramblings
#** My Review
#** Plot synopsis
#** ISBN Number

Discussion
=

* My random ramblings is a good candidate for the text field
* My Review, and Plot synopsis are good candidates for slices
* The title of the book should be put in the caption field because two 
books can have the same title
* ISBN is unique for books so put that in the title filed (The name of the 
tiddler - must be unique)
* Authors can be multiple so this would be a list of authors populated from 
tiddlers tagged "author"
** This requires a macro to populate it. 
** You can use crazyListHere from cpashow.tiddlyspot.com 
** As you might suspect from the name, my macro currently does all sorts of 
stuff in addition to populating a list
* Publisher is a text name populated using a select from tiddlers tagged 
"publisher"

Code a template
=

Create a tiddler to act as the "template" for books

title: "book"-- named the same as the tag used to define books
text:"""
ISBN: {{!!title}} 
Edit ISBN: <$edit field="title" />

Authors: <> 

Publisher: <$select field="publisher"> -- <$list 
filter="[tag[publisher]]">> > 
<> 

My random ramblings: <$edit field="text" />

My Review: <$edit-text tag="textarea" field="review" />

Plot synopsis: <$edit-text tag="textarea"  field="synopsis" />
"""

Code a dashboard

title: "Book Dashboard"
text: """
Add a book: <$edit-text tag="input"  tiddler="$:/temp/newbook" />
<$button>
Add book
<$action-setfield $field="currentbook" $value={{$:/temp/newbook}} />
<$action-setfield $tiddler={{$:/temp/newbook}} $field="tags" 
$value="book" />
<$action-setfield $tiddler="$:/temp/newbook" $field="text" $value="" />

Select a book to edit:
   <$select field="currentbook">
-- 
   <$list filter="[tag[book]]" variable="Current_Book" emptyMessage="""
  There are no books available 
   """>
 > >
 <>
 
   
  
<$tiddler tiddler={{!!currentbook}} >
<$transclude tiddler="book" />

"""

-- 
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 post to this group, send email to tiddlywiki@googlegroups.com.
Visit this group at https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/ff94a189-c08d-48c2-ba2a-057302348f91%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [tw] Re: Navigating and transcluding Slices...Missing Features for the atomic concept:

2016-06-17 Thread 'Mark S.' via TiddlyWiki 
Can you give an example of #3. I've never had luck calling a widget from 
inside a widget and I would like to know how it's done.

All of that, just to call a slice, which could have been made in a second 
in TWC. Am I the only one who thinks this is incredibly daunting, 
especially for new-comers?

Mark

On Friday, June 17, 2016 at 7:51:52 AM UTC-7, c pa wrote:
>
> Folks,
>
> Whenever I feel the need to include slices in my tiddlers, I implement 
> each slice using a combination of the following:
>
> 1. a field and an <$edit-text tag="textarea" $field="slicename" />  
> widget. 
> 2. the same field and an <$transclude mode="block" $field="slicename" />  
> widget.
> 3. a tag (I use edit) and a <$list filter="[all[current]tag[edit]]" 
> emptymessage=""" -- put view widget here --- """> --put edit widget here -- 
>  widget to switch the display between edit and view of the field
>
> Benefits
> 1. Allows me to stay with the tiddlywiki core path
> 2. Imposes standard slice names
> 3. Allows me to look up and manipulate all slice names
>
>
>

-- 
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 post to this group, send email to tiddlywiki@googlegroups.com.
Visit this group at https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/13a9eaf6-3e4d-45e5-a357-2ec53c16%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [tw] Re: Navigating and transcluding Slices...Missing Features for the atomic concept:

2016-06-17 Thread 'c pa' via TiddlyWiki 
Folks,

Whenever I feel the need to include slices in my tiddlers, I implement each 
slice using a combination of the following:

1. a field and an <$edit-text tag="textarea" $field="slicename" />  widget. 
2. the same field and an <$transclude mode="block" $field="slicename" />  
widget.
3. a tag (I use edit) and a <$list filter="[all[current]tag[edit]]" 
emptymessage=""" -- put view widget here --- """> --put edit widget here -- 
 widget to switch the display between edit and view of the field

Benefits
1. Allows me to stay with the tiddlywiki core path
2. Imposes standard slice names
3. Allows me to look up and manipulate all slice names


-- 
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 post to this group, send email to tiddlywiki@googlegroups.com.
Visit this group at https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/c281aa88-df28-4882-8edf-380ff8cddb60%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [tw] Re: Navigating and transcluding Slices...Missing Features for the atomic concept:

2016-06-11 Thread Jeremy Ruston 
Hi Jan

Yet two my mind there is two missing features:
>

I'd acknowledge the impact of the issues you mention, but fixing them is
1,000 times easier than introducing full support for slicing.


> -When you discover that the content you wish to change was transcluded, it
> takes some time to get to the real tiddler; in most cases I have to find
> and open with the searchbar.
> It would be practical if transclusions were clickable Links in the
> edit-Mode. Could this be done with a template or plugin?
>

My favoured approach to fix this is to introduce a mode that makes
transclusions visible, so that one can directly click on a link to open the
target tiddler.


> -It would be important to have better Security mechanisms against
> destroying links. Especially renaming tiddlers can have dangerous effects.
> It would be nice if users were shown a Modal informing about Links Lists
> and Transclusions for which the Tiddker has importance..
>

As discussed elsewhere, I'd favour support for automatically replacing
references to a tiddler when it is renamed.

Best wishes

Jeremy.



>
> Regards Jan
>
> In TWClassic when changing the Name of a Tag-Tiddler i was asked wheter I
> wished to change the tags to.
>
> On Wed, Jun 8, 2016 at 3:40 PM, Jeremy Ruston 
> wrote:
>
>> It’s clear that users want to be able to write/paste long passages of
>> text into a tiddler and then individually address sections (or
>> slices/chunks). In practice, I think that means that anything that one can
>> presently do to an entire tiddler needs to be possible with a slice:
>> transclusion, linking, searching, etc.
>>
>> That means that the system has to deal with two levels of granularity:
>> slices and entire tiddlers. Internally, everywhere that we manipulate
>> tiddlers we’d need to support slices too.
>>
>> In fact, slices would become the fundamental unit; an entire tiddler
>> would be a special case of a slice covering the entire tiddler.
>>
>> That’s where things get interesting: now we’ve redefined a slice to be a
>> tiddler (which is just what we call a fundamental discrete unit of content
>> in TiddlyWiki). Now, for performance reasons, we’d want to avoid repeatedly
>> scanning tiddlers to extract the slices; instead, we’d want to store the
>> individual slices separately so that we can efficiently address them as
>> needed.
>>
>> You can probably see where this goes: we’ve just ended up *renaming*
>> “tiddlers” to “slices”, and adding facilities to deal with sequences of
>> slices as discrete entities called “tiddlers”.
>>
>> That’s pretty much where we are today: it’s easy to combine several
>> tiddlers to make them appear to be a single tiddler: we use transclusion,
>> or macros based on transclusion like the TOC macro.
>>
>> We’ve still got the problem of dealing with long passages of text: that’s
>> where the text-slicer plugin comes in, showing one way that these long
>> texts can be split into chunks, and the chunks recombined in flexible ways.
>>
>> So, my position isn’t ideological, nor am I wilfully ignoring feedback
>> from users. But I am asserting that from an engineering perspective it’s
>> cleaner and more efficient to be dealing with a single fundamental entity,
>> and to approach the original problem from the other end: by splitting and
>> recombining.
>>
>> Best wishes
>>
>> Jeremy
>>
>>
>> On 8 Jun 2016, at 14:27, Jed Carty  wrote:
>>
>> I am a bit stuck at the moment because while I don't want to discourage
>> any exploration into different ways of using TiddlyWiki there is a TW5 way
>> of doing what you are talking about, which is to use either more tiddlers
>> or fields which you then place wherever you want them using transclusions.
>>
>> Using templates you could have the anchor tag part of the transclusion so
>> you could navigate to a spot in an open tiddler. If you want to be able to
>> both open a tiddler and navigate to some spot in that tiddler than we would
>> need a more complex macro but it may be able to be done using only wikitext
>> and simple html. Or we may need to make an action widget that does the same
>> action as clicking on a normal link.
>>
>> --
>> 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 post to this group, send email to tiddlywiki@googlegroups.com.
>> Visit this group at https://groups.google.com/group/tiddlywiki.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/tiddlywiki/097acf29-8df9-45aa-8618-f9c4216a2226%40googlegroups.com
>> 
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>>
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "TiddlyWiki" group.
>> To unsubscr

[tw] Re: Navigating and transcluding Slices...Missing Features for the atomic concept:

2016-06-10 Thread Jan 

Hi Jeremy
The concept of an atomic datastructure sounds logic.
Yet two my mind there is two missing features:

-When you discover that the content you wish to change was transcluded, 
it takes some time to get to the real tiddler; in most cases I have to 
find and open with the searchbar.
It would be practical if transclusions were clickable Links in the 
edit-Mode. Could this be done with a template or plugin?


-It would be important to have better Security mechanisms against 
destroying links. Especially renaming tiddlers can have dangerous 
effects. It would be nice if users were shown a Modal informing about 
Links Lists and Transclusions for which the Tiddker has importance..


Regards Jan

In TWClassic when changing the Name of a Tag-Tiddler i was asked wheter 
I wished to change the tags to.


On Wed, Jun 8, 2016 at 3:40 PM, Jeremy Ruston > wrote:


   It’s clear that users want to be able to write/paste long passages
   of text into a tiddler and then individually address sections (or
   slices/chunks). In practice, I think that means that anything that
   one can presently do to an entire tiddler needs to be possible with
   a slice: transclusion, linking, searching, etc.

   That means that the system has to deal with two levels of
   granularity: slices and entire tiddlers. Internally, everywhere that
   we manipulate tiddlers we’d need to support slices too.

   In fact, slices would become the fundamental unit; an entire tiddler
   would be a special case of a slice covering the entire tiddler.

   That’s where things get interesting: now we’ve redefined a slice to
   be a tiddler (which is just what we call a fundamental discrete unit
   of content in TiddlyWiki). Now, for performance reasons, we’d want
   to avoid repeatedly scanning tiddlers to extract the slices;
   instead, we’d want to store the individual slices separately so that
   we can efficiently address them as needed.

   You can probably see where this goes: we’ve just ended up *renaming*
   “tiddlers” to “slices”, and adding facilities to deal with sequences
   of slices as discrete entities called “tiddlers”.

   That’s pretty much where we are today: it’s easy to combine several
   tiddlers to make them appear to be a single tiddler: we use
   transclusion, or macros based on transclusion like the TOC macro.

   We’ve still got the problem of dealing with long passages of text:
   that’s where the text-slicer plugin comes in, showing one way that
   these long texts can be split into chunks, and the chunks recombined
   in flexible ways.

   So, my position isn’t ideological, nor am I wilfully ignoring
   feedback from users. But I am asserting that from an engineering
   perspective it’s cleaner and more efficient to be dealing with a
   single fundamental entity, and to approach the original problem from
   the other end: by splitting and recombining.

   Best wishes

   Jeremy



On 8 Jun 2016, at 14:27, Jed Carty mailto:inmyso...@gmail.com>> wrote:

I am a bit stuck at the moment because while I don't want to
discourage any exploration into different ways of using TiddlyWiki
there is a TW5 way of doing what you are talking about, which is
to use either more tiddlers or fields which you then place
wherever you want them using transclusions.

Using templates you could have the anchor tag part of the
transclusion so you could navigate to a spot in an open tiddler.
If you want to be able to both open a tiddler and navigate to some
spot in that tiddler than we would need a more complex macro but
it may be able to be done using only wikitext and simple html. Or
we may need to make an action widget that does the same action as
clicking on a normal link.

-- 
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 post to this group, send email to tiddlywiki@googlegroups.com
.
Visit this group at https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit

https://groups.google.com/d/msgid/tiddlywiki/097acf29-8df9-45aa-8618-f9c4216a2226%40googlegroups.com

.
For more options, visit https://groups.google.com/d/optout.



   -- 
   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 post to this group, send email to tiddlywiki@googlegroups.com