Hi Alan, Thanks for the detailed reply, nice of you to spend the time to share your thoughts and experiences thus far. Unfortunately in this day and age communication through the internet and on forums replies are generally limited down to 2 or 3 sentences at best; so well done. On my first pass I thought wow there's alot of info here and it will take a few more times reading it so i have a clear picture in my head of what and how you are doing things. I did notice though you making refence to several things which i need to go off and read a bit more about to understand like #LaunchApplicationPlugin and #ForEachTiddlerPlugin. Both of these sound like they could be of use so a little reading to understand their functionality and usefulness to my needs. My needs are in reality probably not so different to what anyone else my want so they probably can be adapted in some fashion i think, hooray and thanks for the tips to these two plugins. I definitely want to understand ''LaunchApplicationPlugin to setup several rows of buttons to launch > applications and file browsers on important directories.'' Especially the > last bit about (if i understand it right) importing directory listings..... > is that the gist of it? I have a reasonably clear goal mapped out as to: (a) what i want, (b) how i want to achieve it and (c) what sort of functionality i think i need. The problem i find being a 3week newbie is that i don't know half of what is available for TW in the way of plugins and that is forgetting about scripts, macros and anything else. The other dilemma is that when you do go trawling around you invariably find a bunch of other useful stuff which then splits the thought process (well mine, actually in two) and that is do i spend time evaluating the new plugin, test and assess its usefulness?? All of which eats up the all too limited precious commodity 'time' and when you start messing around assessing something else no matter how good the intentions are you lose sometime. Or do I ( and i probably should) continue on developing my TW (s) as originally intended and then comeback and implement updates once i have a working TW. As you can see my thoughts get sidetracked at times, although to be fair i suspect this happens to all of us when you discover a new toy (TW in this case for me). Although as i write my mixed thoughts down as i explain the point, issues and various other things something become a little clearer......food for though perhaps.
So thanks for you time, sharing you experience and pardon my little ramble :) /br Dave On Aug 1, 3:01 am, AlanBCohen <alanbco...@gmail.com> wrote: > Hi Dave, > > (Oops, I just had a flash from HAL 9000) > I'm not much more experienced than you with TW, but I can give you > some feedback. At work, I've got three TW files, index.html, > project.html, and journal.html. Index is also my home page in > firefox. I use it to keep my links to important systems, like the > ones I'm supposed to maintain, the trouble ticket system, the weather > map, the cafeteria menu, and the other TW files. I also used the > LaunchApplicationPlugin to setup several rows of buttons to launch > applications and file browsers on important directories. > Project contains the organization hierarchy of my project, all the > people, client and consultant, the employers and their team > assignments - as I have been able to compile them, along with their > skill sets (func, tech, dba, applications, etc.) as I find out who are > the 'goto's' on each topic. I started this file because I couldn't > get anyone to tell me where this info was, so I built it. > Journal has tiddlers by day and trouble ticket number, along with > using tags for categories and tiddler with the same name as the tags > setup with ForEachTiddlerPlugin routines to make nice lists. I use > the daily journals to assemble my weekly status reports. Right now, I > am finding a fair amount of cut/paste to maintain tiddlers by both > date and trouble ticket; I'm considering using 'YYYY-0MM-0DD_Ticket#' > as a tiddler key and then just use the ForEachTiddler macros to make > lists both ways. That is the core of my work system. I haven't split > this up for any problems; I just like the redundancy that even if one > file gets corrupted, the others are fine. > Since I'm on the functional side (I may be a geek, but t the center of > it all, I'm still an accountant), I can't speak to other > technologies. At work, I am limited to the management-imported > software tools and have no access to the outside internet, so there > may be better tools than I am using; there certainly are a lot of > Plugins I don't have access to. So, others may have better ways to do > things. But, if you need to do things like I've described, TW will do > them well, with a little forethought. > I have to admit, my home use is a lot less sophisticated as I have a > lot less time to work on it. But, I've got a rudimentary addressbook > up and running with a good subset of my 12 year collection in my Palm > using TWAB. Because I can't take a pda into work, I've fallen back on > a dayrunner book for my calendar and a subset of my addressbook. I'd > love to figure out how to print out from TWAB on to Running Mate-sized > paper (3.75" x 6.875", 6 hole,I think). If I could find the paper! > Other than that, I do have a local home page in TW that performs much > like the work one. I'm not yet sure what to do about a calendar in TW > yet. > I hope this helps. > Alan --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TiddlyWiki" group. To post to this group, send email to TiddlyWiki@googlegroups.com To unsubscribe from this group, send email to tiddlywiki+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/TiddlyWiki?hl=en -~----------~----~----~----~------~----~------~--~---
