Hi, Hans Breuer <Hans@xxxxxxxxxx> writes: > Exactly. And by the way: instead of checking if something on win32 > exist, why not simply ask ? Sure, we should have probably done that but I felt the there was no problem when I saw that Tor already ships prebuilt packages for it. > Oh, there is a text tool design ? References ? The basic text tool design is in CVS since summer 2001. I didn't expect it to take so long to get it finished and we are not there yet. The plan is to get the following features in before the upcoming release: - add gui for text boxes: positioning, resizing - store text layers in XCF; mostly there since GimpText implements the GimpConfig interface - convert text to vectors I'd like to address transformations (flip, rotate, affine) as well but we might have to postpone this. However I definitely want to have some migration path to this feature. At the moment only PangoFT2 seems to allow these kind of things. Actually, it doesn't, but it can be done using the FreeType API. If we accepted your patch, I would have to workaround its #ifdefs and could only hope that there is a chance to implement the same functionality in the win32 part of the code. We have eliminated most of the special-casing in the current code base. I really don't want to introduce new ones. > Did you follow _one_ of the links provided in my previous mails ? > Did you notice dates in them ?? Yes, of course I did. > I've brought up the issue of 'Pango Backend Abstraction' almost > two years ago. There were some response from you a long the > line of : > > "the current state of the Gimp Text Tool in Gimp is in no > way final nor has it been designed with care. I haven't > yet found the time to think about this much, but I was > under the impression we could use the FT2 backend on all > supported platforms." > > And with Heads up on Pango HEAD PangoFT2 broke. There still was > a working version 1.0 but nowadays The GIMP relies on Pango 1.2. There is no point in discussing 1.0 versus 1.2. We can't depend on an unmaintained version of Pango. If we go for PangoFT2 as our text rendering engine then it has to be the latest version. Otherwise we have no chance to get any fixes into it. And we had to fix quite a few bits of PangoFT2 to get the text tool to the point it is today. > >We have to guess what your prolems are. You didn't even tell us if the > >latest changes worked. > I think my response time was rather good: > - Your mail 23 May 2003 20:31:35 +0200 > - My ChangeLog entry 2003-05-24 > - The bug report from 2003-05-25 04:56 -??? Yes, and I must admit that I was impressed. Your text tool patch shocked me quite a bit but I was happy to see the makefile changes coming in that fast. However what I was really waiting for during the last months was some feedback about the state of GIMP on windoze. It felt depressing that obviously noone could compile this beast on windoze, let along run it. The latest changes to libgimp were an attempt to make it easier to get gimp compiled on windoze. > And for the record: beside the issue with pangoft2 The GIMP cvs > appears to work as expected (a little unstable though). That is the very first time I ever hear that a GIMP-1.3 was run on windoze. I assume it was the first time, you surely would have told us if it happened before. That is great news. Do you think it would make sense to think about providing packages so more people can test it. Or do believe it's too early for that? > >There is almost no communication between the > >main GIMP developers and the people working with GIMP on Win32. > > I always thought I was working on GIMP on windoze instead of > with. And communictaion should be bidirectional. > Can't talk about people working _with_ Gimp on windoze. You are nitpicky, I meant to say working on GIMP of course. Although it would of course be important to get some feedback from people working with GIMP on windoze as well. > That's fine with me but _please_ don't complain about > lack in communication skills. Sorry, but I do. The good thing about these little flames is that things get said. Perhaps that is needed from time to time. I tried to bring up the issue about lack of feedback before when I suggested we merge the win32 mailing list into gimp-developer. Perhaps that would have avoided a dispute like this one. Sven
