Hi,

On Thu, 2007-09-27 at 21:57 +0200, firepol wrote:

I open an image stored
in /media/usb-external/graphics/work/animals/cat/mycat/christmas/cat.jpg

Now, if I cut a part of the image and I paste it into a new image, then I click "save as" I get as default my home directory (in my case /home/paul/) which is very annoying since I'd like to save the modified image in the same folder (last location) I've just opened a few seconds before. I need to re-navigate the whole tree to select the directory, loosing a bunch of time.

Sometimes you want to save the image there, and sometimes you don't. Since there's no relation between the image you opened and the one you are saving, it would be somewhat odd to open the save file-chooser in the loaction where you last opened a different image.

It's not easy to find a good solution that fits for all cases. For GIMP 2.4 we have changed the behavior of the Open and Save dialogs so that they open in the last used directory if you are using them from the same image. For all other needs, I suggest that you use the Bookmarks feature of the file-chooser dialog to avoid having to renavigate the filesystem.

Sven

El dv 28 de 09 del 2007 a les 19:34 +0200, en/na Sven Neumann va escriure:

It's not easy to find a good solution that fits for all cases. For GIMP 2.4 we have changed the behavior of the Open and Save dialogs so that they open in the last used directory if you are using them from the same image. For all other needs, I suggest that you use the Bookmarks feature of the file-chooser dialog to avoid having to renavigate the filesystem.

Just a couple of ideas.

May be Gimp can auto add/remove Bookmarks? I guess this can give more problems than adressed.

Or may be after modifying file-chooser, there will be a place for app-bookmarks in plus of user-bookmarks?

Yours Pere

Hi,

On Fri, 2007-09-28 at 22:40 +0200, Pere Pujal i Carabantes wrote:

May be Gimp can auto add/remove Bookmarks? I guess this can give more problems than adressed.

Or may be after modifying file-chooser, there will be a place for app-bookmarks in plus of user-bookmarks?

The application can already add bookmarks and GIMP 2.4 already makes use of this feature in some places. I am not convinced though that this would be a good way to solve the problems brought up the user who started the thread.

Perhaps we need to collect the typical usage scenarios that involve use of the file-chooser and evaluate how the current solution deals with them and if there are ways to improve it.

Sven

On Sunday 30 September 2007 20:10:46 Sven Neumann wrote:

The application can already add bookmarks and GIMP 2.4 already makes use of this feature in some places. I am not convinced though that this would be a good way to solve the problems brought up the user who started the thread.

I am imagining a short drop-down history of places one last saved things, preferably with a shortcut key (Ins? Who knows?) which will instantly recall the most recent one.

Cheers; Leon

Leon Brooks GIMP said on Sep 30, 2007 16:51 -0400 (in part):

On Sunday 30 September 2007 20:10:46 Sven Neumann wrote:

The application can already add bookmarks and GIMP 2.4 already makes use of this feature in some places. I am not convinced though that this would be a good way to solve the problems brought up the user who started the thread.

I am imagining a short drop-down history of places one last saved things, preferably with a shortcut key (Ins? Who knows?) which will instantly recall the most recent one.

Is any one familiar with Windows-only File-Ex http://www.cottonwoodsw.com ? (It has a 30-day trial period)

IMO it turns the standard windows File-Open File-Save dialogs into things of beauty.
If Gimp's (aka GTK+ do I have the relationship correct?) Open-Save dialogs could emulate that cross-platform I think it would be ideal! (And satisfy everything Leon has asked for.)

