Re: [Pythoncard-users] time to share your PythonCard gripes and likes

[<bra...@om...>]

Alex Tweedly wrote on 04/24/2005 07:07:40 PM:

> 5. Additional compound widget.
> Seems like every app I do (and 90% of the ones I see), involve a fair 
> number of "paired" components - a static text "label" and a text field 
> (or text area), with the label text is right aligned, to the left of the 

> text field (or occasionally above and left aligned). It would make it 
> much easier for me to have a single widgets (labeled text field, labeled 

> text area) - and a few extra properties such as label text, horizontal 
> vs vertical, spacing and label size.
> 
> (If it isn't easy to do this, consider just doing a "fake" of it in the 
> Resource Editor).


I'm in favor of most of the things you posted, but this one in particular 
would
be most helpful to me and others who build database GUI forms. If there is
any objection to adding so many properties to TextField (you mentioned 
four),
we might be able to do without spacing and label size. I'd be happy if
the label font attributes just matched that of the text field. In other 
cases
I could just make a StaticText label.

Hm...there's also the question of left or right justification for the 
label
in the containing widget. Would there be a containing widget? Something 
that 
holds both the label and the TextField? I guess that gets into the 
question
of container widgets...

FileMaker has a feature whereby a label can be automatically generated
for a widget, but it is not attached in any way. There is a checkbox in 
the dialog
box for adding a field for the layout, along the lines of "create label 
for this field".
This might be easier to add to PythonCard, and would at least provide some
improved convenience.