Lembro que no Conaphp de 2008 surgiu uma discussão forte sobre o MVC. Quais os papeis do model, do view, do controller, etc. Acontece que dependendo da região e da cultura dos programadores, os conceitos variam.

Tem gente que coloca regra de negócio no controller, tem gente que coloca script de validação no model… Não há meios de julgar o que é certo e o que é errado, pois todas as normas (inclusive as oficiais ultra secretas – leiam-se caras pra burro – ABNT, IEEE e cia) são seguidas somente pelos profissionais que DESEJAM segui-las.

Eu penso que você deve dançar conforme a música. Se você trabalha numa empresa que segue normas rígidas, que obriga você a ler, aprender e seguir essas normas determinadas, veja essas normas como boas práticas que vão garantir com que seu trabalho não pereça após a implementação e que alguma outra pessoa vai poder realizar manutenção e adicionar novas funcionalidades ao seu sistema no futuro. Sem contar a iminente possibilidade de você ser demitido por insubordinação, desorganização e outros…

Porém, academicamente falando, um padrão mínimo deve ser seguido.

Quando se trabalha com Zend Framework, por exemplo, segue-se a seguinte referência, sem direito a discussão:

• Model – Esta é a parte de seu aplicativo que define sua funcionalidade básica através de abstrações. Rotinas de acesso aos dados e regras de negócio poderão ser definidas aqui.
• View – Views definem exatamente o que será apresentado ao usuário. Geralmente os controllers fornecem dados para que cada visão possa renderizar de forma humanamente inteligível àqueles que utilizam o sistema. Views irão frequentemente obter dados do usuário. Normalmente é aqui que você irá encontrar código HTML nos seus aplciativos MVC.
• Controller – Controllers são responsáveis por manter a unidade do conjunto. Eles manipulam models, decidem qual view será apresentada para o usuário e, entre outros fatores, fornecem os dados necessários ao view para a renderização da tela dinâmica que será apresentada. Também repassam responsabilidades para outros controllers em algumas situações específicas. A maioria dos experts em MVC recomendam que os controllers sejam mantidos o mais enxuto possível.

Obviamente, há muito mais a ser dito sobre esse padrão, porém essa pouca informação já é suficiente para que qualquer desenvolvedor possa ter uma noção básica sobre a teoria do MVC no desenvolvimento de aplicativos.

O aprendizado por trás disso diz que tudo é relativo. Que os conceitos variam de um lugar para outro, porém diz também que você DEVE seguir as normas, sejam elas quais forem, quando for desenvolver utilizando o padrão MVC.

um abraço,

Diogo Besson

Hey guys, If you’ve any experience of zend we’d love to have your comments. Either email them in or leave them as comments

thanks!

Primul gand pe care l-am avut cu totii in echipa a fost “in ce codam”. A fost usor sa trecem prin cei cativa termeni, care ne mai trecusera pe la ureche, si sa alegem Metoda aia *usoara* prin care tot ce era desenat pe hartie si gandit, sa devina realitate… web. La fel de usor a fost sa incercam sa scriem primele linii de cod mai complicate ca sa ne dam seama ca trebuie sa si gusti inainte sa mananci. Si ca sa trecem in planul concretului ne-am gandit la 3 metode de a face paginile sa fie dinamice (adica sa integram o comunitate, sa avem pagini context sensibile) : un framework, un cms sau php de la 0.

La capitolul framework, am constatat ca este destul de popular codeigniter (http://www.codeigniter.com) si dupa vizionarea a exact doua tutoriale video cu tot cu incercat cod, am fost convinsi ca si noi putem sa dezvoltam un intreg website in 20 de minute (precum video-ul arata un blog gata in tot atatea minute). Problema cu un framework este dificultatea de a intelege cum lucreaza bibliotecile, ce trebuie sa incarci si ce module fac ceea ce zic ca fac. O problema cu care m-am  confruntat personal a fost o simpla logare. In primul rand nu exista modulul gata facut de autentificare ci trebuie supraincarcate anumite clase. In al doilea rand, voiam sa ma folosesc de cunostintele, de baza, de PHP, insa constatam ca pana si sesiunile sunt vazute altfel. Concluzia noastra este ca un framework se studiaza intai. Avantajul, totusi,  al unui astfel de framework este modelul MVC care personal mi s-a parut intuitiv si foarte aplicabil.

Frameworkul Zend a fost inca o propunere, laudat fiind si pentru ca php are module zend, insa nu am reusit sa trecem de configurarea acestuia.

Punctul doi in aceasta discutie, ar fi un Content Management System. Din pacate, tema aleasa nu se preteaza la o astfel de abordare. Sigur ca putem scrie module php pentru CMS, dar intervine si aici problema studierii sistemului. Am fi mers ori pe Joomla ori pe WordPress, care vin si cu un design gata facut si customizabil (mai putin la WordPress).

Solutia numarul 3 ne avantajaza cel mai mult, php de la 0.  Cateva minute pe w3schools si doua trei exemple de lucru cu baza de date face ca PHP sa nu para o necunoscuta. Exista mii de linii de sample code utilizabil si customizabil, apoi reutilizabil in cadrul aceluiasi proiect. Suntem obisnuiti sa codam in C, Java, Scheme, Haskel, Prolog, CLIPS chiar si Verilog, limbajul nu este o problema.  De asemenea partea de control (administratorul) nu trebuie sa fie extrem de complex, noi construim sistem, stim cum merge. Singurul dezavantaj este securitatea care s-ar putea sa ne dea batai de cap.

Cam atat pe partea de programare pe server.

Hi Friends,

Few days ago I was surfing on net to find the solution about jquery, I didn’t get the exact solution. But I found one good article which I would like to share with you.

It was about “Five tools every PHP programmer should know about”. Below are those five tools:

1) Phing – a project build system
2) Xdebug – debugger and profiler tool
3) PHPUnit – unit testing framework
4) Propel – object-relational mapping framework
5) phpMyAdmin / phpPgAdmin – web-based database administration

Thanks !

Hi Friends,

Few days ago I was surfing on net to find the solution about jquery, I didn’t get the exact solution. But I found one good article which I would like to share with you.

It was about “Five tools every PHP programmer should know about”. Below are those five tools:

1) Phing – a project build system
2) Xdebug – debugger and profiler tool
3) PHPUnit – unit testing framework
4) Propel – object-relational mapping framework
5) phpMyAdmin / phpPgAdmin – web-based database administration

Thanks !

If your web site contain a huge number of pages and corresponding level of difficulty in keeping track of all of them, your organization rely on constant and regular web site changes, often with several people working on it and your web site contributors lack sufficient knowledge in HTML and also you need to editorially review each new page before publication. When you are using a CMS will save a lot of time, hassle and money in the long run.

A Content Management System, or CMS for short, is a collection of procedures used to manage work flow in a collaborative environment. These procedures can be manual or computer based. Or in other word, CMS is an administrative software system that allows its users, often unskilled in HTML and web development, to update, edit and create new pages on their website.

In a CMS data can be defined as almost anything – documents, movies, pictures, phone number, scientific data, etc. CMSs are frequently used for storing, controlling, revising, and publishing documentation. Content that is controlled is industry-specific. (Entertainment content differs from the design of a fighter jet). There are various terms for systems (related processes) that do this. Examples include: Web Content Management, Digital Asset Management, Digital Records Management, Electronic Content Management (and others). Synchronization of intermediate steps, and collation into a final product are common goals of each.
Basic of a CMS

A typical CMS works like these; a web design layout is designed and developed. Usually this entails a logo/banner at the top, standard navigation menus across the top, down the left side, and/or at the foot of the page, and a ‘blank’ area where content is inserted, this layout format is then converted into a master template for all subsequent pages. During the process of this conversion, the CMS admin backend is integrated and tested. Web content producers are given access and instructions on how to add text and images to web pages automatically. Most CMS are usually very intuitive and easy to operate. and each generated page is saved onto a database, for future editing or deletion. More elaborate CMS can perform unique functions (such as archiving, built-in search engines, and mod rewrites), but basic functionality is still related to easy creation and editing of web pages.

Types of CMS

• Proprietary CMS
  These systems are usually very expensive to purchase such as the $500,000 and up Vignette system. These high end systems however come loaded with full features and usually have excellent customer and technical support. Common uses of these systems involve very large organizations with departments that require unique functionality.
• Open source
  These systems are typically free and relatively easy to install. Some of the better known open source systems include Mambo and Drupal. Because of its open source nature however, you will find a dearth of customer and technical support, however there exists a huge following and forums dedicated to the popular systems. Customization capabilities vary from system to system. Be sure to do all the necessary research before deciding on one.
