On 04/03/13 08:11, Gustavo Noronha Silva wrote:
I use the Amazon AWS and I've made it into a web app. It works mostly fine when I'm on the console, but it has a tendency of trying to open some things in a new window (such as the account activity report and such), which causes those to be open in a regular Ephy window. This is almost never what I want. So this is what I've been pondering: what if we ask the user when the link will open a new window whether that link should be considered a piece of the application?
I can't help thinking what GNOME really needs for cases like this is an Android-like approach to handling http(s) load requests: By allowing applications to register to handle specific domains. For example, I have Identi.ca and Twitter installed as web apps, but when I click on a link to a post in either in an email or on another web site, it gets loaded in regular Ephy rather than the correct web app. If the Identi.ca web app had registered to handle "http[s]://[*.]identi.ca/*", then when I click the link the app could invoked to handle the request instead of regular Ephy. This provides a way of handling your case, in that if the domain of the page being loaded in the popup matches the URI(s) registered by the web app, then the web app will be prompted to load the page rather than regular Ephy. Also, this may well be a case where having tabs for web apps makes sense — it can load additional requests in additional tabs, also handling your case well. The only additional thing that might be needed is a way let users extend the list of registered domains for a web app. A nice gesture would be dragging a tab from a regular Ephy instance to a web app, followed with a prompt to confirm the decision "Do you want to load pages from *blarg.com* in Identi.ca from now on? [Yes/No/Only once]", and of course some accessible/discoverable version of same. //Mike -- ⊨ Michael Gratton, Percept Wrangler. ⚙ <http://mjog.vee.net/>
Attachment:
signature.asc
Description: OpenPGP digital signature