Well it's not a problem for them now ... Macromedia support the passing of
files back and forth between Photoshop and Fireworks. FW4 supports
importing and exporting of .PSD files and maintaining all the layer and
other information.
It's simple to them.. they might want to get rid of Photoshop, but they know
they're not going to. So if they can't sell Dreamweaver AND Fireworks,
they'll be happy to sell Dreamweaver by itself. That's just good business.
So, taking this same thinking, they'll want users to go with ColdFusion and
Ultradev, but if they can't get both, they'll go for Ultradev and ASP rather
than send them away to another vendor. Similarly, if users don't want
Ultradev, they'll still be happy to supply ColdFusion to be developed with
other tools.
They won't see any conflict and nor do I.
Ford would like you to buy only Ford cars and trucks for your company. But
if you don't buy Ford cars, there's no conflict with them trying to get you
to buy Ford trucks.
Cheers,
Mike Kear
Windsor, NSW, Australia
AFP WebWorks
-----Original Message-----
From: Angél Stewart [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, 17 January 2001 11:20 PM
To: CF-Talk
Subject: How will Macromedia resolve conflict of interest?
Their products previously supported both CF AND ASP.
But now that they own CF..will their ASP support cease?
And if not..how are they going to reconcile supporting a language that
competes directly with their acquired asset, Cold Fusion????
-Gel
www.carigamer.com
Island Gaming At Its Best(TM)
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Structure your ColdFusion code with Fusebox. Get the official book at
http://www.fusionauthority.com/bkinfo.cfm
Archives: http://www.mail-archive.com/cf-talk@houseoffusion.com/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
