Proposal for logging infrastructure in Entitas about entitas HOT 17 OPEN

This would be awesome! What's the procedure on getting it in? I think I could help with it :)

from entitas.

I am not sure yet :)

First just wanted to see how much interest there is for such a feature.

Let's meditate on it for a couple more days and than flesh out a plan.

from entitas.

It sounds pretty interesting. Would it be possible to also see which system did the action?

from entitas.

This is what I meant by Logical events.
Combined with state events you would see something like

2015-12-26T09:56:21Z game1 user1 session1 InitSystem1 startExecution
2015-12-26T09:56:21Z game1 user1 session1 CorePool 34526 45673 1 e_created
2015-12-26T09:56:21Z game1 user1 session1 CorePool 34526 45673 1 c_added PositionComponent(5,4)
2015-12-26T09:56:21Z game1 user1 session1 InitSystem1 finishExecution
2015-12-26T09:56:21Z game1 user1 session1 SystemA startExecution
2015-12-26T09:56:21Z game1 user1 session1 CorePool 34526 45673 1 c_replaced PositionComponent(5,4) PositionComponent(5,5)
2015-12-26T09:56:21Z game1 user1 session1 SystemA finishExecution

This might get chatty, but I think it worth a try.
We can also adjust the log levels.

from entitas.

Ah, ok, was looking at the examples. Then I'm all for it as I've been wishing for a way to see what systems use what components (in an easier way than searching around in the code).

from entitas.

Hello,
I was just wondering what the benefits of having a logging system integrated with Entitas are. If you just provide the events and contexts then we are free to choose our own logging framework. I have previously gotten nlog and log4net to work in my experiments.

from entitas.

That was actually what I planned to do.
Figuring out all the hooks and maybe providing a few classes, which will make it easy to use those.

from entitas.

An integrated logging system could also make sense to use it as a foundation for visualization tools. A consistent logging output across projects could enable visualizing behaviour over time (e.g creating, changing and removing entities) which might help find some bugs.

from entitas.

It might help finding some bugs but as @mzaks said it would be useful only in dev state. The log output would be insane. If done I would like to see it as kind of plugin that is not built in to framework.
I agree with @SvDvorak checking for system-component dependencies is troublesome. Similar thing to Artemis-odb Component-Dependency-Matrix could resolve that issue quite nicely.

from entitas.

@kicholen I agree. It should be very easy to deactivate the logging. In the future I can imagine that we can build all kinds of visualization tools etc based on this data

from entitas.

One of the major problems with Unity development is there is no standard easy to extend logging interface. There have been attempts to replace the built in logger with something better but nothing that the entire community is using.

I think whatever solution you guys come up with needs to be easily extendable / modifiable to use 3rd party loggers.

from entitas.

Yes, I don't plan to add a logging framework (I already did one, it's open source NLog)
I plan to provide sth to plug into with any logging tool you like

from entitas.

@mzaks what's the state with this?

from entitas.

@sschmid Can add it to the new Plugins structure. Schools I clone develop or wait until the release and make PR on master?

from entitas.

Might be safer to wait for the next release. PR on develop please (default branch)
Does it require changes in entitas? or is it a Plugin?

from entitas.

It is a Plugin. Sending the system will/did execute event schools be figured out though. But it will still be a Plugin

from entitas.

It's been a while :) I saw a working prototype ages ago. Shall finalize this? Whats the state with the web UI?

from entitas.