I love the power that Prado brings to the table in terms of its similarities with .NET and the unique MVC architecture that it uses (which is a markedly different approach than what most PHP frameworks use) but in my opinion Prado has grown far too fat and obtuse. I love the concept - in my mind it makes the best approach to code readability - completely separate markup and code, and code is blocked off into events. I wrestle with the evils of procedural programming every day that I work in PHP - yes, I know that it is technically an "object-oriented" language but in reality your scripts execute top to bottom and you can simply inject instances of objects along the way.
For example, look at this markup from PRADO.
Code: Select all
<com:TButton ID="Button1" Text="Click!" OnClick="sayHello" />Code: Select all
<?php
class Home extends TPage
{
public function sayHello($sender, $param)
{
$sender->Text="Yello!";
}
}Having your markup represented as accessible objects in your code-behind is the perfect situation for me. This way I can actually separate my code from my markup and if I need to change something I can simply access the object, modify a property, and be done. .NET does this nearly flawlessly and Prado's made a fine effort at duplicating it, but the model has grown a bit to complex for my tastes, hence, my own framework which takes the best of Prado and leaves out the unneeded fat.