Website Upgrade (1.2) Tonight
by Martin Owens
Dear Develoeprs,
The inkscape website (inkscape.org) may be unavailable from 1am UTC (9pm
EST) for a period lasting about half an hour.
This upgrade will take us from django 1.5 to 1.6.5, django-cms from
1.4.2 to 3.0, haystack from 2.0 to 2.2, Whoosh 2.4 to 2.6 and finally
inkscape-web from 1.1 to 1.2.
The upgrade process involves a bunch of manual steps to the database and
command line and I hope these will be completed shortly after upgrading
the code. My thanks to Hachmann, jazzynico, Brynn and others in helping
prepare this release.
After the upgrade, content will be uploadable to inkscape.org and you
may wish to populate your user account with some of your svg files to
get the ball rolling. Also available will be the ability to upload Addon
tarballs and inkscape release builds (exe files/tarballs etc) which can
be used instead of sourceforge or your friendly file dumping service.
Please see me directly if you need an increased quota to upload large
release files.
I'm going to start everyone off with 10MB quota to start gently. The
idea for most users is to upload svg files which aren't that big. But we
can increase this for different auth groups as needed.
Any questions, reply here.
Best Regards, Martin Owens
9 years, 2 months
LPE Powerstroke
by Johan Engelen
Hi all,
Release is getting closer, and we need to decide what parts of
Powerstroke we are going to release. After release, it will be very
annoying for users if we change the output of Powerstroke for certain
input parameters. So we have to avoid having to do that.
Ideas:
- remove reflection-based extrapolated miters (my original
extrapolation), add the arc extrapolation miter
- remove CubicBezierFit and CubicBezierJohan interpolators, add
Catmull-Rom interpolator
thanks for input. I hope to work on this soon.
-Johan
9 years, 2 months
Re: [Inkscape-devel] LPE Powerstroke
by Johan Engelen
On 4-9-2014 3:52, Liam White wrote:
> On Wed, Sep 3, 2014 at 5:36 PM, Johan Engelen
> <jbc.engelen@...2592... <mailto:jbc.engelen@...2592...>> wrote:
>
> Ideas:
> - remove reflection-based extrapolated miters (my original
> extrapolation), add the arc extrapolation miter
>
> I like this, the arc extrapolation miter is stable and produces
> consistently better results than the reflection-based miter.
I have committed the change that enables Extrapolated Arc (used to be
only available with specialized build) and removes Extrapolated
(mirroring) from the UI. The code to deal with the old extrapolation
setting still works, for people that use it in their files. I am not
sure if we should keep that code around or not. It won't hurt too much
for now, but may become a maintenance burden. (and I don't like having
such undocumented features)
The arc extrapolation definitely has issues, and needs to be improved (I
feel).
cheers,
Johan
9 years, 2 months
Gtk+ 3 build bit-rot alert!
by Alex Valavanis
Hello All,
I thought I'd quickly check how we're doing with the Gtk+ 3 build in
Ubuntu Utopic, and was unpleasantly surprised to see that:
(a) A tonne more symbols that have been deprecated in Gtk+ 3.10
(principally, GtkAction)
(b) We have a few regressions, and have resumed use of some deprecated
symbols that we had previously replaced. (e.g., GtkHBox)
I have updated bug #1016020 with the latest build log (20k lines
caused by deprecation warnings!!) and summarised the failures in the
description.
Obviously, (a) isn't our fault, but we should try to regain the
progress we had made! (b) is more of a concern, since we're actually
moving backwards!
Ultimately, we should really try to enforce
"-Werror=deprecated-declarations" in our dev builds, but clearly we're
far away from that goal. Would it be reasonable to target a
deprecation-free build for Inkscape 1.0?
In the meantime, can I please request that from now on, everyone runs
a strict build with both Gtk+ 2 and Gtk+ 3 before merging in any new
features, so that we can ensure that we're not introducing any new
warnings?
Thanks,
AV
[1] https://bugs.launchpad.net/inkscape/+bug/1016020
9 years, 3 months
Re: [Inkscape-devel] LPE Powerstroke
by Johan Engelen
On 4-9-2014 23:32, Johan Engelen wrote:
> On 4-9-2014 3:52, Liam White wrote:
>> On Wed, Sep 3, 2014 at 5:36 PM, Johan Engelen
>> <jbc.engelen@...2592... <mailto:jbc.engelen@...2592...>> wrote:
>>
>> Ideas:
>> - remove reflection-based extrapolated miters (my original
>> extrapolation), add the arc extrapolation miter
>>
>> I like this, the arc extrapolation miter is stable and produces
>> consistently better results than the reflection-based miter.
>>
>> - remove CubicBezierFit and CubicBezierJohan interpolators
>>
>>
>> I am not so sure about this one. When we announce the 0.91 release,
>> we are going to have a lot of users that previously used the
>> derivative Ponyscape and were encouraged to use either of these two
>> interpolators.
>> I also believe we should add in Ponyscape's CubicBezierSmooth
>> interpolator[0] to aid in the migration process.
>>
>> add Catmull-Rom interpolator
>>
>>
I just tested and saw that Catmull-Rom has quite some disadvantages
compared to CubicBezierJohan. So we should keep that or perhaps your
"Smooth" variant. If we keep the Johan variant, we must give it a
different name (in SVG) and so will definitely be incompatible with
Ponyscape files that use CubicBezierJohan. (we really can't release with
that name in SVG)
-Johan
9 years, 3 months
Stroke placement
by Tavmjong Bah
Hi,
We discussed variable placement of stroke (e.g. inside/outside/10%
inside,90% outside). The key to implementing this is having a good way
to offset a path as then one can use existing rendering libraries to
draw the stroke (including things like dashes, line-caps).
If I can provide a clear (testable) algorithm for how to offset a path,
there is a good chance we can get this into SVG 2. The current Inkscape
code for offsetting is a bit buggy. I believe lib2geom has better code.
Can anybody comment?
Thanks,
Tav
9 years, 3 months
need advice on faq item re command line
by Brynn
Hi Friends,
FAQ #3.8.1 contains some garbled text. Unfortunately, I don't know
anything about using Inkscape from the command line.....or much about the
command line, in the first place. So I'm not sure exactly how to fix it.
The current text is below, for convenience. Or here's the URL:
http://inkscape.org/en/learn/faq/#Missing_console_output_issue Fyi, I'll
be combining this with item #2.20.
Could someone either fix the current text, or offer a short re-write
for me? It's the first sentence or 2, which need attention. Or if that
info is outdated, I need to know the new info.
If anyone wants to see what I'm working on:
http://staging.inkscape.org/en/brynns-user-faq Comments welcome. Besides
updating and re-organizing, I'm taking out a whole bunch of old useless
code! (whole bunch!) It's probably about halfway finished, and then I'll
start on the faq for developers. Note that I have uploaded some tiny images
of icons, in the How-To section, but they have somehow become lost. Martin
is on the case ;-)
And btw, when I get to work on the Developer FAQ, for the most part,
all I'll be able to do, is take out the useless code, and *try* to
reorganize the items. Since I'm such a newbie to this world, I won't be
able to decide if some need to be deleted, or if some text needs to be
updated, or if new items need to be added. That part will have to be up to
you guys :-)
Text below.
Thanks,
brynn
"As of the 0.48.2 release of the windows installer an inkscape.exe and an
inkscape.com. The start menu shortcut points to inkscape.exe which does not
write any output to the console. However, if you type inkscape in a command
prompt, and the install directory (C:\Program Files (x86)\Inkscape\) is in
your path, the command prompt will resolve inkscape.com before inkscape.exe.
The file inkscape.com is actually a windows executable, that
callsinkscape.exe and attaches it to the console window, therefore
displaying stdout and stderr to said console.
If you call inkscape.exe from the command prompt, things like exporting or
converting to plain SVG do work, they just do not output anything to the
console.
If you are using an older version of Inkscape, or just wish for historical
context, see this mailing list thread."
9 years, 3 months
