> And decided to try the two options presented (TWS and TiddlyWeb). I > started with TiddlyWeb because of ease of access to virtual-env/python > stuff (simple package install). My initial trials weren't successful (I'll > post a few notes at the bottom for open discussion). I bit the bullet and > compiled node. However, I wasn't able to point it at my previous > tiddlywiki and maintain the ability to save. So, back to TiddlyWeb and a > simpler attempt (installing into the common bag vs a custom one). After > some work, I was finally successful in importing my previous work. I > wanted to share my notes with others who may find themselves in this > situation.
I'm glad you were able to get it to work, sorry it wasn't as straightforward as it should have been (more details on that below). I've copied the details of your posting to http://tiddlyweb.tiddlyspace.com/TiddlyWeb%20On%20Fedora That space is the target for the migration of the content which has been at http://tiddlyweb.peermore.com/ > 4. Accounts: > > # Optional, but I prefer it. > twanager adduser JamesLampton password > > Login:http://127.0.0.1:8888/challenge If you're going to use a login, you may wish to learn about using policies: http://tiddlyweb.tiddlyspace.com/policy That is, if you want authorization. If you're just after having your name as the modifier of the tiddlers then you're set. > --- To Chris Dent/Wish list --- Hi! > Thanks for writing TiddlyWeb. As someone new to TW, I would like to say > that it's a bit daunting. I think starting from scratch seems well > understood, but coming to TW with existing data was challenging. I hope > this snippet provides a useful example. Yeah, there's quite a learning curve, and it is definitely not welcoming for existing TiddlyWiki users who may have quite a bit of content. There's a very simple reason for this that's never been adequately addressed: I'm not an active user of TiddlyWiki so while I'm engaged by the task of detailing the technical capabilities of TiddlyWeb and how it can work with TiddlyWiki, I'm not sufficiently knowledgable of the paths by which a TiddlyWiki savvy person might wish to come in to the system to create a friendly but also cogent introduction. The early hope was that an existing TiddlyWiki user or users would be sufficiently motivated by the advantages that TiddlyWeb brings them that they would add to the growing corpus of TiddlyWeb documentation. A few years later we are still looking for that person. Anyone who is interested I'm willing to make a member of the space linked above and they can edit to their hearts content, and I will very very very happily answer any questions. I probably know the answer to most questions: the issue is that I don't know the questions. > Initially, I attempted to break my stuff into a separate bag. I could see > this being useful to others in my lab, so I thought I could play with > breaking things out assuming I would have others in play. Adding data into > a bag is straightforward, but pointing the browser at the bag didn't have > options for saving. The documentation for TW seems mainly directed to > developers? I did find some more linear stuff for setting things up (in > Apache:http://tiddlyweb.com/docs/TiddlyWebInstallationForWindows.html), > but it didn't address the multi-user stuff I was looking for. The missing pieces of the pie here are probably two things: One is that tiddlyweb all by itself has no functionality for support tiddlywiki writing back to the server from within tiddlywiki. For that the tiddlywebwiki package is used (which you've already got). What that provides, besides the power to generate tiddlywikis, are the tiddlers within the system bag. In there are plugins such as TiddlyWebAdaptor which are used to send content back to the server. If a TiddlyWiki doesn't contain them it won't know what to do to be able to save. Two is the concept of recipes[1]. A recipe assembles a suite of bags into a usable collection. The "default" recipe which you accessed from your link has the system and common bags. So for your other bags you need to put them in a recipe that also includes system. [1] Here's a starting point for info on recipes: http://tiddlyweb.tiddlyspace.com/recipe > To address your point about bridging the gap between systems such as TW and > TWS, I think posting notes on how to contribute documentation, may be a > start. I would considering helping out, but being a PhD candidate limits > my ability to do any significant heavy lifting at this time. However, I > think the current postures in browser development beg for addressing these > issues to help tiddlywiki adapt and survive. This page has been pointed out a few times: http://tiddlyweb.tiddlyspace.com/MetaDocs But I suspect the pointing needs to happen more actively and regularly. I agree that "the current postures in browser development" (excellent turn of phrase by the way) do make now the right time to make some headway. Thanks very much for your comments. The feedback is what keeps projects like these from fading away. -- 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.
