> cfinput, etc. but I have a lot of legacy code. Some I wrote
> when I was just starting with cf and a lot of it that I
> inherited.
I suspect that this code isn't XHTML-compliant anyway, though, right? I know
the "legacy code" I've left laying around hasn't always been
XHTML-compliant.
> <rant>
> My issue is that a couple of hours of work on Macromedias
> part to fix the tags (the released a hot fix for the form
> tags a while ago and could have done it then) could save
> hundreds to thousands of hours of work for their customers
> who may need to make the switch but not be able to get
> Blackstone.
>
> One of my pet peeves is when people say "oh just wait a
> little while and it will be fixed in the next version" in
> this case "Blackstone". There is no guarantee that I will
> get budget approval for Blackstone and I'm sure that other
> Macromedia customers are in the same boat. Or the other
> issue that can happen (and it did to me with mx and mx 6.1)
> is that the IT decision makers probably won't make Blackstone
> a company standard for a while and we can't install it on our
> production servers until they do, so fixes in a new version
> can't help the problem now.
> </rant>
Perhaps, as a paying Macromedia customer, you should complain to them
directly. I sympathize with you, but I can't solve the problem, beyond
noting that there is an encrypted file named "form.cfm" in my
\WEB-INF\cftags directory.
However, realistically, how soon will XHTML be important to you? I don't
know if it'll be important in a general sense during the lifespan of the
Blackstone release.
Dave Watts, CTO, Fig Leaf Software
http://www.figleaf.com/
phone: 202-797-5496
fax: 202-797-5444
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings] [Donations and Support]
