Re: Rendering a field value in a custom way

Hi Wayne, thanks for your answer. I now created a function that applies the render functions dynamically to the object. So get_* is automagically created. You are right about the downsides of this approach. However my designer really does not like filters, so I have to stick to the approach. Ki

Re: Rendering a field value in a custom way

On Dec 11, 5:49 am, Scoox wrote: > Okay, I *think* I figured out a way to fix this. > > I can add methods such as get_stars to the relevant model. > > Then in that method I can do whatever I like with the string (e.g. > convert it to star symbols). > > Would that be the recommended way to do this?

Re: Rendering a field value in a custom way

Okay, I *think* I figured out a way to fix this. I can add methods such as get_stars to the relevant model. Then in that method I can do whatever I like with the string (e.g. convert it to star symbols). Would that be the recommended way to do this? Kind Regards Stephan -- You received this

Re: Rendering a field value in a custom way

Note: Why do I not to use filters? 1. It's nicer if the designer doesn't always have to put |(...) behind the field name. 2. I do not know how to access the object passed in the filter. E.g. if I use {{rating.stars|muBeautify}} the muBeautify filter would only get a unicode "5", but how would it k

Rendering a field value in a custom way

Hi guys, I want to be able to render a custom field. It's supposed to extend a normal char field. I want to place certain content in front of the field, depending upon the fields value. As an example take a simple field that allows entering a number. Instead of displaying the number, I would like