Closed GoogleCodeExporter closed 9 years ago
yes. there is currently some refactoring.
reordering:
we tried to make reordering of edit-inlines better. from my point of view, the
current solution is crap. unfortunately, this ticket
(http://code.djangoproject.com/ticket/8165) prevents us from doing so. I´ve
tried
different solutions for the last 2 or 3 weeks, but without this ticket being
closed,
reordering won´t work (the way I´d like it to).
generics, related:
this works. I just need to update the trunk.
css:
refactoring css/html is the last thing we´re going to do.
conclusion:
we are currently not sure what to do. reordering edit-inlines is a major issue
for us
and there doesn´t seem to be a nice solution. we´re thinking about putting
grappelli
on hold for a while.
right now, my advice is to NOT use grappelli.
thanks,
patrick
Original comment by sehmaschine
on 7 Apr 2009 at 6:00
I reverted Grappelli to revision 226 and it seems to work much better with
Django 1.0.2
This is an awesome project by the way, thanks for your work.
Original comment by michaelj...@gmail.com
on 7 Apr 2009 at 6:14
with the updates from today, some of your points should be fixed.
please open a new ticket (or several tickets) with more specific errors (if they
still exist).
Original comment by sehmaschine
on 9 Apr 2009 at 11:49
the error with generic relations you mentioned should be fixed by now ...
Original comment by sehmaschine
on 9 Apr 2009 at 1:59
just a note: from r264 on, generic relations should work.
Original comment by sehmaschine
on 9 Apr 2009 at 2:53
Original issue reported on code.google.com by
michaelj...@gmail.com
on 7 Apr 2009 at 2:21