Re: Gimp printing UI - was Re: [Gimp-developer] Update on pre-release schedule
From: Sven Neumann <[EMAIL PROTECTED]> Date: 27 Sep 2003 21:23:51 +0200 Robert L Krawitz <[EMAIL PROTECTED]> writes: >> And also, if it cannot be made possible to spread a image >> over several pages and tile the results, as that would be >> too much change, the possibility of making the printable >> image larger than the printer printable area, and trimming >> the print would be a nice thing for me at last. > >IIRC, there are enhancement requests for this in the gimp-print bug >tracker at sourceforge. > > The real problem is that we don't have a permanent maintainer for the > plugin, so there's nobody to implement RFE's against it or otherwise > improve the interface. As far as number of copies is concerned, this sounds more like a non-GUI feature. Well, of course it will need a GUI element but adding a single spinbutton shouldn't be a problem. That's basically a spooler feature that should be passed through to the GUI. BTW, if someone rewrites the print plug-in GUI, please consider not to use (lengthy) tooltips on each and every widget. This was probably done to improve useability but IMO it makes the plug-in user interface a nightmare to work with (or makes you disable tooltips). That's exactly why I did it. ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: Gimp printing UI - was Re: [Gimp-developer] Update on pre-release schedule
Hi, Robert L Krawitz <[EMAIL PROTECTED]> writes: >> And also, if it cannot be made possible to spread a image over several >> pages and tile the results, as that would be too much change, the >> possibility of making the printable image larger than the printer >> printable area, and trimming the print would be a nice thing for me >> at last. > >IIRC, there are enhancement requests for this in the gimp-print bug >tracker at sourceforge. > > The real problem is that we don't have a permanent maintainer for the > plugin, so there's nobody to implement RFE's against it or otherwise > improve the interface. As far as number of copies is concerned, this sounds more like a non-GUI feature. Well, of course it will need a GUI element but adding a single spinbutton shouldn't be a problem. BTW, if someone rewrites the print plug-in GUI, please consider not to use (lengthy) tooltips on each and every widget. This was probably done to improve useability but IMO it makes the plug-in user interface a nightmare to work with (or makes you disable tooltips). Sven ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: Gimp printing UI - was Re: [Gimp-developer] Update on pre-release schedule
From: Sven Neumann <[EMAIL PROTECTED]> Date: 27 Sep 2003 12:20:23 +0200 "Joao S. O. Bueno" <[EMAIL PROTECTED]> writes: > I don´t know who will be doing it, but it was not until this week that > I noted taht there is no way of printing more than one coppy at once > with the print GUI. Not in 1.2.5 at last (at work is what I use. At > home, I have no wrking printer at the moment) > > And also, if it cannot be made possible to spread a image over several > pages and tile the results, as that would be too much change, the > possibility of making the printable image larger than the printer > printable area, and trimming the print would be a nice thing for me > at last. IIRC, there are enhancement requests for this in the gimp-print bug tracker at sourceforge. The real problem is that we don't have a permanent maintainer for the plugin, so there's nobody to implement RFE's against it or otherwise improve the interface. -- 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 printing UI - was Re: [Gimp-developer] Update on pre-release schedule
Hi, "Joao S. O. Bueno" <[EMAIL PROTECTED]> writes: > I don´t know who will be doing it, but it was not until this week that > I noted taht there is no way of printing more than one coppy at once > with the print GUI. Not in 1.2.5 at last (at work is what I use. At > home, I have no wrking printer at the moment) > > And also, if it cannot be made possible to spread a image over several > pages and tile the results, as that would be too much change, the > possibility of making the printable image larger than the printer > printable area, and trimming the print would be a nice thing for me > at last. IIRC, there are enhancement requests for this in the gimp-print bug tracker at sourceforge. Sven ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Gimp printing UI - was Re: [Gimp-developer] Update on pre-release schedule
I don´t know who will be doing it, but it was not until this week that I noted taht there is no way of printing more than one coppy at once with the print GUI. Not in 1.2.5 at last (at work is what I use. At home, I have no wrking printer at the moment) And also, if it cannot be made possible to spread a image over several pages and tile the results, as that would be too much change, the possibility of making the printable image larger than the printer printable area, and trimming the print would be a nice thing for me at last. Regards, JS -><- On Friday 26 September 2003 5:54 pm, Robert L Krawitz wrote: >Date: Fri, 26 Sep 2003 09:17:56 +0200 >From: David Neary <[EMAIL PROTECTED]> > >As any of you who have been following CVS know, we have been >working towards a 2.0 pre1 release for the end of this month, > and there are now very few blockers to that release left. > >However, there are more blockers than are going to be done in > the next week. So we're going to have another release (1.3.21). > This should come out sometime during the next week. And the 2.0 > pre1 release will be pushed back about 2 weeks, to (give or take) > the 15th of October. > > Is anyone interested in writing a replacement Print plugin, > preferably on top of Gimp-Print 4.3, which is basically going alpha > (it's still officially development, but that's because of an OS X > stopper not related to the GIMP)? A 4.2 plugin would also be of > use, but it's getting about time to move people to 4.3. > > Currently (in the Gimp-Print source), the Print plugin is divided > into two components, libgimpprintui (which is a GTK1-based GUI > library) and the Print plugin itself (which contains all of the > GIMP interface code). It should be possible to rewrite the > libgimpprintui library by itself with minimal (hopefully no) > changes to the plugin. > > I'm not much of a UI programmer (which is why the plugin UI is such > a mess), and this is really something I'd rather farm out to > someone else. I'd like to keep ownership of libgimpprintui within > Gimp-Print at least for now, until the API is completely locked > down for the next release. I'm certainly willing to maintain the > interface into libgimpprint (the Gimp-Print core) against any > Gimp-Print API changes that may happen until 4.4 or 5.0 (whichever > we decide to name the next stable release). -- Este e-mail é, exceto pelas partes citadas de outros e-mails, copyright(c) de João Sebastião de Oliveira Bueno. Nenhuma cópia deste e-mail ou parte do mesmo pode existir nas dependências de, ou em posse de funcionários, de associações protetoras de direitos autorais Brasileiras, dos Estados Unidos da América, ou de outros países. Em particular essa exceção do direito de leitura e posse deste e-mail se extende à ABRA, ABPI, ABES, BSA, RIAA e MPAA. Violadores estão infringindo as leis internacionais de direitos autorais e sujeitos às penalidades cabíveis. Você pode re-utilizar, emendar, acrescentar suas palavras e citar e re-enviar qualquer parte do mesmo, desde que essa nota seja preservada e se não pertencer a alguma das entidades supracitadas. ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] Update on pre-release schedule
Date: Fri, 26 Sep 2003 09:17:56 +0200 From: David Neary <[EMAIL PROTECTED]> As any of you who have been following CVS know, we have been working towards a 2.0 pre1 release for the end of this month, and there are now very few blockers to that release left. However, there are more blockers than are going to be done in the next week. So we're going to have another release (1.3.21). This should come out sometime during the next week. And the 2.0 pre1 release will be pushed back about 2 weeks, to (give or take) the 15th of October. Is anyone interested in writing a replacement Print plugin, preferably on top of Gimp-Print 4.3, which is basically going alpha (it's still officially development, but that's because of an OS X stopper not related to the GIMP)? A 4.2 plugin would also be of use, but it's getting about time to move people to 4.3. Currently (in the Gimp-Print source), the Print plugin is divided into two components, libgimpprintui (which is a GTK1-based GUI library) and the Print plugin itself (which contains all of the GIMP interface code). It should be possible to rewrite the libgimpprintui library by itself with minimal (hopefully no) changes to the plugin. I'm not much of a UI programmer (which is why the plugin UI is such a mess), and this is really something I'd rather farm out to someone else. I'd like to keep ownership of libgimpprintui within Gimp-Print at least for now, until the API is completely locked down for the next release. I'm certainly willing to maintain the interface into libgimpprint (the Gimp-Print core) against any Gimp-Print API changes that may happen until 4.4 or 5.0 (whichever we decide to name the next stable release). -- 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] Update on pre-release schedule
Hi all, As any of you who have been following CVS know, we have been working towards a 2.0 pre1 release for the end of this month, and there are now very few blockers to that release left. However, there are more blockers than are going to be done in the next week. So we're going to have another release (1.3.21). This should come out sometime during the next week. And the 2.0 pre1 release will be pushed back about 2 weeks, to (give or take) the 15th of October. Just to keep ye up to date, the list of blockers for the 2.0 release (which is mostly a filled out list of the things mentioned at camp), and their current status, is below. Blockers for 2.0 prereleases: - Path tool: 1) moving of strokes/paths,*DONE* 2) being able to connect two strokes, *DONE* 3) dragging on curve segments, *DONE* 4) libart stroking,Mostly done 5) im/export into files. *DONE* Text tool features missing: 1) GUI for text boxes Back-end done 2) Implementation of text transforms 3) Font list/selector improvements 4) Text outlineNot a blocker Help browser features missing: 1) Symbolic references for every core function *DONE* 2) Mechanism for cross-referencing with 3rd party *DONE* documentation 3) Registering of documentation files with the core *DONE* at startup, with references. libgimp API changes missing: 1) libgck must die *RESOLVED* 2) Thumbnail API exposedNeary done 3) libgimpmisc API changes 4) gimp_dialog_new () 5) 64 bit clean libgimp All in all, on that list there are 2 or 3 worrying things that might not be done in 2 weeks time, but most of them look like they will be done by then. We do need to clean up Bugzilla a little again. There are now 75 bugs with milestone --, it would be nice to get these sorted to the right place before we hit pre-releases. http://bugzilla.gnome.org/buglist.cgi?product=GIMP&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=NEEDINFO&bug_status=REOPENED&target_milestone=---&cmdtype=doit&order=%27Importance%27&form_name=query There are also 159 bugs open against the 2.0 release (milestone 1.3.x or 2.0). We need to start reducing this number now. So if you have a little spare time, please have a look at these bug reports, either to help close them or to reduce the amount of time needed to fix them. http://bugzilla.gnome.org/buglist.cgi?product=GIMP&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=NEEDINFO&bug_status=REOPENED&target_milestone=1.3.x&target_milestone=2.0&cmdtype=doit&order=%27Importance%27&form_name=query Thanks for your time, Dave. -- David Neary, Lyon, France E-Mail: [EMAIL PROTECTED] ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer