Talk at EuroPython 2010
by Hannes Hochreiner
Harald Armin Massa was so kind as to invite me to give a talk at
EuroPython 2010 on JessyInk. The talk will focus in particular on the
Inkscape extensions I wrote for JessyInk.
As such, I thought it might be a very good opportunity to promote
Inkscape, provide people with an introduction to writing Python
extensions for Inkscape and to present new features or plans that
concern Inkscape's extension facility.
Therefore, I would like to ask for your input:
*) What are the most essential points that have to mentioned when it
comes to Inkscape extensions written in Python ("inkex" and install dirs
come to mind)?
*) Are there any (Python) extensions that demonstrate interesting /
unusual / particularly helpful patterns that would be helpful for
someone looking to develop new extensions?
*) Is there any page / tutorial / other place (irc?, this mailing list?)
that you would like to have mentioned where developers can get help when
they have an extension related problem?
*) Are there any new features or exciting plans for the future of the
extension facility that I should tell people about?
If you can think of anything else, feel free to let me know.
[Inkscape] New From Template Dialog
by Albin Manoël
I try to work on New From Template Dialog
You can see work progress here :
So, I have some questions, all are written down on this page :
So you can read them and answer there, or simply answer me by mail.
Questions are :
Is it possible to add completely new attributes into a svg file ? like:
inkscape:template-name="Web banner 728x90"
inkscape:template-name-fr="Bannière Web 728x90"
inkscape:template-description="A banner for a website, size: 728x90 px"
Also, is "sodipodi:namedview" the correct markup for template attributes ?
Categories names Translations
Do we have to traduce categories names ? If yes, we can add new attributes
in svg files, like :
Should we use underscore between words ? like :
or can we simply use:
I think that keywords are optionals, because they must be traduced in too
many languages. And there is categories in order to find templates. Should
we use them or not ?
Currents categories Background
Is "background" the same category as "Desktop" ?
"default_mm.svg" and "default_pt.svg" don't respect specifications. Must be
"default.mm.svg" and "default.pt.svg". Is it correct ?
Thanks you for all :-)
by Krzysztof Kosiński
I made the following changes to the devlibs:
1. Upgrade Python to 2.6.5
2. Upgrade lxml to 2.2.4
3. Upgrade numpy to 1.4.1
4. Upgrade gettext-tools to 0.17
Please look for any breakage it might have introduced.
The gettext tools update was a bit problematic and two versions of
libintl are now contained in the build dir: one is being used by
Inkscape and the GTK stack, and the second one by the gettext tools.
Fixing this would require either convincing the gettext binaries to
use the devlibs libintl, which I have no idea how to do, or rebuilding
all other libraries to use the one built by gettext.
In the longer run, I think that cross-compiling the devlibs from Linux
might be less painful than recompiling them as needed in MSYS (mainly
because MSYS is excruciatingly slow and sometimes doesn't work).
by bulia byak
This is easily a no-go for the release:
- with Pen or Pencil, draw anything in Spiro mode (any other LPE would
do the same)
- clone (alt+d)
- select original and try to move it by arrow key
- watch Inkscape freeze and die an out-of-memory death, apparently in
some kind of infinite recursion.
I suspect this has something to do with LPE stack cloning that Johan
recently worked on, but as I don't watch commits as closely as I would
like lately, I also cc: others who did some nontrivial changes.
Let's get this fixed quickly :)
Inkscape. Draw Freely.
Re : Re : Re : Re : I suck at Perl (or check-markup)
by Nicolas Dufour
> De : Peter Moulder <Peter.Moulder@...2349...>
> À : Nicolas Dufour <nicoduf@...48...>
>> Another check-markup related issue: [it doesn't support msgctxt
> It's past my bedtime, so I haven't tested interesting cases
> yet, but try the attached patch.
Thanks for the patch. Unfortunately, it still doesn't work. But the error message is different now:
fr.po: parse error; may be a bug in po/check-markup:
And the fuzzy lines are now correctly ignored.
Re : Re : Re : I suck at Perl (or check-markup)
by Nicolas Dufour
Another check-markup related issue: I've just activated gettext context macro C_() support in po/Makevars in order to include all the status bar messages added in the new node tool, but check-markup now returns an error message for each string, translated or not:
fr.po: Not in msg format:
msgctxt "Transform handle tip"
msgid "<b>Rotation center:</b> drag to change the origin of transforms"
I guess it is related to the new msgctxt line. Bug again, I'm really not a Perl expert...
Could you please see if you can fix this issue?
by Ted Gould
I did the release this afternoon, but realized I forgot to write the
e-mail! :) None the less, I put together a pre0 release for the
upcomming 0.48. Please if packages could look at it and ensure that
they can build their package FROM THE TARBALL that would be great for
making sure the tarball is useful.
PS - Odd to me is that there's already 72 downloads of the source!
The path to FREEZE... Woohoo!
by Joshua A. Andler
We're roughly 6 weeks behind the proposed schedule... not good, but
could be worse. If we stick to it, things could shape up nicely.
A quick update... here is the one thing that MUST be done before moving
to Freeze... posting of an "alpha" tarball.
The following outstanding issues HAVE to be addressed to not be cut (and
most unfortunately have not been addressed fully during Frost):
*Jon's swatches MUST be initially editable in the F&S dialog.
*Jon's new Input Devices dialog needs whatever polish to be good enough
(I saw regressions from 0.47 mentioned recently in the tracker).
*Jon's "UX" work (specifically UI placement needs to be settled).
*Tavmjong's LinuxFund text tool work (we'll take what we can get, great
progress has been made!).
*Felipe Sanches' color management work. The "not real" (device) cmyk
thing MUST be addressed prior to release. I'm not saying to remove, but
perhaps disable, it is a part of the SVG spec, but it's not how the CMYK
workflow actually works.
Now is the time to bring up other possibly blocker bugs. Please speak
up... things that can be fixed in point releases and that aren't
critical/high priority should not be brought up.