googlechrome / chrome-app-codelab

The goal of this tutorial is to get you building Chrome apps fast. Once you've completed the tutorial, you will have a simple Todo app. We've done our best to capture some of the trickier parts to the development process keeping the sample simple and straightforward.

LICENSE

Copyright 2013 Google Inc. All Rights Reserved.

Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at

http://www.apache.org/licenses/LICENSE-2.0

Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.

Get Ready to Build Chrome Apps!

Chrome apps are written in HTML5, JavaScript, and CSS, just like web apps. But they look and behave more like native apps, and they have super-powerful capabilities, like the ability to interact with network and hardware devices, media tools, and much more.

This repository contains only the code for the Codelab. Please, make sense of this code by following the step-by-step tutorial in the Chrome Apps docs site

chrome-app-codelab's Issues

<!--

Summary

Motivation

Describe alternatives you've considered

Additional context

Originally posted by @NutthaponSmart in atom/atom#21991

Originally posted by @NutthaponSmart in #12

Move to service-worker-mocks 2.0.0

@jeffposnick commented on Wed Jan 30 2019

Following zackargyle/service-workers#109, the 2.0.0 release of service-worker-mock should have all of our forked changes. We can get back on the official release train (and moving forward, contribute directly to the upstream package if we find any issues.)

<!--

Summary

Motivation

Describe alternatives you've considered

Additional context

Originally posted by @NutthaponSmart in atom/atom#21991

img tags for thumbnails in part 2 of lab 8 are defaulting to display: none;

I couldn't get things to work the way they are described in the second part of lab8, so I decided to just run the clone of the code here, and I'm still having an issue with the image thumbnails. If I go to Google Images and drag and drop any image into the app, I still only get a list item that has the uri as text. If I inspect element, and remove the display: none from the img tag, then I only get the PLACEHOLDER_IMAGE.

Can someone help me figure out why I'm seeing this behavior? Thanks!

How GoogleChrome handle multiple tabs without decreasing the performance ?

I have a react application with multiple tabs, in each tab we can add one or multiple highcharts. Once we reach the third tab, the application becomes very slow, took more than 15 seconds to do actions like adding new tab, delete tab, adding or removing highcharts. I'm already using functions of optimisation like memo, useMemo, useCallback, ... So I'm wondering if there is a possibility to unmount or kill the already visited tabs without hiding them in order to save the memory for the active tab. If you have any idea of how I can modify the architecture in order to speed up the application, because, I'm wondering how google chrome for example handle multiple tabs without decreasing the performance.

Change width and height to bounds in chrome.app.window.create object parameter

Link to documentation is not working.

This link in the README is dead: http://developer.chrome.com/trunk/apps/app_codelab.html