> Should I:
>
> 1. Make a separate field for each translation and add a method in the
> model to return the correct translation to use in templates?
>
> 2. Make a separate table for translations in general with a foreign
> key to the original record and look up the translation that way?
I think y
I would like to share with you some different ideology...
I don't like to use any external software to work aside with main
application. Very often, it's just imposible to use cron on client's
hyper-hostings.
The idea is simple, use ajax.
I got very simple mechanism that uses some javascript to s
you're absolutely right.
I shouldn't say that but still its easier to get information from this
group rather than by reading the docs.
last year I was working with Kohana framework and it was pain in the
ass and great loss of time to learn from source code because
documentation was strongly incomp
> You can supply choices argument in model's field constructor. Or
> replace the form's field with the one that has choices in modelform
> for this model.
choices is that little thing I was looking for.. and suprisingly
couldn't find by myself.
many thanks!
PS. django documentation is gett
Is there any simple way to change to in
autogenerated django admin ?
I have some fields that takes simple values to varchar and integer
fields and these values are predefined alternatives.
for example: field for Ms/Mrs/Mr...
simple link to explanation would do...
--~--~-~--~~-
Thank you for all your elaborated answers
However I still don't see the point to have decouped apps in my
project. Web page mainly is a program for serving some text or media
or for saving some user data under the hood. Having an app for
particular business logic AND another pool of views, tags a
> A slightly fuller description of your intended page structure might let
> people provide more accurate answers to your needs.
Let http://pow.dzierzoniow.pl be my fuller explanation. This page is
my old project written in php on Kohana framework.
There is one 'app' used to generate both menus (i
are you saing this:
http://docs.djangoproject.com/en/dev/howto/custom-template-tags/#inclusion-tags
is an explanation to my question ?
If yes, many thanks to you and... silly me.
if not, could you point me some solution explained in detail?
--~--~-~--~~~---~--~~
It's just simple amazing that I waste another night to figure out how
to glue two and more apps together inside one template.
I read about custom tags and I thing it isn't (or at least it
shouldn't be) the way of doing it. too much fuss imho.
Example:
I have home page with menu on one side, news
9 matches
Mail list logo
