Expand my Community achievements bar.

July 31st AEM Gems Webinar: Elevate your AEM development to master the integration of private GitHub repositories within AEM Cloud Manager.
SOLVED

Problem getting SharedWhiteBoard to work on tablets

Avatar

Level 1

Hi,

I want to use LCCS and flex mobile to create a realtime collaborative whiteboard app so when I saw that LCCS provides this out of the box I was really excited. I tried it as a web app and it works like a charm.

However I can't get it to work on a tablet.

Here is the simple "hello world" type of mobile app. I am using FB 4.5.1 with lccs.swc (for flash player 10.1)

<?xml version="1.0" encoding="utf-8"?>

<s:Application xmlns:fx="http://ns.adobe.com/mxml/2009"

        xmlns:s="library://ns.adobe.com/flex/spark"

       xmlns:rtc="http://ns.adobe.com/rtc"

      applicationDPI="160">

<fx:Declarations>

      <rtc:AdobeHSAuthenticator id="auth" userName="guest"/>

</fx:Declarations>

<rtc:ConnectSessionContainer id="moony"

                                             authenticator="{auth}"

                                             roomURL="some_url" width="100%" height="100%">

          <rtc:SharedWhiteBoard width="100%" height="100%"/>

</rtc:ConnectSessionContainer>

</s:Application>

This is making the compiler unhappy. I am getting this error:

'ConnectSessionContainer' declaration must be contained within the <Declarations> tag, since it is not assignable to the default property's type 'Array' or element type 'mx.core.IVisualElement'.

Not sure exactly what's going on here. Maybe I am making a noob mistake. But it feels like mobile lccs documentation is a bit sparse.

1 Accepted Solution

Avatar

Correct answer by
Level 3

I know of no reason why linking the mx and sparkskins swc will not work.

That said, it's not supported on mobile devices, so I/we make no guarantees.

And performance was a big reason for the switch to Spark, so I'm not all

that surprised that you see some sluggishness.

As I said, we'll be releasing the beta version in a matter of days. We'll be

posting it here, so consider yourself signed up. However, I will warn you

that the SharedWhiteBoard will be the least finished of the components, so I

would not expect to go to production with it immediately.

Thanks

sasha

View solution in original post

3 Replies

Avatar

Level 3

Well, LCCS is not really meant to be mobile compatible yet (soon, I promise,

soon!)

Both ConnectSessionContainer and SharedWhiteBoard extend MX components,

which don't really work for mobile apps.

I believe that what you're seeing is that ConnectSessionContainer isn't

legal to add to the Spark Application, because it inherits from Canvas. It's

a pretty unhelpful error message, though, I agree.

We're busily working on a new version of the SDK and should have a

beta-quality release of it in a matter of days, not weeks.

Thanks

sasha

Avatar

Level 1

Thanks Sasha. I would be very interested in beta testing this! (just tell me how to signup)

So in the meantime I manually added mx.swc and sparkskins.swc to the build path and was able to get it to work on xoom (haven't tested ipad)

Is this an OK workaround or a dirty hack? The app feels a bit sluggish (very little but noticeable) and obviously its not touch enabled. But I was thinking I could enhance the client side code of SharedWhiteBoard to address these problems.

Is that feasible or does it require service side changes as well? And should I wait for the beta release to avoid any wasted effort on my part.

Please advise. Thanks!

Avatar

Correct answer by
Level 3

I know of no reason why linking the mx and sparkskins swc will not work.

That said, it's not supported on mobile devices, so I/we make no guarantees.

And performance was a big reason for the switch to Spark, so I'm not all

that surprised that you see some sluggishness.

As I said, we'll be releasing the beta version in a matter of days. We'll be

posting it here, so consider yourself signed up. However, I will warn you

that the SharedWhiteBoard will be the least finished of the components, so I

would not expect to go to production with it immediately.

Thanks

sasha