Closed 01micko closed 3 years ago
I have edited and added some /usr/local/bin/default* files
This is how my defaultwordprocessor looks like:
#!/bin/sh
if which wps &>/dev/null ; then # kingsoft office
exec wps "$@"
fi
if which abiword &>/dev/null ; then
exec abiword "$@"
fi
yad --title="Error" --image="dialog-error" --button="OK":0 \
--text="There's no program to handle this file, install Kingsoft Office" \
--center --on-top --fixed --sticky --borders="4" && exit 1
Basically it just notifies the user there is no defaultwordprocessor
This is my 'defaultrun'
#!/bin/sh
#arch compat
[ ! "$DISPLAY" ] && exit
# generic
if which gmrun &>/dev/null ; then
exec gmrun
fi
# lxde
if pidof lxpanel &>/dev/null ; then
exec lxpanelctl run
fi
if pidof lxpanelx &>/dev/null ; then
exec lxpanelxctl run
fi
# xfce
if which xfce4-appfinder &>/dev/null ; then
exec xfce4-appfinder
fi
# kde
if which krunner &>/dev/null ; then
exec krunner
fi
# gtkdialog - prun
if which prun &>/dev/null ; then
exec prun
fi
# yad
if which yad &>/dev/null ; then
exe=$(yad --center --title "Run" --entry --window-icon=/usr/share/pixmaps/run48.png)
[ "$exe" ] && exec $exe
fi
# extra
if which lxterminal &>/dev/null ; then
exec lxterminal
fi
if which xterm &>/dev/null ; then
exec xterm
fi
### END ###
This is a generic way to run whatever program is installed
.jwmrc [Key mask="4" key="r"]exec:defaultrun[/Key]
So when I press Win+R, it will pop up something
Sorry about commenting on an "old" issue. But couldn't this be implemented with an adrv? If all the "optional" apps and all their supporting fles are in an adrv then, with an adrv you get a normal puppy, without an adrv you get a minimal puppy. There could also be alternate adrv's with different application collections.
It probably needs some changes to the format of DISTRO_PKGS_SPECS-* to indicate which items should go into the adrv
I'm doing an embryo version of this in LxPupSc with the browser in an adrv - but manual intervention during 3builddistro-Z is needed....
On 04/06/16 12:54, gyrog wrote:
Sorry about commenting on an "old" issue. But couldn't this be implemented with an adrv? If all the "optional" apps and all their supporting fles are in an adrv then, with an adrv you get a normal puppy, without an adrv you get a minimal puppy. There could also be alternate adrv's with different application collections.
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/puppylinux-woof-CE/woof-CE/issues/623#issuecomment-223751667, or mute the thread https://github.com/notifications/unsubscribe/AFpv0cavDRd3NTF5_sQFzbimHedKlBD5ks5qIWeQgaJpZM4GZbWB.
I think this one is fixed, sort of. Most broken root-skeleton applications and menu entries are deleted by 3builddistro now, there's a minimal pinboard layout, and it's easy to build a minimal Puppy by removing all applications from DISTRO_PKGS_SPECS and letting petbuild build just the core set of applications (optionally, put them in adrv).
@dimkr closed the issue #619 about removing CUPS but we really should support a minimal install. Even without X, but that is probably only
possiblepractical after we boot Xorgwizard (#583).CUPS, browser, defaultwordprocessor, defaultmediaplayer, defaultspreadsheet etc should be made optional.
Apart from wizard detection of such, the PuppyPin (usually part of rox-filer package) would need to be edited on the fly if the default set out is used.