I'm not so sure "novalidate" is a viable solution.
If you have a DecimalField and you enter "xxx" this is what happens ...
a) With "novalidate" added to the form:
The value is being removed from the field and the form is being saved
(tested with Firefox and Safari).
b) Without "novalidate":
I agree with Idan. We mainly did Grappelli because of the look & feel (and
then added some functionality like autocompletes).
However, it just doesn´t make sense to simply "beautify" the existing
admin-interface. Rethinking the functionality, adding flexibility, being
able to customize ...
IMO this issue is not related to grappelli whatsoever.
the question is, if the app-index makes sense to an editor? and I think
that this not the case – because an editor doesn´t need know what an "app"
(within a django-project) is.
my experience is that editors are extremely confused about the
before adding a new ticket I just wanted to discuss this issue:
when using template-caching it´s sometimes useful to have a variable for the
"fragement name".
e.g., I want to prefix all caching-variables with "myapp_userid", because I
need to delete alle user-related caching-variables at some
On 12 Dez., 13:29, Russell Keith-Magee <russ...@keith-magee.com>
wrote:
> On Sun, Dec 12, 2010 at 6:04 PM, patrickk <patr...@vonautomatisch.at> wrote:
>
> > On Dec 12, 12:50 am, Russell Keith-Magee <russ...@keith-magee.com>
> > wrote:
> >> On
On Dec 12, 12:50 am, Russell Keith-Magee <russ...@keith-magee.com>
wrote:
> On Sat, Dec 11, 2010 at 11:28 PM, patrickk <patr...@vonautomatisch.at> wrote:
> > hi,
>
> > the plan is to allow for reodering inlines within the admin-interface
> > (using drag/drop)
hi,
the plan is to allow for reodering inlines within the admin-interface
(using drag/drop). before starting to work on patches, I´d like to
discuss some issues ...
features:
1. drag/drop (with jQuery-UI sortables).
2. in case of errors (somewhere within the form), the position of
inline-rows
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
jannis (leidel) asked me to join this thread in order to add some
comments.
we´ve been doing grappelli (http://code.google.com/p/django-grappelli/
wiki/screenshots) for a while now. grappelli initially should be a
"skin" for the admin-interface. while working on it, we´ve had issues
skinning the
@jannis: no, it isn´t. I thinkg you are able to _add_ js to your admin
views, but you´re not able to _remove_ javascripts. there´s still way
too much hardcoded stuff with the admin-interface (IMO).
I hope that including jquery with the admin-interface is not a big
mistake in the long run.
AdminSite), just in case someone
wants to do something similar without grappelli:
http://code.google.com/p/django-grappelli/source/browse/branches/grappelli_2/sites.py
thanks for all the feedback/help,
patrick
On 17 Sep., 12:55, patrickk <patr...@vonautomatisch.at> wrote:
> I´ve opened
define a group, all apps are listed as is.
the file admin.py show how the apps can be defined for an admin-site.
thanks,
patrick
On 6 Sep., 11:38, patrickk <patr...@vonautomatisch.at> wrote:
> my thoughts:
> 1. defining groups within admin.py of each app makes reordering groups
> c
my thoughts:
1. defining groups within admin.py of each app makes reordering groups
complicated.
2. to assign an app to a group, I have to register that app with a
group - if I want (for example) to assign django.contrib.auth to the
group "User Management", I have to change that app (which breaks
On 5 Sep., 06:02, Russell Keith-Magee wrote:
> On Sat, Sep 5, 2009 at 3:32 AM, James Bennett wrote:
>
> > On Fri, Sep 4, 2009 at 2:21 PM, andybak wrote:
> >> 1. I think worrying about projects vs. apps is a red-herring. We are
%}
{% if model.perms.change %}
{% trans 'Change' %}
{% else %}
{% endif %}
{% endfor %}
{% endfor %}
{% endfor %}
On 4 Sep., 15:52, patrickk <patr...@vonautomatisch.at> wrote:
On 4 Sep., 15:30, Russell Keith-Magee <freakboy3...@gmail.com> wrote:
> On Fri, Sep 4, 2009 at 8:37 PM, patrickk<patr...@vonautomatisch.at> wrote:
>
> > fair enough.
>
> > I don´t have a problem with just seperating INSTALLED_APPS from
> > ADMIN_APPS w
, please let me know.
thanks,
patrick
On 4 Sep., 14:23, Russell Keith-Magee <freakboy3...@gmail.com> wrote:
> On Fri, Sep 4, 2009 at 7:19 PM, patrickk<patr...@vonautomatisch.at> wrote:
>
> > thanks for the reply.
>
> > On 4 Sep., 13:02, Luke Plant <l.plant...@
thanks for the reply.
On 4 Sep., 13:02, Luke Plant <l.plant...@cantab.net> wrote:
> On Friday 04 September 2009 10:00:37 patrickk wrote:
>
> > e.g, when I´m using djangos auth-app and I´m extending the user-model
> > with a user-profile, I´m having "auth" (wi
hi everyone,
I just wanted to outline a basic idea in order to improve (at least
from my point of view) the index-page of the admin-interface. I don´t
have any code to share (so far), so I´m basically explaining my idea -
if people agree that this is useful, I´m trying to submit a patch.
here´s
g an
error. this obviously shouldn´t be the case ...
thanks,
patrick
On 7 Jul., 13:12, patrickk <patr...@vonautomatisch.at> wrote:
> more feedback to your inline-solution:
> ### if you use a draghandler for stacked-inlines, there should be a
> draghandler for tabular-inlines as well (inst
s customization so much easier.
and it´s clean and coherent.
### at the change-list, the save-button (if you have forms on the
list) is within the paginator. shouldn´t be there, from my point of
view.
regards,
patrick
On 7 Jul., 11:16, Zain Memon <z...@inzain.net> wrote:
> Hey Patrick --
>
s to actually see what´s in there ...
one more thing: it currently says "Add a choice" - I´m not sure if
this should be "Add a Choice" in order to be translated correctly.
thanks,
patrick
On 7 Jul., 08:21, Zain Memon <z...@inzain.net> wrote:
> Thanks for
@aniybak: yes, we´re doing usability-tests very frequently. that´s one
reason why we came up with django-grappelli ...
btw, I absolutely agree with the "cancel-button".
about the delete-button: IMHO, one needs the possibility to undo the
deletion - that´s why it´s almost impossible to let items
very nice ...
some things I´ve came across:
- the ordering is not preserved in case of errors.
- with stacked inlines, an error should be indicated on the left-hand
side (with comment-selectors). otherwise one has to click through all
selectors.
- with stacked inlines, there´s something wrong
erve reordering on errors. That's my next task :)
> Zain
>
> On Fri, Jun 12, 2009 at 1:34 AM, patrickk <patr...@vonautomatisch.at> wrote:
>
> > if you like to implement reordering inlines (as outlined in wilsons
> > graphic for stacked inlines), you might wanna consider
if you like to implement reordering inlines (as outlined in wilsons
graphic for stacked inlines), you might wanna consider this:
in case of an error, the reordering should be preserved (of course).
as far as I know, this is currently not possible with the way django
handles formsets.
it´d be
:
> On Wed, Oct 22, 2008 at 10:06 AM, patrickk <[EMAIL PROTECTED]> wrote:
> > IMHO, when using "order_with_respect_to", one should be able to order
> > the inlines (stacked & tabular).
>
> Yup, this has been on the todo list for quite some time. We even
> d
this to be solved
or if this behaviour is intentional (for whatever reason).
thanks,
patrick
On 22 Okt., 18:06, patrickk <[EMAIL PROTECTED]> wrote:
> IMHO, when using "order_with_respect_to", one should be able to order
> the inlines (stacked & tabular).
>
> what´s
IMHO, when using "order_with_respect_to", one should be able to order
the inlines (stacked & tabular).
what´s necessary:
1. can_order should be set to true when using "order_with_respect_to".
e.g., if you currently subclass a formset and use can_order=true, there
´s an error in the
I found this patch (http://code.djangoproject.com/ticket/3096), but it
´s not working.
is anybody working on this issue?
thanks,
patrick
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To
ode formset, till I figured out it
´s not possible.
patrick.
On Aug 19, 9:22 pm, "Brian Rosner" <[EMAIL PROTECTED]> wrote:
> On Tue, Aug 19, 2008 at 12:10 PM, patrickk <[EMAIL PROTECTED]> wrote:
>
> > any reason, why it´s currently impossible to use "initial&
any reason, why it´s currently impossible to use "initial" with
inlineformset_factory. is it planned to integreate this feature?
thanks,
patrick
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django developers"
this is a proposal in order to add something like "order_by" to m2m-
fields.
with using an m2m-field, there´s no possibility to enter (or output)
something with a different order than the one provided by the related
model. with using a foreign key & edit_inline, it IS possible.
so, one could say
just 2 small things you may want to implement:
1. the opportunity to translate the apps - useful for the admin
index-page.
2. for showing the permissions, use "app | model | Can ..." insted of
"model | Can ..." - this is especially useful if one has the same
model-names within different apps.
I´ve just been looking at the admin-generator in symfony and it has
the possibility to add multiple search-filters.
we had this problems recently:
1. it´s currently not clear which columns are searched when using the
search-field in the admin-list. that´s sometimes very strange,
especially
Am 16.11.2006 um 11:30 schrieb Aidas Bendoraitis:
>
> Not a bad change, but much more important, in my opinion, would be to
> have an ability to set the fields of inline edited models according
> the formatting set in fields list/tuple; with all the features as
> collapsible groups of fields,
here are some issues concerning styles/layout and a couple of general
issues. some of the mentioned problems might be more important than
others - I just wanted to give a very personal list of what I´ve
noticed:
HTML/CSS:
### booleanfields are displayed different than any other fields -
:
>
> Congratulations about setting up the FileBrowser under svn! By the
> way, if the FileBrowser project is open to public, what is the URL for
> the latest and greatest revision?
>
> Regards,
> Aidas Bendoraitis
>
>
>
> On 11/5/06, patrickk <[EMAIL PROTECTED]> wrote:
>
browser/templates/filebrowser/...
>
> G
>
> On 11/5/06, patrickk <[EMAIL PROTECTED]> wrote:
>>
>> I finally made it to setup trac/svn for our filebrowser (http://
>> www.vonautomatisch.at/django/filebrowser/)
>>
>> my question is: where should I put the med
I finally made it to setup trac/svn for our filebrowser (http://
www.vonautomatisch.at/django/filebrowser/)
my question is: where should I put the media- and template-stuff?
if I use a subdirectory for media/templates, one has to copy this
directory after a svn checkout. I´m not sure if
> So far as I can tell, our biggest long-term management problem right
> now is not one of scaring developers away, it's one of keeping track
> of all the people who want to get involved and all the things they
> want to do. You haven't yet provided an example to the contrary.
well, then I do.
when doing a search in the related-object window in the admin-
interface and using the link "xxx total" after that search, the query
is missing.
because "pop=1" is in the query, the header is shown ...
using 0.95
thanks,
patrick
(don´t know if it is appropriate to post here, but since my
since my comment is rejected by Akismet, I´m posting it here ...
in filterspecs, line 40
{{{
t.append(_('By %s:\n\n') % self.title())
}}}
in filter.html, line 2
{{{
{% blocktrans with title|escape as filter_title %} By
{{ filter_title }} {% endblocktrans %}
}}}
in django.po, line 354:
{{{
sure I could do that.
not DRY though.
anyway, thanks for the hint.
patrick
Am 11.09.2006 um 17:21 schrieb Rob Hudson:
>
> patrickk wrote:
>> 2. when using a custom manipulator for letting the user change his
>> personal values (first name, last name, address, zip_co
10.09.2006 um 22:38 schrieb James Bennett:
>
> On 9/10/06, patrickk <[EMAIL PROTECTED]> wrote:
>> 1. why are these personal values (first name, last name, email) there
>> in the first place? did I miss something?
>
> The User model is not meant to be an exact match
while playing with the authentication system, I don´t really get the
pre-defined model.
we have first_name, last_name and email in there - these values are
optional and we don´t need them for authentication. when I extend the
user-model with a user-profile I´m having (profile) values in 2
just a comment because noone else is answering:
- i can think of using that functionality
- AND would be important for me
- don´t know if a ticket is appropriate (see: http://
code.djangoproject.com/changeset/2830)
patrick
Am 11.05.2006 um 00:23 schrieb Marc Boeren:
>
> Hi,
>
> I've hacked
my apologies for cross-posting, but the thread started in the user-
group ...
is anyone interested in having a FileBrowseField?
it could look like this:
http://www.vonautomatisch.at/django/ftp/get_image.jpg
when clicking on the search-image near the image-field, the file-
browser should open
yes, i probably _could_ install MR (so far, i´ve been using the one-
click-installer with razorlogix).
but you are right, there shouldn´t be a problem.
in the razorlogix help desk it says that using the development server
is not possible.
patrick
Am 01.04.2006 um 15:03 schrieb tonemcd:
>
i´m using razorlogix.
# easy one-click django-install
# it seems that you are limited to the django-version they provide -
so it´s currently not possible to install magic-removal (i didn´t try
it, btw)
# fast and stable (e.g. compared with dreamhost)
# BUT: they´re still having the problem
50 matches
Mail list logo