Showing posts with label chrome. Show all posts
Showing posts with label chrome. Show all posts
Sunday, June 25, 2017
Developers Can Now Bring Their Android Apps to Chrome OS
Developers Can Now Bring Their Android Apps to Chrome OS
Testing our own app with Google�s �ARC Welder� tool
Last year Google slowly began bringing select Android apps to the Chrome Web Store, allowing a batch of useful mobile apps to run on Chromebooks and other Chrome devices.
Android applications run on Chrome OS through a native client extension called �App Runtime for Chrome�, more commonly known as �ARC�, which runs Android codes at near-native speed through a sandboxed Dalvik VM.
In the months following the announcement of ARC over thirty Android apps have been added to the Web Store, including productivity powerhouse Evernote, PDF mark-up tool iAnnotate and social media fave Vine.
Some Chrome users have grown a little impatient at the slow rate of porting more desirable apps over (think Flipboard, VLC, Skype, etc) despite many lesser known utilities and educational tools wrangling their into the Web Store.
Today that changes.
ARC Opens To All
At its press event Google confirmed it plans to open the ARC programme to all Android developers, not just a select few. This means developers themselves can now dive in to test their Android app in Chrome against the ARC plugin to see what works and make changes, like adding support for keyboard tab keys and mouse input, as needed.
Finally, if all works as intended, they are free to promptly publish it to the Chrome Web Store for users to enjoy.
And there�s you thinking it was all new convertible Chromebooks and low-cost Chromebits announced!
In unlocking the flood gates for Android app developers to bring their wares to Chrome OS Google risks seeing developers shun native Chrome Apps (written in web technologies, running offline, leveraging system hardware APIs, etc) in favour of lazy ports.
Similarly, with a big focus due on Service Workers, its plan to app-ify websites with offline and push messaging features, the need for a bona-fide �Web App� is also lessened.
But whatever mess it makes for a consistent developer story it does, for now, mean more apps for users, more opportunities for developers, and more momentum for the Chrome project.
How To Test Android Apps for Chrome Using ARC Welder
The official Chrome developer documentation details the full recommended way for Android devs to get started with ARC.
In short, developers need three things:
- An APK of the application they wish to test
- A PC, Mac or Chromebook running Chrome v40 or later
- The ARC Welder app from the Chrome Web Store
Installing the ARC Welder app from the Web Store also downloads ARC plugin itself (even on Windows, Mac or Linux). Since the plugin is more than 100MB in size eager mobile devs should only install it when not on a metered, cellular or slow connection.
Once up and running the ARC Welder app simplifies the entire process;
- Open ARC Welder
- Add .apk
- Set configuration values (layout, orientation, etc)
- Test
Google say developers should strive to ensure that an app works well for touch and non-touch Chromebooks, should ideally test on the Chrome OS Stable Channel and cautions that the plugin does not yet support all of Google Play Services yet.
ARC Welder allows .apk files to be quickly exported into a .zip file for easy submission to the Chrome Web Store.
Sunday, May 14, 2017
Disable spell check in Chrome and Firefox
Disable spell check in Chrome and Firefox
![]()
When using any browser, you should notice that these check your spelling as you type, just as Word did at the beginning. To some people this is useful (me), to others it not. For those who don�t like this, here�s how to disable it on Firefox and Chrome.
Firefox
This is simple, go to Options > Advanced.
![]()
Now uncheck the �Check my spelling as I type� and you�re free to make mistakes again.
![]()
Chrome
To deactivate the spell checker, go to a text field (a field where you type), right click > Spell-checker options > Check the spelling of text fields.
![]()
This way, you can make as many mistakes as you want, no one will judge, except maybe the NSA, but they were judging you since that video you watch a while ago.
Sunday, April 30, 2017
Diving into an hacked Chrome extension
Diving into an hacked Chrome extension
This page explain how to make minified JS code readable.
Dive into HTML
The HTML part is usually easy : just need to open the .html files and to look around. However, mine appeared tricky ! The developers, a professional software company wishing to increase its visibility, voluntarily made the code harder to read. My .html is actually almost empty, and filled through js event. So I went on...Javascript
The JS code was itself *minified* : no comments, no spaces, no lines jumps. This practice increase code opacity, making it quite unreadable for humans. Below is an example, I changed some code (ie:myID) so you can guess a bit:function openurl(){chrome.extension.sendRequest({openurl:http://www.mywebsite.com},window.close()}var fill=document.getElementById(myDivID);fill.innerHTML=<font color="#888888"><b>My Bold Sentence:</b></font>;fill.title=Fly over title ;);fill=document.getElementById(mySpanID);fill.innerHTML=<img id="image" src="myIcon.png" >My small sentence.;?After asking a friend for keywords, I googled for a "minifier/unminifier". I loved:
- http://jsbeautifier.org/: website, simple, efficient, online deminifier
- Pretty Beautiful Javascript (Chrome extension): elegant, efficient, on-fly deminifier ! In chrome://settings/extensions need to "Allow access to file URLs" chrome extension, need based on the website script
Grap my ugly code. Copy, paste into, run: unminified. Copy, paste into my text editor (or http://jsfiddle.net/): enlightening. I get the following:
function openurl() {Much nicer ! The code is now far more readable and human-friendly. Prepare a cup of coffee, warm up your eyes and fingers: you will have to code tonight !
chrome.extension.sendRequest({
openurl: http://www.mywebsite.com
},
window.close()
}
var fill = document.getElementById(myDivID);
fill.innerHTML = <font color="#888888"><b>My Bold Sentence:</b></font>;
fill.title = Fly over title ;);
fill = document.getElementById(mySpanID);
fill.innerHTML = <img id="image" src="myIcon.png" >My small sentence.;????

Subscribe to:
Posts (Atom)