Hello All,
MUST I use the Form tags, if I have Text Fields (or any controls
really...) that will eventually be submitted to a WebService or
RemoteObject later on?
I guess what I am asking is: Is the developer forced to use Forms,
whenever collecting data for the purpose of sending and/or receiving
(with potential validation before submission)? Is using the Form tags,
just easier in the long haul, when it comes to validation, etc?
The reason I ask, is that I find the <Form> tags (which itself IS a
container object) VERY prohibitive when it comes to laying out my
controls. ALL the examples I've seen thus far, are single column in
nature - the top-down approach to laying out the controls. Well, that
does not work for me - I need to also put fields across too (sometimes
2, 3 or more columns) - and the default <Form> container really isn't
setup for that type of thing.
I've tried creating a Form container, and then inside THAT putting a
HBox container, which of course allows me to put controls across, but
how do I handle subsequent Rows below the previous, when the need arises
for me having to properly line up controls from top to bottom?
In this particular case, I think it would be easier for me, to use
Absolute Positioning - using the Canvas container.
If I use this type of method for laying out my forms, am I screwing
myself later on, by not using the <Form> and <FormItem> tags when
sending data to the server? Or just as important, performing Form
Validation before sending the data to the server?
Or, maybe I am missing something, and there IS a way to properly line up
my Controls from Top to Bottom AND from Left to Right, with having
multiple Fields going across the Form horizontally as well...
Could you all shed some light on this topic?
Thanks in advance for your help,
Mike
Yahoo! Groups Links
<*> To visit your group on the web, go to:
http://groups.yahoo.com/group/flexcoders/
<*> To unsubscribe from this group, send an email to:
[EMAIL PROTECTED]
<*> Your use of Yahoo! Groups is subject to:
http://docs.yahoo.com/info/terms/
