Another useful feature might be the ability to drag and
drop a project folder onto the OmegaT icon (the
shortcut icon on the desktop) so that OmT runs and
opens that project.
In MS Windows, what happens is that when a file is
dragged and dropped onto a shortcut for a program, that
program simply opens the file. You generally can't do
it with a folder, but you can do it with a file. So
perhaps a kludge would be for OmT to create not only a
folder but also a startup file of the same name, which
can be used for running OmT.
This is at least partly implemented in /trunk.
Currently, a project folder can be dragged and dropped unto OmegaT.exe (under Windows). This will successfully open the corresponding project. It works also with a shortcut of OmegaT.exe.
It doesn't work with a batch file (with java -jar, etc.), given the way arguments are passed to a patch file.
I haven't tested yet under Linux, and it remains to be seen how this behaves on a Mac.
One improvement could be to be able to pass an omegat.project file (which I think would be, from the “arguments” point of view, in fact just a path+omegat.project at the end) to OmegaT in addition to just a path. In that case, it would then be possible to associate .project files to OmegaT, to have OmegaT launched automatically when double-clicking on the omegat.project file.
Didier
Diff:
Implemented in /trunk. It is possible to drag either an OmegaT project folder or an omegat.project file to OmegaT.
Didier
Last edit: Didier Briel 2015-05-18
This will also work on OS X.
You can also drag and drop a project folder or
omegat.project
to the Editor pane to open the project (when no project is open; otherwise the dragged item will be treated as source files to import into the current project per RFE#1091).Maybe it won't be a bad idea to add a dialog to confirm adding
omegat.project or a folder containing omegat.project as source files of
the existing project, as in most cases, I suppose, it's not what the
user intends? The dialog may also say that in order to open a new
project, the current one has to be closed.
--
Kos
On 05/18/2015 06:01 AM, Aaron Madlon-Kay wrote:
Related
Feature Requests:
#113Here, when I drag and drop omegat.project to the Editor of an opened project, the current project is closed and the new project is opened.
Didier
Didier, are you sure that's what's happening? After dragging to the editor the project will be reloaded because you added files. I don't see a code path that could result in a different project being opened as a result of what you described (and I can't reproduce locally).
Last edit: Aaron Madlon-Kay 2015-05-20
You're right, my mistake.
So, I second what Kos what saying:
Perhaps it should be detected (that you're dragging an OmegaT project to the Editor).
I'm not sure it make sense to copy an entire OmegaT project into the source folder of another.
Didier
It does not and we've had a number of cases where users click on "Add source files" and that led to all sorts of problems.
Jean-Christophe
Related
Feature Requests:
#113Fair enough. In r7314 when a project (dir or
omegat.project
) is dropped on the editor or the application icon, the current project will be closed and the dropped project will be opened.Last edit: Aaron Madlon-Kay 2015-05-22
Implemented in the released version 3.5 of OmegaT.
Didier