[p2pu-dev] A long way to go for sorting tasks

[Brian Brennan]

I agree on dragging & dropping.

This is certainly not an issue for us now, but keep in mind that (unless
I'm missing something completely obvious) you can't drag & drop on
phones/tablets. So when someone goes to edit their tasks on their
Blackberry Playbook, they are gonna be disappointed (mostly because they
are using a Blackberry Playbook).

I still think moving forward with drag/drop is a good idea and we can cross
(or burn, whatever) that other bridge when we get there.

Brian


On Wed, Feb 1, 2012 at 4:27 PM, Paul Bakulich <paulbakulich at gmail.com>wrote:

> Isn't it possible to do both? Drag & drop and some javascript function to
> change the order with arrows (without page-refresh) and store it for django?
>
> I think much of the site needs more jQuery / Mootools UX.
>
> Although I'm not a awesome jQuery ninja, I'd love to help with this!
>
> --------
> Paul Bakulich
> irc: codepal
>
>
> On 2 February 2012 08:22, Alison Cole <alison at p2pu.org> wrote:
>
>> +1 drag & drop
>> Reordering is a slow process. I have same sadness as Maria.
>>
>> On Wed, Feb 1, 2012 at 6:15 AM, zuzel.vp <zuzel.vp at gmail.com> wrote:
>>
>>> drag and drop is the best way to go to solve this issue:
>>>
>>> http://p2pu.lighthouseapp.com/projects/71002/tickets/97-drag-and-drop-reordering-of-tasks
>>>
>>> On Wed, Feb 1, 2012 at 9:07 AM, Jessy Kate Schingler
>>> <jessy at jessykate.com> wrote:
>>> > +1 to the request and love the drag solution. This was an issue when I
>>> did
>>> > the randomized algorithms course too.
>>> >
>>> > On Feb 1, 2012 9:02 AM, "Jos Flores" <josmasflores at gmail.com> wrote:
>>> >>
>>> >> instead of 'top' and 'bottom' what about having the tasks being
>>> >> draggable so you can put them wherever you want? just a thought!
>>> >>
>>> >> cheers,
>>> >> José
>>> >>
>>> >> On 1 February 2012 11:42, Maria Droujkova <droujkova at gmail.com>
>>> wrote:
>>> >> > Is there any chance to have a "bring to top" and "send to bottom"
>>> >> > buttons in
>>> >> > the task order list? Failing that, can we have "newest tasks at the
>>> top"
>>> >> > as
>>> >> > a default? I need the current tasks to be at the top of the list,
>>> and
>>> >> > they
>>> >> > appear at the bottom. We are in Week 3 of the course and already
>>> it's a
>>> >> > pretty long way to sort (attached picture). What will happen by
>>> Week 15,
>>> >> > with 3-4 tasks per week, I hate to think...
>>> >> >
>>> >> > I recently had to do it with a slower computer and slower connection
>>> >> > (giving
>>> >> > a teacher workshop at Bermuda) and it was harsh, since the page
>>> fully
>>> >> > reloads with each "nudge up/down" action on tasks.
>>> >> >
>>> >> > Cheers,
>>> >> > Maria Droujkova
>>> >> > 919-388-1721
>>> >> >
>>> >> > Make math your own, to make your own math
>>> >> >
>>> >> >
>>> >> >
>>> >> >
>>> >> > _______________________________________________
>>> >> > p2pu-dev mailing list
>>> >> > p2pu-dev at lists.p2pu.org
>>> >> > http://lists.p2pu.org/mailman/listinfo/p2pu-dev
>>> >> >
>>> >> _______________________________________________
>>> >> p2pu-dev mailing list
>>> >> p2pu-dev at lists.p2pu.org
>>> >> http://lists.p2pu.org/mailman/listinfo/p2pu-dev
>>> >
>>> >
>>> > _______________________________________________
>>> > p2pu-dev mailing list
>>> > p2pu-dev at lists.p2pu.org
>>> > http://lists.p2pu.org/mailman/listinfo/p2pu-dev
>>> >
>>> _______________________________________________
>>> p2pu-dev mailing list
>>> p2pu-dev at lists.p2pu.org
>>> http://lists.p2pu.org/mailman/listinfo/p2pu-dev
>>>
>>
>>
>>
>> --
>>
>> Alison
>>
>>
>> _______________________________________________
>> p2pu-dev mailing list
>> p2pu-dev at lists.p2pu.org
>> http://lists.p2pu.org/mailman/listinfo/p2pu-dev
>>
>
> _______________________________________________
> p2pu-dev mailing list
> p2pu-dev at lists.p2pu.org
> http://lists.p2pu.org/mailman/listinfo/p2pu-dev
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.p2pu.org/pipermail/p2pu-dev/attachments/20120201/96836b84/attachment-0001.html>