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.

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/

Ei bine, guess what – Zend Rullz!

Avand in vedere lipsa documentatiei pe tema Zend Framework, care lipseste cu desavarsire pe veb-ul romanesc (e doar o afirmatie a carei natura ‘booleana’ nu o stiu, nu am cautat, nu voi cauta, zend.com are tot ce imi trebuie), m-am hotarat sa fac ceva gen “Cum sa incepi sa lucrezi cu MVC-uri, mai exact cu Zend, care rullz!” imbinat cu “Inveti odata cu mine, invat odata cu tine” si cu “Exemple din Zend Framework + alte chestii practice”.
Evident, pentru multi povestesc aici abureli… like wtf? cine ar vrea sa stie ceva despre MVC-uri?! Ei bine sunt convins ca sunt o gramada acolo. Si desi zend.com ofera tot ce ar avea nevoie, trebuie sa ai putin capu’ mare la unele chestii, foarte multa ambitie si sa nu dormi ceva mai mult timp daca chiar vrei sa faci ceva cu el. Toate astea insa lasati-le pe mana mea.

Cu ocazia acestui post fac o noua categorie – Zend, unde voi pune tot ceea ce tine de Zend Framework, Zend MVC, Zend Studio etc.

Zend studio the boss PHP editor.

Here are some of the useful keyboard shortcuts for you

Editor

* Ctrl + D Duplicate Selection
* Ctrl + E Erase Line
* Ctrl + Space Show Code Completion
* Ctrl + Shift + 4 Collapse All DocBlocks

* Ctrl + Shift + 9 Collapse All DocBlocks
* Ctrl + Shift + E Expand All Folds
* Ctrl + Shift + C Collapse All Folds
* Ctrl + Space + Shft Show Function Arguments

* Ctrl + Shft + F Reformat Code
* Ctrl + / Add Remove Comment
* Ctrl + / + Shft Add Remove PHP Block Comment
* Ctrl + Enter Break Tag

* Ctrl + Back + Quote NBSP Tag
* F1 Open Function Help

Code Folding

* Ctrl + Shift + 1  Collapse All Non-PHP
* Ctrl + Shift + 2  Collapse All Classes
* Ctrl + Shift + 3  Collapse All Functions
* Ctrl + Shift + 4  Collapse All DocBlocks
* Ctrl + Shift + 9  Collapse All DocBlocks
* Ctrl + Shift + E  Expand All Folds
* Ctrl + Shift + C  Collapse All Folds

Debugging & Profiling

* F8 Debug URL
* F12 Profile URL
* Ctrl + F5 Run
* F5 Go

* F10 Step Over
* F11 Step Into
* Shft + F1 1 Step Out
* Shft + F5 Stop Debug

* Shft + F10 Go to Cursor
* F9 Toggle Breakpoint
* Shft + F8 Add Watch
* Ctrl + Alt + B Show In Browser

Find/Replace

* Ctrl + F Find
* F3 Find Next
* Shft + F3 Find Prev
* Ctrl + H Replace
* Ctrl + Alt + F Find In Files

CVS/Subversion

* Alt + U Update
* Alt + C Commit

Tools

* Alt + Ctrl + A Analyze Code
* Ctrl + Shft + I Check Include Files

Zend Studio, as you all must be aware, is a full featured PHP IDE. It does require a little setup so your Run/Debug experience is painless (after all, that is the true reason for using an IDE!).

The following assumptions are made:

1. You are running a linux OS
2. You already have a (working) LAMP setup on your workstation (http://localhost takes you to the homepage)

Here’s the process I used to setup zend studio on my system:

1. Download Zend Core. This is REQUIRED for setting breakpoints and debugging web pages. Select “Zend Core V2.5(Win/Linux)”.. Be sure to select either 32 bit or 64 bit depending on the version of OS/apache2 installed.

Install the software (I prefer to be in “su” mode for all install operations).. Copy the downloaded tar file to the /opt directory. Then, run the following commands to install it..

root@ubuntu:/opt# tar -zxvf ZendCore-2.5.2-linux-glibc23-amd64.tar.gz
root@ubuntu:/opt# cd ZendCore-2.5.2-linux-glibc23-amd64
root@ubuntu:/opt/ZendCore-2.5.2-linux-glibc23-amd64# ./install -g

the “-g” option does a graphic install.. Please refer to the instructions (pdf) in the downloaded file. I selected the “Modify apache” option only. You do not require any other components installed.
You will  be prompted for the location of apache on your computer. For some reason, the installer could not autodetect my main web folder (/var/www).. I entered it into the text field provided. A new directory /usr/local/Zend will be setup with appropriate directives in the apache2.conf file.

2. Download and Install Zend Optimizer. Be sure to select the 32/64 bit version depending on your OS. Zend Optimizer enhances the running speed of php apps. The ZendCore front-end requires this to be installed. Since it is free, we do not complain!

Copy the download file over to the /opt directory
Uncompress/extract the file (tar -zxvf same as in step 1)
Navigate into the directory that is created
Run the install script by using “sudo ./install”
You will be prompted for the location of apache, php.ini file etc (it is a graphic installer).. finally it comes back with a confirmation that the setup is complete.

Now, you should be able to navigate to http://localhost/ZendCore and view your server in GUI goodness. Running phpinfo() should display the Zend Optimizer as being installed like so:

3. Now, onto the task of actually setting up Zend Studio. By default, the ZS sets up a default workspace in your home directory:
/home/username/Zend/workspaces/DefaultWorkspace

Projects that you create will be created in subfolders under this directory. Now, open up Zend Studio and create a new php project (file->new->PHP project). Give the project a name (phptest) and accept the default workspace.

Create a new php file inside the project (right click on project, New->php file).. Name it index.php
Put the following lines in index.php.. It simply displays the php setup on our system:
<?php
phpinfo();
?>

We are ready to test/run/debug our sample application. Before we can do that, we need to make the directory accessible from the web directory. The easiest way to do that is to open the file browser by typing “sudo nautilus” on the console window, navigating to the phptest folder, right clicking and selecting the “Make link” like so:

This action will create a symbolic link to this folder in the same subdirectory. Go ahead and copy this folder link to the /var/www folder (this is the default web folder setup once apache is installed. Rename the sym link to “phptest“.

Thats it! Now, we are ready to run our php file within the Zend framework.. Click on the “Run” button.. Select “PHP web page”
Next, you will be prompted for the Launch URL which in this case is http://localhost/phptest. You should now be able to run any php web app (including Zend Framework applications), set breakpoints, watch variables etc..

Dla potomnych jak utworzyć projekt W Zend Studio 7.0 tak, aby posiadał cały szkielet aplikacji ZF.
1) jeżeli nie mamy skonfigurowanej zmiennej środowiskowej do php.exe, najprościej przeedytować ostatnią linie w pliku :\Katalog_Zenda\bin\zf.bat, aby wyglądała:
:\katalog_z_php\php\php.exe -d safe_mode=Off -f :\Katalog_Zenda\bin\zf\bin\zf.php — %*
2) wykonać polecenie zf.bat create project nasz_nasza_projektu
3) skopiować powstałą strukturę pkików i katalogów w docelowe miejsce
4) w Zend Studio wybrać File -> New ->Zend Framework Project
5) wybrać “Create project from existing source”, wskazać miejsce docelowe wybrane w 3)
6) wybrać “Zend Framework default project structure” lub “Full..”

Chłopaki z zenda obiecali, że w finalnej wersji ma się to już samo robić z wykorzystaniem zend toolsów.

Do testów, polecam na początek, w celu uniknięcia straty czasu na poszukiwaniu dziury w całym, dodać w index.php, na samym początku:

error_reporting(E_ALL | E_STRICT);
ini_set('display_errors', 'On');
ini_set('display_startup_errors', 'On');


oraz zmianić linię :

defined('APPLICATION_PATH')
|| define('APPLICATION_PATH', realpath(dirname(__FILE__) . '/../application'));


na linię:

