difficulty to reach particular layers(paths)
by Hago Ziegler
Hi,
I tried Inkscape.
It's a beautiful program and even very simple to handle.
Well, for trial I made an apple
( http://www.hagoschaos.de/h/freunde/apfel.html ).
At the end I had about 30 objects(paths), but only one layer.
So it became extremely difficult, to change something on any layer down
below.
It became sort of a lucky chance, when I found a path which I was looking
for.
So I would like to know, if there is a more professional way to deal with
the paths and layers.
Regards, Hago
18 years, 1 month
Exporting as PS
by Alberto Simões
Hi
I am having trouble exporting my SVG as a PostScript file. Basically,
it changes some parts of the image and fills them with black.
I am sending the SVG file as attach so you can try to help me.
Thanks
Alberto
--
Alberto Simões
18 years, 1 month
Re: [Inkscape-user] Vector imports
by Beton, Richard
Adam Smith wrote:
> I did some more searching and found this: http://dxf2svg.sourceforge.net/
> It's on sourceforge so you or somebody on the list is probably aware
> of it. Is this a decent start?
Looks like dxf2svg isn't ready for widespread use. Bit of a shame, but
there we are.
We had a discussion on DXF import in late March. There exists dxflib
for reading DXF as an open-source project
(http://dxflib.sourceforge.net/). However, no-one has written an SVG
outputter based on this, which seems a shame. All the other converters
I could find are commercial paid-for software. If I had more spare
time, I'd write a DXF-to-SVG converter app. based on dxflib...
There's an RFE for DXF import
(http://sourceforge.net/tracker/index.php?func=detail&aid=1062140&group_id...)
Rick
--
Visit our website at www.roke.co.uk
Roke Manor Research Ltd, Roke Manor, Romsey, Hampshire SO51 0ZN, UK.
The information contained in this e-mail and any attachments is proprietary to
Roke Manor Research Ltd and must not be passed to any third party without
permission. This communication is for information only and shall not create or
change any contractual relationship.
18 years, 1 month
Donation System Proposal
by Bryce Harrington
Hi all,
The other day we received another donation to Inkscape ($10, less
SourceForge and PayPal fees). :-)
For about a year we've talked on and off about donations for Inkscape.
The major question is not getting the money, but deciding how to apply
the money appropriately.
Of course, we've had no shortage of ideas... From bug
bounties/contracts, to hardware, to developer support, to sponsoring
attendance at conferences. I like all the ideas, although some would be
more feasible than others.
However, the one idea I think I like the best, to start with, is to fund
contract work to enhance file import/export converters. I.e.,
accumulate enough funding to pay a developer to augment an existing
xyz2svg tool for use with Inkscape.
Here is my reasoning for this proposal:
1. These extensions are distinct from the main Inkscape codebase, thus
eliminating a range of potential conflicts of interests, learning
curve issues, and so forth.
2. Users *definitely* want to see the file converters improved. This
is often a crucially important need for them, and they will see the
benefits of the improvements immediately.
3. File converters haven't tended to attract attention from many
developers. Maybe they're not considered 'sexy' enough? Using
money as a motivator is worth a shot.
4. These converters will have definite value beyond Inkscape. A lot of
programs out there are starting to gain SVG support. If we are able
to gain good xyz2svg converters, this could benefit them as well,
plus would help build the reputation of SVG as a good format for
interoperability, which helps all of us out a lot.
5. I emphasize focus on enhancing _existing_ tools over creating new
ones for several reasons. First, the work of creating a basic tool
that does the first 80% of the conversion is usually not too hard
and actually kind of fun; the hard part is getting that last 20%,
and that's where I think funding development will be most
effective. Also, it can be harder to track progress for development
of a tool being written from scratch.
6. We can allow users to contribute to the specific converter they wish
to support; i.e., we establish one pool for the AI extension,
another for DXF, another for VSD, etc. and allow people to choose
which one their donations will go to.
Here are the challenges I see for this proposal, and how we'd be able to
deal with them:
a. Funds collection/distribution: If we get a large number of
donations, there may be an administrative overhead to keep track of
them. I'll set up an account that allows us to accumulate the funds
via SourceForge, and for now I'll just handle the accounting
manually. If it becomes burdensome, myself or someone can script it
up better.
b. Donation fees: Currently, SF and Paypal impose fees for donations.
A $10 donation works out to be $8.48. It'd be nice to preserve a
larger proportion, but beggers can't be choosers. If someone less
lazy than me wants to set up something better, let me know.
c. Deciding the contract terms. This is the point I'm not sure about,
but clearly we need to have some way of establishing the minimum
goals for the funding. I'm open to suggestions, but sure we can
figure something out; contracting developers is nothing particularly
new.
d. Deciding who is allowed to bid on the work. I'm concerned about
random people bidding on the work, and also think that the spirit of
the donations is to also help further Inkscape development in
general. Thus I would be tempted to limit participation to people
who have a track record of doing development work for Inkscape.
These people will be "known quantities", and will have a stake in
doing a good job.
e. Deciding when to close donations and open bidding. In other words,
how do we decide how much money to raise? It's often difficult to
determine how much time it'd take to implement a feature. My
thought is to leave this open ended - we simply post what the
expectations are and how much $$ has been collected, and when a
developer feels enough has been raised, he submits a bid to do the
work. This way, "the market" is left to decide what the rate should
be.
f. Deciding what file converter features to allow donating to. My
feeling is that we should just leave this open to the donors. Any
donation target that someone puts money against is worth adding to
the list.
g. Legal/contractual paperwork and such. I'm blissfully clueless
here. Maybe this part is the achilles heel of the whole idea, or
maybe it's no big deal, I have no idea. But people have paid other
people to do work before, and I'm sure it can be sorted out
somehow.
Anyway, let me know what y'all think of this proposal. Worth doing?
Bryce
>From MAILER-DAEMON Sat Apr 09 15:05:50 2005
From: Service de distribution du courrier <postmaster@...240...>
To: inkscape-user(a)lists.sourceforge.net
Date: Sun, 10 Apr 2005 00:05:41 +0200
Message-ID: <425309CA00284210@...620...>
MIME-Version: 1.0
Content-Type: Multipart/Report; report-type=delivery-status; boundary="========/425309CA0028420F/mx.laposte.net"
X-Spam-Score: -0.1 (/)
X-Spam-Report: Spam Filtering performed by sourceforge.net.
See http://spamassassin.org/tag/ for more details.
Report problems to http://sf.net/tracker/?func=add&group_id=1&atid=200001
-0.1 AWL AWL: From: address is in the auto white-list
Subject: [Inkscape-user] =?ISO-8859-15?Q?Notification_d'=E9tat_de_la_distribution?=
Sender: inkscape-user-admin(a)lists.sourceforge.net
Errors-To: inkscape-user-admin(a)lists.sourceforge.net
X-BeenThere: inkscape-user(a)lists.sourceforge.net
X-Mailman-Version: 2.0.9-sf.net
Precedence: bulk
Reply-To: inkscape-user(a)lists.sourceforge.net
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/inkscape-user>,
<mailto:inkscape-user-request@lists.sourceforge.net?subject=unsubscribe>
List-Id: Inkscape User Community <inkscape-user.lists.sourceforge.net>
List-Post: <mailto:inkscape-user@lists.sourceforge.net>
List-Help: <mailto:inkscape-user-request@lists.sourceforge.net?subject=help>
List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/inkscape-user>,
<mailto:inkscape-user-request@lists.sourceforge.net?subject=subscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum=inkscape-user>
Ce message MIME en plusieurs parties contient une notification d'état de distribution.
Si vous voyez ce texte, il est possible que votre client de courrier ne puisse pas
lire les messages MIME formatés ou les DSN (voir RFC 2045 à 2049 pour des informations générales
sur le protocole MIME et RFC 1891 à 1894 pour des informations spécifiques aux DSN).
--========/425309CA0028420F/mx.laposte.net
Content-Type: text/plain; charset="ISO-8859-15"
Content-Transfer-Encoding: quoted-printable
- Ces destinataires ont =E9t=E9 trait=E9s par le serveur de messagerie :
boite.archivee@...240...; =C9chec; 5.7.0 (=E9tat de s=E9curit=E9 diff=E9ren=
t ou non d=E9fini)
--========/425309CA0028420F/mx.laposte.net
Content-Type: Message/Delivery-Status
Content-Transfer-Encoding: 7Bit
Reporting-MTA: dns; mx.laposte.net
Received-from-MTA: dns; mx.laposte.net (10.150.9.58)
Arrival-Date: Sun, 10 Apr 2005 00:05:41 +0200
Original-Recipient: rfc822;tom@...240...
Final-Recipient: rfc822; boite.archivee@...240...
Action: Failed
Status: 5.7.0 (other or undefined security status)
--========/425309CA0028420F/mx.laposte.net
Content-Type: Text/RFC822-headers; charset="utf-8"
Content-Transfer-Encoding: 7bit
Return-Path: <inkscape-user(a)lists.sourceforge.net>
Received: from mx.laposte.net (10.150.9.58) by mx.laposte.net (7.0.028)
id 425309CA0028420F for boite.archivee@...240...; Sun, 10 Apr 2005 00:05:41 +0200
Received: from lists.sourceforge.net (84.101.175.2) by mx.laposte.net (7.0.028)
id 42530AAA003ED43F for tom@...240...; Sun, 10 Apr 2005 00:05:41 +0200
Message-ID: <42530AAA003ED43F@...619...> (added by postmaster@...240...)
From: inkscape-user(a)lists.sourceforge.net
To: tom@...240...
Subject: hello
Date: Sun, 10 Apr 2005 00:05:23 +0200
MIME-Version: 1.0
Content-Type: multipart/mixed;
boundary="----=_NextPart_000_0013_621514B5.8BB320C5"
X-Priority: 3
X-MSMail-Priority: Normal
--========/425309CA0028420F/mx.laposte.net--
18 years, 1 month
export - image slicing
by Michal Žeravík
dear developers,
latest cvs looks very very good.
I'm missing only a few features:
1. Edit with Gimp ... (for images)
2. export in slices (special layer to define slices ? ..)
3. HSL filter to change colour in objects/groups.
4. some nice plugins from skencil, as blend and so on...
Michal
18 years, 1 month
clipart files ???
by Gracia M. Littauer
Dumb question 101...where are all the clip art files & how do i use
them??? Linux SuSE 9.2; inkscape .40
I DLed what I thought was it, but that turned out to be a php file of a
few Ks; then i found THE file, (all 44 megs?). But I haven't a clue
where it went & how I access it.
I hate it when DLs put stuff where they want, rather than where I
want!!! & then don't give me a clue how to use them.
Yes, the Linux file system is still a bit of a mystery to me.
--
Gracia...Cooleemee, NC Registered Linux user #263390 - SuSE 9.2 Pro
Choices, life is about choices -- well, part of it is. Shit happens is
the other part. Mickey Mouse aka Jari Lynn
18 years, 1 month
Re: [Inkscape-user] 0.41 autopackage - missing dependencies
by Christopher B. Wright
Just wanted to add that I get the same error messages.
Running Mepis Linux (also Debian based). It doesn't
affect anything I actually do in Inkscape... not so
far, anyway.
Christopher B. Wright (wrightc@...537...)
--- Claus Cyrny <claus.cyrny@...22...> wrote:
> Hi,
>
> after installing the 0.41 autopackage, I got the
> following
> error messages in the log:
>
> --- begin ---
>
> description: In order to import Dia files, Dia
> itself must be installed.
> You can get Dia at http://somesite.com
>
> Extension "Grid" failed to load because a dependency
> was not met.
> Dependency::
> type: plugin
> location: path
> string: grid
>
> Extension "Postscript Input" failed to load because
> a dependency was not
> met.
> Dependency::
> type: executable
> location: path
> string: pstoedit
>
> Extension "AI Output" failed to load because a
> dependency was not met.
> Dependency::
> type: executable
> location: path
> string: pstoedit
>
> Extension "EPS Input" failed to load because a
> dependency was not met.
> Dependency::
> type: extension
> location: path
> string: org.inkscape.input.ps
>
> Extension "Sketch Input" failed to load because a
> dependency was not met.
> Dependency::
> type: executable
> location: path
> string: skconvert
>
> Extension "Windows Metafile Input" failed to load
> because a dependency
> was not met.
> Dependency::
> type: executable
> location: path
> string: wmf2svg
>
> Extension "GIMP Gradients" failed to load because a
> dependency was not met.
> Dependency::
> type: plugin
> location: path
> string: gimpgrad
>
> --- end ---
>
> The first one ("Dia") is clear because I haven't
> installed Dia, but what
> about the other ones? I'm particularly concerned
> about the option to
> save as Adobe .AI. What do I need to do? I am
> working under the
> Debian-based Ubuntu Linux.
>
> But besides: There are visible improvements from
> 0.39, which I was using
> until now!
>
> TIA,
>
> Claus
> --
> Profile: http://home.arcor.de/ccyrny/profil/en/ (in
> English)
> Djangology: http://home.arcor.de/ccyrny/djangology/
> (deutsch)
> Glossar "Computergrafik":
> http://home.arcor.de/ccyrny/glossar/ (deutsch)
>
>
>
-------------------------------------------------------
> SF email is sponsored by - The IT Product Guide
> Read honest & candid reviews on hundreds of IT
> Products from real users.
> Discover which products truly live up to the hype.
> Start reading now.
>
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
> _______________________________________________
> Inkscape-user mailing list
> Inkscape-user(a)lists.sourceforge.net
>
https://lists.sourceforge.net/lists/listinfo/inkscape-user
>
>
>
18 years, 1 month
icon theming
by Jakub Steiner
Hi folks,
I tried to start tweaking inkscape icons so it's less of a blur but
stumbled on some obstacles.
As per some discussion on the #inkscape channel I was convinced I could
use ~/.inkscape/icons/ to store PNG icons with filenames corresponding
to the icons.svg object ids or the old XPM icon set. However this
doesn't appear to have any effect.
Failing that, I tried doing them in vector. While
~/.inkscape/icons/icons.svg does seem to override the global icons, I'm
puzzled about the size. The icons in the toolbar, nor the icons in the
menus seem to match the 1:1 zoom of icons.svg thus any effort trying to
position elements to the raster grid are useless. My 16x16px icon got
scaled down to about 10px in the toolbar. What's the magic here?
I'm still convinced that for small resolutions such as the toolbar and
definitely menu icons, bitmap icons will take less effort to draw. Even
if you do them in vector, you still need to make sure the objects align
well to the grid to render sharp. That means either having menu and
toolbar render at the same size or doing every icon twice anyway. [1]
I see the usefulness of SVG icons, phasing them in gnome icon theme, but
for tiny resolutions they don't work without pixel-perfect positioning.
[1] - More on this here:
http://primates.ximian.com/~jimmac/blog/Artwork/SVG-NG/
cheers
--
Jakub Steiner <jimmac@...446...>
Novell, Inc.
18 years, 1 month
0.41 autopackage - missing dependencies
by Brandon Blackmoor
> From: Bryce Harrington <bryce@...69...>
> Subject: Re: [Inkscape-user] 0.41 autopackage - missing dependencies
>
> I think it would be invaluable for 0.42 that this
> whole approach should be rethought and reimplemented
> in a clearer way.
All that's really needed, I think, is to have some instructions on how to
correct the errors.
--
Brandon Blackmoor
bblackmoor@...477...
2005-04-06
18 years, 1 month
