0.44.1 pre1??? what about bug 1535218???
Hi all,
Sorry to post this here, but today Mental posted in the devel list that 0.44.1pre1 is beeing released, althought nobody seem to react to a critical bug report in the bug tracker at sourceforge. I am talking about bug 1535218 (or should I actually call it a regression as it didn't appear in 0.44 release and was introduced in later devel builds) is beeing fixed by someone? I reported it 10 days ago, and it seems that no one is interested in fixing it... But for users, it is a showstopper, as it occurs always when the object's fill gradient is applied to object's stroke (steps to reproduce are described in the bug tracker, see http://sourceforge.net/tracker/index.php?func=detail&aid=1535218&gro... )
It is still present in today's inkscape-0608151000 build, and I'd hate to see this bug make it to 0.44.1 release...
Thanks!
Molumen
On Tue, 2006-08-15 at 21:27 +0200, momo wrote:
Sorry to post this here,
No need to apologize, it's on-topic for the list.
I reported it 10 days ago, and it seems that no one is interested in fixing it...
It'd just gone unnoticed so far. We usually only go through the bug tracker periodically, and prior to a major release.
But for users, it is a showstopper, as it occurs always when the object's fill gradient is applied to object's stroke (steps to reproduce are described in the bug tracker, see http://sourceforge.net/tracker/index.php?func=detail&aid=1535218&gro... )
It is still present in today's inkscape-0608151000 build, and I'd hate to see this bug make it to 0.44.1 release...
Chances are that 0.44.1 is safe, since it's based on 0.44 rather than trunk. I'll check, of course.
With trunk however, I have confirmed that the bug also occurs on Linux, so it's not a platform-specific bug. Looks like an invariant may be violated when the prior stroke gradient is released.
-mental
On Tue, 2006-08-15 at 16:54 -0400, MenTaLguY wrote:
It is still present in today's inkscape-0608151000 build, and I'd hate to see this bug make it to 0.44.1 release...
Chances are that 0.44.1 is safe, since it's based on 0.44 rather than trunk. I'll check, of course.
(0.44.1 wasn't affected)
With trunk however, I have confirmed that the bug also occurs on Linux, so it's not a platform-specific bug. Looks like an invariant may be violated when the prior stroke gradient is released.
Found the problem and fixed it. I'm afraid the bug was my fault, too; sorry about that... The fix should show up in the nightly builds soon.
Thanks for reporting the bug! It was even more serious than it looked.
-mental
Hello,
Thanks for the reply, Mental! I will test the 0.44.1 pre1 for windows as soon as it appears, and report to the devel list if that bug is still present.
Regards,
Molumen
----- Original Message ----- From: "MenTaLguY" <mental@...3...> To: "momo" <momo@...1386...> Cc: inkscape-devel@lists.sourceforge.net Sent: Tuesday, August 15, 2006 10:54 PM Subject: Re: [Inkscape-devel] 0.44.1 pre1??? what about bug 1535218???
On Tue, 2006-08-15 at 21:27 +0200, momo wrote:
Sorry to post this here,
No need to apologize, it's on-topic for the list.
I reported it 10 days ago, and it seems that no one is interested in fixing it...
It'd just gone unnoticed so far. We usually only go through the bug tracker periodically, and prior to a major release.
But for users, it is a showstopper, as it occurs always when the object's fill gradient is applied to object's stroke (steps to reproduce are described in the bug tracker, see http://sourceforge.net/tracker/index.php?func=detail&aid=1535218&gro... )
It is still present in today's inkscape-0608151000 build, and I'd hate to see this bug make it to 0.44.1 release...
Chances are that 0.44.1 is safe, since it's based on 0.44 rather than trunk. I'll check, of course.
With trunk however, I have confirmed that the bug also occurs on Linux, so it's not a platform-specific bug. Looks like an invariant may be violated when the prior stroke gradient is released.
-mental
This build from current SVN has the fix in it: http://inkscape.modevia.com/win32/Inkscape0608160007.zip
It's not the branch, but it's a good way to test.
bob
momo wrote:
Hello,
Thanks for the reply, Mental! I will test the 0.44.1 pre1 for windows as soon as it appears, and report to the devel list if that bug is still present.
Regards,
Molumen
----- Original Message ----- From: "MenTaLguY" <mental@...3...> To: "momo" <momo@...1386...> Cc: inkscape-devel@lists.sourceforge.net Sent: Tuesday, August 15, 2006 10:54 PM Subject: Re: [Inkscape-devel] 0.44.1 pre1??? what about bug 1535218???
On Tue, 2006-08-15 at 21:27 +0200, momo wrote:
Sorry to post this here,
No need to apologize, it's on-topic for the list.
I reported it 10 days ago, and it seems that no one is interested in fixing it...
It'd just gone unnoticed so far. We usually only go through the bug tracker periodically, and prior to a major release.
But for users, it is a showstopper, as it occurs always when the object's fill gradient is applied to object's stroke (steps to reproduce are described in the bug tracker, see http://sourceforge.net/tracker/index.php?func=detail&aid=1535218&gro... )
It is still present in today's inkscape-0608151000 build, and I'd hate to see this bug make it to 0.44.1 release...
Chances are that 0.44.1 is safe, since it's based on 0.44 rather than trunk. I'll check, of course.
With trunk however, I have confirmed that the bug also occurs on Linux, so it's not a platform-specific bug. Looks like an invariant may be violated when the prior stroke gradient is released.
-mental
Thank you, Bob
I downloaded inkscape-0608160200.7z and tested it, and yes, the bug is gone :) Many thanks to Mental for fixing it, we can now continue to test Inkscape in a production environement (we have it installed on every machine in our graphic design studio)
Just a question: when will 0.44.1 pre1 for windows be available?
Molumen
----- Original Message ----- From: "Bob Jamison" <rwjj@...127...> To: inkscape-devel@lists.sourceforge.net Sent: Wednesday, August 16, 2006 2:40 PM Subject: Re: [Inkscape-devel] 0.44.1 pre1??? what about bug 1535218???
This build from current SVN has the fix in it: http://inkscape.modevia.com/win32/Inkscape0608160007.zip
It's not the branch, but it's a good way to test.
bob
momo wrote:
Hello,
Thanks for the reply, Mental! I will test the 0.44.1 pre1 for windows as soon as it appears, and report to the devel list if that bug is still present.
Regards,
Molumen
----- Original Message ----- From: "MenTaLguY" <mental@...3...> To: "momo" <momo@...1386...> Cc: inkscape-devel@lists.sourceforge.net Sent: Tuesday, August 15, 2006 10:54 PM Subject: Re: [Inkscape-devel] 0.44.1 pre1??? what about bug 1535218???
On Tue, 2006-08-15 at 21:27 +0200, momo wrote:
Sorry to post this here,
No need to apologize, it's on-topic for the list.
I reported it 10 days ago, and it seems that no one is interested in fixing it...
It'd just gone unnoticed so far. We usually only go through the bug tracker periodically, and prior to a major release.
But for users, it is a showstopper, as it occurs always when the object's fill gradient is applied to object's stroke (steps to reproduce are described in the bug tracker, see http://sourceforge.net/tracker/index.php?func=detail&aid=1535218&gro... )
It is still present in today's inkscape-0608151000 build, and I'd hate to see this bug make it to 0.44.1 release...
Chances are that 0.44.1 is safe, since it's based on 0.44 rather than trunk. I'll check, of course.
With trunk however, I have confirmed that the bug also occurs on Linux, so it's not a platform-specific bug. Looks like an invariant may be violated when the prior stroke gradient is released.
-mental
Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&da... _______________________________________________ Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel
On Wed, 16 Aug 2006, momo wrote:
Many thanks to Mental for fixing it, we can now continue to test Inkscape in a production environement (we have it installed on every machine in our graphic design studio)
That's interesting, are you having any deployment issues on a network? Why did you guys decide to try out Inkscape? Are you doing print work with it, or mostly web?
--Ted
Ted,
That's interesting, are you having any deployment issues on a network?
Well, we never encountered any problems on that side... Inkscape smoothly run on all the machines here (win 2000 and win XP)
Why did you guys decide to try out Inkscape?
Our designers (including me) just loved the interface (very intuitive and simple). Inkscape's work with tablet is also very smooth, so one of our illustrators use it almost on a daily basis. The tracing tool is one of the most used features by our printing designers: we use it specially to trace bitmap data that aren't available in curves, that we need to use in large scale printing (like logos, slogans etc...). Also we use Inkscape to create webdesign elements (all kind of buttons, panels, etc...). Inkscape's export to bitmap is one of the smoother available on the market today. We compared it to Illustrator CS, Corel Draw 12 and Photoshop's rasterising capabilities, and Inkscape almost always had better results, specially on smaller details/graphics. For example all the icons and smaller graphics on that web are made in Inkscape: www.czechwalker.com
Are you doing print work with it, or mostly web?
Unfortunately Inkscape is not mature enought to be used in printing because of the lack of real CMYK / LAB/ HSB support (SVG 1.2 needed here), very poor export capabilities (yesterday I posted a bug report about resulting PDF files, #1541366) and the poor direct printing possibilities. Everything that comes out from Inkscape is RGB, so talking about printing with Inkscape is a little too soon. Inkscape is still just a supporting software, interesting to print designers by a few of its functions. One of the biggest breaktrough for Inkscape in the field of printing (after the CMYK/LAB/etc... support) will be a descent PDF exporting capability. By descent, I mean the ability to: - generate multipage PDF documents (that hopefully will be possible with SVG 1.2 spec.) - export in the PDF printing spec. (PDF/X-1a, PDF/X-3) - define the bleed and slug areas (for offset printing) - add crop, bleed and registration marks, file infos/comments, color bars. This is what actually does Corel Draw, and it is widely used in our studio for small to medium printing jobs (business cards, brochures, booklets, fliers etc...). The resulting PDFs are directly sent to the printing house.
Another field of use for Inkscape that we (at Lumen Design Studio) see for the future, is the creation of SVG graphics for mobile devices (SVG Tiny/Basic spec.). If Inkscape in its future releases will have the possibility to select the specification of the created file, it will become an irreplaceable tool.
If you'd like, we can actually write some kind of article about the use of Inkscape in our design studio, some kind of interview of every designer, describing the use of Inkscape in every field (printing, webdesign, etc...). Maybe posting it in the wiki will help others to realise what can be done with Inkscape :)
I'm very thankful to all the Inkscape devellopers. You managed to create one of the most attractive vector drawing software available today, and you still devellop it very fast. Thank you!
Best regards from Prague, Mourad Mokrane Art director Lumen Design Studio www.lumenstudio.net T +420 777 164 358 F +420 221 085 247
----- Original Message ----- From: "Ted Gould" <ted@...11...> To: "momo" <momo@...1386...> Cc: inkscape-devel@lists.sourceforge.net Sent: Wednesday, August 16, 2006 6:47 PM Subject: Inkscape at Lumen (was: what about bug 1535218???)
On Wed, 16 Aug 2006, momo wrote:
Many thanks to Mental for fixing it, we can now continue to test Inkscape in a production environement (we have it installed on every machine in our graphic design studio)
That's interesting, are you having any deployment issues on a network? Why did you guys decide to try out Inkscape? Are you doing print work with it, or mostly web?
--Ted
On 17/08/06, momo <momo@...1386...> wrote:
Ted,
... If you'd like, we can actually write some kind of article about the use of Inkscape in our design studio, ...
Could I vote yes to that. To be fair, your info which I snipped is probably enough for us if you are pressed for time, but the use of Inkscape in Design or Publishing is something we would like to hear more about.
At the LUG Radio live, where there were about 170 boys and girls all wearing black shirts emblazoned "cd /pub ; more beer" - or so it seemed, plenty of people said that they used Inkscape for their work: diagrams, icons, logos UI mock ups and web page mock ups. (Since I do web page mock ups in vim, I found the last a little difficult to understand). The actual use - workflow - of Inkscape in a design studio is something I for one would like to hear described, and also any areas where you feel that Inkscape is weak.
Ben
You top post here, yes? I think someone picked me up on that one already. Sorry if I got it wrong ...
OK. I've used Inkscape when developing websites to layout pages as a sort of fast prototype. It's the step after first drafts (in pencil or crayon) but before the client gets to mess it all up. The advantage being that I can then export buttons and gradient fills as PNG and use them in the final page. I use layers to provide for on/off CSS rollovers so that I can do page views which show some of the event based CSS effects.
Of course one finds that it's not possible to transfer across the design "verbatim" but it still useful. I might of used Scribus but I find it a bit unwieldy sometimes and can work a lot faster in Inkscape. Generally I'd like to be able to mix gimp layers, inkscape vectors and scribus layout and pdf handling all in the same app ... let me know when you're done :0)>
Prototypes this way a nice idea of the final look and can be adjusted very quickly. Often we don't have content at this stage and usually http://communimedia.com also have print contracts in parallel so we're not starting from nothing there's usually a few style elements aroud which to mould the site. I'd love to have a wysiwyg page layout package to do this with - I've tried starting in DW templates and then hacking it to get the code nice (ie XHTML1 trans) but this takes longer that hand-writing the whole thing using PHP includes. Nvu, Bluefish and Quanta don't cut it for me yet. Kate / jEdit is my current tool of choice!
The first site I did this process on was crowpoint.co.uk, SVG file (Inkscape 0.43), some page elements / furniture and png screenshot attached. We had a logo from another designer but that was all the lead. The main problem I had (which had been mentioned recently, on the wiki I think) was in getting the repeat on the background right when I came to extract the gradient to put on the web.
Using Inkscape for my web design work prompted me to get more involved - so I'm trying to test svn and to add some useful stuff to the wiki. I also use Inkscape in my other work at a paint your own pottery studio http://barefoot-ceramics.com ... but more on that some other time.
HTH and thanks for all the code.
Paul
PS: Sorry about the weight of this mail, but I thought it would be more instructive with images.
On Thursday 17 August 2006 16:17, Ben Fowler wrote:
On 17/08/06, momo <momo@...1386...> wrote:
<snip>
seemed, plenty of people said that they used Inkscape for their work: diagrams, icons, logos UI mock ups and web page mock ups. (Since I do web page mock ups in vim, I found the last a little difficult to understand). The actual use - workflow - of Inkscape in a design studio is something I for one would like to hear described, and also any areas where you feel that Inkscape is weak.
Ben
On Thu, Aug 17, 2006 at 09:18:44PM +0100, pbhj wrote:
You top post here, yes? I think someone picked me up on that one already. Sorry if I got it wrong ...
We're not anal about it, but we typically encourage in-line posting, with ample trimming of stuff from prior posts.
OK. I've used Inkscape when developing websites to layout pages as a sort of fast prototype. It's the step after first drafts (in pencil or crayon) but before the client gets to mess it all up. The advantage being that I can then export buttons and gradient fills as PNG and use them in the final page. I use layers to provide for on/off CSS rollovers so that I can do page views which show some of the event based CSS effects.
Cool. It amazes me all the different ways people use Inkscape. It's actually a bit of a shame there's so *many* use cases, because it makes it more challenging to decide where to focus... Features for people interested in print work won't help people that want an SVG generation tool, or an animation tool, or a website editor, or a technical drawing tool, or.....
This is why we always love welcoming new people who want to help out in areas that we currently lack developers.
Using Inkscape for my web design work prompted me to get more involved - so I'm trying to test svn and to add some useful stuff to the wiki. I also use Inkscape in my other work at a paint your own pottery studio http://barefoot-ceramics.com ... but more on that some other time.
HTH and thanks for all the code.
Cool, and welcome aboard! :-)
PS: Sorry about the weight of this mail, but I thought it would be more instructive with images.
Thanks. As you might have noticed, the mailing list software choked on it, so it didn't actually come through until today. Sorry about that!
For future reference, most people will post examples to a website, and just include a URL in their email. This is particularly helpful for people who follow the inkscape list through the digest version - it can't really handle attachments. It also helps people viewing archived email messages, since archivers often mess up attachments.
Bryce
On 8/17/06, momo <momo@...1386...> wrote:
If you'd like, we can actually write some kind of article about the use of Inkscape in our design studio, some kind of interview of every designer, describing the use of Inkscape in every field (printing, webdesign, etc...). Maybe posting it in the wiki will help others to realise what can be done with Inkscape :)
Excellent idea, I would love to read it!
On Fri, 2006-08-18 at 00:28 -0300, bulia byak wrote:
On 8/17/06, momo <momo@...1386...> wrote:
If you'd like, we can actually write some kind of article about the use of Inkscape in our design studio, some kind of interview of every designer, describing the use of Inkscape in every field (printing, webdesign, etc...). Maybe posting it in the wiki will help others to realise what can be done with Inkscape :)
Excellent idea, I would love to read it!
Me too :) I think that there would be interest in publishing it to a larger audience than just our website. I think most Linux news outlets like publishing case studies, but I would rather see the article in something more art based. Though, I don't know of any that would be interested in such an article.
--Ted
On Wed, 2006-08-16 at 13:01 +0200, momo wrote:
Hello,
Thanks for the reply, Mental! I will test the 0.44.1 pre1 for windows as soon as it appears, and report to the devel list if that bug is still present.
0.44.1 is just a maintenance release of 0.44; it never contained the bug.
- --+-------------+--+--+-> trunk | \ \ \ +- 0.44 nightly builds | +- 0.44.1
-mental
OOOps!!! My bad! I thought that 0.44.1 will be based on the trunk, that's why I started all that noise about bug 1535218 :((( My apologizes to everybody!!!!
Molumen
----- Original Message ----- From: "MenTaLguY" <mental@...3...> To: "momo" <momo@...1386...> Cc: inkscape-devel@lists.sourceforge.net Sent: Wednesday, August 16, 2006 5:50 PM Subject: Re: [Inkscape-devel] 0.44.1 pre1??? what about bug 1535218???
On Wed, 2006-08-16 at 13:01 +0200, momo wrote:
Hello,
Thanks for the reply, Mental! I will test the 0.44.1 pre1 for windows as soon as it appears, and report to the devel list if that bug is still present.
0.44.1 is just a maintenance release of 0.44; it never contained the bug.
- --+-------------+--+--+-> trunk | \ \ \ +- 0.44 nightly builds | +- 0.44.1
-mental
participants (8)
-
Ben Fowler
-
Bob Jamison
-
Bryce Harrington
-
bulia byak
-
MenTaLguY
-
momo
-
pbhj
-
Ted Gould