[ome-devel] Default FontSize in ROI's text

[Luca Lianas]

Hi Ola,
first of all, thanks for the code.
What we want to do with "custom" labels is to add a mechanism that can be
used to add text to the ROIs without the need to save them within OMERO,
these labels can be saved into an external database (Moodle's for example)
or embedded into JS, HTML or CSS.
In this way we want to implement features like:

   - multi-language support for text in ROIs
   - context related labels (I can use the same image with the same ROIs in
   different contexts like a lecture or a test)

What we want to obtain is something that will require the usage of
OMEROinsight only to import images and create ROIs, other elements like
text and extra ROIs (like markers used by the students to answer to
questions that require a direct interaction with the image) will be managed
using an external system as data storage layer and integrated using your
web viewer.
Actually we are still investigating on which features we want to provide
but the big plan is to add as many features as possible to the web viewer
in order to make easier to us (and eventually to other developers) to add
new features that can be used to embed OMERO and to interact with it.

Cheers,
Luca

2015-02-05 10:52 GMT+01:00 Aleksandra Tarkowska (Staff) <
A.Tarkowska at dundee.ac.uk>:

>   Hi Luca,
>
>  The code Insight determines the default font size according to the
> resolution level is
> https://github.com/jburel/openmicroscopy/commit/6eba7b598ebf2068c88bc280ab06316257353e81#diff-f3bb53eab5e729fb8a7cf17503b3d87eR220
>
>  Could you please tell us more what exactly custom labels are and why you
> need to store them out of OMERO?
>
>  Kind regards
> Ola
>
>   From: Luca Lianas <lianas at crs4.it>
> Reply-To: OME External Developer List <
> ome-devel at lists.openmicroscopy.org.uk>
> Date: Wed, 4 Feb 2015 21:45:41 +0100
> To: "<ome-devel at lists.openmicroscopy.org.uk>" <
> ome-devel at lists.openmicroscopy.org.uk>
> Subject: [ome-devel] Default FontSize in ROI's text
>
>  Hi everyone,
> recently I started working on OMERO's web viewer in order to add some
> features that we are going to use in order to develop a few module for
> Moodle (https://moodle.org/?lang=en) that will enable the usage of OMERO
> images within courses material and exams (I already pushed a first pull
> request related to this task
> https://github.com/openmicroscopy/openmicroscopy/pull/3432).
> One of the features I am working on is to add the possibility to define
> custom labels that will be associated to the ROIs and that won't be saved
> within OMERO's database.
> The task is quite simple: if the ROI has already an associated text (I'll
> just have to replace the default label with the new one), things get a
> little more complicated if I have to create a new text because I need to
> define all the font-related properties; in particular I need to calculate
> the proper FontSize with respect to image's sizes.
> I noticed that OMEROinsight automatically calculates and assign the
> FontSize property to ROIs' text, how does it work? I just want to reproduce
> the same code using Javascript in order to make text defined using OMERO's
> tools and text defined by external app look the same.
> Thanks a lot,
>
>  Luca
>
>  --
>  Luca Lianas
> Data Fusion - Distributed Computing
> CRS4 - Centro di Ricerche, Sviluppo e Studi Superiori della Sardegna
> POLARIS, Edificio 1, 09010 PULA (CA - Italy)
>
>
> Phone: 070/9250266
> Email: luca.lianas at crs4.it
>
>    _______________________________________________ ome-devel mailing list
> ome-devel at lists.openmicroscopy.org.uk
> http://lists.openmicroscopy.org.uk/mailman/listinfo/ome-devel
> The University of Dundee is a registered Scottish Charity, No: SC015096
>
> _______________________________________________
> ome-devel mailing list
> ome-devel at lists.openmicroscopy.org.uk
> http://lists.openmicroscopy.org.uk/mailman/listinfo/ome-devel
>
>


-- 
Luca Lianas
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openmicroscopy.org.uk/pipermail/ome-devel/attachments/20150205/17a98c5b/attachment.html>