Sushi Browser v0.15.X Introduces Automation Through Macro Functions

Sushi Browser v0.15.X Introduces Automation Through Macro Functions

Kura released v0.15.0 of Sushi Browser on April 22, 2018. This version introduces an automation API that allows the use of macro functions. You can download it from the release pages of the official site or GitHub.

He explains that it is similar to iMacros or Selenium IDE. Specifically, it is implemented by an API that is compatible with Puppeteer, the Headless Chrome Automation API. Puppeteer is a Node library which provides a high-level API to control Chromium or Chrome over the DevTools Protocol, according to the official documentation.

The list of implemented APIs is located on Sushi’s GitHub Wiki. Essentially, you currently can manipulate the browser, webpages, dialogs, frames, and elements by emulating mouse and keyboard actions.

You can access it by clicking the Automation menu from the Top or other internal page or entering chrome://automation into the omnibox.

On the Automation page, there are options to record, play, pause, stop, and export macros, as well as change settings. There’s a sidebar listing the created macros on the left. The main pain shows the commands, their targets, their values, and additional info. Lastly, the log lists information relating to any running macro.

Automation in Sushi Browser
Automation in Sushi Browser, courtesy of Kura52

One of a macro’s purposes is to automate commonly recurring tasks. As a basic example, you could create a macro to open multiple instances of a weather website to check the weather in different cities.

These are the release’s other, welcome features:

  • Defect fixes, including for Bookmarks and Favicon importing
  • Change of the display method dialog(window.alert)
  • YouTube-dl version 2018.04.16
  • Infernojs version 5.0.4

Automation is another nice addition to Sushi Browser. I can see it being used as part of a workflow that has repeating tasks. This perhaps is at least one of Kura’s intentions because Sushi’s extension tools, like the Terminal and Text Editor, make it more like an integrated development environment (IDE). The introduction of macros potentially could streamline those tools’ uses and, therefore, enhance the IDE.

 

Advertisements

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s