On Aug 31, 4:50 pm, Terry Brown <[email protected]> wrote:
> Just pushed rev 2 to
>
> https://code.launchpad.net/~leo-editor-team/+junk/inkcall
I've just begun to study the code in detail. My first impression is
"wow", this is very cool. For example, template.svg looks like a lot
of work. Perhaps inkscape created it? Or its precursor?
Terry, before I go on, would you mind if I converted the @auto node to
an @thin node? There are good reasons for doing so: it would allow
helpers of a method to be children of that method. It's remarkable how
effective this is in clarifying the context of helpers. I've already
done this in my @@auto study tree, but I think it would be useful to
have it done all the time.
The following are notes to myself about the code:
The string constants like "co_bc_1" looked like gobbledygook until I
saw their definitions at the start of InkCall class.
There are three steps (after initialization) to this code:
Step 1: make_svg.
Step 2: edit_svg.
Step 3: make_png.
Steps 2 and 3 are just calls to Inkscape via::
proc = subprocess.Popen(cmd, stderr=subprocess.PIPE)
where cmd contains the args to Inkscape.
Step 1 is the hard part. It consists of make_dom and its four
helpers. At present, I have no idea what is going on, but I look
forward to finding out :-) Clearly, at some point I am going to have
to learn a little about Inkscape itself and svg files.
It's frustrating that installing lxml is not at all easy. To my
knowledge, there is no binary installer for Python 3.1.1 available.
The binary installer for Python 3.1 doesn't work(!). It's too bad
that lxml is not part of Python distros.
Terry, is lxml significantly better than Python's standard
xml.etree.ElementTree module?
Edward
--
You received this message because you are subscribed to the Google Groups
"leo-editor" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/leo-editor?hl=en.
