cfml

What is best practice for things like table row looping from a record set? Is that to be kept out of the view? In the model?

I typically do UI stuff in the view, so if I had a query result provided to it, I let the view loop over it. I have seen people abstract out doing that in the model and then returning the HTML to render, but I think its easier to let the views do what they need.

&gt;  I have seen people abstract out doing that in the model and then returning the HTML to render
Did you kill those people?

The ones that do that or the ones that don't do that? You are being vague sir.  :smile:

It looks like someone has a case of the Thursdays today...  :stuck_out_tongue:

Seriously though Derek... if all yer doing is looping over the records to output them and/or format-them-for-output and then output them: view.

If your loop performs any other logic on the values... model. And then loop again to just output them in the view. If that makes sense.

(but I will not pollute this thread with that stuff).

```&lt;!--- in the view ---&gt;

&lt;!--- good ---&gt;
&lt;cfloop query="stuff"&gt;
    #someSimpleValue# #someDateValue.dateFormat("yyyy-mm-dd")#&lt;br&gt; &lt;!--- that's just display logic. All good ---&gt;
&lt;/cfloop&gt;


&lt;!--- bad ---&gt;
&lt;cfloop query="stuff"&gt;
    #someOtherObject.doSomeMoreProcessing(someValue)#&lt;br&gt; &lt;!--- that's business logic, so does not belong in a view ---&gt;
&lt;/cfloop&gt;```

oh so what about if I have a function that just changes a badge color? `setRejectListBadgeColor(rcd.reason)`

I'm still ok doing that in a view if its simpler

ok, maybe stupid question, but how do you access a model function within a view?

`service = new <http://models.my|models.my>.awesome.Service();`

assuming a cfscript block at the top of the page

then `#service.doSomething()#`  on the page

Is the logic hitting a database or is just just a UDF for display purposes? If a simpler UDF for display, you can always put it in ApplicationHelper.cfm.

&gt; how do you access a model function within a view?
You _don't_ (not a ColdBox answer; and MVC one).

ApplicationHelper.cfm sounds like something CFWheels would implement / misuse to put uncategorised UDFs into a special magic global space that is inappropriate for almost all situations, and is jut bad app design.

I could see how there might be some view helper libs that could be exposed to all views (eg: RomanNumeralHelper or something specifically view-ish), but that would make no sense being exposed everywhere.

But I'll double-down on the notion that any functionality that does anything more than format a value for display should not be called from the view layer. And the _formatting_ functionality should have no side effects.

it's specifically for display purposes only

the applicationhelper.cfc works like a champ,  but you're right, I don't need it exposed everywhere so I just put it in indexHelper.cfm

I actually should have suggested indexHelper first, good call.  :the_horns: