I am planning the dijit module, to use dojo widgets into the HTML pages generated by the Satya Portal Pack. The module will provide a full abstraction of java script over PHP and XML. The developer will simply need to type an XML document according to a particular specification and the page elements will be automatically generated by the module. The dijit elements will allow the auto magic implementation of validation and other effects found in the dijit.

In addition to that, each validation will have a server side code also, so that the validations can be enforced on the java script disabled browsers.

I have defined a new event architecture for Satya Portal Pack. This step was long and tiring one. After much of the thoughts and hit and trials, I have finalised following architecture for event management in SPP:

Events can be fired by module at any place with a default event handler. These events can then be handled by other modules by defining their own custom event handlers. These event handlers can be defined with following occurence types:

1) before: With this occurence type, the custom event handler will be fired before the default event handler.

2) after: Custom event handler will be fired after the default handler.

3) instead: Default event handler will not be fired. It will be completely overriden by the custom handler.

There are two kinds of events in the system:

1) Over ridable Events: These kinds of events can have “instead” handlers. They are fired by SPP_Event::fireEvent() function by passing a default function name as argument.

2) Non Over ridable Events: These events cannot have “instead” handlers. In other words, these events cannot be overridden. These events are started by SPP_Event::startEvent() and ended with SPP_Event::endEvent().

The code for these classes has been committed to the svn, and another alpha release will be soon made with these modifications.