I want to share my thoughts about using or not Views module against custom query code. Although I consider it a must-have module if you plan to do things quickly and don't wanna mess with code, from a developer point of view it seems that you lose some control over the final result.
When I look at Views Documentation it seems that is incomplete, and if I later try to reverse engineer the views code to clarify things, it turns worst because of the complexity of the module. The footprint it's to long and it seems that it breaks the drupal way rules for the module design.
So it seems for me that is a trade-off between rapid-development and control.
Let me clarify that by no way I'm saying that I feel that the Views module isn't good. I think it is great!, but (AGAIN) from a DEVELOPER POINT OF VIEW is kind a mess to grasp.
Let me know if someone share my thoughts or not, I will really appreciate your comments.
Comments
If you mean write modules
If you mean write modules that can do complex queries - sure. I am pretty good at writing sql and sometimes the limitations of views ui can be frustrating.
If you're saying doing simple queries takes too long using the views ui, I would offer that you need to spend more time learning it. With views you can export your work to code so that it is not in the database and is portable.
The important thing is to remember that there rarely is a "one of" situation. It's almost always better to write code that is reusable and portable.
I am running in to a similar
I am running in to a similar problem. The Views API documentation feels incomplete or inadequate. Maybe the problem is between the desk and the chair, but I haven't been able to figure out an answer to the problem that I posted earlier this morning. I've been looking on my own for over a week before asking for help.
http://drupal.org/node/955920
Web Developer, Iowa State University College of Veterinary Medicine