Difference between revisions of "Worker - An Introduction"

General verbiage and formatting updates
imported>Handy
imported>Dalto
(General verbiage and formatting updates)
Line 1: Line 1:
__TOC__


<br clear="all"/>
=A Worker in Progress=


[[File: Worker.main.window.png|centre|650px]]
=Overview=


Unfortunately the documentation on Ralf Hoffmann's site (he is the creator of Worker, among other app's) is incomplete and parts at least are somewhat out of date. You basically work much of how Worker is configured out for yourself without having your hand held. That said, the GUI Worker Configuration Manager is pretty self explanatory.


<br clear="all"/>
[[File: worker.top.buttons.png|centre|650px]]
<br clear="all"/>


=Some Background=
[[File: worker.configuration.main.png|centre|650px]]


  Please note: Worker is currently not available in the
<br clear="all"/>
Manjaro repo, so you need to install it with "Yaourt"
The Worker Configuration screen shown above, will give you an inkling of the types of configuration options that are available inside of it. Worker is an extremely capable file manager, that may have been inspired by Jonathan Potter's brilliant Amiga file manager - Directory Opus 4.**. In many ways Worker exceeds the capabilities of DOpus, though it doesn't internally multi-task to quite the same extent that DOpus did.
(or similar) from the Arch User Repository (AUR)[https://aur.archlinux.org/packages/worker/].


Unfortunately the documentation on Ralf Hoffmann's site (he is the creator of Worker, amongst other app's), is incomplete & parts at least are somewhat out of date. You basically work much of how Worker is configured out for yourself without having your hand held. That said, the GUI Worker Configuration Manager is pretty self explanatory.
Ralf has been developing Worker for many years now. You get an introduction to its power on [http://www.boomerangsworld.de/cms/worker/index.html this page]


<br clear="all"/>


[[File: worker.configuration.main.png|centre|650px]]
=Installing Worker=


<br clear="all"/>
Worker is available in the [[Arch_User_Repository|AUR]] as the package {{ic|worker}}.  You can install it in your favorite graphical package manager or by using the command:
The Worker Configuration screen shown above, will give you an inkling of the types of configuration options that are available inside of it.
pamac build worker


Worker is an extremely capable file manager, that I believe was inspired by Jonathan Potter's brilliant Amiga file manager - Directory Opus 4.**. In many ways Worker exceeds the capabilities of DOpus, though it doesn't internally multi-task to quite the same extent that DOpus did.


Ralf has been developing Worker for many years now. You get an introduction to its power on this page: [http://www.boomerangsworld.de/cms/worker/index.html]
=What can this Filemanager called Worker do?=
 
<br clear="all"/>
==What can this Filemanager called Worker do?==


Worker is usually installed with a pretty bare bones button setup. It is then up to the user to make Worker the way that they want Worker to be. This is done by using the Worker Configuration panel. Which is found by hitting the ''C'' - '''Configuration''' in the top left of the Worker window, it is right next to the ''A'' - '''About'''.
Worker is usually installed with a pretty bare bones button setup. It is then up to the user to make Worker the way that they want Worker to be. This is done by using the Worker Configuration panel. Which is found by hitting the ''C'' - '''Configuration''' in the top left of the Worker window, it is right next to the ''A'' - '''About'''.
Line 45: Line 38:
* Combine any number of the aforementioned different types of commands to execute in sequence.
* Combine any number of the aforementioned different types of commands to execute in sequence.


The above barely scratches the surface of what Worker can be configured to do. It is very quick, & has barely any other dependencies than X.org.
The above barely scratches the surface of what Worker can be configured to do. It is very quick and has barely any other dependencies than X.org.


Custom tasks, ranging from the very simple to the extremely complex all fall within the capacity of Worker.  
Custom tasks, ranging from the very simple to the extremely complex all fall within the capacity of Worker.  
Line 55: Line 48:
A good number of screenshots of Worker can be found here: [http://www.boomerangsworld.de/cms/worker/screenshots.html]
A good number of screenshots of Worker can be found here: [http://www.boomerangsworld.de/cms/worker/screenshots.html]


As informative as the screenshots shown at the above link are, they don't show you what can be done colour wise with Worker. Using various colours to suit your eyes/taste & to make Worker more easily used & more practical, as you can use certain colours to good effect (especially where there is danger, as in the case of commands such as DELETE , Reboot , Shutdown & any buttons that you have set up to use Sudo or root privileges one way or another. The first screenshot on this page is a reasonably good example of the use of colours in this way.
As informative as the screenshots shown at the above link are, they don't show you what can be done colour wise with Worker. Using various colours to suit your eyes/taste & to make Worker more easily used & more practical, as you can use certain colours to good effect (especially where there is danger, as in the case of commands such as DELETE , Reboot , Shutdown & any buttons that you have set up to use sudo or root privileges one way or another. The first screenshot on this page is a reasonably good example of the use of colours in this way.


Apart from being able to select the main interface colours as shown in the following image, you can also set the number of colours to be used & also modify the colours to suit you.
Apart from being able to select the main interface colours as shown in the following image, you can also set the number of colours to be used & also modify the colours to suit you.
Line 63: Line 56:


<br clear="all"/>
<br clear="all"/>
When you set Worker up, you can select the font & font size that you would like to use. Choosing fonts is as far as I'm concerned the most pre-historic part of Worker, though as of this edit, the choice of font/&/size is now much better than it was. Fortunately if you do need/want to do it, after you have done it once, there isn't much to do when it comes to resizing fonts thereafter. See this page of the Worker documentation for more on the subject of choosing sizing Worker's fonts: [http://www.boomerangsworld.de/cms/worker/documentation/features/fonts.html]
When you set Worker up, you can select the font & font size that you would like to use. Choosing fonts seems to be the most pre-historic part of Worker, though as of this edit, the choice of font is now much better than it was. Fortunately if you do need/want to do it, after you have done it once, there isn't much to do when it comes to resizing fonts thereafter. See this page of the Worker documentation for more on the subject of choosing sizing Worker's fonts: [http://www.boomerangsworld.de/cms/worker/documentation/features/fonts.html]


<br clear="all"/>
<br clear="all"/>
Line 69: Line 62:


<br clear="all"/>
<br clear="all"/>
==Paths & Bookmarked locations==
 
=Paths & Bookmarked locations=


You can setup custom Path buttons (the Path bank of buttons is the left hand column in the main button bank) you can have as many '''path button banks''' as you want, you cycle through these banks by using the right mouse button (RMB).
You can setup custom Path buttons (the Path bank of buttons is the left hand column in the main button bank) you can have as many '''path button banks''' as you want, you cycle through these banks by using the right mouse button (RMB).
Line 81: Line 75:
<br clear="all"/>
<br clear="all"/>


==Custom Button Configuration==
=Custom Button Configuration=


You also can set up the Worker command button bank(s) to suit you. Choose how many rows of them & how many banks (each bank will have the same number of buttons) as well. I use two banks of buttons, the second bank behind the main bank of 42 buttons, carries buttons for working with many different types of file compression, plus some for audio ripping to various specific formats. You cycle to the next main button bank by hitting the bottom bar in the Worker window - it holds the date/time, free RAM, swap usage - though this is somewhat configurable too.
You also can set up the Worker command button bank(s) to suit you. Choose how many rows of them and how many banks (each bank will have the same number of buttons) as well. You cycle to the next main button bank by hitting the bottom bar in the Worker window - it holds the date/time, free RAM, swap usage - though this is somewhat configurable too.


<br clear="all"/>
<br clear="all"/>
Line 90: Line 84:
<br clear="all"/>
<br clear="all"/>


I use a number of buttons that came as part of my initial Worker install, though most of the buttons in my config have been made by me to suit my needs. When you see a button in a screenshot that has a "dog eared" top right corner, that means that if you use your RMB on it, you will have access to another button option that is hiding underneath. (You could for example have the top button saying '''Edit''' for editing existing files, & the button accessed via the RMB, underneath, saying '''Edit New''' for creating new files.)
It is possible to use the buttons that came as part of the initial Worker install, though it is more common to edit your config to suit your needs. When you see a button in a screenshot that has a "dog eared" top right corner, that means that if you use your RMB on it, you will have access to another button option that is hiding underneath. (You could for example have the top button saying '''Edit''' for editing existing files, & the button accessed via the RMB, underneath, saying '''Edit New''' for creating new files.)


<br clear="all"/>
<br clear="all"/>
Line 104: Line 98:
==Use external applications on files==
==Use external applications on files==


Even though Worker comes with inbuilt text & image viewing abilities, I prefer to set Worker up to use more powerful external programs. So for viewing images, I use Geegie. By associating Geegie with the various types of image file types available (using the Worker Configuration GUI), when I double click on an image file in the Worker display, Geegie displays it for me (you could set different image types to be opened by different image viewing or editing programs if you had the need).
Even though Worker comes with inbuilt text & image viewing abilities, you can also set Worker up to use more powerful external programs. For exmaple, you could use Geegie to view images. By associating Geegie with the various types of image file types available (using the Worker Configuration GUI), when you double click on an image file in the Worker display, Geegie displays it(you could set different image types to be opened by different image viewing or editing programs if you had the need).


<br clear="all"/>
<br clear="all"/>
Line 110: Line 104:


<br clear="all"/>
<br clear="all"/>
I can then view all of the images in that directory by scrolling my mouse wheel, or tell Geegie to go full screen & play a slide show of the images, or do whatever else Geegie will allow me to do with any of the images in that directory.
You can then view all of the images in that directory by scrolling the mouse wheel, or tell Geegie to go full screen and play a slide show of the images, or do whatever else Geegie will allow you to do with any of the images in that directory.


If I '''R'''MB click on the '''F3 - Show Pics''' button (yes you can easily set up function keys too), I will see, '''Edit Pics''' (the RMB buttons are all in different colours than the top LMB accessed buttons). If I have an image file highlighted in Worker, then Pinta (my choice, you can use whatever image editor you wanted to) will open up with the highlighted file ready for me to edit.
If you '''R'''MB click on the '''F3 - Show Pics''' button (yes you can easily set up function keys too), you will see, '''Edit Pics''' (the RMB buttons are all in different colours than the top LMB accessed buttons). If you have an image file highlighted in Worker, then your editor of choice will open up with the highlighted file ready to edit.


This can be done for any type of file on your system that you have a program that you want to use to edit/view it. The '''File Type''' list included in the Worker Configuration GUI (the list is part shown in an the preceding image) is huge, very highly configurable (something like fourteen different custom user options can be set up) plus you can add custom file types quite easily.
This can be done for any type of file on your system that you have a program that you want to use to edit/view it. The '''File Type''' list included in the Worker Configuration GUI (the list is part shown in an the preceding image) is huge, very highly configurable (something like fourteen different custom user options can be set up) plus you can add custom file types quite easily.


For example, I use Evince for .pdf files, Firefox for .html files, Leafpad for .txt & unknown files, I have sudo Leafpad buttons for both creating '''New''' files & of course to work on existing files. So I can select a config file in say the /etc & then use the Worker '''sudo Leafpad''' button on it, which will cause Worker to throw up a terminal window where I have to input my sudo password, then the config file from /etc will be showing in Leafpad & available for me to edit & then save the changes.
For example, you could use Evince for .pdf files, Firefox for .html files and Leafpad for .txt files. It is possible to setup sudo Leafpad buttons for both creating '''New''' files & of course to work on existing files. So you can select a config file in the {{ic|/etc}} and then use the Worker '''sudo Leafpad''' button on it, which will cause Worker to throw up a terminal window where you have to input your sudo password, then the config file from /etc will be showing in Leafpad & available for me to edit & then save the changes.


You can of course use the buttons to call programs that have nothing to do with any of the files in your Worker display. You can run scripts, simple or complex from a button, as normal user or with root privileges, you can combine applications & scripts & most anything else you can come up with to work in sequence. It is up to your imagination &/or needs, to do what you want to do with Worker.
You can of course use the buttons to call programs that have nothing to do with any of the files in your Worker display. You can run scripts, simple or complex from a button, as normal user or with root privileges, you can combine applications & scripts & most anything else you can come up with to work in sequence. It is up to your imagination to do what you want to do with Worker.


<br clear="all"/>
<br clear="all"/>
Line 128: Line 122:
This is all fine & good, unless you are someone who loves working with windows & icons. Under those circumstances you would find Worker to be just exactly what you don't want (you may even think that Worker is pre-historic!).
This is all fine & good, unless you are someone who loves working with windows & icons. Under those circumstances you would find Worker to be just exactly what you don't want (you may even think that Worker is pre-historic!).


For me Worker is perfect.  After all these years of using Worker, I'm still finding things that I can do with Worker to make it suit me even better (that's apart from my swapping an application that I call from Worker to do whatever, for another that has similar capabilities, this happens from time to time).
<br clear="all"/>


<br clear="all"/>
==Backup your worker config & use it elsewhere==
==Backup your ~/.worker/config & use it elsewhere==


You can save your custom ~/.worker/config file ''(it is a '''REALLY''' good idea to keep a backup of this file)''. Apart from saving your configuration from being lost to corruption or whatever, you can transfer your ~/.worker/config file to other installations of Linux (it can run on OS/X too, but it is messy to get it functioning there). You can also edit the ~/.worker/config file directly with a text editor, which can be useful sometimes.
You can save your custom {{ic|~/.worker/config}} file ''(it is a '''REALLY''' good idea to keep a backup of this file)''. Apart from saving your configuration from being lost to corruption or whatever, you can transfer your {{ic|~/.worker/config}} file to other installations of Linux. You can also edit the {{ic|~/.worker/config}} file directly with a text editor, which can be useful sometimes.


<br clear="all"/>
<br clear="all"/>
===Edit the ~/.worker/config file directly===


I'll give an example: I use a 24" 1920x1200 res' display on my main machine. The fonts that I use in Worker range in size from 18 to 24 points. If I transfer my ~/.worker/config file to another system that is using a smaller lower res' monitor, when I then run Worker with my transferred custom config on that machine, the display will be very wrong making Worker pretty unusable. I won't be able to use the Worker Configuration GUI to modify the font size, as the large fonts have made it impossible to do so (can't see/access all the necessary parts of the Worker Configuration GUI).
==Edit the worker config file directly==


So I just go in to the ~/.worker/config file with a text editor, scroll down to the font section & change the sizes. Save it, restart Worker, go into the Worker Configuration GUI (which I can now use) & then adjust/fine tune the config to suit the new machine.
For example, if you transfer worker config file to another system that is using a lower resolution monitor, when you then run Worker with your transferred custom config on that machine, the display will be very wrong making Worker pretty unusable. You may not be access the GUI config  to modify the font size, as the large fonts have made it impossible to do so (can't see/access all the necessary parts of the Worker Configuration GUI).


If you ever strike this problem, this is the part of the ~/.worker/config file you need to edit. The following starts at '''line number 148''' on my machine currently, so that gives you an idea of around where to go looking:
So you can directly edit the {{ic|~/.worker/config}} file with a text editor, scroll down to the font section & change the sizes. Save it, restart Worker, go into the Worker Configuration GUI and adjust/fine tune the config to suit the new machine.
 
If you ever strike this problem, this is the part of the {{ic|~/.worker/config}} file you need to edit.  


  fonts {
  fonts {
Line 159: Line 153:
  }
  }


By looking at the above you can see that it is the '''xfgfonts''' section that is where the large 18 -> 24 size fonts are, so you just make all those numbers suitably smaller & change nothing else, then you can use the Worker Configuration GUI to fine tune your imported settings to suit the new machine.
By looking at the above you can see that it is the '''xfgfonts''' section that is where the large 18 -> 24 size fonts are, so you just make all those numbers suitably smaller, then you can use the Worker Configuration GUI to fine tune your imported settings to suit the new machine.


When I import the setting to another machine, I first install Worker then I just copy my backup ~/.worker/config file into the same location on the new machine. It is the simplest most effective method as it totally replaces the original file.
<br clear="all"/>


<br clear="all"/>


=Making Worker work how you want it to=
=Making Worker work how you want it to=
Line 172: Line 165:


<br clear="all"/>
<br clear="all"/>
==Using an external Text Editor on an existing file==


For the button that I use to edit existing text, I use the following command (bold italic) accessed this way:


'''Worker Configuration > Button Configuration > F4 Leafpad > own command > Configure > program: >''' '''''leafpad {f}'''''
==Options, Options...==
 
For the button that I use to create a new text file, I use the following command (bold italic) accessed this way:


'''Worker Configuration > Button Configuration > F4 Leafpad > own command > Configure > program: >''' '''''leafpad {Rs{Enter Filename:}{}}'''''
The following image shows where you would put either of the above commands plus it has had the '''O''' at the end of the '''program:''' field, selected, so you get to see some of the '''Option flags''' available.
<br clear="all"/>
[[File:worker.button.config.Option.flags.png|centre|650px]]
[[File:worker.button.config.Option.flags.png|centre|650px]]


<br clear="all"/>
==Options, Options...==


There are currently 47 Option flags that can be seen when you hit the '''O''' at the end of the '''program:''' field, where you enter in your own command as seen in the above two examples, it is right before '''leafpad''' .
There are currently 47 Option flags that can be seen when you hit the '''O''' at the end of the '''program:''' field, where you enter in your own command as seen in the above two examples, it is right before '''leafpad''' .


Of those 47 Options, I have the need to use very few of them. When you look at what the options can do, you will see that you can get very sophisticated. Me, I only have comparatively simple requirements of Worker.
Of those 47 Options, you probably won't to need to use all of them. When you look at what the options can do, you will see that you can get very sophisticated but it isn't a requirement.


The previous image shows some of those 47 Option flags in the window on the right hand side of the image. The image also shows some other stuff that was discussed in the previous section or two.  
The previous image shows some of those 47 Option flags in the window on the right hand side of the image.


<br clear="all"/>
<br clear="all"/>


==Inbuilt Commands==
==Built-in Commands==
 
I guess I should also mention that Worker currently also has 61 commands built into it. They are listed when you wish to create a new button (& elsewhere) & choose the '''Add Command''' button. The first in this list of 61 commands is '''own command''' , which is the one I use most often because I'm a power tripper. (wink)


The following screenshot shows some of those 61 commands.
Worker currently also has 61 commands built into it. They are listed when you wish to create a new button (and choose the '''Add Command''' button.  The following screenshot shows some of those 61 commands.


<br clear="all"/>
<br clear="all"/>
Line 212: Line 191:
==Sequencing Commands==
==Sequencing Commands==


You can also have more than one command listed in sequence. Meaning that when setting up a button to do what you want, after the creation of a command, instead of OK'ing out of that window, you add another command, & if needed you keep doing this.
You can also have more than one command listed in sequence. Meaning that when setting up a button to do what you want, after the creation of a command, instead of OK'ing out of that window, you can add another command. You can continue to repeat this as desired.


The above image already has a command (it uses Geegie to show an image that has been selected in one of Worker's file lists), you can add more commands if you need to sequence them for some reason, the commands can be any mixture of both inbuilt commands & external programs.   
The above image already has a command (it uses Geegie to show an image that has been selected in one of Worker's file lists), you can add more commands if you need to sequence them for some reason. The commands can be any mixture of both built-in commands and external programs.   
 
Fairly recently I had the need to do this when I had setup a script that turned dcompmgr on (to stop tearing), then ran VLC & the movie that I'd selected in Worker (before hitting this button of course). The movie would finish & then there was another command that killed dcompmgr. I set this up for both VLC & smplayer.
 
There are also some other buttons on my system that use more than one command in sequence.


<br clear="all"/>
<br clear="all"/>
Line 227: Line 202:


It is very easy to change the applications that we call from inside of Worker, that we use to work on whatever kind of files in whichever way we have chosen. Worker doesn't mind, that is what it is made for (well, a part of what it is made for).
It is very easy to change the applications that we call from inside of Worker, that we use to work on whatever kind of files in whichever way we have chosen. Worker doesn't mind, that is what it is made for (well, a part of what it is made for).
When foundational changes are made to GNU/Linux, the creator of Worker updates Worker (if required) so that Worker will continue to function at least as well as it did before such changes came down to us from the upstream GNU/Linux masters.
In over >10 years of using Worker there has only been a couple of problems that took an upgrade or two (that came in pretty quick succession) to completely overcome. I spoke to Ralph (the creator or Worker) about one of these, he assisted me with a workaround & also had me test a thing or two before he made the next release that solved the problem for everyone else. I can't ask for better than that!


<br clear="all"/>
<br clear="all"/>


=Support=
=See Also=


Following is a link to this page's forum counterpart where you can post any related feedback: [https://forum.manjaro.org/t/wiki-worker-an-introduction-to-the-highly-configurable-file-manager/17667]
You can post any related feedback in the related [https://forum.manjaro.org/t/wiki-worker-an-introduction-to-the-highly-configurable-file-manager/17667 Forum Topic]




[[Category:Contents Page]]
[[Category:Contents Page]]
Anonymous user