Re: PATCH: Bug 186

Apologies for the blunt end statement, but I've spent a lot of time redoing
this widget audit and do not appreciate the dismissive attitude just because
a complex widget does violate "The XWT Way" to a small degree.  I wouldn't
mind if you suggested an actual solution, but batting emails back and forth
saying 'I don't like it' and not much else.  And telling me to do the same
thing just differently doesn't help either.

I spent a lot of time working on the scrollpane widget.  There is no obvious
way to acheive a similar simplicity without the reassignment, and forcing
the developer to do it manually is no solution either.  If it's going to be
*that* potentially confusing to the budding developer, then I'll put an
xwt.println statement in there to spit out to the log file that a
reassignment is taking place.

-----Original Message-----
From: Charles Goodwin [mailto:[email protected]]
Sent: 27 March 2003 13:51
To: '[email protected]'
Subject: Re: [xwt-dev] PATCH: Bug 186


> Hell, myBoxNorth = xwt.newBox(). There's no reassignment there.

I just had that discussion with Andrew.

So I want this in north:

<box id="x" color="gray" hpad="2" vpad="2">
	<box id="ruler" image="ruler" tile="true" />
</box>

$scrollpane.center._SizeChange = function() {
	$ruler.width = center.width;
}

Now this is a very simple example.  The xwt.newBox() syntax for that is
already non-trivial.  Imagine having something half-complex up there.

As for the manual reassignment issue, that's daft as well.  If you read the
doc on scrollpane_tag, you'd know it reassigns, so that's manual reassigment
too.  No matter what dress it's wearing, everything you've suggested is that
same or worse than what's there already, just more verbose.

I'm not debating this crap anymore.  Period.
_______________________________________________
http://lists.xwt.org/listinfo/dev
_______________________________________________
http://lists.xwt.org/listinfo/dev