<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">Which do you like "return" or "returns"? I'll make this change and fix the cast and retest.<div>I'd defer any other additions like naming return values: returns="done:Boolean".<br><div><div><br><div><div>On Oct 21, 2008, at 11:53 AM, P T Withington wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div>On 2008-10-21, at 11:45EDT, André Bargull wrote:<br><br><blockquote type="cite">Was it already decided how to declare return types in LZX? So, how to name the attribute which specifies the type? It's now named "type", any other proposals? Like "return" or "returns"?<br></blockquote><br>Yes: <a href="http://www.openlaszlo.org/pipermail/laszlo-dev/2008-February/013150.html">http://www.openlaszlo.org/pipermail/laszlo-dev/2008-February/013150.html</a><br><br>This is an API addition, so does not need to be vetted like a change, but I think I prefer "return" or "returns" over "type". I would even propose that you should be able to name the return value (purely for documentation purposes), e.g.:<br><br> <method name="update" args="when:Date" returns="done:Boolean><br><br><blockquote type="cite">Any cast needs to be: "foo cast Bar", "Bar(foo)" is only available in plain AS3 code, in cross-runtime code the latter form is a function call. (That's why DHTML broke for you.)<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">We should consider to drop the lowercase "type"-declarations for <attribute> and instead prefer the JavaScript alternatives, because you need to use the Javascript-form anywhere else (typing for function arguments, variables, function return types).<br></blockquote><br>I agree. Originally, we used lower-case in LZX because a) it looked pretty, and b) it is meant to match XML standards. But this means we have to map from the LZX/XML type to the appropriate Javascript type (and document separately the LZX and JS API's of every public class. It's made especially messy by JS's bi-cameral types (boolean/Boolean, etc.) We are probably stuck with the XML types for backwards compatibility, but we should encourage using JS types as we go forward.<br><br><br></div></blockquote></div><br><div> <span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0; "><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; "><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; "><span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; "><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div><br class="Apple-interchange-newline">--</div><div><br>Don Anderson<br>Java/C/C++, Berkeley DB, systems consultant<br><br>voice: 617-547-7881<br>email: <a href="mailto:dda@ddanderson.com">dda@ddanderson.com</a><br>www: <a href="http://www.ddanderson.com/">http://www.ddanderson.com</a><br></div></div></span></span><br class="Apple-interchange-newline"></div></span></div></span><br class="Apple-interchange-newline"> </div><br></div></div></div></body></html>