Re: Django Admin Revamp - Any updates?
On Friday, April 27, 2012 1:06:06 AM UTC+2, Victor Hooi wrote: > Hi, > > Is there any news on the Django Admin rewrite front? > I'm very interested in this topic and have some time to kill so I started the wiki page don't hesitate to comment, correct, review and add you own ideas. https://code.djangoproject.com/wiki/HydroAdmin Regards, Amirouche -- You received this message because you are subscribed to the Google Groups "Django developers" group. To view this discussion on the web visit https://groups.google.com/d/msg/django-developers/-/Ji8aLKXnVd4J. To post to this group, send email to django-developers@googlegroups.com. To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
Re: Proposal: Django URL Admin (django-urls)
On Friday, December 7, 2012 9:07:32 PM UTC+1, Zach Borboa wrote: > > Does something like this exist already? If not, it should. How this can be useful ? You still need to write the view in Python then why not write the urls in Python too, like it's currently the way to go. If something in this spirit might be useful is something where the view could be generated which would be something like databrowser or admin. Could you elaborate ? -- You received this message because you are subscribed to the Google Groups "Django developers" group. To view this discussion on the web visit https://groups.google.com/d/msg/django-developers/-/WUkyoQyQa7YJ. To post to this group, send email to django-developers@googlegroups.com. To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
Re: Is Django documentation translations to land in main repository ?
On Saturday, December 15, 2012 5:05:36 AM UTC+1, Russell Keith-Magee wrote: > > > On Sat, Dec 15, 2012 at 11:53 AM, Amirouche B. > > > wrote: > >> Héllo, >> >> Everything is in the title. Does Django core dev's want to have localized >> documentation in main repository or should it be managed by local DUG ? >> > > Yes :-) > > In a perfect world, you'd be able to get documentation in other languages > on docs.djangoproject.com. If you look at the URL space, you'll see that > we've already prepared for translations -- you hit /en/dev to get the > development docs; in theory, we could serve /fr/dev for french > documentation. > Cool, didn't noticed > > However, what we're missing is the process for managing these translations. > > The core team speak a few languages (we've got German, French and Spanish > covered, and possibly a couple of others), but aren't in a position to > review and commit revisions for lots of other significant languages. > > Taking i18n and l10n as an example; we've moved to using Transifex > specifically because it allows us to give control of translations to local > language communities; then, once per release, we push a single commit of > translation updates to the main repository. Ideally, we'd take a similar > approach for translated docs, but Transifex isn't really well suited to > translation of large bodies of text. > > So - your translation efforts are definitely welcome. What we need to work > out is the process by which we can practically use these translation > efforts -- and, more importantly, make sure that they're kept up to date > (e.g., once a base translation is done, ensuring that translation teams > have a 'todo' list, and we can indicate to readers which translations are > current, and which are stale). Any suggestions on how we could manage this > are also welcome. > I never used Transifex, I don't know why this can not be used for large projects. Maybe it can work ? Here is what I propose: - A manager is choosed among every LUG to manage a Transifex project for its langage - Once every release or every 6 months POs are pushed to main repo - If the L10N effort lakes behind the releases, users are notified that the documentation is not available in their language and propose a) to go to old doc b) to go to english doc (I don't think this is handled by readthedocs so this is another issue) The manager (or the managing team) will have in charge to update PO files on Transifex in a regular fashion. Maybe someone with Transifex experience can tell more about that. Another option I think of, is to break documentation directory and maybe even each locale directory into a git submodule so that LUGs can work on translation without polluting the main git history with L10N stuff while still being able to use git to manage the translation which will also allow to avoid having to use Transifex. Looking forward having other insights about this issue. Regards, Amirouche -- You received this message because you are subscribed to the Google Groups "Django developers" group. To view this discussion on the web visit https://groups.google.com/d/msg/django-developers/-/mcEoC29xAmIJ. To post to this group, send email to django-developers@googlegroups.com. To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
Re: Is Django documentation translations to land in main repository ?
On Sat, Dec 15, 2012 at 11:53 AM, Amirouche B. wrote: > Héllo, > > Everything is in the title. Does Django core dev's want to have localized > documentation in main repository or should it be managed by local DUG ? > Yes :-) In a perfect world, you'd be able to get documentation in other languages on docs.djangoproject.com. If you look at the URL space, you'll see that we've already prepared for translations -- you hit /en/dev to get the development docs; in theory, we could serve /fr/dev for french documentation. However, what we're missing is the process for managing these translations. The core team speak a few languages (we've got German, French and Spanish covered, and possibly a couple of others), but aren't in a position to review and commit revisions for lots of other significant languages. Taking i18n and l10n as an example; we've moved to using Transifex specifically because it allows us to give control of translations to local language communities; then, once per release, we push a single commit of translation updates to the main repository. Ideally, we'd take a similar approach for translated docs, but Transifex isn't really well suited to translation of large bodies of text. So - your translation efforts are definitely welcome. What we need to work out is the process by which we can practically use these translation efforts -- and, more importantly, make sure that they're kept up to date (e.g., once a base translation is done, ensuring that translation teams have a 'todo' list, and we can indicate to readers which translations are current, and which are stale). Any suggestions on how we could manage this are also welcome. Yours, Russ Magee %-) > Thanks to Pilot Systems, I improved a bit the french documentation > [1] basically what I've done is converted it to use the Sphinx support of > .po files and translated the how-tos. > > Now what main repo needs: > - fix the Makefile [2] like it's done in [1] or something smarter maybe > convert the Makefile to a Python script so that we have a better handling > of locales please see [2] > - the source documentation needs some fixes to be fully possible to do > L10N but it's not a priority (problems might be solved in Sphinx) > > Mind the fact that getting .po support and the facility to do > documentation L18N in the main repo is needed to avoid any future effort to > do what is IMO a mistake to translate the documentation in the rst files. > > What do you think ? > > > Thanks. > > > [1] https://bitbucket.org/amirouche/django-fr-translation > [2] > https://bitbucket.org/birkenfeld/sphinx/issue/1026/makefile-for-building-mo-and-merging-po > > -- > You received this message because you are subscribed to the Google Groups > "Django developers" group. > To view this discussion on the web visit > https://groups.google.com/d/msg/django-developers/-/r5vbKm3wovEJ. > To post to this group, send email to django-developers@googlegroups.com. > To unsubscribe from this group, send email to > django-developers+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/django-developers?hl=en. > -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com. To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
Is Django documentation translations to land in main repository ?
Héllo, Everything is in the title. Does Django core dev's want to have localized documentation in main repository or should it be managed by local DUG ? Thanks to Pilot Systems, I improved a bit the french documentation [1] basically what I've done is converted it to use the Sphinx support of .po files and translated the how-tos. Now what main repo needs: - fix the Makefile [2] like it's done in [1] or something smarter maybe convert the Makefile to a Python script so that we have a better handling of locales please see [2] - the source documentation needs some fixes to be fully possible to do L10N but it's not a priority (problems might be solved in Sphinx) Mind the fact that getting .po support and the facility to do documentation L18N in the main repo is needed to avoid any future effort to do what is IMO a mistake to translate the documentation in the rst files. What do you think ? Thanks. [1] https://bitbucket.org/amirouche/django-fr-translation [2] https://bitbucket.org/birkenfeld/sphinx/issue/1026/makefile-for-building-mo-and-merging-po -- You received this message because you are subscribed to the Google Groups "Django developers" group. To view this discussion on the web visit https://groups.google.com/d/msg/django-developers/-/r5vbKm3wovEJ. To post to this group, send email to django-developers@googlegroups.com. To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
Re: Django Admin Revamp - Any updates?
On Fri, Dec 14, 2012 at 11:06 PM, Travis Swicegood wrote:
> Is there a wiki page on the admin and changes that are planned for it?
> This comes up every few months with a "hey, I've done X with the admin,
> can we just use it to replace/update contrib.admin?" Would be nice to have
> everyone's (and by everyone's, I mean Idan's) thoughts on where the admin
> is heading so this conversation doesn't have to keep popping up (or at
> least it can be answered by "go contribute to {{ insert url }}."
>
> /me goes back to yelling at kids on his lawn...
>
> To the best of my knowledge, no, this wiki page doesn't exist, and yes,
creating such a wiki page, gathering requirements and so on, would be a
good next step.
The other thing I would point out is that admin is a contrib app for a
reason -- it's a standalone app. It's entirely possible to recreate
everything Django's admin does as a third party application. If a third
party admin implementation were to appear that had a better feature set
than the existing admin, and/or a better codebase to start from, and there
was a reasonable migration path from old admin configurations to new admin
configurations, *that* might be a viable way to get a new admin into Django.
However, all of this is dependent on someone having enough of an itch, and
enough spare time to scratch it.
Yours,
Russ Magee %-)
--
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send email to django-developers@googlegroups.com.
To unsubscribe from this group, send email to
django-developers+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/django-developers?hl=en.
Re: Django 1.1 is not installable
I'm only using Django 1.1 as part of CI tests, and they have started failing recently because of this, so I'd be happy to see it fixed. -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com. To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
Re: Django Admin Revamp - Any updates?
Is there a wiki page on the admin and changes that are planned for it? This
comes up every few months with a "hey, I've done X with the admin, can we just
use it to replace/update contrib.admin?" Would be nice to have everyone's (and
by everyone's, I mean Idan's) thoughts on where the admin is heading so this
conversation doesn't have to keep popping up (or at least it can be answered by
"go contribute to {{ insert url }}."
/me goes back to yelling at kids on his lawn...
-T
--
Travis Swicegood | @tswicegood (most everywhere)
On Dec 14, 2012, at 8:00 AM, is_null wrote:
> I'm not sure if it's worth mentioning ...
>
> 2. Secure CRUD one-liner goal
>
> The new admin app should, like the current admin app, allow the user to
> enable full secure (permission-based) CRUD in one line of code.
>
> --
> You received this message because you are subscribed to the Google Groups
> "Django developers" group.
> To view this discussion on the web visit
> https://groups.google.com/d/msg/django-developers/-/fxyL124kbP8J.
> To post to this group, send email to django-developers@googlegroups.com.
> To unsubscribe from this group, send email to
> django-developers+unsubscr...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/django-developers?hl=en.
--
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send email to django-developers@googlegroups.com.
To unsubscribe from this group, send email to
django-developers+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/django-developers?hl=en.
Re: Django Admin Revamp - Any updates?
I'm not sure if it's worth mentioning ... 2. Secure CRUD one-liner goal The new admin app should, like the current admin app, allow the user to enable full secure (permission-based) CRUD in one line of code. -- You received this message because you are subscribed to the Google Groups "Django developers" group. To view this discussion on the web visit https://groups.google.com/d/msg/django-developers/-/fxyL124kbP8J. To post to this group, send email to django-developers@googlegroups.com. To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
Re: Django Admin Revamp - Any updates?
On Saturday, April 28, 2012 10:13:03 PM UTC+2, Idan Gazit wrote: > As I wrote, I'd like to have a clear idea of what a new admin will > accomplish before starting to bolt on enhancements, even great enhancements > like grappelli. > > The admin was an impressively future-proof design, given that it is still > so useful years after it was designed. We should aim to make an admin that > will be relevant and useful five years from now; we can't design for that > without a couple of clear, simple goals. Grappelli may or may not align > with those goals. > As I just blogged: "Last year, I sent a letter to santa asking for 12 transformers with super laser powers. I waited nicely and then received a little playmobil." A couple of "clear, simple goals", you ask: 0. Loose coupling goal The new admin app should not include ChangeList (ie. django-tables2), form rendering (ie. django-floppy-forms), queryset filtering (ie. django-filter), etc, etc 1. KISS goal The new admin app should not try to abstract the basics of Django elegant design. Instead of: admin.site.register(Foo, FooAdmin). I could use: url(r'myapp/foo/', admin.ListView.as_view(table=FooTableClass, filters=FooListFilters), name='myapp_foo_list'). Of course, I could use a shortcut / factory / something cool. But the new admin app would be so simple I wouldn't need ModelAdmin and I could override anything easily and I could even reuse parts of it in my own views (see "Loose coupling"). Hope this helps. -- You received this message because you are subscribed to the Google Groups "Django developers" group. To view this discussion on the web visit https://groups.google.com/d/msg/django-developers/-/8oNVlVMOya4J. To post to this group, send email to django-developers@googlegroups.com. To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
Re: Django Admin Revamp - Any updates?
The problem with the external app approach is that it will break the integration between different apps. There is no way to avoid it. Besides, developing something for the django.contrib.admin with an UI up to the recent standards is quite difficult. Going Bootstrap is not only the thing of the moment, is a great way to open the admin app to a wide range of custom widgets already available to the Bootstrap ecosystem, with the nice plus of an out-of-the-box support for mobile devices. Commercially speaking, it's a winning choice. I think that the actual fragmentation of the admin-bootstrap implementations is pretty bad for the django ecosystem. No one sane of mind would base his project on any of the available solutions because there is no official one, and new releases of Django may (will) break it. In my opinion, the solution is easy. The core team should choose a project/team, bless it and wait to see how it will evolve. When ready, integrate it on the core and made it available as an _alternative_ to the default admin package. On 14 December 2012 10:36, James Pic wrote: > There are *many* apps providing bootstrap templates for > django.contrib.admin, here a few: > > - https://github.com/michaelhelmick/django-bootstrap-admin > - https://github.com/gkuhn1/django-admin-templates-twitter-bootstrap > - https://github.com/riccardo-forina/django-admin-bootstrapped > - https://github.com/aobo711/bootstrap-django-admin > - I myself did such templates. > > My thoughts, in case it helps: > > - it takes just a few hours to convert Django admin to bootstrap, that's > probably why there are so many admin/bootstrap apps out there, > - but it's better to tweak colors, just converting the HTML to bootstrap > ends in a too "grayish", "sad" interface IMHO, > - it's a very popular demand - again that's why there are so many apps out > there, > - it's a great opportunity to make a cool navbar, > - forms don't have .as_bootstrap() method, but django-forms-bootstrap > provides |as_bootstrap. That's required for the admin/bootstrap integration > to be "perfect", but optional to make it "good enough". > - this can live in external apps anyway ... > > -- > You received this message because you are subscribed to the Google Groups > "Django developers" group. > To post to this group, send email to django-developers@googlegroups.com. > To unsubscribe from this group, send email to > django-developers+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/django-developers?hl=en. > -- Mobile: +39 3409090319 Visit my website: www.codingnot.es -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com. To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
Re: Django Admin Revamp - Any updates?
There are *many* apps providing bootstrap templates for django.contrib.admin, here a few: - https://github.com/michaelhelmick/django-bootstrap-admin - https://github.com/gkuhn1/django-admin-templates-twitter-bootstrap - https://github.com/riccardo-forina/django-admin-bootstrapped - https://github.com/aobo711/bootstrap-django-admin - I myself did such templates. My thoughts, in case it helps: - it takes just a few hours to convert Django admin to bootstrap, that's probably why there are so many admin/bootstrap apps out there, - but it's better to tweak colors, just converting the HTML to bootstrap ends in a too "grayish", "sad" interface IMHO, - it's a very popular demand - again that's why there are so many apps out there, - it's a great opportunity to make a cool navbar, - forms don't have .as_bootstrap() method, but django-forms-bootstrap provides |as_bootstrap. That's required for the admin/bootstrap integration to be "perfect", but optional to make it "good enough". - this can live in external apps anyway ... -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com. To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
Re: Django Admin Revamp - Any updates?
> > > > > Idan - you mentioned you'd like to get thoughts on what we hope to achieve > > in a new admin - basically, what is the purpose of Django's contrib.admin - > > is that right? If I'm not mistaken the new admin interface couldn't be builded because none of the django core developers had the resources and time to start on such a large task. Has the perhaps changed ? > > > > Is there some place that people can brainstorm or contribute their thoughts > > on this? Should somebody make a wiki page for collecting all this? > > This would indeed be a great asset to get started! -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com. To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