defined('APPLICATION_PATH')
|| define('APPLICATION_PATH', realpath(dirname(__FILE__) .'/../').'\application');


Do pliku configs\application.ini w sekcji “production”:

resources.frontController.throwExceptions = 1
resources.frontController.disableOutputBuffering = 1

I have been working with the Eclipse PDT editor for quite a while now and it impressed me so much that it became my primary editor.

I have worked with Dreamweaver, Zend Studio (this is another extreme great product), Notepad, Edit+ (you should have it – is a life savier) and so many others, but the Eclipse PDT provided me enough tools to work with Zend Framework, core PHP related development, JS scripts, CSS and XML (which is pretty good).

There is a big drawback dough. If you are using Linux (Xubuntu in my case) you should download the Eclipse PDT from their site and not using any installer, since the versions that they have will break with current java versions.

Besides that, is a great FREE PHP editor.

http://www.eclipse.org/pdt/

I always try to help any organization that is development related and will be doing some conference or some event, so…

Eclipse Con 2009 - Santa Clara, CA

En lo laboral ha sido un año de cambio, de profunda transformación. Se han dejado atrás unas herramientas para apostar por otras.  A destacar:

• IDE: se queda en el camino Dreamweaver para pasar a Zend Studio for Eclipse (ZSE) + Aptana. Un cambio brutal para mejor. La integración de ZSE con subversión (SVN) ha sido el cambio más impactante para mí. Aptana para la maquetación web también promete, así como la gran variedad de plugins de Eclipse como el OrangeVolt para XML.
• Zend Framework: en el trabajo hemos apostado por este framework para PHP. Hasta ahora estamos encantados. Tiene un montón de componentes que pueden usarse de manera individual. Particularmente me han gustado el Zend_Translate, Zend_Feed y la gestión de URL amigables con el objeto Router.
• Proyectos multi-idioma: me ha tocado enfrentarme a páginas multi-idioma teniendo que hacer uso de las correspondientes herramientas. Empecé con el Heartsome Translation Suite con sus TMX, que está muy bien pero es de pago. Ahora miraré el Poedit, que es gratuito y ofrece prestaciones similares. Creo que los adaptadores de Zend_Translate permiten el uso de ficheros .po
• Proyectos en local para desarrollo. La idea de trabajar en local con XAMPP hace que se desarrolle más rápido. Un problema que encuentro con esto es que por lo general las versiones de PHP y APACHE de XAMPP son muy modernas mientras que las de los servidores de producción son antiguas. Uno puede estar desarrollando en local cosas que luego no funcionen en el entorno de producción.
• Diseño: quedó atrás el Blueprint para trabajar con CSS nativo. Gracias a mi compañero de trabajo Jorge que me ha aconsejado, dejo atrás los pesados frameworks de CSS para trabajar directamente la maquetación con CSS. Al final, haciendo un buen uso de los floats no es para tanto y se gana en performance.
• Dos monitores y algo de RAM: fundamental para el trabajo diario. Los dos monitores facilitan el trabajo con varias ventanas. Realmente merece la pena el gasto.
• Uso de lectores de RSS:  cuando quiero seguir la pista a una web, ya no pongo su URL en mis “favoritos” (“bookmarks”) Ahora veo si tiene RSS y lo pongo en mis favoritos. Luego agrego mis favoritos al lector de RSS’s. De momento uso el gadget de Google Reader en mi página de inicio de Google. Esto quizás carga mucho el navegador y ya estoy mirando lectores de escritorio, tipo FeedDemon, si conocéis de uno y queréis darlo a conocer…
• Esto es más fotografía pero para las fotos de cabecera, montajes a veces de tipo panorámico, uso Autopano. Se acabó la tediosa tarea de montar, ajustar y crear las panorámicas a mano.

Bueno esto es todo lo importante. Si habéis tenido vuestro propio proceso de cambio me gustará saber de él. Saludos a tod@s.

With the new release of Zend Framework 1.7 , like many others, I was eager to download it and give it a whirl. Now I’m currently developing a ZF web app and we’re still in the early stages so I upgraded our trunk version of ZF to 1.7 and re-ran all my PHPUnit test cases using Zend Studio. To no suprise there was a slight problem:

