Tid Bits

[John Cox]

I fixed the session issue yesterday, and along the way wrote a log
viewer for the profiler. I realize the profiler isn't much to look at
at the moment, but perhaps this weekend I will be able to get the UI
in the way I have it visualized. I will probably provide a config var
to turn it on and off, and I am thinking of actually calling it from
index.php vice the theme, so it would be available for any theme as
you are working.

A couple of thoughts that I had this weekend:

- Logging is cool, but incomplete. I have started added log messages
through out the core so we can see the execution plan. That's how I
figured out the bug in the cookie.

- Same topic, I do like being able to see the name of the var and the
var that was returned, which logging provides.

- What are events? I think those were added after my time, or I just
wasn't paying attention.

- What do you think about automatic module upgrade / installation etc,
instead of having a UI. Instead of throwing an exception, shouldn't
we just install, etc? I am not seeing the downside, when you figure
by the time something gets to production, we have packed it.

- I am going to change the install process a great bit to get
everything ready for the "pack for production".

- On the roles and perms: you are right, we should change them quite a
bit. A one to one is good enough on a group basis. We can do away
with the individual permission, and the inheritance. They just add
confusion.

- I still like masks though, but that should be the primary code
event.

Can't think of anything else at the moment. I am working on logging
everything in the core, and then the profiler UI, and configuration
UI. I think once I get that in you will have a good idea of what I am
working towards.

TTFN