Expand my Community achievements bar.

Guidelines for the Responsible Use of Generative AI in the Experience Cloud Community.
SOLVED

Docs and samples issues

Avatar

Level 3

The comment in WebCamera.as talks about NoteModel. Maybe it should be the CameraModel ?

Dispatched when the NoteModel has fully connected and synchronized with the service
or when it loses that connection

The WebCamera component is a high level "pod" component which allows multiple
users to publish and display webcam video. In the MVC sense, the WebCamera is the view
and controller to the NoteModel's model since it consumes user events, drives them
to the model, accepts model events, and updates the view.

Isn't AFCS rebranded to LCCS?

It's confusing to see AFCS in code and docs.

The developer guide is called "afcs_developerguide.pdf" and has AFCS mentioned many times.

There are several places in the code that should be LCCS instead of AFCS.

Example for use of AFCS in code, there are other places:

WebCamSubscriber.as

AFCS does not support multiple layouts <code>layout()</code> always returns SIDE_BY_SIDE.

The FlashSimpleChat example imports uneeded audio and webcam classes:

import com.adobe.rtc.collaboration.AudioPublisher;
import com.adobe.rtc.collaboration.AudioSubscriber;
import com.adobe.rtc.collaboration.WebcamPublisher;
import com.adobe.rtc.collaboration.WebcamSubscriber;

1 Accepted Solution

Avatar

Correct answer by
Former Community Member

Hi Dan,

You are absolutely right. It should be CameraModel and also AFCS has been rebranded to LCCS but all changes in code and everywhere else were not fixed by the previous release. We are actually doing a complete rebranding of code/example/ourSDKApp currently. You will see all these fixed in coming release soon.

Thanks for letting us know.

Regards

Hironmay Basu

View solution in original post

1 Reply

Avatar

Correct answer by
Former Community Member

Hi Dan,

You are absolutely right. It should be CameraModel and also AFCS has been rebranded to LCCS but all changes in code and everywhere else were not fixed by the previous release. We are actually doing a complete rebranding of code/example/ourSDKApp currently. You will see all these fixed in coming release soon.

Thanks for letting us know.

Regards

Hironmay Basu

The following has evaluated to null or missing: ==> liqladmin("SELECT id, value FROM metrics WHERE id = 'net_accepted_solutions' and user.id = '${acceptedAnswer.author.id}'").data.items [in template "analytics-container" at line 83, column 41] ---- Tip: It's the step after the last dot that caused this error, not those before it. ---- Tip: If the failing expression is known to be legally refer to something that's sometimes null or missing, either specify a default value like myOptionalVar!myDefault, or use <#if myOptionalVar??>when-present<#else>when-missing. (These only cover the last step of the expression; to cover the whole expression, use parenthesis: (myOptionalVar.foo)!myDefault, (myOptionalVar.foo)?? ---- ---- FTL stack trace ("~" means nesting-related): - Failed at: #assign answerAuthorNetSolutions = li... [in template "analytics-container" at line 83, column 5] ----