| Re: What I Want for Christmas. [message #33392 is a reply to message #33339] |
Sat, 21 December 2002 01:13  |
R.Bauer
Messages: 1424
Registered: November 1998
|
Senior Member |
|
|
JD Smith wrote:
> On Tue, 17 Dec 2002 23:56:54 -0700, David Fanning wrote:
>
>> Folks,
>>
>> While I am wenging and moaning about IDL projects, I'll just say that I
>> almost always have the project code mirrored by something that looks
>> nearly identical to it in my Code Management System (I use Perforce).
>>
>> The thought has occurred to me (as it has occurred to others) that it
>> would be WONDERFUL if the IDL project could do the code management task
>> too. (Isn't that part of what a "project" is, after all?)
>>
>>
>
> I hate to do it, but.... Emacs has several lovely built-in version
> control commands. I use CVS, but several others are supported (RCS, etc.)
> by the "vc" mode, bundled with Emacs. In an IDLWAVE buffer, I use all its
> wonderful features, and then when it's time to check in a my changes: C-x
> C-q, up pops a little buffer in which I can enter a log of the changes,
> and then C-c C-c submits and checks-in. I can pop-up a color-annotated
> buffer with the codes coded by change date and the person who submitted
> the change. I can quickly show the difference (as in `diff') of the
> current code from that in the repository, or any specified revision. I
> can tag one or more files with C-x v s, and much more. There's even a
> menu so you don't have to remember all these keys. And if I'm using CVS,
> the PCL-CVS mode lets me do many operations on entire directories (aka
> "projects") at a time. I realize the constant Emacs proselytizing here
> smacks of religious fanaticism, but there are good reasons...
>
> JD
Dear JD
we like very much emacs and all the handy tools. A few days ago I got a
lesson about kde/qt programming with kdevstudio for crosscompiling.
I can't understand why a commercial closed source product like idl did have
such a (I don't have the right word) development environment.
A lot of free developer tools are much more comfortable. And the kde
projects shows, that it is no problem to have for example color coded text
or cvs archive. I believe I better did not a comparison of the qt designer
and the idl widget designer.
The main problem of the idl editor or the widgets is that's they are
programmed in motif.
With the experience I have in idl there is no need for me to have a special
kind of editor to write my sources. But for a beginner each kind of
development environment helps a lot in learning the language. Most windows
IDL programmers which have switched to linux in our institute prefer the
idlde but on linux it is black on grey. Sometimes they use a vmware to get
color coded idlde. Some of them switched to emacs because of the available
environemt. It is so easy to check out an older version from the repository
or to compare two files. And the autocompletion and and and.
greetings
Reimar
--
Forschungszentrum Juelich
email: R.Bauer@fz-juelich.de
http://www.fz-juelich.de/icg/icg-i/
============================================================ ======
a IDL library at ForschungsZentrum Juelich
http://www.fz-juelich.de/icg/icg-i/idl_icglib/idl_lib_intro. html
|
|
|
|
comp.lang.idl-pvwave archive
Members
Search
Help
Login
Home
