| Coyote Library Updates [message #87354] |
Mon, 27 January 2014 20:37  |
David Fanning
Messages: 11724
Registered: August 2001
|
Senior Member |
|
|
Folks,
There have been a number of changes to the Coyote Library over the past
week. This is sort of an on-going process now. As I use a program that I
think belongs in the "formal" Coyote Library I update its documentation
and sometimes give it the name I wish I had given it way back in 2006 or
whenever it was that the program was first created. No particular reason
for a lot of activity this week, but here you go:
WhoAmI -> cgWhoAmI
WhoCalledMe -> cgWhoCalledMe
ProgramRootDir -> cgSourceDir
Find_Resource_File -> cgFindPathTo
fscCleanup7 -> cgCleanup
fscCleanup8 -> cgCleanup
BitGet -> cgBitGet
As a result of these changes, there were about a dozen files
in the Coyote and Catalyst Libraries that had to be updated.
Incidentally, as I was converting Find_Resource_File I found a major bug
that was slowing the program down a great deal. I fixed that both in the
retired program and in the new cgFindPathTo program.
The easiest way to keep updated, of course, is to use the SVN
repositories at idl-coyote.googlecode.com. But, these files are also
available on my web page:
http://www.idlcoyote.com/programs/zip_files/coyoteprograms.z ip
http://www.idlcoyote.com/programs/zip_files/catalyst.zip
http://www.idlcoyote.com/programs/zip_files/retiredcoyotelib rary.zip
Cheers,
David
--
David Fanning, Ph.D.
Fanning Software Consulting, Inc.
Coyote's Guide to IDL Programming: http://www.idlcoyote.com/
Sepore ma de ni thue. ("Perhaps thou speakest truth.")
|
|
|
|
| Re: Coyote Library Updates [message #87368 is a reply to message #87354] |
Tue, 28 January 2014 08:38  |
Paul Van Delst[1]
Messages: 1157
Registered: April 2002
|
Senior Member |
|
|
Hello,
On 01/27/14 23:37, David Fanning wrote:
> The easiest way to keep updated, of course, is to use the SVN
> repositories at idl-coyote.googlecode.com.
So what's the tag URL for this update?
The latest one I see ("coyote_library_5.0") doesn't contain the new
files you mentioned (but still contains the old ones), e.g.
$ svn list http://.../svn/tags/coyote/coyote_library_5.0/whoami.pro
whoami.pro
$ svn list http://.../svn/tags/coyote/coyote_library_5.0/cgwhoami.pro
svn: URL
' http://idl-coyote.googlecode.com/svn/tags/coyote/coyote_libr ary_5.0/cgwhoami.pro'
non-existent in that revision
Just so's you know, I export your libraries into our repository here. I
can't use an svn-external because then no-one can check out your
libraries on any machines behind the various and sundry firewalls.
cheers,
paulv
p.s. For other readers, Coyote library maintenance donations can be made to:
http://www.idlcoyote.com/coyotestore/index.php?main_page=pro duct_info&cPath=67&products_id=186
'cause, you know, we need to keep the ball rolling here.... :o)
p.p.s. Gotta say it: Any endorsement on my part does not reflect any
endorsement by either NOAA or my employer.
|
|
|
|
| Re: Coyote Library Updates [message #87369 is a reply to message #87368] |
Tue, 28 January 2014 08:53 |
David Fanning
Messages: 11724
Registered: August 2001
|
Senior Member |
|
|
Paul van Delst writes:
> On 01/27/14 23:37, David Fanning wrote:
>> The easiest way to keep updated, of course, is to use the SVN
>> repositories at idl-coyote.googlecode.com.
>
> So what's the tag URL for this update?
>
> The latest one I see ("coyote_library_5.0") doesn't contain the new
> files you mentioned (but still contains the old ones), e.g.
>
> $ svn list http://.../svn/tags/coyote/coyote_library_5.0/whoami.pro
> whoami.pro
>
> $ svn list http://.../svn/tags/coyote/coyote_library_5.0/cgwhoami.pro
> svn: URL
> ' http://idl-coyote.googlecode.com/svn/tags/coyote/coyote_libr ary_5.0/cgwhoami.pro'
> non-existent in that revision
>
> Just so's you know, I export your libraries into our repository here. I
> can't use an svn-external because then no-one can check out your
> libraries on any machines behind the various and sundry firewalls.
Well, I apologize, I just learned Coyote hasn't been keeping up with the
tagging. I've docked his pay. We'll see if he does better now. The
latest tagged version (just this minute) is here:
http://idl-coyote.googlecode.com/svn/tags/coyote/coyote_libr ary_6.0
> p.s. For other readers, Coyote library maintenance donations can be
made to:
>
> http://www.idlcoyote.com/coyotestore/index.php?main_page=pro duct_info&cPath=67&products_id=186
>
> 'cause, you know, we need to keep the ball rolling here.... :o)
Indeed. And I'll personally make sure none of this ends up in Coyote's
"licker" budget. :-(
Cheers,
David
--
David Fanning, Ph.D.
Fanning Software Consulting, Inc.
Coyote's Guide to IDL Programming: http://www.idlcoyote.com/
Sepore ma de ni thue. ("Perhaps thou speakest truth.")
|
|
|
|
| Re: Coyote Library Updates [message #87372 is a reply to message #87369] |
Tue, 28 January 2014 11:34 |
Helder Marchetto
Messages: 520
Registered: November 2011
|
Senior Member |
|
|
On Tuesday, January 28, 2014 5:53:29 PM UTC+1, David Fanning wrote:
> Paul van Delst writes:
>
>
>
>> On 01/27/14 23:37, David Fanning wrote:
>
>>> The easiest way to keep updated, of course, is to use the SVN
>
>>> repositories at idl-coyote.googlecode.com.
>
>>
>
>> So what's the tag URL for this update?
>
>>
>
>> The latest one I see ("coyote_library_5.0") doesn't contain the new
>
>> files you mentioned (but still contains the old ones), e.g.
>
>>
>
>> $ svn list http://.../svn/tags/coyote/coyote_library_5.0/whoami.pro
>
>> whoami.pro
>
>>
>
>> $ svn list http://.../svn/tags/coyote/coyote_library_5.0/cgwhoami.pro
>
>> svn: URL
>
>> ' http://idl-coyote.googlecode.com/svn/tags/coyote/coyote_libr ary_5.0/cgwhoami.pro'
>
>> non-existent in that revision
>
>>
>
>> Just so's you know, I export your libraries into our repository here. I
>
>> can't use an svn-external because then no-one can check out your
>
>> libraries on any machines behind the various and sundry firewalls.
>
>
>
> Well, I apologize, I just learned Coyote hasn't been keeping up with the
>
> tagging. I've docked his pay. We'll see if he does better now. The
>
> latest tagged version (just this minute) is here:
>
>
>
> http://idl-coyote.googlecode.com/svn/tags/coyote/coyote_libr ary_6.0
>
>
>
>> p.s. For other readers, Coyote library maintenance donations can be
>
> made to:
>
>>
>
>> http://www.idlcoyote.com/coyotestore/index.php?main_page=pro duct_info&cPath=67&products_id=186
>
>>
>
>> 'cause, you know, we need to keep the ball rolling here.... :o)
>
>
>
> Indeed. And I'll personally make sure none of this ends up in Coyote's
>
> "licker" budget. :-(
>
>
>
> Cheers,
>
>
>
> David
>
> --
>
> David Fanning, Ph.D.
>
> Fanning Software Consulting, Inc.
>
> Coyote's Guide to IDL Programming: http://www.idlcoyote.com/
>
> Sepore ma de ni thue. ("Perhaps thou speakest truth.")
Hi,
given the fact that I have no idea what is happening when I daily execute my svn checkout, it seems like I was using a different command and things where working. So, I'm using:
svn checkout http://idl-coyote.googlecode.com/svn/trunk/coyote E:\Where_I_Put_My_Stuff_On_My_PC
Now the question is: Should I use the address:
http://idl-coyote.googlecode.com/svn/tags/coyote/coyote_libr ary_6.0
or
http://idl-coyote.googlecode.com/svn/trunk/coyote
I have implemented this operation in my task scheduler not to forget checking for updates.
Thanks,
Helder
|
|
|
|
| Re: Coyote Library Updates [message #87373 is a reply to message #87372] |
Tue, 28 January 2014 12:18 |
David Fanning
Messages: 11724
Registered: August 2001
|
Senior Member |
|
|
Helder writes:
> given the fact that I have no idea what is happening when I daily execute my svn checkout, it seems like I was using a different command and things where working. So, I'm using:
>
> svn checkout http://idl-coyote.googlecode.com/svn/trunk/coyote E:\Where_I_Put_My_Stuff_On_My_PC
>
> Now the question is: Should I use the address:
> http://idl-coyote.googlecode.com/svn/tags/coyote/coyote_libr ary_6.0
> or
> http://idl-coyote.googlecode.com/svn/trunk/coyote
>
> I have implemented this operation in my task scheduler not to forget checking for updates.
No, you are doing things exactly right. :-)
You start your day the way I do. (Of course, we have good and bad days,
but hopefully more good than bad.) Paul wants a "stable" release. I'm
never sure exactly what that means, because I update these files
frequently (at least once a week and sometimes several times a day).
But, if a few days to go by and I haven't made any changes and Coyote
remembers to remind me, I make a tagged release.
I do try very hard to have the main repository in good shape at the end
of every day. I'm not perfect, but my score is pretty high.
I know it annoys people to have a lot of these files "retired". But, it
is a lot of work to get all the documentation changed over to the IDLDOC
style that I can have on my web page. I do it a little at a time now,
and only when I find I am using a particular program. Name space is
getting crowded, and I would like to have all my programs with the "cg"
prefix. Eventually, I might get there. When I do make a change, I make
sure all my Library files reflect the change and all the articles on my
web page reflect the change. This is a BIG job, which is another reason
I'm not anxious to do it often. Even a simple change to a routine that
is not used much takes an hour or so to effect. Most changes take most
of an afternoon. Mistakes can be made. I typically wait a couple of days
to make a tagged release after a major upset. I've learned the hard way
to test documentation headers before I commit the files. :-)
Cheers,
David
--
David Fanning, Ph.D.
Fanning Software Consulting, Inc.
Coyote's Guide to IDL Programming: http://www.idlcoyote.com/
Sepore ma de ni thue. ("Perhaps thou speakest truth.")
|
|
|
|
| Re: Coyote Library Updates [message #87374 is a reply to message #87373] |
Tue, 28 January 2014 13:17 |
Helder Marchetto
Messages: 520
Registered: November 2011
|
Senior Member |
|
|
On Tuesday, January 28, 2014 9:18:48 PM UTC+1, David Fanning wrote:
> Helder writes:
>
>
>
>> given the fact that I have no idea what is happening when I daily execute my svn checkout, it seems like I was using a different command and things where working. So, I'm using:
>
>>
>
>> svn checkout http://idl-coyote.googlecode.com/svn/trunk/coyote E:\Where_I_Put_My_Stuff_On_My_PC
>
>>
>
>> Now the question is: Should I use the address:
>
>> http://idl-coyote.googlecode.com/svn/tags/coyote/coyote_libr ary_6.0
>
>> or
>
>> http://idl-coyote.googlecode.com/svn/trunk/coyote
>
>>
>
>> I have implemented this operation in my task scheduler not to forget checking for updates.
>
>
>
> No, you are doing things exactly right. :-)
>
>
>
> You start your day the way I do. (Of course, we have good and bad days,
>
> but hopefully more good than bad.) Paul wants a "stable" release. I'm
>
> never sure exactly what that means, because I update these files
>
> frequently (at least once a week and sometimes several times a day).
>
> But, if a few days to go by and I haven't made any changes and Coyote
>
> remembers to remind me, I make a tagged release.
>
>
>
> I do try very hard to have the main repository in good shape at the end
>
> of every day. I'm not perfect, but my score is pretty high.
>
>
>
> I know it annoys people to have a lot of these files "retired". But, it
>
> is a lot of work to get all the documentation changed over to the IDLDOC
>
> style that I can have on my web page. I do it a little at a time now,
>
> and only when I find I am using a particular program. Name space is
>
> getting crowded, and I would like to have all my programs with the "cg"
>
> prefix. Eventually, I might get there. When I do make a change, I make
>
> sure all my Library files reflect the change and all the articles on my
>
> web page reflect the change. This is a BIG job, which is another reason
>
> I'm not anxious to do it often. Even a simple change to a routine that
>
> is not used much takes an hour or so to effect. Most changes take most
>
> of an afternoon. Mistakes can be made. I typically wait a couple of days
>
> to make a tagged release after a major upset. I've learned the hard way
>
> to test documentation headers before I commit the files. :-)
>
>
>
> Cheers,
>
>
>
> David
>
> --
>
> David Fanning, Ph.D.
>
> Fanning Software Consulting, Inc.
>
> Coyote's Guide to IDL Programming: http://www.idlcoyote.com/
>
> Sepore ma de ni thue. ("Perhaps thou speakest truth.")
Hi David,
thank for your effort. I hope you understand that I wasn't criticizing, rather unsure if I was getting things right. I'm a lone programmer that uses the word "fork" only at lunch time and subversions in my world are mostly subdirectories. That's so much for my ignorance.
I'm grateful that I can use your library and have no problems updating my software to the "cg" changes. It takes me for sure less than it does for you (not because of efficiency, but because of the total nr of lines and dependencies) and if you compare that time to the time I save by using you library... well... then the ratio "cg-update"-to-"cg-gain" is a very very small one and I'm happy to invest time in "cg-updates".
Thanks.
Helder
|
|
|
|
| Re: Coyote Library Updates [message #87381 is a reply to message #87373] |
Wed, 29 January 2014 08:22 |
Paul Van Delst[1]
Messages: 1157
Registered: April 2002
|
Senior Member |
|
|
Hello,
On 01/28/14 15:18, David Fanning wrote:
> Helder writes:
>
>> given the fact that I have no idea what is happening when I daily
>> execute my svn checkout, it seems like I was using a different command
>> and things where working. So, I'm using:
>>
>> svn checkout http://idl-coyote.googlecode.com/svn/trunk/coyote E:\Where_I_Put_My_Stuff_On_My_PC
>>
>> Now the question is: Should I use the address:
>> http://idl-coyote.googlecode.com/svn/tags/coyote/coyote_libr ary_6.0
>> or
>> http://idl-coyote.googlecode.com/svn/trunk/coyote
>>
>> I have implemented this operation in my task scheduler not to forget checking for updates.
>
> No, you are doing things exactly right. :-)
>
> You start your day the way I do. (Of course, we have good and bad days,
> but hopefully more good than bad.) Paul wants a "stable" release. I'm
> never sure exactly what that means, because I update these files
> frequently (at least once a week and sometimes several times a day).
I want something that I can tell other people about. E.g. "before you
can use this software I gave you, you need to install vX.Y.Z of the
coyote library. Here's the URL..."
The tag specifies that release snapshot. It specifies it today. And it
specifies it a year from now. However, the trunk, sans a specific,
non-people-friendly revision number, is whatever the latest version that
has been committed (which may or may not work right. You're very good,
David, but, as you say, not poifect :o)
> But, if a few days to go by and I haven't made any changes and Coyote
> remembers to remind me, I make a tagged release.
>
> I do try very hard to have the main repository in good shape at the end
> of every day. I'm not perfect, but my score is pretty high.
>
> I know it annoys people to have a lot of these files "retired". But, it
> is a lot of work to get all the documentation changed over to the IDLDOC
> style that I can have on my web page. I do it a little at a time now,
> and only when I find I am using a particular program. Name space is
> getting crowded, and I would like to have all my programs with the "cg"
> prefix. Eventually, I might get there. When I do make a change, I make
> sure all my Library files reflect the change and all the articles on my
> web page reflect the change. This is a BIG job, which is another reason
> I'm not anxious to do it often. Even a simple change to a routine that
> is not used much takes an hour or so to effect. Most changes take most
> of an afternoon. Mistakes can be made. I typically wait a couple of days
> to make a tagged release after a major upset. I've learned the hard way
> to test documentation headers before I commit the files. :-)
It's hard work maintaining software. "Eight is a lot of legs, David"
ha ha.
cheers,
paulv
|
|
|
|
| Re: Coyote Library Updates [message #87395 is a reply to message #87381] |
Thu, 30 January 2014 12:41 |
David Fanning
Messages: 11724
Registered: August 2001
|
Senior Member |
|
|
Paul van Delst writes:
> It's hard work maintaining software. "Eight is a lot of legs, David"
I had to have my go-to guy, Dick Jackson, figure this out for me! I
never would have understood it on my own, mostly because after all these
years I still have to call the kids to come over and get the DVD going
for me. (Too many friggin' remotes!) I guess maybe I watch one movie a
year. I *have*, however, seen this movie, but I didn't remember the
line. :-(
I'm not a total nerd, though. I'm pretty sure I have all the dialog in
the Princess Bride and Butch Cassidy and the Sundance Kid committed to
memory. "You idiot, the *fall* is going to kill you!" ;-)
Cheers,
David
--
David Fanning, Ph.D.
Fanning Software Consulting, Inc.
Coyote's Guide to IDL Programming: http://www.idlcoyote.com/
Sepore ma de ni thue. ("Perhaps thou speakest truth.")
|
|
|
|
comp.lang.idl-pvwave archive
Members
Search
Help
Login
Home
