Hi Jeremy and others, Just getting home for the day from teaching.
1. I didn't take your comments as negative in any way. And I have no personal investment in this discussion. I am just throwing out an idea to see if something sticks to it or not. 2. Simplenote, looking at it again, is pretty limiting compared to TiddlyWiki. Just for starters, I see no easy way to create hyperlinks in it. Let alone other formatting, things like tables, list filters, etc. So that is definitely nowhere near an option. It is only for the simplest of notes. 3. Jeremy, you mention Node.js as the solution I am looking for. When I tried out Node.js in January of last year, I recall it slowing down with images just like standalone TWs do. And that made me imagine that eventually, even a large number of text tiddlers could slow it down, too. That is why I didn't continue pursuing it, because it didn't seem to offer me that much of an advantage over the standalones regarding the filesize-and-image-slowdown issue. Has there been some change in Node.js to make it more responsive? Or some workaround? Also, even if Node.js became a solution for me, and I am open to that, it would be too complicated for my audience to consider. 4. There are some comments made above that don't sound like my original idea. So let me restate it in another way. My idea, at least for my website, is simply to have one standalone TW in which I add pretty links by hand to external html files that also open up with a browser, and that those html files be instantly and easily editable like a tiddler is, with wiki formatting etc. I currently have the first part, the standalone TW with the pretty links (see recursos.giffmex.org for an example). It's the quickly editable html files, and a way to quickly create them on the fly, that I don't have. 5. I admit to some confusion in my way of describing my ideas, because in part I am trying to think of something that would work for my website, and in part something that would work for me, for my notes. The website requires small files that open quickly and don't depend on anything too complicated for the user, like the need to acquire other software or learn node.js to view the files. For my own use I could be more flexible about methods, but the scale would be much larger. 6. I am guessing the way to go for my own use would be to have a central TW and a series of other TWs, where the tiddlers in the central TW have only the title of a term, the appropriate tags, and permalinks to tiddlers in other TWs which would contain text, etc. Or, assuming good news from Jeremy re: node.js, to use that. Blessings Dave On Tue, May 5, 2015 at 2:34 PM, Jeremy Ruston <jeremy.rus...@gmail.com> wrote: > Hi Mark, Andreas > > Minor corrections: > > > in a TW EVERY tiddler is ALWAYS loaded, meaning that while you can > store a million tiddlers in a wiki, these million tiddlers are completely > loaded into memory and parsed out from the html, when you open the wiki > > TiddlyWiki already supports externally stored tiddlers via the > _canonical_uri field. They work for images, PDF files. > > > So in theory your approach of spreading out a wiki may be workable, but > I feel that it don't plays well with the vision of having a single file > with everything in it > > The vision of TiddlyWiki is not just to be able to work as a single HTML > file, but also extends to exploding that file into individual files. That > part of the vision is currently only realised in the Node.js configuration. > > > So while you are correct with your assumption that the static files > would contain a fair bit of javascript complexity, it is in theory possible > to make it a reality > > With Dave's idea, a bunch of separate HTML files could share a single > JavaScript file via script tags. > > > Yes, a weakness of TW is that it doesn't scale well. > > The main issue that we see at the moment is that embedding large > images/PDFs doesn't work well. There are users out there with TiddlyWiki > documents containing up to the tens of thousands of tiddlers. Of course, > there's the Node.js configuration which scales even better (and with some > additional work will scale as well as anything else out there). > > Best wishes > > Jeremy > > > > On Tue, May 5, 2015 at 5:30 PM, 'Mark S.' via TiddlyWiki < > tiddlywiki@googlegroups.com> wrote: > >> For personal use, there's nothing quite as flexible as TW. But it doesn't >> scale up without problems. >> >> Something like Simiplenote makes it easy to quickly publish and update >> information meant for consumption by others. A published (static) page >> updates whenever the corresponding note in Simplenote is updated. >> >> If you have your own website, you could have your own MediaWiki. That >> will scale-up and allow in-place editing to authorized individuals. >> >> What it comes down to is that, one way or the other, if you use TW for >> managing your data, you will have to use a separate mechanism to publish >> low-overhead data. So the question is, what publication process will >> involve the least hassle for yourself? >> >> Mark >> >> >> >> >> >> On Tuesday, May 5, 2015 at 8:26:55 AM UTC-7, David Gifford wrote: >>> >>> Hi Mark, >>> >>> I am sharing them via my website on Dreamhost. >>> >>> I will have to look at Simplenote again to see what you mean. I remember >>> it not being the tool I wanted when looking at it a while back. >>> >>>> >>>> -- >> 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 tiddlywiki+unsubscr...@googlegroups.com. >> To post to this group, send email to tiddlywiki@googlegroups.com. >> Visit this group at http://groups.google.com/group/tiddlywiki. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/tiddlywiki/deb0b1a7-3901-4619-809a-0b2b3b4eb5a3%40googlegroups.com >> <https://groups.google.com/d/msgid/tiddlywiki/deb0b1a7-3901-4619-809a-0b2b3b4eb5a3%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> >> For more options, visit https://groups.google.com/d/optout. >> > > > > -- > Jeremy Ruston > mailto:jeremy.rus...@gmail.com > > -- > 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/oVhlyEvPnGk/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > tiddlywiki+unsubscr...@googlegroups.com. > To post to this group, send email to tiddlywiki@googlegroups.com. > Visit this group at http://groups.google.com/group/tiddlywiki. > To view this discussion on the web visit > https://groups.google.com/d/msgid/tiddlywiki/CAPKKYJa_E39Qya9p%3D0gxCNrnTMWGmor%2BqtRpeWGh8OJ4sLj84Q%40mail.gmail.com > <https://groups.google.com/d/msgid/tiddlywiki/CAPKKYJa_E39Qya9p%3D0gxCNrnTMWGmor%2BqtRpeWGh8OJ4sLj84Q%40mail.gmail.com?utm_medium=email&utm_source=footer> > . > > For more options, visit https://groups.google.com/d/optout. > -- 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 tiddlywiki+unsubscr...@googlegroups.com. To post to this group, send email to tiddlywiki@googlegroups.com. Visit this group at http://groups.google.com/group/tiddlywiki. To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/CANE%3DBF%2BgkPSHTO_kSA28HtBjndQfRkd0hqqwbFdPWGz6RLzo8g%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
