I reply to myself for if someone needs to do the same.... 


> 
> 1) Is this pattern feasible?
> 2) Shall I use the mixins aproach for doing this?
> 3) where can I found information to build up my javascript functions to
> embed the pagelink path?
> 4) how can I avoid the replication of javascript code that the loop
> produces. Something like embeding the script tag within <final></final>?
> 
> 

1) yes it is
2) not at all
3) still not sure....here and there
4) place the javascript in the container loop component instead of the
component although this migh look as to break encapsulation (your component
code is spread in two files) in fact you should think the container and the
contained components as a whole logical domain.

So in the container component:

 <script type="text/javascript" language="JavaScript">
         function pDetail(id) {
             
newwindow=window.open("${asset:context:}ProductDetail/"+id,"name","height=255,width=250,toolbar=no,directories=no,status=no,menubar=no,scrollbars=no,resizable=no");
              newwindow.moveTo(150,150);
              newwindow.focus();
                      return false;              
           }
 </script>

and the component template:

<div class="pDiv">
     # 
        PRODUCT DIV TEST
        <div><strong><em>${atext}</em></strong></div>
         ${asset:context:}images/cmi/${sourceimg}  
        END PRODUCT DIV TEST
         
    
</div>



The only thing that I found misterious was when training to get out the
context path to the page, I finally find out the ${asset:contex}, but I feel
it strange it's not an asset, I generally find difficult to get
comprehensive information on what how and where I can acces relevant
information when I writting a page or component. Any way solved 









-- 
View this message in context: 
http://www.nabble.com/T5-PopUp-Windows---JavaScript-tp17070425p17083883.html
Sent from the Tapestry - User mailing list archive at Nabble.com.


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to