Groups | Blog | Home
all groups > macromedia flash flashcom > october 2006 >

macromedia flash flashcom : FCX 1.5 MX and Flash 8


MIBtwo
10/30/2006 7:47:20 PM
Hello,

I was searching about this, but until now I found no sufficient or clear
answer.....
Which communication component set ( and where can you download them ) can be
used to develop for FCS 1.5 in Flash 8 Pro ?
I'd like to use the AVPresence, Chat, etc..... This is a serious request, not
targeting to get the answer "It is better to code them yourself" . The fact is,
that it is necessary to know about the compatibility. So please be kind and try
to clear or explain the circumstances to me. I'd like to start coding but feel
blocked by the simple question which components (FCS V1, V2 or FMS) I should
install.

Thanks in advantage

MIBtwo
MIBtwo
11/1/2006 4:24:45 PM
I'd like you to correct me if I am wrong, but it seems that the "new" fcs2
components available from
http://www.adobe.com/devnet/flashmediaserver/articles/components.html are dated
from June 2002. (Version info of AVPresence shows Version d20, 06.28.2002 for
example)

They seem to be older than the "latest" MX 2004 Communication Components that
I have found on my Harddisk (Version info of AVPresence shows Version d23,
02.22.2003 there)

So ,there is no AS2 compatibility to assume with the fc2_components and some
glitches reported by other people make this assumtion seem to be reality (see
problems with "SimpleConnect" and "VideoConference" reported in several other
threads).
I found no tech. Info, releasenote or anything official pointing out the
limitations to AS1 and the problems with deploying to FP > 6. The only source
of information is here in the forum. It is annoying, time consuming and does
not help in customer satisfaction (just my opinion) that Adobe does not keep in
track with it's own products. How is it to explain that Adobe/MM putsold soles
on new shoes, as it seems to me ?

Both, FMS and Flash 8, are good and well established Products. But (again I
just state my opinion) when a company offers an enrichment ( I still see the
CommComponents in that light) for an expensive product, it should be
supported, documented, maintained and updated in the same manner as the product
itself. Or they should let it be, because all what they cause is confusion when
things are not documented.

I would be glad, if I am wrong with what it seems to me. Maybe I missed
something and somebody can correct my statements (nobody is perfect).

The (sad) result of my investigation is :
- NO AS 2.0 compatibility,
- Problems when deploying to FP > 6 bec. of depricated statements
- partial decreased functionality of fms2_components compared to other
Versions of CommComponents (MX 2004 Components)
- NO docu regarding to limitations or technical info about compatibility.

Conclusion is (as JayCharles mentioned in a former post) :
Best is not to use the predefined CommunicationComponents.

As long as Adobe does not change them to support AS 2 and the actual FP
Versions I agree to JayCharles statement.

EOF

MIBtwo



JayCharles
11/1/2006 6:55:13 PM
Yup... the Communication components are written in AS1. Now, you can use them
(and export to AS2), if you go through the movie clips (the comm. components
are just movie clips), you can pick out the depreciated actionscript.

The main reason I don't like using them is the same reason I don't like using
anything that was purpose built by someone else. It's just easier to write my
own code than it is to pick through someone else's to bend it to fit my needs.
There's nothing inherently wrong with the MM Communication components (there's
good, solid code in there), and if you want to build an app just by drag and
drop, they're pretty good.
AddThis Social Bookmark Button