Nabble - Inkscape - Dev

Move to Launchpad

2009-11-09T19:59:03Z

Hey All,

Please be patient while we are preparing to move to launchpad. I am
adding in a number of our most active devs to the dev team to hopefully
speed things up once things are ready to go. Please DO NOT act on
anything until we send out a green light email (will most likely be sent
by Ted). If you were not added by me, please just request to be a member
of the team, it's nothing personal. :)

Cheers,
Josh

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
Inkscape-devel mailing list
Inkscape-devel@...
https://lists.sourceforge.net/lists/listinfo/inkscape-devel

Re: SVN Release Lockdown

2009-11-09T17:08:39Z

On Mon, Nov 9, 2009 at 1:32 PM, ~suv <suv-sf@...> wrote:
> Sorry if this is a redundant question: Will you include theAdib's patch
> for bug 271695 <https://bugs.launchpad.net/bugs/271695> to fix the cairo
> font embedding issue (win32)?

I could finally test this patch - it works for me and makes sense.

--
bulia byak
Inkscape. Draw Freely.
http://www.inkscape.org

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
Inkscape-devel mailing list
Inkscape-devel@...
https://lists.sourceforge.net/lists/listinfo/inkscape-devel

Re: SVN Release Lockdown

2009-11-09T12:19:30Z

On 11/9/09, Joshua A. Andler wrote:
> Hey All,
>
> I have one last commit to make (which of course triggered a rebuild
> since it touched verbs). In 3 hours, SVN will be locked down for
> release. Any last minute changes, speak now!

Updated ru.po sent to Ted and you some 20 minutes ago :)

Alexandre

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
Inkscape-devel mailing list
Inkscape-devel@...
https://lists.sourceforge.net/lists/listinfo/inkscape-devel

Re: SVN Release Lockdown

2009-11-09T10:32:02Z

On 9/11/09 18:39, Joshua A. Andler wrote:
> I have one last commit to make (which of course triggered a rebuild
> since it touched verbs). In 3 hours, SVN will be locked down for
> release. Any last minute changes, speak now! Oh, and yes Nicolas, the
> last commit I have planned will disable the non-functioning menu item
> for 346721 (boo to a last minute change that triggers a full rebuild). I
> will be posting again in a few hours with an update.

Sorry if this is a redundant question: Will you include theAdib's patch
for bug 271695 <https://bugs.launchpad.net/bugs/271695> to fix the cairo
font embedding issue (win32)?

~suv

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
Inkscape-devel mailing list
Inkscape-devel@...
https://lists.sourceforge.net/lists/listinfo/inkscape-devel

SVN Release Lockdown

2009-11-09T09:39:27Z

Hey All,

I have one last commit to make (which of course triggered a rebuild
since it touched verbs). In 3 hours, SVN will be locked down for
release. Any last minute changes, speak now! Oh, and yes Nicolas, the
last commit I have planned will disable the non-functioning menu item
for 346721 (boo to a last minute change that triggers a full rebuild). I
will be posting again in a few hours with an update.

Cheers,
Josh

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
Inkscape-devel mailing list
Inkscape-devel@...
https://lists.sourceforge.net/lists/listinfo/inkscape-devel

Prev/Next Zoom shorcut with Japanese keyboards

2009-11-08T21:22:47Z

Hello, I'm not sure if this is the right place to send this, say,
minor bug? annoyance? I've found:

The ` and shift-` shortcuts can't be really used with Japanese
keyboard layouts, since the backtick is done by shift-@,
so as you do "shift-@" inkscape gets the backtick, but since
you're pressing shift, it tries to go to "the next zoom" and there's
then no shortcut to go to the previous zoom.

Also as one would at start be already at the "last zoom",
just "no next zoom" is displayed... thus leaving you with
pretty much no shortcut to zoom's history unless you went
to a previous zoom by the menus.

PS: Is not really a feature I'll think I'll use much, I'd just ctrl-
mousewheel my zoom, but since I'm starting with inkscape I
was following the basic tutorial and found myself unable to do it.

Thanks for your time, keep it up with this nice project.
Marcel

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
Inkscape-devel mailing list
Inkscape-devel@...
https://lists.sourceforge.net/lists/listinfo/inkscape-devel

Re: Re : [win32] EPS/PS/PDF export of text objects problematic with 0.47(pre)

2009-11-08T20:08:23Z

Please also commit the follow-up to the PDF export bug. I put the
style setting in wrong places, and when both fill and stroke was set
on text, one overwrote the other. I forgot to test that case,
fortunately ~suv caught it soon enough.

https://bugs.launchpad.net/inkscape/+bug/388257

Regards, Krzysztof

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
Inkscape-devel mailing list
Inkscape-devel@...
https://lists.sourceforge.net/lists/listinfo/inkscape-devel

Re : [win32] EPS/PS/PDF export of text objects problematic with 0.47(pre)

2009-11-07T23:19:00Z

> De : Joshua A. Andler <scislac@...>
> I have a couple patches I am about to commit. Let's lock down on Monday
> morning, once a branch is tagged, the packagers can get to work and
> hopefully we can do the release on Friday! Woohoo!

Great news!

Don't forget to disable the View>Scripts menu (if not fixed meanwhile).
[Bug 346721] Segfault after opening JVM scripts dialog
https://bugs.launchpad.net/inkscape/+bug/346721

Regards,
--
Nicolas

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
Inkscape-devel mailing list
Inkscape-devel@...
https://lists.sourceforge.net/lists/listinfo/inkscape-devel

Re: Advice on how to update lxml on OS X

2009-11-07T18:59:09Z

On 7/11/09 22:31, Chris Mohler wrote:

> On Sun, Nov 8, 2009 at 3:05 PM, JiHO <jo.lists@...> wrote:
>> Basically we need to test with a recent lxml
>> version in MacPorts + the old one in Inkscape.app and check which one
>> gets loaded in Inkscape eventually. I'll have to do some digging to
>> check how I can get access to the lxml version used from within
>> Inkscape so if someone wants to test that before me, by all means,
>> please do! ;)
>
> Maybe this is helpful:
> https://bugs.launchpad.net/inkscape/+bug/448285/comments/9
> https://bugs.launchpad.net/inkscape/+bug/448285/comments/10
>
> I'm on linux, so my ability to help set on OS X is nil :( (Inkscape
> uses the system-wide lxml here)
>
> But this:
> export PYTHONPATH="$PYTHONPATH:$TOP/python/site-packages/$ARCH/$PYTHON_VERS"
> seems worth a shot to me.

