User Tools
blocks:remotecontent
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
blocks:remotecontent [2017/04/13 18:02] admin [Description] |
blocks:remotecontent [2023/01/31 16:46] (current) |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| + | <html><!-- nomoodle --></html>{{ :logo-apl.png?nolink |}}<html><!-- /nomoodle --></html> | ||
| ===== Remote content block ===== | ===== Remote content block ===== | ||
| - | ==== Description ==== | ||
| * **Component Type :** Block | * **Component Type :** Block | ||
| * **Name:** Remote Content | * **Name:** Remote Content | ||
| * **Family:** Content | * **Family:** Content | ||
| - | * **Versions:** 1.9, 2.2 to 3.2 | + | * **Versions:** 1.9, 2.2 to :M39: |
| * **Distribution :** Public | * **Distribution :** Public | ||
| * **Disponibilité :** Stable | * **Disponibilité :** Stable | ||
| + | |||
| + | ==== Description ==== | ||
| The Remote Content Block (and probably "customlabeltype_remote_content" brother plugin, will offer a unified, generic and multimode way of fetchig external content to add within a moodle page from any web site or remote web app having a web service API. This allows to provide customers with solutions of mashing integration with no further development at all, for most of the additional externally generated content a moodle page might need. | The Remote Content Block (and probably "customlabeltype_remote_content" brother plugin, will offer a unified, generic and multimode way of fetchig external content to add within a moodle page from any web site or remote web app having a web service API. This allows to provide customers with solutions of mashing integration with no further development at all, for most of the additional externally generated content a moodle page might need. | ||
| Line 50: | Line 52: | ||
| The capture mode based on start and end patterns assume there are such recognizable patterns in the received content flow. This is not always tivial. We will examine how to use a Dom parser to extract a portion of content based on a XPath identifier that would be more flexible to cut an interesting content sequence. | The capture mode based on start and end patterns assume there are such recognizable patterns in the received content flow. This is not always tivial. We will examine how to use a Dom parser to extract a portion of content based on a XPath identifier that would be more flexible to cut an interesting content sequence. | ||
| - | ==== dynamic remote queries ==== | + | ==== Dynamic remote queries ==== |
| In some cases, (still in study) we will allow internal dynamic values injection in the remote queries (such as username, user id o idnumber, course idnumber or shortname, etc... in general any available contextual available data that might be usefull to divert the remote server reponse) | In some cases, (still in study) we will allow internal dynamic values injection in the remote queries (such as username, user id o idnumber, course idnumber or shortname, etc... in general any available contextual available data that might be usefull to divert the remote server reponse) | ||
blocks/remotecontent.1492099356.txt.gz · Last modified: 2024/04/04 15:50 (external edit)
