Also, there probably should be 2.1.1 Can outer storage of tiddlers (like in text files) quicken the work of TW? At least without considering search mechanisms.
On 21 ноя, 22:09, Yakov <[email protected]> wrote: > So, TW allows to create sophisticated hypertext which can be used to > describe different things. But when semantic links become stronger, > some areas can get so close that it seems natural to unite them in one > TW-document. However, a question arises about operability of big TWs. > > 1.1 What experience do you guys have with big TW-documents? > 1.2 How slow do they tend to be with size? > 1.3 Do you split them into parts and how do you do that? > > Then, some technical questions: > > 2.1 Are there any core possibilities/plugins that allow transclusions > from other documents? Can this be fast enough (faster than use of one > big TW)? > 2.2 Are there any ways to make external acceleration? > 2.2.1 Among ServerSide implementations? > > The other issue about big TiddlyWikis is that it is bad for use as a > web-page by itself. I tested it with my friend (perhaps he used > torrents at that moment) and it took about 15 seconds for him to load > the page (I tried it paired with Opera Unite). I think that time TW > was about 1Mb. > > 3. Do any ServerSide implementations accelerate this thing by sending > just pieces of information to the user, not the whole TiddlyWiki (if > this is possible)? > 3.1 Perhaps TiddlyWeb has such mechanism? > > Any other comments? -- You received this message because you are subscribed to the Google Groups "TiddlyWiki" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/tiddlywiki?hl=en.
