X-Cart forums

[codegrunt]

Howdy. I am finding it hard to get my head around the naming methodology in X-Cart 5.2. I am missing something fundamental I think.

Here is an example. . .

The core view that is responsible for actually running the search and then displaying product search results is:

classes/XLite/View/ItemsList/Product/Customer/ACustomer.php

I understand that this is a product specific itemlist under the customer scope. What I do not understand is why this view is called "ACustomer.php". Why is this not handled in "Search.php"?

As a general question, what is the significance of the "A[object].php" naming scheme? How do you predict which physical class file is responsible for a given view?

Any help appreciated.

[cflsystems]

A[object].php is AbstractObject.php. This class is not intended for direct use. The search class you are looking for will extent this one as well as other classes so the A[object].php class will have more common methods to be reused from other end classes

[qualiteam]

In X-Cart there is a lot of places that display different kinds of product lists. All these lists share some common logic that is implemented by this ACustomer class. And for each list there is its own class (extended from ACustomer) that adds the bits specific for that particular product list.

[codegrunt]

Thanks Alex, Steve. Duh for not connecting "Abstract" to the "A" prefix.