So, unless anyone disagrees with the idea that Wilson should have
first dibs on this position, it sounds like we have ourselves a Design
Czar. Or whatever you want to call it. Woot!
On Feb 7, 10:13 pm, Wilson wrote:
> I just discovered this thread today while I was on my way out of town
> so I ha
I just discovered this thread today while I was on my way out of town
so I haven't had a chance to formulate a proper response. I'll try to
do that later, but for now I'll just jump in quickly and say that I
think it would be great to have somebody coordinating design
contributions and advocating f
Thanks for the nod, Tai. I'd have to put some consideration into
whether or not I wanted to accept the responsibility if it were
offered to me, but I certainly appreciate the "nomination!" :)
Just to quickly respond to this:
> But what's stopping people from re-designing the admin outside of
> dj
I agree with you completely, Russ, and I have reason to believe
someone worthy will be at the helm. Stay tuned. :)
On Feb 7, 6:49 pm, Russell Keith-Magee wrote:
> On Mon, Feb 8, 2010 at 6:25 AM, Idan Gazit wrote:
>
> > On Feb 7, 11:58 pm, "j...@jeffcroft.com" wrote:
> >> You're right, Idan. Sor
On Mon, Feb 8, 2010 at 6:25 AM, Idan Gazit wrote:
>
> On Feb 7, 11:58 pm, "j...@jeffcroft.com" wrote:
>> You're right, Idan. Sorry if I steered it off-track! I sent Wilson a
>> message asking him to check out this thread.
>
> Awesome, thanks!
>
>> I think we first need to make sure we ARE going f
Ignore my last post - my 'fix' only fixes one corner case, and not a
very useful one either. I've got it fairly sorted out now, I'll post
tomorrow about this.
Luke
On Sunday 07 February 2010 21:11:42 Luke Plant wrote:
> On Sunday 07 February 2010 10:45:29 Florian Apolloner wrote:
> > Hi,
> >
>
It feels like a catch 22 situation. We need someone to champion and
shepherd design changes into trunk, but we can't assign such a role to
somebody who hasn't met the criteria that each core committer must
meet. To quote the Django documentation, any design czar or core
designer should have "a long
I think it's important to be clear here - I envisage a design czar to
act like a code committer:
- encourage, review, and shepherd work to completion
- assess different approaches to problems, and decide if necessary
- get minor improvements and fixes make into trunk
- make sure there's work ha
On Sunday 07 February 2010 04:07:22 Luc Saffre wrote:
> Luke, I disagree with your explanations. Django behaves oddly.
>
> Model.save() is the place where empty non-nullable fields cause an
> exception.
> There is no reason for ForeignKey to behave differently.
> ForeignKey fields are different
On Feb 7, 11:58 pm, "j...@jeffcroft.com" wrote:
> You're right, Idan. Sorry if I steered it off-track! I sent Wilson a
> message asking him to check out this thread.
Awesome, thanks!
> I think we first need to make sure we ARE going forward with this
> whole "design czar" idea. Neither Alex no
You're right, Idan. Sorry if I steered it off-track! I sent Wilson a
message asking him to check out this thread.
> What we haven't yet come to a consensus on how to bootstrap a
> design czar/team if Wilson is out. I'll be pleasantly surprised if he
> indicates his availability, but assuming that
Attached patches to #12791 and #6918 to show the difference.
Suggesting that #11924 be closed in favor of #6918, or close two and
rename #12791 or #6918 to "Issues with different encodings than utf-8
in EmailMessage"
On Feb 6, 11:24 pm, "oyvind.salt...@gmail.com"
wrote:
> #12791 applies to the b
On Sun, Feb 7, 2010 at 4:24 PM, Martin v. Löwis wrote:
>> It can now convert and start the test suite, however, this doesn't
>> produce any results, yet.
>
> Following up to myself: it now does run the test suite to completion:
>
> Ran 1425 tests in 384.689s
>
> FAILED (failures=222, errors=539)
>
> It can now convert and start the test suite, however, this doesn't
> produce any results, yet.
Following up to myself: it now does run the test suite to completion:
Ran 1425 tests in 384.689s
FAILED (failures=222, errors=539)
If you are curious what the failures and errors are, just run it fo
On Sunday 07 February 2010 10:45:29 Florian Apolloner wrote:
> Hi,
>
> first of all, I agree with Luke that it's hard to fix this if it's
> possible at all [1]. The only real problem I have with this ticket
> beeing closed is the backwards compatibility issue. Decorating
> admin views worked just
Just to steer the discussion back to practical matters:
1. This thread isn't about what stuff we want to do in the admin, or
whether grappelli is great. How to improve the admin or any other
aspect of Django which has design issues is a great discussion! It
just isn't *this* discussion.
2. *This*
Yep, I think we are mostly in agreement, we just have different areas
of personal interest and passion within the "design for django"
realm. :)
On Feb 7, 10:41 am, jsmullyan wrote:
> Upon re-reading your last post more carefully, Jeff, I realize that
> you actually more-or-less agree with at leas
> You are indeed, but the admin UI is still the center of it. (As for
> the django website -- I would argue that's really a different matter
> than developing django itself, and seems to deserve a separate
> discussion.)
Well, our current "design czar" (Wilson) was tasked with the
responsibility
This post is flawed because it artificially separates accessibility
from design, and it treats design as if it only has to do with
aesthetics. Design encapsulates accessibility, and and good
interaction designer will put accessibility high on his/her list of
priorities.
On Feb 7, 10:34 am, h3 wro
> Grappelli has done a great job of skinning the admin interface.
It depends which version you check. We are currently in the decision
of breaking appart from the Django admin and
create a standalone app or stick with it[0]..
We have started to be a lot more than a "skin". We are currently in
the
Upon re-reading your last post more carefully, Jeff, I realize that
you actually more-or-less agree with at least portions of what I
said. Sorry to kick up dust unnecessarily! My main concern is that
the "look" of the current admin is too hard to modify with the current
implementation, and I thin
On Feb 7, 12:52 pm, "j...@jeffcroft.com" wrote:
> Also, I'll say again: this discussion shouldn't really just be able
> the admin interface -- it should be more broad, talking about who can
> lead *anything* interaction design-related in the Django community.
>
> > If the admin application were de
> unless I've missed something whoever gets the position, would definitionally
> get it before they've done anything!
I strongly suggest you should take a look at grappelli ... some people
*are* doing things ;)
> In conclusion, there is 0 reason design needs to be treated different from a
> pro
> I seem to have inadvertently kicked over an ants nest here.
>
> I promise that the competition proposal wasn't intended to offend or
> devalue the efforts of anyone in the design community. If I have done
> so, I apologize. Please believe that what I wrote as an honest attempt
> to find a way to
Several responses:
> First off, there are designers who have contributed great amounts of
> stuff to the Django community. Nathan Borror has his Basic Apps (which
> interestingly is a designer contributing code, because that's what he
> can contribute easily).
Exactly. Christian Metts comes to mi
There may be good reasons for a Design Czar long term, or at least a
User Experience Czar, in guiding the development of the admin
application. But it seems to me that this is too large a solution for
the current bottleneck, and perhaps more modest solutions should be
considered as well.
If the a
On Sat, Feb 6, 2010 at 8:32 PM, Armin Ronacher
wrote:
> I would like to propose a different solution: do an instance check
> against a django TemplateSyntaxError (or any other template exception
> that has these .source attributes). That should be easy to accomplish
> and the debug system already
Django needs someone who will start and get the admin job done, but
some decisions must be made before by the community. For example:
whether to use CSS reset or not? If, which one? While refactoring some
admin pieces we reduced number of CSS files to one. Would you accept
such solution? Why it's b
On Sun, Feb 7, 2010 at 9:11 AM, j...@jeffcroft.com wrote:
>> I'm opposed to this. Firstly, unless I've missed something whoever
> gets the position, would definitionally get it before they've done
> anything!
>
> To respond to just this bit: you're right, but the reason whoever gets
> this positi
let me just add one (more) point to this discussion (I´ve already
stressed this issue at the other thread).
IMO, when talking about the admin-interface, we´re talking about
different "construction zones":
– the whole structure and user experience with the admin-interface as
mentioned by jeff and o
Hi,
first of all, I agree with Luke that it's hard to fix this if it's
possible at all [1]. The only real problem I have with this ticket
beeing closed is the backwards compatibility issue. Decorating admin
views worked just fine in 1.1 and r11660 broke it (At least I hope it
worked in 1.1, but as
Jeff, I gotta agree that if the design of Djange was developed by a
pro-person it must be redesigned by someone who'd have done at least
the same level.
Apparently, I'm not talking about redesigning. Even not about changing
colors and images - they perfectly fit for a base instance of the
framewor
Dammit. I wrote that last night, it didn't post, and I rewrote it
today. And now both show up. Great. Sorry about that.
On Feb 5, 2:40 pm, "j...@jeffcroft.com" wrote:
> As one of many talented and respected designers in the Django
> community, and also as a good friend of Wilson Miner, I'd like t
33 matches
Mail list logo
