Task #71055

Streamline usage of DebugConsole

Added by Oliver Hader over 5 years ago. Updated over 3 years ago.

Status:
Closed
Priority:
Should have
Assignee:
-
Category:
Backend API
Target version:
Start date:
2015-10-26
Due date:
% Done:

100%

Estimated time:
TYPO3 Version:
7
PHP Version:
Tags:
Complexity:
Sprint Focus:

Description

Since the backend DebugConsole has been rewritten in jQuery, references to the old ExtJS variant can either be removed or adjusted to work with the new DebugConsole.

The general question is, whether the new DebugConsole shall implement the browser's console interface in case the console object is not available, that would be (besides implementing DebugConsole.log()):

console: {
log: TYPO3.DebugConsole.log,
info: TYPO3.DebugConsole.log,
warn: TYPO3.DebugConsole.log,
error: TYPO3.DebugConsole.log
};

If fallback for a missing console object is not the goal of the jQuery DebugConsole, the remaining parts can be cleared up, e.g.
  • all mentions of TYPO3.Backend.DebugConsole (which does not exist anymore) with and without combination of Ext (ExtJs) stuff
  • console.addTab (see HTMLArea, referring to the old ExtJS component)
  • extDirectDebug (see PageRenderer)
#1

Updated by Gerrit Code Review over 5 years ago

  • Status changed from New to Under Review

Patch set 1 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/44303

#2

Updated by Gerrit Code Review over 5 years ago

Patch set 2 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/44303

#3

Updated by Oliver Hader over 5 years ago

  • Subject changed from Streamline DebugConsole to Streamline usage of DebugConsole
#4

Updated by Oliver Hader over 5 years ago

  • Status changed from Under Review to Resolved
  • % Done changed from 0 to 100
#5

Updated by Riccardo De Contardi over 3 years ago

  • Status changed from Resolved to Closed

Also available in: Atom PDF