You can see that we created an html Span, and had the style returned from the row of data.  This way the data object can completely customize the style returned. 

----------------------------------------------------------------------------

However, you can see that there are 2 different attributes, and there is that "grp.obj.name".  The reason for this is that the SObject that we use does not and should not contain "Display code".  In the "Model View Controller" model, that means that the SObject is the Model, and the style generation is the View.  

We solve this problem by creating a SObject display object that contains the style customization logic. 

public class DrugGroupDisp
{
    private drug_group__c obj;
    public drug_group__c getObj()
    {
        return obj;
    }
    public void setObj(drug_group__c s)
    {
        obj = s;
    }

   public String getNameStyle()  

  {
        if (some condition} return 'color: red';

       return 'color: green';

    }

                   
    public void Setup(drug_group__c o)
    {
        obj = o;
    }
}

By having a direct reference to the original SObject, we can get access to all of its attributes, and then if needed we can made modifications and save.

the display object gives us a row level wrapper that can provide customizations that the Visual Force Page can use for rendering.

----------------------------------------------------------------------------

Here is how we load the display object:

public List<DrugGroupDisp> getGroups()
    {
         if (groups == null)
         {
             groups = new List<DrugGroupDisp>(); 
            
             for(drug_group__c groupRow : [select id, name, x1, x2, x3...   from drug_group__c])
            {
                DrugGroupDisp grp = new DrugGroupDisp();
                grp.Setup( groupRow );                                 
                groups.Add( grp);
            }     
        }   
        return groups;
    }