• Custom CMS
  These types of systems are usually preferred as they allow you to develop from scratch, your preferred functionality. Debugging is also less of an issue as your web developer, having written the codes, can easily isolate and fix problems. Bear in mind there are literally hundreds of CMS to choose from. Ranging in costs from free to over $500,000. What you do need to do, is firstly figuring out exactly what functionality your organization needs, your development budget and finally find a system that suits those needs best.The downside to installing a CMS is of course, the amount of web development needed initially. While you are able to obtain free open source CMS programs, you still need to hire someone experienced and capable enough to integrate it correctly. This initial expense however, is usually a necessary evil and is justified as you avoid the need of hiring or outsourcing your webmastering needs down the road.

Ultimately a CMS is meant to make life easier, not creating new rigid standards that require stop gap hacks or workaround solutions.

copas from Globaltor – About Content Management System And Relation With Your Business Needs

今天我在使用 gdata(來自 PHP Zend framework) 嘗試存取一段youtube video的影片的時候遇到了標題的error. 我使用了半個小時設定一個正確的 InstalltionChecker.php, 先排除我的伺服器已經裝有 php-xml libraries, ssl libraries, 但仍然無解. Google 沒有提供一個合用的答案.

最後我發現, 是youtube 判定該 video 違反了某些版權協定, 所以返回了 400錯誤碼, 正解是:

<?php
try {
  $yt = new Zend_Gdata_YouTube();
  $videoEntry = $yt->getVideoEntry($key);
} catch(Zend_Gdata_App_HttpException e) {
  //handle error
}
?>

Today i encountered the above error when i am trying to fetch youtube data given the video id using PHP Zend framework suggested by google. I had made half an hour top setup the InstallationChecker.php, which shows the installation had no errors. I further debug using xdebug, cross check php-xml libraries, ssl libraries on the server, but no clue. Google do not provide a solution.

In the end, youtube banned the video because of copyrights, but just throw a response code 400… to solve it:

<?php
try {
  $yt = new Zend_Gdata_YouTube();
  $videoEntry = $yt->getVideoEntry($key);
} catch(Zend_Gdata_App_HttpException e) {
  //handle error
}
?>

Click here to see more on Zend’s training and certification – You can also get 10% off training with this link

A sample answer to the Zend exam?

Zend offer comprehensive training to go with the Zend Framework and Zend Studio. You can get a year of support with an online training package together from zend (click above for more info). You can also take Zend PHP 5 Certification exams, and their course of the fundamentals of the Zend framework. Zend training is provided on certain dates through the online meeting tool WebEx, supplying training in real time. You will need to take your zend training course online within year of purchasing.

Zend Server is web server designed with a extremely efficient processing of PHP and the php based Zend Framework in mind. Zend Server community edition is free and has a complete stack just for php that can run non-critical applications very efficiently. It is easier to install than some other webservers without a company backing the install pricedure. The paid for Zend Server is more appropriate for crticial enterprise level applications that require rigorous code testing and full Java connectivity.

The Zend frame work is an open source oop framework that is run on PHP 5. It is licensed under the commercially friendly New BSD License to make it appropriate for buisienss use. It was started in 2005 to compete with existing web frameworks such as Ruby on Rails and has quickly grown, with Zend.com now reporting over 10 million downloads. The support has also quickly grown to what you would expect from an enterprise level framework, with a 1000+ page reference guide and over 500 examples. The Zend framework has a learning curve that is simliarly quick to that of PHP, developers can fall back into standard php when required and standard design patterns such as MVC are supported but not required.

The Zend Server is also available to allow you to run the Zend Framework with native OS support and caching optimisations; though the Zend framework can run on other servers such as Apache, the Zend server provides optimisations such as opcode support for quick execution at the native level. Zend studio provides easy generation of MVC code generation and tightly integrated editing for rapid development of Zend framework applications. Zend Studio costs, in contrast to the Zend Framework itself and the community edition of Zend Server which are both free.

All code that is merged into the main branch of the Zend Framework requires unit tests that cover 80% of the code meaning any stable branchds are very stable.

Estou fazendo pesquisa sobre Zend Framework + PHP

A seguir posto links relevantes:

Comunidades e sites sobre PHP:

• PHP Brasil
• PHP Mania
• Revista PHP
• Site oficial do PHP

Comunidades e sites sobre Zend:

