Doctrine 1 has the concept of behaviors which you could add to your models. One of these was the soft-delete behavior, which allowed you to “delete” records without really deleting them.
Doctrine 2 does not have behaviors due to various reasons. However, I needed a way to have a model which worked like soft-delete.
Let’s see one approach to creating such behavior in Doctrine 2.
Dojo is a great JavaScript toolkit, but it’s not perfect: It has a couple of gotchas that can be hard to debug just based on the error (or the lack of it).
To rectify this, here’s a list of some common mistakes and their solutions. It’s usually good to just go through each of these if you can’t figure out what’s up – it has helped me quite many times.
For the past 24 hours, there has been an open hackday/hackfest/hackathon/something in Oulu, Finland – where I live.
This was the first (or second, depending on how you count) open hack day held here, and probably one of the first few held in Finland too.
Mongrel is a refreshing approach to web servers. We’re all familiar with the Apache server and many of us have used Lighthttpd and Nginx and maybe some others too.
So what makes Mongrel special? It’s language agnostic. It doesn’t have a PHP module, it doesn’t have a Python module, and yet you can still use those languages (and plenty more) with it, with very little effort to integrate new languages.
While there are some good shooters coming out lately, no one is really pushing to improve the genre with new ideas or concepts. Most games build on the shoulders of the previous ones, merely improving areas here and there.
What if you were to combine two genres of shooters which are distinctly different from each other?
What if you would combine some ideas from danmaku, or “bullet hell”, shooters into first person (or third person) shooters?
I mentioned shortly on twitter that you should avoid using SQL queries inside loops. There was some questions on how, so here’s a short post that hopefully explains some tricks that you can use.
Often when you see people talking about why they don’t want to become a programmer, their argument is that it’s a job where you just do things alone.
Especially in many news articles complaining the lack of interest girls and women have in IT careers and programming, many girls or women interviewed think the job is boring and lonely.
Then, people want to encourage others to study tech, so they loudly proclaim in those articles how programming is not a lonely job for nerdy nerds.
But those who say that are rarely programmers. What do they know?
What should you do to make sure new code works properly when you’re refactoring old code? I asked myself this question recently, when I needed to refactor a big bunch of procedural PHP code into a neat, testable, OOP-style interface.
The conclusion I came into is that you should write unit tests – not to test the old code, but as requirements for the new code.
So you want to learn to use Zend Framework, and develop a web app with it. Maybe you’ve been looking at a book to help, too.
This is what Keith Pope’s book Zend Framework 1.8 Web Application Development promises to teach you.
And I think this is the best book for the job. Continue reading to find out why.
I have recently received a review copy of Jürgen Petri’s book, NetBeans Platform 6.9 Developer’s Guide, and I will be posting a review of it after I finish reading it in the coming weeks.
You can check the book out on Packt’s store page.
Some of you may recall I was also doing a review of Zend Framework 1.8 Web Application Development. This review was delayed becayse of me being the usual me and forgetting things, so I’d like to apologize to anyone who has been waiting for it. I’m going to post my review of it next week – I already have it written too and it just needs minor edits, so this time I’m not going to forget about it ;)