jonathanrico.

App inventor for android

Here’s a nice tool from Google for building apps for Android:

Learn more here : http://appinventor.googlelabs.com/about/

technology / web — No comments
21
May 10

Google Font API makes the web a little nicer

Almost everyone who has worked with web design understands the limitations of font styling, you are restricted to work with fonts that are available on most users’ computers in order to make things look “nice enough”. Thanks to CSS3 standards, browsers can now make use of web fonts and Google Font API provides a collection of open source web fonts for Making the Web Beautiful!

More information available here.

technology / web — No comments
30
Apr 10

VMForce!

Java inside Force.com!

Salesforce and VMWare are introducing vmForce, the first enterprise cloud for Java developers.

No need to worry about hardware, complex software stacks, scalability, databases, etc… let Force.com handle all that!

development / technology / web — No comments
13
Apr 10

A new Google Docs

Google just released new features for Google Docs, including a new addition to the suite called Drawings!

As a user of google spreadsheets I was very aware of performance issues when working with large data files and this new version of the application seems to boost performance and at least scrolling seems to work very well.

These are some great enhancements to the Google Docs suite and hopefully this brings more ideas for integrating Google Docs with Force.com through the Google Data API Toolkit.

Here’s a video with more info:

technology — No comments
07
Feb 10

Nexus One

The nexus one video series are awesomee, one nexus one please.

development — No comments
04
Feb 10

Force.com Apex Merge/Replace Class ;)

Hello again!

I just developed an Apex class for performing replace/merge operations on any kind of object, and yes any kind of relations as well! , so it doesn’t matter if you have master-detail relationships that can’t be modified, objects tied in a master-detail relationship will be cloned, deleted and inserted with the new values to simulate a merge operation!

To use the Merge class just create an ObjectMerge instance, passing as an argument of the constructor your current record:

ObjectMerge oMerge = new ObjectMerge(SourceObject);

And to peform the merge operation just use the replaceRecord method and thats it!, you can specify if you want to delete the source record after the merge operation is done.

oMerge.replaceRecord(MergeToThisObjectID,DeleteSourceObject);

You can limit the number of records that will be processed in the merge operation for Master-Detail relations to avoid hitting governor limits. The ObjectMerge class will let you know if there are any objects left, and if this is the case just continue performing the merge operation.

Force.com provides a merge DML operation but it’s only available for some of their standard objects, this class can help you get around that. There are still some limitations with this class due to governor limits in the number of describe calls but unless you have a large amount of objects related to the replaced/merged record it should work pretty well.

For now, the Object Merge class only merges/replaces custom objects related to your record, but this can be changed in the class , however keep in mind that no more than 10 relations can be processed due to describe calls limitations so be careful when removing the custom objects limitation because there can be many Non-Custom objects related to your record.

I’ll leave a link in this post to the files but for now here’s an example of how to use the ObjectMerge class in a VisualForce controller that merges contacts, if you have custom objects tied a contact A and want to merge contact A to Contact B you will see how the ObjectMerge class changes all of the objects from contact A to contact B then deletes contact A. Remember, you can try it with any custom object Enjoy!

Download the files from here –> ObjectMerge

(NOTE: There’s a bug with the code viewer plug-in, please ignore the second viewer)

public class MergeController{
    
    //This is just an Aux Object to get a Lookup Field in the VisualForce Page
    public Contact MergeAux{get;set;}
    //Declare an instance of the Object Merge Class
    private ObjectMerge oMerge;
    //Save the current contact in the controller (optional)
    private final Contact currentContact;
        
    public MergeController(ApexPages.StandardController controller){

//Initialize all of our objects
        currentContact = (Contact)controller.getRecord();    
        MergeAux =new Contact();
        oMerge = new ObjectMerge(currentContact);        
        
    }
    
    //Merge Action
    public PageReference doMerge(){

try{
     
            //Run the merge operation!, you can specify a second argument to delete the record after merge or not
            oMerge.replaceRecord(MergeAux.ReportsToId,false);
            
            //Do corresponding actions if merge operation was successful
            if(oMerge.bAppliedReplace){
                PageReference ref = new PageReference('/'+MergeAux.ReportsToId);
                ref.setRedirect(true);
                return ref;
            }else{
                return null;

}catch(Exception e){
            
            ApexPages.addMessages(e);
            return null;    
        }
        
    }

}

//And the Visual Force page will look something like this:

<apex:page standardController="Contact" extensions="MergeController">
     
