Chris Lilley wrote:
> On Saturday, January 16, 2010, 10:32:16 PM, knowone wrote:
> k> How can I save the file as PNG with the drop shadow intact?
> Make sure you are exporting as PNG. Do not 'Save As' Cairo PNG.
> (I came across this a couple of days ago, and the symptom was that blur filters were not being applied. Also, the pixel dimensions of the two methods differ, if the graphic bleeds over the edge of the 'page').
Can someone tell me why we have a non-vector format in the save as list?
One that seems redundant and apparently with less functionality than the
normal export. Is this for testing purposes?
I just built the inkscape trunk from bzr and ran this script
bus = dbus.SessionBus()
inkdoc1 = bus.get_object('org.inkscape', '/org/inkscape/desktop_0')
doc1 = dbus.Interface(inkdoc1, dbus_interface="org.inkscape.document")
im = doc1.image(100 ,100, '/home/ktenney/Firefox_wallpaper.png')
Which worked on a dbus branch a while back.
Now it starts inkscape, but does not place the image
- was the dbus code merged?
- if so, how do I enable/use it?
- if not, where is dbus capable code?
Are we still waiting for the SVG standards before we can implement gradient
I have a ( pretty simple and obvious ) method of rendering gradient meshes
that is simpler than blurring multiple beziergons and is quite fast ( 100 ms
in Java rendering 500x500px approx ), I was wondering if we start putting a
basic gradient mesh in inkscape and we can conform/export to the SVG format
when it comes out.
I believe we are trying to get a triangle gradient primitive approved from
SVG. Do we have any plans of getting a quadrilateral primitive ? It will be
more accurate for gradient mesh. This paper I found explains some
quadrilateral rendering techniques :
just wanted to ask if new development version will be available for testing on http://inkscape.modevia.com/win32/?M=D . It seems that no new devel builds have appeared there for quite some time.
Roland Meub has posted a patch to implement this nice feature (see https://bugs.edge.launchpad.net/inkscape/+bug/171944).
It compiles and works correctly on Ubuntu 9.10, and the only glitch I've found is related to 3Dbox (unexpected translations).
Could a C++ expert review this code and commit?
The new node tool is now in the trunk - please test and report any
bugs. I made a few last minute improvements inspired by the
New features are listed in the release notes:
I also made a new icon for the spray tool. It's much better than the
old one, but there's still something not quite right with it.
Hi, I'm Bryan, the original author of pixelsnap.
I'd be keen to have PixelSnap included in the official Inkscape repository,
and to do whatever's necessary for that purpose (I don't mind releasing it
under GPL, either -- I just like the MIT license because it's short & sweet)
Just a brief rant on why I think PixelSnap is a useful part of a digital
artist's workflow, even if they know inkscape's tools:
I'm a fairly technical user of Inkscape, but in spite of the great work done
on snapping & grids recently (kudos to the people involved with that!), I've
still found the "right" way to be a bit of a pain in the backside.
The reasons Rob gives below are two good examples. Another big reason why
the "right" way is often unworkable is the fact that odd-width strokes are
offset by exactly 0.5 pixels. I understand the reasoning for this, but it
means you have to have 2 pixel-sized grids, one pixel-aligned, and one
Also, you have to keep the grid on permanently while editing for the "right"
way to work, unless you want to go back and edit all your vectors later on.
I don't find it very easy working with grids all over my work. Sometimes I
don't want stuff to snap either -- I only want vertical & horizontal lines
I'd also rather set up meaningful grids for my artwork -- i.e. grids for
layout purposes, not grids to overcome the shortcomings of my screen.
Alexandre Prokoudine wrote:
> On 1/13/10, Rob Antonishen wrote:
>> The biggest benefit is when working with existing images that were not
>> necessarily drawn to pixel snap.
>> Or after rescaling images and resnapping the elements to the nearest
> Exactly :)
Bryan Hoyt, *Web developer* — Brush Technology
*Ph:* +64 3 942 7833 *Mobile:* +64 21 238 7955
On 17/1/10 12:47, Michael Wybrow wrote:
> On 11/01/2010, at 11:42 PM, JiHO wrote:
>>> On 7/12/09 20:51, Wolf Drechsel wrote:
>>>> my attempt in building a 0.47 X11 on Tiger can be visited.
>>>> It is PPC only - are there people around who need Tiger-Intel?
>> I'd say, post it like that. I don't and won't ever have a Tiger
>> machine to test it. The release will be the large scale test I am
>> afraid. I agree it should be posted, as a reward for Wolf's tremendous
> I tested Wolf's build on Friday and it worked fine other than the
> status bar issue which also occurs on all versions of Inkscape I
> tested (though it does go blank moving over the page sliders on 10.4
> but not the other later versions).
> I forgot to write a response on Friday, but you may have noticed that
> I compressed it as a DMG and uploaded in to Sourceforge.
> Thanks for all your work on this Wolf, and also ~suv. Much
Could the newly uploaded Tiger PPC build please be added to the
download page on inkscape.org?
Stable release 0.47 intended for production use is available:
* Mac OS X
o OS X 10.6, Snow Leopard – Universal .dmg
o OS X 10.5, Leopard – Universal .dmg (Please first upgrade X11.app to at least XQuartz v2.1.4.)
+ o OS X 10.4, Tiger - PPC .dmg  (requires Apple's X11 v1.1.3)
I noticed that a few bugs were assigned to somebody with an account
called "krzysztof kosinski (krzy-kos)". I would like to point out that
it's not me, and I'm not receiving notifications about this. My
account is called "Krzysztof Kosiński (tweenk)".
Maybe we could put such information here?