Facing new challenges everyday

Today I discovered how objetive-c allows the programmer to generate a textual representation of a object, you can do it by implementing a description method of NSObject protocol.

Please consider the following class interface:

Contact.h

(more…)

There’s no doubt, ASP.NET is an amazing technology, very productive and easy to use, but it isn’t perfect, his architecture doesn’t help enough when you need add unit tests in your project and you can’t see a clean separation of concerns, some of its urls used to access pages isn’t so intuitive, if you need pass some data over browser address bar it will only read by accessing the old QueryString object.

As completly opposite we have ASP.NET MVC, some of its urls are very intuitive, you don’t need use something like QueryString object to read parameters passed via GET method, you can see a clear separation between model, view and controller layers, all ASP.NET MVC applications can be easily tested using the most famous unit tests frameworks.

In this article I’ll give a small introduction to web development with ASP.NET MVC and data persistence using ADO.NET EntityFramework, a simple contacts application will show how to accomplish this.
(more…)

One of the missing features in Xcode is the hability to add code sense for protocol methods that can be implemented by a class, for example a class that extends UITableViewController, these classes may have a custom implementation of methods found on both UITableViewDelegate or UITableViewDatasource protocols, the signature of these methods isn’t so easy to memorize and some code completion at this point would help a lot.

(more…)

There’s no doubt about Django and its agile development nature, but there are some circustances where we need take more care on user input, one of these circustances is date input, after few hours googling about it I finally found a way to fix date input by just using DateTimeInput widget on DateField of Django ModelForm.

(more…)

After few days using RESTeasy in my project I found a very annoying issue related with its Spring support, please consider the bean declaration below:

For some reason the RESTeasy ContextLoaderListener implementation is unable to resolve property placeholders used by some properties of beans at singleton scope, when I read these properties from my bean logic I see all properties placeholders there as they weren’t resolved.

So I decided to try Jersey since it uses the standard implementation of ContextLoaderListener that comes with Spring, now my application works as expected, all properties placeholders are being correctly resolved on my Spring singleton beans.