Righton. I haven't used it too intensely for filtering and sorting but
I do have some other thoughts about that.
1) Would it be better to come up with a non-changelist changelist for
raw_id_fields. I find myself avoiding raw_id_fields because I don't
necessarily want to register the object in ques
On 4 Ott, 04:09, Chuck Harmston wrote:
> An Ajax admin solution (of the autocomplete sort, which I presume is what
> you're proposing) does not have the same use case for raw_id_fields. It's
> based on the assumption that the user knows the value of the unicode
> representation of the object. It d
We're playing semantic leapfrog here, but I don't see the proposed Ajax
solution as "searching", I see it as "autocompleting"; people won't use it
to discover content, they will use it as a shortcut for accessing content
that they are familiar with. As I said, much of the utility of the
raw_id_fiel
With the AJAX field implementation on the table you're free to
represent the objects however you want. Yeah, there's a few things
left out but did you really say 'no searching'?
-Steve
On Oct 3, 10:09 pm, Chuck Harmston wrote:
> it's based on the assumption that the user knows the value of the u
An Ajax admin solution (of the autocomplete sort, which I presume is what
you're proposing) does not have the same use case for raw_id_fields. It's
based on the assumption that the user knows the value of the unicode
representation of the object. It does not allow for discovery like the
raw_id_fiel
Does anyone besides me think that an AJAX field admin solution
effectively deprecates raw_id_fields?
I'm interested in seeing a ticket like #14370 go forward if only to
close a slew of dusty old tickets about raw_id_fields.
-Steve
On Oct 3, 5:58 am, Marcob wrote:
> Well, M2M and raw_id_fields a
On Sun, Oct 3, 2010 at 5:58 PM, Marcob wrote:
> On 30 Set, 07:34, "subs...@gmail.com" wrote:
>> Hello all,
>> I was browsing the tickets and saw a few of them nagging about some
>> restrictions to raw_id_fields.
>
> Since my first Django installation, a couple of years ago, I fixed and
> used thi
On 30 Set, 07:34, "subs...@gmail.com" wrote:
> Hello all,
> I was browsing the tickets and saw a few of them nagging about some
> restrictions to raw_id_fields.
Since my first Django installation, a couple of years ago, I fixed and
used this patch:
http://code.djangoproject.com/ticket/7028
I see
Edit. Edit.
"I just don't think making an absolute answer to that discussion a
contingency to this called-for feature /is a good idea/".
There we go.
On Oct 1, 11:19 am, "subs...@gmail.com" wrote:
> Please don't think I'm trying to hinder discussion. I just don't think
> making an absolute answ
I know I'm not a core dev but I do have two cents.
I'm not really in favor of overthinking this too much--I think a
satisfactory replacement for raw_id_fields is good enough (adequately
encompasses all the features). I know there are a lot of mature
projects out there when it comes to AjaxFields a
Hi everyone,
Anyway, I'd like to see notes from core devs regarding adding such
feature to Admin interface (so please don't say -1 if you think it's
just not mature enough!).
Or maybe all interested parties should work on some kind of
django-admin-extensions instead of improving admin itself.
Ac
Hi Tyrion,
Multicomplete have no add item button with popup.
This is usually the hardest thing to implement with such control,
because it's rendered *after* the control.
Was it that hard to subclass widgets as Admin*AutocompleteWidget and
add required css media from jquery.ui to them?
Lots of ot
I've tried implementing Autocomplete for the admin using jQuery (new)
Autocomplete,
here's the code: http://bitbucket.org/tyrion/django
and here's a live demo (without css for the autocomplete, so it looks
kinda ugly): http://djangoac.tyrion.mx/admin/ login with test/test.
Let me know what you thi
And then it was so:
http://code.djangoproject.com/ticket/14370
On Sep 30, 3:54 pm, "subs...@gmail.com" wrote:
> Yeah, I think your right. raw_id_fields is a neat idea if you really
> are reluctant to use AJAX. If introducing AJAX into admin is fine,
> dumping these fields altogether seems the be
Yeah, I think your right. raw_id_fields is a neat idea if you really
are reluctant to use AJAX. If introducing AJAX into admin is fine,
dumping these fields altogether seems the best approach.
As for the options given, I've only used ajax-selects. I think its
implementation is rather cumbersome in
On Thu, Sep 30, 2010 at 10:27 PM, subs...@gmail.com wrote:
> At that point its not really raw_id_fields, is it? =)
After all, what's the purpose of these fields?
--
Best regards, Yuri V. Baburov, ICQ# 99934676, Skype: yuri.baburov,
MSN: bu...@live.com
--
You received this message because you
At that point its not really raw_id_fields, is it? =)
-Steve
On Sep 30, 3:07 am, "burc...@gmail.com" wrote:
> Hi Subsume,
>
> why not just replace them with some proper implementation of ajax completion ?
>
> http://djangopackages.com/grids/g/auto-complete/
>
> On Thu, Sep 30, 2010 at 12:34 PM,
Hi Subsume,
why not just replace them with some proper implementation of ajax completion ?
http://djangopackages.com/grids/g/auto-complete/
On Thu, Sep 30, 2010 at 12:34 PM, subs...@gmail.com wrote:
> Hello all,
>
> I was browsing the tickets and saw a few of them nagging about some
> restricti
18 matches
Mail list logo
