I would prefer that to the previous virtual folder solution.
This would make path resolution much simpler and get rid of all the
complex path resolution stuff that would have to be done with the
virtual folder solution.
Howard Lewis Ship wrote:
I'll try and find it later.
A thought that occurs would be to copy what Flex does, and leverage
namespaces to reference components inside libraries.
Thus
<html xmlns:myllib="tapestry-lib:mylib">
<mylib:Foo/>
Thoughts?
On 10/3/07, Hugo Palma <[EMAIL PROTECTED]> wrote:
So if the component name is "folder1/mycomponent" the way to do it would be:
<div t:type="mylib/folder1/mycomponent"/> or <t:myliv.folder1.mycomponent/>
?
I can't find the test class where i can check this. Can you please point
me to it ?
Thanks....
Howard Lewis Ship wrote:
I think there are examples in the test suite.
Basically, libraries are mapped to a virtual folder.
Thus <div t:type="mylib/mycomponent"/> or <t:mylib.mycomponent/>.
On 10/2/07, Hugo Palma <[EMAIL PROTECTED]> wrote:
I can't find any docs on this and i can't get it to work.
Thanks...
