Sargrad, Dave wrote:
> Now that you've seen the pdf files that im currently interested and
> understand that I'm willing to put in the effort to "do this right", and to
> contribute something back to the community, please help me to understand the
> appropriate initial characteristics (API) of the "content stream parser".
OOh, one quick idea that wouldn't be needed for rendering data from a
content stream but would be really handy for editing and analysing it
would be to have the option of using the low level content stream
parser's output to populate a tree representation.
Content streams are stack based with postfix operators, right - RPN
style, in essence, ie
4 3 + 2 -
.
It's a fairly simple problem to read a RPN-style sequence into a tree
with interior nodes as operators and leaves as operands. Such a tree
could be easily created from the output of a content stream parser that
worked like the one I was muttering about. Once you have the tree, you
can do all sorts of interesting things with it. It'd make editing
content streams much easier, and when you're done and want to write it
out you just traverse the tree depth-first .
Hmm. Fun. Not much good for rendering, probably, even if it was possible
to read the stream one top-level child node at a time (which it should
be). For editing, though... I'm going to have to add this to PoDoFoBrowser.
Anyway, definitely sleep time.
--
Craig Ringer
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Podofo-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/podofo-users
