Change change.Ud7vlXQzH.txt by ben <at> cooper.local /Users/ben/src/svn/
openlaszlo/branches/legals on 2006-09-30 17:22:00 PDT
Summary: Improve startup animation
New Features:
Bugs Fixed:
Technical Reviewer: minsky
QA Reviewer: (pending)
Doc Reviewer: (pending)
Documentation:
This change makes the startup sequence look right, but less fancy.
Instead of a load percentage indicator, this just shows a still image
(captured from the swf that had been used for loading) while the app
is loading. This change also tweaks the startup animations to be a
bit slower so we have a chance of seeing >1 frames of it in DHTML.
Release Notes:
Details:
Tests:
Files:
M demos/lzpix/data/canned_favorites.xml
M demos/calendar/calendar.lzx
M demos/calendar/loading.lzx

I didn't mean to include the change to demos/lzpix/data/
canned_favorites.xml. Please ignore that part of the patch.
On Sep 30, 2006, at 5:30 PM, Benjamin Shine wrote:
> Change change.Ud7vlXQzH.txt by ben <at> cooper.local /Users/ben/src/svn/
> openlaszlo/branches/legals on 2006-09-30 17:22:00 PDT
>
> Summary: Improve startup animation
>
> New Features:
>
> Bugs Fixed:
>
> Technical Reviewer: minsky
> QA Reviewer: (pending)
> Doc Reviewer: (pending)
>
> Documentation:
> This change makes the startup sequence look right, but less fancy.
> Instead of a load percentage indicator, this just shows a still
> image (captured from the swf that had been used for loading) while
> the app is loading. This change also tweaks the startup animations
> to be a bit slower so we have a chance of seeing >1 frames of it in
> DHTML.
>
> Release Notes:
>
> Details:
>

Well certainly you could not call getTextWidth 3 times. If the text
element is resizable, I believe that when you set the text it will
have its .width set. You could verify that .width == getTextWidth,
and if so, replace the call with an accessor.
It is possible that getTextWidth is from days gone by...
On 2006-09-30, at 21:14 EDT, Benjamin Shine wrote:
> Calendar does a whole bunch of text measurement. For instance in the
> monthtitle button:
> <method event="ontext">
> this.setX( Math.round( ( this.parent.width -
> this.getTextWidth())/2.0) - 2);
> this.setWidth (this.getTextWidth()+2);
> this.parent.monthtitleshdw.setWidth
> (this.getTextWidth()+2);
>
> </method>
> Can this all be replaced with something simpler and faster?
>
> On Sep 29, 2006, at 4:00 PM, Max Carlson wrote:
>
>> Comments:
>> * There is no x/yscaling in DHTML...
>>
>> * _x/yscale are flash-specific properties - you probably want to
>> read it out of the sprite as it'll be undefined here:
>> + var scale = "_" + xory + "scale";
>>

Centralized handling of fonts; instead of specifying fonts in many places all over the app, I specify fonts in the top-level views. We're now using Verdana 10 throughout. Made the buttons use bold fonts, to match old swf look.

Replaced custom vscrollbar with lz/scrollbar. Changed some positioning values from constraints to constant, when they actually would be constants.

Removed code for rotating arrows in tab-slider, since we just can't support rotation in DHTML.

Replaced basetabslider with tabslider, because tabslider seems to work; we don't need a custom tabslider.

Strange issue with in IE

Max Carlson <max <at> openlaszlo.org>
2006-10-01 06:45:44 GMT

When I try to run this in IE:
<canvas>
<view id="foo" width="560" height="1" bgcolor="0x394660"
oninit="Debug.write(this.sprite.__LZdiv)"/>
</canvas>
The view is way too tall - much larger than one pixel. For some reason
I can't understand, the clientHeight of the div is 19. Any ideas anyone?
Regards,
Max Carlson
OpenLaszlo.org

prioritizing runtime image loading

Scott Evans <gse <at> laszlosystems.com>
2006-10-01 07:40:33 GMT

i have an app that really wants to be able to say
view1.setSource(xxx) and do it before all the other queued up images load
i figured it wouldn't be too hard to subclass LzView and override
setSource to use a priority queue. but when i talked to adam about this,
he warned me that i was in for trouble chasing edge conditions,
spurious/duplicate onload/onerror/etc events, and so on.
i decided to try it anyway. my priorityView is mostly working but acting
a little weird. i get the feeling adam was right, of course. :)
adam also mentioned that the media loader has some built-in priority code
that isn't publically exposed. this seems like a reasonable thing to want
for certain types of apps. any thoughts on exposing resource-loading
priorities? perhaps as an optional second parameter to setSource()?
gse