We are going to do option 1. We'll rely on spectrasource updates and our
own in-house ColdFusion developers, as it is only a big CF app anyway. Once
you get past the learning curve, modifying/maintaining cfa tags is no big
deal. In fact, we're aggressively pursuing additional Spectra projects
within the company.
S
"Tom Briscoe"
<TDB@compassb To: Spectra-Talk
<[EMAIL PROTECTED]>
nk.com> cc:
Subject: Keeping Spectra?
06/18/2002
10:47 AM
Please
respond to
spectra-talk
Hello all. At my company, we're giving thought to budgets for 2003. As
you may recall, Macromedia's support for Spectra is set to cease at the
end of that year. So I'm having to consider our future plans and just
what to do with Spectra in and beyond 2003.
I see a few immediate options:
1) Keep Spectra - Rely on the community, consultants and my own
resources to continue to build and support applications and hope it is
sustainable
2) Replace Spectra - Invest in another "content management" product
like PaperThin's CommonSpot and hope it remains viable on the long term
3) Recreate Spectra - Dump all these packages and their price tags in
favor of home-grown code
I'm looking to start some discussion on this subject. But if you don't
mind sharing, please share the list what you, your company or your
clients (names not needed) are planning to do in regard to Spectra. Or
just chip in your two cents on the best course of action. Anything will
do.
Thanks!
Tom Briscoe
Web Developer
______________________________________________________________________
Structure your ColdFusion code with Fusebox. Get the official book at
http://www.fusionauthority.com/bkinfo.cfm
------------------------------------------------------------------------------
To Unsubscribe visit
http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/spectra_talk or send a
message to [EMAIL PROTECTED] with 'unsubscribe' in the body.
