Hi Jeffrey, replies below..
On Jun 6, 9:01 pm, Jeffrey Goodman <[email protected]> wrote: > Questions: > Is there a maximum reasonable size for a TiddlyWiki? There are upper limits that I experienced in the early days with browsers less powerful, but I have a 2 year old tw document that i update daily that is 2001225 bytes in 2199 selected tiddlers with no big slowdowns on firefox 3.6 The tip I found on this list was to turn off animations under Options > uncheck EnableAnimations; that really helped! > Is it best to create several related or included files? The nice thing is you can link to external assets with links within the tw document or have them embedded within iframes or binary base64. Explore the many wonderful plugins like FileDrop plugin from places like Eric's tiddlytools.com > If I create several separate files is it possible to have them display > with different colors in the Primary File? Yes, you can create many separate tw documents each with their own concern/area of interest and style and link them with a master tw file like Udo's IncludePlugin http://tiddlywiki.abego-software.de/ TiddlyWiki supports custom css http://tiddlywiki.com/#CustomCssClass a way to style in different formats ie display with different colors in the Primary File > What kind of issues do I need to take into consideration that I might > not yet be aware of? my advice: go slow and play, trying different things. Search the group and tiddlywiki.org for ideas, solutions. As for format, I found that Tiddlywiki is great because your data is text and its yours. Not locked in the cloud or binary proprietary format and self-contained. You can throw it in a cloud like DropBox, TiddlySpot or a TonidoPlug computer. it supports common format handling like csv via great plugins like Erics http://tiddlytools.com/#CreateTiddlersFromCSV which maybe some of that FileMaker or other database tables export to. Also great is his ExportTiddlers plugin > -- Don't want to discover later that I should have done things > differently, as data entry and references become extensive and > difficult to export and rebuild. I found after making several versions of my master that I liked over a long time of switching different plugins that overlap in functionality, tweaking many shadow tiddlers- ViewTemplates, toolbars, stylesheet that simple was better for me. Function over beauty. You can have both as you will see, but for me the time to get something working well overrode the time for play. TiddlyWiki is an endless TinkerToy. I try to keep my markup simple, content having primacy and not have a lot of functional <<macros>> in my tiddler bodies so that if I need to parse or export the content someday, it won't be as painful or perplexing. The nice thing is the content is contained within pre tags in div sections but to keep it even simpler i try to contain a thought within a line since I'm not a programmer and the unix shell plays nice with lines. To further help externalize formatting out of the tiddler body, I enjoy tobias' cycleTag plugin with Eric's SetColorCode script for a bit of Joe's Siglet like coloring. Again I found this stuff from the group. Search and have fun! Best, tony -- 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.
