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

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...

remove(unset) property in a property file using ANT PropertyFile task

Using PropertyFile task we can edit the property file during ANT build. Edit property value are very easy and can find here details. http://ant.apache.org/manual/Tasks/propertyfile.html but delete a property or comment a property is the tricky one. If we are using latest ant version (1.8.1 or later), we can delete a property like below. <propertyfile file="my.properties" comment="My properties">   < entry  key="propertykey" operation="del"/> < /propertyfile> but the older version that is before 1.8.1 don't have operation called " del ", if we run the command in lower version ant, we will get a error says undefined operation "del".      there is workaround instead deleting a property we can comment that property using ant's replace command. < replace file="sample.properties">                      < replacefilter token="propertykey" value="#propert...

Secure Coding Guidelines for the Java Programming Language

http://www.oracle.com/technetwork/java/seccodeguide-139067.html Secure Coding Guidelines for the Java Programming Language, Version 3.0 Introduction 0 Fundamentals Guideline 0-1 Prefer to have obviously no flaws than no obvious flaws Guideline 0-2 Design APIs to avoid security concerns Guideline 0-3 Avoid duplication Guideline 0-4 Restrict privileges Guideline 0-5 Establish trust boundaries Guideline 0-6 Contain sensitive data Guideline 0-7 Particular data format and API issues Guideline 0-7a Avoid dynamic SQL Guideline 0-7b XML and HTML generation requires care Guideline 0-7c Restrict XML inclusion Guideline 0-7d Take care interpreting untrusted code 1 Accessibility and Extensibility Guideline 1-1 Limit the accessibility of classes,interfaces, methods, and fields Guideline 1-1a Limit the accessibility of packages Guideline 1-1b Isolate unrelated code Guideline 1-2 Limit the extensibility of classes and methods Guideline 1-3 Understand how a su...