View Single Post
Posts: 200 | Thanked: 44 times | Joined on Jan 2010
#681
Originally Posted by reinob View Post
I would prefer if Yappari left the contacts as they are. It's not the responsibility of a third-party app to fix your broken contacts. If I ever catch Yappari or any other application "fixing" anything of my contacts I'll immediately purge it and be angry about it.

After all, your problem requires a one-off solution. Write a script for that!



I seriously doubt that. Particularly at this stage of *early* development, the less people who play around with the code the less chances that one of them fvcks up.

Cheers.
firstly you wouldnt fix them in the actual phone book you would change them in memory so as you read a entry you check for area code if it doesnt exist in the number you would apply it then send the alterd version from memory to watsao service leaving the phone book in tact.

secondly with decent source control the main developer would still have the choice to push fixes and features into the main branch. this is kind of the essence of open source development. you find me one comercial project that is only worked on by one person. it just doesnt happen people dont have the time. you might even find a very skilled developer will get involved and produce some very elegant and fast code.

im not saying there isnt all ready a very good developer working on it just saying there could be more to increase productivity.

Last edited by jamie721; 2012-06-28 at 11:29.
 

The Following User Says Thank You to jamie721 For This Useful Post: