Re: PATCH: Bug 186

> I would naturally assume I can do the following:
>
> <scrollpane>
>      <box/>
>      <box/>
>      <box/>
> </scrollpane>
>
> It should produce a box with three boxes in a scrollpane. That's the 
> naturally intuitive way for it to work. The extra north/south/etc axis 
> are extra features that will be used by very few people.
> 
> If we're careful, we can make all the widgets work in almost the same 
> way. Makes life easier.

I pretty much agree with you there.  Yes, <scrollpane>boxlist</scrollpane>
should simply put the boxen into the scrollpane (<redirect target />).

However, the extra axis are important and cannot be dealt with so simply.
The extra axis are used by at least 1 widget (table) and the extra axis are
critical for things like a word processing app (rulers) or a spreadsheet app
(indice) as 2 very good examples.

Hence I'm using the notation:

<scrollpane>
	<box/>					// goes in central pane
	<box/>					// goes in central pane
	<box scrollpane_tag="west" />		// goes in western pane
	<box/>					// goes in central pane
	<box scrollpane_tag="north" />	// goes in northern pane
</scrollpane>

So for the majority of people, it will work the xwt way (tm) which is a good
thing (tm) but for those who require that extra bit of functionality, they
will have to rtfm (tm) so they understand how it works.

> Not pointless, but it is almost impossible - as far as I can tell. My 
> patch only stops cascading. However, I'm not going to commit code into 
> the widgets repository that redirects using _0, because it's just ruins 
> the XWT Way(tm) of doing stuff.

Ok, agreed, only when absolutely needed should this happen.  But I can give
you another example.

I'm using group to simplify layout.  To do this, I'm wrapping items added to
group in cell so you can do this:

<group>
	<radiobutton />
	<text />
	<radiobutton />
	<checkbox />
</group>

Rather than have to manually layout everything or create versions of
radiobutton/text/checkbox that do this layout.

Because this obviously skews the access a little, group also contains a
reference array that you'd use as an alternative for easy access.

Whilst it might not be the xwt way (tm) of doing stuff, it's a hell of a lot
simpler than:

<group>
	<cell><radiobutton></cell>
	<cell><text /></cell>
	<cell><radiobutton></cell>
	<cell><checkbox /></cell>
</group>

...where you'd probably have to manually link the radiobuttons together as
well.

There's a balance to be struck between keeping having things work
identically and having things work easily.  Unfortunately, a couple of
widgets have to sacrifice a little for the former to acheive the latter...
I'm open to ideas on how to reduce this to a minimum though.

That's why I'd hope you'd do more widget work with us David.  I'm not a
genius coder, you're much better.  I'm hoping you'll come along and work
with us, even though you disagree with our layout of the widgets.  It'd be
best to get the widget set fully audited and fully working before moving
everything again.  Our layout may not be ideal but it's working and we want
your help and your pragmatic perspectives. :)

Please come and help me improve the widgets.  We're getting there, but it'd
get there quicker if you'd come on #xwt and coordinate with us.
_______________________________________________
http://lists.xwt.org/listinfo/dev