- This topic has 200 replies, 27 voices, and was last updated May 11-6:42 pm by calciumsodium.
-
Posts
-
PPC
Quick opinion (my time is running out):
I agree with both Brian and Robin – they both prove their points:
– for someone that know how to do it, usually directly editing a text configuration file is the best and fastest way to change a configuration (with some very rare exception)
– unfortunately, operating systems are usually English center – all of IceWM’s preferences variables make sense, particularly if you read the comments… But that implies you can understand the language the variable names and comments is written in… For those persons, using a localized GUI is the best and sometimes, the only way to make a simple edition to a config file…each antiX version provides more and more GUI’s to do the most basic (and some advanced) tasks- that is nice, for ease of use (most people do not use the command line or edit config files manually) and also allows people that do not understand English to easily work with antiX…
Back on track – I have a proposal, that probably Robin already thought about: create a “config file” that stores the current workspace names. When reducing the number of work spaces, no big deal, just save the variable shaving off the latest workspace name to the “preferences” file… If adding a workspace, count the number of work spaces. If a new one is added, check the “config file” if there’s a name stored there that matches the new workspace position (second, third, etc). And use that. If not, just let the new workspace be called a number, and the user has to edit it, if need be.
Personal note: I do not dislike the idea that, if I delete a workspace, I also delete it’s name. If I want to re-add a new workspace, I do so and rename it again, from a number to whatever I want, I do not think it’s “too much” work, and it seems to be the same reasoning that the IceWM Devs used – if you want to trash a work space, it’s because you do not want it… Why waste resources storing the name of an unwated workspace?
I hope my reasoning makes sense. I conside the IceWM devs geniuses- I think it’s the Window Manager that provides the more choices and options, out of the box. The way antiX sets it up, and the costumization it includes (like TIM, and Bob’s scripts to memorize window position and provide a recent files menu entry, the workspace script we are talking about, the script that allows users to select the accent color, etc, etc, it’s almost as feature packed as a D.E.P.
Brian Masinick
Regarding 1378 lines of text in the preferences file, one of the first things I do with my file is to consider which of the resources I actually intend to use, then I generally get rid of the rest. Should I ever want to recover them, they are freely available from the IceWM template directory, which is the place from which I populated my personal copy in the first place.
Secondly, you never want to change the names of the resources; that makes no sense.
All that makes sense is to translate the comments, and I recommend using the template source only to do that. Then when users grab their own copies, it ought to be possible to read the localized comments.
When these comments are translated, then people who speak a variety of languages will be able to read the comments and theoretically understand what it means, assuming they also invest time into learning the software too.
--
Brian MasinickRobin
antiX workspace manager script has been updated to store new workspace count permanently within the icewm preferences file.
Download ver. 0.3 for testing: script file from gitlab.
Setup:
1.) Put the script into the /usr/local/bin folder and make it executable (e.g. sudo chmod …)2.) Add the line
antiX-workspace-manager -s &
to your ~/.desktop-session/startup file. This line is needed since IceWM won’t set the workspace count on startup the way you had it before leaving the former session. This way the antiX-workspace-manager script itself will care for the proper workspace count displayed. If no preset was done before (or no preferences file was found), it will gracefully do nothing when used with the -s command line option.Once the additions are proven to work reliable I’ll send a merge request to anticapitalista.
So please let me know whether you encounter any issues with the updated version.
Possibly we’ll have to move the permanent storage of the workspace count and names to an private config file later on, just as PPC had suggested some postings above, in case the very data is needed for the other window managers as well. This move won’t be difficult then.
Best regards
Robin——————
P.S.:
When these comments are translated, then people who speak a variety of languages will be able to read the comments and theoretically understand what it means,
I didn’t want to suggest all the comment lines in this file should be actually translated to all hundred languages… this would blow up the file, and in the end nobody would be able to use it. (I remind you of the unbelievable chaos on some of recent sales packaging or within product manuals in EU: Each sentence or short paragraphe is repeated in ~20 languages, preceded by the language identifier. Then the next sentence or paragraphe follows, again with ~20 translations… Who does have the patience to search the start of the next sentence in your language?)
Windows is like a submarine. Open a window and serious problems will start.
@Robin- it seems to work on a preliminary test!
Suggestion – make adding the entry to the startup file automaticaly, by adding something like this to the start of the script (adapted from my icewm manager GUI):
text="antiX-workspace-manager -s &" file=$HOME/.desktop-session/startup #Check if string exists in file, if it does not, add it: if cat $file | grep ^antiX-workspace-manager; then echo text found, no need to add it else # echo text not found, add text to file echo ${text} >> $file fimake adding the entry to the startup file automaticaly
Great idea, @PPC. I’ll add this. Many thanks!
Windows is like a submarine. Open a window and serious problems will start.
calciumsodium
Many of us use mpv. There are many scripts to configure mpv.
I am suggesting that antiX23 come with a simple mpv.conf file already present in the ~/.config/mpv folder that contains the minimum to allow any user to use without any difficulty.
The contents of this ~/.config/mpv/mpv.conf file may contain:
#Simple mpv configuration #resolutions include: 240, 360, 480, 720, 1080, 1440, 2160 #Just uncomment (remove #) the following line to get 360p resolution. Modify resolution number if necessary. #ytdl-format=bestvideo[height<=?360][fps<=?30][vcodec!=?vp9]+bestaudio/best[height<=360]I tested this mpv.conf file in antiX19, 21, and 23 b1. Works good.
- This reply was modified 28 minutes ago by calciumsodium. Reason: Tested in antiX19, 21, and 23 b1
- You must be logged in to reply to this topic.