Debug Error: /foo/library/Zend/Test/PHPUnit/ControllerTestCase.php line 1099 – Call to undefined method FooControllerTest::incrementAssertionCounter()

Now I did manage to track down exactly what the issue is. I won’t go into details about how but I’ll just say this: Zend Debugger is a god send for debugging PHP applications (and in this case a PHP test suite).

Anywho, basically with the release of ZF 1.7, Zend_Test_PHPUnit_ControllerTestCase::_incrementAssertionCounter() was added and is called by every Zend_Test_PHPUnit_ControllerTestCase::assertBlah(…) function. It simply does a PHPUnit version check and loops through to PHPUnit and calls either PHPUnit_Framework_TestCase::incrementAssertionCounter() if your PHPUnit version < 3.3.0 or PHPUnit_Framework_TestCase::addToAssertionCounter(1) if your PHPUnit version >= 3.3.0.

The problem is this, PHPUnit did not add PHPUnit_Framework_TestCase::incrementAssertionCounter() until version 3.3.0. Hence if you have a version of PHPUnit < 3.3.0, ZF 1.7 is not compatible This is true for all Zend Studio 6.1 users as it ships with PHPUnit v3.2.18. Why did the ZF devs not add a check to make sure the version was above 3.3.0 is beyond me. This breaks ZF 1.7 backwards compatibility with ZF 1.6 as this “increment/add to assertion counter” was not even present in ZF 1.6.

Now here’s the temporary solution: Since you can’t change the PHPUnit location in Zend Studio, you have to patch your Zend Studio install with an updated PHPUnit library. At the time of this writing the latest was 3.3.4. Grab it from PEAR and do the following:

1. Navigate to your ${ZEND_STUDIO_INSTALL_DIR}/plugins/com.zend.php.phpunit_6.1.0.v20080907/resources/library directory.
2. Rename PHPUnit to PHPUnit-3.2.18
3. Move the PHPUnit v3.3.4 folder you got from PEAR into the same directory and make sure it’s named PHPUnit

Now your PHPUnit test cases should happily run in Zend Studio

I’m going to take this issue up with the ZF devs and hopefully they’ll be a bugfix in 1.7.1 but who knows. Just wanted to help anyone who may be experiencing the same problem.

Cansado de tener problemas con la combinación de Eclipse v3.2, PHPEclipse y Subclipse v1.1
decidí probar la versión de prueba de 30 días del Zend Studio for Eclipse.

Los problemas básicamente de Eclipse 3.2 eran un conflicto entre el PHPEclipse y el Subclipse.
Para solucionar de una manera poco elegante pero práctica y rápida desintalé el Subeclipse y comencé a mandar los commits de Dokeos por consola (trabajo sobre una Ubuntu 8.04)

Pero los problemas no iba a parar, al crear un nuevo proyecto en Eclipse, apareció un error inexplicable y nunca más cargo. Es por eso que opté por probar el Zend Studio.

Aqui mis comentarios:

Lo malo

1. La función Ctrl-Click para inspeccionar funciones, constantes, includes, etc no funciona.
2. No existe una lista de las funciones declaradas en un archivo PHP. Hablo sobre la vista “Outline”.
3. Al igual que en PHPEclipse no existe la selección vertical. Algo MUY importante que se debería incluir en este tipo de IDEs. Por ejemplo, las versiones de Delphi y de Notepad++ lo tienen.
4. En la vista “PHPExplorer” (donde se muestra la lista de archivos) se observa el número de Commit pero no la fecha ni el usuario que hizo el commit.
5. 304 Mb la descarga!
6. ¿Olvide decir que cuesta $399 dólares?
   Según el sitio web: $399 for 1 year subscription to support / $717 for 3 years subscription to support

Lo bueno

