Old Forum
https://oldforum.puppylinux.com/viewtop ... 88#p869688
JWMdesk 3.6 addresses many known issues and adds additional features that may be of interest to the Puppy community. See changelog in second post below.
Download JWMdesk-3.6
https://www.smokey01.com/radky/JWMDesk-3.6.pet
JWMdesk-3.6
• Add support for user-defined placement of inter-icon spacers in JWM trays of Woof-CE Pups. Go to the JWMdesk -> Launch tab -> Panel Buttons -> Add Spacer Button.
• Add support for optional tiled or default cascaded placement of desktop windows for JWM >= 2.3.6. If tiled window placement is selected, JWM will attempt to comply on initial placement. If tiled placement fails, desktop windows will revert to cascaded (the default) or centered if specified by the application. Go to the JWMdesk -> Window tab -> Geometry -> Placement.
• Add keybindings to the Aerosnap option for JWM >= 2.3.6. The aerosnap option supports dragging the desktop window to auto-maximize as the cursor contacts the screen edge. The position and action of the cursor at the screen edge will determine the size and position of the maximized window, with a choice of four side configurations (maxright, maxleft, maxtop, maxbottom) plus four corner configurations (maxright-top, maxright-bottom, maxleft-top, maxleft-bottom). To maximize a window to a screen corner (1/4 size), simply drag the window to a screen edge and slide the cursor to the desired screen corner while maintaining cursor contact with the screen edge. To provide sufficient time for cursor interaction with the screen edge, it may be helpful to prolong the delay option up to 2000 ms (2 seconds). Alternatively, by pressing the Alt key and corresponding alphanumeric or directional arrow key, the new JWMdesk keybindings support similar functionality with seven possible configurations of the maximized window (Alt-Right:maxright, Alt-Left:maxleft, Alt-Up:maxtop, Alt-Down:maxbottom, Alt-m:maximize, Alt-x:maxhorizontal, Alt-y:maxvertical). Press the selected Alt-key combination once to switch to the maximized window, and press again to toggle back to the original window size and position. Go to JWMdesk -> Window tab -> Snap -> Aero Snap.
• Add new Theme Manager toggle button to switch between GTK2 and GTK3 color selectors in recent Woof-CE GTK3 Pups. The legacy GTK2 color selector provides a pipette (eyedropper) which facilitates the acquisition and transfer of desktop colors to your new JWM theme.
• Add two new Theme Manager style options for user-defined folder colors (Buntu and Buntu Light).
• Add new JWM Theme Builder GUI with options to create new themes or edit existing themes (Note: this option supports the XML theme format of modern JWM >= 2.3.6). Base, Light and Dark theme templates are available to edit/create/save new themes, or you can explore the Edit options to select and edit existing themes (use the Theme Selector button or simply drag-and-drop a theme to the Builder GUI, then click the Edit button). When editing is finished, enter or confirm the preferred theme name and click the Save button to archive your new creation in the default JWM theme directory. Finally, click the Preview button to view and optionally apply the new theme to the current desktop. Go to the JWM Theme Manager -> JWM Theme Builder.
• Add new Window Title Bar GUI with options to change the font attributes, button theme, button order, button position, text position, menu icon visibility, and window shading by title bar scrolling. Go to the JWM Theme Manager -> JWM Title Bar Manager. Note: the Title Bar GUI requires JWM >= 2.4.
• Adjust the Theme Manager title-bar button option to include custom button icons and colors which emulate the appearance available in mainstream Linux distributions. Go to the JWM Theme Manager -> JWM Title Bar Manager -> Icon Theme -> Custom Button Icons and Custom Button Color.
• Adjust the Theme Manager GUI for improved widget visibility and accessibility.
• Adjust the GTK Theme Switcher to support GTK4 theming.
• Adjust JWMdesk modules for compatibility with recent changes in Woof-CE.
JWMDesk-3.5.4
• Add 'Accent' folder style to the JWMdesk Theme Manager (folder color option similar to Ubuntu accent colors).
• Adjust GUI appearance of gradient svg images generated by the legacy JWM theme switcher. Specifically, the GUI of the legacy theme switcher now accurately depicts the title-bar graphics of JWM themes built with two-color gradients.
• Adjust Icon Layout module of JWMdesk for compatibility with recent changes in EasyOS (abbreviate desk icon labels). Current iterations of EasyOS do not support the Traditional, Bare or 'Trash icon only' puppypin options of Puppy Linux.
• Adjust Display Control module of JWMdesk to automatically disable modulation of screen tint and brightness when the alternate Screen Saver GUI is selected (Display Control -> Screen Saver tab -> Preferences -> Screen Saver GUI). Specifically, selecting the Screen Saver GUI will (1) remove all tint and brightness options from the GUI and (2) remove current persistence settings for tint and brightness and (3) immediately reset screen luminosity to neutral baseline levels (6500K tint and 100% brightness). Subsequently, the Screen Control button of JWMdesk will call the Screen Saver GUI and there will be no conflict with alternate 'redshift' or 'gamma' utilities.
Note: Redshift utilities such as the Display Control module of JWMdesk and other Linux Night Light filters (also known as Blue Light filters or Color Temperature filters) are not designed for monitor calibration or granular control of the rgb spectrum as required for photographic or video color accuracy. Rather, the redshift utilities typically provide screen viewing comfort by modulating the relative proportion of red, green and blue colors in the visible light spectrum. The screen colors are adjusted in accordance with predefined rgb gradient values as demonstrated here: viewtopic.php?p=32277#p32277
Since night light (redshift) utilities alter the screen color temperature by adjusting rgb gamma values, using more than one such utility will override gamma values previously set by another application. This is particularly true for applications that automatically recall prior settings after rebooting. Consequently, the concurrent use of multiple color temperature filters is not recommended.
If you prefer an alternate redshift utility or require granular (independent) control of each rgb value, please disable the Display Control module of JWMdesk (as described above) and use your preferred method for modulating screen luminosity.
JWMDesk-3.5.2
• Adjust GUI widgets of the JWMdesk Theme Manager (add option for JWM title bar buttons).
• Adjust default settings of the (optional) built-in GTK Theme Switcher of JWMdesk (ptheme_gtk). Specifically, disable GTK3 overlay scrolling so that scrollbars are always visible. Please note, some GTK3 applications ignore this setting and only support the default overlay scrollbars.
• Bugfix: compatibility updates for recent changes in Woof-CE (puplock, Xwayland, and theming of the non-Rox desktop).
• Bugfix: compatibility updates for recent changes in EasyOS (uimanager and desk icon placement).
• Critical bugfix: intermittent failed start of the JWMdesk GUI if 'jwm -restart' is called while JWMdesk is loading.
JWMDesk-3.5.1
• Add small (4K) sct utility to the base Display Control module of JWMdesk (for optional modulation of screen color temperature and brightness). Separate download of sct is no longer required.
• Add two new options for title bar buttons (Buntu-dark and Buntu-light).
• Bugfix: critical compatibility update for recent changes in Woof-CE (logout and suspend functions).
• Bugfix: critical compatibility update for recent changes in EasyOS (auto-adjust size of main jwm tray).
JWMDesk-3.5
• Adjust compatibility with the Ptheme desktop manager (if installed and active). In this scenario, JWMdesk automatically adjusts the jwm configuration files for compatibility. If you wish to switch back to the Ptheme desktop manager, simply go to JWMdesk -> Options tab -> Desk Manager and follow the dialogs.
• Adjust compatibility with recent changes in Woof-CE. Specifically, JWMdesk 3.5 supports legacy and modern Woof-CE Pups built with the conventional Xorg desktop environment and is fully compatible with the new hybrid Xwayland environment of Vanilla Dpup 9.0.x and 9.1.x. However, JWMdesk does not support the pure Wayland environment of Vanilla Dpup 10.x which is built without ROX-Filer, JWM or any remnant of the legacy X Window System.
• Adjust dynamic submenus (Drives and Recently used) of the Places accessory menu for compatibility with non-Rox desktops.
• Adjust compatibility with LxPup when the user switches from LXDE to the JWM desktop.
• Adjust xkeyboard wrapper to support cellwriter and xvkbd virtual keyboards (if installed). See Utilities (accessory) menu -> KeyBoard.
• Adjust Desktop Icon Setup for improved user control of desk icon placement. Go to JWMdesk -> Desktop tab.
• Add option to place virtual desktops on left or right side of the main tray. Go to JWMdesk -> Tray tab.
• Add scaling option to auto-reduce main tray to 75% of the screen dimension. Go to JWMdesk -> Tray tab.
• Add search option to quickly find available applications for tray launcher buttons. Go to JWMdesk -> Launch tab -> Available Applications.
• Add full support for the new JWM (non-Xorg and non-ROX) desktop interface of Woof-CE. For example: Vanilla dpup/upup configured with the Xwayland and PCManFM desktop.
• Add full support for the new JWM (non-ROX) desktop interface of EasyOS. Requirement: EasyOs >= 3.4.2 (rollback to prior versions not supported)
• Add color selector to the Theme Manager 'Dark colors' option. This applies the selected dark color to the menu, tray, and inactive window borders. The default dark color is gray20 (#333333) but you can apply any JWM color to match the current desktop theme.
• Add Theme Manager tray transparency option. If the background option is enabled and a screen compositor is active (such as Compton or Picom), the theme manager will automatically apply partial transparency (85% opacity) to the JWM tray. However, even if a compositor is not present, you can select the transparent tray option to automatically apply the selected color to both background and tray, simulating 100% panel transparency.
• Add gradient style to the Theme Manager background option (in addition to solid colors). The background option defaults to a solid-color wallpaper but you can enable the gradient option which applies linear (horizontal, oblique, vertical) or radial gradients based on the current JWM theme color or any user-selected custom color. For granular control of the background option please go to Preferences and choose the preferred wallpaper selector, background text color, and background gradient options.
• Remove duplicative gtk-theme and icon-theme buttons from the Theme Manager module (these legacy options are already available on the Desktop tab of JWMdesk). The Theme Manager still provides legacy jwm-theme and background-theme buttons for quick access to traditional applications which, of course, overwrite the current customized settings of the Theme Manager.
• Update the Theme Manager interface for improved access to all user options.
• Update the Theme Manager legacy wallpaper option which now supports the Puppy default (Nathan) Wallpaper Setter plus the added convenience and simplicity of the optional Qwallpaper.
• Update the legacy JWM theme switcher interface (remove dependence on outdated GUI pixmaps).
JWMDesk-3.3
• Adjust the GUI and color code of the Theme Manager module for improved coordination of GTK and JWM desktop themes. (thanks 666philb)
• Adjust the GTK Theme module for improved management of gtk themes in Pups that do not call lxappearance (GTK2/GTK3) or gtk-chtheme (GTK2).
• Adjust the Time Wizard module for theming consistent with other modules of Puppy Setup.
• Adjust the Window Buttons module for improved management of custom title bar buttons.
• Adjust the filemanager option of the Icon Layout module.
• Adjust the activation delay of the Screen Saver module for improved compatibility with other xset-based screensavers.
• Adjust the pinstall script for ubuntupup64 >= 9.0 (in this case, PMaterial theme icons replace JWMdesk's default button icons).
JWMDesk-3.2
• Adjust GUI widgets of JWMdesk constituent applications for more consistent theming.
• Adjust flat, gradient and dark theme options of the JWMdesk Theme Manager for improved contrast and visibility of selected items in the menu and tray.
• Add simple color tool (color picker) with convenient copy-to-clipboard option. Available as a button option in the JWMdesk Theme Manager (GTK3 Pups only) and in the Utilities accessory menu of the JWM tray (GTK2 and GTK3 Pups).
• Add options for icon size (large or small) and separate color selectors for the cone and sound waves of the JWM tray speaker icon. Supports legacy ALSA tray applets (retrovol and pnmixer) and modern PulseAudio programs (pasystray and pa-applet).
• Adust compatibility with recent changes in Woof-CE code.
• Adust compatibility with recent variants of ubuntuPup64.
JWMDesk-3.1
• Add 'Window only' checkbox option to the Theme Manager module. This option adds the selected color to the window border and provides a contrasting dark theme for the JWM menu and tray. (thanks Recobayu)
• Add 'color selector' to the Window Buttons module for customizing the color of title bar buttons.
• Add configurable 'custom' preset option for launch buttons of the accessory tray.
• Adjust default 'Run' option of the Places accessory menu.
• Adjust tray management in gtk2 and gtk3 Puppy Linux. (thanks TerryH)
• Adjust desktop theming and GTK theme switching in the jwm_config desktop environment. (thanks TerryH)
JWMDesk-3.0
• Add support for three (optional) preset accessory menus of the main JWM tray (Places and System menus on the left side of the tray, and the Utilities menu on the right side). See Options tab and Note-1.
• Add support for user-configured (manually added) accessory menus on the left side of the main JWM tray. See Note-1.
• Add JWM-specific version of the 'Puppy Log Out' utility. See Utilities menu of main tray --> Log out, and Note-2.
• Add small utility to adjust screen tint and brightness. See Desktop tab and the Utilities menu of main tray --> Display control, and Note-3.
• Add support for 666philb's variants of ubuntupup64 >= fossapup64 (DISTRO_VERSION >= 9). See Options tab and Note-4.
• Add new JWM theme manager based on Recobayu's jwm theme color changer (thanks Recobayu). See Desktop tab -> JWM Theme, and Note-5.
• Add quick-button view of the current status of desktop theming. See Desktop tab.
• Add adjustable icon-label and edge-gap parameters to the 'Icon Layout Option' of JWMdesk to better manage the desktop icon burden and to facilitate placement of trays at the top of the screen. See Desktop tab --> Icon Layout, and Note-6.
• Add support for padding (spacing) of the main tray widgets. See Tray tab.
• Add day, date and year options to the built-in clock-setting module (JWMclock). However, the clock-setting option defers to PupClockset if installed. See Tray tab.
• Adjust compatibility with GTK3 and Xwayland iterations of Puppy Linux currently evolving in Woof-CE. See Note-7.
• Adjust compatibility with the jwm_config (ptheme) desktop environment. See Note-8.
• Bugfix: overwriting of user's customized RootMenu parameters in /etc/xdg/templates/_root_.jwmrc.
• Bugfix: overwriting of user's customized tray menus manually added to /root/.jwmrc-tray or /root/.jwm/jwmrc-tray.
• Bugfix: overwriting of user's customized virtual-desktop backgrounds added to /root/.jwm/jwmrc-personal. See Note-9.
• Bugfix: on first run, failed positioning of accessory tray (launch bar) to screen side opposite the main tray.
• Bugfix: failed creation of default accessory tray (launch bar) if the 'Apply' button is clicked before selecting the option for Preset Buttons.
• Bugfix: failed addition of launch buttons to the JWM tray when the path of the application icon is not stipulated in the corresponding .desktop file.
• Bugfix: failed addition of launch buttons to the JWM tray in some scenarios when the tray contains no current launch buttons.
• Bugfix: failed detection of GTK3 themes in the Current Themes report.
• Bugfix: inconsistent positioning of desktop icons by the Minimal-essential and Trash-only options available through the Icon Layout button of JWMdesk. See Note-10.
• Bugfix: failed access to 'Online Help' in the Help dialog.
Note-1: The Places, System and Utilities menus of JWMdesk emulate the traditional menu structure of the classic gnome desktop while providing easy access to common applications and accessories that many use frequently during the course of a typical computing session. Go to the Options tab to enable/disable the new accessory menus.
The preset accessory menus are configured to coexist with the user's customized (manually added) accessory menus (if present and properly configured). JWMdesk will first add the preconfigured Places and System menus to the left side of the main tray, followed by the user's manually configured menus. A single accessory menu is supported on the right side of the main tray, and this location is currently assigned to the preconfigured Utilities menu (with clickable tray icon).
The JWMdesk preset menus utilize onroot values of x, y and z which are supported in JWM vgit >= 1092 and JWM official releases >= 2.3.0, but are not supported in earlier versions of JWM (in which case, JWMdesk will hide this option). Consequently, the preset accessory menus should not conflict with the user's manually configured menus which typically use numerical onroot values (0-9). Please keep in mind, the user must manage (add, delete, edit) any manually generated menus that are not created or directly managed by JWMdesk.
Note-2: The last button of the Log-out interface defaults to the Screen Lock option. However, an optional Suspend (suspend-to-RAM) button is available for those who wish to conserve laptop battery power when idle. Unfortunately, not all systems support the Suspend option (for example: Pups with faulty video drivers or incompatible kernels). Suspend works well for me with most 32-bit and 64-bit Pups, but not with current 64-bit Pups built with Ubuntu binary packages. If your distro and/or hardware will support the Suspend option, please go to the Preferences option of the Utilities accessory menu where you can enable or disable the Suspend button of the Log-out GUI.
Note-3: Display Control calls xrandr or (optionally) an enhanced version of sct to adjust the screen color temperature and brightness. If sct is installed, a toggle button is available to switch between the xrandr and sct interfaces, each providing unique advantages for improved screen viewing. For example, the xrandr interface provides greater contrast and color saturation at lower temperatures, while the sct interface provides the sepia effect of color warmth reminiscent of vintage photographs. Additionally, for multi-monitor configurations, the xrandr interface supports independent settings for each screen while the sct interface iterates identical settings for all screens simultaneously. Importantly, xrandr and sct do not change the actual backlight intensity, rather the observed screen appearance represents software modulation of available light.
If you choose to install the sct utility, there are important caveats. The original release of the sct utility by Ted Unangst has a singular function - to change the screen color temperature via the RandR X window system protocol. However, Display Control requires an updated version of sct (with code from the mgudemann, faf0 and mfachal forks). Specifically, this updated version of sct adds (1) screen brightness control and (2) multi-monitor support and (3) baseline adjustment of color temperatures in smooth 100K increments rather than the original coarse 500K increments. The updated 32-bit and 64-bit sct binaries for Display Control are available in the first post above.
In the xrandr and sct interfaces of Display Control, the selected color temperature values in Degrees Kelvin and the corresponding light intensity values are accessible in hscale slider widgets which are easily navigated. If you prefer single-click profiles to quickly adjust the screen tint and brightness please go to the Presets Option where you will find multiple preconfigured viewing profiles plus a custom option for your favorite profile. Since xrandr does not directly modify the tint of pure white backgrounds, the lower preset values for brightness are particularly useful at night to reduce the screen intensity of application windows that may appear bright white when viewed in some GTK themes.
Alternatively, Display Control provides a useful laptop hardware option (Screen Backlight) to change brightness of the primary screen through /sys/class/backlight (not for external screens in a multi-monitor configuration). When launched, Display Control checks the contents of /sys/class/backlight and if supporting files are not found the Screen Backlight option is not included in the GUI. The default script (brightness-set) which mediates backlight brightness control is courtesy of James Budiono of Fatdog Linux. If you require an alternate mediator of backlight control, the optional and versatile brightnessctl utility (if installed) will integrate seamlessly with Display Control. Please be aware, the new non-Xorg Xwayland Pups of Woof-CE do not support modulation of screen color temperature via xrandr or sct. Consequently, in this scenario the Display Control interface will exclude those options but will provide the option to control (laptop) backlight intensity.
The software (Tint and Brightness) and hardware (Screen Backlight) options can be used simultaneously but many users will choose one option and set the other option to a baseline neutral state (6500K and 100% for color temperature and brightness respectively).
One final consideration: The legacy SS-Control utility (Screen Saver) is included as tab 2 of Display Control with an updated interface and expanded range for the delay/timeout interval (1-300 minutes in 1 minute increments). The Screen Saver tab provides an option in Preferences which allows the user to choose either the standard Display Control GUI or a cutdown GUI that shows only the screen saver interface. The later option may be of interest to those who require nothing more than the screen saver interface or perhaps have no interest in the Display Control module and prefer an alternate application to control screen temperature and brightness (such as the popular Redshift utility).
Note-4: With the advent of Fossapup64, 666philb added four new button options to the Desktop tab of JWMdesk (Dark Mode, Window Effects, Conky Settings, and Notifications). In JWMdesk 3.0 these options are further consolidated in a simple format that will be easily modified or updated in ubuntupup64 variants >= Fossapup64 (caveat: the new buttons are available only for DISTRO_VERSION >= 9).
For those who choose to install this new release in Fossapup64, please go to the distro's quickpet option and install all current updates before installing JWMdesk-3.0. This is necessary since the quickpet option currently contains older JWMdesk files that must be overwritten by JWMdesk 3.0. The pinstall script will automatically retain 666philb's unique icons for the graphical interface. Go to the Options tab to enable the Extra Theme Buttons for the Desktop tab.
Note-5: Based on the jwm theme color changer (jcc) of Recobayu, the JWMdesk Theme Manager supports the modern XML syntax implemented in JWM >= 2.3.0 but does not support theming in earlier (legacy) versions of JWM, in which case JWMdesk will hide this option. The color hex values depicted in button tooltips for Recent colors and Favorite colors may differ slightly from values produced by conventional color selectors but the colors are visually identical as implemented.
The theme manager defaults to a small window which supports essential theming functions. However, if you prefer, a toggle button (upper left corner) will expand the window for quick access to an array of favorite colors. From either window you can quickly switch the current JWM theme color for the desktop menu, tray, and window borders.
Although this application is primarily for managing JWM theme colors, the graphical interface also provides options for more robust desktop theming. Specifically, you can enable checkbox options that will (1) create a new desktop background and (2) create a new RoxFiler folder, both of which will match the color scheme of the new JWM theme.
By design, the primary color selected for the JWM theme is automatically adjusted to provide differential hue and contrast for the foreground and background colors of the desktop menu, tray, windows, wallpaper and folders. This will provide a unified color scheme for the entire desktop. However, if you wish to further customize desktop theming there are separate color selectors for the background and folder options. Unchecking the background option will maintain the current desktop background and unchecking the folder option will revert the folder to the original color. Of course, at the bottom of the graphical interface you will find buttons for quick access to standard (legacy) applications that help you customize the desktop appearance. Consequently, available theming options for the JWM desktop are virtually unlimited.
Importantly, in GTK3 variants of Puppy Linux the Theme Manager provides the default GTK3 color selector plus two GTK2 color selectors to replace and/or supplement the limited and deprecated functionality of the GTK3 version. Specifically, in the GTK3 environment you will find a dedicated 'Legacy' color selector which functions (optionally) as a replacement for the default GTK3 color selector, plus a basic 'Xcolor' selector which functions as a simple color picker similar to the gcolor2 utility for copy-and-paste of desktop colors.
The wallpaper option provides a user-editable entry for creating the background label (banner) with a choice of text formats (no label, flat, outline, shadow and embossed) in multiple sizes (48-152 px). The label option defaults to the name of the current Puppy distro but you can enter any text to create a personalized banner. A toggle button (lower left) provides a convenient portal to additional font options.
The folder option provides a selection of RoxFiler folder styles which may be assigned the color of your choice. This includes folder icons for the Legacy, Modern, PMaterial, Puppy Flat and Puppy Standard icon themes. The color of the 'Adwaita' folder style (if installed) is fixed as defined by the built-in folder icon in PNG format, while the 'Desktop' folder style is also fixed as defined by the current desktop icon theme (/etc/desktop_icon_theme). Please be aware, after the current folder color is changed RoxFiler may require a refresh before the new folder color is visible. You can do this easily in RoxFiler by pressing the F5 key or by clicking the Rescan button in the top menu bar. To restore the original color of the selected folder style, simply uncheck the folder checkbox and click the Apply button (lower left).
One final caveat: The screen will 'blink' twice when the desktop theme changes - first when ROX restarts the desktop and second when JWM restarts. Generally, this process is relatively quick. However, in some scenarios recent vigit releases of JWM v2.4 may impose a 5-second delay before a specific user interaction with JWM is completed (such as jwm -restart which loads a new instance of jwm and resets the primary and accessory menus). Likely this delay is due to an intermittent trigger of the 5000 ms (5 sec) menu-command-timeout originally introduced in JWM vgit-1659 (an early prelude to v2.4). When this delay occurs the desktop may appear unresponsive but after the 5-second delay JWM should restart and the tray will reset. Please allow sufficient time for JWM to restart before you resume interacting with the desktop. At any time, you can close the Theme Manager by clicking the Close button in the window title bar or by pressing the keyboard ESC key. Edit: Initial evaluation suggests the timeout bug is resolved in JWM 2.4.2 (released 28 May 2022).
Note-6: For users who prefer placement of JWM trays at the top of the screen, the new edge-gap option of JWMdesk will allow easy adjustment of the space above the desktop icons to accommodate such trays. Generally, selecting an edge-gap of at least 50px greater than the tray short-dimension will provide a good starting point for comfortable viewing. For example, set the edge-gap to 80 for a tray with a short dimension of 30px. Additionally, the Icon Layout button provides a new option to enable/disable the descriptive label of desktop icons set by the Traditional, Minimal and Trash profiles. Removing icon labels may be of interest to those who prefer a simple intuitive desktop. Lastly, a new button added to the Drive Icon tab provides quick access to the Puppy Event Manager where you can change the placement and spacing of drive and partition icons.
Note-7: Puppy development in Woof-CE is moving from the current GTK2 and Xorg base to the modern GTK3 and Xwayland platforms which will impact the functionality and theming of many long-standing Puppy applications. Consequently, the many components of JWMdesk-3.0 are now modified to support current versions of Puppy Linux that are based on GTK2 and Xorg, as well as future iterations based on GTK3 and Xwayland.
Although many GTK3 widgets can be adjusted to approximate the appearance and functionality of GTK2 widgets familiar to Puppy users for more than a decade, there are other GTK functions in the GTK3 environment that are now deprecated and no longer supported, or modified in a way that we may find counter-productive. For example, the basic GTK3 color selector no longer supports a standard pipette/eyedropper for sampling colors of the desktop, and the mouse scroll wheel no longer interacts with notebook tabs. That said, the Woof-CE team is working diligently to provide a useable GTK3 base for Puppy Linux.
Note-8: JWMdesk is generally compatible with ptheme of the standard Woof-CE JWM desktop environment. However, quickly alternating between JWMdesk and ptheme to manage the JWM desktop is not recommended. If you wish to switch the JWM desktop managers during the current computing session, please exit the active desktop manager before launching the other.
Note-9: JWMdesk-3.0 supports configurable virtual-desktop backgrounds for the JWM tray pager. To include this optional functionality in Puppy Linux the user must edit /root/.jwm/jwmrc-personal and add the appropriate (customized) XML code. For more information, please see MochiMoppel's tutorial: https://oldforum.puppylinux.com/viewtop ... 34#p785738
Note-10: The standard fixPuppyPin utility of Puppy Linux finds the x-coordinates of the Xlock icon and moves that icon (and all icons with identical x-coordinates) to the right side of the screen. However, the Xlock icon is not included in the original Minimal-essential or Trash-only options of the Icon Layout application. Consequently, JWMdesk-3.0 adjusts the RIGHTX variable of fixPuppyPin to include the position of the Trash icon as a determining factor for the right border of desk icons, and the default position of the Trash icon is now along the right side of the screen. Additionally, support is now provided for the unique PuppyPin of EasyOS.
Display Control and Screen Tint
Based on raw data from redshift's colorramp.c, the graph below plots screen color temperature (degrees Kelvin) versus RGB (red/green/blue) gamma values.
At the baseline color temperature of 6500K (daylight) the red/green/blue components of light demonstrate equal gamma values (gamma = 1.0). As the color temperature decreases the green and blue gamma values also decrease (particularly blue) but the red gamma value remains constant at 1.0. This represents the classic shift of the visible light spectrum to red (redshift) at lower color temperatures. Below 1900K blue light is effectively absent.
Since excessive blue light may be disruptive to sleep-wake cycles, we can improve viewing comfort by decreasing the color temperature (below 4500K). On the other hand, higher color temperatures (above 6500K) will shift the visible spectrum to blue and this may be helpful for cinema or gaming applications.
Hi radky!
Thanks a lot for your superb Work !
But seems this Link:
Download JWMdesk-3.0
http://www.smokey01.com/radky/JWMDesk-3.0.pet
is not working.
Got this :
It appears you don't have
permission to access this page.
403 Error. Forbidden.
Maybe just me.
@backi,
Sorry, file permissions at Smokey's server are now adjusted and should be OK for access.
Thanks
Thank you Radky, including the small script of jcc into JWMdesk code. I very like it. I think it is more powerfull for puppy linux in the next release.
How if the user don't want to change the tray and menu color? i.e. still black. In jwm theme color it change all tray and menu automatically. Maybe some user just want to change the WindowStyle color, but not the tray and menu color.. So, is it possible to add a checkbutton for it?
Thank you very much Radky..
@recobayu,
Yes, we can add a 'Window only' checkbox which (if checked) will apply the selected color to the border of the active window only, while applying a contrasting dark background to the menu, tray and inactive window border.
I'll wait a day or two for any additional suggestions before releasing an update.
Thanks
The current Woof-CE produced releases (slacko, dpupos) have Tray1 as the Launcher only tray and Tray2 as the main standard tray. JWMdesk 3.0 is renaming the trays. This is an issue if hybrid autohide is selected. The tray1-hybrid file is left as it is. The renamed tray2 file still has an include statement for tray1_hybrid.
Two issues appear to be happening:
Additions to the Launcher Tray(now Tray2), are not added to the hybrid file, so a mis-match of the 2 trays occurs.
There also appears to be an issue with maximizing windows. I originally identified the overall issue, when maximizing windows. the windows are only maximized to the bottom of the tray. However, this didn't occur when retesting.
@TerryH,
Generally, running JWMdesk and the default Woof-CE tray manager simultaneously is not recommended. Please close the active tray manager before launching the other.
The default Woof-CE tray manager provides a very elegant and refined interface for changing JWM configuration options. On the other hand, JWMdesk is designed as a simple alternative JWM desktop manager which may provide unique functionality while implementing slightly different configuration nomenclature
For example, the default Woof-CE tray manager supports eight trays, of which one or two are typically present in a default installation of the iso. On the other hand, JWMdesk supports two trays (main tray and the optional accessory/launcher tray).
If you choose to install JWMdesk in a Woof-CE pup, the main tray will be identified as Tray-1 and the optional accessory tray as Tray-2. In this scenario, JWMdesk does not attempt to manage the configuration of any current accessory trays that already exist. In other words, if you choose to add an accessory tray, JWMdesk will reset the default configuration of the accessory tray as follows:
Go to JWMdesk -> Options tab -> Accessory tray -> uncheck the 'Launch Bar' checkbox and click the Apply button to remove the current accessory tray. Then re-select the 'Launch Bar' checkbox and choose the number of Preset buttons, and once again click the Apply button. This should restart JWMdesk in the Tray tab of the Tray-2 configuration interface and automatically load the new default accessory tray. At this point, in the Tray tab of JWMdesk, you can choose the preferred position for the accessory tray and also select the autohide option (Standard, Hybrid or Disable). You can easily remove the JWMdesk accessory tray by unchecking the 'Launch Bar' checkbox and clicking the Apply button.
---
At the moment I don't see a causal relationship between JWMdesk and failed maximizing of JWM windows.
Thanks for the report.
Don't know if this is the right thread to ask, but I'm trying to tweak a cayan-theme pet, and I have JWM thememaker installed. I can change window and title bar, border colors etc, but not text within windows. When I open the Color menu in GTK it notifies, 'Setting color scheme is not available without lxsession as session manager.'
Do I have lxsession? Or is that another application I need to load?
thanks
~geo
Hi radky first of all congratulations for all your hard work
I just updated the JWM and i notice that the script desksetup.sh has some code for nuthing but thats me 
you created 2 svg files but you all so copy some files, so i wonder why you got it that peace of code 
Old Version of Clock /usr/local/jwmdesk updates format without no need to reboot and in new version i need to reboot
you need to update the code to eval `gtkdialog -p GUI --center` or eval `gtkdialog --program=GUI --center` in order to update
There may be one or more small issues but cant figureout yet but for now its this
Best Regards António
geo_c wrote: ↑Thu Aug 12, 2021 3:08 amDon't know if this is the right thread to ask, but I'm trying to tweak a cayan-theme pet, and I have JWM thememaker installed. I can change window and title bar, border colors etc, but not text within windows. When I open the Color menu in GTK it notifies, 'Setting color scheme is not available without lxsession as session manager.'
Do I have lxsession? Or is that another application I need to load?
thanks
~geo
@geo_c,
Trio's JWM thememaker utility is not part of JWMdesk. You might consider posting your request in a separate thread where users of that application could offer advice.
Lxsession is the session manager of lxpanel (not JWM). You will find it lxpanel Pups, such as Peebee's LxPup variations.
Good luck in you quest for the ultimate desktop theme. 
AntonioPt wrote: ↑Thu Aug 12, 2021 4:00 amHi radky first of all congratulations for all your hard work
I just updated the JWM and i notice that the script desksetup.sh has some code for nuthing but thats me
you created 2 svg files but you all so copy some files, so i wonder why you got it that peace of code
Old Version of Clock /usr/local/jwmdesk updates format without no need to reboot and in new version i need to reboot
you need to update the code to eval `gtkdialog -p GUI --center` or eval `gtkdialog --program=GUI --center` in order to updateThere may be one or more small issues but cant figureout yet but for now its this
Best Regards António
@AntonioPt,
Thanks for your comments.
The desksetup.sh utility automatically creates the two main svg images displayed on tab-1 and tab-2. One of those files (deskicons.svg) is then symlinked to the appropriate system icon path: /usr/share/icons/hicolor/48x48/apps/. From this location the icon can be called and used for the title-bar icon (left upper corner).
The JWMclock module of JWMdesk-3.X is for JWM only, and it updates the clock by changing the strftime string in the XML code of the jwm tray, followed by the 'jwm -restart' command to refresh the time display. Rebooting is not required. The initial position of the graphical interface in the screen 'center' is determined by the 'window-position' parameter. The legacy 'GUI -center' parameter is not required for GUI placement and it has no impact on the clock format. If you require greater control of the clock font attributes (color, size and style), the legacy PupClockset utility may be of interest (see PupMates).
I hope this helps.
Thank you for all your work on this, radky. It has some cool options, and I especially appreciate your attention to tint.
My low vision issues make me find problems that are only problems for a few of us.
I'm using my Lenovo Thinkpad to test this.
Here's a pic of what happens to the tint after I put the redshift on in Fossapup64, for reasons I can show you in the next pic):
The other problem, was with the toggles inside of the xrandr, none of it changed the whites. Everything turned sepia except the color white, which remained a painfully bright white. The next pic is of the color change, using the Display Control (I killed redshift), where I cannot figure out how to make the whites less painful:
I wonder how well you can see the differences in tint from the screen shots? It's hard for me to see in preview, but then I'm looking through one tint or the other.
Thank you again for all you do, and sorry to have such difficult eyes, but those are the challenges for me.
The first thing to adjust to get a good picture is the backlight.
If the backlight is too bright the picture will be unpleasant. No settings of the gamma will be satisfactory.
For an external flat screen monitor, the backlight can be adjusted in the monitor's configuration menu.
For a laptop, you can adjust the brightness of the backlight using brightness-set
For example, brightness-set 8
Or you can use an app like adjbacklight
For an external monitor, you can then adjust the white level and the black level.
Sometimes the white level is labelled contrast and the black level is labelled brightness.
Sometimes the contrast and brightness are true contrast and brightness controls.
Most people adjust the white level much too bright and the black level much too black.
Only after adjusting the backlight properly should you adjust the gamma. Redshift, xgamma, and xrandr adjust the gamma.
The only way to adjust painfully bright whites is to adjust the backlight brightness.
PS I don't like redshift, I never use it.
Hi hundido,
The following excerpt is Note-3 from the second post of this thread, describing how the xrandr and sct utilities are implemented in the 'Display Control' module of JWMdesk.
Note-3: Display Control calls xrandr or (optionally) an enhanced version of sct to adjust the screen color temperature and brightness. If sct is installed, a toggle button is available to switch between the xrandr and sct interfaces, each providing unique advantages for improved screen viewing. For example, the xrandr interface provides greater contrast and color saturation at lower temperatures, while the sct interface provides the sepia effect of color warmth reminiscent of vintage photographs. Additionally, for multi-monitor configurations, the xrandr interface supports independent settings for each screen while the sct interface iterates identical settings for all screens simultaneously. Importantly, xrandr and sct do not change the actual backlight intensity, rather the observed screen appearance represents software modulation of available light.
If you choose to install the sct utility, there are important caveats. The original release of the sct utility by Ted Unangst has a singular function - to change the screen color temperature via the RandR X window system protocol. However, Display Control requires an updated version of sct (with code from the mgudemann, faf0 and mfachal forks). Specifically, this updated version of sct adds (1) screen brightness control and (2) multi-monitor support and (3) baseline adjustment of color temperatures in smooth 100K increments rather than the original coarse 500K increments. The updated 32-bit and 64-bit sct binaries for Display Control are available in the first post above.
In the xrandr and sct interfaces of Display Control, the selected color temperature values in Degrees Kelvin and the corresponding light intensity values are accessible in hscale slider widgets which are easily navigated. If you prefer single-click profiles to quickly adjust the screen tint and brightness please go to the Presets Option where you will find multiple preconfigured viewing profiles plus a custom option for your favorite profile. Since xrandr does not directly modify the tint of pure white backgrounds, the lower preset values for brightness are particularly useful at night to reduce the screen intensity of application windows that may appear bright white when viewed in some GTK themes.
Alternatively, Display Control provides a useful laptop hardware option (Screen Backlight) to change brightness of the primary screen through /sys/class/backlight (not for external screens in a multi-monitor configuration). When launched, Display Control checks the contents of /sys/class/backlight and if supporting files are not found the Screen Backlight option is not included in the GUI. The default script (brightness-set) which mediates backlight brightness control is courtesy of James Budiono of Fatdog Linux. If you require an alternate mediator of backlight control, the optional and versatile brightnessctl utility (if installed) will integrate seamlessly with Display Control. Please be aware, the new non-Xorg Xwayland Pups of Woof-CE do not support modulation of screen color temperature via xrandr or sct. Consequently, in this scenario the Display Control interface will exclude those options but will provide the option to control (laptop) backlight intensity.
The software (Tint and Brightness) and hardware (Screen Backlight) options can be used simultaneously but many users will choose one option and set the other option to a baseline neutral state (6500K and 100% for color temperature and brightness respectively).
Your screenshot above shows you have selected the 'Xrandr' interface for control of tint and brightness. Since the tint slider control of xrandr does not directly modify the tint of pure white backgrounds, the residual bright sreen intensity may be uncomfortable for those with sensitive vision. You can use the brightness slider control to reduce the screen intensity of application windows that may appear bright white, but this represents software modulation of light intensity and the effect may not be sufficient for sensitive eyes. For this reason, some users may prefer the 'Sct' interface to control screen tint and brightness, but this requires the modified version of sct which is available for download in the first post of this thread. After the modified sct utility is installed, the GUI of Display Control will show a toggle button which you can use to switch quickly between the xrandr and sct interfaces for control of screen tint and brightness.
If the software modulation of tint and brightness by xrandr and/or sct proves insufficient for your needs, please use the backlight slider control (if available) to adjust the actual intensity of the screen backlight. This option uses the brightness-set utility of James Budiono to directly modify light intensity. In this scenario you can use the tint control of 'Display Control' to decrease the screen color temperature for less blue light and improved sleep. At the same time, you can use the backlight control to decrease the overall backlight screen intensity for less of the painfully bright white.
Please see the third post of this thread for a simple graph that depicts the relationship between screen color temperature and the intensity of blue light that may impact our sleep-wake cycles.
Display Control and Screen Tint
viewtopic.php?p=32277&sid=0c48d885a0b0f ... 74f#p32277
I have a feeling that this version 3.1 of JWMdesk is more recent than the one I have pre-installed on @puddlemoon's jackalpup. If I install this new pet, will it update, or instead potentially break my current install?
Hi geo_c,
Installing newer versions of JWMdesk will update old files and add a few new files.
JWMdesk no longer includes companion Pupmates such as PupControl (available as separate download).
The next release (JWMdesk 3.2) will be available in a few days.
I've got JWMdesk-3.2 running on Fossapup, and Jackalpup, along with the tint control app, which is really helpful on my laptop monitor that never seems to be quite right compared to an external hdmi monitor.
@geo_c
Thanks for the report, and thanks for testing the JWMdesk screen control module.
Thank you for your replies, radky and williams2.
I'm not understanding if sct, in the gui, is controlled by the slider labelled "tint", which I see in my screenshot under the Xrandr, or if there's supposed to be a tab between Xrandr and Screensaver that I don't have. When I click on the sct binaries to try to install them again, my system tells me I already have them installed.
I tried on my Lenovo Thinkpad with Fossapup64, and I tried on a Acer Aspire 5738 using Xenial64.
Is Fossapup an xwayland and not xorg pup, because the note said tint won't work in xrandr or sct in xwayland pups, if I understood? If that's what's happening, do you know what is the newest pup sct would work in?
Could someone please post a screenshot highlighting where the sct gui is? I feel like I'm missing something.
Hi hundido,
Thanks for your question.
hundido wrote:
I'm not understanding if sct, in the gui, is controlled by the slider labelled "tint", which I see in my screenshot under the Xrandr, or if there's supposed to be a tab between Xrandr and Screensaver that I don't have. When I click on the sct binaries to try to install them again, my system tells me I already have them installed.
The Xrandr and Sct tabs of the Display Control module are not available at the same time.
Xrandr is the default GUI interface for 'Display Control' as shown in the first screenshot below. After the optional Sct binary is installed you will see a 'toggle' button (also shown in the first screenshot below).
Click the toggle button to switch between the Xrandr and Sct interfaces. After switching to the Sct interface, the GUI will appear as you see in the second sreenshot below.
Both GUI interfaces (Xrandr or Sct) will have the tint and brightness slider widgets to control the screen color temperature and light intensity respectively. If the Xrandr interface does not produce a comfortable screen appearance, then you could toggle (switch) to the Sct interface to adjust the screen appearance in a manner identical to the sepia effect of the popular Redshift utility. Please see the third post of this thread to better understand the relationship between screen color temperature and the visible light spectrum.
If Xrandr or Sct do not produce the desired screen appearance, the following may be helpful. If the laptop supports hardware backlight control, then please set the Tint and Brightness slider widgets of 'Display Control' to neutral positions (tint = 6500K, brightness = 100) and use the Backlight option to adjust the (hardware) light intensity of the laptop screen. Alternatively, for external monitors, some users may prefer the available manual controls for adjustment of screen brightness and contrast.
hundido wrote:
Is Fossapup an xwayland and not xorg pup, because the note said tint won't work in xrandr or sct in xwayland pups, if I understood? If that's what's happening, do you know what is the newest pup sct would work in?
At this time, all legacy Pups (including your installations of Xenialpup64 and fossapup64) use Xorg for the display server. Both Xrandr and Sct are fully functional in Xorg-based Pups. Please keep in mind, the installed Sct binary must be the one available in the first post of this thread.
On the other hand, new Woof-CE Pups (such as Vanilla Dpup) are currently evolving and available for testing but are not yet official releases. These Pups of the future have many new features including the replacement of Xorg with a different display server (Cage compositor running Xwayland).
Xwayland does not support xrandr or sct modulation of screen tint and brightness. In this scenario, only the Backlight option of 'Display Control' is available for the adjustment of screen illumination. However, for those who prefer Xorg, our Woof-CE devs have provided an option to toggle (switch) between the Xwayland and legacy Xorg display servers. This convenient option will ease the switch to Xwayland, if and when Puppy Linux officially transitions to Xwayland.
I hope this helps.
radky,
Thanks so much for the screenshots and extra instruction. My problem was I didn't figure out that was the toggle button until I saw your labeled screenshot. I have sct set to about 1800 and it is wonderful. Thank you, thank you for that visual magic that makes it possible for me to play with puppies.
All the gratitude,
hundido wrote: ↑Fri Oct 22, 2021 5:34 amradky,
Thanks so much for the screenshots and extra instruction. My problem was I didn't figure out that was the toggle button until I saw your labeled screenshot. I have sct set to about 1800 and it is wonderful. Thank you, thank you for that visual magic that makes it possible for me to play with puppies.
All the gratitude,
Same here! My pup has never looked better than it does now!
Thanks! JWMdesk-3.3 seems to have cleared up an issue that I was experiencing on my Fossapup64-proper install which was not occurring on my Jackalpup re-master. The inactive window transparency was not able to turn off. No matter how I set in picom window effects, the inactive windows were still transitioning to semi-transparent. Installing JWM-3.3 has solved the problem.
JWM-3.3 seems to be running very well in both installs.
@geo_c wrote:
JWM-3.3 seems to be running very well in both installs.
Thanks for testing the new release. Your report is very much appreciated!