Re: New necko cache?
On 02/21/2014 12:01 AM, Honza Bambas wrote: On 2/20/2014 10:25 PM, Neil wrote: Well, that was confusing. The old contract ID was @mozilla.org/network/cache-service;1 The new contract ID is @mozilla.org/netwerk/cache-storage-service;1 Turns out that there are two differences, not one. Yes, forgot to mention, sorry. Hoped it's obvious from looking into the IDL file. Why do you take this as two differences? netwerk vs network HTH Ms2ger ___ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
Re: How to force winxp compatibility building with vc11
JoeS wrote: I tried hacking the following into the tail end of msvc11.bat file in mozilla-build: Try setting MOZ_MAXWINSDK=70100 Alternatively, try installing the SDK 7.1 compilers and use the msvc10.bat file. (You can still use the VS debugger.) -- Warning: May contain traces of nuts. ___ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
Re: [Proposal] Move global namespace classes under dom/events to mozilla or mozilla::dom
Hi, On 2014/02/12 23:22, Boris Zbarsky wrote: On 2/12/14 4:46 AM, Masayuki Nakano wrote: I'm not sure which is the best name for the classes. E.g., DOMWheelEvent vs. PointerEvent. I believe in this case PointerEvent is correct, because http://www.w3.org/TR/pointerevents/#pointerevent-interface but DOMWheelEvent should probably be just WheelEvent because https://dvcs.w3.org/hg/dom3events/raw-file/tip/html/DOM3-Events.html#interface-WheelEvent In general, the names for things that are standardized should just match the standard name, in the mozilla::dom namespace. In some (rare) cases the standard name starts with DOM; in those situations we should have our name start with DOM as well. Thank you for your reply. It sounds reasonable to me. However, there is a problem. nsDOMEvent will be just Event. And also the header file name will be Event.h. This sounds too general. How do you think about this problem? -- Masayuki Nakano masay...@d-toybox.com Manager, Internationalization, Mozilla Japan. ___ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
VK_ENTER has gone
Hi, there were similar two keyCode constants, one was VK_RETURN (DOM_VK_RETURN/NS_VK_RETURN), the other was VK_ENTER (DOM_VK_ENTER/NS_VK_ENTER). These were making a lot of developers confused and event handlers duplicated. Now, VK_ENTER has gone. See bug 969247 for the detail. https://bugzilla.mozilla.org/show_bug.cgi?id=969247 I hope that this doesn't cause any problem. But KeyboardEvent.DOM_VK_ENTER is now undefined in JS code. This might be a big change for some cases. If you find any problems about this change, please file new bugs and mark them as depending on bug 969247. Thanks in advance. -- Masayuki Nakano masay...@d-toybox.com Manager, Internationalization, Mozilla Japan. ___ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
Re: [Proposal] Move global namespace classes under dom/events to mozilla or mozilla::dom
Masayuki Nakano wrote: nsDOMEvent will be just Event. Well, only if you're using the mozilla::dom namespace. And also the header file name will be Event.h. Won't it be mozilla/dom/Event.h ? -- Warning: May contain traces of nuts. ___ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
Re: [Proposal] Move global namespace classes under dom/events to mozilla or mozilla::dom
On 2014/02/21 20:21, Neil wrote: And also the header file name will be Event.h. Won't it be mozilla/dom/Event.h ? Oh, good point. http://mxr.mozilla.org/mozilla-central/source/dom/events/moz.build#38 38 EXPORTS.mozilla.dom += [ 39 'EventTarget.h', 40 'PointerEvent.h', 41 'Touch.h', 42 ] Now, they are exported as mozilla/dom/*.h. -- Masayuki Nakano masay...@d-toybox.com Manager, Internationalization, Mozilla Japan. ___ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
Re: [Proposal] Move global namespace classes under dom/events to mozilla or mozilla::dom
On 2/21/14 6:07 AM, Masayuki Nakano wrote: nsDOMEvent will be just Event. Just like Element is just Element as long as you're in DOM code, yes. This is a good thing, imo. Of course in code not in the mozilla::dom namespace, you get mozilla::dom::Event or dom::Event, which seems fine to me. -Boris ___ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
Re: We live in a memory-constrained world
On 02/21/2014 01:38 PM, Nicholas Nethercote wrote: Greetings, We now live in a memory-constrained world. By we, I mean anyone working on Mozilla platform code. When desktop Firefox was our only product, this wasn't especially true -- bad leaks and the like were a problem, sure, but ordinary usage wasn't much of an issue. But now with Firefox on Android and particularly Firefox OS, it is most definitely true. In particular, work is currently underway to get Firefox OS working on devices that only have 128 MiB of RAM. The codename for these devices is Tarako (https://wiki.mozilla.org/FirefoxOS/Tarako). In case it's not obvious, the memory situation on these devices is *tight*. Optimizations that wouldn't have been worthwhile in the desktop-only days are now worthwhile. For example, an optimization that saves 100 KiB of memory per process is pretty worthwhile for Firefox OS. Thanks for the heads-up. Time to throw https://bugzilla.mozilla.org/show_bug.cgi?id=807359 back on the barbie... (Feel free to give it a new memshrink priority as you see fit, Nicholas) Jason ___ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
