Porteus

Posted: **25 Mar 2020, 16:29**

Kulle wrote: ↑
25 Mar 2020, 10:01
Wexond web browser,
privacy-focused and extensible.
see here: https://awesomeopensource.com/project/wexond/desktop
Download Appimages:
https://www.electronjs.org/apps/wexond

Does anyone know about https://www.electronjs.org ? Is that a trustworthy source?
On https://awesomeopensource.com/project/wexond/desktop there is not a single hit when searching for Linux…

But the github has AppImages, but for some weird reason only for i386, not for x86-64:
https://github.com/wexond/desktop/relea ... 0.0-beta.3 only has Wexond-4.0.0-beta.3-i386.AppImage
Unless Wexond-4.0.0-beta.3.AppImage is x86-64.

Posted: **26 Mar 2020, 10:01**

Hi Rava,
Wexond-4.0.0-beta.3.AppImage is x86-64 !
But 4.0 is not an electron application.
Version 3.1.0 is electron application.
You can find it also on the website
https://github.com/wexond/desktop/relea ... nightly.10

Posted: **26 Mar 2020, 10:03**

Kulle wrote: ↑
26 Mar 2020, 10:01
But 4.0 is not an electron application.
Version 3.1.0 is electron application.

Was ist das überhaupt mit dem Electron Programm oder nicht Electron Programm?
Gibt es da eine einfache Erklärung?

Posted: **26 Mar 2020, 10:15**

What Are Electron apps?
A brief explanation is here:
https://www.omgubuntu.co.uk/2019/02/best-electron-apps

Posted: **26 Mar 2020, 10:43**

^
Thanks kulle for the heads up. To quote the main pros and cons from that URL:

Benefits of using Electron to build desktop applications include:

Work on all platforms, including Linux
Low barrier to entry — devs with web skills can reuse them
Various OS integrations, including tray applets, media keys, etc
Large community of developers and users
Automatic updates

Downsides to using Electron to build applications include:

Every app comes with the entire runtime
Some apps are poor quality
Large download sizes
High memory usage

So, for me, if available, I would always prefer a native x86-64 Linux program over an Electron one.

Posted: **26 Mar 2020, 13:40**

I tried the Wexond-4.0.0-beta.3.AppImage with Porteus 5.0rc1 and it runs reasonably fast.
Is there a way to copy files out of an AppImage? I want to try to create a regular module out of it, so that there is only the bare needed minimum of libraries added with wexond, which should reduce the memory usage at least a bit.

AppImages are are variant of ISO images, so there should be a way to open these and copy files out just like with a ISO image.

Posted: **28 Mar 2020, 08:05**

Hi Rava.

