You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cordova.apache.org by "Raymond Camden (Created) (JIRA)" <ji...@apache.org> on 2012/01/30 22:27:10 UTC
[jira] [Created] (CB-206) No documentation for navigator.app
methods
No documentation for navigator.app methods
------------------------------------------
Key: CB-206
URL: https://issues.apache.org/jira/browse/CB-206
Project: Apache Callback
Issue Type: Bug
Components: Docs
Affects Versions: 1.3.0
Reporter: Raymond Camden
Priority: Minor
There are a few method available in the navigator.app space, for example, exitApp, but there are not documented anywhere.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CB-206) No documentation for navigator.app
methods
Posted by "Filip Maj (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CB-206?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13196616#comment-13196616 ]
Filip Maj commented on CB-206:
------------------------------
Alright down this rabbit hole we go :)
+1 to what Jesse said, but I'll take it one step further: I don't think exitApp is a good API addition. I believe that window.close() should do this, use standard "web" approach whenever possible. Whether we want to monkey-patch window.close() and whether it is possible within Cordova is the more important question to answer, in my mind.
> No documentation for navigator.app methods
> ------------------------------------------
>
> Key: CB-206
> URL: https://issues.apache.org/jira/browse/CB-206
> Project: Apache Callback
> Issue Type: Bug
> Components: Docs
> Affects Versions: 1.3.0
> Reporter: Raymond Camden
> Priority: Minor
>
> There are a few method available in the navigator.app space, for example, exitApp, but there are not documented anywhere.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CB-206) No documentation for navigator.app
methods
Posted by "Jesse MacFadyen (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CB-206?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13196611#comment-13196611 ]
Jesse MacFadyen commented on CB-206:
------------------------------------
This is all possible on WP7, but I am reluctant to implement them as I do not understand the need for them.
I think the first step should be justification of their existence in the first place.
What are the implications of this API + jQM or other JS frameworks that already provide history management?
The current implementation on WP7 allows you to add an event listener ( via document ) for the back button event, at which time you can simple call javascript: history.go(-1);
The history stack is managed in the DOM already, and this only seems to make sense to me when more than one browser is present ( via activities/views where they cannot share history ), am I missing something?
The addition of 'exitApp' does make sense to me in cases where the history stack is empty, as this is the default behaviour for WP7 and expected by the user.
> No documentation for navigator.app methods
> ------------------------------------------
>
> Key: CB-206
> URL: https://issues.apache.org/jira/browse/CB-206
> Project: Apache Callback
> Issue Type: Bug
> Components: Docs
> Affects Versions: 1.3.0
> Reporter: Raymond Camden
> Priority: Minor
>
> There are a few method available in the navigator.app space, for example, exitApp, but there are not documented anywhere.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CB-206) No documentation for navigator.app
methods
Posted by "Simon MacDonald (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CB-206?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13196574#comment-13196574 ]
Simon MacDonald commented on CB-206:
------------------------------------
No, it is not based on a standard. The methods under the App class were originally introduced in Android and then implemented in BlackBerry as well. Personally, I think we should look if it is possible to support App under WP7 and if it is let's get it done and documented for 1.5.
> No documentation for navigator.app methods
> ------------------------------------------
>
> Key: CB-206
> URL: https://issues.apache.org/jira/browse/CB-206
> Project: Apache Callback
> Issue Type: Bug
> Components: Docs
> Affects Versions: 1.3.0
> Reporter: Raymond Camden
> Priority: Minor
>
> There are a few method available in the navigator.app space, for example, exitApp, but there are not documented anywhere.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CB-206) No documentation for navigator.app
methods
Posted by "Joe Bowser (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CB-206?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13196614#comment-13196614 ]
Joe Bowser commented on CB-206:
-------------------------------
I agree with Jesse on the history. Maintaining our own history on Android has made the most recent refactor CB-190 much harder. I would rather have the ability of using browser history whenever possible.
> No documentation for navigator.app methods
> ------------------------------------------
>
> Key: CB-206
> URL: https://issues.apache.org/jira/browse/CB-206
> Project: Apache Callback
> Issue Type: Bug
> Components: Docs
> Affects Versions: 1.3.0
> Reporter: Raymond Camden
> Priority: Minor
>
> There are a few method available in the navigator.app space, for example, exitApp, but there are not documented anywhere.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (CB-206) No documentation for navigator.app methods
Posted by "Filip Maj (Closed) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CB-206?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Filip Maj closed CB-206.
------------------------
Resolution: Invalid
They are not part of the official Cordova API, so we will not be documenting until they are. The first step to becoming officially supported is having good potential / representation across platforms.
I'll close this issue for now :)
> No documentation for navigator.app methods
> ------------------------------------------
>
> Key: CB-206
> URL: https://issues.apache.org/jira/browse/CB-206
> Project: Apache Callback
> Issue Type: Bug
> Components: Docs
> Affects Versions: 1.3.0
> Reporter: Raymond Camden
> Priority: Minor
>
> There are a few method available in the navigator.app space, for example, exitApp, but there are not documented anywhere.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (CB-206) No documentation for navigator.app methods
Posted by "Michael Brooks (Closed) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CB-206?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Michael Brooks closed CB-206.
-----------------------------
Resolution: Not A Problem
Assignee: Michael Brooks (was: Jesse MacFadyen)
> No documentation for navigator.app methods
> ------------------------------------------
>
> Key: CB-206
> URL: https://issues.apache.org/jira/browse/CB-206
> Project: Apache Callback
> Issue Type: Wish
> Components: Docs
> Affects Versions: 1.3.0
> Reporter: Raymond Camden
> Assignee: Michael Brooks
> Priority: Minor
>
> There are a few method available in the navigator.app space, for example, exitApp, but there are not documented anywhere.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CB-206) No documentation for navigator.app
methods
Posted by "Jesse MacFadyen (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CB-206?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jesse MacFadyen updated CB-206:
-------------------------------
Issue Type: Wish (was: Bug)
> No documentation for navigator.app methods
> ------------------------------------------
>
> Key: CB-206
> URL: https://issues.apache.org/jira/browse/CB-206
> Project: Apache Callback
> Issue Type: Wish
> Components: Docs
> Affects Versions: 1.3.0
> Reporter: Raymond Camden
> Assignee: Jesse MacFadyen
> Priority: Minor
>
> There are a few method available in the navigator.app space, for example, exitApp, but there are not documented anywhere.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CB-206) No documentation for navigator.app
methods
Posted by "Michael Brooks (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CB-206?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13196459#comment-13196459 ]
Michael Brooks commented on CB-206:
-----------------------------------
Is `navigator.app` even based on a standard? I couldn't find much referenced on Google.
Regardless Raymond, thanks for posting an issue around the docs accuracy! We need more of these. If you find anything else, please post away!
Michael
> No documentation for navigator.app methods
> ------------------------------------------
>
> Key: CB-206
> URL: https://issues.apache.org/jira/browse/CB-206
> Project: Apache Callback
> Issue Type: Bug
> Components: Docs
> Affects Versions: 1.3.0
> Reporter: Raymond Camden
> Priority: Minor
>
> There are a few method available in the navigator.app space, for example, exitApp, but there are not documented anywhere.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Reopened] (CB-206) No documentation for navigator.app
methods
Posted by "Jesse MacFadyen (Reopened) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CB-206?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jesse MacFadyen reopened CB-206:
--------------------------------
Assignee: Jesse MacFadyen
Creating a feature request from this issue. So we can continue to discuss it.
> No documentation for navigator.app methods
> ------------------------------------------
>
> Key: CB-206
> URL: https://issues.apache.org/jira/browse/CB-206
> Project: Apache Callback
> Issue Type: Bug
> Components: Docs
> Affects Versions: 1.3.0
> Reporter: Raymond Camden
> Assignee: Jesse MacFadyen
> Priority: Minor
>
> There are a few method available in the navigator.app space, for example, exitApp, but there are not documented anywhere.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CB-206) No documentation for navigator.app
methods
Posted by "Raymond Camden (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CB-206?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13196444#comment-13196444 ]
Raymond Camden commented on CB-206:
-----------------------------------
But if they are supported (I assume they are?) shouldn't they be documented? Even if the docs are per platform? I didn't even know this existed until today. If they are not officially supported and folks shouldn't be using them, then yeah, keep em hidden. ;)
> No documentation for navigator.app methods
> ------------------------------------------
>
> Key: CB-206
> URL: https://issues.apache.org/jira/browse/CB-206
> Project: Apache Callback
> Issue Type: Bug
> Components: Docs
> Affects Versions: 1.3.0
> Reporter: Raymond Camden
> Priority: Minor
>
> There are a few method available in the navigator.app space, for example, exitApp, but there are not documented anywhere.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CB-206) No documentation for navigator.app
methods
Posted by "Filip Maj (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CB-206?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13196439#comment-13196439 ]
Filip Maj commented on CB-206:
------------------------------
Probably because they are only specific to a single platform :)
> No documentation for navigator.app methods
> ------------------------------------------
>
> Key: CB-206
> URL: https://issues.apache.org/jira/browse/CB-206
> Project: Apache Callback
> Issue Type: Bug
> Components: Docs
> Affects Versions: 1.3.0
> Reporter: Raymond Camden
> Priority: Minor
>
> There are a few method available in the navigator.app space, for example, exitApp, but there are not documented anywhere.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CB-206) No documentation for navigator.app
methods
Posted by "Michael Brooks (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CB-206?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13198153#comment-13198153 ]
Michael Brooks commented on CB-206:
-----------------------------------
Ok, let's take the App Specification discussion to the dev mailing-list. Currently, the general consensus is that these are internal APIs that we do not want to document (i.e. commit every platform to implement). The one exception is the ability to close an application ( {{close();}} ), which Android and BlackBerry support as an undocumented API.
I'm closing this issue. Thanks for the discussion guys!
> No documentation for navigator.app methods
> ------------------------------------------
>
> Key: CB-206
> URL: https://issues.apache.org/jira/browse/CB-206
> Project: Apache Callback
> Issue Type: Wish
> Components: Docs
> Affects Versions: 1.3.0
> Reporter: Raymond Camden
> Assignee: Jesse MacFadyen
> Priority: Minor
>
> There are a few method available in the navigator.app space, for example, exitApp, but there are not documented anywhere.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CB-206) No documentation for navigator.app
methods
Posted by "Drew Walters (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CB-206?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13196450#comment-13196450 ]
Drew Walters commented on CB-206:
---------------------------------
Should be noted that I added BlackBerry support for navigator.app API so there are at least two platforms now :-)
> No documentation for navigator.app methods
> ------------------------------------------
>
> Key: CB-206
> URL: https://issues.apache.org/jira/browse/CB-206
> Project: Apache Callback
> Issue Type: Bug
> Components: Docs
> Affects Versions: 1.3.0
> Reporter: Raymond Camden
> Priority: Minor
>
> There are a few method available in the navigator.app space, for example, exitApp, but there are not documented anywhere.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CB-206) No documentation for navigator.app
methods
Posted by "Bryce Curtis (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CB-206?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13196697#comment-13196697 ]
Bryce Curtis commented on CB-206:
---------------------------------
There is no spec for navigator.app. It was initially introduced to handle app management and resources that were unique to Android. For example hooking the back button which will probably never be in a spec. Later, it was added to BB, since it had some common features with Android.
Regarding exitApp(), it is used by both Android & BB since the OS supports it, and has proven useful to be able to programmatically exit. We can have a discussion as to whether to "assign" a web approach such as window.close() instead, but there have been issues with javascript frameworks (like jQuery) that sometimes use window and history manipulations to do their magic. (Some of the complexity with history was due to jQuery issues.)
There's a difference between pure web apps and PhoneGap apps that seems to leave a few unique functions that can't be done the web way, yet aren't across all the platforms. This is what navigator.app addresses. Maybe we need to propose an App spec, come up with some other mapping, or stub out an API that degrades if not supported by a platform.
Maybe we should start with a list of scenarios which drove much of the navigator.app API?
Anyway, this should good for discussion :-)
> No documentation for navigator.app methods
> ------------------------------------------
>
> Key: CB-206
> URL: https://issues.apache.org/jira/browse/CB-206
> Project: Apache Callback
> Issue Type: Wish
> Components: Docs
> Affects Versions: 1.3.0
> Reporter: Raymond Camden
> Assignee: Jesse MacFadyen
> Priority: Minor
>
> There are a few method available in the navigator.app space, for example, exitApp, but there are not documented anywhere.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira