I have created small binary app and I would like it to autoupdate completely automatically, how do I do that ?
Its a huge app and I do not want to download-and-unzip the whole folder like I am doing right now, but I would like to do it binary+diff update.
Thanks.
Google has open-sourced its auto updater for Windows. It's called Omaha and hosted on Google code here.
Related
Even after searching on Google a lot I am not able to find the solution to my problem. I am looking for an alternative to the following button through command line which delete service worker, cache and all other stored data for a specific website or web application.
In Google Chrome Dev Tools --> Goto Application --> Clear storage --> Clear Site Data
Are there any specific file/folder in this location to delete? Or just simply, using a switch with some parameters while opening Chrome can do this?
I already visited this link but it suggests to clear all the data instead for a specific website.
http://stackoverflow.com/questions/12621969/clear-cache-of-browser-by-command-line
Kindly show me the path !!
DevTools functions aren't available through the command line. These are features for developers to test applications with and develop them further. They aren't for automating tasks external to development purposes.
When there is an update available in store. If you click on the app it opens an information page where you can see the changelog for the current version of app. Some developers provide this information some doesn't. I wonder where is this information is written in app code. Is it app manifest file ?
To remind again, i don't mean in store description.
There's no built-in way to store/display a changelog. The changelog you see in some apps is handled manually, like you would do to display any other kind of information.
I am very much impressed by the way this app was build , https://chrome.google.com/webstore/detail/visual-history/emnpecigdjglcgfabfnmlphhgfdifaan
I wonder if SAP Lumira was involved in this application, for the live visualitations to work fine. but i am not sure of how it was developed as an app as it can only export as png files and the data can only be from flat files and hana database. Any help to analyse the nature of this application is appreciated.
I think your question is not stated correctly: it's like asking "how to build visualizations for the web" (in other words, it's too broad and it's not specific to Chrome apps). I think what you want is a way to analyze the source of an app. What you can always do for that is:
After installing the app you're interested in, visit chrome://extensions.
Turn on the Developer mode (a check box in the upper-right corner).
Find the app in the list and note down its app ID.
Go to Chrome settings directory, e.g. ~/.config/google-chrome for Linux - the location will depend on the OS and the Chrome channel that you're using.
Find the app's installation directory, which will look something like <Chrome settings directory from #4>/Profile N/Extensions/<app ID>/<app version>.
You will see the entire app's source there.
Specifically for this app, you can see in the sources that it uses something called JavaScript Graph framework (see /canvas.js) together with D3.js (see /protovis-3.2/).
I'm trying to control the size and position of newly spawned Google Chrome windows via the command line (through C#.)
My command line ends up looking like:
--new-window --window-position=100,100 --window-size=800,600 www.UrlToOpen.com
However, the new window just opens over top of where the last Chrome window was started.
The end result I'm looking for is to be able to start multiple instances of Google Chrome, in separate windows, with a specific location and size. The only way I've been able to do this so far is by specifying that each instance is to have it's own --user-data-dir. However, this is not ideal given how many extensions a user may have installed, and it would not be the best user experience.
Does anyone have any suggestions?
If Chrome is not programmed to allow this, you only have one option.
Create the process and keep the process object.
Use Process.MainWindowHandle to get the newly created window (you might need to use a loop and Process.Refresh, or Process.WaitForInputIdle)
Use the SetWindowPos native function to position the window wherever you want it.
Native hooks could be used to detect creation of the window, but that requires you to create an unmanaged DLL.
I have another idea for you, why not use a chrome extension for handling the positioning.
Background: We had related difficulties. Internal webapp that opens multiple documents in windows, and need to be placed in other monitors.
The javascript does not support this, for security reasons and only a native extension can properly work with the tabs/windows objects.
Therefore, we have created an open source chrome extension for doing exactly that: flexible windows position across multi-monitor setups.
Perhaps more interest to you would be the feature to use predefine templates. The template file is located in any webserver you like and therefore can be easily share across different users.
The chrome extension is called "MultiWindow Positioner" and its complete free. You can get it at the chrome store here
The actual source code you find in github in the project chrome-multiwindow-positioner
Disclaimer: I am the maintainer of the open source (MIT) github project. If there any interesting idea, or comments feel free to share them here.
Is there any way to export you open graph settings, or copy them between apps?
We have domain names that we used to deploy our code to before it goes into production.
http://dev-mysite.blah.com
http://int-mysite.blah.com
http://preprod-mysite.blah.com
http://mysite.blah.com
We have setup facebook apps for each of these domain names. And now I need to configure each of these apps to have Open Graph actions and objects. It seems like a pretty common scenario so what do you do?
No, currently you have to do this manually.
However, you can rationalise it down to two app ids - one for production, and the other for all pre-prod and dev environments. This should cut down the work.