I'm back for a while, until work takes over again.
I've built and internally tested V910 and the only thing I've found is it seems to take longer to do anything in the shutdown menu so it's now up to you to load test it. If nothing serious appears by Easter I shall move it to Release status then.
Have fun!
15 Aug 2013
Latest JWM Test Version is now attached. JWM Release 2.2 is now a month behind schedule while joe fixes the last few problems and changes he wants in it so I don't expect many more unless major stoppers appear.
21 July 2013
Latest JWM Test Version is now 835, could our non-english reading puppians please check their languages out. Thanks.
Many Languages are still wanted if anyone has time please. the pot you need to work with is in L18L's post (the fourth one down) not puppy's as we only use a subset. http://www.murga-linux.com/puppy/viewto ... 994#709994.
7 july 2013
Latest JWM Test version 827, fixes and a few new languages included.
4 july 2013
JWM Test version 819 has been uploaded as 815 ocassionally had problems with windows in the tray, sorry.
25 june 2013
JWM Test Version 815 has been uploaded.
As usual, providing no serious problems are found, I intend using this for the next release version in about seven days so can I have responses in the thread with the puppy's tested against listed please.
22 june 2013
We have a new test version, it includes fixes and additions.
15 June 2013
I have uploaded a test build of v777 for your testing. If all is ok after some user testing.
04 june 2013
I have uploaded a test build of version 768 for testing.
30 May 2013
I have uploaded a test build of jwm at version 762 for testing.
My initial reaction is that pages and windows seem to be being redrawn quicker, looking at Topview it also seems to use less cpu%age when the system is dealing with a decent load, other than those I have not found any differance yet.
15 May 2013
I have updated jwm to a release version build of 755 although I have yet to build the new x86_64 version.
It appears in two packages, as I have had requests to separate the NLS so a few people could see what languages were inside it and 'create' their own language files to be added into the set. I don't intend to carry this practice on by default as it is not normally done with a jwm build. Could those creating the language files please attach them to their responses and i'll see that they get back to joe for inclusion in the main package source.
7 May 2013
I have added below a x86_64 pet for TESTING ONLY by the fatdog64 and slackbones community. Although normally it would be best for them to add mick's jwmconfig130213.pet (page3 for url) as it has been updated to match the new jwm's config for 32bit puppies only, it's not an exact match for the way fatdog64 and slackbones64 and it does show an error on start so for now I won't recomend it be installed.
@32bit users and others, please note that mick has created a new jwmconfig2, it's at/near the bottom of page 9 and will be needed for V750+.
6 May 2013
Test Version 750 uploaded, if it's without problems next week I shall rebuild as a Release.
3 May 2013
I have uploaded a test version of JWM Version 746.
21 Apr 2013
I have rebuilt jwm's v731up to my release standard.
I have also built a new test version v733, notes are at the bottom of page7.
14 Apr 2013
A new test version 731 has been uploaded.
Please check my note at the bottom of page7 before use.
12 Apr 2013
Production Version is still 704
A new Test Version 726 has been uploaded. If no problems appear in the next week I will rebuild it at Release Standard.
This new Snapshot version has been classed by joe as a Master/Head Build and could be used by joe for his next full release (2.3) so I expect it will become the Production Version for a while.
05 Apr 2013
Production Version is still 704
A new Test Version 722 has been uploaded. If no problems appear in the next week I will rebuild it at Release Standard.
28 Mar 2013
The production Version has updated to 704.
The Test Version has updated to 716. Those new to testing please remember to use mick's jwmconfig2 mentioned and linked on page3.
There will also be a changelog on the message on page 7 for those wanting to see what has happened.
17 Mar 2013 The production version at this time is still jwm2-691.
Version 704 is at TEST ONLY status until the 24th when it will be rebuilt as production if no problems have arisen.
I have uploaded a new version JWM2-704 for final testing only, please test and report asap. It contains the 'core only'. Anyone new to testing jwm2 please also download and install micks (01micko) config pet mentioned on page3 as it's a co-requisite (if you have not already done so)!
Notes start on page5
Please make sure you include what puppy's you have tested on with your reply's.
-------------------------------
I have built a final release version of jwm2-691 and removed the previous versions.
The new version is in two pets.
The first pet, jwm2-691-w5c.pet contains only the core jwm component and docs and for someone upgrading should be enough for those upgrading from V679 or later.
The second pet, jwm2-config-691.pet contains the config components and will be needed for anyone upgrading from a version pre jwm2-679 or working from woof.
Alternately to using the second pet, you can instead use 01micko's jwmconfig2-130213.pet mentioned with a link on page 3 which works as well and has some additional functions which I do like.
---------------------------------------------------------------
I have a JWM upgrade at Version 691 attached below for you all, that seems to be ok and without that annoying window outside the screen, please test and report.
There is only one this time.
The thread picks up around the bottom of page2 for v691.
I have left version 679 in case anyone has to step back.
-------------------------------------------------------------
I have been testing for Joe Wing who has come back to working and improving jwm, in building an updated jwm for puppy. I think we have a working one now, however he is still improving it and I shall update on intervals.
For my point, it's primarily for my Mage2, as the standard one did have problems, but I will build and test against as many puppy versions as I can when I have what I consider 'puppy stable' releases.
So far there are mage2 and wary/racy versions available, the later has been tested against others and seems to work happily so for now I shall only build the two.
There are a couple of changes puppy woof builders (not users) will need to do with using the standard /etc/xdg/templates/_root_.jwmrc file which I have needed to altered slightly, as he has changed a few things. I'm not sure if the gtk people (thunor?) need to know, but I will add a note in his thread.
To quote joe
"With the latest snapshot, the number of user-configurable layers has been reduced to three ("above", "normal", and "below"). In addition, there is now a configuration option (the "border" attribute on the "TrayButton" tag) to set whether tray buttons have a border rather than the rule where tray buttons that are smaller than 48 pixels are flat".
There are other changes as well that affect the appearance slightly. However I believe to the better, but certainly the new build is so far both faster as well as more pleasing to use!
The current version I have built and tested against is 679 and is attached for others to play with. If your not using mage2 please use the jwm-679-w5c pet as the mage2 version is built specifically for mageia puppy's.
One thing you need to be aware of is that as part of the update fixes, jwm now passes application errors on rather than 'absorbing' them as it did in the past. This means that any application that has a problem and is opened under jwm will have it's errors passed onto the /tmp/xerrs.log file, this file will grow and needs ocassionally checking. I have found it interesting in that some errors have appeared here that were not found elsewhere. The problem is that some are not really relevant, being things like notices of lib links instead of the actual lib files being used, however it is finding errors and those found should be fixed, and this may only require a recomilation of the package to deal with updates, or the addition of a missing lib file that was not realized as missing![/url]