{"action":"opened","issue":{"url":"https://api.github.com/repos/Aeva/m.grl/issues/101","labels_url":"https://api.github.com/repos/Aeva/m.grl/issues/101/labels{/name}","comments_url":"https://api.github.com/repos/Aeva/m.grl/issues/101/comments","events_url":"https://api.github.com/repos/Aeva/m.grl/issues/101/events","html_url":"https://github.com/Aeva/m.grl/issues/101","id":77375892,"number":101,"title":"Composition RenderNode prefabs","user":{"login":"Aeva","id":768449,"avatar_url":"https://avatars.githubusercontent.com/u/768449?v=3","gravatar_id":"","url":"https://api.github.com/users/Aeva","html_url":"https://github.com/Aeva","followers_url":"https://api.github.com/users/Aeva/followers","following_url":"https://api.github.com/users/Aeva/following{/other_user}","gists_url":"https://api.github.com/users/Aeva/gists{/gist_id}","starred_url":"https://api.github.com/users/Aeva/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/Aeva/subscriptions","organizations_url":"https://api.github.com/users/Aeva/orgs","repos_url":"https://api.github.com/users/Aeva/repos","events_url":"https://api.github.com/users/Aeva/events{/privacy}","received_events_url":"https://api.github.com/users/Aeva/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/Aeva/m.grl/labels/enhancement","name":"enhancement","color":"84b6eb"}],"state":"open","locked":false,"assignee":null,"milestone":{"url":"https://api.github.com/repos/Aeva/m.grl/milestones/1","html_url":"https://github.com/Aeva/m.grl/milestones/Milestone%20One","labels_url":"https://api.github.com/repos/Aeva/m.grl/milestones/1/labels","id":829516,"number":1,"title":"Milestone One","description":"This milestone is complete when the jta model format's file format is stable, and there are enough core features to make this project useful for other people.\r\n\r\nThe estimated completion date is a floating target.","creator":{"login":"Aeva","id":768449,"avatar_url":"https://avatars.githubusercontent.com/u/768449?v=3","gravatar_id":"","url":"https://api.github.com/users/Aeva","html_url":"https://github.com/Aeva","followers_url":"https://api.github.com/users/Aeva/followers","following_url":"https://api.github.com/users/Aeva/following{/other_user}","gists_url":"https://api.github.com/users/Aeva/gists{/gist_id}","starred_url":"https://api.github.com/users/Aeva/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/Aeva/subscriptions","organizations_url":"https://api.github.com/users/Aeva/orgs","repos_url":"https://api.github.com/users/Aeva/repos","events_url":"https://api.github.com/users/Aeva/events{/privacy}","received_events_url":"https://api.github.com/users/Aeva/received_events","type":"User","site_admin":false},"open_issues":16,"closed_issues":49,"state":"open","created_at":"2014-10-16T21:22:56Z","updated_at":"2015-05-17T19:23:06Z","due_on":null,"closed_at":null},"comments":0,"created_at":"2015-05-17T19:23:06Z","updated_at":"2015-05-17T19:23:06Z","closed_at":null,"body":"Once issue #100 is complete, it will be possible to have interesting pefabs for rendering.  Issue #95 should be implemented as a RenderNode prefab.  This would, however, not be utilized in the user-defined rendering stack, but rather would make use of an early pipeline stage.\r\n\r\nThis issue focuses on composition RenderNodes, which take two image buffers and interpolates between them.  This can be used for stereoscopic rendering modes, transition effects (eg screen wipe, shatter, etc), as well as for loading screens.\r\n\r\n - [ ] make the stereoscopic demo's fragment shader to be a bundled shader\r\n - [ ] simple screen wipe transition effect\r\n - [ ] loading screen prefab\r\n\r\nThe loading screen prefab includes a render node and a simple bundled image or three to visualize a the loading bar etc.  When the media ready event is fired, it triggers a transition effect (something that could be swapped out via a property on the loading screen render node).  The loading screen rendernode probably should have a .reset_loading method, so that it can be activated again at a later point.\r\n\r\nIt would be a reasonable configuration to have it so that the loading screen render node is always the top level render node in the tree, and it should be optimized such that this does not introduce any significant overhead.\r\n\r\nIt could also be that the loading screen itself is a separate render node that can be overridden should the dev desire to do so.  Different 'themes' might be bundled with m.grl so that one can have some basic customization in place regardless."}}