...<$tiddler tiddler=<<currentTiddler>>><div class=<<frame-classes>>>...
...<$tiddler tiddler=<<currentTiddler>>><div class=<<frame-classes>>>...
TypeError: this.getLastFrame(...).getBoundingClientRect is not a function
<$tiddler tiddler=<<currentTiddler>>>
\define frame-classes()tc-tiddler-frame tc-tiddler-view-frame $(missingTiddlerClass)$ $(shadowTiddlerClass)$ $(systemTiddlerClass)$ $(tiddlerTagClasses)$\end\define folded-state()$:/state/folded/$(currentTiddler)$\end<$set name="storyTiddler" value=<<currentTiddler>>><$set name="tiddlerInfoState" value=<<qualify "$:/state/popup/tiddler-info">>><$tiddler tiddler=<<currentTiddler>>><div class=<<frame-classes>>><$list filter="[all[shadows+tiddlers]tag[$:/tags/ViewTemplate]!has[draft.of]]" variable="listItem"><$transclude tiddler=<<listItem>>/></$list></div></$tiddler></$set></$set>
\define frame-classes()tc-tiddler-frame tc-tiddler-view-frame $(missingTiddlerClass)$ $(shadowTiddlerClass)$ $(systemTiddlerClass)$ $(tiddlerTagClasses)$\end
\define folded-state()$:/state/folded/$(currentTiddler)$\end
<$set name="storyTiddler" value=<<currentTiddler>>><$set name="tiddlerInfoState" value=<<qualify "$:/state/popup/tiddler-info">>><$tiddler tiddler=<<currentTiddler>>><div class=<<frame-classes>>><$list filter="[all[shadows+tiddlers]tag[$:/tags/ViewTemplate]!has[draft.of]]" variable="listItem"><$transclude tiddler=<<listItem>>/></$list></div></$tiddler></$set></$set>
--
You received this message because you are subscribed to a topic in the Google Groups "TiddlyWiki" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/tiddlywiki/_nZI7Kt-UR0/unsubscribe.
To unsubscribe from this group and all its topics, send an email to tiddlywiki+unsubscribe@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/7a7359b3-cf27-4606-b740-386a6d0bfef1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Yes, of course.
Il 31/Ott/2017 23:02, "BJ" <bugg...@gmail.com> ha scritto:
The problem is that when the next version is released, if the shadow tiddler you modified has been updated you will have to redo all you changes in the context of the new shadow tiddler.--
On Tuesday, October 31, 2017 at 9:35:53 PM UTC+1, mauloop wrote:Why not?Probably I will be burned as an heretic, but I have already overwritten the $:/core/ui/PageTemplate. This let me have custom view and edit templates, dinamically selected based on a tiddler field. It works for me (at least it seems to work since about one week ago, that is when I did it). What's wrong in this?However I appreciate very much your suggestions. Thanks for the attention.)+(auloop
You received this message because you are subscribed to a topic in the Google Groups "TiddlyWiki" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/tiddlywiki/_nZI7Kt-UR0/unsubscribe.
To unsubscribe from this group and all its topics, send an email to tiddlywiki+...@googlegroups.com.
To unsubscribe from this group and all its topics, send an email to tiddlywiki+unsubscribe@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/e8f0efcb-9c20-400f-8960-bada2374c31a%40googlegroups.com.
Also I don't understand the meaning of:
<$tiddler tiddler=<<currentTiddler>>>since the TiddlerWidget reference tells: The TiddlerWidget is used to set a value for the current tiddler variable. I fell in a loop. Please, help me.
The TiddlerWidget is used to set a value for the current tiddler variable, valid within the scope of the TiddlerWidget.The tiddler widget assigns several useful CSS classes to variables that it creates:
- - missingTiddlerClass
- - shadowTiddlerClass
- - systemTiddlerClass
- - tiddlerTagClasses
<$tiddler tiddler="MyOtherTiddler">
<div class=<<missingTiddlerClass>>>
<$transclude/> <- this shows nothing if the tiddler doesn't exist.
</div>
</$tiddler>
... and I inserted some newline to make the code more readable. When I saved the "beautified" ViewTemplate it happened that clicking on any link raised a Javascript error.
Starting with TW 5.1.15 (the next version as of this writing) we will have a new \whitespace pragma.
\whitespace trim
\whitespace notrim
Is there someone here about that could help me to understand the reasons for the behaviour I described?And also the meaning of <$tiddler tiddler=<<currentTiddler>>>?
Is there someone here about that could help me to understand the reasons for the behaviour I described?And also the meaning of <$tiddler tiddler=<<currentTiddler>>>?
I assume this is part of default TW action going into play that behaves untypically--i.e. HTML IDs don't work in TW as you'd normally think?
They are reserved for Tiddler Titles only, I think.
I found it VERY confusing when I started--that a tiddler can't use IDs (#) within it for normal business.
I hope I will find the time to learn more about HTML IDs.
But the fact is (by the point of view of an absolutely HTML newbye, that is just what I am) that i simply clicked between two tags and pressed the ENTER key, unaware of IDs, links mechanism and all that stuff.
I think that having the chance to override the shadows tiddler to customize the wiki to own's taste is a great feature.
This combined with macros and widgets gives to people like me the opportunity to build a wiki that fit exactly their needs.
But if one falls in troubles with strange behaviour like this there could be chances that one gives away thinking the work is to hard for him.
I spent about an hour rolling back my changes one by one to find the trick. :^(((
Now click on any link in the page (both in the story or in the sidebar): it seems that tiddlers are opened, but the page doesn't scroll to the clicked tiddler. Il looks very strange to me that simply adding a newline could change the wiki behaviour.
If a scrollable widget can't handle thetm-scroll
message because the inner DIV fits within the outer DIV, then by default the message falls through to the parent widget. Setting the fallthrough attribute tono
prevents this behaviour.
I first found something similar on a wiki I was working on, with a little different result. In that case I had a working custom ViewTemplate with more changes and I inserted some newline to make the code more readable. When I saved the "beautified" ViewTemplate it happened that clicking on any link raised a Javascript error.
TypeError: this.getLastFrame(...).getBoundingClientRect is not a function
Let's try a ASCII-art for the "fallthrough" mechanism:child|+-- parent|+-- grandparent
Thanks for your several answers. I'm reading them on my phone, that is not much comfortable.
I plan to come back soon to review everything carefully and look at the threads, videos and other resources that you suggested.
But I can't wait to thank you for your kindness and express my admiration for your skill. You are a mine of knowledge.
I've already posted here in the past and every time I found kind people that spended some of their time for me. Thanks to everyone.
)+(auloop
But I can't wait to thank you for your kindness and express my admiration for your skill.
You are a mine of knowledge.
I've already posted here in the past and every time I found kind people that spended some of their time for me. Thanks to everyone.
)+(auloop
That's a very nice explanation, Mario.
But it begs the question: Why is a 'line feed' rendered as a DOM object (div even?) and not just wrapped up in either the next or prior element?
About the scroll mechanism -- does it actually send out a series of scroll commands in order to line up the tiddler?
Does it use any of the old HTML technology?
I ask because the sidebar links seem to be usuing <a href=*> .
Yea, ... You found a rare behaviour, that I did also experience some time ago, ...
At tiddlywiki.com there are 3 story-views- classic (default)- pop- zoomingEach of them treat "showing, removing, scrolling" tiddlers in a slightly different way. ... There are several other plugins.
I first found something similar on a wiki I was working on, with a little different result. In that case I had a working custom ViewTemplate with more changes and I inserted some newline to make the code more readable. When I saved the "beautified" ViewTemplate it happened that clicking on any link raised a Javascript error.
TypeError: this.getLastFrame(...).getBoundingClientRect is not a functionThis shouldn't happen, because there are several "stranger" tests along the line. The point is. We can't navigate to whitespace, because the browser API doesn't provide enough info. We can only navigate to "wrapping" DOM elements.
--
You received this message because you are subscribed to a topic in the Google Groups "TiddlyWiki" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/tiddlywiki/_nZI7Kt-UR0/unsubscribe.
To unsubscribe from this group and all its topics, send an email to tiddlywiki+unsubscribe@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/50fc682d-ec05-4ae0-8293-9eba04dea15f%40googlegroups.com.
What is not working? I changed the filter that PageTemplate/story uses to select tiddlers to display in order to make it choose just the one listed in {{$:/History list!!current-tiddler}} or alternately the first one in {{$:/Story list!!list}}.This makes more sense if you set new tiddlers opening policies to open always at the top, so when you close a tiddlers you fall back to last one viewed (in most cases).This works for me, if this was the part you refer as not working, but it's not required for the rest of the template to work.I appreciate your feedback. Thanks in advance,)+(auloop
Il 05/Nov/2017 08:47, "BJ" <bugg...@gmail.com> ha scritto:
This is quite advanced stuff! Your solution looks good, although the storyview seems not to work.
It is good to see how some else solves the same problem.
On Sunday, November 5, 2017 at 1:33:08 AM UTC+1, mauloop wrote:Finally I was able to make your typestemplate working. If I would have it before it would have saved a lot of work to me.I did something similar, even if with wiki syntax macros only. If you would like to take a look here it isThanks for your help.)+(auloop
Il giorno mercoledì 1 novembre 2017 19:50:44 UTC+1, BJ ha scritto:I've put a demo here:
http://typestemplatedemo.tiddlyspot.com/
On Wednesday, November 1, 2017 at 12:48:29 AM UTC+1, mauloop wrote:@BJStill cannot make your typestemplate plugin work. I tried it directly on your site. Maybe for this I should better open a new thread.
--
You received this message because you are subscribed to a topic in the Google Groups "TiddlyWiki" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/tiddlywiki/_nZI7Kt-UR0/unsubscribe.
To unsubscribe from this group and all its topics, 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 unsubscribe from this group and all its topics, send an email to tiddlywiki+unsubscribe@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/c4cb3647-5740-4a6b-a394-da04b01dae36%40googlegroups.com.