Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add separator or highlighting title in admin #6

Open
vasylnakvasiuk opened this issue Mar 11, 2010 · 4 comments
Open

Add separator or highlighting title in admin #6

vasylnakvasiuk opened this issue Mar 11, 2010 · 4 comments

Comments

@vasylnakvasiuk
Copy link

I think, that in admin: user (who use admin) must understand, what fields must be translated, and what fields are "static" (without translation).
Maybe, addition separator (between "static" and "tranlsation" fields) or some highlighting title - good idea.
The best (IMHO): add some highlighting title and don't change order (same fields order, like in model). Thanks^)

@ojii
Copy link
Owner

ojii commented Mar 11, 2010

this is something the developer of a multilingual app can do using use_fieldsets. I'm not too happy with the idea of an automated way to do this, maybe I'll think of some 'default' way in case you don't specify your own fieldsets...

@vasylnakvasiuk
Copy link
Author

ok. thanks for great job!!!

@xlotlu
Copy link
Contributor

xlotlu commented Mar 26, 2010

Since Django maintains model fields order, leaving the translation fields unordered breaks expectations, which is wrong (TM).
The fieldset part should indeed be the developer's job. Unless you consider issue #10.

@ojii
Copy link
Owner

ojii commented Mar 26, 2010

Well this would be a optional 'auto-fieldsetting' anyway. I would not enforce this. You can always provide your own fieldsets.

I personally think that some sort of smart default fieldset would be nice. But it has no priority for me at the moment. If someone want's to write up some code for this, go right ahead though.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants