[ome-devel] Access settings from importer gui

[Curtis Rueden]

Hi Christoph,

> An alternative is to implement a custom dialog for the reader. I was
> hesitating with that, since it will interfere with the API and,
> perhaps, leads to problems in headless mode!?

If you really care about issues like that, I would encourage you to get
involved in the SCIFIO [1] project, which is the flagship image I/O library
for ImageJ2 [2]. One of ImageJ2's design goals is to be fully usable
headless. There are tutorials available for SCIFIO [3], but the design is
still in beta and needs more iterations before it will be complete. Feel
free to write to the SCIFIO mailing list [4] with any questions or ideas.

Regards,
Curtis

[1] http://imagej.net/SCIFIO
[2] http://imagej.net/ImageJ2
[3] https://github.com/scifio/scifio-tutorials
[4] http://scif.io/mailman/listinfo/scifio


On Thu, Jul 17, 2014 at 4:19 AM, Christoph Sommer <
christoph.sommer at imba.oeaw.ac.at> wrote:

>  Hi Curtis,
>
>
> That's what the MetadataLevel is for. For example, the BMPReader only
> populates optional metadata when the MetadataLevel is set to a value higher
> than MetadataLevel.MINIMUM:
> However, the ImageJ plugin always sets the metadata level higher than
> MINIMUM. So while your reader can respect that value, it won't really save
> any time at the ImageJ level to do so.
>
> Yes. I was looking into the MetadataLevels enums. But, as you wrote, the
> level is always set to "All" using the importer GUI.
>
> An alternative is to implement a custom dialog for the reader. I was
> hesitating with that, since it will interfere with the API and, perhaps,
> leads to problems in headless mode!?
>
> Cheers,
> Christoph
>
>
>
>
>
>  Regards,
> Curtis
>
>
> On Wed, Jul 16, 2014 at 8:41 AM, Christoph Sommer <
> christoph.sommer at imba.oeaw.ac.at> wrote:
>
>> Hey Mellisa,
>>
>>
>>  For what specifically are these settings needed in your reader?  If we
>>> know the use case, we might be able to suggest an alternative.
>>>
>>  In my reader it takes quite some time to extract the ROIs (data may
>> contain long time-lapse...). Of course, I would try to avoid reading the
>> ROIs in, when the user actually just wants to look at the raw pixel data
>> (i.e. "Display ROIs" not checked)
>>
>> Cheers,
>> Christoph
>> PS: thanks for you prompt reply! :)
>>
>>
>> _______________________________________________
>> ome-devel mailing list
>> ome-devel at lists.openmicroscopy.org.uk
>> http://lists.openmicroscopy.org.uk/mailman/listinfo/ome-devel
>>
>
>
>
> _______________________________________________
> ome-devel mailing list
> ome-devel at lists.openmicroscopy.org.uk
> http://lists.openmicroscopy.org.uk/mailman/listinfo/ome-devel
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openmicroscopy.org.uk/pipermail/ome-devel/attachments/20140717/dfe5ee7a/attachment.html>