- This topic has 84 replies, 9 voices, and was last updated May 10-9:57 pm by marcelocripe.
-
Posts
-
PPC
@anticapitalista – I’ll try to fix that tomorrow!!! š
@anticapitalista:
Here you go. It was an easy fix. You can use this version of the script and perform the edits on the text that you already did or simply change line 579 to match the one on the new script (I can’t paste it here, the forum messes it up- it’s the first line of the send_to_desktop function. You should let dave know that the output of that app-select version on his git is faulty, when using the “–select” flag… (I hope you are reading this, Dave- the new app-select version seems perfect, except for the extra text on the output of “app-select –select”! Congratulations!)Edit:
@anticapitalista- if you changed the text, please remember to update what’s up for localization on Transifex, or users will get the changed strings in English…P.
- This reply was modified 2 months, 1 week ago by PPC.
Brian Masinick
@PPC: Tried out your fix, then app-select and both are working.
Thanks for your efforts once again!
--
Brian Masinick
oops
@PPC: Tried out your fix, then app-select and both are working.
Thanks for your efforts once again!
+1 … It is a good idea. (I added some stuffs, for MX and antiX into my .zip file, if you are interested here it is a sample)
- This reply was modified 2 months ago by oops.
- This reply was modified 2 months ago by oops.
Brian Masinick
Hi oops, I tried your tool and it works too, although for me, not all of the modified appearance modifications are visible to me. In some cases the font is changed; in other cases I get little image marks that indicate that the item or component is missing from my system. Not sure what those would be without digging deep into the tool, but if it’s fun and you enjoy it, that’s what this is all about.
--
Brian Masinickoops
Hi Brian … Yes it is funny, and it is a really good idea to play with ~/.icewm/prefoverride file for IceWM. (maybe featherpad is missing for you?)
Edit: the icewm-manager-gui-v53colors-f-no-colors_tof-1.zip (is with the: “send_to_desktop function” corrected above)
- This reply was modified 2 months ago by oops.
- This reply was modified 2 months ago by oops.
This is the reason I do not like to use external apps- they may change their output… Sigh. I fixed both functions that depend on app-select, they now work with the current app-select version that was made available on the repo…
Hi Oops – I like the idea of extending the scripts functionality – now that the basis is done, it’s simply, to follow create new functions and just add them to the script! There are lots of stuff I would like to add to script, but I think most people won’t use them, so I left them out. There’s one setting I was tempted to add – the option to only show the system tray “info squares” about network connections that are being used (i.e.- not showing a square for ethernet and another for wi-fi, if only a kind of connection is being used). I like this option because I just use that square has an interative Network connection icon, that provides much more info than just if I’m connected or not…
It’s the variable “NetStatusShowOnlyRunning” (I hope I did not type that wrong).
I find too confusing, having so many squares, so I have usually one (network) or two (network and CPU/RAM). Those two squares show basically all the important info from Conky…P.
Brian Masinick
This is the reason I do not like to use external apps- they may change their outputā¦ Sigh. I fixed both functions that depend on app-select, they now work with the current app-select version that was made available on the repoā¦
I tried this script and it appears to be working fine; hopefully I do not discover any issues (later) because I replaced the icewm-manager-gui script with today’s update after spot checking several of the features. I think it’s fine, hence my confidence in making the change.
--
Brian Masinickoops
Hi Oops ā I like the idea of extending the scripts functionality ā now that the basis is done, itās simply, to follow create new functions and just add them to the script! …
P.
Hi PPC. right, I have also today created a “Custom config” by default by (sample):
... cat << EOF > $HOME/.icewm/prefoverride ... # -------------------------------------------------------------- # ADDED BY : icewm-manager-gui-v53colors-f-no-colors_tof.sh TaskBarAtTop=0 # 0/1 TimeFormat=%H:%M TaskBarShowClock=1 TaskBarClockLeds=0 TaskBarShowNetStatus=1 TaskBarShowMEMStatus=1 TaskBarShowCPUStatus=1 TaskBarShowMailboxStatus=1 ShowMenuButtonIcon=1 CenterLarge=1 ShowMoveSizeStatus=1 TaskBarAutoHide=0 TaskBarDoubleHeight=0 TaskBarShowShowDesktopButton=1 TaskBarShowWorkspaces=1 TaskBarShowWindowListMenu=0 ... EOF ...I was thinking about adding one more feature to this script, but it’s the opposite of GUI: some launch flags that can be used to launch the more complex functions (that do more than simply changing values on the prefoverride file):
– a switch to run the “Manage IceWM’s startup file” function, the “Add application icon to zzz-icewm desktop” and “select Theme”. The main idea is having modularity – users would be able to create shortcuts to the function they want, from the menu, the toolbar or desktop… But I’ve never really did “flags” right, so if anticapitalista likes this idea, I’m not sure how long it would take to implement thisP.
I have also today created a āCustom configā by default
Nice idea. I thought about it (that would make it unnecessary to click twice on some options to enable them on the first run), but I decided against it in the end because I did not want the script to change any value that the user did not decide to change…
I loved when I found out that a script can create a file with any content we want – that made FT10 grow a lot in functionality!P.
oops
I have also today created a āCustom configā by default
Nice idea. I thought about it (that would make it unnecessary to click twice on some options to enable them on the first run), but I decided against it in the end because I did not want the script to change any value that the user did not decide to changeā¦
I loved when I found out that a script can create a file with any content we want ā that made FT10 grow a lot in functionality!P.
Hello PPC, … I added this by a function too (as option).
IceWM becomes almost a very light DE now š (as option too)
Edit: an easy way to select a wallpapper (backgrounds) with a function too:
cd /usr/share/wallpaper/ ; mywallpaper=$(yad --file --width=800 --height=600 --add-preview --text ="Selecione imagem ou texto:":FL "@kill -USR1 YAD_PID" --file-filter="Image Files (*.jpg *.jpeg)| *.jpg *.JPG *.jpeg *.JPEG *.png *.PNG") ; echo $mywallpaper ; mywallpaper_conf="DesktopBackgroundImage = \""$mywallpaper"\"" ; echo $mywallpaper_conf- This reply was modified 2 months ago by oops.
- This reply was modified 2 months ago by oops.
IceWM becomes almost a very light DE now
From wikipedia:
“In computing, a desktop environment (DE) is an implementation of the desktop metaphor made of a bundle of programs running on top of a computer operating system that share a common graphical user interface (GUI), sometimes described as a graphical shell. The desktop environment was seen mostly on personal computers until the rise of mobile computing. Desktop GUIs help the user to easily access and edit files, while they usually do not provide access to all of the features found in the underlying operating system[…] A desktop environment typically consists of icons, windows, toolbars, folders, wallpapers and desktop widgets. A GUI might also provide drag and drop functionality and other features that make the desktop metaphor more complete. A desktop environment aims to be an intuitive way for the user to interact with the computer using concepts which are similar to those used when interacting with the physical world, such as buttons and windows.”
I think that antiX full, specially running zzz-IceWM, with IceWM as window manager, it’s recent menu and toolbar configurations, our themes, wallpapers, icon packs, zzz as default File (and desktop icon) manager, our helper scripts (that I hope will soon include this GUI script), Control Center and the vastly improved antiX-Updater and Package Installer, is now so feature rich that it can be considered an “antiX Linux zzz-icewm” D.E.
There are only a couple of things most modern DE’s include, that antix does not, out of the box (but that can be installed from Package Installer/Synaptic): system notifications (users can install Dunst to have that feature) and a compositor (users can install Compton, etc, from Synaptic, to have that feature, and then launch it, with their default or edited config file).
Drag and drop functionality does work in many ways, but not the way modern Windows users are used to – to place icons on the toolbar, desktop, or personal menu favorites/pinned apps, you can’t drag and drop, but have to use individual GUI ways to perform those tasks. Adding toolbar icons is, for now, the most intuitive of this actions, since Toolbar Icon Manager now comes on the toolbar itself. I hope some future menu configuration will include the Personal Menu Manager as the Personal Menu initial entry (so that menu can be managed within it self too). Unfortunately, until app-select’s extensions work out of the box, there is no extremely intuitive way to add application icons to the desktop, only the one that is provided in this GUI script…
Just to let folks know how great it would be, having the extensions I’m talking about working in app-select: you will be able to select any app from the list, right click it and then select to add it to the toolbar, to the personal menu or to the desktop – cool, hum?Edit: I saw your edit – I’m a believer on not wasting time reinventing things – yes, a simple and small yad script can change the wallpaper, but our script has many more features than that, allow to select colors, stretch images, select a random image, time wallpaper changes, etc! I can’t beat all that functionality! š
P.
- This reply was modified 2 months ago by PPC.
- This reply was modified 2 months ago by PPC.
Brian Masinick
For what it’s worth, I can remember when I was using graphical window environments before the fully packaged concepts that became known as Desktop Environments. Perhaps the first one of all was either Enlightenment, if you acknowledge it as a complete Desktop Environment, or Xfce, in it’s initial configuration, before it adopted the current Gtk libraries. KDE very closely followed Xfce; they were close enough that it’s difficult to “call” which one was first. GNOME followed about a year later, at least in complete form.
The thing that the early desktop environments offered that was missing from other GUI configurations, at least from my recollection, was drag and drop capability. I note this because I was a UNIX user, developer, and administrator during the time the X Window System was introduced, then the Motif interface was introduced. Motif had a lot of features, but it wasn’t referred to as a Desktop Environment. Shortly thereafter, the Common Desktop Environment (CDE) was created, and another collaboration between AT&T and Sun Microsystems produced UNIX System V combined with Sun “Solaris”; these were the early UNIX desktop environments. Five to eight years later, depending on your counting point, the various Linux and free software alternatives reached common use.
Quoting one source –
https://www.google.com/search?client=firefox-b-1-d&q=What+distinguishes+a+window+manager+from+a+desktop+environment%3F“A desktop environment (DE) usually rides on top of a Window Manager and adds many features, including panels, status bars, drag-and-drop capabilities, and a suite of integrated applications and tools. In fact, user opinions on operating systems are typically based on one thing: the Desktop Environment.”
--
Brian Masinick
- You must be logged in to reply to this topic.