Full disclosure - I did a lot of beta-testing for this in its upgrade from Win9x to Win2K/XP and am perhaps biased. Note: author has recently added a note that its not Vista-ready (and may or may not ever be :-( ). That alone is sufficient to keep me on WinXp as long as possible.

Regards ... Alec -- buralex-gmail

* buralex@gmail.com [09-30-07 18:57]:

That alone is sufficient to keep me on WinXp as long as possible.

I will pray for you. In linux.

On Monday 01 October 2007 08:56:40 buralex@gmail.com wrote:

Note: author has recently added a note that its not Vista- ready (and may or may not ever be :-( ). That alone is sufficient to keep me on WinXp as long as possible.

Or to inspire you to make a really robust & portable GTK version which *will* run on Vista. At least under GIMP if nowhere else. (-:

An advantage to making it fly under GTK is that it then becomes reasonable to use the features with other apps, naturally including file managers. (-:

Cheers; Leon

On Monday 01 October 2007 09:55:19 Patrick Shanahan wrote:

I will pray for you.    In linux.

What, not in Plan9? Or Hurd? Where's your ambition? (-:

Cheers; Leon

Hi!

El dg 30 de 09 del 2007 a les 12:10 +0200, en/na Sven Neumann va escriure:

The application can already add bookmarks and GIMP 2.4 already makes use of this feature in some places.

I see the "Recently Used" (files) entry in file-chooser. Can it hold "Recently Used Dirs" ?

I am not convinced though that this would be a good way to solve the problems brought up the user who started the thread.

No, dir bookmarks not solve any problem, but can come in help when the gimp assumption about the directory where to save a file and the user wanted directory differs.

There are two issues here: Find good default saving assumptions for most users. What to do when a user has different needs.

Bookmarking recent saving dirs deals with the second case.

Perhaps we need to collect the typical usage scenarios that involve use of the file-chooser and evaluate how the current solution deals with them and if there are ways to improve it.

I just have a suggestion for "paste as new" and is that the default saving directory for the new image can inherit the default saving directory from the image where the action is called, or if it is called from the toolbox, inherite from the active image.

As this, the users can have some control over the default saving directory.

Yours
Pere

Hi,

On Mon, 2007-10-01 at 23:31 +0200, Pere Pujal i Carabantes wrote:

I see the "Recently Used" (files) entry in file-chooser. Can it hold "Recently Used Dirs" ?

For the Save dialog, this would probably make more sense than presenting recently used files. Would probably make sense to bring this up for discussion on the gtk-developer list or at least file a bug report for it against the GTK+ file-chooser.

I just have a suggestion for "paste as new" and is that the default saving directory for the new image can inherit the default saving directory from the image where the action is called, or if it is called from the toolbox, inherite from the active image.

That would be rather confusing, IMO. But what about the following:

If an image already has a filename associated to it, then open the Save file-chooser in that folder. Otherwise use the folder of the most recent save operation. Would that make sense?

Sven

On Tue, 02 Oct 2007 18:20:33 +0200, Sven Neumann wrote:

If an image already has a filename associated to it, then open the Save file-chooser in that folder. Otherwise use the folder of the most recent save operation. Would that make sense?

Definitely. That should be the default behavior.

If needed, the current behavior (always use the last directory) can be emulated with a temporary bookmark. The opposite is not true: if you are working on several images and want to save each of them in the directory they came from, then the current file-chooser behavior gets in the way.

-Raphaël

hi gimpusers!

please, what is the difference between a plug-in and a script? I am asking because I never know if I should copy a plug-in (e.g. from the registry.gimp.org - site) in to the plug-in or the script folder. I'ts always a try and error thing. And most of the times it's working when I am copying the plug-in into the scripts folder. but what is then a plug-in?

thanks for explanations, tina

El dt 02 de 10 del 2007 a les 18:20 +0200, en/na Sven Neumann va escriure:

Hi,

On Mon, 2007-10-01 at 23:31 +0200, Pere Pujal i Carabantes wrote:

I see the "Recently Used" (files) entry in file-chooser. Can it hold "Recently Used Dirs" ?

For the Save dialog, this would probably make more sense than presenting recently used files. Would probably make sense to bring this up for discussion on the gtk-developer list or at least file a bug report for it against the GTK+ file-chooser.

Done, see:
http://mail.gnome.org/archives/gtk-devel-list/2007-October/msg00010.html

If an image already has a filename associated to it, then open the Save file-chooser in that folder. Otherwise use the folder of the most recent save operation. Would that make sense?

I have to disagree, that can be very confusing. (and very powerfull BTW, you can change the default saving directory on the fly):

open a/b/c.xcf (named file) new unnamed.xcf
new unnamed1.xcf
save unnamed.xcf to d/e/f.xcf (file-chooser comes up) default saving directory comes d/e
save a/b/c.xcf ( CTRL+S file-chooser doe not appear as the file has yet a name)
default saving directory comes a/b nearly without notice save unnamed1.xcf

What happens? a/b is presented when I just manualy selected d/e in the previous opened file-chooser.

What about this?: If an image already has a filename associated to it, then open the Save file-chooser in that folder. Otherwise use the folder of the most recent save operation that implies the use of file-chooser.

Yours Pere

A plugin is an executable - ie. it's a program you can run, like you can run Inkscape or GIMP.
A script is a set of text instructions which are run by a script interpreter (script-fu).

Thus, it's easy to tell the difference: * If it has a .scm extension, it's a script * Failing that, if you can open it in a text editor and it looks somewhat readable, it's a script.

On 10/5/07, Bettina Lechner wrote:

hi gimpusers!

please, what is the difference between a plug-in and a script? I am asking because I never know if I should copy a plug-in (e.g. from the registry.gimp.org - site) in to the plug-in or the script folder. I'ts always a try and error thing. And most of the times it's working when I am copying the plug-in into the scripts folder. but what is then a plug-in?

thanks for explanations, tina

--

newhouse - new media Bettina Karena Lechner
neue str 16, 2565 neuhaus
austria

mobil: +43 660 46 25 0 25 tel.: +43 26 74 878 72
fax: +43 2674 878 81
mailto:lechner@newhouse.at
www.newhouse.at
---
Der Anfang ist die Hälfte des Ganzen. Aristoteles (384 - 322 v. Chr)

Hi,

On Thu, 2007-10-04 at 17:12 +0200, Raphaël Quinet wrote:

On Tue, 02 Oct 2007 18:20:33 +0200, Sven Neumann wrote:

If an image already has a filename associated to it, then open the Save file-chooser in that folder. Otherwise use the folder of the most recent save operation. Would that make sense?

Definitely. That should be the default behavior.

If needed, the current behavior (always use the last directory) can be emulated with a temporary bookmark. The opposite is not true: if you are working on several images and want to save each of them in the directory they came from, then the current file-chooser behavior gets in the way.

Huh? In GIMP 2.4 the Save As file-chooser opens in the directory where you loaded the image from. Your last sentence seems to imply that this is the behavior that you desire and I don't see why you describe it as 'gets in the way'.

Sven

Von: "David Gowers"

Thus, it's easy to tell the difference: * If it has a .scm extension, it's a script * Failing that, if you can open it in a text editor and it looks somewhat readable, it's a script.

So unless we get some plugins written in e.g. Brainfuck or Piet, everything is a script?

SCNR, Michael

On 10/5/07, Bettina Lechner wrote:

please, what is the difference between a plug-in and a script? I am asking because I never know if I should copy a plug-in (e.g. from the registry.gimp.org - site) in to the plug-in or the script folder.

In answer to the main point of the Bettina's message, it is easy to know what you need to do with items you get from the plug-in registry, and in which directory to put the files so you will be able to use them in GIMP.

If the file ends in .scm, it is a Script-Fu script and it belongs in the scripts directory.

If the file ends in .c, it is a C-coded source file which needs to be compiled (typically using gimptool if its a single file). The compiled file is an executable that will go in the plug-ins directory.

Everything else will go in to the plug-ins directory.

David Gowers wrote: > A plugin is an executable - ie. it's a program you can run, like you > can run Inkscape or GIMP.
> A script is a set of text instructions which are run by a script > interpreter (script-fu).

For the most part, what David wrote is true. To muddy the waters a bit, when it comes to GIMP, text instructions in a file written using the Ruby, Perl, or Python languages, which makes them technically scripts, are plug-ins when it comes to GIMP and need to be put in the plug-ins directory. They should also be marked executable (when running GIMP under Linux).

Hi,

On Fri, 2007-10-05 at 12:40 -0400, Kevin Cozens wrote:

If the file ends in .scm, it is a Script-Fu script and it belongs in the scripts directory.

Yes, that folder should have been called "script-fu" in the first place as only Script-Fu scripts go there. But for historical reasons it's "scripts".

Sven