[Octave-bug-tracker] [bug #58633] [octave forge] (image + dicom) move reference of dicom functions from image to dicom package

[Hartmut]

URL:
  <https://savannah.gnu.org/bugs/?58633>

                 Summary: [octave forge] (image + dicom) move reference of
dicom functions from image to dicom package
                 Project: GNU Octave
            Submitted by: hardy
            Submitted on: Sat 20 Jun 2020 05:05:22 PM UTC
                Category: Octave Forge Package
                Severity: 3 - Normal
                Priority: 5 - Normal
              Item Group: Documentation
                  Status: None
             Assigned to: None
         Originator Name: 
        Originator Email: 
             Open/Closed: Open
                 Release: 5.2.0
         Discussion Lock: Any
        Operating System: Any

    _______________________________________________________

Details:

Currently the dicom related functions are still referenced in the image
package. But since some time, there is now also the dicom package, that
actually does contain these functions.

Here is what happens currently: (Octave 5.2.0, image 2.12.0, dicom 0.3.0)


>> pkg unload image
>> dicomread('foo')
warning: the 'dicomread' function belongs to the image package from Octave
Forge
which you have installed but not loaded.  To load the package, run 'pkg
load image' from the Octave prompt.
   [...]

>> pkg load image
>> dicomread('foo')
warning: the 'dicomread' function belongs to the image package from Octave
Forge
but has not yet been implemented.
   [...]


There seem to be (at least) two lists of all Octave functions somewhere (I do
not know where). Octave core seems to "know" that dicomread belongs to the
image package. And also the image package seems to "know" that the dicomread
function should belong to it.

Shouldn't we change this association to the dicom package? The function (and
all the other dicom related functions IS imlemented there). And I I understood
correct, there are no plans to move those dicom related functions into the
image package. So I would like to guide the user in a more helpful way, and
tell him staight away: Please install and load the dicom package to get those
functions!

Any opinions on this?

Where are the (function listing) files in the source, that we would need to
change to make this happen? (Is this really necessary to do in Octave core AND
in the image package sources?)




    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/bugs/?58633>

_______________________________________________
  Message sent via Savannah
  https://savannah.gnu.org/