Work at SourceForge, help us to make it a better place! We have an immediate need for a Support Technician in our San Francisco or Denver office.

Close

#21 GDL documentation, help, contributing

closed
nobody
None
5
2011-04-17
2006-10-16
Paul
No

Hi,

Just short intro: I am studying mathematics in
Darmstadt, Germany and this semester I am doing some
courses about image processing/correction. I heard
first about the language IDL and as I don't want to use
commercial software, if not necessary, i searched for
an open source clone... and I found one.

The problem is that it's very complicated to be able to
use GDL without beeing familiar with IDL. How do I call
files? What is the difference between @file, .r file,
.c file? Is there any place where those things (like
.r, .c and so on) are documented? How do I recompile a
file? Where are the compiled files saved?
And so on.

I am spending hours trying to read the C++ code, trying
out how GDL reacts, try & failure. I think this are all
simple, very simple things if you know how GDL work.

Well, I am no C++ crack, but I think at least
contributing a little bit of documentation would be
good for GDL. There is nothing, is there? Some Mailing
list? Wiki? IRC? FAQ? For new users some documentation
would be more helpful then new features, I think.

Do you have some url/text to read? Should I ask you
questions per mail or per sourceforge tracker? What do
you prefer? And which mail? Would be great if you had a
little bit of time to answer my questions. I will write
some kind of GDL intro/user guide then.

Regards
Paul.

Discussion

  • Joel Gales
    Joel Gales
    2006-10-17

    Logged In: YES
    user_id=958613

    Paul,

    Because GDL is a clone of IDL we rely informally on IDL
    documentation, some of which can be found on the web. See
    for example:

    http://vis.lbl.gov/NERSC/Software/idl

    for a particularly complete set of guides.

    Not everything in IDL is supported in GDL, but if not then
    this support can be requested.

    We, of course, would appreciate any documentation you would
    be willing to provide.

    Regards,

    Joel

     
  • Paul
    Paul
    2006-10-17

    Logged In: YES
    user_id=1023203

    Hi Joel,

    Thanks for you reply. Yes, I know this and the IDL
    documentation works fine for programming in GDL.

    The point is that I spent hours finding out how to run and
    compile in GDL. I said it yet -- I touched IDL only once in
    the university, so I have no idea how it works. I just
    pressed Strg+F5 and F5 to compile and run an file.

    Imagine someone like me after installing successfully GDL
    sitting there, trying to find out how to compile and run
    files. I thought that .COMPILE und .RUN where not
    implemented because I first started the commands without
    argument, just to test them. And I didn't manage it to
    recompile a function I build. Then, there were an error with
    a while ... do begin ... endwhile and until I find out that
    this error was caused because I called the file with an @...
    I know, All my fault, I did the error somewhere else (I think).

    But I want to use GDL now and I want other people to know
    that there is an alternative for IDL, a free one. So I'll
    try to write some Intro-Howto. Installing, calling files,
    etc. Perhaps some differences to IDL. I won't do it this
    week, next week I am not at home, but in two, three weeks
    I'll start to write it. If I have questions I'll ask them
    here, ok? As I am not so good reading C++ code... ;-)

    Regards
    Paul.

    P.S.: Is there any possibility to display line numbers in
    the error messages to debug?

     
  • Sven Geier
    Sven Geier
    2006-10-29

    Logged In: YES
    user_id=152543

    I slapped together the
    quickest-and-dirtiest-piece-of-documentation you've ever
    seen and put it here:

    http://sgeier.net/tools/GDL-intro-oct-06.pdf

    I'd call it "GDL for real programmers" as it merely mentions
    (but by no means explains) what I consider the most
    important aspects of GDL on ought to mention to someone
    who's "kinda starting out". I'll happily expand on it and/or
    contribute it to a "GDL documentation project" when and if
    such a thing ever happens... ;)

     
  • Alain C.
    Alain C.
    2007-02-13

    Logged In: YES
    user_id=1418043
    Originator: NO

    To learn how to compile GDL, if you read french, you can use this document
    http://aramis.obspm.fr/~coulais/IDL_et_GDL/memo_GDL0.8.11.html
    to learn how to compile from scratch GDL but also some other mandatory libraries like plplot.
    With some skill, only the blue boxes are useful. Take care that the link to the TGZ is old, now.

    I don't plan to translate it to english. I am desapointed with such a document :
    -- some people read it but don't take car of the details (famous known bugs with old GCC in FC)
    -- some people with good skills read it but do not follow the exact syntax --> pbs ...
    -- some people dont have the skills to do it

    At the end, the result : GDL does not work. In fact, they means: "I don't know how to compile it" or
    "plplot does not compile on my computer" ...

    --> we need RPM and pre-compiled GDL packages as frequently as possible.

     
  • Alain C.
    Alain C.
    2007-02-13

    Logged In: YES
    user_id=1418043
    Originator: NO

    To learn how to compile GDL, if you read french, you can use this document
    http://aramis.obspm.fr/~coulais/IDL_et_GDL/memo_GDL0.8.11.html
    to learn how to compile from scratch GDL but also some other mandatory libraries like plplot.
    With some skill, only the blue boxes are useful. Take care that the link to the TGZ is old, now.

    I don't plan to translate it to english. I am desapointed with such a document :
    -- some people read it but don't take car of the details (famous known bugs with old GCC in FC)
    -- some people with good skills read it but do not follow the exact syntax --> pbs ...
    -- some people dont have the skills to do it

    At the end, the result : GDL does not work. In fact, they means: "I don't know how to compile it" or
    "plplot does not compile on my computer" ...

    --> we need RPM and pre-compiled GDL packages as frequently as possible.

     
    • status: open --> closed