1. PHP Functions: Biblioteca de funciones de PHP, ahorra tiempo en lugar de visitar www.php.net
2. El SVN SI funciona.
3. Ningun crash hasta el momento.
4. Fácil de instalar unos “10 clicks”. No hubo necesidad de instalar otros plugins.
5. Lee muy bien los .js. En PHPEclipse es necesario instalar otro plugin.
6. Incluye la funcionalidad “Create NEW SQL connection” un wizard para crear cadenas de conexión, aunque no lo utilicé porque en Dokeos ya existe una clase “Database”.
7. Y muchos pequeñas cosas que podrían facilitar el desarrollo desde cero (from scratch) aunque en mi caso no fueron usadas debido a que Dokeos ya tiene incluidas clases para manejar la BD, la Seguridad, las Sessiones, etc, etc.

La versión utilizada fue:
Zend Studio for Eclipse Professional Edition Build ID: 20080601

Conclusiones

El Zend Studio es un buen producto, tiene algunas funcionalidades que harán más rápido el proceso de desarrollo, sin embargo, por $399 uno espero algo mucho mejor. Si tan solo el PHPEclipse. Pronto una reseña de Eclipse Ganymede la última versión de Eclipse.

Actualización: Pueden ver este post para poder instalar Eclipse 3.4 Ganymede + PHPEclipse + Subeclipse

Tenho certeza que não sou o único desenvolvedor PHP que vive com esta pergunta no fundo da alma.

Abaixo vou colocar uma lista com algumas das IDEs que já testei, outras que baixei mas não usei ainda, e alguns editores, agradeço se vocês comentarem dizendo quais IDEs usam e seus motivos (pontos fortes e fracos)

Zend Studio – ótima interface, PHPDoc embutido, hide/expand os métodos, mas o FTP é bem ruim…

HTML-Kit – Editor muito leve, FTP ótimo, muitas opções de configurações e plugins, não te deixa na mão, mas peca na interface. Adicionando vários plugins ele fica bem legal, e bem pesado também.

jEdit – Simples demais, passei uns 10 minutos usando, mas achei que faltava muita coisa, me parecia estar usando a calculadora básica do windows, mas sem o botão de “scientific mode”.

Aptana Studio – visual cool, apesar da minha primeira experiência com ele foi de cara uma tela de erro do windows com relação ao Java, é muito interessante, com recursos similares ao Zend Studio. Uma feature legal é um grid com as tarefas que você pode adicionar e depois validando como realizada ou não. Isso evita você ficar perdido no projeto.

PHPed – usei há muito tempo atrás, teve várias mudanças, será que alguém é a favor?

Não mencionei aqui IDE nem editores pra MAC, I´m sorry.

Conto com a participação de vocês para dizer quais IDEs usam e porquê.

Yesterday I managed to discover a minor bug in the Zend_Controller_Router_Route class in the Zend Framework. In one of my view scripts I used the url helper to display the href part of a link doing something like this:

<a href="<?= $this->url(array(), 'newsCommentsRss') ?>">rss</a>

The newsCommentsRss route is an instance of the Zend_Controller_Router_Route class and is created like this:

$routes['newsCommentsRss'] = new Zend_Controller_Router_Route('/news/:id/comments/rss',
    array('module' => 'feed', 'controller' => 'rss', 'action' => 'newsComments', 'id' => null),
    array('id' => '\d+'));

The route consist of some static words along with a variable called :id that is supposed to be a number (see the regexp in the last argument to the constructor). It’s initially set to null, so if I somehow forget to set it using the Zend_View’s url helper, Zend Framework will promptly tell me to do stuff the right way! As you can see above I actually forgot to set the id when using the url helper (it’s supposed to be set in the first argument to the helper, but I specified an empty array). It was pure luck that I noticed it, but the weird part is that the :id in the route was set to the correct value even if I didn’t specify it. What gives?! Since I like my things to be logical I had to find out what was going on here.

I use Zend Studio these days and downloaded and installed the standalone Zend Debugger so I could do some debugging of ZF. At first I thought the bug was in the url helper so I added a break point at the line where I output the route and started the debugger. To set a break point in Zend Studio you just have to click on the line you want to break point to be set.

