#Voodoopad for windows code#
#Voodoopad for windows mac#
#Voodoopad for windows windows#

These are then divided into subcategories as necessary. So for example, in the wedding wiki, the high level categories are: Time, Place, Invitations, Dress, Guest list, Reception, Ceremony, Pre-wedding party, Other, Attendants, Music. The other general subject wikis I organize by subject. Class notes is broken down by date, book notes by chapter, and other by subject. The school wiki is divided into classes, then each class is broken down into class notes, book notes, and other. It also makes it easy to cross reference notes from other classes and other days. This is the most brilliant use, I think, because I can make new entries for words and concepts, and these words will be conveniently linked to their definitions in all pages relating to my notes. The fifth one is for school - I use it to take notes in all my classes. I have five separate wikis (separate because I don't want them to cross-link with each other):Д¬hicago (to keep track of stuff when we were in the process of moving)Д¬rafts (for keeping track of craft projects and ideas) Go forth and let the unholy writings of the followers of Merlin Mann and David Allen seep into your noggin. To wrap it up, I would be remiss if I didn't mention the 43 Folders wiki page on VoodooPad and highlight Getting Things Done with VoodooPad.

#Voodoopad for windows code#

I didn't get to the part where I added XML-RPC code to Instiki, after wading through VoodooPad's API support for a few hours. Seems like the VoodooPad remote-wiki support is in a funky state in-between versions. I've also thought of attempting to bang VoodooPad and Instiki together to form the most unholy duo of hyperlinked personal knowledge management. I've never seen anyone say when, exactly they've used that or when it saved their ass. Lots of people note that you can execute the text of a page in a VoodooPad document as a script. Thus far, my inability to grok Applescript has tabled these ideas. I've also thought of passing that HTML through Ruby's ERB so I can add some programmatic stuff. and using that to make the HTML VoodooPad exports a little nicer to look at it in a browser. They mostly circle around writing all the pages as Markdown, Textile, etc. I have all these crazy ideas of stuff to do with VoodooPad.

#Voodoopad for windows windows#

This could be because I'm unwilling to pay for Windows software, as I'd only use it at work. That said, it beats the pants off anything similar I've found for Windows.

#Voodoopad for windows mac#

VoodooPad is very useful and worth the price of admission, but its not on the same level of complete awesomenewss other Mac applications I use are. I set up topic pages and pages to hold links early on, but I use those exceedingly rarely. I keep a daily log if there's something on my mind regarding the project and thats pretty much it. I'm not really using it as a Wiki that much. I've been using VoodooPad as a backup brain for my current project.

Posted by sohcahtoa at 8:30 AM on April 6, 2005 Examples include a workspace for a meeting agenda, workspace for outlines for presentations I'll be giving, a collection of links for something work related ('BypassingContentFilters' for example), and a page on a vendor product I'm evaluating. Reviewing the 'Recent Changes' page, I probably create one 'project' page every other day, on average. The 'top' page of the wiki is just links to a few things: The DailyEntries page, a BookMarks page, and a PersonalPages page in which I create links to non-work-related ideas or projects. If something takes the feel of a multistep project that will take more than one day to complete, I make its own page off of the daily entry page. I use each day as a scratchpad, recording phone calls and one-off tasks. I have a page called DailyEntries on which I pre-build a link for each day of the month, like:

I use QwikiWiki running on the loopback of my Windows desktop.