xsltforms-support

[Xsltforms-support] img within xf:trigger

[christophe g. <chr...@e-...>]

Hi all
is there a way to properly render a structure like this one?

<xf:trigger class="tree-icon" appearance="minimal" ref="current()/@l">
            <img  class="tree-icon elbow-line"
src="/db/e-Smile/system/resource/images/s.gif"/>
</xf:trigger>

With the current release, the img stuff is not rendered at all. This
structure (trigger+img) can be pretty usefull in complex scenario - for
instance I use it to render a classic dynamic tree structure (with '+' and
'-' triggers to expand/collapse the tree.

A workaround seems to write it this way:
<xf:trigger class="tree-icon" appearance="minimal" ref="current()/@l">
       <xf:label>
            <img  class="tree-icon elbow-line"
src="/db/e-Smile/system/resource/images/s.gif"/>
       </xf:label>
</xf:trigger>

But this option is only a partial one (= img is rendered) as the xf:label
adds '*' (required) and 'x'(alert) symbols on the form.

Thanks
Christophs

-- 
Christophe Geiser, social entrepreneur
e-Smile, solutions in monitoring and information management
--

Re: [Xsltforms-support] img within xf:trigger

[COUTHURES A. <ala...@ag...>]

Hi Christophe,
> is there a way to properly render a structure like this one?
>
> <xf:trigger class="tree-icon" appearance="minimal" ref="current()/@l">
>             <img  class="tree-icon elbow-line" 
> src="/db/e-Smile/system/resource/images/s.gif"/>
> </xf:trigger>
>
> With the current release, the img stuff is not rendered at all. This 
> structure (trigger+img) can be pretty usefull in complex scenario - 
> for instance I use it to render a classic dynamic tree structure (with 
> '+' and '-' triggers to expand/collapse the tree.
>
> A workaround seems to write it this way:
> <xf:trigger class="tree-icon" appearance="minimal" ref="current()/@l">
>        <xf:label>
>             <img  class="tree-icon elbow-line" 
> src="/db/e-Smile/system/resource/images/s.gif"/>
>        </xf:label>
> </xf:trigger>
I prefer the mediatype approach. Can you test this ?

<xf:trigger class="tree-icon" appearance="minimal" ref="current()/@l">
       <xf:label>
            <xf:output  class="tree-icon elbow-line" 
value="'/db/e-Smile/system/resource/images/s.gif'" mediatype="image/*"/>
       </xf:label>
</xf:trigger>
>
> But this option is only a partial one (= img is rendered) as the 
> xf:label adds '*' (required) and 'x'(alert) symbols on the form.
I can't see that with a simple test case. Don't you have a binding on 
this attribute ?

-Alain

Re: [Xsltforms-support] img within xf:trigger

[COUTHURES A. <ala...@ag...>]

Christophe,
> The first one works quite well
The "geo" example you sent is a quite complex XForms document based on 
CSS and elaborated XPath expressions but I'm not sure that the Mozilla 
extension interprets them correctly:

When selecting every element with an @id at the main repeat, "continent" 
elements are selected. Because they don't have a @structure attribute, 
their names shouldn't be displayed...

About unwanted required and irrelevant icons, they are displayed because 
of inherited CSS classes forcing display.

-Alain

Re: [Xsltforms-support] img within xf:trigger

[christophe g. <chr...@e-...>]

Dear Alain
Thanks a lot for your answer - and for having taken time to look into this
matter.
Agreed, the form is a bit complex - and its core structure is already pretty
well rendered with xsltforms.

I like the idea of directly playing with instance data through a tree view
(and its an important part of some of my forms). I will therefore try to dig
further into the remaining details (e.g. icons rendering) when I have some
more time... but hopefully soon - except if you see a fundamental reason
preventing this to be achievable with xsltforms.

Wishing you an excellent day

Christophe



On Sun, Feb 7, 2010 at 10:34 PM, COUTHURES Alain <
ala...@ag...> wrote:

>  Christophe,
>
>  The first one works quite well
>
> The "geo" example you sent is a quite complex XForms document based on CSS
> and elaborated XPath expressions but I'm not sure that the Mozilla extension
> interprets them correctly:
>
> When selecting every element with an @id at the main repeat, "continent"
> elements are selected. Because they don't have a @structure attribute, their
> names shouldn't be displayed...
>
> About unwanted required and irrelevant icons, they are displayed because of
> inherited CSS classes forcing display.
>
> -Alain
>



-- 
Christophe Geiser, social entrepreneur
e-Smile, solutions in monitoring and information management
--