[Gimp-developer] Print plugin for 2.0
Does 2.0 have any functioning print plugin? If not, what changes need to be made to the current 4.2-based plugin? -- Robert Krawitz [EMAIL PROTECTED] Tall Clubs International -- http://www.tall.org/ or 1-888-IM-TALL-2 Member of the League for Programming Freedom -- mail [EMAIL PROTECTED] Project lead for Gimp Print --http://gimp-print.sourceforge.net Linux doesn't dictate how I work, I dictate how Linux works. --Eric Crampton ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] Print plugin for 2.0
Hi, Robert L Krawitz [EMAIL PROTECTED] writes: Does 2.0 have any functioning print plugin? If not, what changes need to be made to the current 4.2-based plugin? It has a functional print plug-in based on gimp-print 4.2. For GIMP-2.2, we'd like to provide a print plug-in based on a newer gimp-print release (that would be 5.0 then?). Perhaps we would even do that change in some 2.0.x release. It depends on the timing of your releases and whether someone does the necessary hacking. Sven ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] Print plugin for 2.0
Hi, Robert L Krawitz wrote: I'm the Gimp-Print project lead, that's why I asked the question :-) I know :) Sorry to hear the 5.0 release is still a bit away. In the 5.0 tree, the plugin has been split into two pieces, a UI library (libgimpprintui) and the GIMP plugin proper (which is tiny, and contains all of the GIMP-specific code). We should work out the appropriate ownership of of these two components, and the correct dividing line. It would be really great if you would continue to maintain the gimp-print plug-in that's in GIMP CVS. Understandably, since gimp-print is now very much its own project, our release schedules aren't going to match up for the most part, but currently the goal would be to support the latest stable release of gimp-print in the GIMP. Having 2 GIMP plug-ins (1 in gimp-print that's based on the last stable GIMP and another in the GIMP that's based on the last stable gimp-print) doesn't really make sense. I would propose that the gimp-print plug-in gets updated in the GIMP tree when the libgimp API changes, and then gets updated to use the new gimpprint when a stable release comes out. What do you think? Cheers, Dave. -- Dave Neary [EMAIL PROTECTED] ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] Print plugin for 2.0
Hi, Robert L Krawitz [EMAIL PROTECTED] writes: In the 5.0 tree, the plugin has been split into two pieces, a UI library (libgimpprintui) and the GIMP plugin proper (which is tiny, and contains all of the GIMP-specific code). We should work out the appropriate ownership of of these two components, and the correct dividing line. There's still a GIMP plug-in in the 5.0 tree? Now I am confused. I thought our plan to get rid of that circularity was that you drop the GIMP plug-in entirely and leave it up to the GIMP team to provide a plug-in that builds on the gimp-print library. Is that not the plan? Sven ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] Some more open issues for 2.0
Hi, I'd like to give an update on the list of open issues that I posted two days ago... - gimp.spec should not be in the tarball Done. - need a final splash image I've opened a bug report for this (http://bugzilla.gnome.org/show_bug.cgi?id=136993). Got no feedback yet but I am not (yet) worried... - review debug output Has been addressed and seems completed. - test help and if it works, remove or #ifdef debug output The new help plug-in has code that used to live in the helpbrowser plug-in. Brix moved it into a plug-in of its own so that the webbrowser can be used to access the help pages. This has been done after pre4. Seems to work fine, but should see some more testing especially on windows. There's massive debug output in there that shouldn't end up in the final version. I haven't received any feedback yet, so I assume that it is working for everyone? The debug output should probably stay for now. It might be useful in case that we address the i18n issues with the help system. - consider to add localization support to the help system The API is in-place, so we can easily do this for 2.0.1 but it would of course be nice to get this into 2.0. Simply because there is translated help available already but at the moment it cannot be used from The GIMP. Mitch wanted to look at this. I've explained this in more detail in other mails and it seems that we probably want to change the install location of the gimp-help.xml files. This should happen before 2.0 gets out. So I'd like to treat this a bug that should be fixed before 2.0 but it should not be considered a blocker. If we don't get around to it, we will have to live with the way it's done right now. This is being tracked in http://bugzilla.gnome.org/show_bug.cgi?id=136996 Sven ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] the GIMP help system, i18n and other problems
Sorry, my mta was a bit messed up lately, so the most of this was discussed before i got it. On Fri, Mar 12, 2004 at 01:59:16PM +0100, Sven Neumann wrote: Hi, (b) Extend the gimp-help.xml format to allow to specify a fallback URL that should be used when no other mapping is given. We will go for the (b) here. I'm fine with that. Adding an url for every id looks for me to much work. (2) How do we handle internationalisation? This isn't completely clear yet. I'll list the open issues: [... details] These are all rather small changes that are easy to implement but we should better do them now. So if there's consensus on this, I would like to see this being implemented over the weekend. Well, only i can do is agree with the proposals and discussions. There is nothing what i can add here. Thanks for implementing this for 2.0 release! Greetings, -- Roman Joost www: http://www.romanofski.de email: [EMAIL PROTECTED] signature.asc Description: Digital signature
Re: [Gimp-developer] Print plugin for 2.0
Date: Fri, 12 Mar 2004 14:25:23 +0100 From: Dave Neary [EMAIL PROTECTED] Hi, Robert L Krawitz wrote: I'm the Gimp-Print project lead, that's why I asked the question :-) I know :) Sorry to hear the 5.0 release is still a bit away. In the 5.0 tree, the plugin has been split into two pieces, a UI library (libgimpprintui) and the GIMP plugin proper (which is tiny, and contains all of the GIMP-specific code). We should work out the appropriate ownership of of these two components, and the correct dividing line. It would be really great if you would continue to maintain the gimp-print plug-in that's in GIMP CVS. Understandably, since gimp-print is now very much its own project, our release schedules aren't going to match up for the most part, but currently the goal would be to support the latest stable release of gimp-print in the GIMP. Having 2 GIMP plug-ins (1 in gimp-print that's based on the last stable GIMP and another in the GIMP that's based on the last stable gimp-print) doesn't really make sense. I would propose that the gimp-print plug-in gets updated in the GIMP tree when the libgimp API changes, and then gets updated to use the new gimpprint when a stable release comes out. The current plugin (based on 4.2) is basically in sustaining at this point, and really approaching EOL. We're hardly even fixing bugs in 4.2 any more. We're probably going to do one more 4.2 release for a few bugs, an OS X problem that isn't a Gimp-Print problem but which gets blamed on it, and a couple of new Epson printers. But that won't cause you any problems. I'm not going to remove it from our source base, since there will be very few 4.2 releases left. The plugin in our 5.0 tree is another matter. Since the 5.0 API isn't locked down, it's premature (IMHO) to transfer it to the GIMP. There are major structural changes from the 4.2 plugin; in particular, it has been split into two pieces, libgimpprint and the Print plugin proper. libgimpprint is a GTK+ (1.2 right now) UI, without any linkage to libgimp. The GIMP-specific code is in the plugin, consisting of 4 files of less than 1000 lines of code: 4571492 11003 print-image-gimp.c 4251418 13702 print.c 55 2221590 print_gimp.h 38 1991372 print-intl.h 9753331 27667 total The question is what should be transferred to the GIMP when our API stabilizes. Certainly the core GIMP plugin is a good candidate, but libgimpprintui is less clear. It's actually much larger than the plugin proper (and badly in need of cleanup). It could at least in principle be used as a print facility by other GTK-based applications, although it's not completely general (it only handles single pages). 4438 12230 136157 panel.c 13713945 36094 plist.c 155 4653964 print-image-thumbnail.c 44 2151385 printrc.h 105 3823287 printrcl.l 285 6546321 printrcy.y 8692482 25134 ui-utils.c 7267 20373 212342 total (I'd ideally like to support both a 4.2 and a 5.0 plugin concurrently, because people who have built workflows around 4.2 may not want to switch in one shot.) -- Robert Krawitz [EMAIL PROTECTED] Tall Clubs International -- http://www.tall.org/ or 1-888-IM-TALL-2 Member of the League for Programming Freedom -- mail [EMAIL PROTECTED] Project lead for Gimp Print --http://gimp-print.sourceforge.net Linux doesn't dictate how I work, I dictate how Linux works. --Eric Crampton ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] Print plugin for 2.0
From: Sven Neumann [EMAIL PROTECTED] Date: 12 Mar 2004 14:19:13 +0100 Robert L Krawitz [EMAIL PROTECTED] writes: In the 5.0 tree, the plugin has been split into two pieces, a UI library (libgimpprintui) and the GIMP plugin proper (which is tiny, and contains all of the GIMP-specific code). We should work out the appropriate ownership of of these two components, and the correct dividing line. There's still a GIMP plug-in in the 5.0 tree? Now I am confused. I thought our plan to get rid of that circularity was that you drop the GIMP plug-in entirely and leave it up to the GIMP team to provide a plug-in that builds on the gimp-print library. Is that not the plan? See my previous reply to Dave Nearly on this. That's the plan, but there are architectural and execution issues to be worked. I'm hoping to do a lot of work and get close to locking down the 5.0 API this weekend, although I don't know whether I'll manage to complete everything. The changes I want to do will generalize the input mode support, so you really want them in place before GEGL (and for that matter the Cinepaint folks really need these changes too). I want to stabilize the 5.0 API, and hopefully have something that will be backward compatible at 5.2, so it's premature to transfer ownership yet. -- Robert Krawitz [EMAIL PROTECTED] Tall Clubs International -- http://www.tall.org/ or 1-888-IM-TALL-2 Member of the League for Programming Freedom -- mail [EMAIL PROTECTED] Project lead for Gimp Print --http://gimp-print.sourceforge.net Linux doesn't dictate how I work, I dictate how Linux works. --Eric Crampton ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-print-devel] Re: [Gimp-developer] Print plugin for 2.0
Hi, Robert L Krawitz [EMAIL PROTECTED] writes: libgimpprint is a GTK+ (1.2 right now) UI, without any linkage to libgimp. It will have to be ported to the GTK+-2.x API if you want it to be useful. Are there any plans to do that? Sven ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-print-devel] Re: [Gimp-developer] Print plugin for 2.0
From: Sven Neumann [EMAIL PROTECTED] Date: 13 Mar 2004 03:45:21 +0100 Robert L Krawitz [EMAIL PROTECTED] writes: libgimpprint is a GTK+ (1.2 right now) UI, without any linkage to libgimp. It will have to be ported to the GTK+-2.x API if you want it to be useful. Are there any plans to do that? No, but we could use a volunteer. -- Robert Krawitz [EMAIL PROTECTED] Tall Clubs International -- http://www.tall.org/ or 1-888-IM-TALL-2 Member of the League for Programming Freedom -- mail [EMAIL PROTECTED] Project lead for Gimp Print --http://gimp-print.sourceforge.net Linux doesn't dictate how I work, I dictate how Linux works. --Eric Crampton ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
[Gimp-developer] no ppd file usable with gimp2.0pre4?
Hi As first the good, i can print now with gimp2.0pre4. And now the bad. If i use a ppd file in the preferences from postscript level2 in gimp i lost the preview and i get no printer output. Only if i dont use a ppd file for my Stylus 670 with turboprint driver i get a preview and a good print. I use Suse 8.2 with updatet ghostscript7.07.1rc1 (gimp-print 4.2.6), turboprint1.86, cups1.1.18. Any hints for me? Thanks frank ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
