On Wed, 4 Apr 2007, Talha Yalta wrote:
6- When I have more than 41 tables...
Do you mean more than 41 models?
I cannot add the 42nd and above to the model table by dragging
and dropping since the model table icon is invisible and the
icon window doesn't scroll while the mouse button is pressed
(due to dragging)
I would say that more than a couple of dozen models per GUI
session is going beyond the design limits: with that number of
models you want a script, or set of scripts. But I'll take a
look.
7- Sessions are not saved as a single compressed file. I have a,
say, session1.gretl file plus a session1 directory with the
data, an xml file, and all the model files.
Sessions are in fact saved as a single compressed file. Open
sessions are also represented by a directory containing the files
you mention: the "save" file is a compressed archive of the
directory in question. (I guess I should make these directories
hidden so that people won't get confused.)
8- What is worse, when I "save as" a new session, say
session2,
I get a session2.gretl file, however, the old session1 directory
is now replaced with a session2 directory with all the files
lost.
Wait a minute: Are you saying that if you save as "session2" the
session won't open again? (Never mind what's going on in the
background -- just concentrate on things at the visible level not
working as they are clearly supposed to work.)
9- Suggestion: Being able to create a model table with more
models (more than 6, maybe 8) would be nice to have.
I guess this might be feasible for PDF formatting on a landscape
page. I judged that 6 was about the limit for on-screen
legibility.
10- Suggestion: Whoever I show gretl to, they are simply blown
away by the icon view concept. How models and graphs can be
saved as icons for future reference, how they can easily be
combined and exported to LaTeX, the little utilities... This is
some serious innovation IMO. However, the default view doesn't
do the program justice...
I agree that the session concept is not fully exploited at
present, and that is something we will come back to and
re-examine. Thanks for the suggestions. Right now we're focused
on particular econometric functionality (the bootstrap and VECMs)
but the UI does need reconsideration.
--
Allin Cottrell
Department of Economics
Wake Forest University, NC