- Inkscape Devel - Inkscape Mailman

hacking latex-pstricks.cpp to export text as text
by Richard Henwood 25 Jul '07

25 Jul '07

Hi folks, I'm would like to provide a choice for psTricks export to export text as text (not paths). My problems are that I can't get the position of the text within: PrintLatex::text(Inkscape::Extension::Print *mod, char const *text,NR::Point p, SPStyle const *const style) 'p' looks like it should contain this information (ie. p[NR::X]) but it contains the value 0. Further up, 'latex-pstricks-out.cpp' is making a call to: sp_item_invoke_print (mod->base, &context); where Inkscape::Extension::Print = *mod; mod->base = SP_ITEM (sp_document_root (doc)); ...so; any thoughts appreciated! r,

2 1

filter effects - who is working on what?
by Felipe Sanches 25 Jul '07

25 Jul '07

I have recently jumped in and I still feel a bit uncomfortable with the idea of possible redundant work. Can we start a new page at the wiki to map our current efforts on the filter effects development? It would list for each filter, who has already done what an which problems have emerged. I feel that this way we can have a better idea of which areas need more work and which filters are already fully compliant with the specs. Juca

3 3

Gtk-apps.org
by Jose Hevia 25 Jul '07

25 Jul '07

Hi, I always loved the kde-apps.org (gnome-look,kde-look...) interface and form-factor versus other approaches. Now gtk-apps.org has been created. http://www.gtk-apps.org/ Someone with good English skills could add an entry for Inscape?

1 0

Font Variants
by Gail Banaszkiewicz 24 Jul '07

24 Jul '07

