Re: [dev-servo] NCSU Team introduction

On 2016-11-21 5:22 PM, bban...@ncsu.edu wrote: On Thursday, November 3, 2016 at 5:43:29 PM UTC-4, Josh Matthews wrote: On 2016-11-03 4:05 PM, ysu...@ncsu.edu wrote: Hi Josh, Do we need to write test cases for what we have done so far? If yes, do we need to run auto test cases (e.g. unit

Re: [dev-servo] NCSU Team introduction

On Thursday, November 3, 2016 at 5:43:29 PM UTC-4, Josh Matthews wrote: > On 2016-11-03 4:05 PM, ysu...@ncsu.edu wrote: > > Hi Josh, > > > > Do we need to write test cases for what we have done so far? If yes, do we > > need to run auto test cases (e.g. unit test) or a simple HTML test page is >

Re: [dev-servo] Servo embedding story & killing mozbrowser

Till Schneidereit 2016 November 17 at 09:22 Our focus is on creating a unified developer experience for Servo embedding. With the core embedding API targeting Rust, we're looking into building a lightweight runtime that seamlessly ties into the Rust

[dev-servo] Creating a JSObject -> id map for the Debugger IPC server.

For the Servo debugger, we need some kind of IPC layer: The debugger server (i.e. the thing that talks the Chrome debugging protocol) needs to live in the same process (and perhaps even the same thread) as the constellation; it needs to work closely with the constellation to figure out which