Bug #2990
openfile|open dialog should open in workflows directory
0%
Description
Kenneth Evans has requested:
Is there an easy way to fix Kepler so the initial directory you get with
File | Open is where your workflows are, rather than where Kepler is.
Just starting Kepler in that directory doesn’t seem to work.
This makes sense to me. I also think the dialog should be saving its state, so that if a user navigates to a new workflow location, the next time it opens it will be in that directory that the user had selected.
Updated by Dan Higgins about 17 years ago
I think we should try to get the initial file dialog to point to the 'demos' directory and then remember the last directory.
Updated by Dan Higgins almost 17 years ago
File|Open now initially opens into the $KEPLER/demos directory and remembers where the last location was (until shut-down).
Updated by Christopher Brooks over 16 years ago
I'm reopening this bug because if the user uses the kepler.sh script
then having File->Open open kepler/demos is odd. Instead we should
open the current directory where the user invoked kepler.sh.
The same is probably true for kepler.bat and kepler.exe. We might
want to consider creating a bin directory and placing these scripts
and exes in that directory so that the user can place $KEPLER/bin
in their path.
My rationale on this is that if you think about how a user works on a system,
they are probably working on workflows in their own directory, not
in kepler/demos/.
There is a difference between when a program is invoked from the command
line and when it is invoked from a menu choice.
- If a command is invoked from the command line, then File > Open should If the command is invoked from a menu choice, then the File -> Open
open the current directory
should ideally open the last directory that was opened (even in a previous
run). Or, having kepler/demos opened is a reasonable work around.
These are just my $0.02. This bug was closed before we had kepler.sh and
kepler.bat.