On 20 Oct 2011, at 00:54, Aparajita Fishman wrote:
fusebox is probably why. With fusebox you know exactly which fuse caused the problem and theoretically there are no side effects so fixing that fuse only fixes the problem. My debugging time went way down when I started using it.
That's exactly what I've found. Where the error is encountered is where the bug is, whereas before I'd have to treck away upstream to find the real source of the problem.
While I'm on the subject of efficiency, I've started using the 'poor man's class'. What an absolute gold mine that is ! - if ever there was a misnomer...
I started off just wanting something to wrap a collection with. Then I realised you can hide code-driven behaviours in it. My customer has requested a more open environment for their content developers to work in, where they can ideally work on some of the active pages. The 'poor man's class' is just the perfect tool for supplying them with a consistent looking API into the properties and functions of the site.
Peter _______________________________________________ Active4D-dev mailing list [email protected] http://list.aparajitaworld.com/listinfo/active4d-dev Archives: http://vasudev.aparajitaworld.com/archive/active4d-dev/
