Account Options

  1. Sign in
The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Google Groups Home for chromium.org
« Groups Home
Breaking Change: chrome.appWindow ->chrome.app.window
There are currently too many topics in this group that display first. To make this topic appear first, remove this option from another topic.
There was an error processing your request. Please try again.
flag
  3 messages - Collapse all  -  Translate all to Translated (View all originals)
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 
From:
To:
Cc:
Followup To:
Add Cc | Add Followup-to | Edit Subject
Subject:
Validation:
For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers you hear
 
Antony Sargent  
View profile  
 More options Jul 20 2012, 4:57 pm
From: Antony Sargent <asarg...@chromium.org>
Date: Fri, 20 Jul 2012 13:57:20 -0700
Local: Fri, Jul 20 2012 4:57 pm
Subject: Breaking Change: chrome.appWindow ->chrome.app.window

[For context, this only affects apps using our new packaged
app<http://developer.chrome.com/apps> system
which is still in experimental form and only available in the canary and
dev channels.]

I just landed http://codereview.chromium.org/10659021/ which renames the
chrome.appWindow namespace to chrome.app.window, which will affect most
packaged apps. This change should show up in the next canary build and then
the next Chrome 22 dev build.


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
rsanchez1  
View profile  
 More options Jul 20 2012, 7:54 pm
From: rsanchez1 <rsanchez1...@gmail.com>
Date: Fri, 20 Jul 2012 16:54:42 -0700 (PDT)
Local: Fri, Jul 20 2012 7:54 pm
Subject: Re: Breaking Change: chrome.appWindow ->chrome.app.window

Just to make sure, this won't affect any packaged apps already in the
Chrome Web Store, will it? I released my packaged app on the Chrome Web
Store back in February, so I'm not sure if I'm using the new packaged apps
system. Also, will we have to change to the new packaged app system
eventually if we are not using it yet?


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
taterbase  
View profile  
 More options Jul 20 2012, 10:21 pm
From: taterbase <shan...@gmail.com>
Date: Fri, 20 Jul 2012 19:21:00 -0700 (PDT)
Subject: Re: Breaking Change: chrome.appWindow ->chrome.app.window

rsanchez1, I don't believe so. The packaged apps mentioned here are not yet
allowed to be distributed.


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
End of messages
« Back to Discussions « Newer topic     Older topic »