• Zend Brasil
• Site oficial do Zend
• IDE Zend Studio
• Zend Framework
• Instalando o Zend no Windows

Livros sobre Zend:

• Zend Frameword em Ação
• Zend Frameword: Desenvolvimento em PHP Orientado a Objetos com MVC
• Guia de Programação com Zend Framework

Apostilas sobre PHP:

• Apostilas em .zip

Artigos sobre Zend:

• Frameworks no PHP O que, quando, por que e qual?
• Zend Framework – Uma visão geral
• Flex e PHP com Zend

Lembrando que para desenvolver Zend você deve conhecer de programação, orientação a objetos e php.

Durant mon passage en tant que développeur dans une agence multimedia dans le cadre de mon stage de fin d’étude, j’ai pu acquérir des connaissances et surtout j’ai pu apprendre à utiliser un nouvel outil(Et oui!! nouveau pour moi^^) le Zend framework mais y a aussi CakePHP qui utilise encore PHP 4. bon j’aime pas trop parler, je vous laisse voir ce comparatif qui est très instructif. Bonne lecture;))>COMPARATIF

First things first; I’m not a Zend Framework guru at all! One could rather describe me as PHP enthusiast who is working REALLY hard to learn ZF together with its hard-to-understand MVC philosophy.

I have already installed ZF on different platforms, beginning from my HP laptop based on a dual-core AMD processor, up to a shared host at Media Temple. This is just the start of a adventure…

Stay tuned, I’ll be back very soon.

Julian just came with a detailed tutorial of how to install Zend Studion on the 64 edition of Ubuntu.

It has both solutions, installing the normal version and the 64 version of Zend Studio.

Check it out: http://www.smooka.com/blog/2009/11/02/installing-zend-studio-on-ubuntu-64-bit/

Acabo de confirmar que 3 desarrolladores, ingenieros PHP certificados por Zend, trabajarán en Dokeos a partir de la próxima semana, para mejorar la calidad de nuestros servicios sobre dokeos. Es para mi un placer y un honor de tener un conjunto de mentes tan brillantes reunidas en una sola empresa. Solo existen 5 ingenieros Zend en Perú.

Sin aprovechar para descansar, estaremos preparando, este mes, el programa de curso para preparación a la certificación Zend, para el cual Gary Rojas, el cuarto y último certificado en PHP5, ha acceptado desde ya de combinar esfuerzos con nosotros.

Con este cuadret fantástico, estaremos brindandoles el mejor curso “all times” de PHP que pudió ser organizado a fines de prepararles en la certificación de Zend aquí en Lima.

Más sobre esto más tarde… Si están interesados, por favor dejen nos un comentario.

Hi Friends,
To day i brief you about ZF. So now we start

What is ZF
Zend Framework is a simple, straightforward, open-source software framework for PHP 5 designed to eliminate the tedious details of coding and let you focus on the big picture. Its strength is in its highly-modular MVC design, making your code more reusable and easier to maintain. Develop by Zend (the PHP company).

Features of ZF
Zend Framework features include:

• All components are fully object-oriented PHP 5 and are E_STRICT compliant
• Use-at-will architecture with loosely coupled components and minimal interdependencies
• Extensible MVC implementation supporting layouts and PHP-based templates by default
• Support for multiple database systems and vendors, including MySQL, Oracle, IBM DB2, Microsoft SQL Server, PostgreSQL, SQLite, and Informix Dynamic Server
• Email composition and delivery, retrieval via mbox, Maildir, POP3 and IMAP4
• Flexible caching sub-system with support for many types of backends, such as memory or a file system.

References
#http://www.zendframework.com/about/overview
#en.wikipedia.org/wiki/Zend_Framework

One thing I like about Zend, is the option to let it build your forms for you. You can mix and match form elements just as you would with regular objects and in the end, let Zend build the form for you. You can use regular textboxes, radio buttons, submit buttons, etc and even the occasional date picker is not a problem if you are using Zend X.

One thing that was giving me some problems though, was displaying error messages. It is always nice to give good feedback to your users with a nice, meaningful message about what was wrong with the input they provided.

To accomplish this, I build the form, consisting of a first name, infix, last name and email address.
Before reading on, I must mention that wordpress screwed up my code formatting, but your IDE should be able to make something good out of it.


$this->setAction($this->_actionUrl)
->setMethod('post')
->setAttrib('id', 'signupform')

$this->addElement('text', 'firstname', array('label' => 'First name'));
$username = $this->getElement('firstname')
->addValidator('alnum')
->setRequired(true)

$this->addElement('text', 'infix', array('label' => 'Infix'));
$username = $this->getElement('infix')
->addValidator('alnum')
->setRequired(false)

$this->addElement('text', 'lastname', array('label' => 'Last name'));
$username = $this->getElement('lastname')
->addValidator('alnum')
->setRequired(true)

$this->addElement('text', 'email', array('label' => 'Email address'));
$email = $this->getElement('email')
->addValidator('EmailAddress')
->setRequired(true)

$submit = $this->addElement('submit', 'Signup');


I can now stick this into my views using:
Controller:
$form = new SignupForm('/user/signup');
$this->view->form = $form;
View:
<?php echo $form; ?>
Refreshing the page should now give you a simple form with a submit button. This form does nothing now though, and we could use some interaction at the end:
public function signupAction() {
$form = new SignupForm('/user/signup');
if ($this->_request->isPost()) {
if ($form->isValid($this->getRequest()->getPost())) {
echo "Congratulations, your form validated";
}
}
}
As you can see here, we are actively checking if the form was indeed valid. Remember the validators we added to the form? The Zend Form is smart enough to iterate over the elements with values from the POST and decide whether or not the input is valid. It doesn’t stop there though, it continues iterating until the end, all the while collecting error messages from the validated input.
Before displaying what was wrong with the user’s input, we must first add these messages somewhere. We add them to the form, as that is where they belong:
$this->addElement('text', 'firstname', array('label' => 'First name'));
$username = $this->getElement('firstname')
->addValidator('alnum')
->setRequired(true)
->addErrorMessage("Something was wrong with your first name");

$this->addElement('text', 'lastname', array('label' => 'Last name'));
$username = $this->getElement('lastname')
->addValidator('alnum')
->setRequired(true)
->addErrorMessage("Something was wrong with your lastname");

$this->addElement('text', 'email', array('label' => 'Email address'));
$email = $this->getElement('email')
->addValidator('EmailAddress')
->setRequired(true)
->addErrorMessage("Something was wrong with your email");

These messages could be nicer and could even be retrieved from a language table if you want. You could also add messages that are returned depending on what kind of validation went wrong.
For now, let’s leave it this way and display the messages to our user:
if ($form->isValid($this->getRequest()->getPost())) {
// Your validated form code
else {
$messages = $form->getErrors();
$this->view->formResponse = $messages;
}
This was what stomped me a little in the beginning. The form has a method called getErrorMessages() and since we added the messages to our form elements using addErrorMessage(), it seemed only logical to retrieve these with aforementioned method. For reasons unknown to me, the Zend team decided it was best to use getErrors().

Feel free to make this prettier and perhaps trow in some AJAX to make this more dynamic.

In partnership with Marco Tabini and Associates (MTA) (php|architect; CodeWorks; php|tek), we are excited to announce the launch of The Great PHP on Windows contest. Do you have what it takes to win? Of course you do .

You are encouraged to leverage existing open-source libraries and applications, including blogs engines, forums, photo galleries and other platform/components as part of your submission.

For complete details visit http://phparch.com/win

The Quick Summary:

• Write a new application designed to run in PHP on Windows using IIS—or make a significant contribution to an existing open-source project along the same lines
• The best application, selected jointly by a panel of experts and by our readers, will win a grand prize
  which includes a 52″ Digital HD home entertainment system, as well as an all-expenses paid trip to php|tek 2010 in Chicago. Runner-up prizes include 2 XBox 360 Ultimate and subscriptions to php|architect.
• Not familiar with Windows? No worries—we have partnered with Applied Innovations to give you absolutely free hosting on a pre-configured virtual machine for the duration of the contest.
• Registration and submissions for the contest will be accepted October 19^th, 2009 through February 28^th, 2010 and with judging and public voting will occur March 1^st – 31^st.
• For the duration of the contest, Applied Innovations will provide free web hosting to all participants (shared) and a free VM to the first 60 participants who register.
• Contest is open to all U.S. residents excluding MTA, Applied Innovations, and Microsoft employees and affiliated individuals. (MTA is the official sponsor with AppliedI and Microsoft as promotion entities.)

The contest is open to residents of the United States only—but you can still win by voting, no matter where you are.

 Good Luck!