Details
-
Type:
extRequest
-
Status: Closed
-
Priority:
Major
-
Resolution: Won't Fix
-
Fix Version/s: Sprint 4.1.3
-
Component/s: FIWARE-TECH-HELP
-
Labels:None
-
HD-Chapter:Apps
-
HD-Enabler:Wirecloud
Description
Web Browser: Google Chrome version 38.0.2125.104
Operating System: OSX version 10.9.5
User id: cloudtestulpgc
Tested GE(s): Wirecloud
Responsible: fiware@ulpgc.es
Description
The platform doesn’t provide any way to export a widget or mashup for use
it independently of wirecloud.
This is important because a user could want to have a widget allocated in
his own platform. The user could have his own instance of wirecloud
running, but for a relative small project, the wirecloud platform probably
expends more resources that the application itself.
How to replicate: Try to export a widget or mashup and try to use them
isolated.
_______________________________________________
Fiware-lab-help mailing list
Fiware-lab-help@lists.fi-ware.org
https://lists.fi-ware.org/listinfo/fiware-lab-help
Activity
Dear Álvaro,
We will try to explain it better:
We mean that a developer could export the widget, and use it stand alone
without embed it or have an instance of wirecloud running.
For example, a user develops a mashup inside wirecloud platform, makes all
the html, js and links the widgets. It would be great if the user can
export this mashup with only the API resources it needed.
User deploys the mashup after in a webserver without any dependency of a
wirecloud instance.
It´s not really a bug, just a thought of the result of the experience of a
standard developer who is starting to work with wirecloud.
Best regards,
2014-11-03 15:53 GMT+00:00 FW External User (JIRA) <
Dear tester,
please provide more information about this. For example, what do you mean
with "running a widget or mashup independently of wirecloud"?
Have you read the "Embedding mashups inside other web pages" section
<https://forge.fi-ware.org/plugins/mediawiki/wiki/fiware/index.php/Application_Mashup_-_Wirecloud_-_User_and_Programmer_Guide#Embedding_mashups_inside_other_web_pages>
of
the Wirecloud user and programmer guide?
Best regards,
Álvaro
_______________________________________________
Fiware-lab-help mailing list
Fiware-lab-help@lists.fi-ware.org
https://lists.fi-ware.org/listinfo/fiware-lab-help
I will mark this as won't fix because there is a lot of things to take into account, for example, some widgets/operators need accessing the Wirecloud's proxy. This is not going to be easy to implement. But may be take into account in next releases.