- Inkscape Devel - Inkscape Mailman

UniConvertor update for 0.48 on Windows
by Krzysztof Kosiński 13 Aug '10

13 Aug '10

Hello After some cowboy patching and hacking MinGW includes I managed to update UniConvertor to version 1.1.5 in the Windows devlibs (r18). The attached fix is required for the 0.48 branch in order to work properly with the updated UniConvertor; I have committed it to trunk already. I guess this was the last blocker issue for 0.48, so let's get on with releasing! Regards, Krzysztof

4 4

Fwd: Re : Inskape 0.48pre1 - Error message when saving as wmf
by Igor Novikov 13 Aug '10

13 Aug '10

On Thu, Jul 8, 2010 at 6:14 PM, bulia byak <buliabyak@...400...> wrote: > 2010/7/8 Nicolas Dufour <nicoduf@...48...>: > > 1. Removing the Uniconvertor scripts from the devlibs. UniConvertor > import or export scripts warn users to install UniConvertor manually (and > give the site address) when the libs are missing. (Note to self: fix the > gettext import bug in uniconv_output.py...). > > I think that will be perceived as a regression. Lots of formats that > used to work will suddenly stop working. We had a lot of pain with > displaying messages like this - most people simply perceive any such > message as an error and complain or give up without reading. Those who > read it and act on it will be a minority. > >From other side a lot of win32 users ask us "Why you announce XXX feature but i have not this in Inkscape?". We cannot synchronize our project development cycles, it's normally. But we could provide for user a way updating UniConvertor. External UniConvertor installation is a best solution because current bundle updating is a task rather for programmer than for conventional user/designer. > What's such a big problem with including a new UC into devlibs? > Actually there are not impossible tasks. It's just a subject of additional development time and resulted bundle size. Latest version has several new native extensions and more complex structure. And in next versions we will add new native resources because users ask for more and more complex features. As a simple solution we can provide for users an Inkscape-0.48-with-UniConvertor.zip archive with Inkscape installer, UniConvertor MSI and small REAME file inside. To simplify UniConvertor download the best way is not a message "You need downloading from bla-bla-bla site..." but just a button "Download" which opened browser on required page. Last option is for those users who download Inkscape exe installer only. Another valuable reason is planned preferences for translation. We are going provide a lot of translation options (we already have the code but we still not expose it as a command line options) and naturally such preferences could be managed better from GUI than command line. So we will add preferences dialogs for each format into UniConvertor. It's not an easy task so for Inkscape team will be better utilizing ready dialogs from UniConvertor than creating the same but on Inkscape side. And as I have wrote UniConvertor translation progress dialog would be also a good additional feature for Inkscape. Regards, Igor Novikov sK1 Project http://sk1project.org

7 19

Inkscape 0.48 status
by Joshua A. Andler 13 Aug '10

13 Aug '10

Hey All, 0.48 is wrapped up now code-wise... we got that Save As dialog issue on win32 fixed, uniconvertor on win32 is up to date, we also got 3 last minute Connector Tool crash fixes. I've requested that Ted cut the tarball, so once we have that the packagers can begin their work. I will only be available through next Sunday (22nd) to work on the release due to the upcoming surgery, and from the sound of things, probably won't be back anytime soon. I think we have more than enough time to get this done. Jon: Please update your stuff in the release notes. Cheers, Josh

1 0

svg open 2010, again
by Alexandre Prokoudine 12 Aug '10

12 Aug '10

Hi, Is anybody apart from Tav going to SVG Open 2010? :) Alexandre Prokoudine http://libregraphicsworld.org

1 0

Re: [Inkscape-devel] more UI mockups :)
by Valerie 12 Aug '10

12 Aug '10

