Setting up your development environment

This presentation is a snapshot how I have setup my development environment. I am constantly evaluating, so this presentation is constantly changing. It gives developers and people that are planning to start with development practical tips, I am presenting in some way best practicals. Because it is my view and what I have found it is also questionable. I am talking about coding styles, Editors, IDE, build tools like phing, git and all that stuff.

Transcript

1. Development Tools Joomladagen 2013 Robert Deutz
2. Challenges
3. DEVELOPMENT TESTING PACKAGING
4. 5 Areas
5. Version Control 1
6. Code quality and consistency 2
7. Integrated Development Environment 3
8. Some little tools 4
9. Build tools 5
11. Version Control
12. Never do development without a version control system RULE 1
13. CVS SVN Mercury Git Centralised Distributed
14. Centralised Version Control Systems • very popular at the end of the last century • complicated when working in not centralised teams • merging and working on different things at the same moment is complicated • still room for using it but NOT in an Open Source Project like Joomla!
15. Distributed • Best thing since sliced bread • good for not centralised teams • Supports merging and branching in an easy way • It allows a group of people to work on different ideas and in parallel on a single codebase
16. CVS SVN Mercury Git Centralised Distributed
17. GIT
18. try.github.com Got 15 minutes and want to learn Git?
19. Tools if you don‘t like the command line
20. Tower (MAC)
21. Source Tree (MAC)
23. Code quality and consistency
24. Write beautiful and well documented code. RULE 2 ALWAYS
25. We do • use brackets • use tabs • format code always in the same way • use meaningful function, variable, methods and class names • use phpDoc Blocks • not copy code (DRY: don‘t repeat yourself)
26. We write helpful comments As I wrote this code only god and I know what it is doing, now only god knows WRONG Registers a handler to a particular event group. RIGHT
28. Integrated Development Environment (IDE)
29. We are using an IDE RULE 3 WHEN IT MAKES SENSE
30. I don‘t care which one
31. IDEs • Eclipse (Zend Studio, phpEclipse, .....) • PHP Storm (free license for Joomla! developers) • NetBeans IDE • ......
32. Cooler Editor: Sublime Text • Packages for almost everything we need • extremely fast • Edit features from heaven • .... but not an IDE • comes closer and closer
33. How to chose a IDE • Don‘t give up! • It need‘s time, so think first about your requirements • Think about your development process, what you have to do to make sure that you can support your process properly
34. My Setup
36. Some little tools
37. We are trying to automate steps in our development process RULE 4 DEVELOPERS ARE LAZY
38. Code formatting Code Sniffer
39. phpcs --standard=Joomla *
40. OR
41. integrate it in editor / IDE
42. PHP Documenter
43. Creates from your well documented and formated code an API documentation, with just a klick
46. Build tools
47. Don‘t do it by yourself when a script can do it for you RULE 5
48. PHING (phing.info)
49. extendable executing commands packaging checkout from a repository copy files replace tags in files
50. extendable executing commands packaging checkout from a repository copy files replace tags in files
51. Extendable
52. 2 FILES
53. map
56. packaging
58. Hartstikke bedankt! Twitter: rdeutz Email: rdeutz@gmail.com Web1: rdbs.de Web2: babioon.com Web3: robert-deutz.de
59. [1] http://digitaldisseny.com/en/blog/141-setting-up-codesniffer-to-validate-joomla-coding-standards-on-ubuntu [2] http://git-scm.com [3] http://docs.joomla.org/Git_for_Testers_and_Trackers