- Inkscape Devel - Inkscape Mailman

Re: [Inkscape-devel] Visio support
by MilesTogoe 08 Dec '09

08 Dec '09

On 12/07/2009 04:17 PM, Alexandre Prokoudine wrote: > R U sure you wanted to send this privately? :) > not private - forgot to hit reply-all > Alexandre > > On 12/8/09, MilesTogoe<miles.togoe@...400...> wrote: > >> On 12/07/2009 02:51 PM, Alexandre Prokoudine wrote: >> >>> On 12/8/09, Paul den Hertog wrote: >>> >>> >>> >>>> Diederik: Visio 2003 can export to SVG if I'm correct. Have you tested >>>> that? And have you seen this: >>>> >>>> http://vdxtosvg.sourceforge.net/ >>>> >>>> >>> Can't speak for Diederik, but I tried this and it didn't work for me out >>> of box. >>> >>> >>> >>>> By the way, are extentions called tools on the website? >>>> >>>> >>> Where exactly? >>> >>> Alexandre >>> >>> >>> >> dia and kivio have never really cut it compared to visio. some more >> Inkscape features might be worthy of consideration for a summer of code >> project - pieces are there (connectors, resizing objects) ie I drag in >> all kinds of road symbols from another inkscape template drawing, resize >> and are good to go. I see some areas needing work: >> 1) the connectors seem to need some work (have not tried in .47 to see >> if any diffs) >> 2) centered text - text and a shape can be grouped but I don't think the >> textbox can always remain centered - a uml type group would also be very >> handy >> 3) visio file import (incl pre MS purchase for us former users) >> 4) it would be so much nicer if arrowheads would take same color as >> stroke without have to call in separate extension >> >> haven't used visio in so long, I forget if there were other things I >> missed. >> >> >> >> >> >> >> >> >>> ------------------------------------------------------------------------------ >>> Return on Information: >>> Google Enterprise Search pays you back >>> Get the facts. >>> http://p.sf.net/sfu/google-dev2dev >>> _______________________________________________ >>> Inkscape-devel mailing list >>> Inkscape-devel(a)lists.sourceforge.net >>> https://lists.sourceforge.net/lists/listinfo/inkscape-devel >>> >>> >>> >> >> > >

1 0

Re: [Inkscape-devel] Visio support
by Paul den Hertog 07 Dec '09

07 Dec '09

On Tue, 2009-12-08 at 00:51 +0300, Alexandre Prokoudine wrote: > On 12/8/09, Paul den Hertog wrote: > > > Diederik: Visio 2003 can export to SVG if I'm correct. Have you tested > > that? And have you seen this: > > > > http://vdxtosvg.sourceforge.net/ > > Can't speak for Diederik, but I tried this and it didn't work for me out of box. > > > By the way, are extentions called tools on the website? > > Where exactly? > > Alexandre > > ------------------------------------------------------------------------------ > Return on Information: > Google Enterprise Search pays you back > Get the facts. > http://p.sf.net/sfu/google-dev2dev > _______________________________________________ > Inkscape-devel mailing list > Inkscape-devel(a)lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/inkscape-devel On the main website: http://wiki.inkscape.org/wiki/index.php/Tools Or is there another repository of extentions? I shall do some tests tomorrow with the exported files trough Visio and Inkscape, I'm curious what the resulst will be.

1 0

Re: [Inkscape-devel] Visio support
by Paul den Hertog 07 Dec '09

07 Dec '09