The problem is: the current launch script doesn't see any user environment
configuration, so $PYTHONPATH initially will always be empty... except we
want to load only modules installed in assumed default locations (system
python, macports), like this for example:

# Setup PYTHONPATH to use python modules shipped with Inkscape
ARCH=`arch`
PYTHON_VERS=`python -V 2>&1 | cut -c 8-10`
# testing new PYTHONPATH proposed by JiHO in 'inkscape-devel' 07.11.09 22:05
# including predefined module paths (system python, macports)
#
# 3rd party modules for Python 2.5.1 on OS X 10.5.8 should be installed into
# /Library/Python/2.5/site-packages
# 3rd party modules for Python 2.6.1 on OS X 10.6.x should be installed into
# /Library/Python/2.6/site-packages ???
# local modules compatible with system python 2.5.1 on OS X 10.5.8:
# $MACPORTS_PREFIX/lib/python2.5/site-packages
# $MACPORTS_PREFIX/Library/Frameworks/Python.framework/Versions/2.5/lib/python2.5/site-packages/
# local modules compatible with MacPorts python 2.6.x on OS X 10.5.8:
# $MACPORTS_PREFIX/Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6/site-packages/
#
MACPORTS_PREFIX="/Volumes/blue/mp"
#MACPORTS_PREFIX="/opt/local"
MACPORTS_PYTHONPATH="$MACPORTS_PREFIX/Library/Frameworks/Python.framework/Versions/$PYTHON_VERS/lib/python$PYTHON_VERS/site-packages/"
SYSTEM_PYTHONPATH="/Library/Python/$PYTHON_VERS/site-packages/"
export PYTHONPATH="$SYSTEM_PYTHONPATH:$MACPORTS_PYTHONPATH:$TOP/python/site-packages/$ARCH/$PYTHON_VERS"

works for me with Inkscape 0.47pre4 from sf.net, system Python 2.5.1 and my
updated MacPorts modules.

TODO:
1) verify paths:
- default path to the Python frameworks in MacPorts installed in '/opt/local'
- default path to site-packages for the system Python on OS X 10.6 Snow Leopard
2) test modules:
- any module installed for the system Python on 10.5 and 10.6.
3) what about OS X 10.4 Tiger?
4) precedence of system Python over MacPorts modules or vice versa?

~suv

attached: diff for 'inkscape', 0.47pre4 (r22446)

--- inkscape-orig.sh 2009-10-18 18:29:05.000000000 +0200
+++ inkscape 2009-11-08 03:26:53.000000000 +0100
@@ -26,9 +26,27 @@
# Setup PYTHONPATH to use python modules shipped with Inkscape
ARCH=`arch`
PYTHON_VERS=`python -V 2>&1 | cut -c 8-10`
-export PYTHONPATH="$TOP/python/site-packages/$ARCH/$PYTHON_VERS"
+#export PYTHONPATH="$TOP/python/site-packages/$ARCH/$PYTHON_VERS"
# NB: we are only preprending some stuff to the default python path so if the directory does not exist it should not harm the rest

+# testing new PYTHONPATH proposed by JiHO in 'inkscape-devel' 2009-11-07
+# including predefined module paths (system python, macports)
+#
+# 3rd party modules for Python 2.5.1 on OS X 10.5.8 should be installed into:
+# /Library/Python/2.5/site-packages
+# 3rd party modules for Python 2.6.1 on OS X 10.6.x should be installed into:
+# /Library/Python/2.6/site-packages ???
+# local modules compatible with system python 2.5.1 on OS X 10.5.8:
+# $MACPORTS_PREFIX/lib/python2.5/site-packages
+# $MACPORTS_PREFIX/Library/Frameworks/Python.framework/Versions/2.5/lib/python2.5/site-packages/
+# local modules compatible with MacPorts python 2.6.x on OS X 10.5.8:
+# $MACPORTS_PREFIX/Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6/site-packages/
+#
+MACPORTS_PREFIX="/opt/local"
+MACPORTS_PYTHONPATH="$MACPORTS_PREFIX/Library/Frameworks/Python.framework/Versions/$PYTHON_VERS/lib/python$PYTHON_VERS/site-packages/"
+SYSTEM_PYTHONPATH="/Library/Python/$PYTHON_VERS/site-packages/"
+export PYTHONPATH="$SYSTEM_PYTHONPATH:$MACPORTS_PYTHONPATH:$TOP/python/site-packages/$ARCH/$PYTHON_VERS"
+
# No longer required if path rewriting has been conducted.
# export DYLD_LIBRARY_PATH="$TOP/lib"

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
Inkscape-devel mailing list
Inkscape-devel@...
https://lists.sourceforge.net/lists/listinfo/inkscape-devel

Re: [win32] EPS/PS/PDF export of text objects problematic with 0.47(pre)

2009-11-07T17:00:08Z

On Sat, 2009-11-07 at 20:53 -0400, bulia byak wrote:
> Thanks Krzysztof, both your patches are tested and applied.
>
> Any more patches to consider before the release? If there are none,
> why don't we go ahead and release this coming week?
>

I have a couple patches I am about to commit. Let's lock down on Monday
morning, once a branch is tagged, the packagers can get to work and
hopefully we can do the release on Friday! Woohoo!

Cheers,
Josh

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
Inkscape-devel mailing list
Inkscape-devel@...
https://lists.sourceforge.net/lists/listinfo/inkscape-devel

Re: [win32] EPS/PS/PDF export of text objects problematic with 0.47(pre)

2009-11-07T16:53:07Z

Thanks Krzysztof, both your patches are tested and applied.

Any more patches to consider before the release? If there are none,
why don't we go ahead and release this coming week?

--
bulia byak
Inkscape. Draw Freely.
http://www.inkscape.org

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
Inkscape-devel mailing list
Inkscape-devel@...
https://lists.sourceforge.net/lists/listinfo/inkscape-devel

Re: Mac OS X compiling prob

2009-11-07T15:09:46Z

On 7/11/09 21:56, JiHO wrote:
>>> Or should I have copied the line into one of the files?
>
>> In the previous posting in that thread I described that I put the shell
>> environment configuration [2] into a shell script which I source
>> whenever I need the build environment set up (e.g. to run configure):
>
> This is precisely what osx-build.sh (in packaging/macosx/) is there
> for. Would you care to comment on why you don't use it?

