> Can't all of that be done by establishing standards for a project or all
> projects. Why does it have to be Fusebox? I have been looking at Fusebox
> and I guess that I am a bit confused as to what it is and why I should use
> it over some other set of standards?
Which other set?
In addition to that, the more people using a standard the more likely it is
to be helpful across development efforts. OF course, any standard will work
to help achieve the same ends as fusebox within a particular development
effort, project, or company. But the real strength of finding some common
standard (and if something about it doesn't work for you, explain what it is
and get something in the spec that will!) is when you start moving apps
between developers, companies, etc. A fusebox app will easily plug into
another fusebox app without many problems. Another methodology may achieve
everything else, but when you decide to plug your calendar into John's
client management app, the fact that you both used your own internal
methodology won't matter a whit.
Which isn't to say that Fusebox is perfect, but it is actively evolving, has
a good recognition in the community, etc. If you can use it, why not? If you
can't, is it something that could be worked into the spec?
And if the anwer to that last question is NO, then no harm, no foul, right?
It's certainly something worth considering...
c
--
Chris Lott <[EMAIL PROTECTED]>, Technical Manager
p907.474.5122 | f907.474.5402 | PGP Key ID: 0x8687E87E
------------------------------------------------------------------------------
Archives: http://www.eGroups.com/list/cf-talk
To Unsubscribe visit
http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/cf_talk or send a
message to [EMAIL PROTECTED] with 'unsubscribe' in the body.