On 12/07/2009 09:28 PM, Paul den Hertog wrote: > This is rather new for me, posting on a list trough email. So if I do > something wrong, please correct me. Diederik: Welcome! I didn't notice anything wrong yet ;-) Paul: Haha thanks :-) > Inkscape was just it for making vector logo's and lay-outs, but I am > realy missing Visio support. If this would get implemented in Inkscape > it will be definitely a true winner. Diederik: Visio 2003 can export to SVG if I'm correct. Have you tested that? And have you seen this: http://vdxtosvg.sourceforge.net/ Paul: Hmm.. I definitely check this out. The problem is that my school team always save there files in .vsd. Is there a possibility to convert this to a format i can use, within Linux? Currently I am explorering all the features of Inkscape, nice work!! I've noticed that there is a portable version, so I will try to get my team to use it :) We have all sort of shapes in our business models, can I donate them to the community like a .vst (I think Visio shape template) or separate .vss (Visio shape's file). Then the creation of diagrams are heavily simplified. Alexandre: Dia actually can import VDX files (XML based Visio files from Office 2003) and export SVG, so you can use Dia as a roundabout to some extent. Paul: I smell a opportunity to implement this in Inkscape :$, But for the meantime it looks like a nice workaround. I must say that Dia looks nice, but is rather difficult. By the way, are extentions called tools on the website? Thanks again : ), Paul

1 0

Re: [Inkscape-devel] Visio support
by Alexandre Prokoudine 07 Dec '09

07 Dec '09

On 12/8/09, Paul den Hertog wrote: > Diederik: Visio 2003 can export to SVG if I'm correct. Have you tested > that? And have you seen this: > > http://vdxtosvg.sourceforge.net/ Can't speak for Diederik, but I tried this and it didn't work for me out of box. > By the way, are extentions called tools on the website? Where exactly? Alexandre

1 0

Visio support
by Paul den Hertog 07 Dec '09

07 Dec '09

Hello, This is rather new for me, posting on a list trough email. So if I do something wrong, please correct me. I've been a Windows user for years, but I made the switch to linux a year ago. After some test ofcource. Most of my that I used had good natives in Linux, photoshop -> gimp (did took some time, but was worth the effort) and office. But I am a frequent user of Visio, I used to make landscape drawings of networks and now on school business diagrams. Inkscape was just it for making vector logo's and lay-outs, but I am realy missing Visio support. If this would get implemented in Inkscape it will be definitely a true winner. I can't code myself, I realy want to help. I did post a question on Launchpad, but they told me to do a post here. Link: https://answers.launchpad.net/inkscape/+question/93150 School is a time consuming hobby, but I want to help where I can. Thanks for reading, Paul

3 2

Rendering of the 0.47 about screen
by JiHO 07 Dec '09

07 Dec '09

Rendering the 0.47 about screen with normal quality for blur en effects in the preferences I get this: http://dl.dropbox.com/u/1047321/Screen%20shot%202009-12-07%20at%2014.00.02%… Is that limited to my system? OS X Snow Leopard, release version of Inkscape. JiHO --- http://maururu.net

2 2

Inkscape devel snapshots
by heathenx 07 Dec '09

07 Dec '09

I have been using http://inkscape.modevia.com/svn-snap/?M=D in the past to grab sourceforge snapshots periodically. Is there a going to be a new place to grab the bazaar snapshots or does it work differently now? heathenx

1 0

Inkscape Mac Os X 64bit
by Giovanni Lanzani 07 Dec '09

07 Dec '09

I was wondering, now that SL supports 64bit widely, is it possible to create an Inkscape build which runs in 64bit? lisanet.de already made one from Gimp, and it seems to be working much faster than before. Of course in Gimp speed is more relevant than in Inkscape, but I guess a speed up is welcome (even if it would just be a startup speed up). Or are there things (like Python libraries, etc.) which prevent this? Thanks Giovanni

3 6

new: SVG Color 1.2 uncalibrated device colors
by Felipe Sanches 07 Dec '09

07 Dec '09

folks, Today I have implemented parsing, output and basic handling of uncalibrated device colors as defined in SVG Color 1.2 Working Draft: http://www.w3.org/TR/2009/WD-SVGColor12-20091001/#device I have hooked device-cmyk handling to our color pickers so that if you select colors in the CMYK tab, these ink values will be preserved, unless you switch to some other color picker tab. Color space conversion happens every time you switch color pickers. Both SVG 1.1 color values and device-cmyk values are output, but device-cmyk is the value used whenever it is available. I'd like to thank the effort of the brazillian inkscape users community for mantaining a wiki-page that lists what they believe that needs to be implemented in CMYK/professional printing support from the perspective of users and print professionals. Theis wiki-page is here: http://wiki.softwarelivre.org/InkscapeBrasil/EspecificacaoCMYK (in brazillian portuguese) Felipe "Juca" Sanches

2 2

Re: [Inkscape-devel] URGENT: Please update Mac OS X install instructions in the tarball !
by ~suv 07 Dec '09

07 Dec '09

On 30/11/09 13:24, Wolf Drechsel wrote: >>> I am very grateful that a lot of people invested lots of time in the >>> wonderful packaging/macosx/osx-build.sh script. >>> >>> PLEASE, add a few lines to the READMEs - or create a distinguished >>> "README_Mac_OS_X" to make clear, that the install procedure on a Mac >>> is a different one. >> >> Could you propose what should be added to the README. I think it's a >> good idea to update it, but I'm afraid that I would write something >> incorrect if I tried as I have no experience on OSX. > > I'll be happy to give it a try - could friend ~suv have a look on it in > order to avoid greater portions of nonsense please ? I am not very comfortable with the proposed changes by Wolf: a) README why only adding hints for OS X users? There are other platforms with special build tools (e.g. btool for win32) and - judging from the list of wiki pages about compilation on different linux platforms - deviations/adaptations from the generic 'configure/make/make install' routine are more common and not limited to Mac OS X. b) INSTALL again - why adding only one of the sub-pages from the wiki which is already linked from the top wiki page about compilation and not the others as well? Personally I'd keep it as it is. If you need more information, the instructions are clear: read the wiki pages. Alternative proposal 1) In the README file add a section to or after the description of the generic installation, mentioning the wiki pages for more information about platform specific issues. 2) In 'packaging/macosx' and 'packaging/win32' add new README files containing either a summary or a copy of the platform specific wiki page about building and packaging. OTOH a 'packaging/macosx/README' could be as short as 1) please read the wiki page about compiling Inkscape on OS X: <http://wiki.inkscape.org/wiki/index.php/CompilingMacOsX> 2) consider additional information about MacPorts installation: <http://www.macports.org/install.php> using MacPorts: <http://guide.macports.org/#using> 3) run './osx-build.sh help' for an overview of the options available to configure, build and package Inkscape on OS X ~suv appending fullquote since Wolf's mail didn't make it to the list: >>> I am very grateful that a lot of people invested lots of time in the >>> wonderful packaging/macosx/osx-build.sh script. >>> >>> PLEASE, add a few lines to the READMEs - or create a distinguished >>> "README_Mac_OS_X" to make clear, that the install procedure on a Mac >>> is a different one. >> >> Could you propose what should be added to the README. I think it's a >> good idea to update it, but I'm afraid that I would write something >> incorrect if I tried as I have no experience on OSX. > > I'll be happy to give it a try - could friend ~suv have a look on it in order to avoid greater portions of nonsense please ? > > I suggest to change this chapter of the README: > >> Inkscape uses the standard procedure for compilation and installation: >> >> ./configure >> make >> make install >> >> If a "./configure" file is not present, you can create it by running >> the "./autogen.sh" command, which calls in turn a number of other >> programs such as automake and autoconf. See INSTALL for more >> details. > > into: > > ++++++++++++++++++++++++++++++++++++++++++++++++++++ > Installation for *nixes (Mac OS X users please have a look at the end of the file): > ========================================================== > > Inkscape uses the standard procedure for compilation and installation: > > ./configure > make > make install > > If a "./configure" file is not present, you can create it by running > the "./autogen.sh" command, which calls in turn a number of other > programs such as automake and autoconf. See INSTALL for more > details. > ++++++++++++++++++++++++++++++++++++++++++++++++++++ > > > At end of file: > ++++++++++++++++++++++++++++++++++++++++++++++++++++ > Installation for Mac OS X users > ======================= > > We try to keep the Wiki pages on compiling inkscape up-to-date and comprehensive. It is here: > > http://wiki.inkscape.org/wiki/index.php/CompilingMacOsX > > For a brief overlook: > We suggest to use macports (http://macports.org) in order to achieve all the necessary components and libraries. Than there is a mighty tool called "osx-build.sh" in the packaging/macosx directory of the unpacked tarball. This script will do most of the work for you. > ++++++++++++++++++++++++++++++++++++++++++++++++++++ > > > In the INSTALL file change: > >> Basic Installation >> ================== >> >> If you have problems compiling Inkscape, then see >> http://wiki.inkscape.org/wiki/index.php/CompilingInkscape . >> >> The remainder of this file gives generic installation instructions. > > into > >>> Basic Installation for *nixes - Mac OS X users please have a look at the README >>> =========================================================== >>> >>> If you have problems compiling Inkscape, then see >>> http://wiki.inkscape.org/wiki/index.php/CompilingInkscape >>> >>> if you are a Mac OS X user, please dont read on, keep to the wiki pages instead: >>> http://wiki.inkscape.org/wiki/index.php/CompilingMacOsX >>> >>> The remainder of this file gives generic installation instructions. >>> … > > > >

6 7