When starting the debugger it stops at the first line asking you what to do next. Since we only want to see what happens at the break point I just hit run. The line with the break point itself is not too interesting. The interesting part is what happens inside the url helper class. When the debugger stops at the break point I “stepped inside” to see what was going on.

I kept on stepping until I reached the url method of the url helper. At some point in that method it fetches the route using the getRoute method of the router instance:

$route = $router->getRoute($name);

I stepped on until that line had been executed. When inspecting the $route variable I saw that the :id part of route had already been set.

The bug had to be somewhere else then!

Since I use ZF’s MVC components I also use the front dispatcher that matches the current request to all the routes to see which module/controller/action it is supposed to execute. I added a breakpoint in the code where the dispatcher kicks in to see what happened.

When stepping through the front controller I found the point where it tries to route the current request:

$router->route($this->_request);

I stepped into that call and found the piece of code that iterates through all routes to see if anyone matches:

foreach (array_reverse($this->_routes) as $name => $route) {
    if ($params = $route->match($pathInfo)) {
        $this->_setRequestParams($request, $params);
        $this->_currentRoute = $name;
        break;
    }
}

I stepped through some iterations until it tried to match the newsControllerRss route. I inspected the route object and saw that the values has not been set yet. I entered the match method of the Zend_Controller_Router_Route and started stepping through.

Now we are operating on the newsCommentsRss instance itself so I added a watch on $this and switched to the watches view in Zend Studio since I’m only interested in the route object.

The match method splits up the request it’s looking for into several parts. The request at this time was “news/11/Title” and is split up into an array with three elements. Some of you might see that the rss route (news/:id/comments/rss) is very similar to the current request. The difference is the static /rss at the end.

The match method loops through the parts of the request and doing matches against each part of the route. The first part of the request and the route is the same. Next iteration!

The next part of the request is “11″ and the next part of the route is :id which must be a number. Since 11 is in fact a number this part also matches, but, since we have a variable in the route, the value is stored in the object itself:

if ($name !== null) {
    // It's a variable. Setting a value
    $this->_values[$name] = $pathPart;
    $unique[$name] = true;
} else {
    $pathStaticCount++;
}

At this moment $this had been changed (see the next two images).

Before second iteration:

After second iteration:

The third iteration will try to match the “Title” part from the request against the static “comments” part of the route. Since these two don’t match the match method returns false to let the outer loop have a go at the next route in the array. But hold on … what about the value that was set to 11? It’s not reset! And there you go! Bug found.

Some of you might notice that it’s not that easy to actually be affected by this bug. You need two similar routes like the two I have:

1. /news/:id/:title
2. /news/:id/comments/rss

and they have to appear in that order in the array of routes (the dispatcher searches routes in reverse order). You also have to actually have a request that matches the first one and on that same page output the second one. You might say that it’s stupid to have routes like this, but hey, everybody is allowed to be stupid once in a while!

When an error happens in something as big as the Zend Framework it can take quite some time to find out whats going on without a debugger. I would probably be still trying to figure out what was going on without the debug feature in Zend Studio. Since I’m such a nice guy (yeah right) I created an issue in ZF’s issue tracker. Just like all nice guys should!

EDIT: I just saw that the bug had been fixed (the last comment in the issue).

Famoso editor PHP conhecido por e muito e desconhecido por muitos (??). Feito pela Zend Development & Production este poderoso editor PHP conta com biblioteca de funções nativas e reconhecimento de variáveis, isto é, todas as variáveis que você utilizou ficam armazenadas no editor, assim, toda vez que for utilizar uma variável, ele exibe as que já foram utilizadas em forma de um menu dropdown.

E então, depois de uma noite de domingo e de uma aventura frustrada na internet em busca de um download que realmente funcionasse para o Zend Studio Client 5, resolvi “uploadear” o meu e disponibilizar para download aqui no blog.

Ele já vem com keygenerator e tudo que tem direito. Aproveitem. Obs.: o arquivo compactado .rar não possui senha para abertura.

Tamanho: 62MB

Link: 4shared

Link para download.

I loaded the Zend Studio for Eclipse and worked within it for about a week. That was as long as I needed to know that I had to switch back to the stand-alone 5.5 version.

