- From: Rik Cabanier <rcabanier@magicleap.com>
- Date: Mon, 20 Aug 2018 15:55:50 -0700
- To: trsmith@mozilla.com
- Cc: public-immersive-web@w3.org
- Message-ID: <CADHwi=Try0-SQA-8p8L7w8rAh-tv8DikTpo_XMgce6s5h7ehzw@mail.gmail.com>
On Mon, Aug 20, 2018 at 1:31 PM Trevor Smith <trsmith@mozilla.com> wrote: > Great! Thanks, Rik. > > Let's move this thread to that Issue. If it feels like the conversation is > split, go ahead and create a separate Issue for the script-driven path and > then people can work together on the path of their choice and find > consensus on how each would work > I added an issue: https://github.com/immersive-web/proposals/issues/19 > On Mon, Aug 20, 2018 at 1:09 PM Rik Cabanier <rcabanier@magicleap.com> > wrote: > >> I created a github issue so we can continue the discussion there: >> https://github.com/immersive-web/proposals/issues/18 >> <https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_immersive-2Dweb_proposals_issues_18&d=DwMFaQ&c=0ia8zh_eZtQM1JEjWgVLZg&r=jahSgznxrAL5kPgsRvs7bhKUEd9M5X0d-NE2WJg7VT0&m=RNGZ4T2l4TVS3RSg_wr91C5jjiPFGg8VanzHPrl6eyc&s=jilYruMQzbxigj-nNPMtD6npC5NDeI-3a7GQUV4s0aQ&e=> >> >> It seems that there are 2 camps at the moment where one side wants to >> build upon the current architecture and the other wants to build a more >> flexible script driven solution. Should I open an issue on that? >> >> >> On Fri, Aug 17, 2018 at 4:27 PM Waliczek, Nell <nhw@amazon.com> wrote: >> >>> This is something that I have heard several different folks express >>> interest in. The best way to move this forward would be to write up an >>> issue on the Proposals Repo https://github.com/immersive-web/proposals >>> <https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_immersive-2Dweb_proposals&d=DwMGaQ&c=0ia8zh_eZtQM1JEjWgVLZg&r=jahSgznxrAL5kPgsRvs7bhKUEd9M5X0d-NE2WJg7VT0&m=IHxKbziTOHAqPbdgA6_-VEyszxOKo-r7DJ1_alMyVxg&s=PCCWIJzVu9w36Z6EfnFY18NFKC_9kiZxmBrOqWqduZA&e=> >>> . The write-up should have a clear description of the problem and a rough >>> idea of how you’re thinking about trying to solve it. A few paragraphs is >>> more than sufficient; no need for a full explainer or idl of any sort yet. >>> >>> >>> >>> Another company will need to respond to the issue to say they’re >>> interested in collaborating on design with intent to implement if agreement >>> can be reached. Initial design work can start in the issue, and, when >>> ready, Trevor will open up a repo in the Immersive Web GitHub organization >>> for you to start iterating on the design in more detail. >>> >>> >>> >>> I’m very excited that Magic Leap is seriously considering participating >>> in standards design rather than taking an approach that would run the risk >>> of fracturing the Immersive Web 😊 >>> >>> >>> >>> Nell >>> >>> >>> >>> *From: *Rik Cabanier <rcabanier@magicleap.com> >>> *Date: *Friday, August 17, 2018 at 3:34 PM >>> *To: *"public-immersive-web@w3.org" <public-immersive-web@w3.org> >>> *Subject: *3d favicons >>> *Resent-From: *<public-immersive-web@w3.org> >>> *Resent-Date: *Friday, August 17, 2018 at 3:32 PM >>> >>> >>> >>> All, >>> >>> >>> >>> We're interested in coming up with a standardized way of supporting 3D >>> favicons so a website can have a 2D and a 3D icon. >>> >>> Helio [1] already implemented some support but we want to have a >>> standardized solution that incorporates everyone's input. >>> >>> >>> >>> Is anyone else interested in pursuing this? >>> >>> >>> >>> Rik >>> >>> >>> >>> 1: https://www.magicleap.com/experiences/helio >>> >> > > -- > Trevor F. Smith > Reality Research Engineer > Emerging Technologies @ Mozilla > trsmith@mozilla.com >
Received on Monday, 20 August 2018 22:56:26 UTC