Chris Dent於 2013年5月21日星期二UTC+8上午3時34分33秒寫道： > > On Sun, 19 May 2013, G.J.Robert wrote: > > > Adding a couple of remarks: I do sense the increase of TSpace server in > > last months (also my ISP has also improved their cables...), and today > my > > 15~17MB space loads in just 20s on my home laptop, it's really a great > > improvement! I guess I can reconsider to move back to online editing. > I'm > > not sure how fast can it load in less stable and firm environment like > > mobile networks (sadly we don't have LTE in Taiwan yet, and network > speed > > here is never comparable to those in the States and Europe) > > We've recently discovered the extent to which reaching half way > round the world has an impact as well. > > There's a change coming[1] in TiddlyWeb which may speed things up a > bit more (with standard TiddlyWiki) but is unlikely to make a huge > difference in a space your size: The sheer number of bytes that need > to be transmitted in a row is the controlling factor (thus the > desire for some kind of lazy solution). > > > I have just also tried "_tiddlywiki" of @apps on one of my smaller > spaces. > > It loads fine, only that it seems to break some functions or some > plugins, > > so my space looks a bit different in the top bar (it seems that the top > bar > > from other included spaces gets rendered first instead of my > > customizations), and I've got "ReferenceError: hasClass is not defined" > > every time a tiddler is opened. > > Yes, there's definitely some work that needs to be done to make > _tiddlywiki work better. It needs more brains. If there were > unlimited time and energy I'd really love to get it correct and make > it the default way to view a tiddlywiki produced by TiddlySpace, > when online. > > If you have a chance could you describe how you imagine the ideal > lazy system for tiddlyspace + tiddlywiki would work? >
Hi Chris, Thanks for your kind listening and responding. I'm not a coder at all but I'll try my best on this. Let's recall when TiddlyWiki just get so well noticed in it's 1.x age. There was an adaptation called "LesserWiki" if some people remember it. (discontinued long ago and sadly I can't even find it's official site now) It seemed to use AJAX methods behind the curtain so every tiddler was retrieved when a link is clicked (a throbber indicating the loading is in progress). Ever since seeing it, I've always hoped that TiddlyWiki itself has this kind of serverside backend. I imagined that on page loading only necessary frame codes and plugins are loaded and rendered, with of course the DefaultTiddlers and tiddler transcluded on Sidebar, MainMenu, Topbar etc. are loaded at the first place. The rest of all the tiddlers are treated like a backend database and are only retrieved when being clicked/searched/inquired for. Of course as I further used and got knowledge about a little how TW works, I realized that making modern TW (even the classic edition) load lazily with so many transclusions, plugins, layout and environment settings is definitely not easy. For example, how will ForEachTiddlerPlugin behave when most of the tiddlers are not loaded at all? Will it throw complete and desirable output when the macro is executed? Will it take too long as loading the whole TiddlyWiki? And what I'm thinking may go way too far from the original design of TiddlyWiki as a single HTML file with all tiddler data as loaded but hidden divs. Wait a moment, am I talking about "loading on demand," not "lazy loading"? Oh sweet Jesus. Pardon me if my concepts are so confused. My biggest wish is the AJAX "on demand" way, but at least, I like enough the way "@apps _tiddlywiki" loads the spaces. Although it is not "on demand loading", but it does reduce the initial time to render the page frame and does load all the data eventually after very acceptable delay. If I can find a direction to pay suggestions, how about distinguishing more clearly between those tiddlers definitely needed initially (all the plugins, stylesheets and tiddlers making up the whole layout) and those irrelevant to the structure (only playing as data), and making sure that the necessary ones get loaded first, so that the initial page is 100% usable and correctly operational? Pardon me if this is not the problem now. And also in my guess, whether we are doing "load on demand" or "lazy loading", the essential set of tiddlers consisting of the page may be the same, isn't it? Is the difference only in whether the page keeps loading all the other tiddlers until finished, or the page enters the standby mode awaiting user actions to retrieve the other tiddlers? (Btw, I have also just tested "@apps _tiddlywiki" lazy loading on my big big 15MB space. Besides of the incomplete structure got rendered, this time the biggest problem is that the page data never finished loading. The percentage is always at 81%. Does the server timed out because of the size of my space?) > > Thanks. > > [1] > > https://github.com/tiddlyweb/tiddlyweb/commit/de43319c459e5ea873f1129352a47f24c75c92f1 > > > -- > Chris Dent http://burningchrome.com/ > [...] > -- 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?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
