Thanks all. Suffering from a bit of information overload now :).
I'm usually one to do well in small environments that are well contained. Back in the day when I was a (hobby) programmer, I faired well in Borland Pascal, Delphi, and also in Java, because those environments were small, contained and had great (context based) help documents. I never got into C, C++, perl, python, linux, or any of those languages/environments, mostly because I didn't like the language or because the context was so large. Having access to thousands of libraries is not always an advantage. Not when they are there all at once. And even if they are, they have to be presented to you in a timely, orderly fashion... in small chunks. In such a way that it expands on what you already know. Building blocks, expanding on a fundament. TiddlyWiki is easy to start out with. It's just a wiki, you write wiki text and that's that. First you edit your MainMenu, your SiteTitle and your SiteSubtitle. Then you start messing with some templates: StyleSheet, ColorPalette, there are not many. You read StyleSheetColors and StyleSheetLayout to determine what you need to overrule, and they are there, easy to find. Then you dive into PageTemplate and ViewTemplate, and that's that. But then you start dealing with Macro's, with Plugins, and you start reading the plugin code, and there is SO MUCH... that you don't understand. The information on the tiddlywiki.org is not comprehensive and well-laid out. That is, it's not a manual. The plugins use a lot of weird formatting that is hard to understand without explanation. It's difficult to know what core functions are available, especially since I hardly know any javascript. So thank you for your suggestions, I've noted them all, will check them out at some later time. I guess I have to familiair myself with the system some more first. Reading templates and macros and code is hard when there is so much formatting and constructs you don't understand. So.. one thing at a time. I guess my choice to use multiple records per tiddler is indeed a hard one... will have to check that out sometime. I believe it should be possible to use a macro to retrieve "record" sections from tiddlers, make them into a virtual temporary tiddler, and then use the slicing mechanism on them and all the other existing functionality to work on that. But the idea of having a single-record tiddler and using a custom ViewTemplate on that to render it into something special is also a beautiful thing. Okay, it is possible to adapt the standard ViewTemplate using the HideWhen plugin and others, in order to make it do a zillion things, but that makes it very hard to export this application as a whole, as a package you would offer to others to download like Shulman does with his site. In any case, I will continue my education ;). I have just studied the concept of transclusions. I had come across them in Shulman's BookmarkList, and he has used transclusions there to eliminate inline javascript code. @Mark S.: You have explained to me the /% ... %/ syntax, but why does this content sometimes show up? I will cite a shorter version of BookmarkList here: --------------------------- /% !info |Name|BookmarkList| |Source|http://www.TiddlyTools.com/#BookmarkList| <-- why does this table show up in the rendered tiddler? Oh wait, I think I know. Usage <<< <--- what does this marker do? {{{ <<tiddler BookmarkList>> }}} @@display:block;height:15em;overflow:auto;<<tiddler BookmarkList##show>>@@ <-- is this double-@@ necessary to activate the CSS? <<< !end <-- does this !end have any special purpose other than delimiting the section? Could it also have been !boogiemaster? !out $1 <-- I know this is a transclusion marker !end !show <<tiddler BookmarkList##out with: {{ var out=["My Bookmarks\n"]; .... .... out.join("\n----\n"); <-- I know this tranclusion uses last expressed value of this javascript section, in this case the value of out.join() }}>> !end %/ <-- all of the previous content was wrapped up in these markers, but still it renders.. is that because it is transcluded through the below <<tiddler BookmarkList##show>> ? <<tiddler {{var src='BookmarkList'; src+ (tiddler&&tiddler.title==src?'##info':'##show');}}>> <-- ingenious way to show extra content depending on the way it is used ------------------------- BTW, I would be willing to write some real TiddlyWiki manual at some point (if I can get myself to do it). It would not use TiddlyWiki as an environment, but rather some real standalone wiki that uses pages. It could be done in tiddlywiki.org but I probably would prefer a standalone wiki using a theme that looks a lot nicer than tiddlywiki.org. (WHY does almost everything involving TiddlyWiki look so freakin primitive? Almost like web2.0 never happened....) Grtz, Xen. -- 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.
