Dear Emilien, First of all thank your very much for your interest in our GE. Please find below my answers, inlined in this email. El 22/10/2014 15:10, Emilien Schneider escribió: >> >> Hi, >> >> We're currently filling the template to apply for the first open call >> and we're planning to use Application Mashup for the project. >> I have some questions regarding this GE. >> >> We have a platform based on the e-learning platform Claroline Connect. >> We would like to add a web application that is linked to Claroline >> Connect but only displays a limited amount of information to logged in >> users. >> >> If I understood correctly what can be done with Application Mashup, I >> have to create 2 new widgets : >> - one to identify the users with a form >> - one to display what needs to be displayed >> Is that correct? >> >> We need more information to be of any help. We do not know whether you intend to use Wirecloud to "widgetize" the Claroline Connect platform and allow users to configure their own dashboards/workspaces with the widgets of their interest (or, similarly, whether you intend to preconfigure these dashboards during the configuration of a new course) or, on the contrary, you are thinking about using widgets within your portal. The first approach is the most useful (e.g. Jira allows you to configure your own dashboard using widgets, but does not has the power of Wirecloud behind the scenes so it imposes more restrictions). The second approach is also feasible but you will face more restrictions because what you are doing in the end is publishing a mashup outside Wirecloud and embedded in your own portal. Could you please further elaborate on your approach? Regarding the two widgets you mention. Both of them are feasible if you intend to embed html+javascript+css in them. In the end, a widget is treated by the platform as a simple iFrame. A different question is how you design it in terms of endpoints to make it more reusable (i.e. participate in different mashups connected to different widgets). Moreover, regarding the widget that identify users with a form (are you talking about a registration/ sign up?) you can opt to use FIWARE IdM GE, Wirecloud registration/sign in or your own approach as long as you manage to integrate it with Wirecloud (many Django connectors/backends are supported by Wirecloud). Also take into account that you can deploy your own customized instances of WireCloud (reference implementation of the Application Mashup GE) and avoid the dependences with the FIWARE Lab portal (the mashup portal at FIWARE Lab is based on Wirecloud, but you are locked-in with the FIWARE IdM, etc.). You can also make modifications to it (maintaining the AGPL license). >> If I create these two widgets, do I need to make them public, or can I >> develop some private widgets? >> >> What do you mean with "private widgets"? Widgets are written in html+css+javascript, so their code will be downloaded by the client. Nevertheless, when you upload a widget to Wirecloud, it is only accessible from your account, unless you decide to publish it in the catalog/store and share/sell it. The backend code is maintained "private" and you can choose your own license for your widgets. The do not need to comply with AGPL. > > >> Could you tell me if I understand those things in the right way? >> >> Thanks in advance for your help, >> >> Regards, >> >> *Emilien Schneider* >> 07 82 25 30 18 >> http://emilienschneider.poucr.net >> -- Soutenez des projets responsables : http://www.wedogood.co -- >> >> Best regards Álvaro -------------- next part -------------- An HTML attachment was scrubbed... URL: <https://lists.fiware.org/private/fiware-tech-help/attachments/20141023/8e7f4d09/attachment.html>
You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy Cookies policy