Ticket #46 (closed task)

Opened 5 years ago

Last modified 5 years ago

Implement Tasklist competion action

Reported by: Joel Owned by:
Priority: trivial Milestone: Eraser 6.0
Component: Version:
Keywords: Cc:
Processor Architecture: Blocked By:
Blocking: Operating System:

Description

Much like how v5 does it now, perhaps with a few refinements?

Blocking

IdSummaryMilestone
#46└ Implement Tasklist competion actionEraser 6.0

Blocked by

IdSummaryMilestone
#46└ Implement Tasklist competion actionEraser 6.0

Change History

comment:1 Changed 5 years ago by Joel

My belief is that this is difficult to implement, and cranky at best.

The reason is this: In v5, tasks were executed synchronously. The completion of a task had a distinct meaning. In v6, tasks are executed asynchronously, therefore the completion of one task may be immediately followed by an execution of the next task. What is defined as "when task is finished?"

Bringing the argument further, what will happen in future when Eraser is implemented as a Service? The program will not be able to schedule system shutdowns, etc since the service is not running under any user.

Opinions?

comment:2 Changed 5 years ago by Joel

  • Priority changed from major to trivial

comment:3 Changed 5 years ago by Joel

  • Status changed from new to pending

comment:4 Changed 5 years ago by trac-robot

  • Status changed from pending to closed

This ticket was closed automatically by the system. It was previously set to a Pending status and hasn't been updated within 14 days.

Note: See TracTickets for help on using tickets.