Proposal: JS library in admin and tools
Hi there, After reading this post http://groups.google.com/group/django-developers/browse_thread/thread/8d6e4d7d163db943?hl=en I decided to ask you guys about your opinions in choosing an official JavaScript library for Django - what would be the benefits and drawbacks of that -. I mean, Rails has an official JS library (Prototype/script.aculo.us), Symfony too (Prototype/script.aculo.us), and both can work with other libraries without too much rework. Well, as an Prototype ex-user, and as a currently jQuery heavy user, I much recommend jQuery, because of its ease of use and unobstrusive approach - it doesn't clash with other libraries or classes -. Also, as Django Developer Tools already uses jQuery, it would be great to adopt the same library for it and the admin site, if this extension gets to the Django trunk. Diogo --~--~-~--~~~---~--~~ 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: Proposal: JS library in admin and tools
Hmm, OK, at least this thread seems to be constructive, not just flame war... :-) Jacob, could you please open a thread about the admin-ui proposal? If I can contribute already, I'd like to make some propositions there, all of them interface-related... Thanks, Diogo On 18 ago, 16:36, Yuri Baburov wrote: > On Wed, Aug 19, 2009 at 1:53 AM, Jacob Kaplan-Moss wrote: > > > On Tue, Aug 18, 2009 at 12:35 PM, Yuri Baburov wrote: > >> Do you think that using *any* javascript framework for admin interface > >> will get boost for useful admin, overall django improvements and > >> third-party plugins development? > > > That's a different question entirely. The admin's an optional > > *application*, not part of the framework-y parts; it's also designed > > for end-users, not other developers. Data entry clerks aren't > > constrained by a choice of tooling in the admin interface the way > > developers would in the framework as a whole. Indeed, if you look at > > the admin-ui SoC project you'll see that this ship has already sailed: > > the new features added there (and, Murphy willing, to trunk soon > > enough) are indeed using jQuery. > > Jacob, > > How Django will/would package jQuery? That one for admin-ui. > > This will probably be part of proposal, but maybe you can tell something now > :) > > -- > Best regards, Yuri V. Baburov, ICQ# 99934676, Skype: yuri.baburov, > MSN: bu...@live.com --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
So has Instagram...
... just been acquired by Facebook? And it uses Django? The feeling I'm having today is not of surprise; for a lot of Django users and developers, it's no news that this framework can handle huge traffic and highly-demanding scalable systems. But the feeling I have is of deep happiness for being a small part of such a big and awesome community that you built. Therefore, I thank you all for keeping evolving this great framework along with its community, and hope that it keeps being my favorite MVC for many years to come. :-) Cheers! Diogo -- 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/-/3kBV96WVAUQJ. 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: Python 3
http://docs.djangoproject.com/en/dev/faq/install/#can-i-use-django-with-python-3 On Dec 15, 5:45 am, sirex wrote: > On 15 Gruo, 01:51, Russell Keith-Magee > wrote: > > > but we're not planning to actively support Python 3 any time soon. > > Why? > > Maybe there should be two versions of Django, one that supports Python > 3 and other that supports Python 2? -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-develop...@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: JsonField
Hi, guys, I agree that we should use the right tool for the job; But even a relational database can be used for semi-structured data when it's not going to be directly queried. Matter of fact, there's even a design pattern recognized for that: http://martinfowler.com/eaaCatalog/serializedLOB.html Example of use: think of a semi-structured data store (in a relational database) that is going to be read through a search engine (think about ElasticSearch of Solr, here). But yes, if you're going to need to query for this data by parts of the JSON field, then you're shooting your own foot. So, in the end, we have to think a lot about what's the problem we're trying to solve - it's not as simple as "don't use RDBMS for non-relational data" -, IMHO. Well, at least here's my 2 cents. Cheers, Diogo On 8 nov, 08:34, Tom Evans wrote: > On Mon, Nov 7, 2011 at 11:48 PM, Torsten Bronger > > wrote: > > > While I appreciate that Django core is supposed to enforce good > > design practices, one must be careful with that if some practice may > > have valid use cases. You cannot prevent the user from shooting in > > the foot anyway. > > > While we make extensive use of the relational model in our project, > > I remembered to have a couple of JSON fields (though we don't have a > > field class them them so far), so I skimmed through our code to see > > why we did this. > > And so do I - the main point here is that we have both successfully > loaded the gun and aimed it at our foot without this field existing in > core. I think it's important to have that distinction between things > you can do and things you should do, in order to make you think > "should I really be doing this". > > Cheers > > Tom -- 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: Translation corrections
Thanks a lot, guys! I'm looking forward to make my move into helping Django to evolve! :-) See ya! Diogo On Jul 21, 3:26 am, "Andrews Medina" <[EMAIL PROTECTED]> wrote: > On Mon, Jul 21, 2008 at 12:45 AM, diogobaeder <[EMAIL PROTECTED]> wrote: > > > Hi! > > Hi, > > I'm Brazilian too. > > > > > I'm willing to start contributing to Django, already, but in a field > > that will not be hard for me to understand, and in which I can be more > > usefull: the Brazillian-Portuguese translation package. I'd like to > > propose some corrections in it, since I'm Brazillian and do not agree > > with some terms and phrases used in it. > > That's great. I think that you can contribut in the translate project > for the Django documentation to portuguese. For more informations, see > the group (http://groups.google.com/group/django-l10n-portuguese) and > the repository (http://code.google.com/p/django-l10n-portuguese/) > about this project. > > There are a group for brazilians djangonauts too. The group is > ahttp://groups.google.com/group/django-brasiland website > ishttp://djangobrasil.org > > Thanks! > > -- > Andrews Medinawww.andrewsmedina.com --~--~-~--~~~---~--~~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~--~~~~--~~--~--~---
Re: Global custom tags
Ops, sorry, Alex, it was a lack of attention of mine... I tabbed the auto-complete for the developers list, sorry... I'll repost it in the correct list, please ignore this one. Thanks, Diogo On Jul 2, 3:04 pm, Alex Gaynor wrote: > On Thu, Jul 2, 2009 at 1:03 PM, Diogo Baeder wrote: > > Hi there, > > > Is there a way to create a custom tag that can be used in different > > applications at the same time, so that I could make the call on the > > "base.html" template? The custom tag, here, is a blog subjects menu, which I > > want to use in all the pages (all the apps) of the website, in the frontend. > > > I know that I must create a "templatetags" subdirectory, to act as a > > module, inside the apps, if I want to create a template tag for that app, > > but what if I want to make it visible to all apps and callable from a base > > template? > > > Thanks! > > > __ > > Diogo Baeder > >http://www.diogobaeder.com.br > > django-developers is for the development of Django itself, not development > with Django. Your question should be asked on the django-users mailing > list. > > Alex > > -- > "I disapprove of what you say, but I will defend to the death your right to > say it." --Voltaire > "The people's good is the highest law."--Cicero --~--~-~--~~~---~--~~ 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: Cannot access admin site after update
Russ,
I "updated" to revisions 11000 and 10500, and the problem is still
there. I noticed that the problem happens right down the
{% get_admin_log 10 as admin_log for_user user %}
part of the recent actions, and, given my recent move from a desktop
machine to a laptop, I think it's some inconsistency in my logs. So,
given the problem might be in my machine, I'll put this one in the
django-users group, but thanks nevertheless.
Diogo
On Jul 7, 12:56 am, Russell Keith-Magee
wrote:
> On Tue, Jul 7, 2009 at 11:46 AM, Diogo Baeder wrote:
>
> > Hi, guys,
>
> > Got this after updating my django trunk working copy to r.11199, and
> > cannot access the admin site anymore:
>
> >http://dpaste.com/63968/
>
> > Any ideas of what it might be?
>
> If you are looking for help debugging a problem, please ask on
> Django-users. Django-developers is for discussing the development of
> Django itself.
>
> If you think you have found a problem with a recent Django commit and
> you're looking to help correct it, you're going to have to narrow down
> your claim - "I updated to r11199" doesn't give us much to work with.
> Ideally, it would be nice to have a minimal example that reproduces
> the problem, and the specific revision at which things break - i.e.,
> works at r11101, breaks on r11102.
>
> 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: Problem with admin after moving to another machine
Russ: yes, I must be out of my mind. Yes, I will post in the other group. Sorry for this unbrained programmer... I'll try to drink less Coca- Cola and see if my attention comes back... :-P Thanks! And congrats for the great support! :-) Diogo On Jul 7, 11:58 pm, Russell Keith-Magee wrote: > On Wed, Jul 8, 2009 at 10:16 AM, Diogo Baeder wrote: > > > Hi there, > > > I started to have this error: > >http://dpaste.com/64355/ > > while trying to access my admin site, after I moved my website from one > > machine (my desktop) to the other (my laptop). I already restored my > > PostgreSQL database, and recreated the superuser (while trying to solve > > this problem), but I still cannot access the admin page... can it be > > something with the recent actions log? If so, how do I purge it? I don't > > need this log... > > Like I told you yesterday, Django-developers is for discussing the > development of Django itself. "How do I" questions should be directed > to django-users. > > 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 -~--~~~~--~~--~--~---