Sorry if I don't use these scripts whenever I update from SVN. I ran the
autogen.sh/configure script quite some time ago, but since then I didn't
make a fresh checkout nor build from a released src package. Therefore I
have used neither autogen.sh nor configure lately and didn't research an
issue I had encountered with my first build attempts when I tried to
follow the wiki page step by step (skipping the first 'For the
impatient' section and using the 'recommended' instructions).

<off-topic>
When updating from SVN or testing patches I usually don't need to run
osx-build.sh because locally I have linked inkscape-bin to
'src/inkscape' (as well as some of the resources inside the bundle to
the corresponding subdirectories in 'src/Build/share/inkscape').

Due to an unsolved bug in MacPorts 1.8.x I haven't been able to update
the MacPorts dependencies since its upgrade to 1.8 which entailed same
basic changes to all portfiles that make them incompatible with older
'port' builds. Because of this I currently do not 'need' to re-bundle
newer libraries or resource files for gtk+ and the rest.

Once this bug in MacPorts is fixed (hopefully 1.8.2) I will again build
the full app regularly and try to report back any issues I encounter.
</off-topic>

> If you find that it gets outdated, please report it (not necessarily a
> full blown bug report but an email will be enough to start with). Now
> if I follow correctly, you are suggesting that
>
> export ACLOCAL_FLAGS="-I $LIBPREFIX/share/aclocal"
> export PKG_CONFIG_PATH="$LIBPREFIX/lib/pkgconfig:$PKG_CONFIG_PATH"
>
> should be added to osx-build.sh right? Wolf, if you could test whether
> that solves the problem on your system, tht would be nice. If it does,
> I'll add to once the trunk is reopened.

Going again through my old logs from the first attempts to build
inkscape because I can't remember the details... roughly these are the
steps I took (as fair as I can reconstruct it now):

source ../config_build.sh ### set build environment
./autogen.sh ### failed, after setting $ACLOCAL_FLAGS succeeded
cd packaging/macosx
./osx-build.sh c ### failed (libpng), $PKG_CONFIG_PATH didn't help
cd ../..
./configure --enable-osxapp \
--prefix=/path/to/inkscape/packaging/macosx/../../Build/
### configure succeeded, likely that $PKG_CONFIG_PATH helped (not verified)
cd packaging/macosx
./osx-build.sh p -py /path/to/Python-packages

Looking at this now it seems that the mix (src/autogen.sh and
packaging/macosx/osx-build.sh) didn't work (my mistake) i.e. once I
started with ./autogen.sh I needed to follow with ./configure using the
correct configure flags copied from osx-build.sh. But honestly I am
afraid that drawing this conclusion without re-testing isn't correct
either ;-)

Yet it most likely means that the build scripts in 'packaging/macosx'
don't need to be updated.

@ Wolf - sorry, AFAICT now my tips are wrong and you better stick to
using the build scripts in 'packaging/macosx' only and don't run
autogen.sh/configure by itself.

@JiHO - I'll try next week to build a fresh checkout or 0.47pre4
strictly using your scripts (without updating the MacPorts tree first)
and report back if I encounter any errors.

~suv (who shouldn't have answered without re-checking the build logs!)

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
Inkscape-devel mailing list
Inkscape-devel@...
https://lists.sourceforge.net/lists/listinfo/inkscape-devel

Re: Advice on how to update lxml on OS X

2009-11-07T13:56:56Z

On Sat, Nov 7, 2009 at 22:31, Chris Mohler <cr33dog@...> wrote:
> Maybe this is helpful:
> https://bugs.launchpad.net/inkscape/+bug/448285/comments/9
> https://bugs.launchpad.net/inkscape/+bug/448285/comments/10

That definitely helps! Thanks.

> If there's anything I can do or provide from a linux (or win32) box,
> just let me know.

Well, the problem is really time to test everything. My MacPorts
installation is in need of serious updating and I have very little
time to spend on that+Inkscape. Yet, I would be happy to send some of
my daytime work your way so that I can free so time in my schedule.
You could definitely do this work on a linux box. Does that work for
you ;)

... oh man, how much would I like this to be *actually* feasible!

Cheers,

JiHO
---
http://maururu.net

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
Inkscape-devel mailing list
Inkscape-devel@...
https://lists.sourceforge.net/lists/listinfo/inkscape-devel

Re: Advice on how to update lxml on OS X

2009-11-07T13:31:17Z

On Sun, Nov 8, 2009 at 3:05 PM, JiHO <jo.lists@...> wrote:
> Basically we need to test with a recent lxml
> version in MacPorts + the old one in Inkscape.app and check which one
> gets loaded in Inkscape eventually. I'll have to do some digging to
> check how I can get access to the lxml version used from within
> Inkscape so if someone wants to test that before me, by all means,
> please do! ;)

Maybe this is helpful:
https://bugs.launchpad.net/inkscape/+bug/448285/comments/9
https://bugs.launchpad.net/inkscape/+bug/448285/comments/10

I'm on linux, so my ability to help set on OS X is nil :( (Inkscape
uses the system-wide lxml here)

But this:
export PYTHONPATH="$PYTHONPATH:$TOP/python/site-packages/$ARCH/$PYTHON_VERS"
seems worth a shot to me.

If there's anything I can do or provide from a linux (or win32) box,
just let me know.

Chris

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
Inkscape-devel mailing list
Inkscape-devel@...
https://lists.sourceforge.net/lists/listinfo/inkscape-devel

Re: Advice on how to update lxml on OS X

2009-11-07T13:05:13Z

On Fri, Oct 30, 2009 at 01:47, Chris Mohler <cr33dog@...> wrote:
> Hmm - shouldn't this be the other way around? Try system-wide first,
> then fall back to bundled libs if need be? Particularly since the
> bundled version of lxml (and numpy?) is quite dated it seems to make
> sense to me - but then again I have no experience packaging for OSX.

I don't recall the specifics but I think it PYTHONPATH was not working
exactly as PATH. For example, we are doing:

export PYTHONPATH="$TOP/python/site-packages/$ARCH/$PYTHON_VERS"

and this only *prepends* stuff to PYTHONPATH (or at least it used to),
it does not replace it. With PATH, you would have to do:

export PATH="foo:$PATH"

to prepend, and

export PATH="foo"

would reset PATH, not add to it.

But maybe we can try:

export PYTHONPATH="$PYTHONPATH:$TOP/python/site-packages/$ARCH/$PYTHON_VERS"

and see if that works. Basically we need to test with a recent lxml
version in MacPorts + the old one in Inkscape.app and check which one
gets loaded in Inkscape eventually. I'll have to do some digging to
check how I can get access to the lxml version used from within
Inkscape so if someone wants to test that before me, by all means,
please do! ;)

JiHO
---
http://maururu.net

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
Inkscape-devel mailing list
Inkscape-devel@...
https://lists.sourceforge.net/lists/listinfo/inkscape-devel

Re: Advice on how to update lxml on OS X

2009-11-07T12:58:24Z

On Thu, Oct 29, 2009 at 23:22, ~suv <suv-sf@...> wrote:

> I have been running your Inkscape development snapshots and later my own
> SVN builds with custom shell launcher scripts (script, openDoc and
> bin/inkscape), and have my normal shell environment (set with ~/.profile
> - a symbolic link to ~/.bash_profile - and ~/.bashrc) in Inkscape
> available by using a login shell in the first level (script and openDoc)
> which automatically sources the default startup files of my $SHELL
> (whatever that might be). See bug #383456 “[OS X] launch Inkscape with a
> login shell” <https://bugs.launchpad.net/inkscape/+bug/383456> where I
> filed my initial ideas. That report is quite old and I have learned a
> lot since, but basically the attached patch is what gets the user
> configuration into the shell launcher script for inkscape-bin.

I never realized this. From your bug report, I would say that updating
script exec would be the best solution but for now the bash --login
will do. I'll commit that as soon as the trunk reopens.

>> Please let me know what you think,
>
> If this is something you might consider I could attach my current launch
> scripts to bug #383456 (status 'work-in-progress': additionally they log
> all inkscape console output into a separate file, add a time stamp, PID
> and list some env variables plus any arguments to inkscape-bin e.g. when
> called by a python extension script - mainly debugging info not of
> interest for the regular Inkscape user).

This would be welcome indeed. I would suggest, however, to make it a
new bug report/blueprint, assigned to me, that reads "Adding debugging
output to Inkscape on OS X" or something.

Thanks a lot,

JiHO
---
http://maururu.net

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
Inkscape-devel mailing list
Inkscape-devel@...
https://lists.sourceforge.net/lists/listinfo/inkscape-devel

Re: Mac OS X compiling prob

2009-11-07T12:56:14Z

> Or should I have copied the line into one of the files?

> In the previous posting in that thread I described that I put the shell
> environment configuration [2] into a shell script which I source
> whenever I need the build environment set up (e.g. to run configure):

This is precisely what osx-build.sh (in packaging/macosx/) is there
for. Would you care to comment on why you don't use it?

If you find that it gets outdated, please report it (not necessarily a
full blown bug report but an email will be enough to start with). Now
if I follow correctly, you are suggesting that

export ACLOCAL_FLAGS="-I $LIBPREFIX/share/aclocal"
export PKG_CONFIG_PATH="$LIBPREFIX/lib/pkgconfig:$PKG_CONFIG_PATH"

should be added to osx-build.sh right? Wolf, if you could test whether
that solves the problem on your system, tht would be nice. If it does,
I'll add to once the trunk is reopened.

JiHO
---
http://maururu.net

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
Inkscape-devel mailing list
Inkscape-devel@...
https://lists.sourceforge.net/lists/listinfo/inkscape-devel

Re: Mac OS X compiling prob

2009-11-07T06:45:16Z

On 7/11/09 14:06, Wolf Drechsel wrote:

> On 7/11/09 13:50, ~suv wrote:
>> On 7/11/09 11:55, Wolf Drechsel wrote:
>>> as I'm running into the well-known "gnuplot-inkscape"-bug of 0.46,
>>> and unluckily no 0.47 ppc precompiled packages are available, I tried
>>> to compile the most recent package myself on Mac OS X 10.4.11 PPC.
>>>
>>> After "./configure" I run into this error message:
>>>
>>> configure: error: libpng >= 1.2 is needed to compile inkscape
>>>
>>> But I do have a suitable libpng:
>>>
>>> port installed libpng
>>> The following ports are currently installed:
>>> libpng @1.2.38_0 (active)
>>
>> Initially when running autogen.sh and configure on OS X 10.5.8 i386 I
>> had the same issue. My workaround at that time is described in an
>> earlier thread [1], but as I lack experience and coding skills
>> myself I
>> can't judge its validity. Maybe one of devs involved in the osx
>> packaging process can provide more insight into this problem.
>>
>> [1] <http://thread.gmane.org/gmane.comp.graphics.inkscape.devel/31219/focus=31221>
>
> Sorry that I'm really a kid… - I assumed that the sentence "and after
> adding the PKG_CONFIG_PATH to the shell environment" means pasting
>
> export PKG_CONFIG_PATH="$LIBPREFIX/lib/pkgconfig:$PKG_CONFIG_PATH"
>
> into the shell - and than do autogen, configure, make and make install.
>
> So did I - but ended up with the same error.
> Or should I have copied the line into one of the files?

In the previous posting in that thread I described that I put the shell
environment configuration [2] into a shell script which I source
whenever I need the build environment set up (e.g. to run configure):

contents of config-env.sh:
#<--- snip --->
#!/bin/sh

export LIBPREFIX="/opt/local"
# automake seach path
export CPATH="$LIBPREFIX/include"
# configure search path
export CPPFLAGS="-I$LIBPREFIX/include"
export LDFLAGS="-L$LIBPREFIX/lib"
# compiler arguments
export CFLAGS="-O3 -Wall"
export CXXFLAGS="$CFLAGS"
# to speed up the compilation
export CC="ccache gcc"
export CXX="ccache g++"

export ACLOCAL_FLAGS="-I $LIBPREFIX/share/aclocal"
export PKG_CONFIG_PATH="$LIBPREFIX/lib/pkgconfig:$PKG_CONFIG_PATH"

#eof
#<--- snip --->

But please note that I am not sure if this is the correct way to handle
the issue - in one of my other posts in that previous thread I mention
that the MacPorts inkscape-devel port [3] includes a set of patches for
autogen.sh and configure that possibly address a similar problem with a
proper solution... I never tried to make use of those patches and I
never build inkscape-devel via MacPorts (only the needed dependencies to
build Inkscape.app outside of MacPorts).

~suv (I know that's not very helpful, but it's all I know ATM)

[2] the build environment variables as mentioned on the Wiki page about
building Inkscape on OS X.
<http://wiki.inkscape.org/wiki/index.php/CompilingMacOsX#Setting_the_build_environment>

[3] inkscape-devel Portfile:
<http://trac.macports.org/browser/trunk/dports/graphics/inkscape-devel/Portfile>
Patches in the files subdirectory:
<http://trac.macports.org/browser/trunk/dports/graphics/inkscape-devel>

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
Inkscape-devel mailing list
Inkscape-devel@...
https://lists.sourceforge.net/lists/listinfo/inkscape-devel

