I was using xulrunner to developing desktop application, so I want to storage the indexDB files in to customized place other than %AppData%/

2015-02-06 Thread Yonggang Luo
How to do that? Looking for ways to do that.
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform


Re: Some more PLDHashTable API tweaks

2015-02-06 Thread Nicholas Nethercote
On Fri, Feb 6, 2015 at 6:59 PM, Philip Chee  wrote:
>>
>> - PLD_NewDHashTable() and PLD_HashTableDestroy() have been removed. You 
>> should
>>   now just use |new|+PL_DHashTableInit() and PLD_HashTableDestroy()+|delete|,
>
> ITYM PL_DHashTableFinish()+|delete|

I do. Thank you for the correction.

Nick
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform


Intent to implement and ship: vertical text support (CSS writing-mode and related properties)

2015-02-06 Thread Jonathan Kew

We are working on support for

  v
  e
  r
  t
  i
  c
  a
  l

text in Gecko. This will allow web content (and eventually complete web 
apps, if desired) to use vertical writing, as traditionally used in East 
Asia.


In addition to the CSS writing-mode property, this will involve support 
for text-orientation (which determines whether glyphs within vertical 
text remain "upright" as if in horizontal text, or are rotated 90° to 
render "sideways"), and for logical versions of many properties that 
refer to physical directions (such as margin-left, padding-top, 
border-bottom, min-width, max-height, etc. etc.), so that stylesheets -- 
in particular, the UA's built-in stylesheets -- can be written in a form 
that works for both horizontal and vertical content.


The top-level meta bug covering this work is 
https://bugzilla.mozilla.org/show_bug.cgi?id=145503.


The major standards relevant to this work are:
http://dev.w3.org/csswg/css-writing-modes/
http://dev.w3.org/csswg/css-logical-props/

This will be part of the standard Gecko engine, available to HTML 
content across all products and platforms. (At this time, we are not 
planning to support vertical writing modes for XUL.)


Our intention is to implement and release support for vertical text and 
layout in stages: initially, vertical mode will be supported for simple 
blocks and inline elements, including styling and editing text as 
expected. Some of the simpler form controls such as checkboxes, radio 
buttons, input fields and textareas should also be usable in the first 
release. However, more complex controls and layout constructs will not 
be vertical-enabled until later releases. Thus, the initial release 
should be adequate to support pages that want to display straightforward 
blocks of text using vertical writing (e.g. a news site, blog, or ebook 
reader).


There is already some vertical writing mode support in webkit, blink and 
IE, and tests are being developed (e.g. see 
http://www.gtalbot.org/BrowserBugsSection/CSS3WritingModes/). Current 
implementations are prefixed, and appear to be somewhat incomplete 
and/or based on earlier drafts of the specs, but there seems to be a 
good prospect of browsers converging as the specifications become more 
stable.


A good deal of the layout work to support writing modes has landed over 
the past year. It is controlled by the boolean pref 
"layout.css.vertical-text.enabled", which is currently false by default.


We intend to enable this feature by toggling the vertical-text pref to 
true in https://bugzilla.mozilla.org/show_bug.cgi?id=1099032 once the 
code is sufficiently stable. This may be in Gecko 38, if the remaining 
dependencies can be resolved.


JK

___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform


Re: Some more PLDHashTable API tweaks

2015-02-06 Thread Philip Chee
On 05/02/2015 11:45, Nicholas Nethercote wrote:
> Hi,
> 
> I just landed the patches in
> https://bugzilla.mozilla.org/show_bug.cgi?id=1050035. They
> affect PLDHashTable's API in the following ways.
> 
> - PLDHashTable now allocates its entry storage lazily. (nsTHashtable and
>   friends do too, since they are just layers on top of PLDHashTable.) This is 
> a
>   nice space win because about 45% of all created PLDHashTables never get any
>   elements inserted into them.
> 
> - As a result, PL_DHashTableInit() is now infallible. This is possible because
>   the allocation of entry storage now only occurs on table insertion, in
>   PL_DHashTableAdd().
> 
> - An infallible version of PL_DHashTableAdd() has been added. To use the
>   fallible version you need a |fallible_t| argument. All the old callsites 
> were
>   updated appropriately, to keep them fallible.
> 
> - PLD_NewDHashTable() and PLD_HashTableDestroy() have been removed. You should
>   now just use |new|+PL_DHashTableInit() and PLD_HashTableDestroy()+|delete|,
ITYM PL_DHashTableFinish()+|delete|

>   which are more obvious and only slightly more verbose. (And I have plans to
>   add a destructor and an initializing constructor, so in the end you'll be
>   able to just use |new| and |delete|).
> 
> I prepared a comm-central update patch in
> https://bugzilla.mozilla.org/show_bug.cgi?id=1129692.
> 
> Nick

Phil

-- 
Philip Chee , 
http://flashblock.mozdev.org/ http://xsidebar.mozdev.org
Guard us from the she-wolf and the wolf, and guard us from the thief,
oh Night, and so be good for us to pass.
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform