pa_mcclamrock wrote:ecomoney wrote:There are still a lot of bugs for a release candidate. Whats all the rush to release? Lets make sure we get it right first.
Hear, hear!
Please read my explanation for the release of RC1 instead of Beta3. Release candidates are not expected to be bug free, just showstopper bug free, with fixes in train for the others. They are an opportunity to expose the new product to a wider testing audience to see if new problems are exposed in the process. Having squashed the major bugs from the Alpha and Beta series I felt the move was entirely justified.
@ecomoney et al - This release of Puppy has already had more testing releases than any previous official Puppy release except 2.15CE - which had a greater need of testing due to my own inexperience with buidling Puppy from the Unleashed tree. Progress has been steady but inexorable. The Deep Thought product is now ready for wider testing IMHO. I do not expect this version will be followed with a dotpoint-1 update as have some previous official versions either. Barry had to occasionally resort to actual releases in order to get things tested - witness 2.16-1 and 2.17-1 for example. This time around we have a committed and knowledgable pool of community Alpha and Beta testers who have brought us this far without the need to "rush" an actual release out into the wider community to find these bugs.
Please, enough of the recriminations over the choices I have made. They were ALL MY CHOICES and I will live or die by the end result. We don't have that "end result" yet, so less rushing to judgement would certainly be helpful.
pa_mcclamrock wrote:PETget still takes far too long on the "updating menus" stage when installing or uninstalling. (EDIT: For some reason, this appears to be true only before you create a pup_save file and reboot--which I just did. Then I installed a couple of .PETs, and "updating menus" only took a few seconds, as it should!)
Let's see if things are better in the next release, since Zigbert has made further modifications to the fixmenus script at the heart of the menu update process.
pa_mcclamrock wrote:PETget's instruction to "restart the window manager" (which there isn't any obvious way to do without restarting the X server) is still there, and it appears that you don't even really need to click "Refresh Menus" any more.
Not true. The need varies between JWM and Icewm. In JWM you always have to refresh the window manager, but in Icewm you don't. Taking account of both systems is a bit more tricky than just allowing for one process, but worth it in the overall scheme of things. Maybe we'll move to a single WM again down the track - either Icewm or the newly updated JWM with Patriot's valuable input - but for the moment I'm happy to have both so our users have a real choice of environment and can make an informed decision for later on when Woof builds are the norm.
pa_mcclamrock wrote:Restore "Restart IceWM" to the IceWM menu!
That's what Refresh menus does anyway, as ttuuxxx has pointed out.
pa_mcclamrock wrote:In SeaMonkey, the View --> Show/Hide menu has "Tab Bar" grayed out, which made me think maybe the tabbed browsing function was hacked out of the new SeaMonkey in a misguided effort to save space--until I saw that the tab bar will appear if you click File --> New --> Navigator Tab.
As ttuuxxx has suggested, this one is probably a Seamonkey issue rather than a Puppy issue. Nevertheless, Seamonkey 1.1.14 is the most stable version of the Seamonkey line to have surfaced so far, and there is little to choose between it and Firepup for performance alone. With ttuuxxx adopting Seamonkey for Puppy, we may well get a Seapuppy version down the track, but not if people keep throwing cold water on his enthusiasm! (Not you David, but an allusion to earlier posts in this thread).
Hope that helps.
[i]Actions speak louder than words ... and they usually work when words don't![/i]
SIP:whodo@proxy01.sipphone.com; whodo@realsip.com