{"issue":{"pull_request":{"diff_url":null,"html_url":null,"patch_url":null},"state":"open","user":{"avatar_url":"https://secure.gravatar.com/avatar/6fd171430d7b32e8e296228e3e5a64f8?d=https://a248.e.akamai.net/assets.github.com%2Fimages%2Fgravatars%2Fgravatar-140.png","gravatar_id":"6fd171430d7b32e8e296228e3e5a64f8","url":"https://api.github.com/users/nicholas-jordan","login":"nicholas-jordan","id":1149743},"milestone":null,"assignee":null,"updated_at":"2011-10-28T14:08:07Z","labels":[],"comments":0,"closed_at":null,"url":"https://api.github.com/repos/nicholas-jordan/GreenDroid/issues/3","body":"to achieve effective forward progress on correcting \"... current version is so laggy, it is almost unusable on some devices ...\" seen on Cyril's blog an implementation of directed acyclic graph / spanning trees as a code-concept has to be in place as a \"driver-engine\" behind UI elements in code ~ theory on  directed acyclic graph / spanning trees is well developed - what needs to be done is examine how powerful we want GD to be as a UI driver/engine = the code can be made to run efficiently with reliable recovery of complex user-state even across complete system reset() on the physical device & that is not normally achieved in UI Design ..... to provide the ability for cyrilmottier/GreenDroid ~ stubbs can be placed in the codebase + these can be used if someone wants to achieve the performance build out the stubb ","html_url":"https://github.com/nicholas-jordan/GreenDroid/issues/3","title":"directed acyclic graph implementation","number":3,"id":2078865,"created_at":"2011-10-28T14:08:07Z"},"action":"opened"}