SlideServe
Télécharger Obtenir Pro
Menu
Accueil Pro
Préférences
ApparenceLight Aide et commentaires
© SlideServe · v2026

contentXXL – Device Support

kacia avatar
kacia
13 diapositives · 292 Views · Sep 05, 2014

contentXXL – Device Support. contentXXL Device Support . Overview Configuration How it is implemented 4. Customization 5. Limitations. 1. Overview. Device Support means content is displayed different depending on the device which is used

contentXXL – Device Support - slide 1
01 / 13contentXXL – Device Support
1 / 17

Télécharger la présentation

contentXXL – Device Support
Une image / un lien ci-dessous est fourni (tel quel) pour télécharger la présentation

Politique de téléchargement : le contenu du site vous est fourni TEL QUEL pour votre information et votre usage personnel ; il ne peut être vendu, concédé sous licence ni partagé sur d’autres sites sans l’accord de son auteur.Le contenu vous est fourni TEL QUEL, pour votre information et votre usage personnel uniquement. Téléchargez la présentation en cliquant sur ce lien. Lors du téléchargement, si vous ne parvenez pas à télécharger une présentation, l’éditeur a peut-être supprimé le fichier de son serveur.Pendant le téléchargement, si vous ne parvenez pas à obtenir une présentation, le fichier a peut-être été supprimé par l’éditeur.

F I N

Plus de contenu associé

Transcription de la présentation

  1. contentXXL – Device Support

  2. contentXXL Device Support • Overview • Configuration • How it is implemented 4. Customization 5. Limitations

  3. 1. Overview Device Support means • content is displayed different depending on the device which is used • This is done by applying another set of templates for a specific device • Standard device: Webbrowser (must not be configured) • In this paper we will focus on using this feature for displaying a text-only version. Other devices can be supported in the same way.

  4. 2. Configuration • How to register a device A device is identified by base url only. There is no other identification included (but you can write your own one and redirect to base url) Create a new entry in the table ‘PortalSettings’ with a settingskey ‘device’ and a settingsvalue like ‘url=yourdomain.com;device=textonly;‘ (this url must be registered as baseurl as well) In the global.asax the current device is recognized from the baseurl in the Application_BeginRequest eventhandler Context.Items("currentDevice") is set (in our case context.items(“currentDevice“) = „textonly“)You can use this value to implement device specific logic in templates

  5. 2. Configuration • Pagetemplate: Any device must have a default pagetemplate in the shadow-folder: Name convention is <device>.ascx (e.g. textonly.ascx) Otherwise the ‚Device not supported‘ message appears Special pagetemplates may be placed in pagetemplates/textonly/ e.g. pagetemplates/textonly/myspecialtemplate.ascx is the textonly template for pagetemplates/myspecialtemplate.ascx (this is not mandatory).

  6. 2. Configuration • How to apply a special set of templates for a device This is done in the module settings manager by creating a standard modulesettings template with output for this device and the specific settings: The templates configured here are applied for any module of this object type when textonly mode is active

  7. 3. How it is implemented Database: ‚ModuleSettingsTemplate‘ contains device information settings are stored in ‚ModuleInstance‘ and ‚ModuleSettings‘

  8. 3. How it is implemented • Class PageTemplateHelper • is called from desktopdefault.aspx • handles device information • Most important method: • CreateLayout() • returns LayoutInfo object • properties • TextOnlyTemplateName() • IsTextOnlyMode() • are legacy from contentXXL 2.54 • now the more general device concept is • followed

  9. 3. How it is implemented • ClassLayoutinfo • provides path to pagetemplate

  10. 3. How it is implemented • Class ModuleSettingsDeviceValidator • called from ModuleInstanceInfo instance • ValidateCustomSettings • (ByVal moduleID As Integer, ByVal device As String, ByVal portalID As Integer, • ByRef customSettings As ModuleCustomSettingsCollection) • fills ModuleCustomSettingsCollection with default device custom settings • ValidateInstance(ByVal moduleID As Integer, ByVal device As String, ByVal portalID As Integer, • ByRef instance As ModuleInstanceInfo) • provides default device general settings

  11. 4. Customization File customsettingsmap.xmlin plugin folder maps module custom settings with standard device modulesettingstemplate custom settings and can be overwritten in the shadow-folder Example: <?xml version="1.0" encoding="UTF-8"?> <customSettings> <setting key="articletemplate" type="template" /> <setting key="printtemplate" type="template" /> <setting key="bigitemtemplate" type="template" /> <setting key="bigitemalttemplate" type="template" /> <setting key="smallitemtemplate" type="template" /> <setting key="smallitemalttemplate" type="template" /> <setting key="headertemplate" type="template" /> <setting key="footertemplate" type="template" /> </customSettings> In device mode the templates defined in the setting nodes are applied from the modulesettingstemplate, other custom settings (like No. preview) are module specific.

  12. 4. Limitations • inherent to this concept all modules of the same type are rendered with the same templates (no flexibility) • device support is not implemented for Search and Navigation (due to a different handling of module settings regarding templates in these modules) • device support is has nothing to do with .NET Mobile Extensions or other Frameworks, that support devices. • text-only version is (in Germany) not accepted as barrier-free version for handycaped people.

  13. contentXXL Thank you!