Brian,
Now that I read it ... so obvious. I've come from a long history of procedural
coding. So I understand OOP but don't take full advantage of it yet ...
obviously .. :-)
Thanx and Greetz!
Gerard.
Brian Neal wrote:
> On Sep 25, 4:33 am, Gerard Petersen <[EMAIL PROTECTED]> wrote:
>> Hi
On Sep 25, 4:33 am, Gerard Petersen <[EMAIL PROTECTED]> wrote:
> Hi All,
>
> I'm finding myself creating more and more fields in a model to keep my
> templates clean. Since it's merely temporary calculated data, and not data to
> store permanently it feels like the wrong place. An example:
>
>
Daniel,
On the object dynamicness, I think my brain malfunctioned because somehow I new
this, but you just helped me remove 3 fields on my product model ... ;-)
As far as placing the calculation in the view or the template (thanks on the
example btw). An invoice is now generated in html but
On Sep 25, 10:33 am, Gerard Petersen <[EMAIL PROTECTED]> wrote:
> Hi All,
>
> I'm finding myself creating more and more fields in a model to keep my
> templates clean. Since it's merely temporary calculated data, and not data to
> store permanently it feels like the wrong place. An example:
>
>
Hi All,
I'm finding myself creating more and more fields in a model to keep my
templates clean. Since it's merely temporary calculated data, and not data to
store permanently it feels like the wrong place. An example:
I have a product model (child object of an order model). The product has a
5 matches
Mail list logo
