You need to add the new window manager to the /usr/bin/change-wm script.musher0 wrote:Hello again, jemimah.
Almost got stuck in flwm (hehe), until I followed your tracks back to /etc/wm, and placed "openbox-session" there. My fault, I tried to introduce good old wmx in Fluppy. And now I've put your wm chooser out of commission
So you're not using the usual Puppy .xinitrc, eh?
Second question: how do I integrate another wm than the three you suggest ?
I'm not criticizing -- you really did a fabulous job with Fluppy. I like it a lot.
It's just me being curious, and trying to get back to my old groove!
Many thanks in advance.
Fluppy 013
Flwm is not very configurable besides modifying the source code. What functions do you want?musher0 wrote:jemimah?
Two more questions, if I may:
How would I give a separate function to each of the mouse buttons in FLWM?
At present, they all display whatever is in /.wmx
How would I reinstate desktop icons on the FLWM desktop? Change or copy PuppyPin manually?
Again, thanks in advance.
And have a great day!
You can copy /root/Choices/ROX-Filer/PuppyPin.orig over /root/Choices/ROX-Filer/PuppyPin.
Why not just increase the size of the Panel?musher0 wrote:Me again...(I hear you saying: "Shucks...")
I noticed that if you change the size of the drive icons at the bottom in /usr/local/lib/X11/pixmaps, they will change for the duration of the session if you restart with xwin from console, but they won't stick for the next session, at least not from booting from a CD / DVD. True or false : this is a quirky problem, not a Fluppy problem? (I think I remember that Puppy 4.0 had the same bug.)
BFN.
This happens when the tray apps start before the icewm tray has completely loaded. I thought the delay was long enough, but I guess not.rjbrewer wrote:About half the times I boot Fluppy I get an X in the tray and a little
window in upper left of screen.
The only way to close it is by restarting X.
What is that thing?
I tried (see lines 22 and ff.), but I probably did something wrong... Please edit!jemimah wrote:You need to add the new window manager to the /usr/bin/change-wm script.musher0 wrote:Hello again, jemimah.
Almost got stuck in flwm (hehe), until I followed your tracks back to /etc/wm, and placed "openbox-session" there. My fault, I tried to introduce good old wmx in Fluppy. And now I've put your wm chooser out of commission
So you're not using the usual Puppy .xinitrc, eh?
Second question: how do I integrate another wm than the three you suggest ?
I'm not criticizing -- you really did a fabulous job with Fluppy. I like it a lot.
It's just me being curious, and trying to get back to my old groove!
Many thanks in advance.
Code: Select all
#! /bin/bash
set -x
WM=`cat /etc/windowmanager`
if [[ $WM == startflwm ]] ; then
FLWM='<default>true</default>'
else
FLWM='<default>false</default>'
fi
if [[ $WM == icewm-session ]] ; then
ICEWM='<default>true</default>'
else
ICEWM='<default>false</default>'
fi
if [[ $WM == openbox-session ]] ; then
OPENB='<default>true</default>'
else
OPENB='<default>false</default>'
fi
if [[ $WM == wmx ]] ; then
OPENB='<default>true</default>'
else
OPENB='<default>false</default>'
fi
export MAIN_DIALOG="
<window title="Change Window Manager">
<vbox>
<frame Choose a Window Manager>
<radiobutton>
<label>Flwm</label>
$FLWM
<action>if true echo startflwm > /etc/wm</action>
</radiobutton>
<radiobutton>
<label>Icewm</label>
$ICEWM
<action>if true echo icewm-session > /etc/wm</action>
</radiobutton>
<radiobutton>
<label>OpenBox</label>
$OPENB
<action>if true echo openbox-session > /etc/wm</action>
</radiobutton>
<label>wmx</label>
$WMX
<action>if true echo wmx > /etc/wm</action>
</radiobutton>
</frame>
<text><label>Changes will be applied when you restart Xwindows</label></text>
<hbox>
<button tooltip-text="Exit">
<input file stock="gtk-quit"></input>
<label>Exit</label>
<action type="exit">Exit-NOW</action>
</button>
</hbox>
</vbox>
</window>"
gtkdialog3 --program=MAIN_DIALOG --center
musher0
~~~~~~~~~~
"You want it darker? We kill the flame." (L. Cohen)
~~~~~~~~~~
"You want it darker? We kill the flame." (L. Cohen)
> Flwm is not very configurable besides modifying the source code.jemimah wrote:Flwm is not very configurable besides modifying the source code. What functions do you want?musher0 wrote:jemimah?
Two more questions, if I may:
How would I give a separate function to each of the mouse buttons in FLWM?
At present, they all display whatever is in /.wmx
How would I reinstate desktop icons on the FLWM desktop? Change or copy PuppyPin manually?
Again, thanks in advance.
And have a great day!
You can copy /root/Choices/ROX-Filer/PuppyPin.orig over /root/Choices/ROX-Filer/PuppyPin.
I see. Somewhat like wmx, eh? You can do wonders with wmx, but only if you know where the parameters are in the source.
> What functions do you want?
It would be nice to have the regular puppy menu appear on screen with a right click of the mouse.
> You can copy /root/Choices/ROX-Filer/PuppyPin.orig over /root/Choices/ROX-Filer/PuppyPin.
Ah. Thanks.
musher0
~~~~~~~~~~
"You want it darker? We kill the flame." (L. Cohen)
~~~~~~~~~~
"You want it darker? We kill the flame." (L. Cohen)
Try this:
Code: Select all
#! /bin/bash
set -x
WM=`cat /etc/windowmanager`
if [[ $WM == startflwm ]] ; then
FLWM='<default>true</default>'
else
FLWM='<default>false</default>'
fi
if [[ $WM == icewm-session ]] ; then
ICEWM='<default>true</default>'
else
ICEWM='<default>false</default>'
fi
if [[ $WM == openbox-session ]] ; then
OPENB='<default>true</default>'
else
OPENB='<default>false</default>'
fi
if [[ $WM == wmx ]] ; then
WMX='<default>true</default>'
else
WMX='<default>false</default>'
fi
export MAIN_DIALOG="
<window title=\"Change Window Manager\">
<vbox>
<frame Choose a Window Manager>
<radiobutton>
<label>Flwm</label>
$FLWM
<action>if true echo startflwm > /etc/wm</action>
</radiobutton>
<radiobutton>
<label>Icewm</label>
$ICEWM
<action>if true echo icewm-session > /etc/wm</action>
</radiobutton>
<radiobutton>
<label>OpenBox</label>
$OPENB
<action>if true echo openbox-session > /etc/wm</action>
</radiobutton>
<radiobutton>
<label>Wmx</label>
$WMX
<action>if true echo wmx > /etc/wm</action>
</radiobutton>
</frame>
<text><label>Changes will be applied when you restart Xwindows</label></text>
<hbox>
<button tooltip-text=\"Exit\">
<input file stock=\"gtk-quit\"></input>
<label>Exit</label>
<action type=\"exit\">Exit-NOW</action>
</button>
</hbox>
</vbox>
</window>"
gtkdialog3 --program=MAIN_DIALOG --center
There is a script, flwm-menu that will build the menu like that. But it depended on jwm and I haven't updated it for icewm. The ultimate problem with having multiple window managers is the time it takes to generate all the menus.musher0 wrote:
> What functions do you want?
It would be nice to have the regular puppy menu appear on screen with a right click of the mouse.
The icewm menu is not bad because it's only one file. But if you're generating a new file for each menu entry for Rox-Menu, Flwm-menu, and also creating a RoxApp for all the menu entries - well this requires some thought. The snap-merge script that saves your stuff in Pupmode 13 is really slow, and that becomes very obvious when you're trying to copy down all those files generated by the menu scripts.
I'll think about it some more.
Like in the panel that appears with FLWM? That's an idea, although I try not to have the ROX-panel "slide", 'cause it can get confusing, or you may forget what's in the off-screen section.jemimah wrote:Why not just increase the size of the Panel?musher0 wrote:Me again...(I hear you saying: "Shucks...")
I noticed that if you change the size of the drive icons at the bottom in /usr/local/lib/X11/pixmaps, they will change for the duration of the session if you restart with xwin from console, but they won't stick for the next session, at least not from booting from a CD / DVD. True or false : this is a quirky problem, not a Fluppy problem? (I think I remember that Puppy 4.0 had the same bug.)
BFN.
I finally decided to use "force" , by introducing this at line 146 of the Fluppy .xinitrc:
Code: Select all
cp -f /usr/local/lib/X11/pixmaps/dsq32x/* /usr/local/lib/X11/pixmaps
Introduces a half-second delay in the boot-up of X, but other than that, works fine.
Here's the result, in real size:
- Attachments
-
- cp-force-dsq32x-result.jpg
- (23.3 KiB) Downloaded 330 times
musher0
~~~~~~~~~~
"You want it darker? We kill the flame." (L. Cohen)
~~~~~~~~~~
"You want it darker? We kill the flame." (L. Cohen)
Would aragon's spm (simple puppy menu), based on ae menu, be suitable? Maybe simpler to implement? I mention it because it's independent of any wm existing in the Puppy: this menu is created based on the listing in /usr/share/applications.jemimah wrote:There is a script, flwm-menu that will build the menu like that. But it depended on jwm and I haven't updated it for icewm. The ultimate problem with having multiple window managers is the time it takes to generate all the menus.musher0 wrote:
> What functions do you want?
It would be nice to have the regular puppy menu appear on screen with a right click of the mouse.
The icewm menu is not bad because it's only one file. But if you're generating a new file for each menu entry for Rox-Menu, Flwm-menu, and also creating a RoxApp for all the menu entries - well this requires some thought. The snap-merge script that saves your stuff in Pupmode 13 is really slow, and that becomes very obvious when you're trying to copy down all those files generated by the menu scripts.
I'll think about it some more.
In any case, the role of the programmer is not to cater to every user's whim of fancy, ( Specially mine! I'm already too much of an individualist ! )
Maybe just give pointers as to how this ot that can be done in the environment you chose to provide initially.
BFN.
Last edited by musher0 on Sun 27 Jun 2010, 16:44, edited 1 time in total.
musher0
~~~~~~~~~~
"You want it darker? We kill the flame." (L. Cohen)
~~~~~~~~~~
"You want it darker? We kill the flame." (L. Cohen)
Yes, it can be done, but there are 2-3 limitations:jemimah wrote:If you have that problem, just decrease the percentage the taskbar takes.musher0 wrote:
Like in the panel that appears with FLWM? That's an idea, although I try not to have the ROX-panel "slide", 'cause it can get confusing, or you may forget what's in the off-screen section.
1) the smallest width of the ROX panel is 16 pixels.
2) if you have rox applets displayed in the panel, the panel will only shrink to the smallest width allowed by the applet. This supercedes #1 above.
3) Finally, readability by the human operator... If it's too small, it's of no use. (Well, the identification bubbles still pop up, but still, it's awfully small for human eyes.)
musher0
~~~~~~~~~~
"You want it darker? We kill the flame." (L. Cohen)
~~~~~~~~~~
"You want it darker? We kill the flame." (L. Cohen)
Hello again. jemimah.
When I launch the panel under wmx (it doesn't have one by default), thus:
I get:
Is this error of any consequence?
Thanks in advance.
BFN.
When I launch the panel under wmx (it doesn't have one by default), thus:
Code: Select all
rox -b=/root/Choices/ROX-Filer/OpenboxPanel
Code: Select all
/usr/local/apps/ROX-Filer/ROX-Filer: /usr/lib/libxml2.so.2: no version information available (required by /usr/local/apps/ROX-Filer/ROX-Filer)
Thanks in advance.
BFN.
musher0
~~~~~~~~~~
"You want it darker? We kill the flame." (L. Cohen)
~~~~~~~~~~
"You want it darker? We kill the flame." (L. Cohen)
I used to see the same thing with earlier4.xx Puppies. (freememaplet)jemimah wrote:This happens when the tray apps start before the icewm tray has completely loaded. I thought the delay was long enough, but I guess not.rjbrewer wrote:About half the times I boot Fluppy I get an X in the tray and a little
window in upper left of screen.
The only way to close it is by restarting X.
What is that thing?
May be the reason for no freememaplet showing on my Fluppy full
installs.
Inspiron 700m, Pent.M 1.6Ghz, 1Gb ram.
Msi Wind U100, N270 1.6>2.0Ghz, 1.5Gb ram.
Eeepc 8g 701, 900Mhz, 1Gb ram.
Full installs
Should be.
Code: Select all
cat /proc/cpuinfo|grep processor
Thank you.jemimah wrote:Should be.
Code: Select all
cat /proc/cpuinfo|grep processor
Inspiron 700m, Pent.M 1.6Ghz, 1Gb ram.
Msi Wind U100, N270 1.6>2.0Ghz, 1.5Gb ram.
Eeepc 8g 701, 900Mhz, 1Gb ram.
Full installs