Identifying Coldbox-specific Functions

I am working on a quite large and complex application that uses Coldbox
(actually it uses Textus - the previous name for Coldbox) and I just
realized maybe a little too late, that when the application gets to
certain size it is easy to get confused by the amount of functions and
method calls that are being used, and when you throw in Coldbox, which
has its own set of functions and methods you get to the point in which
you look at a function and don't really know if it is a method from
your current event handler or from a parent event handler, or from
Coldbox, or even maybe a CF function that u just didn't remember.

For this reason, I would suggest that there should be a way of
identifying coldbox-specific functions (getPlugin, setValue, etc),
something like a prefix (i.e. "cb_setValue()" ) or a common scope (i.e.
"coldbox.getValue()" )

On the initial versions of Coldbox (Textus), all of the framework
specific methods were accessed via a "controller" object, so you had
"controller.getValue()" and things like that - yes, I know how one can
think of it as redundant or even too much to type, but when your app
starts to get large and complicated u really want to know where
everything comes from, and even gets simpler for people that are not
familiar to the framework to realize that there is a family of
functions that go together and are part of the same thing.

Hi Oscar,
you have a very good point. I believe some issues could arise in the
form of backwards compatability, where previous versions are going to
need to find and replace all there methods in order to adhere to the
new methods. Unless they could be sort of aliases to those methods and
slowly deprecated them from the framework???

Any ideas??

I have been going over this for a while now and have a good and clean
solution for this.

Use the "super" scope!! Wallah!!!

So if you want to distinguish the coldbox methods, since you are
implementing a controller via inheritance.
Then use the super.getValue(), super.setView(), etc.

I hope this will give you a good distinguising alternative.