What if saving session dialogue would have an option "whether to run include relevant_packages.gfn
on the next gretl session? Oleh 17 лютого 2018, 22:58:37, від "Riccardo (Jack) Lucchetti" <r.lucchetti(a)univpm.it>: On Sat, 17 Feb 2018, Allin Cottrell wrote: >> It has been explained (to me and others) that the session concept is a GUI >> thing. I don't see why contributed functions need to be saved in there. I >> would just end this practice, and the problem of this thread would not >> appear. Or what am I missing? > > Well, maybe you're right, but here's the sort of thing you may be missing. > Suppose I save an SVAR result "as an icon" then save my session. I (or > perhaps someone else) later opens the saved session file, and double-clicks > on the icon. This should result in a call to the SVAR bundle-printer > function. (And the same goes for contributed packages, not just addons.) Will > the function be available? We don't really know, unless we bundle the > relevant functions into the session file. > > True, the session file is inherently a GUI thing, but ideally it should be a > snapshot of the state of gretl at the time of saving, so you could open the > file later and pick up where you left off -- or, in principle, send the file > to someone else, who could reconstitute your gretl state without having to > load any other files. > > One thing is clear: _if_ we're going to save loaded functions in the session > file, we have to mark the ones that belong to specific packages as owned by > those packages so we don't get false-positive conflicts. I guess that we might make a distinction here between regular packages and addons. A function from an addon should always be available (bar version changes, of course), whereas a function from a package is only avalable if the user installed that package on the machine that he/she is using to open the session file. Not sure if this is relevant, though. ------------------------------------------------------- Riccardo (Jack) Lucchetti Dipartimento di Scienze Economiche e Sociali (DiSES) Università Politecnica delle Marche (formerly known as Università di Ancona) r.lucchetti(a)univpm.it http://www2.econ.univpm.it/servizi/hpp/lucchetti ------------------------------------------------------- _______________________________________________ Gretl-users mailing list Gretl-users(a)lists.wfu.edu http://lists.wfu.edu/mailman/listinfo/gretl-users
What if saving session dialogue would have
an option "whether to run include relevant_packages.gfn
on the next gretl session?
Oleh
17 лÑÑого 2018, 22:58:37, вÑд "Riccardo (Jack) Lucchetti" <r.lucche...@univpm.it>:
On Sat, 17 Feb 2018, Allin Cottrell wrote: >> It has been explained (to me and others) that the session concept is a GUI >> thing. I don't see why contributed functions need to be saved in there. I >> would just end this practice, and the problem of this thread would not >> appear. Or what am I missing? > > Well, maybe you're right, but here's the sort of thing you may be missing. > Suppose I save an SVAR result "as an icon" then save my session. I (or > perhaps someone else) later opens the saved session file, and double-clicks > on the icon. This should result in a call to the SVAR bundle-printer > function. (And the same goes for contributed packages, not just addons.) Will > the function be available? We don't really know, unless we bundle the > relevant functions into the session file. > > True, the session file is inherently a GUI thing, but ideally it should be a > snapshot of the state of gretl at the time of saving, so you could open the > file later and pick up where you left off -- or, in principle, send the file > to someone else, who could reconstitute your gretl state without having to > load any other files. > > One thing is clear: _if_ we're going to save loaded functions in the session > file, we have to mark the ones that belong to specific packages as owned by > those packages so we don't get false-positive conflicts. I guess that we might make a distinction here between regular packages and addons. A function from an addon should always be available (bar version changes, of course), whereas a function from a package is only avalable if the user installed that package on the machine that he/she is using to open the session file. Not sure if this is relevant, though. ------------------------------------------------------- Riccardo (Jack) Lucchetti Dipartimento di Scienze Economiche e Sociali (DiSES) Università Politecnica delle Marche (formerly known as Università di Ancona) r.lucche...@univpm.it http://www2.econ.univpm.it/servizi/hpp/lucchetti -------------------------------------------------------_______________________________________________ Gretl-users mailing list gretl-us...@lists.wfu.edu http://lists.wfu.edu/mailman/listinfo/gretl-users
