The original example had more data points. But, the spirit of the example can be rewritten using <gridcolumn> as,

<canvas debug="true">
  <dataset name="weather">
    <forecast>
<day label="TODAY" imageurl="http://www.srh.noaa.gov/ifps/text/images/hi_shwrs70.jpg";
desc="Rain Likely" temp="Hi  60&#176;F "/>
<day label="Tonight " imageurl="http://www.srh.noaa.gov/ifps/text/images/nwind.jpg";
desc="Breezy " temp="Lo  34&#176;F "/>
    </forecast>
  </dataset>

  <grid bgcolor0="0xAA0000" bgcolor1="0x880000"
        datapath="weather:/" contentdatapath="forecast/day">
    <gridcolumn>Label<text datapath="@label"/></gridcolumn>
    <gridcolumn width="400">Url<text datapath="@imageurl"/></gridcolumn>
    <gridcolumn>Description<text datapath="@desc"/></gridcolumn>
    <gridcolumn>Temperature<text datapath="@temp"/></gridcolumn>
  </grid>

</canvas>


The original version looks like:

<canvas debug="true">
  <dataset name="weather">
    <forecast>
<day label="TODAY" imageurl="http://www.srh.noaa.gov/ifps/text/images/hi_shwrs70.jpg";
desc="Rain Likely" temp="Hi  60&#176;F "/>
<day label="Tonight " imageurl="http://www.srh.noaa.gov/ifps/text/images/nwind.jpg";
desc="Breezy " temp="Lo  34&#176;F "/>
    </forecast>
  </dataset>

  <grid bgcolor0="0xAA0000" bgcolor1="0x880000"
          datapath="weather:/" contentdatapath="forecast/day" />
</canvas>




There are 2 issues here:

1) Henry is right (again!):  XML attributes do not have an order, so
the example is just broken.  To make the column order the same across
platforms, you would have to bind the columns to nodes (which are
ordered), not attributes; or, impose some ordering on the columns
(e.g., does grid have an option to specify its columns, rather than
intuiting them from the databinding?).  Diddling the runtimes to make
the column orders match is not the correct solution.

[DOC Guy: In fact, his would make a good documentation example,
showing the inherent unorderedness of XML attributes and how to deal
with that, assuming there is a way to specify grid column order.]

2) I do see one more deferred event handling in the DHTML case than
in the SWF case.  This may be indicative of another problem.

I don't know about your theory of SWF node instantiation and the
other bugs, but I do not believe it is relevant here.

On 2007-01-26, at 22:08 EST, Max Carlson wrote:

> So, it sounds like swf is instantiating backwards in legals, when
> compared to trunk.
>
> I remember way back in the day we had to reverse the view init
> order of children in SWF to get things to look right.  We no longer
> do this, which could explain the behavior.
>
> This also sounds like it could be the issue underlying these bugs:
> LPP-3331 - Flash: Components Menu example is missing openMenu right/
> below/top LPP-3274 - Laszlo in 10 scripting->method example not
> showing 5
> yellow boxes on startup
>
> We need to make sure swf is consistent between trunk and legals,
> and dhtml and swf are consistent in legals.
>
> -Max
>
> Philip Romanik wrote:
>> Hi guys,
>> I'm looking into a jira bug (http://jira.openlaszlo.org/jira/
>> browse/LPP-3379) where the display order is reversed between swf
>> and dhtml. Is there anything I can do about the ordering? The
>> behavior of dhtml matches v3.3 (it displays data in the order it's
>> listed). It is reversed in swf. Here's an app that demonstrates it.
>> I think this issue came up a while back. Do either of you remember?
>> Thanks!
>> Phil
>> <canvas debug="true">
>>   <dataset name="weather">
>>     <forecast>
>>       <day label="TODAY" imageurl="http://www.srh.noaa.gov/ifps/
>> text/images/hi_shwrs70.jpg"
>> desc="Rain Likely" temp="Hi  60&#176;F "/>
>>       <day label="Tonight " imageurl="http://www.srh.noaa.gov/ifps/
>> text/images/nwind.jpg"
>> desc="Breezy " temp="Lo  34&#176;F "/>
>>     </forecast>
>>   </dataset>
>>   <grid bgcolor0="0xAA0000" bgcolor1="0x880000"
>>           datapath="weather:/" contentdatapath="forecast/day" />
>> </canvas>
>
> --
> Regards,
> Max Carlson
> OpenLaszlo.org

Reply via email to