     <apex:form >
         <apex:pageBlock >
             <apex:pageMessages id="messages">
             </apex:pageMessages>
             
             <apex:pageBlockButtons >
                 <apex:commandButton value="Merge" action="{!doMerge}" rerender="messages"/>
             </apex:pageBlockButtons>
             <apex:pageBlockSection columns="1">
                 <apex:outputField value="{!Contact.Name}"/>
                 <apex:inputField value="{!MergeAux.ReportsToId}"/>                
                 
             </apex:pageBlockSection>
         </apex:pageBlock>
     </apex:form>
     
</apex:page>

development — No comments
25
Jan 10

Interesting ways of architecting Apex Triggers

Hello everyone!

I came across a blog post at gokubi.com (http://gokubi.com/archives/two-interesting-ways-to-architect-apex-triggers) about some interesting ways of architecting Apex Triggers.

We have developed a lot of logic in Apex Triggers and ended with some really nasty code in some scenarios; this post got me thinking about new ways to architect triggers using a more object-oriented approach. So just to follow the thoughts in this post I’ll show you what I did to organize our triggers and it has been working pretty good so far.

NOTE: Please refer to the code section below

//Step 1

I started by creating an Apex Class to replicate some of the triggers functionality…

//Step 2

The next step will be to start coding our Apex Class that will perform all of the logic in our triggers, so let’s say the we are building a trigger for My_Object__c custom object.

//Step 3

And finally, we just need to create the Apex Triggers that will just initialize our Trigger class and initialize an instance of the corresponding Apex Class that will handle all of the logic.

And that’s it! Just remeber to cast the the collections correctly before accessing the collections from the ExtTrigger class because we can’t work with generic sobject collections.

Some of the benefits that I’ve seen by organizing Apex Triggers in this way are the following:

100% Test Coverage in Apex Triggers (although all of the Test Coverage should be done in the handler Apex Class)
Since we can call functions to perform specific actions in Apex Classes, we end up with more organized code, it’s easier to read in the sense that you can just go to see the calls inside the “onBeforeInsert” section for example..
Avoid the max number of characters governor limit:
- Maximum number of characters for a class: 100,000
- Maximum number of characters for a trigger: 32,000

Thanks to everyone that posted in gokubi’s blog post any feedback on this is appreciated

//--------------Step 1

public class ExtTrigger {

public List newValues;
	public List oldValues;
	public Map newMap;
	public Map oldMap;

public Boolean isInsert = false;
	public Boolean isUpdate = false;
	public Boolean isDelete = false;
	public Boolean isUndelete = false;
	public Boolean isBefore = false;
	public Boolean isAfter = false;

public ExtTrigger(List oldValues,List newValues,Map oldMap,Map newMap){

this.newValues = newValues;
		this.oldValues = oldValues;
		this.oldMap = oldMap;
		this.newMap = newMap;

}

//--------------Step 2

public class My_Object_Trigger {

//Attributes
	public ExtTrigger MTrigger;

public My_Object_Trigger(ExtTrigger MTrigger){

this.MTrigger = MTrigger;

}

public void onBeforeInsert(){

try{

doSomething();
			doSomethingElse();

}catch(Exception e){

System.debug('Trigger Insert Exception '+e);
		((My_Object_c)MTrigger.newValues[0]).addError(sExceptionMessage);

}

public void onBeforeUpdate(){

try{

doSomething();
			doSomethingElse();

}catch(Exception e){

System.debug('Trigger Update Exception '+e);
			((My_Object_c)MTrigger.oldValues[0]).addError(sExceptionMessage);

}

//Etc....

private void doSomething(){}
	private void doSomethingElse(){}

}

//--------------Step 3

trigger My_Object_Trigger on My_Object__c (before insert, before update) {

//Create the instance of ExtTrigger and call the constructor in our apex class
	My_Object_Trigger triggerHandler = new My_Object_Trigger(
	new ExtTrigger(Trigger.old,Trigger.new,Trigger.oldMap,Trigger.newMap)
	);

if(Trigger.isBefore){

//Now we set the attributes for our trigger depending on the current context
		triggerHandler.MTrigger.isBefore = true;
	
		if(Trigger.isInsert){
	
			triggerHandler.MTrigger.isInsert = true;
			triggerHandler.onBeforeInsert();
	
		}
	
		if(Trigger.isUpdate){
	
			triggerHandler.MTrigger.isUpdate = true;
			triggerHandler.onBeforeUpdate();
	
		}

}