You can download ZDOC from the ZDOC Programmers page by clicking
here.
ZDOC FAQ :-
This is a list of frequently asked questions about ZDOC. It should cover most queries, but mail me if you have any others. RTFM before mailing me -- i dont have a lot of time to answer a billion queries. They arent in any specific order -- just dumped in when i recv queries.
[0.0] How fast do you release ZDOC versions ?
[0.0] Varies -- depending on my mood and how much time I have. It usually takes a week between version upgrades when I have access to a machine for a minimum of 8hrs/day and no other work. This will slow down or stop to one version every month or so when i cross a decent threshold of features.
[0.1] You dont have access to a machine ?
[0.1] I dont have any machine with the exception of my PalmPro. No PC/Unix machine. I get access thru public terminals where i've installed the GNU SDK. I dont have a great deal of cash to afford a decent laptop.
[0.2] How stable is ZDOC ?
[0.2] As stable as I could make it. It doesnt crash under the 2.0 debug ROM which is supposed to include lots of checks. As I spent a year programming on a Irix platform i've dealt with a lot x/motif memory leaks. As a result my memory handling routines should be stabler than most other ppls. I cant guarantee anything though. Its not as thoroughly tested as some of my other software and you use it at your own risk. As a general rule of thumb try to open files which are less than 250K and do not open them unless you have at least 3 times the file length in free RAM. i.e. if youre editing a 100K file make sure you have 300K free ram in your pilot. (Check it via the memory utility)
[0.3] What about bugs ?
[0.3] What about them ? (heh.) I've weeded out most of em. If you find any try and fix it yourself (the code is GPLised) and mail the thing to me with all possible details of it -- i'll whack it up soon, or modify/improve it to fit in all versions of ZDOC.
[0.4] Is there a seperate programmers page for ZDOC ?
[0.4] Yup. Try this one.
[0.5] I've put a really groovy must have thingy into ZDOC. How do i release it ?
[0.5] Mail it to me with express instructions including where it fits and what it does. Mail me the version of ZDOC used (must be the most release version i.e. no alpha/beta) and i'll put it up with your name (if you would like your name there).
[0.6] Can i send you encrypted mail ? Your PGP key is on your site.
[0.6] NO. Not regarding ZDOC. I allow/use encryption for confidential mails only. Mailing me encrypted junk gets you onto my kill filter ASAP.
[0.7] I lost my data !! ZDOC wiped my system !! it crashed..etc..etc.
[0.7] Restore from hotsync. mail me OS version, what you did, what files you worked on, what files you had loaded and what versions they were, all file/database sizes. I'll try and work on it to remove the bug, but no guarantees are made. Youre using this program at your own risk. I *do* have *some* motivation to remove total loss bugs (if any occur -- ive not seen it happen yet) since i use ZDOC extensively myself. (and no.. i dont take the advice from [0.2] seriously either. i routinely use it in low memory situations, but ive never lost anything uptil now -- on the other hand i DO keep hotsyncing at every oppurtunity)
[0.8] Does ZDOC work with/compatible with any other DOC readers/writers ?
[0.8] I've always kept a freeware DOC reader on my system. Usually its
Aportis DOC Mobile edition or the freeware DOC reader from Aportis. They
cause no problems and ZDOC can handle bookmarks easily (i.e. right now
it just ignores them).
[0.9] Why dyou keep a freeware reader on your system ?
[0.9] Just in case (heh). Acutally i prefer to work with readonly mode readers rather than a reader/writer such as ZDOC for browsing files. Its safer. For editing files I just use ZDOC. Note that ZDOC Ver2.x or below open files in ReadOnly mode and are as safe (or safer) than Aportis readers since Aportis readers add bookmarks which means they write to the file. ZDOC 2.x or below DO NOT write to the file.
[1.0] How stable is the code ?
[1.0] Very. ive not seriously broken it til now. It uses PalmOS 2.x API calls only to allocate/deallocate memory and no funny stuff. It should be compatible with PalmOS 3.x too..although i dont have a palm iii so i guess i'll wait til i find someone who tries it on one.
[1.1] Are you registered with 3COM ?
[1.1] I'll try to get ZDOC PalmOS certified..no guarantees on this. I've registered ZDOC's AppId with 3COM -- it's ZURK.
[1.2] Im a newbie programmer...i wanna learn ! Cant find anything -- help !
[1.2] Mail me -- i usually help if im not too busy. it takes a while but i'll get around to replying. Note that i only help ppl who work on GPLed code and use GCC. If you use any other development engine/develop commercial/shareware code -- forget it. Mail me your website, the location of GPLised code that you have contributed to the general public and any apps (with code). If i like what i see and i think you have potential i'll reply. Very newbie newbies who havent done anything but are prepared to show intent to develop GPLised apps are also welcome. I must have your website tho, and you must be using GCC.
[1.3] How come you havent put your real name/have a nonexistant company name/have a fake address etc on your site ?
[1.3] I believe in my freedom to remain anonymous. As such i dont put any real names/addresses up. I guard my privacy VERY carefully. And no, i wont give it to you if you ask me either. You may email me of course. My email address is functional (zurk@geocities.com).
[1.4] Have you written/going to write any other pilot software besides ZDOC ?
[1.4] dunno. will see.
[1.5] I want ##spiffy feature #999## in ZDOC. How do i do that ?
[1.5] Mail me your specs for #999 and i'll include it if i think it interesting. otherwise i'll delete the mail. get off your lazy backside and do it yourself before mailiing me...unless youre a total newbie.
<-EOF->