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/devtools and
On Thu, Jul 23, 2015 at 11:43 AM, J. Ryan Stinnett jry...@gmail.com wrote:
On Thu, Jul 23, 2015 at 8:11 AM, Paul Rouget p...@mozilla.com 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
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
On Thu, Jul 23, 2015 at 10:54 PM, Jeff Griffiths jgriffi...@mozilla.com wrote:
On Thu, Jul 23, 2015 at 11:43 AM, J. Ryan Stinnett jry...@gmail.com wrote:
On Thu, Jul 23, 2015 at 8:11 AM, Paul Rouget p...@mozilla.com wrote:
I guess by moving things to /devtools/, you also want to update the
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 directory.
On 23/07/2015 17:36, Panos Astithas wrote:
On Thu, Jul 23, 2015 at 8:25 AM, Paul Rouget p...@mozilla.com wrote:
On Wed, Jul 22, 2015 at 2:48 PM, Panos Astithas p...@mozilla.com wrote:
If you are thinking about shipping them as part of browser.html, we still
have XUL dependencies that we
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 organize
On Thu, Jul 23, 2015 at 8:11 AM, Paul Rouget p...@mozilla.com 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
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 reduce
On Thu, Jul 23, 2015 at 8:25 AM, Paul Rouget p...@mozilla.com wrote:
On Wed, Jul 22, 2015 at 2:48 PM, Panos Astithas p...@mozilla.com 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
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 jry...@gmail.com wrote:
The DevTools team is planning to move our code out of
/browser/devtools and
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
On Wed, Jul 22, 2015 at 2:48 PM, Panos Astithas p...@mozilla.com 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
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 p...@mozilla.com wrote:
Does that
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
[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 jry...@gmail.com wrote:
The DevTools team is planning to move our code out of
/browser/devtools and /toolkit/devtools and into a
16 matches
Mail list logo
