Phritz Homepage :: Forum

Re: Phritz kernel todo [by lan]

Fri, 2 Nov 2007 12:56:19 -0400

Kernel Development:: Phritz kernel todo
Hi,
I�ve only just come across your Framework and it has my interest.

It looks like it has bee quite a while since you have done anything on it and there does not seem to be much attention given to your Framework. Hopefully you have not lost heart.

Regarding your thinking about the view. There is a very interesting article on SitePoint is you have not yet read it. http://www.sitepoint.com/article/beyond-template-engine It talks about how we are thinking wrongly about templates and provides a template class.

I think I will be following the above but I also like the Tinybutstrong template engine although I have not used it yet www.tinybutstrong.com . This one seems to be powerful and absolutely minimises logic in a template.

All the best with this project. I hope you keep at it.

Phritz events [by mrfritz379]

Wed, 27 Sep 2006 21:44:45 -0400

Kernel Development:: Phritz events
Currently, in the source, there's a candidate for a Phritz event management system. I thought about instituting a typical Observer/Observable interface to handle events, but I think I like the idea of a centralized event managent system that allows objects to bind themselves to other objects and their methods. Of course the observable object needs to send a global notification of the event using the PhritzEvent::notify() method. This allows an element of control on the part of the observable regarding which methods can be bound.

The current bind() method allows observers to bind themselves to events triggered by specific objects (using a GUID created at the object's instantiation) or by any object of a given class (including subclasses). The idea is to save a certain amount of passing objects around as parameters as the observer object never has to have 'contact' with the observed object until the event is triggered.

One plan that I have for implementing this interface is to allow the User management system (that hasn't been created yet) to change display themes according to user preferences while running in the backround. It offers a lot of room for customization of the running application without having to modify the kernel. Loaded modules could interact with any of the kernel objects without having to every really have contact with the kernel objects.

Phritz module todo [by mrfritz379]

Wed, 27 Sep 2006 21:31:21 -0400

Module Development:: Phritz module todo
Here's the plan for module development for the Phritz framework.

Currently, there are only two modules in the source-- the db module that has the DAO interface, the DB instance and the PhritzDbObject class. The other module is just the Test module that's up at dev.fritz-works.com.

I'm currently torn between keeping the DB classes in a module or moving them into the core of the framework. Initially, my thinking was that a database is not absolutely essential to a running application. A calculator application shouldn't really need any kind of database instantiation to run simple calculations. Perhaps the database should be moved to the lib directory, still keeping it seperate from the kernel, but not a seperate module.

Other modules that I want to see implemented at some point in the future are many of the basic parts of an application including User management, Session management and Authorization. Ultimately, I'd like to see a PhritzCMS package that would be kind of a meta-package that loads all of the above-mentioned modules. But that's a long way off.