Re: Visual Studio Project Generation
This is awesome! Thank you! Chris P. On 2/19/2014 8:28 AM, Gregory Szorc wrote: The tree (only inbound so far) now has (alpha) support for generating Visual Studio Project files. Features: * IntelliSense works * Build from within Visual Studio * Launch binaries from Visual Studio * Debug symbols loaded automatically (breakpoints work) Please read https://hg.mozilla.org/integration/mozilla-inbound/file/default/build/docs/visualstudio.rst for usage info. File bugs against Core :: Build Config to request improvements. Bug 973770 is on file and has a patch to generate Eclipse projects. That should hopefully land soon. ___ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
Re: New necko cache?
On 19.02.2014 01:56, Neil wrote: In particular, I understand that there is a preference to toggle the cache. What does application code have to do in order to work with whichever cache has been enabled? Nothing? It's a different backend behind the same API, at least that's my rough and possibly not quite correct understanding... ___ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
Re: Announcing AsyncShutdown
Indeed, AsyncShutdown should help you in the normal scenario, i.e. if Firefox is quit normally. It won't help you if the process crashes, is killed by the task manager, or the computer goes to sleep. Cheers, David On 2/18/14 6:35 PM, Noitidart wrote: Much thanks David. Im working on an addon called Floppers. It's for Twitter. It also tells you who has blocked you. So how it does this is it checks the history of users that you have been in contact with but not on your Following or Follewer lists, it checks behind the scense. How it does it is by Requesting Friend on each account behind the scense, after the XMLHTTPRequest completes, the req either goes through or come back saying you are blocked, and i updated my SQLite database. However if it went through I must cancel the request so the user on the other end never sees the req came. So its critical I keep firefox open for at least 1 more XMLHTTPReq and thats to cancel the req. Which should be just 1 to 30 seconds max (for super slow connections). Im worried if a ctrl+alt+del happens after the friend req is sent, im trying to find a way to notify the user when the process is hung up or crashed after the first req. Much thanks for the reply David and really appreciate this module nonetheless, it should help me with making that final call if they don't ctrl+alt+del the process or some other thing causes the process to hang/crash. -- David Rajchenbach-Teller, PhD Performance Team, Mozilla ___ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
Re: New necko cache?
+cc On Tue, Feb 18, 2014 at 7:56 PM, Neil n...@parkwaycc.co.uk wrote: Where can I find documentation for the new necko cache? So far I've only turned up some draft planning documents. In particular, I understand that there is a preference to toggle the cache. What does application code have to do in order to work with whichever cache has been enabled? -- Warning: May contain traces of nuts. ___ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform ___ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
Firebug in embedded XULRunner.
Hello, we're using XULRunner as an engine for displaying web pages in a Java application. The way we're using XULRunner is via JWebBrowser - a Java control that embeds SWT Browser that embeds XULRunner. We need to debug and measure execution time of JavaScript inside the pages we display. We have Firebug in Firefox for this, but we don't know how to get Firebug into embedded XULRunner (we use xulrunner-22.0.en-US.win32). The author of JWebBrowser has helped us to some degree. He says (in http://sourceforge.net/p/djproject/discussion/671154/thread/bfb4b536/): I don't know if all plugins can work in the embedded mode, I just know that Flash does. Anyway, the piece of information I have about profiles is that the SWT Browser that I embed uses the eclipse profile in XULRunner. If you add the plugin (by copying or linking the necessary resources there), then the plugin should be taken into account. The trick is to find where this profile is located, which I never investigated. Could you guys help us further? Thanks and regards, Aurimas Pranskevičius ___ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
Re: New necko cache?
On 02/19/2014 11:50 AM, Dao wrote: On 19.02.2014 01:56, Neil wrote: In particular, I understand that there is a preference to toggle the cache. What does application code have to do in order to work with whichever cache has been enabled? Nothing? It's a different backend behind the same API, at least that's my rough and possibly not quite correct understanding... We've changed the API some time ago. Honza wrote a wrapper that implemented the new API but used the old cache backend. The preference change now just replaces the old backend with the new one. old API: http://mxr.mozilla.org/mozilla-central/source/netwerk/cache/*.idl new API: http://mxr.mozilla.org/mozilla-central/source/netwerk/cache2/*.idl Michal ___ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
Re: Non-technical comments in Bugzilla
Nicholas Nethercote wrote: On Thu, Feb 13, 2014 at 1:39 PM, Botond Ballobba...@mozilla.com wrote: landing - For comments that include commit URLs summary - For comments that summarize a previously lengthy discussion workaround - For comments that include a workaround for an unfixed bug spam - For comments that don't provide technical content STR - For comments (other than the description) that contain STR. Useful for locating refined or alternate STR in later comments. diagnosis - Where we understand the cause of a bug but haven't fixed it yet, for a comment that describes the cause. design - Where we know how we'd like to fix a bug, bug haven't done it yet, for a comment that describes the plan for how to fix it. Documentation of these within Bugzilla would be good. A keyword system might be too restrictive at this point, but auto-suggestions of common tags could be helpful. the tagging system's autocomplete already sorts by most-frequently-used first. documentation-wise, i suggest using a wiki rather than bugzilla itself. two other useful tags are obsolete and typo, both will also cause the comment to be collapsed by default. -- byron jones - :glob - bugzilla.mozilla.org team - ___ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
DXR now indexing comm-central
We've just added comm-central to DXR! You can find it at http://dxr.mozilla.org/comm-central/source/ or through the new Switch Tree menu. The menu knows some tricks: it tries hard to preserve things like your browsing position and your search query while moving from tree to tree, so you can chase similar lines of inquiry across branches. This will become even more thorough in the future: for instance, pinning it so you can flit between branches while keeping your eyes locked at the same line of a file. This marks the beginning of our conquest of All The Trees. More are coming: https://bugzilla.mozilla.org/show_bug.cgi?id=820531. Thanks to Kendall Libby for getting the build going and Joshua Cranmer for sage advice on the build system. For now, it's indexing as if it were building SeaMonkey, but we'll be switching to Thunderbird as soon as we get that working. There are only about 16 files' difference between the two, so most of you probably won't notice. With wishes of happy hacking, Erik ___ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
Re: New necko cache?
Honza Bambas wrote: On 2/19/2014 1:56 AM, Neil wrote: Where can I find documentation for the new necko cache? So far I've only turned up some draft planning documents. In particular, I understand that there is a preference to toggle the cache. What does application code have to do in order to work with whichever cache has been enabled? The old API in netwerk/cache will go away, I'm occasionally checking the tree if no one has added usage of the old API and fix it (so far I just found places I forgot to update my self;)) Sure, it's usage of the old API outside mozilla-central that I'm worried about. -- Warning: May contain traces of nuts. ___ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
Re: New necko cache?
On 2/19/2014 11:09 PM, Neil wrote: Honza Bambas wrote: On 2/19/2014 1:56 AM, Neil wrote: Where can I find documentation for the new necko cache? So far I've only turned up some draft planning documents. In particular, I understand that there is a preference to toggle the cache. What does application code have to do in order to work with whichever cache has been enabled? The old API in netwerk/cache will go away, I'm occasionally checking the tree if no one has added usage of the old API and fix it (so far I just found places I forgot to update my self;)) Sure, it's usage of the old API outside mozilla-central that I'm worried about. That is something I plan soon communicate to the outside world. I was hoping this week to start writing docs (API + impl). When we have it we can link to it in a post on dev-platform and other forum with extension developers audience. -hb- ___ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
Re: New necko cache?
Michal Novotny wrote: On 02/19/2014 11:50 AM, Dao wrote: On 19.02.2014 01:56, Neil wrote: In particular, I understand that there is a preference to toggle the cache. What does application code have to do in order to work with whichever cache has been enabled? Nothing? It's a different backend behind the same API, at least that's my rough and possibly not quite correct understanding... We've changed the API some time ago. Honza wrote a wrapper that implemented the new API but used the old cache backend. The preference change now just replaces the old backend with the new one. old API: netwerk/cache/*.idl new API: netwerk/cache2/*.idl Is the conversion straightforward? In particular, the API calls I'm interested in: 1. Given an HTTP or FTP URI, return the size of the cached data 2. Returning the size of the disk cache 3. Clearing the disk and memory cache 4. Clearing the offline app cache Also, are the prefs used by the cache the same? In particular, browser.cache.check_doc_frequency, browser.cache.disk.capacity, browser.cache.disk.parent_directory and browser.cache.disk.smart_size.enabled come to mind. -- Warning: May contain traces of nuts. ___ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
Re: New necko cache?
On Tue, Feb 18, 2014 at 7:56 PM, Neil n...@parkwaycc.co.uk mailto:n...@parkwaycc.co.uk wrote: Where can I find documentation for the new necko cache? So far I've only turned up some draft planning documents. In particular, I understand that there is a preference to toggle the cache. What does application code have to do in order to work with whichever cache has been enabled? Application code generally doesn't have to do anything to work with the new cache, unless it's a direct consumer of the cache API (we changed a few APIs from sync to async IIRC). Mostly we just have the new code, but as you point out there are some design docs and blogs posts and meta-bugs tracking the work: http://www.janbambas.cz/new-firefox-http-cache-backend-implementation/ https://wiki.mozilla.org/Necko/Cache/Plans https://bugzilla.mozilla.org/show_bug.cgi?id=913806 Is there something specific you're wondering about? Jason ___ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
Fwd: [Planned Maintenance Notification] Tree Closure Try Reset
Please see below for tree closing activities on Sat, Feb 22 -- including a reset of the try repo. Original Message Subject:[Planned Maintenance Notification] Tree Closure Date: Wed, 19 Feb 2014 23:20:05 - From: notificati...@mozilla.com To: infra-...@mozilla.com, dev-plann...@lists.mozilla.org, dev-tree-managem...@lists.mozilla.org, dev-platform@lists.mozilla.org, dev-...@lists.mozilla.org, dev-g...@lists.mozilla.org Short Summary : There will be a tree closing maintenance window on Saturday for multiple maintenance procedures and changes to be done: Main tracking bug: 971818 962291 - reset try repository 971445 - reboot github-sync3 971684 - Rearrange product delivery mounts to remove nested client-side mounts 606362 - Add SSL/TLS support to RabbitMQ (pulse.mozilla.org) 974449 - bouncer db master failover Mozilla IT Outage Notification: -- Issue Status: Upcoming Bug IDs: 971818 Start Date:2014-02-22 Start Time:12:00 PST Duration: 330 minutes (expected) Site: SCL3 Services: Tree Closure, hg.mozilla.org, git.mozilla.org Impact of Work:The general impact is that during the entire window, committing code to create new builds and tests will be unavailable. In addition, recent builds through ftp.mozilla.org may be unavailable for the duration of the window. If you have any questions or concerns please address them to notificati...@mozilla.com -- ___ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
