[Fwd: Re: XSLT Attribute to Element / Preventing Deletions?]

Hi

> 1) could someone tell how difficult it is to write XSLT-transformations
>    that convert specific tag-attributes to elements and back again? 
>    Or even better, does someone have a recipe for this?

one:

<xsl:template match="/xpath/path/to/@attribute">
<attribute>
	<xsl:value-of select="."/>
</attribute>
</xsl:template>

back:

<xsl:template match="/xpath/path/to/attribute">
	<xsl:attribute name="attribute">
		<xsl:value-of select="."/>
	</xsl:attribute>
</xsl:template>

did you mean that?

But we have to find a better solution for this anyway. With this "better
solution" a <xsl:value-of select="/path/to/@attribute"> should be enough
in the main xslt file without a need to convert the xml back and forth.

> 2) How could/should i prevent BXE from deleting "required" elements and/or
>    attributes? Basically I don't want a user e.g. erasing (in BXE-WYSIWYG-mode) 
>    the title in this structure:
> 
>     <list>
>         <title>sometitle</title>
>         <li>alksjd</li>
>         <li>alksjd</li>
>     </list>
> 
>     (bxe-attributes left out for convenience)
>     the title is content-editable and only the complete list or
>     single elements (<li/>) should be allowed to be deleted.

Unfortunately our current schema implementation can't handle this....
I'll think about a solution (I have one in my mind but i don't know if
it's feasible right now)

chregu



-- 
bx-editor-dev mailing list
[email protected]
http://lists.bitflux.ch/cgi-bin/listinfo/bx-editor-dev