Package Details: whatsapp-nativefier 0.3.2846-1

Git Clone URL: https://aur.archlinux.org/whatsapp-nativefier.git (read-only)
Package Base: whatsapp-nativefier
Description: WhatsApp desktop built with nativefier (electron)
Upstream URL: https://web.whatsapp.com
Licenses: custom
Submitter: frealgagu
Maintainer: frealgagu
Last Packager: frealgagu
Votes: 49
Popularity: 3.415939
First Submitted: 2018-12-14 22:30
Last Updated: 2019-04-13 13:58

Latest Comments

1 2 3 4 5 6 ... Next › Last »

Freso commented on 2019-05-13 09:55

I’d prefer if frealgagu doesn’t implement this, however, it is easy to clone a PKGBUILD and maintain it locally using git. Just git fetch and git merge when there’s an update on AUR. I do this for a couple of PKGBUILDs where I want to tweak the defaults.

Frikinux commented on 2019-05-13 07:10

@je-vv Yeap! The only way that I believe... it's that the Maintainer edit the PKGBUILD with this option.

je-vv commented on 2019-05-12 23:12

@Frikinux, sorry about that. I didn't remember about back then. Yes, I tried then, and I'm currently using the 1st option. I didn't like them back then because none of them is permanent, for the 1st one, I have to remember to modify the PKGBUILD when upgrading, and for the 2nd one, that json gets overwritten on upgrade as well (it gives the chance to edit it after the upgrade, but you still have to remember to do it).

Is there a way to have a ~/ config file overwriting just that parameter? Or, is there a way to make both options available through a wrapper applying the corresponding configuration? So far it's a configuration in a json file, I'm wondering if it might be an argument instead, that has precedence over the json file.

Any ways, I guess for you "start-in-tray" by default is not an option, right?

Frikinux commented on 2019-05-12 14:04

@je-vv On 2019-02-03 I answered this same question. Yes you can. You can not forget to put the quotes in the argument.

Before installing, modify in PKGBUILD as nativefier option: --tray "start-in-tray" \

Or... Once installed, edit the file:

/opt/whatsapp-nativefier/resources/app/nativefier.json

and change "tray":false for "tray":"start-in-tray" (with quotes)

je-vv commented on 2019-05-12 00:03

BTW, according to nativefier-api-tray, it's possible. However I applied whatsapp-nativefier --tray start-in-tray without any success... But looking at the PKGBUILD, it seems nativefier has to be called with the argument for --tray. Would it be possible to nativefy whatsapp with that?

je-vv commented on 2019-05-11 23:58

Is there a way to start whatsapp-nativefier on tray (iconified on tray), like --start-in-tray? Is it possible to create a wrapper around whatsapp-nativefier to achieve that?

PF71 commented on 2019-04-15 12:50

@frealgagu Thanks for the insight, guess I'll stick to browser WA Web for now until nativefier can support extensions.

EDIT: I've found a workaround! I exported the CSS code of my chosen Stylish styles and then injected it in a new nativefier.

frealgagu commented on 2019-04-15 04:25

@PF71 this package does not run over Chrome, it runs over electron, nativefier encapsulates electron pointing to a specified url. I don't think stylish works over electron, so I guess that what you suggest is not possible.

Please visit https://github.com/jiahaog/nativefier and you will have an idea of how nativiefier works.

PF71 commented on 2019-04-14 23:56

@frealgagu Thanks for creating this package, it makes life easier by not having to open a browser tab for WA Web.

However, I like to use WA Web on Firefox using themes/skins or other CSS customizations from Stylish (https://userstyles.org/). Is there any way a Stylish extension can be used on whatsapp-nativefier like on a browser?

Another question, would you consider making a nativefier that runs on Mozilla's Gecko engine instead of Chrome?

frealgagu commented on 2019-04-13 21:05

@saulocastelo The fix is working. Thanks for your collaboration.