Saumya

Developing for a fragmented landscape is not easy. Its even difficult, if you choose to use, a library or framework, which says develop once and run everywhere or something like it makes your application look like native. First thing first. With every new release, we have another step addition to test. Contrary to the belief that, the new Operating System is obviously capable of running the old running application, it adds one more fragment to the already fragmented landscape. So if you are a mobile developer, keep this in mind that new OS, is a new test step. Well, lets add one more device to this equation. Lets just focus on Apple devices, considering there so called, minimum number of device types. An iDevice is suppose to run the latest vesion of the iOS. But in the development environment, you might not able to keep up with new device types or OS updates. And only this can break your application. So make sure, you have latest device and latest OS. Ok, then test your application in this device, chances are your application may run but chances are it might not too. So the point is search arround the internet from the beginning itself, if there are known problems with the exact device and OS combination.

more

This is probably exciting and why I moved, to Wintersmith. Part of the blogging itself, is learning the engine and the Jade template engine.

Here is a tip to configure the author name.

With every blog post, there is an author name, below the title, which reads as “written by author”. This comes from the blog itself as you probably know already. Thats fine and thats the default behaviour. If one needs to change it and which could be changed, here is the thing.

The details are populated from the authors folder. The author name specified in the blog meta data,ie; the top section, when writing the blog, is mapped to a file with the same name as author. So the file name is author.json in the authors folder, where author is specified in the blog meta-data. If it finds the file, then the author name below the title of the post is updated with the new data from the file and an email link is attached with it which is also taken from the .json file. This is interesting, if it does not find the file, simply the autor name from the blog meta data, is put out in the blog, without the email link.

Happy hacking.

This is the first time, I worked with Parse and must say its a nice to have tool for any web developer. Parse minimises the task a lot in terms of backend and hosting.
Parse has a lot of options to choose from and one can choose to use the only required ones.
Well, I started of with hosting only, for one of my Facebook applications. They even have a SDK to integrate the Facebook SDK with them. I have not yet implemented their SDK yet, but docs show its simplicity of use.
I have started working on a BackboneJS application integrating Facebook and hosting in Parse. That went quite smooth. Actually Parse has extended BackboneJS to provide another SDK of their own to create frontend applications.
Happy coding.