Try to extract the appimage (whatever-version-blah.appimage --appimage-extract) (See post #15 in this very topic --> Howto: Popular AppImages one click away (Post by M. Eerie #73118))

Then you could recreate the same filesystem structure into a module, but keep in mind not to overwrite unwanted libs already present in the union filesystem. In fact, this is the appimage nature, me thinks. You fire it, you use it, you forget it, then the system remains intact.

I think ncmprhnsbl, would instruct you taking blender as an example.

(Edit)
Also, have a look here, on how to build Blender appimage, starting from the latest stable version of the ( .tar.bz2) package.

AppImages are in fact "automated" squashed filesystems

Cheers!

Posted: **28 Mar 2020, 08:49**

A handy Translatium app

(Electron, however)

Posted: **28 Mar 2020, 08:56**

M. Eerie, thanks for the hands up.

M. Eerie wrote: ↑
28 Mar 2020, 08:05
AppImages are in fact "automated" squashed filesystems

I know, and they are good as they are.

The downsize is of course they often have larger than necessary memory usage, and they often bring more libraries than necessary.

So, when one uses a program on a regular basis or plan doing so (with me and Wexond-4.0.0-beta.3.AppImage) it would make much sense to convert in into a minimal standard x86-64 module for 5.0rc1 Porteus to minimize not only its size, but also its memory usage.
By minimal I mean the same approach I used in the past when sliming down GIMP modules: reducing the size by removing unneeded localizations, removing very large splash image and large paint brushes almost no one ever uses.
By doing so I reduced a GIMP module from approx 45 MB to a mere 12 to 14 MB.

If I would manage a similar reduction with Wexond - I would hope do, but I cannot say, I have to look into the files themselves and especially how many libraries are unneeded because the system already provides adequate ones.

I will create a "x86-64 module" thread when I was successful, but it could take some days, or it also could go quickly. Depends on when I am able to do very important RL stuff, but the Corona shut-down adds insecurities in my plans and not everything that needs to be done is in my sole hands with the current restrictions put on almost everything.

M. Eerie wrote: ↑
28 Mar 2020, 08:49
A handy Translatium app

Sounds handy indeed.

Posted: **28 Mar 2020, 09:04**

M. Eerie wrote: ↑
28 Mar 2020, 08:49
A handy Translatium app

(Electron, however)

How does one download it?
I get redirected to https://snapcraft.io/translatium and there I get the info of

Code: Select all

Install using the command line
$ sudo snap install translatium

Don't have snapd? Get set up for snaps.

Or am I just missing the direct link to the AppImage in the initial URL of https://translatiumapp.com/ ?

update
Seems it is not a mere AppImage but a Snaps thingy, whatever exactly that might be.
https://snapcraft.io/install/translatium/arch#install

Enable snaps on Arch Linux and install Translatium

Snaps are applications packaged with all their dependencies to run on all popular Linux distributions from a single build. They update automatically and roll back gracefully.

Snaps are discoverable and installable from the Snap Store, an app store with an audience of millions.

On https://snapcraft.io/docs/installing-snapd it says

Installing snapd

Snaps can be used on all major Linux distributions, including Ubuntu, Linux Mint, Debian and Fedora.

Seems they not regard Slackware as a major Linux distribution since Slackware is not mentioned even once on that page.

M. Eerie, did you manage to download and run Translatium without "enabling snaps"?

Posted: **28 Mar 2020, 09:20**

Oh, yes! I forgot it.

Appimage is here

Try to execute it like this:
Translatium*.AppImage --no-sandbox

Cheers!

Posted: **28 Mar 2020, 09:46**

Rava wrote: ↑
28 Mar 2020, 08:56
it would make much sense to convert in into a minimal standard x86-64 module for 5.0rc1 Porteus to minimize not only its size, but also its memory usage

Agree. My approach is to maintain their use to a minimum, and only use those that I consider essential and/or well maintained.

Also, I somehow find them a convenient way to not mix things up. (I.e. I don't feel like having something like krita as a module in my XFCE system...)

Cheers!

Posted: **28 Mar 2020, 10:46**

M. Eerie wrote: ↑
28 Mar 2020, 09:20
Appimage is here

Try to execute it like this:
Translatium*.AppImage --no-sandbox

Thanks.
And once again, "Translatium-11.0.1.AppImage" could be the x86-64 version. Why do they omit that info? Same with Wexond.

M. Eerie wrote: ↑
28 Mar 2020, 09:46
(I.e. I don't feel like having something like krita as a module in my XFCE system...)

yeah while krita in itself looks like a nice program, using it in XFCE seems weird. This sentence from wikipedia tells me about the issues:
Krita

The current version of Krita is developed with Qt 5 and KDE Frameworks 5.

KDE Frameworks 5 when running XFCE sound anticlimactic.

Posted: **29 Mar 2020, 17:54**

Kulle, is there a way to get nighly builds of Wexond?
I was searching for the ability to zoom in when browsing and they stated that this is implemented in 4.0.0 beta 4, but I did not find a single URL where such beta could be downloaded. To illustrate the issue: see the screenshot of how a standard non zoomed in page looks like on a full-hd screen.

Here is the direct link of the full HD screenshot without zoom (and some typos

):
https://abload.de/img/wexond-fullhd-withoutxwjpp.png

Posted: **30 Mar 2020, 09:00**

Latest Clipgrab version doesn't work. I've posted a link to the working previous version.

Cheers!