Sven may be correct about the potential confusion between data files
and session files, but I disagree strongly with his solution.
I suspect that this is a matter of approach to econometric projects,
but for me the overriding issue is to ensure that there is a clear
trail of what has been done to raw data as well as what models have
been estimated. Quite apart from my own mistakes, I have had to deal
with so much trouble caused
by students and researchers who fail to maintain a satisfactory
record of what they have been done.
For this reason, in my view it is basic good practice to use script
files (a) to document the process of transforming data variables and
creating new data files, and (b) to maintain a record of the models
that have been tested so that the process can be replicated either
with new or updated data or by other researchers or in preparing work
for publication. In this context, a clear distinction between data
files, script files, etc should be the dominant way of
working. Session files may be convenient but they discourage good
working practice. For myself, I do 99% of my work through script
files (or do files in Stata) and I insist that my students and
research assistants should work in a similar way because it is so
much easier to understand what has been done.
This is a plea to maintain the primacy of gdt datafiles combined with
script files, which are simple text. Session files should not become
the default file type.
Gordon Hughes
Therefore I think that it would be worth considering centering
everything on the session files (.gretl). In that respect I think Eviews
has got it right: just one workfile potentially holding all kinds of
objects that you may need. The datafiles (.gdt) would still be supported
of course as an export/import format, but the interface would make it
clear to the user that it's an explicit export (save data as...) and
that the active storage file is always the session file.
Of course that would be more like a medium-term plan I guess, so in the
short term I would suggest the following:
* when a session is opened, don't show any datafile name in the status
line just below the menu bar -- that's confusing precisely because that
file may not exist anymore or be altered in the meantime
* not show a dialog for ctrl-s (too annoying for real work)
* so probably follow your suggestion to interpret ctrl-s as saving the
session (though some people may be shocked when they don't find a .gdt
file afterwards)