Loading Profile...
http://dev.bubbletop.com/engine/WidgetRq usefulness?
Widget Preview is a great feature
but why use a different WidgetRq (http://dev.bubbletop.com/engine/WidgetRq) for Widget Preview (http://dev.bubbletop.com/widgetpreview/) than the one used on Bubbletop personal page (http://www.bubbletop.com/WidgetRq)?
it seems different/broken and thus does not enable to test the developed widget in real conditions
thanks!
but why use a different WidgetRq (http://dev.bubbletop.com/engine/WidgetRq) for Widget Preview (http://dev.bubbletop.com/widgetpreview/) than the one used on Bubbletop personal page (http://www.bubbletop.com/WidgetRq)?
it seems different/broken and thus does not enable to test the developed widget in real conditions
thanks!
1
person has this question
I have this question, too!
Tell me when someone answers.
The more people who ask this question, the more it gets noticed.
The more people who ask this question, the more it gets noticed.
Create a customer community for your own organization
Plans starting at $19/month
-
Inappropriate?The reason of having a separate widget engine is to create a sandbox environment just for development and testing. To test in real conditions, please add your widget to the Development Panel inside of Bubbletop. you can enable this feature in your Profile panel.
thanks,
The company says
this answers the question
-
Inappropriate?The problem with this is that when one tests a widget in the sandbox, it doesn't behave the same way as in real conditions, which makes it not very useful..
I’m sad
EMPLOYEE
