with todays build I can't open files... instead they are always linked as images in a new document. this sucks
David
I'm using a debian distribution with gnome 2.6 My brother actually made a debian package for me, because I had problems compliling since my libtool is version 1.5a but as it seems 1.4 or the such is needed. anyway: everything works fine, exept that I can't open files
David
On Fri, 2004-05-07 at 09:44, David Christian Berg wrote:
with todays build I can't open files... instead they are always linked as images in a new document. this sucks
Are you talking about bitmap images are SVG files? If they are bitmaps, yes, it is supposed to be that way. It is one way to handle bitmaps, and yes, it is not ideal. I've got it on my TODO list to actually encode them in the file - but that isn't a quick fix.
--Ted
Are you talking about bitmap images are SVG files? If they are bitmaps, yes, it is supposed to be that way. It is one way to handle bitmaps, and yes, it is not ideal. I've got it on my TODO list to actually encode them in the file - but that isn't a quick fix.
--Ted
I'm actually talking about inkscape svg files... freshly safed with todays build.
Personally I think, that bitmaps should be linked and not embedded, unless the user explicitely wants them embeded.
David
On Fri, 2004-05-07 at 11:03, David Christian Berg wrote:
I'm actually talking about inkscape svg files... freshly safed with todays build.
Okay, I just updated my CVS and built - and I have no idea of what you're talking about. Can you give me some short steps to reproduce the problem?
Personally I think, that bitmaps should be linked and not embedded, unless the user explicitely wants them embeded.
Yes, ofcourse, but I think that we should provide both options - and now users don't have the choice to have them embedded.
--Ted
On Sat, May 08, 2004 at 10:27:48AM -0700, Ted Gould wrote:
Okay, I just updated my CVS and built - and I have no idea of what you're talking about. Can you give me some short steps to reproduce the problem?
:) run inkscape. select help/tutorials/any of them. Wait 5 minutes. See imported image. ;)
In what ways can I debug the execution path?
Actually I can't, since as I said, my brother compiled it and he ain't online right now. I asked him yesterday, if he had encountered anything, that could explain the problem, but he didn't know of anything that could, or anything at all. So basically I'm stuck with two versions of inkscape that aren't working for me, right now... I just installed the latest debian-package, .38.1-something, and it crashes on me everytime, I try to open the "fill and stroke" dialog :(
Well, so for now I'm stuck with some wierd old build of sodipodi, which lacks many useful functions.
I probably need to do some cleaning up or such.
David
On Sat, May 08, 2004 at 10:27:48AM -0700, Ted Gould wrote:
Okay, I just updated my CVS and built - and I have no idea of what you're talking about. Can you give me some short steps to reproduce the problem?
I'm digging through the code, and some of the C++ "tricks" are starting to hurt my head. I put in a little debugging to see what's happening at "open" calls. Here's what I'm seeing:
Extension: svg Input->open calling Implementation... Implementation extension/internal/gdkpixbuf-input.cpp open called
so, it looks like the right extension is getting called, but the wrong implementation. Unfortunately, I don't understand how
doc = Inkscape::Extension::open (key, uri);
translates into a specific extension. Equally, I can't see how "imp" is being set inside this call to "open".
I'll keep digging...
On Sat, May 08, 2004 at 09:05:44PM -0700, Kees Cook wrote:
Extension: svg Input->open calling Implementation... Implementation extension/internal/gdkpixbuf-input.cpp open called
Ah-ha! I'm wrong... it's the wrong extension. I renamed the gdk one, and here's what I'm seeing on an open...
AI Input: .ai SVG Input: .svg matched SVGZ Input: .svgz Dia Input: .dia GDKpixbuf ani Input: .ani GDKpixbuf bmp Input: .bmp GDKpixbuf gif Input: .gif GDKpixbuf ico Input: .ico GDKpixbuf jpeg Input: .jpeg GDKpixbuf png Input: .png GDKpixbuf pnm Input: .pnm GDKpixbuf ras Input: .ras GDKpixbuf svg Input: .svg matched GDKpixbuf tga Input: .tga GDKpixbuf tiff Input: .tiff GDKpixbuf wbmp Input: .wbmp GDKpixbuf xbm Input: .xbm GDKpixbuf xpm Input: .xpm Text Input: .txt calling open: GDKpixbuf svg Input Extension: GDKpixbuf svg Input->open calling Implementation... Implementation extension/internal/gdkpixbuf-input.cpp open called
I've disabled the svg extension for the gdk thing, and added a little more to the extension name to help future debugging.
(I am using libgdk-pixbuf-dev 0.22.0-3 according to dpkg)
On Sun, 2004-05-09 at 05:07, Kees Cook wrote:
Ah-ha! I'm wrong... it's the wrong extension. I renamed the gdk one, and here's what I'm seeing on an open...
Without knowing, what you're talking about: your right! if I get rid of the extension I get a dialog "Autodetection faild, file opened as SVG" and it works just fine.
David
On Sat, 2004-05-08 at 22:07, Kees Cook wrote:
On Sat, May 08, 2004 at 09:05:44PM -0700, Kees Cook wrote:
Extension: svg Input->open calling Implementation... Implementation extension/internal/gdkpixbuf-input.cpp open called
Ah-ha! I'm wrong... it's the wrong extension. I renamed the gdk one, and here's what I'm seeing on an open...
Ah, okay. Basically what is happening is that autodetect is using the GDK SVG open instead of the internal Inkscape one. (which is a bad thing). And the reason that I can't see it on my machine is that GTK+ 2.4 with SVG is broken, so I don't have an SVG loader. Cool, nice job debugging that one! Thanks.
I think I'm going to fix it by just not using the GDK SVG loader - does anyone see a reason that they'd want an SVG rendered by rsvg as a bitmap in their graphic?
--Ted
On Sun, 2004-05-09 at 22:48, Kees Cook wrote:
On Sun, May 09, 2004 at 08:32:57PM -0700, Ted Gould wrote:
Cool! I missed this the first time - Thanks for fixing my bug too!
Sure! It forced me to get more familiar with the extension system. :)
Cool. Any comments? I went to a seminar on design patterns last week and I can now say that the extensions system follows the 'Bridge' design pattern. Yeah, I meant to do that all along... ;)
--Ted
On Mon, May 10, 2004 at 09:32:47AM -0700, Ted Gould wrote:
Cool. Any comments? I went to a seminar on design patterns last week and I can now say that the extensions system follows the 'Bridge' design pattern. Yeah, I meant to do that all along... ;)
Heheh. Mostly, it makes my head hurt. :) I think it's very cool, but a little hard to debug. ;) I might suggest adding an entire debug channel to all the actions the system is performing. ("initializing X", "found Y", "calling ABC in extension Z", etc.)
I'd also like to see some separation from GUI actions in at least the printing extension design. That way you can hook an interface to the configuration logic, and that interface can be a GUI, or just a set of XML configs, etc. From what I can tell, that's mostly done, but I don't entirely understand how it works. :)
On Fri, May 07, 2004 at 04:44:19PM +0000, David Christian Berg wrote:
with todays build I can't open files... instead they are always linked as images in a new document. this sucks
I can't open certain files... like the tutorials, and some other stuff I have. "About" works, as do simple files. Am I the only one seeing this?
well, with my inkscape, it doesn't matter, how simple the files are, after all... This is the downside of working with cvs :( but it sure is worth it.
David
participants (4)
-
Carl Hetherington -
David Christian Berg -
Kees Cook -
Ted Gould