Geoff Burling wrote:
> Unfortunately, I have not seen any actitivity on the mailing list for it.
> (Or is everyone who is working on it keeping their communications to
> personal email?)

Nope, there is a lot of activity on the plucker-dev list. 

Our mascot is 'dead' (it is a rubberchicken;), but the project
is very much alive. We are working very hard to be able to make 
a new release soon.

Some of the things we have added since the last release:

- support for compression of the documents 

- multi-database support (i.e. you could have one database
  with documents/web pages that rarely change, and then use 
  another database for your everyday web pages)

- scrollbars

- a parser written in python, so we can get rid of the awk
  scripts

- better support for Windows users (like you would care :)

- LaTeX and HTML versions of the documentation

These two are untested since the parsers don't support them
yet:

- support for named anchors (<A HREF="...#name">)

- a few new 'function codes' (margins, alignment of text) 
  to give the parser writers more freedom to replicate the 
  original document.  

There is also ongoing work to add an installation script
to make it easier for the average user to get it running
and also a perl version of the parser + some kind of server
solution (like Avantgo.com). I'm the maintainer of the Palm 
application, so don't ask me to explain how this server 
solution will work ;-) 

The size of the viewer is still very modest, about 16K.
And the compression will decrease the database a lot
(my 720K database decreased to 420K).

Anyone interested in trying out the latest development
version could get it from our cvs repository:

cvs -d :pserver:[EMAIL PROTECTED]:/cvs/dev -z3 login

and then just hit ENTER at the password prompt.

But wait until Friday/Saturday when I have been able to 
check in my latest changes to the code.

The documentation is not updated, but it shouldn't be too
hard to get it working. Let me know if you run into any 
problems and I will try to help you out.

/Mike

Reply via email to