A week ago I started working on a simple editor/IDE for PHP called ape. That’s my weak try on creating a reverse acronym as ape stands for - ape is a PHP editor. This is kind of an introductory post into the whole developing process of it, as my intention is to blog about it a bit more :)
First, to answer the question everyone is giving me when I mention I’m writing ape:
“Why the hell do you do that (to yourself)?”
Programming is fun. Programming is interesting. Programming makes me learn new things. I like having fun and I do this to learn more about programming and having even more fun. I’m writing web applications each and every day, so writing a desktop app requires a different way of thinking and leaving my “comfort zone” (altho, I’m quite comfortable in front of the keyboard hackin’ away code). ape is written in python and pyqt, but again, it’s not about the language used, for me it is about programming.
Netbeans is my main IDE for quite some time now and I love it. I know my way around vim, too. But, netbeans has too many features for my taste - I use SVN, git, (on rare occasions I write them) run unit tests from the console. As for vim, maybe I just don’t get it enough, but I feel less productive with it. Debugging PHP apps ends up var_dump-ing things all over the place. So, basically what I want/need from an editor is grouping files into projects, regex search/replace, code coloring & completion and, of course, file editing.
I plan to write a feature a day. On my personal projects I usually want to push out as much code as I can during one day as I’m highly motivated, but this time want to try a different approach. So far I didn’t got far, figured out syntax highlighting, opening files from a file browser widget thingy and things like that, but more on that in other posts.
If anyone wants to take a look, the source code is up on github. It is licensed under GNU GPL v2, as pyqt is licensed under it and I don’t want to waste my time on figuring out could I use MIT or some other license.