Re: Mac OS X compiling prob

2009-11-07T05:06:56Z

Hello ~suv,

thanks for your reply.

Sorry that I'm really a kid… - I assumed that the sentence "and after
adding the PKG_CONFIG_PATH to the shell environment" means pasting

export PKG_CONFIG_PATH="$LIBPREFIX/lib/pkgconfig:$PKG_CONFIG_PATH"

into the shell - and than do autogen, configure, make and make install.

So did I - but ended up with the same error.
Or should I have copied the line into one of the files?

Greetings,

Wolf

> On 7/11/09 11:55, Wolf Drechsel wrote:
>> as I'm running into the well-known "gnuplot-inkscape"-bug of 0.46,
>> and unluckily no 0.47 ppc precompiled packages are available, I tried
>> to compile the most recent package myself on Mac OS X 10.4.11 PPC.
>>
>> After "./configure" I run into this error message:
>>
>> configure: error: libpng >= 1.2 is needed to compile inkscape
>>
>> But I do have a suitable libpng:
>>
>> port installed libpng
>> The following ports are currently installed:
>> libpng @1.2.38_0 (active)
>
> Initially when running autogen.sh and configure on OS X 10.5.8 i386 I
> had the same issue. My workaround at that time is described in an
> earlier thread [1], but as I lack experience and coding skills
> myself I
> can't judge its validity. Maybe one of devs involved in the osx
> packaging process can provide more insight into this problem.
>
> ~suv
>
> [1]
> <http://thread.gmane.org/gmane.comp.graphics.inkscape.devel/31219/
> focus=31221>

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
Inkscape-devel mailing list
Inkscape-devel@...
https://lists.sourceforge.net/lists/listinfo/inkscape-devel

Re: Mac OS X compiling prob

2009-11-07T04:50:17Z

On 7/11/09 11:55, Wolf Drechsel wrote:

> as I'm running into the well-known "gnuplot-inkscape"-bug of 0.46,
> and unluckily no 0.47 ppc precompiled packages are available, I tried
> to compile the most recent package myself on Mac OS X 10.4.11 PPC.
>
> After "./configure" I run into this error message:
>
> configure: error: libpng >= 1.2 is needed to compile inkscape
>
> But I do have a suitable libpng:
>
> port installed libpng
> The following ports are currently installed:
> libpng @1.2.38_0 (active)

Initially when running autogen.sh and configure on OS X 10.5.8 i386 I
had the same issue. My workaround at that time is described in an
earlier thread [1], but as I lack experience and coding skills myself I
can't judge its validity. Maybe one of devs involved in the osx
packaging process can provide more insight into this problem.

~suv

[1]
<http://thread.gmane.org/gmane.comp.graphics.inkscape.devel/31219/focus=31221>

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
Inkscape-devel mailing list
Inkscape-devel@...
https://lists.sourceforge.net/lists/listinfo/inkscape-devel

Mac OS X compiling prob

2009-11-07T02:55:09Z

Hello everybody,

as I'm running into the well-known "gnuplot-inkscape"-bug of 0.46,
and unluckily no 0.47 ppc precompiled packages are available, I tried
to compile the most recent package myself on Mac OS X 10.4.11 PPC.

After "./configure" I run into this error message:

configure: error: libpng >= 1.2 is needed to compile inkscape

But I do have a suitable libpng:

port installed libpng
The following ports are currently installed:
libpng @1.2.38_0 (active)

So this may be a path issue - I googled that several people had this
problem as well, but couldnt find how to resolve it.

Any hint would be appreciated.

Greetings,

Wolf

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
Inkscape-devel mailing list
Inkscape-devel@...
https://lists.sourceforge.net/lists/listinfo/inkscape-devel

Re: [win32] EPS/PS/PDF export of text objects problematic with 0.47(pre)

2009-11-06T17:41:48Z

On 7/11/09 01:20, Krzysztof Kosiński wrote:
> Please check whether the attached patch fixes the issue (for me it
> does, at least for the testcase at Launchpad). It's also attached to
> the LP bug.
>
> It seems that cairo_restore does not clear the path in
> extension/internal/cairo-render-context.cpp, function renderGlyphtext.
> When text has fill but no stroke and text to path is active, only
> cairo_fill_preserve is called. This causes an accumulation of text
> paths observed in exported PDFs.

[Bug 388257] <https://bugs.launchpad.net/bugs/388257>: patch tested and
fix confirmed with Inkscape 0.46+devel r22557+patch on OS X 10.5.8 with
several test cases attached to the LP bug report and local SVG files
with multiline text objects and varying fonts.

Thank you Krzysztof! Any chance this gets into 0.47?

> BTW, I noted that the ellipse prefs fix isn't committed yet. Could a
> release warden commit it? I posted it here somewhere, as well as here:
> https://bugs.launchpad.net/inkscape/+bug/459811

ditto

--
~suv

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
Inkscape-devel mailing list
Inkscape-devel@...
https://lists.sourceforge.net/lists/listinfo/inkscape-devel

Re: [win32] EPS/PS/PDF export of text objects problematic with 0.47(pre)

2009-11-06T16:20:31Z

Please check whether the attached patch fixes the issue (for me it
does, at least for the testcase at Launchpad). It's also attached to
the LP bug.

It seems that cairo_restore does not clear the path in
extension/internal/cairo-render-context.cpp, function renderGlyphtext.
When text has fill but no stroke and text to path is active, only
cairo_fill_preserve is called. This causes an accumulation of text
paths observed in exported PDFs.

BTW, I noted that the ellipse prefs fix isn't committed yet. Could a
release warden commit it? I posted it here somewhere, as well as here:
https://bugs.launchpad.net/inkscape/+bug/459811

Regards, Krzysztof

[pdf-export-fix.patch]