> > This time UI mockups come from Pablo Lizardo: > > > > http://www.flickr.com/photos/pablolizardo/4845828488/in/photostream/ > > http://www.flickr.com/photos/pablolizardo/4845888941/in/photostream/ > > Apart from it being a clear Photoshop rip-off, it's not very much > different from our current interface. Except that Fill&Stroke is all > dumped into a single pane, losing many options along the way. > > Curiously, Photoshop had acquired a horizontal top panel with tool > options much later than other software, and I think even later than > Inkscape had it. And now we are urged to imitate Photoshop even in > that element. Familiarity so utterly trumps usability that it's not > even funny. Well, it seems you're looking more at the top panels while some of us are more focused on other parts. :) I didn't pay attention to the top panel until you mentioned it. Every mock-up will likely have its good parts and bad parts. Here's what I do like in these mock-ups: 1. The layer panel I like the arrangement, it makes efficient use of space but gives you information about a layer at just a glance. It just needs a slider to pop up besides the numerical value when clicked to adjust opacity more easily. I think the view button could be moved to the far left though to avoid accidentally clicking on the lock button. 2. Parts of the fill and stroke panel Of course, options will have to be restored, but there are elements I do think are interesting: a. The stroke/fill button I suppose when you click on the hollow square, the hollow square is brought to the forefont and you're basically editing your stroke color now, and vice-versa? I think this kind of preview is kind of neat. Of course, the options he removed will have to be brought back in. b. I like the more compact view for caps and markers, though some options are missing now. I wouldn't mind seeing something like this at the bottom: http://j.imagehost.org/view/0548/stroke For those who absolutely Need the names, the name could always pop up when you hover over it. I'm not so sure about the other proposed changes, but I did find these to be nice ideas. Right now I avoid using the fill and stroke panel whenever I can because it's a pain to navigate (too many tabs), something more compact may be nicer.

2 1

SpamBlacklist not working
by unknown＠example.com 12 Aug '10

12 Aug '10

I tried to revert the last edit to http://wiki.inkscape.org/wiki/index.php/MicrosoftVisio and the wiki responded to the Save page with: Warning: file(/var/www/wiki.inkscape.org/htdocs/extensions/SpamBlacklist/wikimedia_b… [function.file]: failed to open stream: No such file or directory in /var/www/wiki.inkscape.org/htdocs/extensions/SpamBlacklist/SpamBlacklist_body.php on line 97 Warning: array_merge() [function.array-merge]: Argument #2 is not an array in /var/www/wiki.inkscape.org/htdocs/extensions/SpamBlacklist/SpamBlacklist_body.php on line 97 Warning: array_map() [function.array-map]: Argument #2 should be an array in /var/www/wiki.inkscape.org/htdocs/extensions/SpamBlacklist/SpamBlacklist_body.php on line 102 Warning: array_filter() [function.array-filter]: The first argument should be an array in /var/www/wiki.inkscape.org/htdocs/extensions/SpamBlacklist/SpamBlacklist_body.php on line 102

1 0

more UI mockups :)
by Alexandre Prokoudine 11 Aug '10

11 Aug '10

Hi, This time UI mockups come from Pablo Lizardo: http://www.flickr.com/photos/pablolizardo/4845828488/in/photostream/ http://www.flickr.com/photos/pablolizardo/4845888941/in/photostream/ Alexandre Prokoudine http://libregraphicsworld.org

4 4

Crashes
by Joshua A. Andler 11 Aug '10

11 Aug '10

Hey All, It seems like a decent number of tweets and complaints I've seen around the community (understandably) are about inkscape crashing. Doing basic searches for bugs tagged w/ crash gives the following info: All statuses is over 200 bugs and Confirmed or In Progress have 84. 84 crash bugs that can be reproduced seems unreasonably high for something intended for production work and code-wise there's a chance that some are caused by shared underlying issues. If anyone is interested in taking a look into these to see if there are any you might be able to fix, that would be awesome. http://bit.ly/InkCrash Cheers, Josh

4 12

Release Notes for 0.48: Connectors and Swatches
by Tavmjong Bah 09 Aug '10

09 Aug '10

Hi, There appears to be nothing in the release notes about the new Connector Tool additions. The Swatches section needs to be expanded with an explanation of how to use them. Why is a linear gradient created when clicking on the Swatches icon in the Fill and Stroke dialog? Tav

4 3

3D Box and 0.49
by Krzysztof Kosiński 08 Aug '10

08 Aug '10

Hello 3D Box is the main thing that prevents us from fixing the coordinate system bug. (The second thing are guides, but they're much easier to fix.) The reason is that it has a design fault - it stores perspectives and faces in desktop coordinates. A simple Y inversion does not fix the problem, because some code (e.g. default face coloring) is dependent on the chirality of the 3D coordinate system, and flipping the Y axis inverts the chirality. There's also a slew of other bugs related to 3D box in our bug tracker. What do we do with it in 0.49? I would really like to see the coordinate system bug fixed in 0.49, even if it means rewriting the 3D box from scratch, or even disabling it. Fancy features aren't very useful if we don't get the basics right. The issue of supporting legacy documents with 3D boxes is separate and I think it can be done if the 3D box gets rewritten first. We would just need to fix the document at load time. Initially I wanted to do this by direct XML manipulation before creating the SP tree, but now I see this has limitations - compatibility code at SP level is probably a better idea. Regards, Krzysztof.

2 1