I love working in the Zend Framework view system. One thing that bothers me, however, is that I must create a complex set of models when trying to send email. I decided that I’d like to move all of this output for the mail class into my own view system as well.
Goal: to create a site serving females that felt a specific male in their life deserved positive recognition. Then, to monetize the recipient from one of two targeted ads.
The goal was to use links that Amazon provided themselves to showcase categories and percentage discounts with my affiliate tag. The thought was a clean interface would easily encourage people to click a discount of say 90% but send affiliate contributions my way.
Have you ever used Zend Form, created a submit button, and had a few extra tags that were just throwing you off? I know you have… You probably did it like me:
What is the measurement of a good career? Promotion? Raises? Running a project / leading a team? Usually all of this. However, the most traditional measurement of success in a career is moving upward. Time to run a department, time to lead a team, etc. However, I submit a very radical idea: Sometimes just be great, don’t lead.
By default, when using the Zend Paginator, the result set will come back as an array. If you are using a paginator associated with a database result set, and that db has a class defined for its row, it will come back as that class. However, if this is not the case, or you are not using information from a database, you may still want a different result than just a plain array.
So, while chatting with one of the developers on my team, we started talking about testing an XML document creation process he had been working on. He wrote a unit test and said “see, here is my class which generates the XML, and then here I use DomDocument to add the nodes I know it will have and test against that.”