(old)Puppy Linux Discussion Forum

Posted: **Tue 19 Jan 2010, 22:52**

Argolance wrote:Hello,
My test with jwm-464.tar.bz2 was successful.
My question: Is it better to work on this latest tar.bz2 file or on the one that comes with Puppy 4.31? If this one is better than that one, what is please the version of jWM I have to download?
Thank you for your kind attention.
Regards

I would stick to the 464, posted above, That one is the latest stable one.
ttuuxxx

Posted: **Tue 19 Jan 2010, 22:59**

Thanks for your responsiveness.
So, those 'little things that seem to be a bit problematic' mentioned above are probably due to my fault?

Posted: **Tue 19 Jan 2010, 23:09**

Hello,
I would like to do a pet file to test my work. What must I do? Or is there somewhere any tutorial that could explain this step clearly?
Thank you.

Posted: **Tue 19 Jan 2010, 23:17**

Sorry! I found it here:
http://puppylinux.org/wikka/Compiling?show_comments=1

Posted: **Wed 20 Jan 2010, 05:49**

So, those 'little things that seem to be a bit problematic' mentioned above are probably due to my fault?

What are the little things?

Posted: **Wed 20 Jan 2010, 10:26**

Hello,
When running a window to write a mail in Seamonkey or especially when working with gimp, I noticed that windows (not the main windows!) were not properly displayed while clicking on their own bar in the task bar. They appear a very very short moment then disappear...
Both of the JWM versions (the original one and the French localized one) have got this problem...
Regards

Posted: **Tue 26 Jan 2010, 18:05**

Bonjour à tous,

Does someone can give us the options to compile jwm for Puppy/Toutou Linux.
Because after translation of files we have behavior issues with jwm.
Thank you.

Cordialement

Posted: **Tue 26 Jan 2010, 22:13**

Hello,
(@esmourguit >... ça faisait un bail!)

Could somebody tell me what JWM version comes with Puppy 4.31 and the tarbal to download?
Thank you.
Regards

Posted: **Tue 26 Jan 2010, 22:15**

Hello,
(@esmourguit >... ça faisait un bail! )

2 questions:

* Could somebody tell me what JWM version comes with Puppy 4.31 and the corresponding tarbal file to download?

* How to use the purists version? The tarbal contains a few files. What should be done with these files: add them in the src folder and replace the existing ones then compile? Or something else?

Thank you.
Regards

Posted: **Tue 26 Jan 2010, 23:28**

Argolance wrote:Hello,
(@esmourguit >... ça faisait un bail! )

2 questions:
* Could somebody tell me what JWM version comes with Puppy 4.31 and the corresponding tarbal file to download?

* How to use the purists version? The tarbal contains a few files. What should be done with these files: add them in the src folder and replace the existing ones then compile? Or something else?
Thank you.
Regards

hmmm not sure for 4.31 but for 4.2 I compiled this one
http://joewing.net/programs/jwm/snapsho ... 56.tar.bz2
and the package was on this thread
http://www.murga-linux.com/puppy/viewto ... 866#291866
it was downloaded only 631 times lol
ttuuxxx

Posted: **Tue 26 Jan 2010, 23:33**

Argolance wrote:Hello,
(@esmourguit >... ça faisait un bail! )

2 questions:
* Could somebody tell me what JWM version comes with Puppy 4.31 and the corresponding tarbal file to download?

* How to use the purists version? The tarbal contains a few files. What should be done with these files: add them in the src folder and replace the existing ones then compile? Or something else?
Thank you.
Regards

If you have 4.31 running just open a terminal and type
jwm -v
it will give you the build number
then go to http://joewing.net/programs/jwm/snapshots/jwm-456
to download 438-464 versions
or http://joewing.net/programs/jwm/releases/
for 0.1 - 2.0.1 versions
ttuuxxx

Posted: **Sun 07 Feb 2010, 00:05**

