Hi,
I've just committed a patch (trunk revision 10062) that replaces the bitmap selector list (in the preferences) with a file selector. It reuses the existing "open" dialogs (the file type filter are set to executable files - or everything, on Gnu/Linux and OSX - and the preview disabled), but the change doesn't affect usual "open" or "import" operations. I hesitated to create a new specific dialog, but found it more logic to reuse the existing ones. The initial goal of that patch was to make it work on Windows (see Bug #26261, Edit externally doesn't work on Windows, https://bugs.launchpad.net/inkscape/+bug/262617), but it also adds command line arguments support (as far as the image is the last argument...). It should work on Windows (native dialog and GTK), Gnu/Linux and OS-X (thanks ~suv for your help!).
Don't hesitate to comment. Regards. -- Nicolas
On Mon, 2011-02-21 at 19:30 +0000, Nicolas Dufour wrote:
Gnu/Linux and OS-X (thanks ~suv for your help!).
Don't hesitate to comment.
If it's just a file selection dialog box, then it's not working on gnome. There are existing ways of listing installed applications that don't require the use to go hunting in the obscure file system.
Unless I misunderstood how you've implemented this.
Martin,
De : Martin Owens <doctormo@...400...>
If it's just a file selection dialog box, then it's not working on gnome. There are existing ways of listing installed applications that don't require the use to go hunting in the obscure file system.
Unless I misunderstood how you've implemented this.
Inkscape already uses two kinds of file dialogs: a GTK one, for Gnu/Linux and OSX, and a native one for Windows. I've just modified the "open file" version of both dialogs in order to use a different file type filter and remove the preview when called from the preferences, modified the context menu to support URI, filenames and command line options, and created a new preference widget that provides an entry field and a browse button linked to the file dialog. Nothing revolutionary ;) Thus there's no reason why (bug excepted) why it shouldn't work on gnome.
Regards, -- Nicolas
On Tue, 2011-02-22 at 09:06 +0000, Nicolas Dufour wrote:
Thus there's no reason why (bug excepted) why it shouldn't work on gnome.
Thanks for the further information. I'm still a little confused. As a design; getting users to select executable files is wrong on Gnome. If this is what you have, then it's broken by it's design, even if it technically works.
It sounds like you've programmed to the Windows concept of selecting program file via their exe file. Which isn't how XDG/FreeDesktop systems work (gnome, kde etc), these use .desktop files in known locations which have translated names, icons and descriptions of the program.
Have I gotten the right end of the stick, that you've modified the file selection dialog to allow you to select executable files from the file system?
Best regards, Martin Owens
De : Martin Owens <doctormo@...400...>
It sounds like you've programmed to the Windows concept of selecting program file via their exe file. Which isn't how XDG/FreeDesktop systems work (gnome, kde etc), these use .desktop files in known locations which have translated names, icons and descriptions of the program.
Have I gotten the right end of the stick, that you've modified the file selection dialog to allow you to select executable files from the file system?
Yes, you're right. I wanted to reproduced the Scribus external apps preferences dialog (ok, it's not a gnome application...), and wasn't aware it could harm to do that. I also wanted it to work with command lines in order to allow OSX users to use 'open' commands. Regarding the gnome concept, the old inkscape list was not better than the new selector since it just listed some manually chosen applications. How should we handle that specific preference then? Just let a simple text entry (full command line)? Auto-detect installed applications and add a command line arguments entry field? Do you have links to applications that successfully uses that concept on all platforms?
Short term (for now, I don't want to spend too much time on it if it requires too much work), should we keep the patched version or revert the changes? If it's just a problem with the selector, we could just keep the entry field and the context menu changes so that bitmap editing works on OSX and Windows.
Regards, -- Nicolas
participants (2)
-
Martin Owens -
Nicolas Dufour