Moving from xulrunner to firefox SDK

2017-08-21 Thread Manish
Hi, I am working on a desktop application named "AZARDI" which is based on xulrunner. It is an offline ePub Reader for all three major platforms (Windows, Mac, Linux). You can check it out at http://azardi.infogridpacific.com/. I have been deploying the application successfully with xulrunner

Re: New string types: nsAutoStringN<> and nsAutoCStringN<>

2017-08-21 Thread Mike Hommey
On Tue, Aug 22, 2017 at 04:38:04PM +1000, Nicholas Nethercote wrote: > I really wish our top-level namespace was "moz", rather than "mozilla". It's never too late to change it. I, for one, vote +1. Mike ___ dev-platform mailing list dev-platform@lists.m

Re: New string types: nsAutoStringN<> and nsAutoCStringN<>

2017-08-21 Thread Nicholas Nethercote
I really wish our top-level namespace was "moz", rather than "mozilla". Nick On Tue, Aug 22, 2017 at 10:31 AM, Eric Rahm wrote: > On Mon, Aug 21, 2017 at 8:32 AM, Jonathan Kew wrote: > > > > > Wouldn't it be more "modern Gecko-ish", though, to drop the "ns" prefix, > > and perhaps put Auto[C]S

Re: New string types: nsAutoStringN<> and nsAutoCStringN<>

2017-08-21 Thread Kris Maglione
On Mon, Aug 21, 2017 at 05:31:14PM -0700, Eric Rahm wrote: I'm not sure how much backing that has -- we'd be going from nsString => String which is pretty close to std::string -- it would be interesting to get some feedback. It's already a pretty common practice to have MFBT identifiers with t

Re: New string types: nsAutoStringN<> and nsAutoCStringN<>

2017-08-21 Thread Chris Peterson
On 2017-08-21 5:31 PM, Eric Rahm wrote: I'm not sure how much backing that has -- we'd be going from nsString => String which is pretty close to std::string -- it would be interesting to get some feedback. Or follow Rust's precedent and use type name `Str`. That would avoid confusion with std:

Re: New string types: nsAutoStringN<> and nsAutoCStringN<>

2017-08-21 Thread Eric Rahm
On Mon, Aug 21, 2017 at 8:32 AM, Jonathan Kew wrote: > > Wouldn't it be more "modern Gecko-ish", though, to drop the "ns" prefix, > and perhaps put Auto[C]String into the mozilla namespace? > > As Nick said, renaming all the things is a job for another day :) Coincidentally I have some pending c

Photon Engineering Newsletter #13

2017-08-21 Thread Jared Wein
(via https://msujaws.wordpress.com/2017/08/18/photon-engineering-newsletter-13/ ) This week I’m taking over for Dolske as he takes a vacation to view the eclipse. This is issue #13

Re: Quantum Flow Engineering Newsletter #20

2017-08-21 Thread Olli Pettay
On 08/18/2017 08:28 PM, Ehsan Akhgari wrote: On Fri, Aug 18, 2017 at 9:39 AM, Ryan VanderMeulen mailto:rvandermeu...@mozilla.com>> wrote: Is there a good way to get a sense of what the higher-impact bugs are that remain for improving Speedometer? Just going through the deps is difficu

Re: New string types: nsAutoStringN<> and nsAutoCStringN<>

2017-08-21 Thread Jonathan Kew
On 20/08/2017 23:35, Nicholas Nethercote wrote: Hi, For a long time we have had types nsAutoString and nsAutoCString which are strings with 64 chars of inline storage. They are good for holding short strings, most often on the stack, because they avoid the need to heap allocate a char buffer. I

Re: New string types: nsAutoStringN<> and nsAutoCStringN<>

2017-08-21 Thread Ben Kelly
On Mon, Aug 21, 2017 at 10:00 AM, Ben Kelly wrote: > Should that be `mStorage[N + 1]`? > Maybe not since things like NSID_LENGTH include the null pointer on their end. Sorry for my confusion. ___ dev-platform mailing list dev-platform@lists.mozilla.or

Re: New string types: nsAutoStringN<> and nsAutoCStringN<>

2017-08-21 Thread Ben Kelly
On Sun, Aug 20, 2017 at 6:35 PM, Nicholas Nethercote wrote: > Hi, > > For a long time we have had types nsAutoString and nsAutoCString which are > strings with 64 chars of inline storage. They are good for holding short > strings, most often on the stack, because they avoid the need to heap > all

[Firefox Desktop] Issues found: August 14th to August 18th

2017-08-21 Thread Cornel Ionce
Hi everyone, Here's the list of new issues found and filed by the Desktop Release QA Team last week, *August 14 - August 18* (week 33). Additional details on the team's priorities last week, as well as the plans for the current week are available at: https://public.etherpad-mozilla.org/p