Because so many things have to be changed FireOrb is going to be done in a nightly build process. The function naming system has to be put into place at the same time as development of some other systems like theming are put into place. This means I can change maybe 40 function names while creating a build for say the backend theming or while cleaning up the hook system.

The hook system is going to be the next big change right after getting seperate templates to work for the front and backend. The use of module_invoke_all and some other chaos makes it hard to find out just where Drupal gets its list of available hooks. While this mean flexibility for third party developers it means that core system development becomes incredibly impossible to organize. You can find hook_init and hook_exit quite easily but the rest are hidden in a mish mash of spagetti code, what function implements hook_menu? What about those other critical core hooks where are they started from? . There should be a central array that has core hooks listed. This make it easier to extend the core for both core development and third party development. Having a global containing this array would make things so much easier performance wise. The global can be called and adjusted appropiatly before calling hooks preventing loading of uneccessary modules.

That's enough for now. FireOrb build 0001 is now in the demo area. File releases will come soon after the theming/templating system is complete.

Happy Publishing!

Join Hiveminds and link to your website or blog.