Release 0.3.4 of the RPushbullet package arrived on CRAN today. RPushbullet interfaces the neat Pushbullet service for inter-device messaging, communication, and more. It lets you easily send (programmatic) alerts like the one to the left to your browser, phone, tablet, … – or all at once.
This release contains a contributed PR to better reflect an error code, and adds a mkdocs-material-based documentation site (just like a few other packages of mine). See below for more details.
Changes in version 0.3.4 (2021-03-01)
Return code checking using error code content if it exists (Thomas Shafer in #64).
Enabled GitHub Actions with encrypted JSON file for API access.
Added a package documentation website.
Courtesy of my CRANberries, there is also a diffstat report for this release. More details about the package are at the RPushbullet webpage and the RPushbullet GitHub repo.
If you like this or other open-source work I do, you can now sponsor me at GitHub.
This post by Dirk Eddelbuettel originated on his Thinking inside the box blog. Please report excessive re-aggregation in third-party for-profit settings.
Release 0.3.3 of the RPushbullet package just got to CRAN. RPushbullet offers an interface to the neat Pushbullet service for inter-device messaging, communication, and more. It lets you easily send (programmatic) alerts like the one to the left to your browser, phone, tablet, … – or all at once.
This release further robustifies operations via two contributed PRs. The first by Chan-Yub ensures we set UTF-8 encoding on pushes. The second by Alexandre permits to downgrade from http/2 to http/1.1 which he needed for some operations with a particular backend. I made that PR a bit more general by turning the downgrade into one driven by a new options()
toggle. Special thanks also to Jeroen in help debugging this issue. See below for more details.
Changes in version 0.3.3 (2020-01-18)
Courtesy of CRANberries, there is also a diffstat report for this release. More details about the package are at the RPushbullet webpage and the RPushbullet GitHub repo.
If you like this or other open-source work I do, you can now sponsor me at GitHub. For the first year, GitHub will match your contributions.
This post by Dirk Eddelbuettel originated on his Thinking inside the box blog. Please report excessive re-aggregation in third-party for-profit settings.
A new release 0.3.2 of the RPushbullet package is now on CRAN. RPushbullet is interfacing the neat Pushbullet service for inter-device messaging, communication, and more. It lets you easily send alerts like the one to the left to your browser, phone, tablet, … – or all at once.
This is the first new release in almost 2 1/2 years, and it once again benefits greatly from contributed pull requests by Colin (twice !) and Chan-Yub – see below for details.
Changes in version 0.3.2 (2019-07-21)
The Travis setup was robustified with respect to the token needed to run tests (Dirk in #48)
The configuration file is now readable only by the user (Colin Gillespie in #50)
At startup initialization is now more consistent (Colin Gillespie in #53 fixing #52)
A new function to fetch prior posts was added (Chanyub Park in #54). `
Courtesy of CRANberries, there is also a diffstat report for this release. More details about the package are at the RPushbullet webpage and the RPushbullet GitHub repo.
This post by Dirk Eddelbuettel originated on his Thinking inside the box blog. Please report excessive re-aggregation in third-party for-profit settings.
A new release 0.3.1 of the RPushbullet package, following the recent 0.3.0 release is now on CRAN. RPushbullet is interfacing the neat Pushbullet service for inter-device messaging, communication, and more. It lets you easily send alerts like the one to the to your browser, phone, tablet, ... -- or all at once.
This release owes once again a lot to Seth Wenchel who helped to update and extend a number of features. We fixed one more small bug stemming from the RJSONIO to jsonlite transition, and added a few more helpers. We also enabled Travis testing and with it covr-based coverage analysis using pretty much the same setup I described in this recent blog post.
Changes in version 0.3.1 (2017-02-17)
The target device designation was corrected (#39).
Three new (unexported) helper functions test the validity of the api key, device and channel (Seth in #41).
The
summary
method for thepbDevices
class was corrected (Seth in #43).New helper functions
pbValidateConf
,pbGetUser
,pbGetChannelInfo
were added (Seth in #44 closing #40).New classes
pbUser
andpbChannelInfo
were added (Seth in #44).Travis CI tests (and covr coverage analysis) are now enabled via an encrypted config file (#45).
Courtesy of CRANberries, there is also a diffstat report for this release.
More details about the package are at the RPushbullet webpage and the RPushbullet GitHub repo.
This post by Dirk Eddelbuettel originated on his Thinking inside the box blog. Please report excessive re-aggregation in third-party for-profit settings.
A major new update of the RPushbullet package is now on CRAN. RPushbullet interfacing the neat Pushbullet service for inter-device messaging, communication, and more. It lets you easily send alerts like the one to the to your browser, phone, tablet, ... -- or all at once.
This release owes a lot to Seth Wenchel who was instrumental in driving several key refactorings. We now use the curl package instead of relying on system()
calls to the binary. We also switched from RJSONIO to jsonlite. A new helper function to create the required resourcefile was added, and several other changes were made as detailed below in the extract from the NEWS.Rd
file.
Changes in version 0.3.0 (2017-02-03)
The
curl
binary use was replaced by use of the curl package; several new helper functions added (PRs #30, #36 by Seth closing #29)Use of RJSONIO was replaced by use of jsonlite (PR #32 by Seth closing #31)
A new function
pbSetup
was added to aid creating the resource file (PRs #34, #37 by Seth and Dirk)The package intialization was refactored so that non-loading calls such as
RPushbullet::pbPost(...)
now work (#33 closing #26)The test suite was updated and extended
The Travis script was updated use run.sh
DESCRIPTION, README.md and other files were updated for current
R CMD check
standardsDeprecated parts such as 'type=address' were removed, and the documentation was updated accordingly.
Coverage support was added (in a 'on-demand' setting as automated runs would need a Pushbullet API token)
Courtesy of CRANberries, there is also a diffstat report for this release.
More details about the package are at the RPushbullet webpage and the RPushbullet GitHub repo.
This post by Dirk Eddelbuettel originated on his Thinking inside the box blog. Please report excessive re-aggregation in third-party for-profit settings.
A new releases of the RPushbullet package (interfacing the neat Pushbullet service) arrived on CRAN today.
It brings several weeks of extensions, corrections and cleanups---with key contributions by Mike Birdgeneau and Henrik Bengtsson.
RPushbullet now has support for channels (a reasonably new feature upstream). Setup, initialization and tests all got improved as well. Changes are summarized below based in the extract from the NEWS.Rd
file.
Changes in version 0.2.0 (2015-02-07)
Added support for Pushbullet 'channels' (once again thanks to Mike Birdgeneau for the initial push on this)
Support for pushes was solidified: proper choices of either device, email or channel should work in all cases
S3 methods are now properly exports (thanks to Henrik Bengtsson)
File transfer mode has been improved / corrected (thanks to Mike Birdgeneau)
The regression test suite was expanded and robustified
This NEWS file was added. Better late than never.
Courtesy of CRANberries, there is also a diffstat report for this release.
More details about the package are at the RPushbullet webpage and the RPushbullet GitHub repo.
This post by Dirk Eddelbuettel originated on his Thinking inside the box blog. Please report excessive re-aggregation in third-party for-profit settings.
A minor bugfix release 0.1.1 of the RPushbullet package (interfacing the neat Pushbullet service) landed on CRAN yesterday morning.
It cleans up a small issue related to the ability to transfer files between devices via the Pushbullet service where the ability to select a (non-default) target device has now been restored.
With that, allow me to borrow one excellent use case of RPushbullet from the blog of Karl Broman: how to use RPushbullet for error notifications from R:
options(error = function() {
library(RPushbullet)
pbPost("note", "Error", geterrmessage())
})
This is very clever: should an error occur, you get immediate notification in browser or on your phone. Left as an exercise for the reader is to combine this with the equally excellent rfoaas package (github|cran) to get appropriately colourful error messages...
More details about the package are at the RPushbullet webpage and the RPushbullet GitHub repo.
Courtesy of CRANberries, there is also a diffstat report for this release.
This post by Dirk Eddelbuettel originated on his Thinking inside the box blog. Please report excessive re-aggregation in third-party for-profit settings.
A new release 0.1.0 of the RPushbullet package (interfacing the neat Pushbullet service) landed on CRAN today.
It brings a number of goodies relative to the first release 0.0.2 of a few months ago:
~/.rpushbullet.json
file or optionsrecpients
which can be indices, device names or, if missing entirely, the (new) default deviceemail
is supported as another recipient option in which case the Pushbullet service will send an email to the give addresspbGetDevices()
now returns a proper S3 object with corresponding print()
and summary()
methodsThere is a whole boat load of more wickedness in the Pushbullet API so if anybody feels compelled to add it, fire off pull requests at GitHub.
More details about the package are at the RPushbullet webpage and the RPushbullet GitHub repo.
Courtesy of CRANberries, there is also a diffstat report for this release.
This post by Dirk Eddelbuettel originated on his Thinking inside the box blog. Please report excessive re-aggregation in third-party for-profit settings.
This post by Dirk Eddelbuettel originated on his Thinking inside the box blog. Please report excessive re-aggregation in third-party for-profit settings.