On Fri, Jul 24, 2015 at 12:15:22PM +0800, Philip Chee wrote:
> On 23/07/2015 14:40, Mike Hommey wrote:
> > On Thu, Jul 23, 2015 at 02:34:50PM +0800, Philip Chee wrote:
> >> On 22/07/2015 05:54, J. Ryan Stinnett wrote:
> >>> The DevTools team is planning to move our code out of
> >>> /browser/devtoo
On Thu, Jul 23, 2015 at 10:54 PM, Jeff Griffiths wrote:
> On Thu, Jul 23, 2015 at 11:43 AM, J. Ryan Stinnett wrote:
>> On Thu, Jul 23, 2015 at 8:11 AM, Paul Rouget wrote:
>>> I guess by moving things to /devtools/, you also want to update the
>>> URLs to chrome://devtools/content.
>>> So then, w
On 23/07/2015 17:36, Panos Astithas wrote:
> On Thu, Jul 23, 2015 at 8:25 AM, Paul Rouget wrote:
>
>> On Wed, Jul 22, 2015 at 2:48 PM, Panos Astithas wrote:
>> > If you are thinking about shipping them as part of browser.html, we still
>> > have XUL dependencies that we need to get rid of first
On 23/07/2015 14:40, Mike Hommey wrote:
> On Thu, Jul 23, 2015 at 02:34:50PM +0800, Philip Chee wrote:
>> On 22/07/2015 05:54, J. Ryan Stinnett wrote:
>>> The DevTools team is planning to move our code out of
>>> /browser/devtools and /toolkit/devtools and into a new top level
>>> /devtools direc
On Thu, Jul 23, 2015 at 11:43 AM, J. Ryan Stinnett wrote:
> On Thu, Jul 23, 2015 at 8:11 AM, Paul Rouget wrote:
>> I guess by moving things to /devtools/, you also want to update the
>> URLs to chrome://devtools/content.
>> So then, we can compile and open the devtools with non-firefox builds
>>
On Thu, Jul 23, 2015 at 8:11 AM, Paul Rouget wrote:
> I guess by moving things to /devtools/, you also want to update the
> URLs to chrome://devtools/content.
> So then, we can compile and open the devtools with non-firefox builds
> (thunderbird, b2g, seamonkey, ...).
> But if the devtools include
I guess by moving things to /devtools/, you also want to update the
URLs to chrome://devtools/content.
So then, we can compile and open the devtools with non-firefox builds
(thunderbird, b2g, seamonkey, ...).
But if the devtools include browser code, this won't work. For
example, we import
chrome:/
On Thu, Jul 23, 2015 at 8:25 AM, Paul Rouget wrote:
> On Wed, Jul 22, 2015 at 2:48 PM, Panos Astithas wrote:
> > If you are thinking about shipping them as part of browser.html, we still
> > have XUL dependencies that we need to get rid of first and that work is
> > independent from moving the c
On Thu, Jul 23, 2015 at 02:34:50PM +0800, Philip Chee wrote:
> On 22/07/2015 05:54, J. Ryan Stinnett wrote:
> > The DevTools team is planning to move our code out of
> > /browser/devtools and /toolkit/devtools and into a new top level
> > /devtools directory.
> >
> > The main goals of this are to
On 22/07/2015 05:54, J. Ryan Stinnett wrote:
> The DevTools team is planning to move our code out of
> /browser/devtools and /toolkit/devtools and into a new top level
> /devtools directory.
>
> The main goals of this are to reduce confusion for new DevTools
> contributors and help us better organ
On Wed, Jul 22, 2015 at 2:48 PM, Panos Astithas wrote:
> If you are thinking about shipping them as part of browser.html, we still
> have XUL dependencies that we need to get rid of first and that work is
> independent from moving the code to a top-level devtools/ directory.
We don't use XUL, but
If you are thinking about shipping them as part of browser.html, we still
have XUL dependencies that we need to get rid of first and that work is
independent from moving the code to a top-level devtools/ directory.
On Wed, Jul 22, 2015 at 1:48 PM, Paul Rouget wrote:
> Does that include getting r
Does that include getting rid of /browser/ dependencies?
Ideally, we'd like to be able to compile non-Firefox builds with our devtools.
On Tue, Jul 21, 2015 at 11:54 PM, J. Ryan Stinnett wrote:
> The DevTools team is planning to move our code out of
> /browser/devtools and /toolkit/devtools and i
Yes, it's something that we'd like to do, but it's not trivial. Sure
creating a new product is easy, and moving bugs is fairly simple, but
educating people is a thing, and fixing everyone's workflows and scripts is
getting annoying, and it probably all adds up to something hard.
So while I'd like t
[tangentially related] Are there plans ot move DevTools to a product in
Bugzilla to match this code layout?
Kevin
On Tue, Jul 21, 2015 at 2:54 PM, J. Ryan Stinnett wrote:
> The DevTools team is planning to move our code out of
> /browser/devtools and /toolkit/devtools and into a new top level
>
The DevTools team is planning to move our code out of
/browser/devtools and /toolkit/devtools and into a new top level
/devtools directory.
The main goals of this are to reduce confusion for new DevTools
contributors and help us better organize our work in the future. It
will also aid future users
16 matches
Mail list logo
