Hello again,
Thanks everyone for your input.
I don't know if "display:none" means it never had to be loaded to begin
> with before though?
>
Mat, I'm not sure about this either. I've found this in reveal.js which may
suggests that the DOM needs to be involved directly in order to prevent
rendering of the hidden content:
if(!this.isOpen) {
domNode.setAttribute("hidden","true");
}
But again, I'm no JS expert to draw any such conclusions.
But if you "reverse" the matter it is easier; i.e if you click-to-scroll
> rather than scroll-to-activate. There's for example this CSS solution.
> Maybe something here.
>
I agree :)
The dynalist plugin is fully functional, and it essentially works by
> creating state tiddlers for reveal widgets that should be rendered only
> when visible in the viewport. If you study the templates used, you should
> be able to use the same logic to trigger different reveal widgets inside of
> one tiddler as well.
>
Thank you Saq for explaining the mechanism on the top level. It will be
some time before I get the level of understanding that's required here.
Also the load or first render time is more likely the most impact on the
> experience of the user
>
Tony, that's right and this impact is exactly what I'm trying to attenuate
by delaying rendering until the moment the content is visible.
It is also my view that javascript solutions should be last on the list of
> solutions where possible, and if resorted to they should be generic in
> nature, better native features than plugins. I think a search for html/css
> solutions would be the best, but then javascript is not my hammer, ie when
> you have a hammer everything looks like a nail.
>
I 100% agree with you Tony. I'm a core purist/minimalist in the sense that
I give precedence to the tools already available in the core. I'm actually
in the process of replacing all my $formula macros with the core
math/compare operators. But again, in this particular scenario it looks
like a step up to JS would be needed.
Regards,
Hubert
On Wednesday, 13 May 2020 21:54:24 UTC+1, TonyM wrote:
>
> Hubert,
>
> Keep in mind what the bottleneck on a phone is, for many it is processing,
> to my understanding using javascript is more processor intensive than CSS
> or html render to my knowledge. Also the load or first render time is more
> likely the most impact on the experience of the user, just like the splash
> screen feature makes a big difference for wiki load because people know
> something is happening.
>
> It is also my view that javascript solutions should be last on the list of
> solutions where possible, and if resorted to they should be generic in
> nature, better native features than plugins. I think a search for html/css
> solutions would be the best, but then javascript is not my hammer, ie when
> you have a hammer everything looks like a nail.
>
> I have made some large tables on a desktop and adding a reveal feature,
> like hiding columns or rows at initial load the user then exposes more with
> a click is one approach.
>
> Regards
> Tony
>
> On Thursday, May 14, 2020 at 2:36:00 AM UTC+10, Hubert wrote:
>>
>> Hi Tony,
>>
>> A possible line of enquiry may be html css overflow parameters which
>>> allow scrollable content, but you may need to set a height.
>>>
>>
>> Thanks for your suggestion. I was actually looking at CSS @media queries
>> and overflow-block
>> <https://developer.mozilla.org/en-US/docs/Web/CSS/@media/overflow-block>
>> sounds familiar but I suspect that we do need a JS element for this
>> approach. I might be wrong though.
>>
>> Thank you!
>> Hubert
>>
>> On Wednesday, 13 May 2020 13:56:32 UTC+1, TonyM wrote:
>>>
>>> Hubert
>>>
>>> A possible line of enquiry may be html css overflow parameters which
>>> allow scrollable content, but you may need to set a height.
>>>
>>> I may be missing your requirement but I hope it helps.
>>>
>>> Regards
>>> Tony
>>>
>>>
--
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 [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/tiddlywiki/ae74efa5-a175-42df-bcc8-2845a233eda1%40googlegroups.com.