I'm not sure if Joe is watching this thread, or if anyone else has been having input into the snapshot versions lately, but make has failed in the last couple (IIRC - certainly the last one, anyway) when using --disable-xmu

Code: Select all

gcc -o jwm background.o border.o button.o client.o clientlist.o clock.o color.o command.o confirm.o cursor.o debug.o desktop.o dock.o event.o error.o font.o gradient.o group.o hlp.o hint.o icon.o image.o key.o lex.o main.o match.o menu.o misc.o move.o outline.o pager.o parse.o place.o popup.o render.o resize.o root.o screen.o status.o swallow.o taskbaro timing.o tray.o traybutton.o winmenu.o -L/usr/X11/lib -lX11 -lpng12   -ljpeg -L/usr/X11R7/lib -lXft -lXrender -lfontconfig -lfreetype -lz -lX11   -L/usr/X11R7/lib -lXrender -l11   -lfribidi   -lXpm -lXext -lXinerama -g
button.o: In function `DrawButton':
/tmp/0/jwm-468/src/button.c:122: undefined reference to `XmuDrawRoundedRectangle'
collect2: ld returned 1 exit status
make[1]: *** [jwm] Error 1
make[1]: Leaving directory `/tmp/0/jwm-468/src'
make: *** [all] Error 2

Posted: **Sat 13 Feb 2010, 01:43**

I posted a while back about issues I had with kcompmgr (and xcompmgr) that occurred both in jwm and icewm. There were artifacts of rox-filer left on the desktop and diagonal tearing when windows opened or closed, or when playing videos flash or otherwise. I posted a screen shot of my issues in IceWM and people seemed to jump on it because it wasnt jwm. Although I knew this forum was dedicated to Patriots work on jwm 2.0, I had hoped since it used kcompmgr someone may have had an idea on the issue and what the trouble might be. I had some help from Patriot himself but no one seemed to know what the issue was for certain, but I am happy to report I seem to have fixed it.

Patriot wrote:Hmmm .....

joel wrote: ..... When I enable kcompmgr or xcompmgr the shadows and transparencies show fine, but when I open a window, then a folder within that window it leaves traces on the desktop of the prior window.
Based on the screenshot, it really doesn't seem to be JWM as JWM does not support pixmap captions ... I believe that you seem to be having some issues with IceWM ...

..... secondly when I use one of the compmgrs pwidgets goes crazy with certian programs like celestia. When celestia is open the widgets flicked through even if I fulscreen celestia. Now it only happens when I have a compmgr active.
Is this the celestia 3d space simulation? ... If it is, then OpenGL is presumed to be active/working and it is probably a driver related issue ... certain drivers requires tweaking the xorg.conf file to work with composite properly ... I couldn't remember off hand but nvidia cards seems to need a tweak ...

..... My guess is that conky wants to draw windows on top of everything elese and this conflicts with kcompmgr.
Not quite so ... the conky version used in pwidgets were patched to draw on rox desktop canvas (if specified by the individual widget). I did some initial pwidgets testing back then on composite screens and did not encounter such conflicts ... I'll do some tests again later and see how it goes .....

Rgds

All I needed to do was tweak a few options in xorg.conf. I wanted to relay this to anyone who uses IceWM but would like the eye candy effects of xcompmgr or kcompmgr. I suggest using kcompmgr because as Patriot says it has had a number of bug fixes. I do think personally that IceWM is much more pleasant to look at than jwm, and was frustrated at the bugs which rendered it useless in IceWM in the hope they find this and don't have to post and wait for help or search endlessly for an answer.

Now the card in my laptop is an ATI Raedon M7500, which is terribly difficult to work with but I made it work so you should be able to also with other cards. The kcompmgr that Patriot included will work fine just set the values for the transparency, opacity, etc that you wish.

After that just past these lines into the xorg.conf where the options for the card are defined.

Option SyncToVBlank=1
Option XVideoTextureSyncToVBlank=1

Also:

Make sure "Option "XAANoOffscreenPixmaps" "true" is either set to false, off, or the line is commented out. For what ever reason this Option (if you are using it) seems to conflict with the other two you need to add.

Posted: **Sat 18 Sep 2010, 10:24**

Hello,
In the French version of Puppy 4.31, called Toutou LINUX, we could not keep the JWM release that comes with Puppy, cause we noticed issues we just 'solved' using an older one

. I recently tested the latest release of JWM (2.0.1): it seems that encountered problems were rectified

. But, as it is the case with Puppy 4.31, applications windows cannot be resized from top left and right corners

.

An other example: when dragging down a maximized window from its title bar, it becomes minimized. Here are two behaviors I noticed in different releases of Puppy when dropped:

- The window stays minimized
- ... or turns back to the maximized position!

My question: How and where configure all these windows behaviors?

Regards!

Posted: **Mon 20 Sep 2010, 21:00**

Hello,
Bug (?) report (noticed on 2 PC and a laptop):

- When fade-in/out is enabled xlock makes the system wickedly freeze. Keyboard is 'dead', mouse 'alive' but ineffective. Have to shutdown with power button .
- When disabled (basic configuration), system doesn't freeze but screen-saver doesn't run...

Regards.

Posted: **Sat 11 Aug 2018, 08:01**

Patriot wrote:Hmmm ...

I've recently looked into how XDG menus are converted to JWM menus in puppy. I've made some minor enhancements to jwm-xdgmenu utility & fixmenus script.

The jwm-xdgmenu will :

1. Add double spaces before a menu entry
2. Allow adjustable menu heights
3. Check for icon extension. Default to .png if it's missing.
4. still be backward compatible with previous jwm template.

The fixmenus script will now retain formatting and layout of the template. The sample template is for puppy 4.1.x and you are expected to use it as a base example.

At the same time, I've also updated blinky with gnome status icons to go along with the new look of JWM enhancements.

Rgds

Is this the most recent source for this jwm-xdgmenu:
http://www.murga-linux.com/puppy/viewto ... 430#302430

I couldn't find it in github for woof-CE

Anyway, I might try to compile it for termux-proot-debian on my samsung s9+ which uses the arm64 (AKA AArch64) architecture.

Posted: **Sun 12 Aug 2018, 09:33**

s243a wrote:Is this the most recent source for this jwm-xdgmenu:
http://www.murga-linux.com/puppy/viewto ... 430#302430

The source that I use is xdg-puppy 0.7.8. The recipe in my fork of OpenEmbedded has the download link and build script:

https://github.com/bkauler/oe-qky-src/t ... /xdg-puppy

OE is a cross-compile environment, so a bit more complicated. For normal compiling, there is a script in the package.

Posted: **Sun 12 Aug 2018, 09:36**

puppylinux site on ibiblio.org also has a source package, seems older version, don't know what is different:

http://distro.ibiblio.org/puppylinux/sources/x/

Posted: **Mon 18 Mar 2019, 00:09**

One of main reasons I don't use Puppy by default even though its facilities are perfectly good for my usual web-browsing pottering around needs is that if the browser is minimised to the taskbar I cannot simply drop an html file from file manager onto Joe's Window Manager firefox-or-otherbrowser-minimised tray icon. That's something I do all the time in XenialDog, which uses Openbox and tint2 and as soon as I drop file on the minimised taskbar icon for firefox, firefox opens up displaying the file. That's what I want and hate working without! Yes, I could put a lot of effort into configuring openbox/tint2 on Puppy, or find a pup that uses that, but I'd love to see JWM incorporating that functionality.

wiak

Posted: **Mon 18 Mar 2019, 02:50**

Hello wiak.

Or replace the jwm task-and-tray bar with Tint? You can use another bar in jwm if
.jwmrc-tray does not exist. I have done it from time to time with bmpanel2.

Strictly speaking, the bar is not part of a WM. A WM should only manage windows,
as the expression implies.

BFN.

(old)Puppy Linux Discussion Forum

JWM 2.0.1 Enhancements and Fixes