On Tue, Nov 06, 2001, Bill Janssen wrote:
> Another thought I had was to use function code 0x1B instead of 0x53,
That would not be according to the spec. which says that the function
code's least significant 3 bits represent the remaining function code
length; the most significant 5 bits represen
Alright, you say po-tay-to, I say wxPerl!
http://www.perl.com/pub/a/2001/09/12/wxtutorial1.html
I'll see if I can get Robert's gui or parts of it working in this,
just something to tinker with. You all know how I feel about Python.
/d
> How should the viewer render the segments? Should it show the text as
> "one" document (i.e. merge the current and next/previous segment)?
Yes, that was my thinking.
> That would require two simultaneously opened records and also *MAJOR*
> changes to several parts of the viewer (like the scrol
> Please feel free to modify/improve as you see fit, as I am
> not much of a python wizard. If you pass everything around as a 3-ple, you
> can chop out the itoa function from PluckerDocs.py.
Another thought I had was to use function code 0x1B instead of 0x53,
which saves a tiny bit in the functi
Hi Bill,
> > If someone could test it out and see what things need
> correcting, especially
> > that the charset work by Bill still is working as expected.
>
> I looked it over a bit, and didn't see anything that would raise a
> flag. It looks like all the parser diffs were to PluckerDocs.py and
On Tue, Nov 06, 2001, MJ Ray wrote:
> Why shouldn't there be something to do that sequence for me and leave
> me in the library screen?
Try the viewer I have put at http://www.sslug.dk/~micke/plucker/viewer.zip
I have changed "Details..." to /I and reserved /D for "Delete document"
(/D is also u
On Mon, Nov 05, 2001, Bill Janssen wrote:
> How about the viewer? Does this provide enough information to
> actually implement the necessary viewer changes?
How should the viewer render the segments? Should it show the text as
"one" document (i.e. merge the current and next/previous segment)?
On Mon, Nov 05, 2001, aardvarko wrote:
> It seems as though it wouldn't be terribly difficult to implement - just
> close the current document, save its name to a global variable or somesuch,
> and set a flag 'DeleteLastDocument'. Then let the user open another document
> and add a bit to the Ope
Gary:
> I use sitescooper to create about a dozen plucker files each day. I usually
> want to delete a file after reading it.
> I understand your logic though.
I don't. I sync quite a few pages most times (when my Palm isn't ill like
it seems to be at the moment -- that's the last time I use hac
