How to set the sucess message after inserting values to db in django admin site

How to set the sucess message after inserting values to db in django admin site like message department added sucessfully model: class departmentForm(forms.ModelForm): model=mdldepartments def clean(self): dept_msg = u"Department name allows only

Re: managing javascript and css resources

Gabriel, For addons.mozilla.org we use this syntax: http://github.com/jbalogh/zamboni/blob/master/settings.py#L268 In TEMPLATE_DEBUG=False, we use a minified version of these assets, in TEMPLATE_DEBUG=True we just use the individual assets unbundled. We have a management command which

Re: managing javascript and css resources

I like the idea of having these "bundles" or "stacks" for media. Just thinking out loud here, if there were a compression engine in play that could do concatenation as well as minification you could have a useful syntax for ordered combinations of scripts similar to how ModelAdmin's fieldsets work

Re: Cujo .... an experimental branch of django.

On Wed, Apr 21, 2010 at 1:33 PM, Jeremy Dunck wrote: > On Wed, Apr 21, 2010 at 1:14 PM, Tom X. Tobin wrote: > ... >> There are no formal plans (on experimental's side) to merge anything >> from experimental to trunk.  Anyone is welcome to package up

Re: Cujo .... an experimental branch of django.

On Wed, Apr 21, 2010 at 1:47 PM, Kevin Howerton wrote: > From the github: > > "* Commits should be atomic: they should each encompass a single logical >change that works on its own. You can use "git rebase --interactive" to >collapse multiple commits into a

Re: Cujo .... an experimental branch of django.

>From the github: "* Commits should be atomic: they should each encompass a single logical change that works on its own. You can use "git rebase --interactive" to collapse multiple commits into a single commit before pushing your code up for contribution." I think the idea is to

Re: Cujo .... an experimental branch of django.

On Wed, Apr 21, 2010 at 7:14 PM, Tom X. Tobin wrote: > On Wed, Apr 21, 2010 at 1:08 PM, Tom Evans wrote: >> On Wed, Apr 21, 2010 at 6:14 PM, Tom X. Tobin >> wrote: >>> That said, we don't want to degrade the

Re: Cujo .... an experimental branch of django.

On Wed, Apr 21, 2010 at 1:14 PM, Tom X. Tobin wrote: ... > There are no formal plans (on experimental's side) to merge anything > from experimental to trunk.  Anyone is welcome to package up code from > experimental and champion a change for inclusion in Django proper,

Re: Cujo .... an experimental branch of django.

On Wed, Apr 21, 2010 at 1:08 PM, Tom Evans wrote: > On Wed, Apr 21, 2010 at 6:14 PM, Tom X. Tobin wrote: >> That said, we don't want to degrade the signal-to-noise ratio here, so >> we'll be working off of the mailing list Kevin mentioned. >> >

Re: Cujo .... an experimental branch of django.

On Wed, Apr 21, 2010 at 6:14 PM, Tom X. Tobin wrote: > That said, we don't want to degrade the signal-to-noise ratio here, so > we'll be working off of the mailing list Kevin mentioned. > Presumably, you will be discussing anything you plan to merge from

Re: managing javascript and css resources

I've read hpws, but not the sequel. I suppose following that train of thought, there should be the option for using 2 separate stacks - one for the head of the document, and one for the tail (stylesheets at the top and scripts at the bottom!) > "These aren't something we could easily incorporate.

Re: managing javascript and css resources

"I understand that Django has historically been anti-javascript-framework-blessing, and I'm wondering if opening this can of worms would mean having to incorporate some kind of a pluggable backend system (for working with different frameworks, or multiple frameworks at a time) - something I've

Re: managing javascript and css resources

On Wed, Apr 21, 2010 at 11:40 AM, Owen Nelson wrote: > Jacob Kaplan-Moss wrote: >> If you'd like to look into it, a good place to start would be by >> looking at the existing static asset management tools in the ecosystem... >> > I most certainly would like to.  I'll prepare a

Re: Cujo .... an experimental branch of django.

On Wed, Apr 21, 2010 at 11:46 AM, Kevin Howerton wrote: > Thanks for the support Russ... > > I think Cujo (the name at least) has been abandoned and I have joined my > efforts with some other developers also interested in contributing to an > experimental branch. > >

Re: Cujo .... an experimental branch of django.

On Wed, Apr 21, 2010 at 11:53 AM, Jeremy Dunck wrote: > Tom, it may be inconvenient at this point, but please consider forking > the github django repo so that upstream pulls can be handled more > easily. I've been running a private Git mirror of Django for a long time now,

Re: Cujo .... an experimental branch of django.

Tom, it may be inconvenient at this point, but please consider forking the github django repo so that upstream pulls can be handled more easily. On Wed, Apr 21, 2010 at 11:46 AM, Kevin Howerton wrote: ... > I think Cujo (the name at least) has been abandoned and I have

Re: Cujo .... an experimental branch of django.

Thanks for the support Russ... I think Cujo (the name at least) has been abandoned and I have joined my efforts with some other developers also interested in contributing to an experimental branch. http://github.com/tomxtobin/django-experimental

Re: managing javascript and css resources

Jacob Kaplan-Moss wrote: > If you'd like to look into it, a good place to start would be by > looking at the existing static asset management tools in the ecosystem... > I most certainly would like to. I'll prepare a "report" with my findings. -- You received this message because you are

Re: managing javascript and css resources

Hi Owen -- I'd agree that static asset handling in Django needs to be improved, though like you I'm not sure of the correct direction for this to go in. If you'd like to look into it, a good place to start would be by looking at the existing static asset management tools in the ecosystem -- last

managing javascript and css resources

I've been thinking about this ever since I learned that django's admin was going to be using jQuery, but I admit I didn't really consider it that important until recently (building sites against 1.2-beta). I know now is not a fantastic time to be talking about features, but this is something I'd

Re: Process discussion: reboot

Hello, I'm glad someone from the core development team brings this up. I've lost motivation to contribute to Django after the many failed attempts to improve WSGI support. I consider myself of the users Shawn Milochik describes: "There is frustration on the part of some Django users who would

Re: Process discussion: reboot

On Tue, Apr 20, 2010 at 4:39 PM, Jacob Kaplan-Moss wrote: > On Mon, Apr 19, 2010 at 2:32 PM, Giuseppe Ciotta wrote: >> Having an additional field{s} in the ticket, only accessible to core >> developers, where they would put the "official" (as in: approved