Scott,

We'd like the option 2 (per your response above); where the user in
TBE would see the whole message.  Or at least some way of controlling
the entire message that is displayed to the user without having to
hover when hard returns exist.

Thanks,
Catrina

On Oct 15, 9:55 pm, Scott Henninger <shennin...@topquadrant.com>
wrote:
> Catrina;  Displaying attributes as text input for SPARQLMotion scripts
> in Ensemble, which I believe you are doing in this case,  is currently
> changing in Ensemble. This is in progress for the 3.2 release.  The
> most noticeable difference will be the SPARQLMotion player, which
> provides a uniform look for running scripts in Ensemble.
>
> It will also be the case that rdfs:comment for arguments will be used
> as the label in an input form instead of a property's rdf:label.  This
> provides for additional flexibility so properties can be reused as
> arguments with unique labels.
>
> The "hover feature" will be supported in 3.2.  Any label displayed in
> the form or SPARQLMotion player will pop-up a tooltip to display the
> full string when a mouse-over occurs.
>
> Returns in the values of rdfs:comment is supported as you outlined.
> However, by the following statement:
>
> <Ideally, we'd like the users to see the rdfs:label as is with the
> hard
>   returns.  Is this possible?>
>
> Are you suggesting that the desired display would 1) always show the
> entire string, with the returns, or that 2) the string only to the
> first return should be displayed and the rest when the user hovers
> over the label?
>
> -- Scott
>
> On Oct 15, 11:01 am, Catrina <catrina.pend...@thomsonreuters.com>
> wrote:
>
>
>
> > Just picking this up again since I have not received any response yet.
>
> > We're also experiencing issues where some scripts (seems like ones
> > that were created in TBC 3.0.1) allow the hover feature to display the
> > rest of the rdfs:label when hard returns exist.  Scripts originating
> > in TBC 3.1.0 or 3.1.1 do not seem to offer the hover feature.  Is this
> > a feature that was dropped?
>
> > The following shows an example property in n3 with hard returns in the
> > rdfs:label:
> > :options
> >       rdf:type rdf:Property ;
> >       rdfs:label """Enter desired option:
> >    1) Option Choice 1
> >    2) Option Choice 2
> >    3) Option Choice 3"""^^xsd:string ;
> >       rdfs:range xsd:string ;
> >       rdfs:subPropertyOf sp:arg .
>
> > When a script requiring this arg is executed in TBE, the user sees the
> > first line "Enter desired option:" of the rdfs:label.  If the script
> > originated in TBC 3.0.1, the user can hover the mouse over the "Enter
> > desired option:" text and the rest of the rdfs:label will appear
> > (showing 1, 2, and 3 options).  However, if the script originated in
> > TBC 3.1.0 or 3.1.1, the user will not see anything after "Enter
> > desired option:" regardless of hovering.
>
> > Ideally, we'd like the users to see the rdfs:label as is with the hard
> > returns.  Is this possible?
>
> > Thanks,
> > Catrina
>
> > On Sep 29, 10:42 am, Catrina <catrina.pend...@thomsonreuters.com>
> > wrote:
>
> > > Is it possible to display carriage returns in an rdfs:label for an
> > > sp:arg where the carriage returns will be displayed in Ensemble
> > > without having to hover over the text to view the full rdfs:label?
>
> > > Currently, if we placehardreturns in the rdfs:label for an sp:arg,
> > > we have to hover over the label in order to view the rest of the
> > > contents after thehardreturn.  Is it possible to display all of the
> > > label's contents without having to hover in Ensemble?
>
> > > Thanks,
> > > Catrina- Hide quoted text -
>
> - Show quoted text -
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"TopBraid Composer Users" group.
To post to this group, send email to topbraid-composer-users@googlegroups.com
To unsubscribe from this group, send email to 
topbraid-composer-users+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/topbraid-composer-users?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to