Thanks Marcel for your response, i'm going to post this question in the
good forum.
Just to precise my code i use in iOs (href is the url):
window.open(href,
'_blank','location=yes,enableViewportScale=yes,closebuttoncaption=Fermer');
and window.open(href, '_blank','location=yes');
sorry
Still something strange going on, there is no way to search!
Cheers,
Erik Jan
On 9 Jan,2014, at 2:18 , Andrew Grieve agri...@chromium.org wrote:
Awesome, thanks Steve.
On Wed, Jan 8, 2014 at 3:27 PM, Steven Gill stevengil...@gmail.com wrote:
I just tried to publish it and it
If it does work to put the values in a sibling file to strings.xml,
you can use source-file to copy you own file into res/values which
will then not be re-added on each prepare.
On Wed, Jan 8, 2014 at 8:02 PM, Ross Gerbasi rgerb...@gmail.com wrote:
Hello all, back on this Android plugin resource
Good point about postMessage allowing devs to add their own messages.
That's a very compelling argument to keep postMessage around, but I
don't think it means we should be using it for our officially
supported hooks.
On Wed, Jan 8, 2014 at 9:40 PM, purplecabbage purplecabb...@gmail.com wrote:
Good call I went with glass.xml like Axel had mentioned. That does work and
does not get overwritten. Still would love to think about allowing
plugin.xml to use config.xml variables to write into platform source files.
-ross
On Thu, Jan 9, 2014 at 7:03 AM, Andrew Grieve agri...@chromium.org
There was discussion some time ago about adding platform tags to the
top-level app config.xml, which could contain config-file tags to do what
you want. Having a plugin inject default values would not be supported,
though. The best you could do in that model would be printing a message at
install
On Thu, Jan 9, 2014 at 6:06 AM, Andrew Grieve agri...@chromium.org wrote:
Good point about postMessage allowing devs to add their own messages.
That's a very compelling argument to keep postMessage around, but I
don't think it means we should be using it for our officially
supported hooks.
On Thu, Jan 9, 2014 at 9:25 AM, Joe Bowser bows...@gmail.com wrote:
On Thu, Jan 9, 2014 at 6:06 AM, Andrew Grieve agri...@chromium.org wrote:
Good point about postMessage allowing devs to add their own messages.
That's a very compelling argument to keep postMessage around, but I
don't think it
Hey guys,
I hope this is the right place for this. I'm with Mozilla working on
Firefox OS support for cordova. Piotr is working with me on this. He
opened up a PR on the cordova-mobile-spec project that improves the
contacts automatic tests, and this is needed for the tests to pass on
Firefox OS.
I personally don't care if we want to go all traditional Java on the
codebase to 'win' code completion,etc but I do question if this is a real
priority issue.
Aside: I think we need to do a hangout. (We should have one anytime email
word count goes above one scroll.)
On Thu, Jan 9, 2014 at
We need to add notes to a few of the plugins for Firefox OS-specific
caveats. What is the best way to add this documentation?
I'm looking at this project: https://github.com/apache/cordova-docs.
Should I add it there and open a PR?
Also, I see that it is localized. What is the localization
Hey James,
That is the correct repo to add the docs to. PR would be perfect.
Hopefully someone else can chime in with the localization process. I am
unfamiliar with it. Here is a wiki article for it.
https://wiki.apache.org/cordova/CordovaTranslations
-Steve
On Thu, Jan 9, 2014 at 11:41 AM,
Hi James,
If you can create the corresponding Jira issue that would be great (as per
this workflow):
http://wiki.apache.org/cordova/ProcessingPullRequests
The problem in general with pull requests from Github is, we don't get
notifications that someone filed one...
On Thu, Jan 9, 2014 at 11:24
Done: https://issues.apache.org/jira/browse/CB-5757 (created as
sub-task of the task tracking all our work)
Thanks, it's still nice to create a PR so we can keep track of what
hasn't been merged but should be. Otherwise it's really hard to make
sure everything gets merged.
On Thu, Jan 9, 2014 at
Thanks Steven. The docs on edge are really different, actually, and
the plugins seem to be treated as external docs. The plugin docs are
just links to an .md file in the repo, for example:
https://github.com/apache/cordova-plugin-battery-status/blob/dev/doc/index.md
This is a much nicer way to
Well yes of course - its just that a PR should have a corresponding Jira
issue (PR/patchfile definitely required for non-committers)
On Thu, Jan 9, 2014 at 2:20 PM, James Long jl...@mozilla.com wrote:
Done: https://issues.apache.org/jira/browse/CB-5757 (created as
sub-task of the task
16 matches
Mail list logo
