The last few months I have been keen to move my existing version control activities over to Bazaar, away from Subversion. Today that desire was rather firmly set in stone when I discovered that Bazaar doesn’t create a .bzr directory under every subdirectory in the tree like Subversion does with its .svn directories. This makes things so much easier to work with when you have to, say, upgrade your version of Wordpress and you need to use FTP to transfer the files. Clearly you don’t want to transfer your VCS data as well so previously I had resorted to creating a sync script that disregarded the unwanted directories. So, thank you Bazaar for making my life that little bit easier!
I am having some issues with the Magento translation tool - mostly that it doesn’t allow for version 1.0 translations - so I am posting this unofficial translation here. It’s fairly complete spelling-wise and is only lacking a look over for grammatical changes and places where entirely different words are used, rather than just a spelling change. An example that springs to mind is “State/Province” possibly being changed to “State/Territory”.
I discovered a few flaws in my Magento Australia module, all of which were due to my own silliness. It’s funny how bugs tend to pop up in the simplest of places due to the developer missing them while he concentrates on the more advanced stuff.
I have recently been doing quite a bit of development with both ExtJS and jQuery and I thought I would share my experiences with both of them. One thing to keep in mind is that I’m not going to say whether one is really good or bad - they’re both excellent libraries and your choice for any given project might simply come down to personal preference. That said, the rest of this will be my opinion on the two.
In my new position at Fontis, I have been tasked with continuing development on a somewhat larger project for an external client. It doesn’t sound like anything too dramatic - web site written in PHP, using the CakePHP framework, and driven by a database. I just didn’t factor in Murphy’s Law.
CouchDB is a (relatively) new database option for development that focuses on documents, rather than generic relational systems like most databases do. I think the concept is appealing and support for things like automatic versioning and distributed processing and storage could mean a lot fewer headaches that trying to get a custom system going yourself. Also interesting is the JSON storage format, which would make this ideal to use in many asynchronous web applications as the data returned can be used straight away on the browser.
I haven’t had any cause to use this system yet but I’ll be sure to write a review when I do. Anyone else taken this for a spin?