6:26 p.m.
Hi,
once more I have a little feature request:
In the function package editor it would be nice IMO if for an existing
package the "save" button were accompanied by a "save as" button.
Scenario (I have just been facing it ;-) :
You change something in the code, or bump the version number, or
whatever, and want to save the changed package under a different name
(in my case, including the changed version number). This doesn't seem
possible currently.
Apart from that, I'm planning to publish/upload the py4gretl
cointegration packages soon. My naive plan is to just tick the "upload
when saving" - option and see what happens. Anything I should do before
that?
Thanks,
Sven
9:04 p.m.
On Thu, 8 Mar 2007, Sven Schreiber wrote:
once more I have a little feature request:
In the function package editor it would be nice IMO if for an existing
package the "save" button were accompanied by a "save as" button.
Scenario (I have just been facing it ;-) :
You change something in the code, or bump the version number, or
whatever, and want to save the changed package under a different name
(in my case, including the changed version number). This doesn't seem
possible currently.
This relates to something we discussed a while ago, which is still
unfinished business I'm afraid. I don't want to enable "Save as"
in that context (in fact, I deliberately removed it), the reason
being that we don't want the name of a function package to come
unstuck from the name of its public interface. What should happen
is that the version number gets automatically factored into the
file name. I'll do that before we release of 1.6.2, which should
be soon.
Apart from that, I'm planning to publish/upload the py4gretl
cointegration packages soon. My naive plan is to just tick the
"upload when saving" - option and see what happens. Anything I
should do before that?
I think that should work, but I should probably run a test to
confirm that.
Allin.
9:13 p.m.
On Thu, 8 Mar 2007, Sven Schreiber wrote:
You change something in the code, or bump the version number, or
whatever, and want to save the changed package under a different name
(in my case, including the changed version number).
I've now made some relevant changes in CVS. The function package
editor has a checkbox, "include version in filename". I've also
put in some stipulations on what the version string should look
like, to make it straightforward to add or subtract version
strings if needed. So: a package filename should look like one of
the following
interface-M.N.P.gfn
interface-M.N.gfn
interface-M.gfn
interface.gfn
where M, N and P are all numbers (major, minor, patchlevel, if you
like). To conform to this, the py4gretl files would best be
renamed as, for example:
py4gretl_vecm-0.8.2.gfn
This is not tested properly yet, but I'll do that soon.
Allin.
10:23 p.m.
Allin Cottrell schrieb:
interface-M.N.P.gfn
interface-M.N.gfn
interface-M.gfn
interface.gfn
where M, N and P are all numbers (major, minor, patchlevel, if you
like). To conform to this, the py4gretl files would best be renamed as,
for example:
py4gretl_vecm-0.8.2.gfn
Ok, I'll do that.
This is not tested properly yet, but I'll do that soon.
Me too :-)
-sven
10:50 p.m.
On Fri, 9 Mar 2007, Sven Schreiber wrote:
Allin Cottrell schrieb:
>
> interface-M.N.P.gfn
> interface-M.N.gfn
> interface-M.gfn
> interface.gfn
>
> where M, N and P are all numbers (major, minor, patchlevel, if you
> like). To conform to this, the py4gretl files would best be renamed as,
> for example:
>
> py4gretl_vecm-0.8.2.gfn
Ok, I'll do that.
Thanks!
> This is not tested properly yet, but I'll do that soon.
Me too :-)
Actually, I now realize that this won't work right just yet, for a
package that already has a version number in its filename. I'll
work on that this evening and commit a fix.
Allin.
11:14 p.m.
Allin Cottrell schrieb:
On Fri, 9 Mar 2007, Sven Schreiber wrote:
> Allin Cottrell schrieb:
>>
>> interface-M.N.P.gfn
>> interface-M.N.gfn
>> interface-M.gfn
>> interface.gfn
>>
>> where M, N and P are all numbers (major, minor, patchlevel, if you
>> like). To conform to this, the py4gretl files would best be renamed as,
>> for example:
>>
>> py4gretl_vecm-0.8.2.gfn
>
> Ok, I'll do that.
Thanks!
>> This is not tested properly yet, but I'll do that soon.
>
> Me too :-)
Actually, I now realize that this won't work right just yet, for a
package that already has a version number in its filename. I'll work on
that this evening and commit a fix.
I wouldn't worry too much about existing packages, I can re-package
things just fine. (Or did I misunderstand you?)
cheers,
sven
12:09 a.m.
On Sat, 10 Mar 2007, Sven Schreiber wrote:
I wouldn't worry too much about existing packages, I can
re-package
things just fine. (Or did I misunderstand you?)
Here's what I think will happen:
* Existing package, no version in file name: version string will
be added OK (if you check the relevant box).
* Existing package with version in file name: version string will
be removed OK, if you uncheck the box.
* Edit existing package with version in file name: edit the
package and change the version string: the filename will not be
changed to reflect the new version string.
Since (if I'm understanding you right) it's the last case that
you're interested in, this needs some more work!
Allin.
6496
days inactive
6498
days old
6 comments
2 participants
participants (2)
-
Allin Cottrell -
Sven Schreiber