[binarycloud-dev] bc:href

[<bin...@li...>]

Hi All,

i'm currently implementing the BccHrefCompiler. What do you think about this
format:

<bc:href>
	<!-- the link itself, required -->
	<href>/archive/mp3/any_document.mp3</href>

	<!--
	the content, can be image, string (see blow),
	required
	-->
	<content>Testlink</content>

	<!--
	internal link = usedocroot
	default/optional
	-->
	<internal>true</internal>

	<!--
	only used if internal equals false
	default/optional
	-->
	<protocol>http</protocol>

	<!- these are translated 1:1, optional-->
	<attributes>
		<target>_BLANK</target>
		<onmouseover>popup()</onmouseover>
		<onmouseout>popdown()</onmouseout>
	</attributes>
</bc:href>


With images from repository:
<bc:href>
	<href>/test.php</href>
	<content>
		<bc:img>
			<id>bcFire</id>
		</bc:img>
	</content>
</bc:href>

With language strings:
<bc:href>
	<href>/test.php</href>
	<content>
		<bc:string>
			<id>desc.mp3link</id>
		</bc:string>
	</content>
</bc:href>

Using markup:

<bc:href>
	<href>/test.php</href>
	<content>
		<bc:markup>
			<img src="hello.gif">
			<br>A Link<br>
		</bc:markup>
	</content>
</bc:href>


Alternatively, using the UrlRepository where all the tags can also be
present (bc:image, bc:markup etc):

<bc:href>
	<id>href.menu.home</id>
</bc:href>


The prefered method would be to use the url repository throughout (promotes
readbility and administration), but nevertheless if <id> is not present it's
assumed as a direct entry (no repository lookup).


Andi