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

Patrick Mueller edited comment on CB-1234 at 12/12/12 5:45 PM:
---------------------------------------------------------------

The file 8.patch is the original patch from the pull request - 
https://github.com/apache/incubator-cordova-weinre/pull/8 - since that repo may 
disappear soon.

Note that this patch also includes a completely unrelated (as far as I know) 
set of changes to some weinre HTML for skinning or something.  Those changes 
will need a separate bug report file, to get them incorporated.  These changes 
should NOT be applied for this particular issue.
                
      was (Author: pmuellr):
    The original patch from the pull request - 
https://github.com/apache/incubator-cordova-weinre/pull/8 - since that repo may 
disappear soon.
                  
> Console should queue log messages if not connected
> --------------------------------------------------
>
>                 Key: CB-1234
>                 URL: https://issues.apache.org/jira/browse/CB-1234
>             Project: Apache Cordova
>          Issue Type: New Feature
>          Components: weinre
>    Affects Versions: 2.0.0
>            Reporter: Matt Johnson
>            Assignee: Patrick Mueller
>         Attachments: 8.patch
>
>
> Console log messages (log, debug, error, info, warn) from the target may be 
> lost if they are executed on the device before the remote connection is fully 
> complete.  These should be queued up if there is no remote connection (and 
> dequeued when one is acquired) so all log messages are retained.
> I have a pull request at 
> https://github.com/apache/incubator-cordova-weinre/pull/8 that does this as 
> well as turns the Console into a passthru so that all calls to Console still 
> act on the OriginalConsole as well as the RemoteConsole so that the target 
> behavior with weinre is unchanged.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to