[Laszlo-checkins] r7128 - openlaszlo/trunk/WEB-INF/lps/schema

[hqm@openlaszlo.org]

Author: hqm
Date: 2007-11-05 05:20:01 -0800 (Mon, 05 Nov 2007)
New Revision: 7128

Modified:
   openlaszlo/trunk/WEB-INF/lps/schema/lfc.lzx
Log:
Change 20071104-hqm-0 by hqm at IBM-2E06404CB67 on 2007-11-04 21:44:46 EST
    in /cygdrive/c/users/hqm/openlaszlo/trunk
    for http://svn.openlaszlo.org/openlaszlo/trunk

Summary: workaround to get rid of warning when 'apply' is overridden

New Features:

Bugs Fixed: LPP-5042

Technical Reviewer: ptw
QA Reviewer: jcrowley
Doc Reviewer:

Documentation:

Release Notes:

Details:

See bug report LPP-5042


    

Tests:
compile

example/components/style_example.lzx, and should not  see this compiler warning anymore:
lz/windowpanel.lzx:259:88: In element 'state' attribute 'apply' is overriding parent class attribute which has the same name but type: method





Modified: openlaszlo/trunk/WEB-INF/lps/schema/lfc.lzx
===================================================================
--- openlaszlo/trunk/WEB-INF/lps/schema/lfc.lzx	2007-11-05 12:09:51 UTC (rev 7127)
+++ openlaszlo/trunk/WEB-INF/lps/schema/lfc.lzx	2007-11-05 13:20:01 UTC (rev 7128)
@@ -25,7 +25,12 @@
   <method name="isPrototypeOf" override="false"/>
   <method name="toLocaleString" override="false"/>
   <method name="prototype" override="false"/>
-  <method name="apply" override="false"/>
+  <!-- 
+   'apply' is ambiguous because <state> is
+   using it for both a method and an attribute. Just omit it from
+   the declarations for now.
+  <method name="apply" override="false"/> 
+  -->
   <method name="call" override="false"/>
 </interface>
 
@@ -504,8 +509,10 @@
 
 <interface name="state" extends="node">
   <!-- This is unfortunately both a setter attribute AND a method. No
-       real nice way to represent that. -->
-  <method name="apply" override="true" />
+       real nice way to represent that.
+   -->
+  <attribute name="apply" override="true" />
+
   <!-- If pooling is true, views that are created by the state are not
        destroyed when the state is removed - instead they just act as
        if they were by sending the onremovesubview event and setting