refactoring the halo namespaces

[Beau Simensen]

While working on Halo this evening I decided that there are more than enough classes in Halo to warrant namespacing them better. I started on the view classes (since that is where I was working) but over the next few days I am going to try to rename things where appropriate.

In some cases I am considering leaving things as they are. Candidates for this:

• halo_HttpRequest
• halo_HttpResponse
• halo_ModelAndView
• halo_Dispatcher
• halo_DispatcherUtil
• halo_IController

Other suggestions are welcome. :)

If I decide to move these, I may leave them in place and deprecate them slowly over time.

--

Beau D. Simensen


Dragonfly Development Inc
http://dflydev.com/

[aek]

you could restructure the halo folder project without changing the
class name for example:

--halo
----examples
----view
--------skittle

and would be more like packages

[Beau Simensen]

That is an interesting idea. I'll consider it but I think for now I think I'll stick with the flat structure (all in the same directory) just to simplify the class loading process from Substrate. Once renamed ( to things like halo_handler_IHandlerMapping ) I can look at breaking them up into PEAR style directories (like halo/handler/IHandlerMapping.php ).

--

Beau D. Simensen


Dragonfly Development Inc
http://dflydev.com/

--
You received this message because you are subscribed to the Google Groups "Halo General Discussion" group.
To post to this group, send email to halo...@googlegroups.com.
To unsubscribe from this group, send email to halo-php+u...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/halo-php?hl=en.