Removing references to legacy packaged apps across extension docs.

Removing references to legacy packaged apps across extension docs.

BUG=147662

[Aaron Boodman, 2012-09-16 00:44:35]

http://codereview.chromium.org/10914218/diff/4001/chrome/common/extensions/do...
File chrome/common/extensions/docs/server2/templates/articles/autoupdate.html
(right):

http://codereview.chromium.org/10914218/diff/4001/chrome/common/extensions/do...
chrome/common/extensions/docs/server2/templates/articles/autoupdate.html:53: ID
of an extension by going to the Extensions page (<b>chrome://extensions</b>).
What did we decide to do about pages like this that describe concepts that are
common to all types of packages?

[Mihai Parparita -not on Chrome, 2012-09-16 04:55:02]

http://codereview.chromium.org/10914218/diff/4001/chrome/common/extensions/do...
File chrome/common/extensions/docs/server2/templates/articles/autoupdate.html
(left):

http://codereview.chromium.org/10914218/diff/4001/chrome/common/extensions/do...
chrome/common/extensions/docs/server2/templates/articles/autoupdate.html:55:
Hosted apps, however, are not listed on the Extensions page.  You can find the
ID of any
Hosted apps are not (publicly) deprecated yet, we shouldn't remove references to
them.

http://codereview.chromium.org/10914218/diff/4001/chrome/common/extensions/do...
File chrome/common/extensions/docs/server2/templates/articles/autoupdate.html
(right):

http://codereview.chromium.org/10914218/diff/4001/chrome/common/extensions/do...
chrome/common/extensions/docs/server2/templates/articles/autoupdate.html:53: ID
of an extension by going to the Extensions page (<b>chrome://extensions</b>).
On 2012/09/16 00:44:35, Aaron Boodman wrote:
> What did we decide to do about pages like this that describe concepts that are
> common to all types of packages?

Given that this page appears in the apps doc set too
(http://developer.chrome.com/apps/autoupdate.html), I think the reference to
packaged apps can stay (it's equally applicable to both legacy and platform
apps).

http://codereview.chromium.org/10914218/diff/4001/chrome/common/extensions/do...
File chrome/common/extensions/docs/server2/templates/articles/overview.html
(left):

http://codereview.chromium.org/10914218/diff/4001/chrome/common/extensions/do...
chrome/common/extensions/docs/server2/templates/articles/overview.html:116: <img
src="{{static}}/images/overview/flash-app.png"
Delete this image file if it's no longer referenced anywhere.

http://codereview.chromium.org/10914218/diff/4001/chrome/common/extensions/do...
File chrome/common/extensions/docs/server2/templates/intros/ttsEngine.html
(left):

http://codereview.chromium.org/10914218/diff/4001/chrome/common/extensions/do...
chrome/common/extensions/docs/server2/templates/intros/ttsEngine.html:5: an
utterance to be spoken and other parameters when any extension or packaged
Platform apps can use the tts module, this reference can stay.

http://codereview.chromium.org/10914218/diff/4001/chrome/common/extensions/do...
File
chrome/common/extensions/docs/server2/templates/public/extensions/index.html
(left):

http://codereview.chromium.org/10914218/diff/4001/chrome/common/extensions/do...
chrome/common/extensions/docs/server2/templates/public/extensions/index.html:37:
<img src="{{static}}/images/index/html5app.png" width="200" height="160"
align="right" style="margin-top:0px; margin-left:0.5em" alt="A screenshot of a
packaged app that implements a jigsaw puzzle">
Another image that can be removed.

[Aaron Boodman, 2012-09-17 21:18:04]

http://codereview.chromium.org/10914218/diff/4001/chrome/common/extensions/do...
File chrome/common/extensions/docs/server2/templates/articles/autoupdate.html
(right):

http://codereview.chromium.org/10914218/diff/4001/chrome/common/extensions/do...
chrome/common/extensions/docs/server2/templates/articles/autoupdate.html:53: ID
of an extension by going to the Extensions page (<b>chrome://extensions</b>).
On 2012/09/16 04:55:02, Mihai Parparita wrote:
> On 2012/09/16 00:44:35, Aaron Boodman wrote:
> > What did we decide to do about pages like this that describe concepts that
are
> > common to all types of packages?
> 
> Given that this page appears in the apps doc set too
> (http://developer.chrome.com/apps/autoupdate.html), I think the reference to
> packaged apps can stay (it's equally applicable to both legacy and platform
> apps).

Yeah. My question was what we decided to do in the long term.

I keep coming back to the idea that we should factor out the concepts that are
common to all Chrome package types into some separate section, like
developer.chrome.com/packages. It would have its own landing page and would
describe everything that is common between themes, extensions, hosted apps,
legacy packaged apps, and packaged apps, along with any other new types we
introduce over time.

Then /extensions/manifest.html, for example, would just list the keys that are
specific to extensions, and would include a link to /package/manifest.html.

For the specific case of autoupdate, I'm not even sure if we even need an
extensions and apps specific page. We'd just point to the one at
/packages/autoupdate.html.

That said, for now, can we branch on whether this is for extensions and packaged
apps and use the right words, rather than saying 'extension or packaged app'? I
thought we had support for that.

[Aaron Boodman, 2012-09-17 21:23:08]

http://codereview.chromium.org/10914218/diff/4001/chrome/common/extensions/do...
File chrome/common/extensions/docs/server2/templates/articles/autoupdate.html
(left):

http://codereview.chromium.org/10914218/diff/4001/chrome/common/extensions/do...
chrome/common/extensions/docs/server2/templates/articles/autoupdate.html:55:
Hosted apps, however, are not listed on the Extensions page.  You can find the
ID of any
On 2012/09/16 04:55:02, Mihai Parparita wrote:
> Hosted apps are not (publicly) deprecated yet, we shouldn't remove references
to
> them.

Again, this caveat is something that should only be shown for the apps
documentation, I think.

Here's an example:
http://src.chromium.org/viewvc/chrome/trunk/src/chrome/common/extensions/docs...
-- {{?is_apps}}

[mkearney1, 2012-09-17 21:30:16]

http://codereview.chromium.org/10914218/diff/4001/chrome/common/extensions/do...
File chrome/common/extensions/docs/server2/templates/articles/autoupdate.html
(left):

http://codereview.chromium.org/10914218/diff/4001/chrome/common/extensions/do...
chrome/common/extensions/docs/server2/templates/articles/autoupdate.html:55:
Hosted apps, however, are not listed on the Extensions page.  You can find the
ID of any
Yes, we need the apps stuff to be in apps docs-- it's very confusing talking
about extensions, apps, and hosted apps in same breadth. I have a recommendation
for the manifest which I will send in a separate email to you both. It's not
going to answer every cross-over instance though.
On 2012/09/17 21:23:08, Aaron Boodman wrote:
> On 2012/09/16 04:55:02, Mihai Parparita wrote:
> > Hosted apps are not (publicly) deprecated yet, we shouldn't remove
references
> to
> > them.
> 
> Again, this caveat is something that should only be shown for the apps
> documentation, I think.
> 
> Here's an example:
>
http://src.chromium.org/viewvc/chrome/trunk/src/chrome/common/extensions/docs...
> -- {{?is_apps}}

http://codereview.chromium.org/10914218/diff/4001/chrome/common/extensions/do...
File chrome/common/extensions/docs/server2/templates/articles/autoupdate.html
(right):

http://codereview.chromium.org/10914218/diff/4001/chrome/common/extensions/do...
chrome/common/extensions/docs/server2/templates/articles/autoupdate.html:53: ID
of an extension by going to the Extensions page (<b>chrome://extensions</b>).
I have a to-do to investigate if there are any special circumstances for
autoupdating apps. Assuming there are, then it would seem like we should be very
clear about these. If there aren't, then we could just keep this as is.

On 2012/09/16 04:55:02, Mihai Parparita wrote:
> On 2012/09/16 00:44:35, Aaron Boodman wrote:
> > What did we decide to do about pages like this that describe concepts that
are
> > common to all types of packages?
> 
> Given that this page appears in the apps doc set too
> (http://developer.chrome.com/apps/autoupdate.html), I think the reference to
> packaged apps can stay (it's equally applicable to both legacy and platform
> apps).