ListViewData.php is in view or controller

[rakeshray]

Hi,

As we know sugarCRM is MVC based,
I want to know about file include/ListView/ListViewData.php ,which type of file it is.

it is file of View or Controller ?

At same time i want to put code of file upload . I want to put file upload option in menu.
I want to put the code of file upload in "model" or controller . This code is business logic and not related to database so i think it should be inside controller . So i want to know where i should put this code . I want to put code according to MVC architecture only.
Please any body give me idea how to implement it

Thanks

[rafael.q.g@hotmail.com]

include/ListView/ListViewData.php is a controler, once it make db queries and also haven't any function to write responses ro users it isn't a view. It also isn't a model once it doesn't represents any entity.

This file is used by sugar engine, so is not recommended to do any change here, once this file is used by list view of all modules.

To customize list view for one module you have to customize one of (or both) files:
[custom]/modules/<module_name>/metadata/listviewdefs.php
modules/<module_name>/views/view.list.php

Customizing this files you are able to add new options in your menu and also make many others customzations, been them accoring with MVC (depending also of you business logic implementation), and according sugar framework architecture.

[rakeshray]

include/ListView/ListViewData.php is a controler, once it make db queries and also haven't any function to write responses ro users it isn't a view. It also isn't a model once it doesn't represents any entity.

This file is used by sugar engine, so is not recommended to do any change here, once this file is used by list view of all modules.

To customize list view for one module you have to customize one of (or both) files:
[custom]/modules/<module_name>/metadata/listviewdefs.php
modules/<module_name>/views/view.list.php

Customizing this files you are able to add new options in your menu and also make many others customzations, been them accoring with MVC (depending also of you business logic implementation), and according sugar framework architecture.

Thanks a lot MR. rafael .
As i read in developer guide, model contains code for communication with data base.
Controller contains all business logic except code related to view.
So i think any business logic not related to data base should be in controller.From this point of view code for file uploading should be in controller.
One thing i want to know .. Is SugarCRM is completely MVC based ?
Suppose i am defining a function in custom file in custom module for file upload , then i think it will not be in MVC architecture.

[rafael.q.g@hotmail.com]

The custom files are extentions which allows you to change sugar standard behavior.
For example the two files I listed to you:

[custom]/modules/<module_name>/metadata/listviewdefs.php

modules/<module_name>/views/view.list.php

Both of them theorically are just view files, but you are allowed to customize it the way you want, with your own code.

So, whether do you use this files just for layout stuffs, and for every action you call/request a business object/service to handle that action, it still will be MVC. But whether did you make the bussiness logic directky on these files, it won't be MVC anymore.

There is many ways to separete view from control, one example is using the custom file named Controller.php which could be located on module root folder. This file can have methods to be called by actions invoked from screens.

[rakeshray]

Thank you very much !
I got idea