Hi everyone, I just wanted to clarify what exactly the problem described in this bug is: 904962 (http://sourceforge.net/tracker/index.php?func=detail&aid=904962&group_id=93…) At first it sounds as though fonts are actually not showing up at all for some platforms, but I'm wondering if the problem now is simply that the UI doesn't separate font family and variants beyond what CSS allows (so no small caps, outline, swoosh, etc). If you can shed any light (and I bet bulia can at least), it will be much appreciated. Thanks, Gail

4 5

feImage filter
by Felipe Sanches 24 Jul '07

24 Jul '07

I have been working on feDisplacementMap but I havent figured out a way to test my first drafts of code since the displacementmap test on the SVG 1,1 full test suite also depends on feImage. That sucks! So, I stopped working on fedisplacementmap and started to implement feImage. The specs say that feImage should behave similarly to the image element. So, I imagine that it may be possible to not duplicate code. But I tryied to look at sp-image.cppand I dont know exactly how to reuse it. Could anybody help on this? Juca

2 1

Fonts
by Thomas Worthington 24 Jul '07

24 Jul '07

Hi, Is anyone actually working on fixing the font problems (ie, no styles except the very basic ones)? This is a total show-stopper for professional use. If no one is working on it, is there a guide to how to start on working with the Inkscape code, submitting patches etcetera? I'm not sure that I'll have much time to work on it but I am a programmer and I have worked with Linux fonts quite a lot over the years. I really like Inkscape and use it for design work (real, paid design work) quite a lot but it always hits a wall when a client is already using use a font which Inkscape can't handle but has to be incorporated, like Helvetica Black, which happened yesterday. There is almost nothing else which causes me to have to revert to Illustrator now other than font handling and I'm starting to really resent Illustrator because of it. Thomas Worthington

8 17

Skeletal Strokes (InkscapeLPE)
by unknown＠example.com 24 Jul '07

24 Jul '07

Hello all, Progress report of my GSoC: Skeletal strokes seems to work! (many thanks to the 2geom people!) See a screenshot here: http://wiki.inkscape.org/wiki/images/Lpe-skeletal.png and the wiki page here: http://wiki.inkscape.org/wiki/index.php/LivePathEffects I'd very much like people to test LivePathEffect things and report bugs on the wiki. Although one must know that the skeletal strokes effect is still under heavy development. Because I very much like my own branch and I'd like to keep it a little while longer, you need to checkout the live-path-effects branch to see this in action and test stuff, sorry! Cheers! Johan

3 4

feTurbulence - copyright status?
by Felipe Sanches 23 Jul '07

23 Jul '07

Reading the SVG specs, I see that there is a big chunk of C code in the feTurbulence filter effect spec. What is the copyright status of this piece of code? Is it public domain? After all, it is inside the specs, would them sue us if we copy&paste it? If we can use it let me know the conditions so that I can try to implement this filter more easily. the code is here: http://www.w3.org/TR/SVG11/filters.html#feTurbulence Juca

3 3

Re: [Inkscape-devel] Inkscape-devel Digest, Vol 14, Issue 43
by Joshua Facemyer / Impressus Art 23 Jul '07

23 Jul '07

> > > This list, like the Blur slider below it, must > > > search the selected object's filter stack for feBlend or feComposite, > > > display the current mode of that filter and let me change it (or add a > > > new filter to the top of the stack, but only if no such filter already > > > exists in the selected object's stack). > > That would interact very badly with many interesting filters, as they > > may be built out of multiple feBlend/feGaussianBlur elements; simply > > picking the first or last feBlend element (or even all of them, > > depending on how the filter is designed) won't give desirable results. > OK, that was just one of my ideas, I don't insist on making it that > way too much. It may indeed be confusing sometimes, although also > useful IMHO. What do others think? I agree that the user should be in control of exactly which instance of a filter he is editing - he might have a blurred object that is then composited which he wants to again blur after the composite. There is no way you can code the dialog to determine what instance of the filter he intends to adjust. I'm not familiar with the current implementation, so please pardon my ignorance. However, I think it is necessary to have a list of filters on a pane of the dialog (much like the layers dialog) in order of implementation for the object/group which can easily be chosen for editing. They could then be named (?) and kept track of that way if so desired. It's a familiar method already, and seems to me the most intuitive way to control the filters. Of course, then you might even have some sort of indication (maybe an icon) of what filters are affecting the object, but which are applied to a different subset of objects (group), which could then be chosen and edited. It might be fairly complex, but something like this: choose the filter, a dialog asks if you want to switch the selection to the group affected by the filter (if it's different from the current selection). Make sense? It does to me, but I'm the one thinking it...

1 0

Re: [Inkscape-devel] Inkscape-devel Digest, Vol 14, Issue 39
by Christopher Brown 21 Jul '07

21 Jul '07

> Date: Thu, 19 Jul 2007 20:58:00 +0200 > From: David Christian Berg <david@...407...> > Subject: Re: [Inkscape-devel] Changed bitmap handling > > On Thu, 2007-07-19 at 12:30 -0400, bulia byak wrote: > > On 7/19/07, David Christian Berg <david@...407...> wrote: > > > Ok, sorry to disagree, but the always embed option is only good for > > > home-use, not for professional use. > > > > Not at all. Some professionals may sometimes want their images not > > embedded, but far from always. > > Ok, maybe the "only" was exaggerated and should be a "mainly", but still > my point is valid :) > > > Even with some bitmap capabilities > > > integrated in Inkscape people will continue to want to use GIMP or > > > Photoshop to do sophisticated adjustments. Extracting and re-embedding > > > is a little cumbersome. > > > > OK, I think we can make this behavior settable in prefs, but with the > > default being to embed. > > Actually I think it should just be a checkbox "embed" in the import > dialog that is checked by default. (I'll have to figure about dragging > files into the document still) > > > > Or think of one image being used on a poster, a booklet and within some > > > entrance ticket or the such. It's great to only have to change it at one > > > place! > > > > You're comparing some inconvenience (having to extract or change > > prefs) with a nasty surprise and frustration that may be caused when > > you e.g. crop the image for the poster and then discover that it got > > cropped in the booklet as well. The latter is much worse than the > > former, and is simply unacceptable as default behavior. > > Why would you crop an image? You do that in Inkscape with the clip > option :-D > > > > I don't see a strong need for an image lying directly in an > > > automatically created folder next to the SVG... these can almost just as > > > well be embedded. However externally linked image are a must imho. > > > > Sure, we need this option, but off by default. > > Off by default, meaning, unless the user changes a setting, it will always embed images? For my purposes, i.e. permanent effects on bitmaps, I think I should keep the format that the image is already in. If the user wants to embed an image, he can do so easily with the python extension. > > > As for the editing problem: I believe that editing an image would be > > > introduced by double-clicking the image. When the linked image has no > > > write access, a message should show up: > > > Right now I'm using the Extensions menu. What is the advantage to double-clicking, and how do you picture the interface? > > > "The image cannot be edited because you do not have writing access to > > > the linked file. Would you like to embed the image in the the document > > > to continue editing?" > > > > Yes, but only if the setting is changed to not embed. By default, it > > just gets silently embedded and no warning is needed. > > I disagree! If in a document there is a non-embedded image, this warning > should always appear! By default no images will be linked so therefore > the dialogue will not appear. Acutally a similar dialogue should be > shown for _all_ embedded image, as a warning that this changes the > original image. As far as writing over the original image, I would never do that. For image.jpeg, right now I'm creating a copied image at image_orig.jpg, unless image_orig.jpg is taken, at which point I ask the user for somewhere to save the new image, unless the image_orig.jpg which already exists is equivalent to image.jpeg. Back when I used Windows, that was how Picasa handled the issue, and I thought it would work for me too. (Also, I ask the user for a new location if image_orig.jpg and/or image.jpeg are unwriteable.) > > Anyways, we basically agree on the topic. > > Cheers! > > David > These are mostly little things, but I'm curious about your idea of double-clicking of images to edit them. -Christopher

2 1