You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@myfaces.apache.org by "Udo Schnurpfeil (JIRA)" <de...@myfaces.apache.org> on 2014/03/05 20:30:43 UTC
[jira] [Commented] (TOBAGO-1373) Better JavaScript logging: using
browser console and fill browser gaps.
[ https://issues.apache.org/jira/browse/TOBAGO-1373?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13921273#comment-13921273 ]
Udo Schnurpfeil commented on TOBAGO-1373:
-----------------------------------------
The old LOG object is marked deprecated in 2.0 and removed in 3.0
> Better JavaScript logging: using browser console and fill browser gaps.
> -----------------------------------------------------------------------
>
> Key: TOBAGO-1373
> URL: https://issues.apache.org/jira/browse/TOBAGO-1373
> Project: MyFaces Tobago
> Issue Type: New Feature
> Components: Themes
> Reporter: Udo Schnurpfeil
> Assignee: Udo Schnurpfeil
> Fix For: 2.0.0-beta-1, 2.0.0, 3.0.0-alpha-1, 3.0.0
>
>
> Currently Tobago uses its own wrapper for logging in JavaScript.
> This should be replaced with the browsers console object like:
> LOG.info() -> console.info()
> Old browsers are not supporting some or all of it functionality. Here you can see what is possible in Firefox https://developer.mozilla.org/en-US/docs/Web/API/console
> or Chrome https://developers.google.com/chrome-developer-tools/docs/console-api
> For all undefined functions we should define a replacement, so the JavaScript code can use them all.
> One important advantage of not wrapping the calls is, that you can see the Code-Pointer in the Debugger-Console in the browser and jump into the code (if the browser supports that).
> Don't forget: all debugging code in Tobago will be markted with this suffix
> // @DEV_ONLY
> which will be removed in the compressed version, so it will not influence the production performance.
--
This message was sent by Atlassian JIRA
(v6.2#6252)