well, if not using classes it is easy to push messy detail into functions and display the actual logic as sequence of function calls. By messy details I mean the not very readable mixtures of HTML tags and PHP variables. Overhead of many function calls is balanced by the much improved clarity of the application logic.
Before using classes I could banish the many little functions into a separate file and include it - so the primary file was the application logic pure and simple. Now, with classes I cannot do that sort of separation of file content, although I could of course make another class and instantiate it (or use a static class and define something short to avoid writing long classname::xxx() names).
Perhaps subclassing would be an appropriate way to do it - define the utility routines in the superclass and subclass to add the application logic - seems a little strained to just achieve what I want.
Thanks. ...Ian.