Index: src/extension/internal/cairo-render-context.cpp =================================================================== --- src/extension/internal/cairo-render-context.cpp (revision 22560) +++ src/extension/internal/cairo-render-context.cpp (working copy) @@ -1458,7 +1458,7 @@ #define GLYPH_ARRAY_SIZE 64 unsigned int -CairoRenderContext::_showGlyphs(cairo_t *cr, PangoFont *font, std::vector<CairoGlyphInfo> const &glyphtext, bool is_stroke) +CairoRenderContext::_showGlyphs(cairo_t *cr, PangoFont *font, std::vector<CairoGlyphInfo> const &glyphtext, bool path) { cairo_glyph_t glyph_array[GLYPH_ARRAY_SIZE]; cairo_glyph_t *glyphs = glyph_array; @@ -1482,15 +1482,10 @@ i++; } - if (is_stroke) { + if (path) { cairo_glyph_path(cr, glyphs, num_glyphs - num_invalid_glyphs); } else { - if (_is_texttopath) { - cairo_glyph_path(cr, glyphs, num_glyphs - num_invalid_glyphs); - cairo_fill_preserve(cr); - } else { - cairo_show_glyphs(cr, glyphs, num_glyphs - num_invalid_glyphs); - } + cairo_show_glyphs(cr, glyphs, num_glyphs - num_invalid_glyphs); } if (num_glyphs > GLYPH_ARRAY_SIZE) @@ -1552,20 +1547,30 @@ _showGlyphs(_cr, font, glyphtext, TRUE); } } else { - + bool fill = false, stroke = false, have_path = false; if (style->fill.isColor() || style->fill.isPaintserver()) { // set fill style _setFillStyle(style, NULL); - - _showGlyphs(_cr, font, glyphtext, FALSE); + fill = true; } if (style->stroke.isColor() || style->stroke.isPaintserver()) { // set stroke style _setStrokeStyle(style, NULL); - - // paint stroke - _showGlyphs(_cr, font, glyphtext, TRUE); + stroke = true; + } + if (fill) { + if (_is_texttopath) { + _showGlyphs(_cr, font, glyphtext, true); + have_path = true; + if (stroke) cairo_fill_preserve(_cr); + else cairo_fill(_cr); + } else { + _showGlyphs(_cr, font, glyphtext, false); + } + } + if (stroke) { + if (!have_path) _showGlyphs(_cr, font, glyphtext, true); cairo_stroke(_cr); } } Index: src/style.cpp =================================================================== --- src/style.cpp (revision 22560) +++ src/style.cpp (working copy) @@ -2684,7 +2684,7 @@ style->stroke_width.set = FALSE; style->stroke_width.unit = SP_CSS_UNIT_NONE; - style->stroke_width.computed = 1.0; + style->stroke_width.computed = 0.0; style->stroke_linecap.set = FALSE; style->stroke_linecap.value = style->stroke_linecap.computed = SP_STROKE_LINECAP_BUTT;

Re: [win32] EPS/PS/PDF export of text objects problematic with 0.47(pre)

2009-11-05T17:56:19Z

[update]

A) cairo font embedding bug (win32)
<https://bugs.launchpad.net/bugs/469180>
<https://bugs.launchpad.net/bugs/271695>

On 5/11/09 09:37, Adrian Johnson wrote:
> I written a patch for cairo to fix this. I've put the patch and
> cairo/pixman dlls built with the patch here:
>
> http://people.freedesktop.org/~ajohnson/bug271695/
>
> I still need to do further testing with the patch.

AFAIU the cairo patch only concerns the win32 packaging process (i.e.
updating Cairo in the Dev Libraries repository).

B) 'Convert texts to paths' export option
<https://bugs.launchpad.net/bugs/388257>

On 3/11/09 19:31, ivan louette wrote:
> The problem only occurs with filled text without outline. No problem for
> me with only outline text or text with fill and outline.

I verified that keeping the text stroke style attributes by setting a
stroke fill color and stroke-width to '0.00' px does not trigger the
bug: Inkscape 0.46+devel r22552 then creates PDFs of the same quality
and file size as Inkscape 0.46.

Could this be related to the changes described in the release notes as
'Optimized CSS properties'[1]?

There is no patch available and the bug happens on all platforms.

~suv

[1]
<http://wiki.inkscape.org/wiki/index.php/Release_notes/0.47#Optimized_CSS_properties>

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
Inkscape-devel mailing list
Inkscape-devel@...
https://lists.sourceforge.net/lists/listinfo/inkscape-devel

Re: Upcoming Releases

2009-11-04T10:48:45Z

On Wed, 2009-11-04 at 12:26 -0400, bulia byak wrote:
> Exactly. And a better SVN with easier branches won't change that.
> Let's not be carried away by the shiny new tools. Branches' freedom
> can easily turn sour. Whenever there's a chance to effect a change by
> a series of focused, well-planned changes in the trunk, each of which
> leaves it in a workable state, this should be preferred to branching.

I won't (completely) disagree about the shiny new tools remark... but I
will also say that you (bulia) have a particularly good record for the
well-planned changes. I've seen others (in a number of projects) not
have such success with what they thought were well-planned changes.

> Exactly. That's why we're doing Inkscape in the first place :) It is
> so much more than the sum of what each of us could do alone.

Yay for collaboration! :)

Cheers,
Josh

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
Inkscape-devel mailing list
Inkscape-devel@...
https://lists.sourceforge.net/lists/listinfo/inkscape-devel

Re: Upcoming Releases

2009-11-04T10:41:19Z

On Wed, 2009-11-04 at 10:22 +0100, J.B.C.Engelen@... wrote:
> I'm not sure whether it is the refactoring that troubles this release.

I'm not saying it troubled this release, but that something of that
nature would potentially (not definitely) make for a longer 0.48 cycle.

> However, a practical problem of large refactoring is that it touches the
> source in many different places. This makes it very likely that changes
> in trunk coincide with refactoring changes in the branch. A lot of time
> (and frustration) will be spent merging in changes from trunk. This is
> also true for non-refactoring but invasive new features, like LPE was.

Well, I'm not going to say that a proper DVCS will make the merges less
difficult, however, just as I am willing to test branches, I am also
willing to help merge more often (and address issues that arise) to make
it easier on the devs in the trenches.

> Moreover, very few people test branches. I remember Josh (ScislaC) and
> sim (?) being the only ones who regularly checked out my LPE branch for
> testing. A branch was used for group/stacked LPE, but perhaps two people
> (other than the devs) tested it a little.

I think you're underestimating our community. :) As with any high
profile, exciting, or important changes, if you tap the community I
think they will surprise you. For things that are less obvious or
exciting, there are still a couple of us that would be more than happy
to test.

> Many bugs are discovered late, and it seems a branch will only delay
> that. On the upside, there are also a lot of bugs that are discovered
> early but the bugreports reach the developer(s) very late or not at all;
> the upside is that when a branch is used, the bugs are easier to target
> to a specific branch and to specific developer(s).

I can't disagree about when bugs are discovered... there's a reason why
regular users report bugs after release that no one saw in testing. :)
The branch recommendation was really just for 0.48 though... is there
something you're working on that you're particularly concerned about?
Post a diff right now and I'll start testing.

