On Aug 19, 11:46 am, Mathieu Leduc-Hamel wrote:
> I really the approach you took with your datatrans application. Do you have
> an example application of your solution. I would like to implement in our
> solution but i need to convince my colleagues ! ;-)
You can see a live application running
Oh no I think i didn't understand correctly your points.
You created a lookup table, then it means you'll to translate the differents
fields values in one specific section of the admin backend of django which
contain every translatable fields of your project ?
On Thu, Aug 19, 2010 at 11:44 AM, Ma
Hi jef,
I really the approach you took with your datatrans application. Do you have
an example application of your solution. I would like to implement in our
solution but i need to convince my colleagues ! ;-)
Does that mean that with your solution, these translated fields will be in
the general
On Wed, 2010-08-18 at 14:24 -0700, Tom wrote:
> I'm interested in writing a unit test suite that does not require all
> the components of Django to be bootstrapped.
> Correct me if I'm wrong, there are only integration tests bundled with
> Django.
There are lots of tests that would certainly class
> I haven't seen django-datatrans before. Does it play well with the
> Django ORM querying style? The other registration based apps don't.
>
> - hejsan
It does nothing at the ORM layer, it only comes in action on the model
instances, when accessing their fields.
django-datatrans was kept very sim
Am 19.08.2010 um 01:50 schrieb Waldemar Kornewald:
> No comments means it's still not good enough and I'll never get it
> into an acceptable shape? :)
No, in that case we would tell you :) It's much more likely that nobody had
time yet (in the last 3 days) to look at your patch thoroughly.
Jann
