You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ripple.apache.org by "Jim Cummins (JIRA)" <ji...@apache.org> on 2014/05/01 20:25:15 UTC

[jira] [Commented] (RIPPLE-55) Option to hide Plugin Registration Error

    [ https://issues.apache.org/jira/browse/RIPPLE-55?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13986838#comment-13986838 ] 

Jim Cummins commented on RIPPLE-55:
-----------------------------------

For me, this is a critical issue as it fires all the time. The delay is causes actually prevents me from being able to test my app's load process properly. Even a hard coded option to disable the popup by returning success or error would be helpful at this point. At this point, I've stopped using ripple because of this issue. :(

> Option to hide Plugin Registration Error
> ----------------------------------------
>
>                 Key: RIPPLE-55
>                 URL: https://issues.apache.org/jira/browse/RIPPLE-55
>             Project: Apache Ripple
>          Issue Type: Improvement
>         Environment: Chrome
>            Reporter: Daniel Hough
>            Priority: Trivial
>              Labels: features
>
> I have a few plugins registered for my Cordova which will not work in Ripple, for perfectly valid reasons. Every time I refresh the page (which is a *lot*) I see the "I Haz Cheezburger?!" modal which pops up wondering if I'd like to pass some JSON to the success or error callback.
> While this is very useful, it would be nice to have somewhere to define the default JSON to pass through every time, rather than have the modal pop up every time. It adds about 3 seconds to the process, and given that I am refreshing about 200 times each day it would save me a total of 10 whole minutes of development time each day, which is not a trivial amount. I think many people would appreciate this feature.
> If it's already an option, I would love for someone to point me in the direction of how to do it, and I would be more than happy to update documentation myself to make it clearer. Thank you.



--
This message was sent by Atlassian JIRA
(v6.2#6252)