> I think more important than a branch is a teamed effort for big
> projects. From my own experience, refactoring alone is no fun;
> refactoring in a team (thanks Verbal and Diederik!) is much more fun. So
> I feel that before anyone should take up refactoring, he should find a
> team to do it with. This reduces the risk of 'vacation' or 'sick of it'
> problems.

Yes it is more fun... this is why I want 0.47 out the door. So we can
get back to collaborative development. Releases are a "drag"... momentum
comes to a crawl, the energy is sapped from the community, and
contributions are few and far between. This is part of my wanting to be
able to get 0.48 done quickly, to keep the pace and energy as much as
possible into a longer refactoring cycle.

Cheers,
Josh

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
Inkscape-devel mailing list
Inkscape-devel@...
https://lists.sourceforge.net/lists/listinfo/inkscape-devel

Re: Upcoming Releases

2009-11-04T08:26:24Z

On Wed, Nov 4, 2009 at 5:22 AM, <J.B.C.Engelen@...> wrote:
> I don't know what my opinion is. Having bug-likely stuff in a branch is
> nice of course.
>
> However, a practical problem of large refactoring is that it touches the
> source in many different places. This makes it very likely that changes
> in trunk coincide with refactoring changes in the branch. A lot of time
> (and frustration) will be spent merging in changes from trunk. This is
> also true for non-refactoring but invasive new features, like LPE was.

Exactly. And a better SVN with easier branches won't change that.
Let's not be carried away by the shiny new tools. Branches' freedom
can easily turn sour. Whenever there's a chance to effect a change by
a series of focused, well-planned changes in the trunk, each of which
leaves it in a workable state, this should be preferred to branching.

> I think more important than a branch is a teamed effort for big
> projects. From my own experience, refactoring alone is no fun;
> refactoring in a team (thanks Verbal and Diederik!) is much more fun. So
> I feel that before anyone should take up refactoring, he should find a
> team to do it with. This reduces the risk of 'vacation' or 'sick of it'
> problems.

Exactly. That's why we're doing Inkscape in the first place :) It is
so much more than the sum of what each of us could do alone.

--
bulia byak
Inkscape. Draw Freely.
http://www.inkscape.org

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
Inkscape-devel mailing list
Inkscape-devel@...
https://lists.sourceforge.net/lists/listinfo/inkscape-devel

Re: Upcoming Releases

2009-11-04T08:09:12Z

On 11/4/09, J.B.C.Engelen wrote:

> Moreover, very few people test branches. I remember Josh (ScislaC) and
> sim (?) being the only ones who regularly checked out my LPE branch for
> testing. A branch was used for group/stacked LPE, but perhaps two people
> (other than the devs) tested it a little.

We just need something like graphicall.org :)

Alexandre

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
Inkscape-devel mailing list
Inkscape-devel@...
https://lists.sourceforge.net/lists/listinfo/inkscape-devel

Re: [win32] EPS/PS/PDF export of text objectsproblematic with 0.47(pre)

2009-11-04T05:45:59Z

> Adding some numbers to illustrate my concerns (it's not about the number
> of expected bug reports but the number of frustrated users...)

By frustration, do you mean you expect them to complain about large file sizes or do you mean they'll complain about large file sizes potentially causing other problems like out of memory, etc?

For me, I'd still be OK will being frustrated in the short term with large files sizes if their downstream effect wasn't to crash my system or other nasty effects. My primary concerns are to keep the quality and keep my system stable. I'll deal with file sizes for the short term. I hope I'm representative of other Windows users and not leading you down the wrong path.

