Skip to main content

How to create google chrome app

Creating google chrome application is very as creating  a web application.

Create web application using html, javascript & css.
can run in apache server or as file system in browser and test.
when application is ready, create file in root folder "manifest.json"
with below content
{
  "name": "<<application name>>",
  "description": "<<description.........>>",
  "version": "1",
  "app": {
    "launch": {
      "local_path": "<<index html file or the start page of your application>>"
    }
  },
   "icons": { 
"16": "icon16.png",
"48": "icon48.png",
        "128": "icon128.png" }
}

in local_path specify the index page or the first page of your web application.
icons - are used as logos of your chrome app.
16 - will be used as favicon (16X16)
48 - used to show in extensions page (48X48)
128 - used as logo for your app (128X128)

Once ready with above you can test the app in chrome locally.
go to Tools --> Extensions
expand the "Developer Mode"
click on "Load Unpacked Extension..." button.
select your application folder. If your manifest file is correct it will install the app in browser.
Now you can test your app, 
If you are ready to release to Chrome Webstore, 
compress you application folder and make as zip
upload your zipped app.
fill the form and upload your app's screen shots.
that's all you are ready to publish your application.


Happy coding....


Comments

Post a Comment

Popular posts from this blog

Running and debugging jetty maven plugin in Netbeans

Coding with Netbeans will make developer life simple. We don't need search for plugins and install different plugins from different places. Maven projects can opened as directly in Netbeans without any settings. Here is the way to run & debug using maven jetty plugin. We can't add Jetty server as servers in Netbeans. Run project: Right click on project and open the properties. click on "Actions" on left side. On right side there will be list of available actions.  To run jetty can be created a new action or override default "Run Project" Here I am overriding default one, Because I can run the project just by hitting "F6" key click on "Run Project" Enter the value "Execute Goals" as "jetty:run", If you want run as offline add "jetty:run -o" "Active Profiles" can be empty In "set Properties" field we can set like skip test. Here I am skipping test. Done, After setting y...
2 comments
Read more

Disable hibernate Optimistic Lock for specific scenario

Optimistic Lock gives more control on concurrent modification on data. That can be achieved very easily in hibernate using @Version column. But in some cases we may have to avoid concurrency check, example background process. To disable Optimistic lock set OptimisticLockMode as NONE for entity class while hibernate is initiating. We can't remove version column that needs Database changes and ORM changes. In this way we can disable Optimistic Lock by code. implement "org.hibernate.event.Initializable" interface override the below method.     @Override     public void initialize(Configuration cfg) {         Iterator<?> persistentClassIterator = cfg.getClassMappings();         while (persistentClassIterator.hasNext()) {             PersistentClass persistentClass = PersistentClass.class.cast(persistentClassIterato...
Post a Comment
Read more

unlock the static files while jetty is running on windows.

When running a java maven web application  in jetty on windows. All static files are locked and not able edit and save those files while jetty is running. This will eat developers time beacuse each and every change in javascript & css files, jetty have to re-started. Depends on application's dependencies that build will take more than 5minutes. Why jetty is locking the static files? Jetty buffers static content for webapps such as html files, css files, images etc and uses memory mapped files to do this if the NIO connectors are being used. The problem is that on Windows, memory mapping a file causes the file to be locked, so that the file cannot be updated or replaced. This means that effectively you have to stop Jetty in order to update a file Jetty provides a configuration switch in the  webdefault.xml  file for the  DefaultServlet  which enables or disables the use of memory mapped files. If you are running on Windows and are having file locking p...
2 comments
Read more