Closed GoogleCodeExporter closed 9 years ago
First I am not convinced that drag-and-drop is really that user friendly,
especially
when the page list is very big (drag-drop-scroll is painful). Is it a real
requests
from a client?
Secondly it's I find pretty dangerous because it kind of facilitate an
operation that
break the URLs. When your pages start to be linked by other websites, you don't
want
them to move around, ever.
For these reasons I have no plan to implement that in a near future. If you
want to
do it yourself I recommend to do it with a small draggable surface so
accidental drag
and drop are difficult to do.
What do you think?
Original comment by batiste....@gmail.com
on 9 Feb 2010 at 2:15
While some projects with a large volume of pages might truly be less usable, I
think
the majority of sites won't have an issue with it.
The breaking of URLs is in itself a larger (and unrelated) problem to a
drag-and-drop
interface, as one can still reorder pages the way the interface is now. There
should
probably be a setting to respect original URLs, but it probably needs more
thought.
A small icon (much like the re-order icon in iPhone's interface) would be
useful, as
well as a button to specifically enable re-ordering to avoid accidental
reordering.
Original comment by intellin...@gmail.com
on 9 Feb 2010 at 7:57
Here is a basic implementation:
http://github.com/batiste/django-page-
cms/commit/57720605cff5eb3f50baf49e5a13a8534801dc61
When the row is dropped somewhere the row is added as the child as the first
left
brother.
Original comment by batiste....@gmail.com
on 10 Feb 2010 at 2:36
[deleted comment]
Awesome - you rock. Giving it a shot now.
Thanks.
Original comment by intellin...@gmail.com
on 10 Feb 2010 at 2:42
Hmm - can't seem to get it to work on my first try - any new settings or
scripts to
load in for it?
Original comment by intellin...@gmail.com
on 10 Feb 2010 at 3:01
$ git pull
$ ./manage.py build_media pages
Does it help? The drag and drop handle zone is the same place than the link to
move
the pages.
Original comment by batiste....@gmail.com
on 10 Feb 2010 at 3:38
Original comment by batiste....@gmail.com
on 6 May 2010 at 7:22
Original issue reported on code.google.com by
intellin...@gmail.com
on 3 Feb 2010 at 7:44