I found at least as many of the same issues with the software as Eran Galperin did. I experienced the issues with the build and had to kill the task several times. And I too hate the “dreaded queue.”

Futhermore, I was disappointed in many other seemingly small changes in usability. For example,

• in Zend Studio 5.5 you can simply hit Ctrl + Tab to browse through your open files, as in Windows programs like Word or Photoshop. In Zend Studio for Eclipse, I have to hit Ctrl + F6 to browse through my open files, which necessitates the removal of my right hand from the home keys and just seems somewhat of an awkward key combination.
• In Zend Studio 5.5, you could hold down the Ctrl key and hit Enter when you want to insert a <br> tag at the end of your HTML code. This just seemed to disappear in Zend Studio for Eclipse.
• Adding a remote server to the project took me into some kind of file reading loop that would never finish. So, to combat the bug, I just stopped adding the remote folders to the project. However, this caused much of the code assist to “not know” about classes and variables, since it apparently must be added to the project for the inflection to work.

A bit nit picky you might say, but these small changes add up to a lot of minutes in a 10 hour day of programming and reduced my efficiency by enough of a margin to have me wanting to go back to 5.5. I really wanted the new version to work well, but it seems really buggy and cumbersome. So I switched back and am flying through code again!

Hopefully these issues will be resolved by the next release, but it makes me wonder how much the integration into Eclipse has limited or will limit the program’s usability. The standalone version seemed like a better route to me if they just took the advice of my previous post and then continued making updates and improvements.

Conoscete questo simbolo? No? allora lasciate che vi illustri il fantastico mondo dello Zend Framework di casa Zend!
Cos’è lo Zend Framework?
Lo Zend Framwork, come dal nome stesso, è un framework utile a velocizzare e ottimizzare le proprie applicazioni web in linguaggio PHP.Esso infatti contiene classi metodi e oggetti che fanno un po cio che fa php nativo, per velocizzare la procedura di scrittura del codice e renderla semplice e lineare rispettando i modelli w3c e MvC. La sua semplicita’ di utilizzo lo rende uno dei framework php piu utilizzati al mondo. Volete quache esempio? Vi accontento subito.

Script per la connessione al db.

php 5:

$Connessione=mysql_connect($server,$user,$password);

$sql = "SELECT * FROM table WHERE column = 'value'";

$database=mysql_select_db($name_db,$connessione);

$tutto=mysql_query($sql,$connessione);

Mysql_close($connessione);

Zend Framework:

$db = Zend_Db::factory('Pdo_Mysql', array(
'host'     => '127.0.0.1',
'username' => 'webuser',
'password' => 'xxxxxxxx',
'dbname'   => 'test'
));

$result = $db->fetchAll("SELECT * FROM table WHERE column = 'value'");

Ho reso un po l’idea? Visto come con una programmazione e struttura ad oggetti e soprattuto con la splendida tecnologia dello Zend Framework riusciamo ad eseguire una connessione al db veloce e un esecuzione di una query altrettanto rapida? Beh questo e solo un granello di sabbia nel deserto, delle funzionalita e i vantaggi di zend. E possibile gestire i post e i get con semplicita’ estrema, validare una data stringa e controllare diverse opzioni impostate da noi, controllo sull’email e ottima gestione delle richieste XHtmlReques. Insomma, detto cosi sembra un framework da sbavo. E lo è! Qui di seguito troverete diversi link utili:

Home Page del Framework
Documentazione Completa in inglese
Api del framework
Versione 1.3 ( stabile ) del framework
Il team della Zend Inc

Optimiza tu tiempo y mejora tu experiencia en el diseño y desarrollo en internet utilizando editores web. En este artículo te mostramos una lista de alternativas en el medio, puedes agregar o recomendar tu favorito.

Encuentre mas información en : Maestros del Web >> Editores web que facilitan tu trabajo

Achtung! Der Anti-Hype-Blog ist umgezogen nach www.anti-hype.de!

Du findest den gesuchten Artikel nun hier:

• Zend Studio for Eclipse