Expand my Community achievements bar.

Dive into Adobe Summit 2024! Explore curated list of AEM sessions & labs, register, connect with experts, ask questions, engage, and share insights. Don't miss the excitement.

Just a quick hello

Avatar

Level 2

Hi People,

Just about to start the collaborative aspects of our current flex 4 application, so thought I'd pop along here first and say hi (seeing as I'm very likely to be coming here begging for help real soon) :-)

so, anyone else here using with flex 4? any head's up needed?

anyway just wanted to say hello

cheers

glenn

3 Replies

Avatar

Former Community Member

Hi,

Flash Builder beta and Flex 4 will work fine for our swc's. However, you might want to put the authenticator component( a non-visual component) inside <fx:Declarations> tag or inside the ConnectSessionContainer tag itself as shown in some of our examples.

Let us know if you find issues with our SDK while using flex 4.

Thanks

Hironmay Basu

Avatar

Level 2

HI

Thanks for the reply.

I will do. I imagine that the problems will be with the pre built pods??

Must say, I had a little go with cocomo a while ago, but Im really looking forward to having the time to really dig into this. Looks like a very interesting set of APIs.

Like I said, I'll be back soon with questions and a head ache!

Thanks again

glenn

tinylion development & design

Avatar

Level 2

3 days into my first round with the API and flex 4.

well, so far so good!

Getting everything setup and added into our current project was simple and worked first time as expected. log in of guests, changing/assigning roles, setting groups, and running the session in a sub model, all exactly what we wanted and I swear the first lot of code we did work first attempt. Great stuff. I dont think you could have made it any simpler to get working. SO pleased. in fact the client saw the additions after two days and asked me id I'd been working over the Christmas holidays! (well I said yes, wouldnt you!!)

anyway, flex 4. All is ok apart from as expected the pods all play up. well apart from the file share which isnt having any problems. All the problems with the pods are exactly what was expected and they all work well enough to be able to test that the sessions are working so thats cool.

we're going through writing some custom ones in spark, most of which we'll put up on google code. i'll drop some urls here when its ready (rough and ready most likely)

so, all in all a good experience for us. we're very pleased with what we had out the box.

to be able to take a project that is already over 12 months into development and add a major new set of functionality lilke this, and have the bones of it up and working in about 2 hours is amazing really and is testiment to the API

great work guys.

we're all looking forward to really get stuck into it now.

cheers

glenn