Existing users, 
I use viJournal 1.3 because it's basically an rtf file browser that can also create new documents. The "file browser" interface makes managing the journal documents easy, and the fact that it uses a universal file format like rtf is very comforting to me, because it means that in the year 2037, when I'm using Mac OS XXXIV, there's a very good chance I'll still be able to access all these documents.
Version 1.6 has a serious problem in that it abandons the rtf format and replaces it with its own special document type. That means that in the year 2037, if you want to read your journal, you will have to use viJournal, and there's no guarantee it will still be around and that it will work with whatever operating system exists at that time. So your data may be virtually irretrievable.
Also, there does not appear to be a way to export your journal to a more universal file format -- at least, after great searching, I couldn't find that feature.
So if you want to make certain that you can read your journal decades from now, I strongly advice that you use an earlier version of viJournal.
Version:
serious things to consider
Feedback Type: Commentary
Contributed by: Zackpunk Friday, June 23 2006 @ 11:39 AM PDT
Product Platform: MacOSX
Used Product For: Over One Year
Recommend Product: YES
Comments
serious things to consider - merrillfb
Actually, the full viJournal has export capability, albeit not in the most intuitive manner. You have to select all the desired entries in the Browser and then select Save A Copy As... which will allow you your RTF format.Would be nice to have a one stop function for this.
Sunday, June 25 2006 @ 08:55 PM PDT
serious things to consider - tdibble_dotmac
Also, the native file format is rtfd, although it also keeps other files in the package.Right-click on the ".vjentry" package for a date, click "Show Contents", and note the *.rtfd files there. The first entry for a date gets a nice name on the file, while any subsequent sessions get hashcode names. If you wanted to retrieve the titles for the secondary sessions, you'd look in the _vj_sessions_info.plist file right there in the package (plist is a standard XML data format file; easily read by hand or by computer).
IMHO, since it's just a package, all the contents are fully accessible using basic OS commands. That makes it just as future-proof as plain old rtf/rtfd files. It'd take a little script programming to make into whatever format you're more comfortable with, but no need for the creating application at all.
Friday, September 22 2006 @ 12:12 PM PDT
serious things to consider - merrillfb
Actually, the full viJournal has export capability, albeit not in the most intuitive manner. You have to select all the desired entries in the Browser and then select Save A Copy As... which will allow you your RTF format.Would be nice to have a one stop function for this.
Reply to This
Sunday, June 25 2006 @ 08:53 PM PDT