Did you ever wish there was an iPhone Client for SugarCRM?
Did you ever wish there was an iPhone Client for SugarCRM? Well, worry no more! Pramati Technologies is pleased to announce a free iPhone native Client for SugarCRM. Yes it is absolutely FREE!
Get used to the true mobile solution for SugarCRM with a brand new iPhone native Client from Pramati Technologies.
The following are the highlights of the iPhone client:
- It is iPhone native and not HTML based
- It is truly mobile;
o Works with limited, intermittent and no connectivity modes.
o Works on the principles of “Store, Operate and Sync”!
- Dynamic and offline search as opposed to server based batch search
- Supports Create, Read, Update and Delete operations on major modules
- Unlimited updates of offline data!
- iPhone like navigations
- On demand sync with the server.
- Ability to email or call directly from your contacts
- Integration with Google Maps
For further details, please check out the following URL: http://www.pramatiservices.com/index.jsp?id=uit_iphonedev
Thanks
Raj
FaceBook Apps Testing
Facebook Apps Testing: Does it sound surprising or does it sound interesting. When i got to look at this area as a potential offerable service line i had both the reactions to myself. But as i spent some quality time, understanding how these cool apps are built and more importantly how these apps should satisfy what i thought as a well laid out policy from facebook, it made me realize that there is a lot that can be done.
While developers can/should focus on their prime responsibility to probably create close to perfect facebook apps, its also imperative some one else should take a look at independently testing the same. Functional testing is not just that makes it complete. In fact the challenges lying are ensuring what the developers cannot do and what the application cannot do as prescrbed.
Understanding the anatomy of a facebook application goes a longway in ensuring how succesfully we do this.Deploying large scale, high-performance and scalable facebook applications is certainly a challenge and worth offering as a competency. Testing and ensuring the usability, functionality, browser compatibility and load, performance and scalability aspects of the same is thus a core competency in its own.
QLabs engineers have real time expertise in testing the best in class Facebook applications built by Pramati. This experience helps QLabs engineers to understand and apply the required knowledge, competency, and delivery excellence in the shortest possible time frame. QLabs engineers have the required expertise to check what a potential Facebook application can do, and what the developers are not allowed to do in accordance with the Facebook policies.
QLabs covers all aspects of Facebook application testing. That said, then, having your Facebook applications satisfy the Facebook policy has never been easier!
Check out our offerings on facebook apps testing at http://www.pramatiservices.com/index.jsp?id=qlabs
Calendar getDisplayName() JDK 6.0 vs JDK 1.5.0
If you have somehow used jdk6.0 while developing your application that uses Calendar API of java.util.Calendar, and have used getDisplayName method to extract the display names for fields of the calendar, specific to your desired style and locale, and then had to compile your application with jdk1.5.0 only to realize that compiler spits swear words at you…Here is quick fix for you!
This is what you did in jdk6.0:
//get your application locale
Locale userLocale = getContext().getLocale();
//define a calendar
Calendar calendarInstance = Calendar.getInstance();
//Extract the month name in SHORT format (viz. "Jan","Feb" etc.) for the context locale.
calendarInstance.getDisplayName(calendarInstance.get(Calendar.MONTH),Calendar.SHORT,userLocale);
Here is what you can do to achieve the same getDisplayName functionality in jdk 5.0:
//import the following class
import java.text.DateFormatSymbols;
//declare variable.
DateFormatSymbols dateFormatSymbols = new DateFormatSymbols();
//Get the short names for months in a Calendar
String[] months = dateFormatSymbols.getShortMonths();
//Use the month field of Calendar to fetch the short name of month for cell label.
String monthDisplayName = months[calendarInstance.get(Calendar.MONTH)];
Once you acquire the SHORT name for the field, you can use it for your labels, or column headers etc. based on where you require it.
Ideally, you shouldn’t have to fall back on the previous version of jdk, yet sometimes the project requirements can’t be altered even for better things in life.