[TYPO3-dev] Status of "devlog" extension

[Steffen Müller]

Hi.

Sorry for my late reply.
I'm happy to see there's interest in the logging topic.

On 01.06.2013 21:41 Georg Grossberger wrote:
> 
> So here a first draft: https://github.com/Trenker/typo3.devlog.git
> 

It seems that you have put some remarkable effort into Logging. Would
you like to join the Logging task force for the TYPO3 core?
But first let me answer your questions and then tell a bit about goals
for 6.2 LTS for core logging.

> The integration of the Logging API is a good idea. This raises an
> important question:
> 
> How much functionality of the current devlog will be provided by the new
> logging API? The two (IMO critical) features in question: grouping the
> entries per run, detailed debug data display.
> 

The Logging API in TYPO3 (>= 6.0) is, as its name implies, just an API.
It does not come with a view (aka BE log module). IMO grouping of data
and detailed display is part of the particular view.
I'm not sure what you mean by "grouping entries by run", but if you want
to group log records of a single request, this should be easy since we
have a unique request_id in each log record.
The log() API accepts a data array argument, just like the devlog() API
did. So from the data model of the core Logging API is capable of that.

The Logging API has been documented at [1]

The BE log module is not (yet) capable of displaying log records from
the Logging API. This definitly needs to be solved for 6.2.

> If it has features for this, than the devlog - in its current state -
> will not be needed anymore, but may only be a set of decorators or
> processors for dev-infos.
> 

Would you like to share your ideas on [2] and create some issues for
that, so we have discussion and potential changesets in one row?

What are the goals for logging the TYPO3 6.2

First of all, the logging topic is definitly on the roadmap for 6.2.
We have been discussing the goals for logging in 6.2 in the core
team/active contributors meetup. Ernesto as release manager and me as
Logging task force leader sat upon the next steps and a short article is
on the way to give the community an idea about our plans.
In short, we aim to a) create a future concept for core logging, b) ship
good default configuration sets, c) replace log implementation from old
methods with new API (incl. deprecating old log APIs like devlog) and d)
create compatibility for the demands of input and output (be log module).
We also thought of creating a BE module based on datatables like in
ExtensionManager. Although this new module does not have highest
priority, anyone is welcome to contribute.

Again, I would be really happy to win you or any other person interested
in Logging to push the logging topic forward for 6.2 LTS.

Just apply for membership at [2] and add some notes which topic you're
interested to help.

[1]
http://docs.typo3.org/typo3cms/CoreApiReference/ApiOverview/Logging/Index.html
[2] http://forge.typo3.org/projects/typo3v4-logging

-- 
cheers,
Steffen

TYPO3 Blog: http://www.t3node.com/
Twitter: @t3node - http://twitter.com/t3node