all-IT

As development hardware are currently quite popular Macs running, but on these aluminum beauties an operating system based on Unix.

Another reason might be that the development environment Eclipse is supported on MacOS good. This is especially true for Java (using the Java Development Tool - JDT). However, PHP web applications go well with Eclipse and the PHP development tool - PST program.

The PDT does not own with PHP interpreter. Ie, they must provide themselves for a web server with PHP module. On the Mac, you get the comprehensive package with MAMP .

If you want to make a PHP script to run under Eclipse, you have to do the two know each other. But before Eclipse PDT requires a debugger. You can choose between the Zend debugger, which is unfortunately not included with MAMP and XDebug, the Module is integrated into MAMP with me did not work.

An updated version of XDebug can be installed over brew.

  brew install xdebug 

Brew is indeed ahead of Xcode, but should be absent from any Mac developer. There is no installation guide is on github .

But back to XDebug. During installation you will be advised of the following steps:

  To use this software:
   * Add the following line to php.ini:
     zend_extension = "/ usr/local/Cellar/xdebug/2.1.1/xdebug.so"
   * Restart your webserver.
   * Write a PHP page that calls "phpinfo ();"
   a browser and look for the info on the xdebug module. * Load it into a browser and look for the info on the xdebug module.
   * If you see it, you have been successful! 

The php.ini that MAMP can bring, not be edited with normal user rights. With sudo, but it is already.

  Applications / MAMP / bin / php / php5.3.6 / conf / php.ini sudo vi / Applications / MAMP / bin / php / php5.3.6 / conf / php.ini 

In the [xdebug] then the Directive is fully complied for the xdebug module add:

  [Xdebug]
 zend_extension = "/ usr/local/Cellar/xdebug/2.1.1/xdebug.so" 

Start with the Web server and monitor the success as described above.

Does everything have to configure in Eclipse, only the settings in a PHP Executeable to start from where PHP scripts can be.

As development hardware are currently quite popular Macs running, but on these aluminum beauties an operating system based on Unix. Another reason might be that the development environment Eclipse is supported on MacOS good. This is especially true for Java (using the Java Development Tool - JDT). However, PHP web applications go well with Eclipse and the PHP development tool - PST program. The PDT does not own with PHP interpreter. Ie, they must provide themselves for a web server with PHP module. On the Mac, you get the comprehensive package with MAMP. If you want to make a PHP script to run under Eclipse, you have to do the two know each other. But before Eclipse PDT requires a debugger. You can choose between the Zend debugger, which is unfortunately not included with MAMP and XDebug, the Module is integrated into MAMP with me did not work. An updated version of XDebug can be installed over brew. Brew brew install xdebug but requires Xcode, but it should be missing from any Mac developer. There is no installation guide is on github. But back to XDebug. During installation you will be advised of the following steps: To use this software: * Add the following line to php.ini: zend_extension = "/ usr/local/Cellar/xdebug/2.1.1/xdebug.so" * Restart your webserver . * Write a PHP page that calls "phpinfo ()" * Load it into a browser and look for the info on the xdebug module. * If you see it, you have been successful! The php.ini that MAMP can bring, not be edited with normal user rights. With sudo, but it is already. sudo vi / Applications/MAMP/bin/php/php5.3.6/conf/php.ini In [xdebug] then the Directive is fully complied for the xdebug module add: [xdebug] zend_extension = "/ usr/local/Cellar/xdebug/2.1 .1/xdebug.so "run by the web server and monitor the success as described above. Does everything have to configure in Eclipse, only the settings in a PHP Executeable to start from where PHP scripts can be.

gklinkmann written by \ \ tags: eclipse , macos , php

I have neglected in recent times the topic Grails in this blog a bit. So it is now after this dry spell at the time, again to write a blog entry on this subject (may result in more).
One of my first article on Grails showed how to make Grails and Eclipse together. This entry was so successful that I did as a permanent site was built as part of a small tutorial on the blog.

This is a couple of months ago and support the creation of Grails applications with Eclipse has become steadily better.
Was it the beginning so that by far the best IDE for Grails was IDEA, the free Eclipse gets more and more. No later than the change of Grails developers to SpringSource and the associated integration into the Eclipse-based SpringSource Tool Suite (STS) , a lot has happened.

Aside from the main memory - Hunger of STS, I feel as old Eclipse users in good hands. With NetBeans and IDEA I could never really get used.

To enable Grails to support the Grails and Groovy on the Extensions tab extensions of the STS dashboards are installed (see screenshot). Then there are for Grails projects its own perspective, with syntax highlighting, code completion and a clear navigation in the Project Explorer.
In the toolbar there is a button in the Grails perspective Grails commands to execute (such as run-app ).

