{"action":"opened","issue":{"url":"https://api.github.com/repos/FabMo/FabMo-Engine/issues/192","labels_url":"https://api.github.com/repos/FabMo/FabMo-Engine/issues/192/labels{/name}","comments_url":"https://api.github.com/repos/FabMo/FabMo-Engine/issues/192/comments","events_url":"https://api.github.com/repos/FabMo/FabMo-Engine/issues/192/events","html_url":"https://github.com/FabMo/FabMo-Engine/issues/192","id":108943845,"number":192,"title":"\"Up Next\"","user":{"login":"ryansturmer","id":1383181,"avatar_url":"https://avatars.githubusercontent.com/u/1383181?v=3","gravatar_id":"","url":"https://api.github.com/users/ryansturmer","html_url":"https://github.com/ryansturmer","followers_url":"https://api.github.com/users/ryansturmer/followers","following_url":"https://api.github.com/users/ryansturmer/following{/other_user}","gists_url":"https://api.github.com/users/ryansturmer/gists{/gist_id}","starred_url":"https://api.github.com/users/ryansturmer/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/ryansturmer/subscriptions","organizations_url":"https://api.github.com/users/ryansturmer/orgs","repos_url":"https://api.github.com/users/ryansturmer/repos","events_url":"https://api.github.com/users/ryansturmer/events{/privacy}","received_events_url":"https://api.github.com/users/ryansturmer/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":0,"created_at":"2015-09-29T19:38:50Z","updated_at":"2015-09-29T19:38:50Z","closed_at":null,"body":"The job manager's \"pending\" display could use a revamp, in the form of something that makes it easier to do what you nearly always want to do when you enter the job  manager:  Run the next job.\r\n\r\nWhen you open the job manager, it's for one of two reasons:\r\n\r\n1. You were ejected to the job manager by an app whose purpose is to get you to run the new job that was just submitted\r\n2.  You've come to the job manager on your own, either back from making some tool adjustment before doing a cut, or to go fish around in the history for some reason.\r\n\r\nIn the first case (and first part of the second case) what you almost always want to do is interact with the next-to-be-run job in the job queue.  Most of the time, you want to run it, although almost as often you want to preview it, and very infrequently you may wish to download its contents, cancel it, etc.\r\n\r\nI propose something like the attached as a new interface for the pending display:\r\n\r\n![20150929_152141](https://cloud.githubusercontent.com/assets/1383181/10175947/e250bc08-66bf-11e5-860f-4ab1ecdd5f15.jpg)\r\n\r\nIt takes the latest job, and puts it front and center for the user to interact with.  Below it is the rest of the queue, or nothing if there's nothing in the queue (the pending table should be hidden if it's empty) - if there's nothing up next or pending, the history should be displayed straight away.  No need to land on an empty page if there's nothing to see.\r\n\r\nThis layout can look good on mobile or on desktop, as it is scrolling-first, and the idea of displaying the next job as a \"card\" might allow us to do something with gestures down the line (you could swipe left, tinder-style to dismiss a job, or swipe right to initiate it)\r\n\r\nIt's almost not even worth displaying the \"pending\" jobs most of the time - as I feel you're most usually really only interested in the very next one.  This isn't true though in the case of \"compound jobs\" where you've got multiple jobs queued up to do multiple parts, such as with handibot \"cookie-cuttering\"\r\n\r\n"}}