Chamilo LCMS Connect » Core » Common

Some submanagers (e.g. the RepoViewer and the StreamingMediaManager) may have to be run in standalone mode at one time or another. That is, they are not displayed in the context of a specific application or component but in their own window / popup.

Given the nature of submanagers, a parent application is always required, but such an application is not a classic application like the repository or the weblcms, it is more like a wrapper which allows us to use some basic functionality like get_user, set_parameter, get_url, etc. The current application class however also forces us to implement some things like is_active, which is only relevant for installable applications and not for (sub)managers which allow access to a certain kind of (external) functionality.

This is why the current structure is inadequate:

Application

CoreApplication

=> RepositoryManager
=> GroupManager

WebApplication

=> WeblcmsManager
=> PersonalCalendarManager

with the following floating around independently:

HtmlEditorFileBrowser (the Browse server popup in CKEditor for images, videos, etc.)
StreamingMediaManagerLauncher (the popup to select e.g. a YouTube video)

The new structure would be like this:

Application

LauncherApplication

=> HtmlEditorFileLauncher
=> StreamingMediaManagerLauncher

BasicApplication

=> CoreApplication
> RepositoryManager
> GroupManager
=> WebApplication
> WeblcmsManager
> PersonalCalendarManager