I agree with the idea that flash forms should mirror html forms.  A couple
examples:

1. Not being able to name fieldnames the same.  In HTML, it simply returns a
comma delimited list upon submit, but throws an error in flash forms.
2. The calendar popup should have a way to quickly change the year rather
than scrolling through the months (I know there are hacks for this, but it
should be built in), and have a way to insert NO date.  Currently if you
have a date already selected, there is no way to clear it out.
3. File upload capability (I know there are hacks for this as well)
4. Get rid of the 64k limit/error
5. Ability to script new objects (currently the "New" keyword is not
allowed)
6. CFGRID does not recognize a new row when it is inserted/created
programmatically
7. Again, layout and page load time is a major pain in the butt, especially
when dealing with dynamic forms that currently have to be compiles EVERY
time.

I realize some of these may be bugs and not features, but their existence
made us dump our flash form development altogether.

Mike

-----Original Message-----
From: Mike Kear [mailto:[EMAIL PROTECTED]
Sent: Wednesday, December 21, 2005 10:48 PM
To: CF-Talk
Subject: Re: Flash Forms - Why Not?


Thanks for asking Tim,

I'd like to see flash forms add to but NOT TAKE AWAY from html forms.
Therefore, everything an HTML form does, ought to happen in flash forms.
For example,  make them respond to the mouse wheel.  Make drop down menus
drop down with a press of the down arrow key. etc.  So people who are used
to filling in forms in html find the flash forms behave in the same way ,but
also add some cool new features, such as the calendar popup, and the
validation with highlighting etc.

As it is now, if you use flash forms, you can use the terrific calendar
popup, and the cool way the field holding the current focus is highlighted
etc  but you lose other stuff.

Accessibility and standards compliance is a major issue and growing in
importance, specially on government and QANGO sites, so it would be good to
have flash forms fully compliant with the accessibility standards.

Also the biggest negative to flash forms is the time to load.  I had one I
thought was pretty cool, with a lot of neat things on it, but the client
said it didnt work.  When I investigated some more, it turned out he was
using a dialup connection and hadn't waited long enough for the "loading"
graphic to appear even, let alone the whole form.  I'm busy changing the
form now to a XML format one, based on the example in CFFORMS.com.

I really like the following aspects:

[A] you're making the CFFORM concept work.   In CF5 it looked terrific in
the specs, but failed to deliver the goods.  It now looks like we're pretty
close to the goods.
[B]  The ease of use for coders is terrific.  I have written a codegenerator
that creates basic forms off a datasource table, and then I tweak from
there.   Far less time spent writing validation scripts etc.
[C] I love the simple way you can make wizard-style forms and concertina
styles.

Merry Christmas!!

Cheers
Mike Kear
Windsor, NSW, Australia
Certified Advanced ColdFusion Developer
AFP Webworks
http://afpwebworks.com
ColdFusion, PHP, ASP, ASP.NET hosting from AUD$15/month




~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~|
Find out how CFTicket can increase your company's customer support 
efficiency by 100%
http://www.houseoffusion.com/banners/view.cfm?bannerid=49

Message: http://www.houseoffusion.com/lists.cfm/link=i:4:227506
Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4
Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4
Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
Donations & Support: http://www.houseoffusion.com/tiny.cfm/54

Reply via email to