>
> On 3/11/09 23:18, Jon wrote:
> > * Keep the quality of the PDF high even if (in the short term) the
> > exported file size is large
>
> bug #271695:
> 632 KB (osx) vs. 24 MB (win32) (EPS export)
>
> bug #431314:
> 80 KB (osx) vs. 3.8 MB (win32) (PDF export)
> (and this is only a reduced case of a one-page-document, the original
> file doesn't even get exported on win32)

I better see your concern. I'm going to test more PDF exports on my Vista w/0.47pre4 today.

> > * Don't make me remember some hacky 'Path > Object to Path' before
> > saving as EPS/PS/PDF workaround that goes away when you fix things.
> > This is much uglier marketing wise than a short term file size issue
> > in my opinion.
>
> Without applying this 'hack' when using the current 0.47pre version you
> get *both* bad text/font quality and even bigger file size when
> exporting with the 'Convert texts to paths' option:
>
> bug #271695:
> 2.7 MB (0.46) vs. 411 MB (0.47pre3) (EPS export)
> (but with lower text/font quality due to bug #388257)

Yikes.

I almost hate to even suggest this idea as the downstream impacts may be horrible, but that said, is is possible to hard-code your best pragmatic (high text/font quality) workaround into the "save as EPS/PS/PDF code path" *only* for Windows systems to limit the exposure and only until you can do a point release fix?

How close (time wise) do you feel you are in determining true root cause and implementing a tested fix?

Jon

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
Inkscape-devel mailing list
Inkscape-devel@...
https://lists.sourceforge.net/lists/listinfo/inkscape-devel

Re: Upcoming Releases

2009-11-04T01:22:01Z

> -----Original Message-----
> From: Joshua A. Andler [mailto:scislac@...]
> Sent: Wednesday, November 04, 2009 02:40
>
> > How do we define "major"?
>
> Well, typically something that we would label as a refactoring task.
> However, if someone has a "major" change and throws it in a
> branch and it is deemed to be safe enough to be worth the
> possible risk for 0.48, we'll merge it.

I'm not sure whether it is the refactoring that troubles this release.

I don't know what my opinion is. Having bug-likely stuff in a branch is
nice of course.

However, a practical problem of large refactoring is that it touches the
source in many different places. This makes it very likely that changes
in trunk coincide with refactoring changes in the branch. A lot of time
(and frustration) will be spent merging in changes from trunk. This is
also true for non-refactoring but invasive new features, like LPE was.

Moreover, very few people test branches. I remember Josh (ScislaC) and
sim (?) being the only ones who regularly checked out my LPE branch for
testing. A branch was used for group/stacked LPE, but perhaps two people
(other than the devs) tested it a little.
Many bugs are discovered late, and it seems a branch will only delay
that. On the upside, there are also a lot of bugs that are discovered
early but the bugreports reach the developer(s) very late or not at all;
the upside is that when a branch is used, the bugs are easier to target
to a specific branch and to specific developer(s).

I think more important than a branch is a teamed effort for big
projects. From my own experience, refactoring alone is no fun;
refactoring in a team (thanks Verbal and Diederik!) is much more fun. So
I feel that before anyone should take up refactoring, he should find a
team to do it with. This reduces the risk of 'vacation' or 'sick of it'
problems.

Ciao,
Johan

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
Inkscape-devel mailing list
Inkscape-devel@...
https://lists.sourceforge.net/lists/listinfo/inkscape-devel

Re: Upcoming Releases

2009-11-03T17:40:02Z

On Tue, 2009-11-03 at 16:25 -0500, bulia byak wrote:
> Is this patch being worked on? It's been my impression that the issue
> is at least hard to reproduce, to start with.

Jon, care to comment?

> I may be wildly off the mark, but I would vote to release right now.

I will be honest that even if it is an issue, if we don't have a fix in
sight, it's worth releasing with this so we all can get on with active,
collaborative development.

> How do we define "major"?

Well, typically something that we would label as a refactoring task.
However, if someone has a "major" change and throws it in a branch and
it is deemed to be safe enough to be worth the possible risk for 0.48,
we'll merge it.

> Generally I'm in favor of making 0.48 more restrictive, because
> otherwise we won't be able to do it fast. I'd suggest that people
> start working on patches already, so they are ready to commit when we
> reopen!

I completely agree!

> Such policy is an absolute must, and mostly we adhere to it. I think
> it only gets violated when the damage is discovered too late when the
> original author is no longer available.

Well, this possibly ties into the branches stuff. I've noticed a few
times where people commit stuff and then leave on vacation or the like.
So, if someone has a number of changes that they want to commit and know
they will be unavailable for a few weeks to a few months or longer, put
it in a branch. Honestly, the same goes for "Here's what I've done, I
don't feel like working on it anymore" type contributions, until they've
been deemed safe to merge.

Cheers,
Josh

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
Inkscape-devel mailing list
Inkscape-devel@...
https://lists.sourceforge.net/lists/listinfo/inkscape-devel

Re: Upcoming Releases

2009-11-03T17:24:58Z

On Tue, 2009-11-03 at 23:54 +0100, J.B.C.Engelen@... wrote:
> I have several patches in the bugtracker that fix important issues:
> https://bugs.launchpad.net/inkscape/+bug/445790
> https://bugs.launchpad.net/inkscape/+bug/409043
>
> Less important but still:
> https://bugs.launchpad.net/inkscape/+bug/456148

Thanks, I will check these out either later tonight or tomorrow.

Cheers,
Josh

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
Inkscape-devel mailing list
Inkscape-devel@...
https://lists.sourceforge.net/lists/listinfo/inkscape-devel

Re: [win32] EPS/PS/PDF export of text objectsproblematic with 0.47(pre)

2009-11-03T17:08:19Z

Adding some numbers to illustrate my concerns (it's not about the number
of expected bug reports but the number of frustrated users...)

On 3/11/09 23:18, Jon wrote:
> * Keep the quality of the PDF high even if (in the short term) the
> exported file size is large

bug #271695:
632 KB (osx) vs. 24 MB (win32) (EPS export)

bug #431314:
80 KB (osx) vs. 3.8 MB (win32) (PDF export)
(and this is only a reduced case of a one-page-document, the original
file doesn't even get exported on win32)

> * Don't make me remember some hacky 'Path > Object to Path' before
> saving as EPS/PS/PDF workaround that goes away when you fix things.
> This is much uglier marketing wise than a short term file size issue
> in my opinion.

Without applying this 'hack' when using the current 0.47pre version you
get *both* bad text/font quality and even bigger file size when
exporting with the 'Convert texts to paths' option:

bug #271695:
2.7 MB (0.46) vs. 411 MB (0.47pre3) (EPS export)
(but with lower text/font quality due to bug #388257)

~suv

[ note: for the font embedding issue I don't have comparable file size
numbers of exports on linux platforms available ]

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
Inkscape-devel mailing list
Inkscape-devel@...
https://lists.sourceforge.net/lists/listinfo/inkscape-devel

Re: Upcoming Releases

2009-11-03T14:54:01Z

> -----Original Message-----
> From: bulia byak [mailto:buliabyak@...]
> Sent: dinsdag 3 november 2009 22:26
> To: Joshua A. Andler
> Cc: inkscape-devel
> Subject: Re: [Inkscape-devel] Upcoming Releases
>
> On Tue, Nov 3, 2009 at 3:05 PM, Joshua A. Andler
> <scislac@...> wrote:
> > Hey All,
> >
> > Obviously, we are still waiting on the final patch for 0.47
> before it
> > can be released. When we were wanting to release 0.46, we had a
> > similar issue with a Win32 specific issue holding up the
> release. This
> > brings up something that needs to be addressed before the
> 0.48 cycle begins.
>
> Is this patch being worked on? It's been my impression that
> the issue is at least hard to reproduce, to start with.
>
> I may be wildly off the mark, but I would vote to release right now.

I have several patches in the bugtracker that fix important issues:
https://bugs.launchpad.net/inkscape/+bug/445790
https://bugs.launchpad.net/inkscape/+bug/409043

Less important but still:
https://bugs.launchpad.net/inkscape/+bug/456148

- Johan

------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
Inkscape-devel mailing list
Inkscape-devel@...
https://lists.sourceforge.net/lists/listinfo/inkscape-devel

Re: [win32] EPS/PS/PDF export of text objectsproblematic with 0.47(pre)

2009-11-03T14:18:34Z

> My question was more towards the 'marketing' of Inkscape as a
> cross-platform tool that fully supports exchange with other vector
> format like PDF and PS. (And since I spent some time now with bug triage
> I am anticipating a lot of bug reports once Inkscape 0.47 is out and
> produces PDFs on win32 that are huge compared to the same files exported
> with Inkscape 0.46). But maybe I 'underestimate' the flexibility of
> Inkscape users on win32 platforms - that's why I asked for feedback ;-)

As an Inkscape on Windows user, my preferences...

* Ensure the cross-platform tool and exchange with other vector formats memes continue to be a high priority
* Keep the quality of the PDF high even if (in the short term) the exported file size is large
* Don't make me remember some hacky 'Path > Object to Path' before saving as EPS/PS/PDF workaround that goes away when you fix things. This is much uglier marketing wise than a short term file size issue in my opinion.
* Don't let the fix continually slide out because of "higher priorities"
* Don't let this become a blocking issue for 0.47 release

Yes, you'll likely get more bug reports filed, but maybe fewer than you think. If not, it just keeps you motivated to get rid of the issue ;)

Great job, and a big THANKS!

Jon

------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
Inkscape-devel mailing list
Inkscape-devel@...
https://lists.sourceforge.net/lists/listinfo/inkscape-devel