Ah. That helps a lot. Thanks. On Sun, Aug 4, 2013 at 4:30 AM, Jeremy Ruston <[email protected]>wrote:
> TW5 currently only implements lazy loading when it's running in the > browser talking to a TiddlyWeb-compatible server. When it syncs, it first > requests a "skinny" version of each tiddler (consisting of all the fields > apart from the text field). An attempt to read those skinny tiddlers with > wiki.getTiddler() returns just the skinny fields, but an attempt to read > one using wiki.getTiddlerText() will trigger an asynchronous load of the > full tiddler text, which in turn triggers a refresh cycle, updating the > display to reflect the newly loaded tiddler. Widgets that loop through all > tiddlers are fine; it's only if they trigger wiki.getTiddlerText() for a > tiddler that it will get loaded. > > So, the browser-based search built into TW5 will only search the text of > tiddlers that have been fully loaded. The expectation is that when lazy > loading is used in a client-server configuration, then it's the server that > really needs to handle search operations, because it's only the server that > can "see" the text of all tiddlers. So, the plan is to integrate TW's built > in search with TiddlyWeb's search API. The simplest approach is that any > local search triggers an asynchronous server side search. The results of > the search would be asynchronously loaded such that they would dynamically > appear in the local search results. > > The plan is to extend lazy loading to work to some degree for standalone > TW5 files; by default such a configuration would only have read-only access > to lazily loaded content. > > Best wishes > > Jeremy > > > > On Sat, Aug 3, 2013 at 9:47 PM, Steve Rutter <[email protected]> wrote: > >> Hopefully Jeremy, or someone intimate with TW5 code will respond. >> >> Can you explain how lazy loading works in the context of a TW being used >> to store searched-for information? I don't get how the tiddlers can be >> searched across if they are lazily loaded, or OTOH, how lazy loading is not >> destroyed the moment a single search is performed, or a macro is executed >> that has to loop through every tiddler. >> >> Thanks >> >> -- >> 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 http://groups.google.com/group/tiddlywiki. >> For more options, visit https://groups.google.com/groups/opt_out. >> >> >> > > > > -- > Jeremy Ruston > mailto:[email protected] > > -- > 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 http://groups.google.com/group/tiddlywiki. > For more options, visit https://groups.google.com/groups/opt_out. > > > -- 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 http://groups.google.com/group/tiddlywiki. For more options, visit https://groups.google.com/groups/opt_out.
