[X] -1 (NO), because :replacing scanpage by "pageContext" does not solve the problem
The problem is to move out SCAN specific code. This code does that.
What you mean is that the processorInterface is not a beautiful and flexibele way to call functions. That is true (IMO), but it is not the problem tackled here.
To deal with ProcessorInterface we need to expand the function framework and entice everyone to use that. Once that is done the ProcessorInterface (and PageContext) can possibly be phased out.
Currently, however, ProcessorInterface is not the issue, SCAN is
-- Pierre van Rooden Mediapark, C 107 tel. +31 (0)35 6772815 "Never summon anything bigger than your head."