When installing the Grails Extensions is the installation directory of the current STS Grails saved version.

  springsource / ~> Ls spring / source
    grails-1.3.5
    grails-1.3.6				
    grails-1.3.7
    maven-2.2.1.RELEASE				
    roo-1.1.0.RELEASE			
    tc-server-devel-2.0.4.RELEASE
    sts-2.5.0.RELEASE 

Are there any updates (Help -> check for updates), a new version of Grails there is this added. In the Preferences (Groovy -> Grails) you have to take the new version of the workspace. The Grails project is still the upgrade command is necessary.

Conclusion:
The Grails integration into Eclipse has taken a big step forward. From IDEA functionality should still lead. Grails projects there are only supported in the paid version ULTIMATE.
The free development environment NetBeans and Eclipse-based STS hardly differ in the Grails support. Here the personal preference will decide on the IDE.

Links:
Talk about this topic on stackoverflow.com

I have neglected in recent times the topic Grails in this blog a bit. So it is now after this dry spell at the time, again to write a blog entry on this subject (may result in more). One of my first article was to Grails, Grails, and how to get Eclipse to each other. This entry was so successful that I have integrated it as a fixed site as part of a small tutorial on the blog. This is a couple of months ago and support the creation of Grails applications with Eclipse has become steadily better. Was it the beginning so that by far the best IDE for Grails was IDEA, the free Eclipse gets more and more. No later than the change of Grails developers to SpringSource and the associated integration into the Eclipse-based SpringSource Tool Suite (STS), a lot has happened. Aside from the main memory - Hunger of STS, I feel as old Eclipse users in good hands. With NetBeans and IDEA I could never really get used. To enable Grails to support the Grails and Groovy on the Extensions tab extensions of the STS dashboards are installed (see screenshot). Then there are for Grails projects its own perspective, with syntax highlighting, code completion and a clear navigation in the Project Explorer. The toolbar is available in the Grails perspective a button to run Grails commands (such as run-app). When installing the Grails Extensions is the installation directory of the current STS Grails saved version. ~> Ls spring source / grails-1.3.5 grails-1.3.6 grails-maven-1.3.7 2.2.1.RELEASE roo-1.1.0.RELEASE tc-server-devel-2.5.0-2.0.4.RELEASE sts . RELEASE there with the updates (Help -> check for updates), a new version of Grails there is this added. In the Preferences (Groovy -> Grails) you have to take the new version of the workspace. The Grails project is still needed the upgrade command. Conclusion: The Grails integration into Eclipse has taken a big step forward. From IDEA functionality should still lead. Grails projects there are only supported in the paid version ULTIMATE. The free development environment NetBeans and Eclipse-based STS hardly differ in the Grails support. Here the personal preference will decide on the IDE. Links: Talk about this topic on stackoverflow.com

gklinkmann written by \ \ tags: eclipse , development environment , Grails , Groovy , Java

Eclipse is for me as a developer, my daily bread, and accompanied me for years. The logo has changed little during this time (and why - I liked it).

Eclipse now wants to make a new logo to point out that the project does not stop there.
Designs are in demand, which should result in a contest for new logo. The winner a prize of $ 500 is waiting.

The proposals already submitted one can here look.

Which would you choose you?

Eclipse is for me as a developer, my daily bread, and accompanied me for years. The logo has changed little during this time (and why - I liked it). Eclipse now wants to make a new logo to point out that the project does not stop there. Designs are in demand, which should result in a contest for new logo. The winner a prize of $ 500 is waiting. The proposals already submitted can be viewed here. Which would you choose you?

gklinkmann written by \ \ tags: eclipse , ide , java

From my perspective, Groovy , the dynamic language for the Java Virtual Machine, arrived on the big hype curve at the point of technical reality. With Scala and Clojure instead just two new programming languages ​​are driven by the community of disciples of Java.

So it must be questioned at the time at what you yourself have so far implemented in Groovy, but whether it remains or jumps on the train Scala.

