Hi Dave At the moment, running under Node.js is more about having the convenience of managing your tiddlers as individual files. When a TW is built it includes a representation of all tiddlers, whether it is built for serving to the browser via tiddlywiki --server, or built as a standalone HTML file.
The reason that Firefox is crashing is because all of those images are packed into the TiddlyWiki file as base64 tiddlers. Unpacking and displaying them will be much less efficient than working with an ordinary independent image file. TiddlyWiki5 does support lazy loading, where the original TiddlyWiki file is built with "skinny tiddlers" that omit the body, but include the metadata (tags etc), and then the body is loaded on demand. Lazy loading is currently only implemented when running on TiddlyWeb/TiddlySpace, but the plan is to support it natively too. What's needed is a way of specifying tiddlers within a wiki folder that should be served skinny. For example, a new filter operation like "[is[image]]". For better performance with images, it would be useful to be able to render images as ordinary <img src=...> tags, rather than base64. I'll investigate some quick hacks that will get things working for you, Best wishes Jeremy On Tue, Jan 28, 2014 at 7:27 PM, David Gifford <[email protected]> wrote: > Still trying to drive trucks over your bridges, Jeremy! But seriously, > that was my whole motivation for using node.js, because I thought that it > saved the tiddlers as separate files and loaded them as needed, thus > reducing filesize. But if node.js has the same limitation as standalone, > then I am not sure what the advantage is, other than playing around with > putting tiddlers in folders? > > Dave > > > On Tue, Jan 28, 2014 at 2:25 PM, David Gifford <[email protected]> wrote: > >> 145MB is the filesize. And Firefox gave me an error when I tried to click >> on it. >> >> Dave >> >> >> On Tue, Jan 28, 2014 at 2:05 PM, Jeremy Ruston >> <[email protected]>wrote: >> >>> Hi Dave >>> >>> It's actually not Node.js that's running out of memory here, it's the >>> browser. It's not normal behaviour, though, and I've not seen anything like >>> this reported before. It's certainly not something that's associated with >>> running Node.js. >>> >>> You say that you've got 2000 tiddlers in there with many images, perhaps >>> it's just that you're generating a sufficiently large TW file to confuse >>> the browser. >>> >>> If you save the wiki as a standalone HTML file, how big is it? >>> >>> tiddlywiki --rendertiddler $:/core/save/all index.html text/plain >>> >>> Another possibility is that you've inadvertently set up an infinite loop >>> - TW tries to protect you from circular transclusion, but if you somehow >>> managed it, the symptom would likely be an out of memory error. >>> >>> Best wishes >>> >>> Jeremy >>> >>> >>> >>> On Tue, Jan 28, 2014 at 7:00 PM, David Gifford <[email protected]>wrote: >>> >>>> This is a pretty important question for me. If I don't get this >>>> resolved, node.js will not be worth investing my time and effort in. >>>> >>>> Dave >>>> >>>> >>>> On Tuesday, January 28, 2014 7:43:52 AM UTC-5, David Gifford wrote: >>>>> >>>>> Hi all >>>>> >>>>> >>>>> In node.js, using 5.0.6 beta, Windows 8.0, Firefox, I am starting to >>>>> get the message below. Not sure what memory it is out of. This is a brand >>>>> new computer with lots of memory. Tried clearing the browser history, etc, >>>>> and that hasn't helped. Amazingly, though, the tiddlers did manage to >>>>> save, >>>>> despite the error message. Any ideas? I have just over 2000 tiddlers, many >>>>> of them are image tiddlers. And I tweaked the tiddlerinfo panel so that >>>>> there is an extra tab that displays the title, tags and text of all >>>>> tiddlers tagged with that tiddler's title. >>>>> >>>>> Here is the text of the error: >>>>> >>>>> Internal JavaScript Error >>>>> Well, this is embarrassing. It is recommended that you restart >>>>> TiddlyWiki by refreshing your browser >>>>> uncaught exception: out of memory >>>>> >>>> -- >>>> 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 a topic in the >>> Google Groups "TiddlyWiki" group. >>> To unsubscribe from this topic, visit >>> https://groups.google.com/d/topic/tiddlywiki/dIrdnKRfmj8/unsubscribe. >>> To unsubscribe from this group and all its topics, 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. >>> >> >> >> >> -- >> David Gifford >> Christian Reformed World Missions, Mexico City >> > > > > -- > David Gifford > Christian Reformed World Missions, Mexico City > > -- > 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.
