[CLOSED]JWM Desktop Updates to V755(Release) and V910(Test)
scsijon, et-al
I have an update for the jwm-config. It is now ready for when Joe releases 2.2. When I did a git clone jwm identifies itself as version 2.2 so I had to fix it. I put it (along with jwm-750) in the ThinSlacko delta release.
I have an update for the jwm-config. It is now ready for when Joe releases 2.2. When I did a git clone jwm identifies itself as version 2.2 so I had to fix it. I put it (along with jwm-750) in the ThinSlacko delta release.
- Attachments
-
- jwmconfig2-130504.pet
- (54.33 KiB) Downloaded 503 times
Puppy Linux Blog - contact me for access
We are now up to Version 755.
I have split the NLS for this version only to allow the language builders to 'do their own thing'. Pleasase add your files to your reply and i'll ensure joe gets them for inclusion in the source.
I have also re-added back in a small post-install script that was accidentally removed from the release sets. My apologies to woof builders for that exclusion. The script does not affect anyone else and does not appear in the test versions.
I have split the NLS for this version only to allow the language builders to 'do their own thing'. Pleasase add your files to your reply and i'll ensure joe gets them for inclusion in the source.
I have also re-added back in a small post-install script that was accidentally removed from the release sets. My apologies to woof builders for that exclusion. The script does not affect anyone else and does not appear in the test versions.
- OscarTalks
- Posts: 2196
- Joined: Mon 06 Feb 2012, 00:58
- Location: London, England
I was experimenting with a recent Google Earth 7.1.1.1580 (beta) and found that if the maximized window is closed and re-opened it does not fill the screen despite the button showing as maximized. If I reduce down and maximize again it fills the screen again.
I posted an .SFS and a .PET here:-
http://www.murga-linux.com/puppy/viewtopic.php?t=86211
Not sure if this is a JWM issue or a bug in the Google Earth code, but it doesn't happen in Openbox in Lucid and it doesn't happen in JWM with the slightly earlier 7.0 Google Earth.
I posted an .SFS and a .PET here:-
http://www.murga-linux.com/puppy/viewtopic.php?t=86211
Not sure if this is a JWM issue or a bug in the Google Earth code, but it doesn't happen in Openbox in Lucid and it doesn't happen in JWM with the slightly earlier 7.0 Google Earth.
Oscar in England
sorry folks, I have been up above my ears (literally) in paint. !I hate painting ceilings!
However I have downloaded joe's latest v762 and will build today. If it passes my basic set it should be up tonight/tomorrow for your wider testing.
EDIT: Done, see first post for the 32bit test pet, x86_64 will appear this weekend.
@Oscar, I suspect it's google earth but when I have built the next version can you try again. If it's still happening I shall pass it on to joe for a check.
However I have downloaded joe's latest v762 and will build today. If it passes my basic set it should be up tonight/tomorrow for your wider testing.
EDIT: Done, see first post for the 32bit test pet, x86_64 will appear this weekend.
@Oscar, I suspect it's google earth but when I have built the next version can you try again. If it's still happening I shall pass it on to joe for a check.
If the ceiling's fairly plain, you can use a specialized roller cover for ceilings from Sears (hardly any dripping!) and go a bit slower with it..
more jwm-ish (dotpet of 762 and etc)
Handles well in racy 5491 and slacko55. One of the differences I looked for was the handling of 'serial translucency' with kcompmgr -n enabled - it does indeed seem more simplified, in essence the 'stepping' of the translucency effect according to layer of individual windows. The overall visual effect is similar to pre-750 versions but slightly different in use (actually seems more robust in keeping with Joe's overall plan). Moving windows by r-click-drag in the pager feels quite smooth and even the 'pop' as desktop is changed when moving over halfway past the boundary is hardly noticeable.
Custom-compile in p431. Oh well, still has the drawing-remnant issue for max, max-h and max-v when using titlebar button for that in p431 (but fine with window or tasklist button menu) with kcompmgr -n enabled. Noticeably less smooth in p431 for moving windows by r-click-drag in the pager also. The stepping of serial translucency is simplified for sure, much more obvious when the xpad windows I use for test have the same bg. Comparing against vgit-731, sloppy focus looks a bit better integrated now too.
All very quick and responsive, looks like a winner to me.
more jwm-ish (dotpet of 762 and etc)
Handles well in racy 5491 and slacko55. One of the differences I looked for was the handling of 'serial translucency' with kcompmgr -n enabled - it does indeed seem more simplified, in essence the 'stepping' of the translucency effect according to layer of individual windows. The overall visual effect is similar to pre-750 versions but slightly different in use (actually seems more robust in keeping with Joe's overall plan). Moving windows by r-click-drag in the pager feels quite smooth and even the 'pop' as desktop is changed when moving over halfway past the boundary is hardly noticeable.
Custom-compile in p431. Oh well, still has the drawing-remnant issue for max, max-h and max-v when using titlebar button for that in p431 (but fine with window or tasklist button menu) with kcompmgr -n enabled. Noticeably less smooth in p431 for moving windows by r-click-drag in the pager also. The stepping of serial translucency is simplified for sure, much more obvious when the xpad windows I use for test have the same bg. Comparing against vgit-731, sloppy focus looks a bit better integrated now too.
All very quick and responsive, looks like a winner to me.
- Attachments
-
- 762.png
- with kcompmgr -n in slacko55
- (52.8 KiB) Downloaded 739 times
thanks 'f00, but the house is a pre-1st world war timber and iron roofed building, nothing is plain, straight, square,etc.,..., but I like it as it's 'small' and there is only me (and four cats) living in it nowadays. And before anyone yells about the cats, they are all desexed, were strays, and up here in the wheat belt, a necessity to keep mice out of the house and workshops for at least 9 months of the year.
However, back on topic.
I've just downloaded a new snapshot v768, so that should come the test way uploaded tonight, one thing it has is some updated po files that need checking please by our non-english speakers please, and a few more supplied if people have time. from an initial build, it seems a bit faster with window creation as joe has apparently done some changes and removed some redundant code.
However, back on topic.
I've just downloaded a new snapshot v768, so that should come the test way uploaded tonight, one thing it has is some updated po files that need checking please by our non-english speakers please, and a few more supplied if people have time. from an initial build, it seems a bit faster with window creation as joe has apparently done some changes and removed some redundant code.
Hi,
I use Precise 5.6 with a 1024 x 768 pixel screen.
After installing jwm 768 and Restarting X both abiword
and dillo open their 936 x 702 windows in a new position
(some 25 pixels right of their pre-768-installation point).
My regards
PS I used 936 x 702 because if I made my dillo or abiword
less than full screen windows with other than a 4 x 3 ratio
they only opened in the exact position I wanted on exactly
every second opening.
I use Precise 5.6 with a 1024 x 768 pixel screen.
After installing jwm 768 and Restarting X both abiword
and dillo open their 936 x 702 windows in a new position
(some 25 pixels right of their pre-768-installation point).
My regards
PS I used 936 x 702 because if I made my dillo or abiword
less than full screen windows with other than a 4 x 3 ratio
they only opened in the exact position I wanted on exactly
every second opening.
@jasper, hi
Is it only those two apps or do all apps start to the right?
Also, if you shrink them a little bit more, do they still move right?
before I put a problem to joe, I had best get some further info as I cannot duplicate your problem on any of my boxes, although i don't have precise 5.6 loaded anywhere, downloading one now. By the way there is a 5.6.1 bugfix out.
Is it only those two apps or do all apps start to the right?
Also, if you shrink them a little bit more, do they still move right?
before I put a problem to joe, I had best get some further info as I cannot duplicate your problem on any of my boxes, although i don't have precise 5.6 loaded anywhere, downloading one now. By the way there is a 5.6.1 bugfix out.
Hi again,
I reduced abiword to 900 x 675 and dillo to 800 x 600 and
checked the pre and post v 768 positions with a pixel ruler
and saw no movement, Since you have almost certainly hit the
nail on head and as they are the only apps I want to and can
open in a specific position I did not try to test more apps.
I did post in BarryK's Precise 5.6/5.6.1 at the very bottom
of page 5 about the superb speed increase in JWM menus
thanks to technosaurus - I expect Joe and yourself already
know about that.
I will not be suggesting to BarryK that there may be a
minor bug in Precise 5.6/5.6.1 (though I do hope npierce
will update Barry on his abiword non-US spell-checker
problem fixes).
To be honest I have never used the layer optioms in earnest
and I gather JWM v768 Test has some speed increases and
a nice right click shade option. I only use JWM and ROX so
I'm very pleased Joe is making improvements and although
I was and am happy to try to test v768 I have no idea of
any other changes.
My regards
I reduced abiword to 900 x 675 and dillo to 800 x 600 and
checked the pre and post v 768 positions with a pixel ruler
and saw no movement, Since you have almost certainly hit the
nail on head and as they are the only apps I want to and can
open in a specific position I did not try to test more apps.
I did post in BarryK's Precise 5.6/5.6.1 at the very bottom
of page 5 about the superb speed increase in JWM menus
thanks to technosaurus - I expect Joe and yourself already
know about that.
I will not be suggesting to BarryK that there may be a
minor bug in Precise 5.6/5.6.1 (though I do hope npierce
will update Barry on his abiword non-US spell-checker
problem fixes).
To be honest I have never used the layer optioms in earnest
and I gather JWM v768 Test has some speed increases and
a nice right click shade option. I only use JWM and ROX so
I'm very pleased Joe is making improvements and although
I was and am happy to try to test v768 I have no idea of
any other changes.
My regards
I fear that my request for easier window minimization (issue #45) may make it easier to break nested windows. Ideally, when all of the windows in a stack have individual minimize buttons, you'd expect to be able to minimize all of them using the taskbar entry as well. But when you're dealing with windows that cannot be closed until the child window is closed... things are easier to break.
This can be duplicated in QtWeb. Options -> Advanced -> Search Providers -> Add New. Minimize and restore the main window several times, and one of the nested windows will break. Granted, you had the ability to minimize multiple nested windows before issue #45 was resolved, you just couldn't do it from the taskbar. But I can't duplicate this in v574.
This can be duplicated in QtWeb. Options -> Advanced -> Search Providers -> Add New. Minimize and restore the main window several times, and one of the nested windows will break. Granted, you had the ability to minimize multiple nested windows before issue #45 was resolved, you just couldn't do it from the taskbar. But I can't duplicate this in v574.
- Attachments
-
- jwm_capture185.jpg
- That's a lot of nested windows
- (56.76 KiB) Downloaded 599 times
[color=green]Primary[/color] - Intel Pentium 4 2.40GHz, 571MB RAM, ATI Radeon 7000. Linux Mint 17 Qiana installed.
[color=blue]Secondary[/color] - Pentium 3 533MHz, 385MB RAM, ATI Rage 128 Pro ULTRA TF. Precise Puppy 5.7.1 Retro full install.
[color=blue]Secondary[/color] - Pentium 3 533MHz, 385MB RAM, ATI Rage 128 Pro ULTRA TF. Precise Puppy 5.7.1 Retro full install.
v722 test build
@jasper, I think your problem has been fixed by joe with the latest snapshot.
@session, Yours may also be ok now, joe has done some fixes that may have sorted it all out.
I shall build, test and make available a V772 test build tomorrow, I have to go out tonight to a CFA meeting.
@session, Yours may also be ok now, joe has done some fixes that may have sorted it all out.
I shall build, test and make available a V772 test build tomorrow, I have to go out tonight to a CFA meeting.
ChangeLog<---(from current all the way back to 2005!) says
If you like that feature, it can be swapped back in with the src/cursor.c from 762 .. doesn't seem to break anything in 772 as far as I can tell. Of course whether the custom hover cursors look 'right' depends on your cursor set
as of Fri May 31 18:42:46 2013No more custom cursors for close/minimize/maximize.
If you like that feature, it can be swapped back in with the src/cursor.c from 762 .. doesn't seem to break anything in 772 as far as I can tell. Of course whether the custom hover cursors look 'right' depends on your cursor set
v775
I have uploaded a test version 775, have fun!
...meanwhile, my problem is fixed.
Resizing while maximized is now disabled... I've used that quite often to set window size, but it became redundant after recent versions made it so easy to maximize X or Y; this is certainly more streamlined.
@jasper: window placement is a little different after v768 in some apps... you can always use the --geometry option, say 936x702+0+0 (curiously, dillo won't respect 0+0, you have to do 0+1 to get as close to the corner as possible)
Resizing while maximized is now disabled... I've used that quite often to set window size, but it became redundant after recent versions made it so easy to maximize X or Y; this is certainly more streamlined.
@jasper: window placement is a little different after v768 in some apps... you can always use the --geometry option, say 936x702+0+0 (curiously, dillo won't respect 0+0, you have to do 0+1 to get as close to the corner as possible)
Last edited by session on Thu 13 Jun 2013, 03:52, edited 1 time in total.
[color=green]Primary[/color] - Intel Pentium 4 2.40GHz, 571MB RAM, ATI Radeon 7000. Linux Mint 17 Qiana installed.
[color=blue]Secondary[/color] - Pentium 3 533MHz, 385MB RAM, ATI Rage 128 Pro ULTRA TF. Precise Puppy 5.7.1 Retro full install.
[color=blue]Secondary[/color] - Pentium 3 533MHz, 385MB RAM, ATI Rage 128 Pro ULTRA TF. Precise Puppy 5.7.1 Retro full install.
@jasper, I have added a problem to joe's issue list for you.
EDIT 14june: I have just downloaded v777, I shall build and test tonight before uploading tomorrow as i'm working today elsewhere.
EDIT 14june: I have just downloaded v777, I shall build and test tonight before uploading tomorrow as i'm working today elsewhere.
Last edited by scsijon on Thu 13 Jun 2013, 21:54, edited 1 time in total.
@jasper
Joe answered with:-
Can you try to work it out with sessions help?
I have put the problem on joe's system on hold until needed.
regards
Joe answered with:-
I must admit that I haden't seen this mentioned in the changelog, else I would have mentioned it.The window placement has changed somewhat, so I would expect that some windows might open in different locations. Are the applications being started with a "-geometry" option?
Can you try to work it out with sessions help?
I have put the problem on joe's system on hold until needed.
regards