No apology necessary. I just didn't want you to think I had ignored your earlier request. As a look-and-feel issue, it didn't get my top priority for RC1, but your feedback and support is still greatly valued. It will be fixed for RC1 Office Edition, you can count on it.Springer wrote:WhoDo:Thanks, and sorry if that sounded like griping - I really appreciate the work, and feel bad I've offered only feedback rather than code - I wish there was more I could do to help, but the UI stuff, although important to me as a desktop Puppy user, is not my area of expertise.Point taken. I did listen when you made it the first time, but I've been too wrapped up in internal infrastructure and bug squishing to get the time to fix it for you. I will have it right for Puppy 2.15CE Office Edition.
Yep. Pizza's post has the answer by example.Springer wrote:(BTW - how are you quoting other messages in your posts? Not like me, obviously...)
I don't like it much either, from the perspective of user-friendliness for refugees, but I can see how valuable it is to the young lions who rip and tear their way around the desktop at a great rate of knots. It will always be there. Only question is should it be on or off by default. The jury is still out on that.Springer wrote:Not sure I'll make the meeting (that's 4AM in Texas!), but my argument boils down to this: right-clicks, by general convention, usually bring up a context-sensitive menu. If a right click on the desktop brought up desktop setup menus or basic admin tools I wouldn't complain, (these need some consolidation in a "control panel" or the like in nearly all Linux distros, anyway), but bringing up the main menu seems both redundant and wrong...
If I had the multimedia squash file built, then they would ALL be in there. It wouldn't be a problem because it wouldn't be an integral part of the distribution, but an individual user download/add-on. That gets around the problems, AFAIK. If someone - anyone - would build that file then I could take multimedia out of Standard Edition and make it smaller; under 100Mb which was the original target.Springer wrote: If we decide we don't want to ship prop. codecs with Puppy (IMO, we should ship them anyway in Viz/Office), then at least we should make it "automagically" possible to download and install them.
Hope that explains things a bit better.