Dierk König, author of "Groovy in Action" (the best technical book I've read lately), once the following 7 Groovy usage patterns for identified:

Super Glue, Liquid Heart, Keyhole Surgery, Smart Configuration, Unlimited Openness, House-Elf Scripts, Prototype

Or not quite as prosaic as:

• Link between Java components (such as Spring and Hibernate in Grails)
• Outsourcing Buisiness logic to dynamically adapt to changes they can
• Possibility of intervention in current applications
• Advanced configuration by means of a programming language (to finally get rid of the clumsy XML)
• the slight change of code at run time
• Help for all tasks involved with programming (build automation, continuous integration, deployment, installer, service monitoring, reports, statistics, automated documentation, functional tests, HTML scraping, Web remote control, XML-RPC, web services)
• Tool for rapid prototyping, with the possibility they may later ported to Java.

But back to the starting point. What do I do with Groovy?

First of all, I write 95% of new tests in Groovy. The syntax of crisp, perfect interoperability with Java and the good (but improvable) integration in Eclipse to make the creation of tests much less annoying. There are also smaller Web applications and Web services based on Grails (the Webframwork based on its part also Groovy), as well as tools that are purely written in Groovy.

Ultimately, one can say that the hype has given way to the everyday and Groovy fits perfectly into the daily work. With Griffon and GPars are 2 other frameworks for Swing applications and Concurrent Programming (threads) on Groovy basis. And a vibrant community has formed around this dynamic language. A switch to Scala or closure is thus for me the moment the question.

And to be quite Ehlich, when the children ask, "Daddy what are you doing?" Sounds like "I program groovy" a lot cooler than "I have been programming Scala."

Links:
Groovy Usage Patterns by Dierk Koenig

From my perspective, Groovy, the dynamic language for the Java Virtual Machine, arrived on the big hype curve at the point of technical reality. Scala and Clojure instead just two new programming languages ​​are driven by the community of disciples of Java. So it must be questioned at the time at what you yourself have so far implemented in Groovy, but whether it remains or jumps on the train Scala. Dierk König, author of "Groovy in Action" (the best technical book I've read lately), once the following 7 usage patterns for Groovy identified: Super Glue, Liquid Heart, Keyhole Surgery, Smart Configuration, Unlimited Openness, House -Eleven scripts Prototype Or not quite as prosaic as: a link between Java components (such as Spring and Hibernate in Grails) Outsourcing Buisiness logic in order to adapt it dynamically to changes to possibility of intervention into current applications extending the configuration by means of a (get rid of at last the clumsy XML) programming language, the slight change of code at run-time support for all tasks involved with programming (build automation, continuous integration, deployment, installer, service monitoring, reports, statistics, automated documentation, functional tests, HTML scraping, Web remote control, XML-RPC, Web Services) tool for rapid prototyping, with the possibility of these later ported to Java. But back to the starting point. What do I do with Groovy? First of all, I write 95% of new tests in Groovy. The syntax of crisp, perfect interoperability with Java and the good (but improvable) integration in Eclipse to make the creation of tests much less annoying. There are also smaller Web applications and Web services based on Grails (the Webframwork based on its part also Groovy), as well as tools that are purely written in Groovy. Ultimately, one can say that the hype has given way to the everyday and Groovy fits perfectly into the daily work. With Griffon and GPars are 2 other frameworks for Swing applications and Concurrent Programming (threads) on Groovy basis. And a vibrant community has formed around this dynamic language. A switch to Scala or closure is thus for me the moment the question. And to be quite Ehlich, when the children ask, "Daddy what are you doing?" Sounds like "I program groovy" a lot cooler than "I have been programming Scala." :-) Links: Groovy Usage Patterns by Dierk Koenig

gklinkmann written by \ \ tags: eclipse , Grails , Groovy , Java , Open Source , Spring , Web , web2.0 , xml

The holidays are over - unfortunately. A little late, but for more in number, the "weekly links" are:

jQuery Accessible RIA - (accessible jquery)

AJAX Frameworks and accessibility, there are two things that are not really compatible. That there is another way, this shows hosted on GitHub project.

Symfony Components - standalone libraries for PHP

Symfony is one of those nice new framework for PHP. The project has provided a few components that can be utilized without installing the entire framework. I'm already looking forward to the announced request handler.

PHPUnit using PTI integrated into Eclipse

For instructions on how to integrate the PHPUnit testing framework in Eclipse.

SystemRescueCd

The rescue CD with many useful tools, if the PC would sometimes cause problems.

Raphaël-JavaScript Library for svg and vml

A JavaScript library to create graphs and charts in SVG and VML (Microsoft) format. Well worth seeing.

The holidays are over - unfortunately. A little late, but for more in number, the "weekly links" are: jQuery Accessible RIA - (accessible jQuery) AJAX frameworks and accessibility, there are two things that are not really compatible. That there is another way, this shows hosted on GitHub project. Symfony Components - standalone libraries for PHP Symfony is one of those nice new framework for PHP. The project has provided a few components that can be utilized without installing the entire framework. I'm already looking forward to the announced request handler. PHPUnit using PTI integrated in Eclipse Tutorial on how to integrate the PHPUnit testing framework in Eclipse. SystemRescueCd The rescue CD with many useful tools, if the PC would sometimes cause problems. Raphaël-JavaScript Library for svg and vml A JavaScript library to create graphs and charts in SVG and VML (Microsoft) format. Well worth seeing.

gklinkmann written by \ \ tags: Ajax , eclipse , ide , Javascript , Linux , php , web , windows