Dimitar thanks for the idea.And Roger thanks for your description that made
me understand better what Dimitar is talking about, as I am not familiar
about "database message resources".
With your reference I am able to present solution to my boss better now.
Thanks a lot guys
learn something new t
>
> If the "Product" described in the first message is pure fiction and
> you have the ability to change the data model you can get rid of the
> multiple names from the "Product" entity, put a "unique_name", use it
> to point to resource in your bundle with some static prefix like
> "product.name."
Few more thoughts on this matter:
I haven't explicitly said that the solution I've proposed is far from
standard i18n functionality, it was my best choice for the given
example.
If the "Product" described in the first message is pure fiction and
you have the ability to change the data model you c
>
> Thanks a lot
No problem about the code
I get your point clearly.
I will definitely take this in to consideration.
I guess I need to look back into my design patterns as well ha
If anyone else have any thoughts or suggestion please fill free to hit me
Thanks
Hi Steven,
I don't know what's the best practice but I'll give you my quick thoughts.
It seems you have to implement some sort of logic (choosing the right name).
The main question is where is the best place to put this kind of logic?
IMO this kind of problems are solved using the "decorator patt
5 matches
Mail list logo
