Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cocoon.apache.org
Received-SPF: pass (herse.apache.org: domain of riceyeh@gmail.com designates
 64.233.166.179 as permitted sender)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
        s=beta; d=gmail.com;
        h=received:message-id:date:from:to:subject:mime-version:content-type;
        b=K+nB0fbqKH4SKZ03uEslU7Y7sVOcesRn9nKrq9OW4DAN5YMPJwoVIwCKiEVBaE5Dv/iRvjm+oNfGOWf82vz/w2EGoYn6CFLTxPAlyRcxVEQu9PToOjDDf+m11AGjMtSu8ezQj25066wK/utCJ7MTUMNYxCDyfL3gDhmf+Cp1QjY=
Message-ID: <47f71d940611110916w39201098s7ad4cba5b74812f3@mail.gmail.com>
Date: Sun, 12 Nov 2006 01:16:01 +0800
From: "Rice Yeh" <riceyeh@gmail.com>
To: dev@cocoon.apache.org
Subject: call a function not in global object in <map:call >
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_Part_685_24364564.1163265361548"

------=_Part_685_24364564.1163265361548
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

Hi,
  It seems for now the function attribute in <map:call> must be a function
in the global object. I think it might be better if this function could be
within a scope object because our project groups all javascript objects like
java packages (or just like what dojo does). There are more javascript codes
than java codes in our project, so goruping them in different naming spaces
is needed. Cocoon itself is a good environment for easily javascript coding
at the server side with its flowscript and continuation. However, it seems
not that care about naming space at javascript code itself. Maybe some ideas
from dojo can be borrowed here. Like dojo has dojo naming space, cocoon has
cocoon naming space, and within cocoon, there are cocoon.flow,
cocoon.flow.continuation,...

Rice

------=_Part_685_24364564.1163265361548
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

Hi,<br>&nbsp; It seems for now the function attribute in &lt;map:call&gt; must be a function in the global object. I think it might be better if this function could be within a scope object because our project groups all javascript objects like java packages (or just like what dojo does). There are more javascript codes than java codes in our project, so goruping them in different naming spaces is needed. Cocoon itself is a good environment for easily javascript coding at the server side with its flowscript and continuation. However, it seems not that care about naming space at javascript code itself. Maybe some ideas from dojo can be borrowed here. Like dojo has dojo naming space, cocoon has cocoon naming space, and within cocoon, there are 
cocoon.flow, cocoon.flow.continuation,...<br><br>Rice<br>

------=_Part_685_24364564.1163265361548--