in this case static mean a page 'build from fixed html' - ie uses the browser to parse html into a dom, as opposed to tiddlywiki that creates (and recreates) the dom from a (dynamic) list of tiddlers.
On Thursday, March 2, 2017 at 8:24:41 AM UTC+1, Mat wrote: > > To be honest, no really great answer so far ;-) ...but, I guess the main > point with a static TW is *faster/easier for the visitor to load*. > > Wikipedia states: > > A *static web page* [...] is a web page that is delivered to the user >> exactly as stored, in contrast to dynamic web pages which are generated by >> a web application. >> > > But vanilla TW seems to qualify for both. So I wonder what disqualifies > something in TW from being exported into static? > > * anything that relies on JavaScript > > ... more? > > And, for us mortals, what are the practical consequences; Which widgets > are disabled? Other? > > BTW, this indicates it is a good idea to try to replace JS functionality > in TW core with CSS (!) when possible. Comments on this - @Jermolene ? > > > Tobias wrote: >> >> >> Static means node generated sites [snip] >> > > I'm not sure that's correct since single-file TW also can export static. > > > <:-) > -- 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 post to this group, send email to [email protected]. 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/56f2feb5-b975-4cd6-aef0-096ef427f8e7%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
