Elephant was providing a Log System, widely used by the whole set of modules. The Log System had also a view where we could see what was going on on our web site. Who entered the system, how many times a file was downloaded, which document was saved or deleted and so on and on. Quite useful, really, because we could follow up the moment something was created, modified or deleted. And who did the action. Yes, and then what? You might think... you go and ask the one who did it what was the deleted content?

We knew what happened but, if this was the case, could scarcely do something to repear it.

Elephant has a complex page construction, element composed and factory driven. Thus, Elephant has powerful configuration grounds and might walk soundly step by step.

To understand what goes on when rendering the HTML, we first need to understand what a page is. One page, one context. One context, multiple layout and content elements. Real world, though, shows that most of times, pages are composed by layout elements spanning site-wide and a single content element. Real life is complex, but follows phisics laws.

I have been disconnected  from this site quite long. It seems that time isn't working the right way with me. You know, the more I'm supposed to understand the more complicated to write about it. Well, this time I made a break and gathered myself in order to put my two cents saying something about Zkoss.

First, I would like you to notice that this goes about web application frameworks. Java Server Faces, Flex, Google Web Toolkit, Wicket and those of that kind. I have stressed most of them in my way of being productive writing web applications. Difficult, let me tell you.