COMP 3000 2011 Report: Macpup - Revision history

Rcarrot1: /* Software Packaging */

2011-12-17T08:58:48Z

Software Packaging

← Older revision		Revision as of 08:58, 17 December 2011
Line 104:		Line 104:

	[[File:Ppm-dependencies.png\|thumb\|left\|Puppy Package Manager checks for dependencies]]		[[File:Ppm-dependencies.png\|thumb\|left\|Puppy Package Manager checks for dependencies]]

			In versions [http://macpup.org/macpup411.php 411] and [http://macpup.org/macpup412.php 412] of Macpup a tool called Petch was included. Petch was a command line installer made for Puppy Linux by a developer that went by the alias tombh. It would search through several online repositories for the package that you were trying to find, return a list of matches that it found, ask you if you'd like to download one of the packages it found, and then offer to install the package for you<ref>Last modified December 17, 2011, "[http://208.109.22.214/puppy/viewtopic.php?t=33436&sid=2fa098b0cbc8e23777e68f000832d95e Puppy Linux Discussion Forum:: View Topic - Petch-0.3.pet -- CLI Puppy repository search and install]", accessed on December-17-2011</ref>. Unfortunately, about a month and a half after its release, tombh posted that he would no longer be supporting Petch and was beginning to move away from Puppy Linux in general<ref>Last modified December 17, 2011, "[http://www.murga-linux.com/puppy/viewtopic.php?p=244608#244608 Puppy Linux Discussion Forum:: View Topic - About tombh]", accessed on December-17-2011</ref>. There is no mention of Petch appearing in Macpup past version 412, and it is not included in Macpup 528 which we are working with.

	In version 5 of Puppy Linux a new package manager called Quick Pet was introduced, it is an easy to use, cut-down version of the full featured Puppy Package Manager (PPM) <ref name="lucid">Last modified November 8, 2011, "[http://puppylinux.org/wikka/lucidpuppyquickpet PuppyLinux: Quickpet]", accessed on November-8-2011</ref>. Both Quick Pet and the PPM are included in Macpup 528. Quick Pet highlights some of the most popular software available for Puppy, organized by category (popular pets, internet pets, useful pets, sfs gets, and drivers), and allows for one click installations <ref name="lucid"/>. SFS files that are downloaded through Quick Pet’s SFS Grabber utility get automatically installed. The alternative way to manually install these files is to download them, place them in /mnt/home, and then follow the instructions in the BootManager to add the SFS file to the boot up sequence <ref name="sfs"/>.		In version 5 of Puppy Linux a new package manager called Quick Pet was introduced, it is an easy to use, cut-down version of the full featured Puppy Package Manager (PPM) <ref name="lucid">Last modified November 8, 2011, "[http://puppylinux.org/wikka/lucidpuppyquickpet PuppyLinux: Quickpet]", accessed on November-8-2011</ref>. Both Quick Pet and the PPM are included in Macpup 528. Quick Pet highlights some of the most popular software available for Puppy, organized by category (popular pets, internet pets, useful pets, sfs gets, and drivers), and allows for one click installations <ref name="lucid"/>. SFS files that are downloaded through Quick Pet’s SFS Grabber utility get automatically installed. The alternative way to manually install these files is to download them, place them in /mnt/home, and then follow the instructions in the BootManager to add the SFS file to the boot up sequence <ref name="sfs"/>.

Kbyrd: /* Basic Operation */

2011-12-17T08:41:13Z

Basic Operation

← Older revision		Revision as of 08:41, 17 December 2011
Line 83:		Line 83:
	To install an application first open Quickpet or Puppy Package Manager. We chose to test the installation of Skype and VLC media player. In Puppy Package Manager you can navigate your way through each category of package or enter a query in the "Find" text field below. Once you found the desired application package to install, just click on it and the PPM will download and install it for you, it's that simple! Quickpet offers a list of some of the more popular applications, and provides a simple click and install process similar to that of PPM. After successfully installing our applications we tested a .mkv video file in VLC media player, and tested a few Skype calls and they both seemed to perform quite well in comparison to other OS versions.		To install an application first open Quickpet or Puppy Package Manager. We chose to test the installation of Skype and VLC media player. In Puppy Package Manager you can navigate your way through each category of package or enter a query in the "Find" text field below. Once you found the desired application package to install, just click on it and the PPM will download and install it for you, it's that simple! Quickpet offers a list of some of the more popular applications, and provides a simple click and install process similar to that of PPM. After successfully installing our applications we tested a .mkv video file in VLC media player, and tested a few Skype calls and they both seemed to perform quite well in comparison to other OS versions.

			[[File:Macpup-installing-programs.PNG\|thumb\|right\|Installing VLC and Skype]]
	[[File:QuickPet.PNG\|thumb\|right\|Quickpet Download Package Manager ]]		[[File:QuickPet.PNG\|thumb\|right\|Quickpet Download Package Manager ]]

Kbyrd: /* Basic Operation */

2011-12-17T08:37:46Z

Basic Operation

← Older revision		Revision as of 08:37, 17 December 2011
Line 81:		Line 81:
	With Puppy Linux having binary-compatibility with Ubuntu Lucid Lyncpackages Macpup 5.28 contains all the apps from Lucid Puppy with the addition of Firefox 7.01 beta. Additional apps such as Opera, Skype, Open Office, Virtual Box, Adobe Reader, and many driver updates are also available using the Quickpet App on the ibar or the Puppy Package Manager.		With Puppy Linux having binary-compatibility with Ubuntu Lucid Lyncpackages Macpup 5.28 contains all the apps from Lucid Puppy with the addition of Firefox 7.01 beta. Additional apps such as Opera, Skype, Open Office, Virtual Box, Adobe Reader, and many driver updates are also available using the Quickpet App on the ibar or the Puppy Package Manager.

	To install an application...		To install an application first open Quickpet or Puppy Package Manager. We chose to test the installation of Skype and VLC media player. In Puppy Package Manager you can navigate your way through each category of package or enter a query in the "Find" text field below. Once you found the desired application package to install, just click on it and the PPM will download and install it for you, it's that simple! Quickpet offers a list of some of the more popular applications, and provides a simple click and install process similar to that of PPM. After successfully installing our applications we tested a .mkv video file in VLC media player, and tested a few Skype calls and they both seemed to perform quite well in comparison to other OS versions.

	[[File:QuickPet.PNG\|thumb\|right\|Quickpet Download Package Manager ]]		[[File:QuickPet.PNG\|thumb\|right\|Quickpet Download Package Manager ]]

Rcarrot1: /* Initialization */

2011-12-17T08:27:38Z

Initialization

← Older revision		Revision as of 08:27, 17 December 2011
Line 230:		Line 230:

	==Initialization==		==Initialization==
	~~While searching for some information on how Macpup starts up we found a few different pages that all seemed~~ to ~~describe different methods~~ of the ~~OS booting up. We finally came across~~ a ~~[http://thinkbeenet.blogspot.com/2010/04/puppy-boot-process.html blog post]~~ with ~~information on what scripts are started upon bootup~~. ~~After examining the files within Macpup~~ we ~~found~~ the ~~blog to be accurate and we've expanded on the information given there below. Most~~ of ~~the information was found by reading the script comments and README files~~ that ~~were included in most directories~~.		One of Macpup’s defining attributes is its ability to run completely in RAM, and run very quickly. One of the ways it’s managed to achieve this is by having the initialization sequence start a very minimum essential set of services that most users would not want to tamper with. Below we will describe the majority of processes that are running after booting into Macpup.

	The ~~initialization sequence~~ for ~~Macpup uses~~ the ~~same boot process as its parent distribution, Puppy Linux, does~~. ~~Initialization~~ is ~~a bit different depending on whether you are booting~~ Macpup ~~from a live CD or from a full install~~ on ~~a hard drive. We are going to cover~~ the ~~boot process~~ for ~~a full install of Macpup~~. ~~The boot~~ process ~~begins with the bootloader launching the kernel~~. ~~The kernel then runs~~ the script /sbin/init. ~~This script first checks to see if~~ the ~~file “/fsckme.flg” exists. If it~~ does, ~~then a filesystem check needs to be run before proceeding any further~~. ~~The script will then create a ramdisk and populate it with a Linux environment~~. /~~sbin~~/init ~~then calls the script /etc/rc~~.d/~~rc.sysinit~~ which ~~first makes the filesystem useable~~.		Busybox is a program that combines tiny versions of many common UNIX utilities into a single small executable <ref name="aboutbusy" />. The tradeoff for this is that the utilities typically have fewer features than their full featured counterparts. Busybox is included in Macpup and is one of the first programs to be run during initialization. A stripped down version of ‘init’, the parent of all processes on the system which is responsible for starting all other processes<ref>Last modified December 17, 2011 "[http://linux.die.net/man/8/init init(8): Upstart process management daemon - Linux man page]", accessed on December-17-2011</ref>, is included in Busybox. It is executed in the first script run on Macpup, /sbin/init. It should be noted that the Busybox version of init does not support run levels<ref>Last modified March 08, 2006 "[http://spblinux.de/2.0/doc/init.html init]", accessed on December-17-2011</ref>, which is why Macpup does not support them.

	~~The sysinit script then calls~~ /etc/rc.d/rc.~~update~~. ~~The purpose of this script is~~ to ~~perform any required updates to files when~~ a ~~new version~~ of ~~Macpup is booted~~. ~~Scripts are also called from~~ the ~~update script to clean up any obsolete files from older versions of~~ Macpup, ~~or old .pet packages~~.		Another important part of initialization is starting X, which is done at the end of the /etc/profile script. X is a protocol that provides the basis for a graphical user interface and rich input device capability for networked computers<ref name="xwiki">Last modified December 17, 2011 "[http://en.wikipedia.org/wiki/X_Window_System X Window System - Wikipedia, the free encyclopedia]", accessed on December-17-2011</ref>. It creates a hardware abstraction layer so that software can be written to use a generalized set of commands, which allows for device independence<ref name="xwiki" />. Enlightenment, the default window manager for Macpup, is run on top of X.

	~~Back in the sysinit script, some kernel modules are loaded, and then any extra modules that the user~~ has specified in the BootManager are loaded. Next we move on to setting up services such as printing and networking. The scripts /etc/rc.d/network and /etc/rc.d/services are called. The services script will run all executable scripts found in /etc/init.d with the command line parameter “start”. Here are some notes on some particular services that are started ~~from~~ the ~~init~~.~~d directory:~~		Macpup also has several other important daemons that are started during the initialization sequence. The ‘cupsd’ daemon is started, which is required for printing<ref>Last modified December 17, 2011 "[ http://www.manpagez.com/man/8/cupsd/ man page cupsd section 8]", accessed on December-17-2011</ref>. This daemon can be disabled if you don’t need to print, however it doesn’t use much memory so leaving it running isn’t going to have any real negative effects. The messagebus daemon, ‘dbusd’, is also started. This daemon allows applications to communicate between each other<ref>Last modified December 17, 2011 "[http://linux.die.net/man/1/dbus-daemon-1 dbus-daemon-1(1): Message bus daemon - Linux man page]", accessed on December-17-2011</ref>. Only certain applications make use of this daemon, and most derivatives of Puppy Linux are built with applications that don’t. It’s still recommended that you leave this daemon enabled unless you’re sure that no applications require it. The sys_logger is executed, which starts the daemons ‘syslogd’ and ‘klogd’. These daemons log kernel and application events (especially error messages) to various log files, mainly /var/log/messages<ref>Last modified December 17, 2011 "[http://unixhelp.ed.ac.uk/CGI/man-cgi?syslogd+8 UNIX man pages: syslogd(8)]", accessed on December-17-2011</ref><ref>Last modified December 17, 2011 "[http://linux.die.net/man/8/klogd klogd(8):Kernel Log Daemon - Linux man pages]", accessed on December-17-2011</ref>. Finally, udev is executed, which starts the ‘udevd’ and ‘pup_event_frontend_d’ daemons. The purpose of these daemons is to receive information from the kernel about hardware events, such as a USB device being plugged in or removed. Macpup will still run without these daemons enabled, and disabling them will save a considerable amount of CPU usage and resources.

	~~'''cups:'''~~
	~~This runs the CUPS~~ daemon ~~‘cupsd’~~, required for printing. <ref>Last modified ~~November 10~~, 2011 "[http://www.manpagez.com/man/8/cupsd/ man page cupsd section 8]", accessed on ~~November~~-10-2011</ref>

	~~'''messagebus:'''~~
	This ~~runs the ‘dbusd’~~ daemon. ~~DBUS~~ is ~~a method for~~ applications to communicate ~~with~~ each other <ref>Last modified ~~November 10~~, 2011 "[http://linux.die.net/man/1/dbus-daemon-1 dbus-daemon-1: Message bus daemon - Linux man page]", accessed on ~~November~~-10-2011</ref>. Only certain applications use this, and most Puppy ~~distributions~~ are built with ~~apps~~ that don’t.

	~~'''~~sys_logger~~:'''~~
	~~This runs~~ the daemons ‘syslogd’ and ‘klogd’~~, which~~ log kernel and application events (especially error messages) to various log files, ~~mostly to~~ /var/log/messages <ref>Last modified ~~November 10~~, 2011 "[http://unixhelp.ed.ac.uk/CGI/man-cgi?syslogd+8 UNIX man pages: syslogd(8)]", accessed on ~~November~~-10-2011</ref><ref>Last modified ~~November 10~~, 2011 "[http://linux.die.net/man/8/klogd ~~UNIX~~ klogd(8): Kernel Log Daemon - Linux man ~~page~~]", accessed on ~~November~~-10-2011</ref>~~<ref>Last modified November 10, 2011 "[http://bkhome~~.~~org/blog/?viewDetailed=01355 Barry Kauler - Powered by PPLOG]"~~, ~~accessed on November-10-2011</ref>.~~

	~~'''~~udev~~:'''~~
	~~Runs~~ the ~~daemons~~ ‘udevd’ and ~~‘pup_even_frontend_d’~~. ~~This~~ is ~~a mechanism that receives hardware event~~ from the kernel, such as a USB ~~drive~~ being plugged in or removed. ~~‘udevd’ is essential during bootup. However after bootup the~~ daemons ~~can be killed~~, ~~which actually saves quite a bit~~ a CPU usage and resources.

	Most Linux distributions would have runlevels that give an order to which services start in which order. Macpup and Puppy Linux do not have run levels, and run a very minimum essential set of services.

	Finally, back in /etc/rc.d/rc.sysinit, we have a few more tasks to finish up. The script discovers media devices such as CD drives, mice, and keyboards, and also runs the script /etc/rc.d/rc.country which asks for the keyboard layout. The script rc.local is also called, which is simply the line “modprobe fbcon”. This gets you a framebuffer console <ref>Last modified November 10, 2011 "[http://www.kernel.org/doc/Documentation/fb/fbcon.txt http://www.kernel.org/doc/Documentation/fb/fbcon.txt]", accessed on November-10-2011</ref>. This is the end of the sysinit script, from here we head to the /etc/profile script.

	The profile script evaluates all the files in the /etc/profile.d directory. The usual purpose for these files is to set environment variables for a particular package. Finally the profile script will start X (which provides an interface for GUIs <ref>Last modified November 10, 2011 "[http://en.wikipedia.org/wiki/X_Window_System X Window System - Wikipedia]", accessed on November-10-2011</ref>). When X starts it runs /root/.xinitrc, which will start any file in /root/Startup. After .xinitrc has finished running, the windowmanager is started and the user is in control.

	= References =		= References =
	<references />		<references />

Rcarrot1: /* BusyBox */

2011-12-17T08:07:38Z

BusyBox

← Older revision		Revision as of 08:07, 17 December 2011
Line 199:		Line 199:

	===BusyBox===		===BusyBox===
	Macpup includes BusyBox version 1.16.2 which was released on June 12th 2010<ref name = "busybox" >Last modified November 9, 2011, "[http://busybox.net/ BusyBox]", accessed on November-09-2011</ref>. The latest stable build as of November 9th 2011 is version 1.19.3 which was released on October 29th 2011<ref name = "busybox" >Last modified November 9, 2011, "[http://busybox.net/ BusyBox]", accessed on November-09-2011</ref>. The version of BusyBox that is included in Macpup hasn’t been modified by the distribution authors at all. BusyBox combines tiny versions of many common UNIX utilities into a single small executable and provides replacements for most of the utilities you usually find in GNU fileutils, shellutils, etc<ref>Last modified November 9, 2011, "[http://busybox.net/about.html About BusyBox]", accessed on November-09-2011</ref>. Having all these small utilities combined into a small executable is most likely why this particular package was chosen for Macpup’s standard installation.		Macpup includes BusyBox version 1.16.2 which was released on June 12th 2010<ref name = "busybox" >Last modified November 9, 2011, "[http://busybox.net/ BusyBox]", accessed on November-09-2011</ref>. The latest stable build as of November 9th 2011 is version 1.19.3 which was released on October 29th 2011<ref name = "busybox" >Last modified November 9, 2011, "[http://busybox.net/ BusyBox]", accessed on November-09-2011</ref>. The version of BusyBox that is included in Macpup hasn’t been modified by the distribution authors at all. BusyBox combines tiny versions of many common UNIX utilities into a single small executable and provides replacements for most of the utilities you usually find in GNU fileutils, shellutils, etc<ref name="aboutbusy">Last modified November 9, 2011, "[http://busybox.net/about.html About BusyBox]", accessed on November-09-2011</ref>. Having all these small utilities combined into a small executable is most likely why this particular package was chosen for Macpup’s standard installation.

	===ROXTerm===		===ROXTerm===

Kbyrd: /* Installing Applications */

2011-12-17T07:14:48Z

Installing Applications

← Older revision		Revision as of 07:14, 17 December 2011
Line 80:		Line 80:
	====Installing Applications====		====Installing Applications====
	With Puppy Linux having binary-compatibility with Ubuntu Lucid Lyncpackages Macpup 5.28 contains all the apps from Lucid Puppy with the addition of Firefox 7.01 beta. Additional apps such as Opera, Skype, Open Office, Virtual Box, Adobe Reader, and many driver updates are also available using the Quickpet App on the ibar or the Puppy Package Manager.		With Puppy Linux having binary-compatibility with Ubuntu Lucid Lyncpackages Macpup 5.28 contains all the apps from Lucid Puppy with the addition of Firefox 7.01 beta. Additional apps such as Opera, Skype, Open Office, Virtual Box, Adobe Reader, and many driver updates are also available using the Quickpet App on the ibar or the Puppy Package Manager.

			To install an application...

	[[File:QuickPet.PNG\|thumb\|right\|Quickpet Download Package Manager ]]		[[File:QuickPet.PNG\|thumb\|right\|Quickpet Download Package Manager ]]

Kbyrd: /* Basic Operation */

2011-12-17T07:09:57Z

Basic Operation

← Older revision		Revision as of 07:09, 17 December 2011
Line 56:		Line 56:

	If you’re careful with your memory usage Macpup does perform very well however. We installed Thunderbird and had it running along with Opera and a few other pre-installed applications that come with Macpup and had no slowdowns, which we feel is a pretty standard session for many users. Despite the problems we ran into we still think Macpup does perform very well even with limited resources, newer versions of Windows simply wouldn’t run on that little RAM and the older ones would allow far less usability than what we experienced with Macpup.		If you’re careful with your memory usage Macpup does perform very well however. We installed Thunderbird and had it running along with Opera and a few other pre-installed applications that come with Macpup and had no slowdowns, which we feel is a pretty standard session for many users. Despite the problems we ran into we still think Macpup does perform very well even with limited resources, newer versions of Windows simply wouldn’t run on that little RAM and the older ones would allow far less usability than what we experienced with Macpup.

	~~===Customization===~~

	[[File:Enlightenment_Screenshot.jpg\|thumb\|right\|Macpup with Enlightenment E17]]		[[File:Enlightenment_Screenshot.jpg\|thumb\|right\|Macpup with Enlightenment E17]]
Line 65:		Line 63:
	With Enlightenment being Macpups default Window Manager we decided to play around with a lot more of it's features compared to Joe's Window Manager (JWM). One of our favourite features was the ability to set Virtual Desktops. Virtual desktops allow you to create a grid of different workspaces which can easily be accessed through the ibar. To set multiple virtual desktops is a quick task. First click on the Macpup main menu, and choose "Desktop" then "Virtual" and then click on "Set Virtual Desktops". This will open the Virtual Desktop Settings window. Next drag the vertical and horizontal sliders to add the desired amount of virtual desktops, and then click apply and you're done!		With Enlightenment being Macpups default Window Manager we decided to play around with a lot more of it's features compared to Joe's Window Manager (JWM). One of our favourite features was the ability to set Virtual Desktops. Virtual desktops allow you to create a grid of different workspaces which can easily be accessed through the ibar. To set multiple virtual desktops is a quick task. First click on the Macpup main menu, and choose "Desktop" then "Virtual" and then click on "Set Virtual Desktops". This will open the Virtual Desktop Settings window. Next drag the vertical and horizontal sliders to add the desired amount of virtual desktops, and then click apply and you're done!

	[[File:~~Macpup_Custom_Theme2~~.PNG ‎\|thumb\|right\|Macpup with MPClub Theme Installed]]		[[File:Macpup_Custom_Theme.PNG ‎\|thumb\|right\|Macpup with MPClub Theme Installed]]

	Next we decided to see what else we could change about the appearance. While reading the guide on E17 customization [http://hardkap.net/forums/topic/e17-guide here], we came across a catchy looking theme pack called MPClub by Agust and runtt21. You can download it [http://macpup.org/runtt21/files/MP511-MPClub-1.pet here.] Once downloaded, you can open the file with the puppy package manager and it will install it. The next step is to set the new installed theme. You can do this by selecting “Settings” in the main menu, then selecting “Theme”. This will open the Theme Selector window which will allow you to select between system and personal installed themes. We want to select “Personal”, and then select the MPClub theme and click apply.		Next we decided to see what else we could change about the appearance. While reading the guide on E17 customization [http://hardkap.net/forums/topic/e17-guide here], we came across a catchy looking theme pack called MPClub by Agust and runtt21. You can download it [http://macpup.org/runtt21/files/MP511-MPClub-1.pet here.] Once downloaded, you can open the file with the puppy package manager and it will install it. The next step is to set the new installed theme. You can do this by selecting “Settings” in the main menu, then selecting “Theme”. This will open the Theme Selector window which will allow you to select between system and personal installed themes. We want to select “Personal”, and then select the MPClub theme and click apply.

Kbyrd: /* Customization */

2011-12-17T07:05:47Z

Customization

← Older revision		Revision as of 07:05, 17 December 2011
Line 63:		Line 63:
	Macpup provides two window managers to choose from:		Macpup provides two window managers to choose from:
	=====1. Enlightenment E17=====		=====1. Enlightenment E17=====
	With Enlightenment being Macpups default Window Manager we decided to play around with a lot more of it's features compared to Joe's Window Manager (JWM). One of our favourite features was the ability to set Virtual Desktops. Virtual desktops allow you to create a grid of different workspaces which can easily be accessed through the ibar. To set multiple virtual desktops is a quick task. First click on the Macpup main menu, and choose "Desktop" then "Virtual" and then click on "Set Virtual Desktops". This will open the Virtual Desktop Settings window, drag the vertical and horizontal sliders to add the desired amount of virtual desktops, and click apply.		With Enlightenment being Macpups default Window Manager we decided to play around with a lot more of it's features compared to Joe's Window Manager (JWM). One of our favourite features was the ability to set Virtual Desktops. Virtual desktops allow you to create a grid of different workspaces which can easily be accessed through the ibar. To set multiple virtual desktops is a quick task. First click on the Macpup main menu, and choose "Desktop" then "Virtual" and then click on "Set Virtual Desktops". This will open the Virtual Desktop Settings window. Next drag the vertical and horizontal sliders to add the desired amount of virtual desktops, and then click apply and you're done!

	[[File:Macpup_Custom_Theme2.PNG ‎\|thumb\|right\|Macpup with MPClub Theme Installed]]		[[File:Macpup_Custom_Theme2.PNG ‎\|thumb\|right\|Macpup with MPClub Theme Installed]]
Line 71:		Line 71:
	After successfully changing our theme, we wanted to have different wallpapers setup on our different virtual desktops that we added earlier. To do this, click “Settings” in the main menu then select “Wallpaper”. Click on the “advanced” button and select “This Desktop” under where to place the wallpaper and click apply. Next change to a different virtual desktop and repeat the same process but this time change the wallpaper to a different image. You can do this for all the virtual desktops that you have enabled!		After successfully changing our theme, we wanted to have different wallpapers setup on our different virtual desktops that we added earlier. To do this, click “Settings” in the main menu then select “Wallpaper”. Click on the “advanced” button and select “This Desktop” under where to place the wallpaper and click apply. Next change to a different virtual desktop and repeat the same process but this time change the wallpaper to a different image. You can do this for all the virtual desktops that you have enabled!

	‎[[File:Macpup_Custom_Desktops.PNG \|thumb\|right\|~~Macpup with JWM~~]]		[[File:Setting_Virtual_Desktops_2.PNG\|thumb\|left\|Setting Virtual Desktops]]

			‎[[File:Macpup_Custom_Desktops.PNG \|thumb\|right\|Custom wallpapers set on Virtual Desktops]]

	[[File:JWM_Screenshot.PNG\|thumb\|right\|Macpup with JWM]]		[[File:JWM_Screenshot.PNG\|thumb\|right\|Macpup with JWM]]
Line 77:		Line 79:
	=====2. JWM=====		=====2. JWM=====
	JWM is a lightweight stacking window manager written by Joe Wingbermuehle. It provides an interface similar to Windows 98 with a modern-looking appearance. <ref>Last modified October 15, 2011, "[http://www.joewing.net/programs/jwm/ joewing.net \| JWM (Joe's Window Manager)]", accessed on October-15-2011</ref>		JWM is a lightweight stacking window manager written by Joe Wingbermuehle. It provides an interface similar to Windows 98 with a modern-looking appearance. <ref>Last modified October 15, 2011, "[http://www.joewing.net/programs/jwm/ joewing.net \| JWM (Joe's Window Manager)]", accessed on October-15-2011</ref>

	~~[[File:Setting_Virtual_Desktops_2.PNG\|thumb\|left\|Setting Virtual Desktops]]~~

	====Installing Applications====		====Installing Applications====

Kbyrd: /* Customization */

2011-12-17T07:01:53Z

Customization

← Older revision		Revision as of 07:01, 17 December 2011
Line 63:		Line 63:
	Macpup provides two window managers to choose from:		Macpup provides two window managers to choose from:
	=====1. Enlightenment E17=====		=====1. Enlightenment E17=====
	With Enlightenment being Macpups default Window Manager we decided to play around with a lot more of it's features compared to Joe's Window Manager (JWM). One of our favourite features was the ability to set Virtual Desktops. Virtual desktops allow you to create a grid of different workspaces which can easily be accessed through the ibar.		With Enlightenment being Macpups default Window Manager we decided to play around with a lot more of it's features compared to Joe's Window Manager (JWM). One of our favourite features was the ability to set Virtual Desktops. Virtual desktops allow you to create a grid of different workspaces which can easily be accessed through the ibar. To set multiple virtual desktops is a quick task. First click on the Macpup main menu, and choose "Desktop" then "Virtual" and then click on "Set Virtual Desktops". This will open the Virtual Desktop Settings window, drag the vertical and horizontal sliders to add the desired amount of virtual desktops, and click apply.

	[[File:Macpup_Custom_Theme2.PNG ‎\|thumb\|right\|Macpup with MPClub Theme Installed]]		[[File:Macpup_Custom_Theme2.PNG ‎\|thumb\|right\|Macpup with MPClub Theme Installed]]

	~~As Enlightenment claims to be highly customizable,~~ we ~~first~~ decided to see what we could change about the appearance. While reading the guide on E17 customization [http://hardkap.net/forums/topic/e17-guide here], we came across a catchy looking theme pack called MPClub by Agust and runtt21. You can download it [http://macpup.org/runtt21/files/MP511-MPClub-1.pet here.] Once downloaded, you can open the file with the puppy package manager and it will install it. The next step is to set the new installed theme. You can do this by selecting “Settings” in the main menu, then selecting “Theme”. This will open the Theme Selector window which will allow you to select between system and personal installed themes. We want to select “Personal”, and then select the MPClub theme and click apply.		Next we decided to see what else we could change about the appearance. While reading the guide on E17 customization [http://hardkap.net/forums/topic/e17-guide here], we came across a catchy looking theme pack called MPClub by Agust and runtt21. You can download it [http://macpup.org/runtt21/files/MP511-MPClub-1.pet here.] Once downloaded, you can open the file with the puppy package manager and it will install it. The next step is to set the new installed theme. You can do this by selecting “Settings” in the main menu, then selecting “Theme”. This will open the Theme Selector window which will allow you to select between system and personal installed themes. We want to select “Personal”, and then select the MPClub theme and click apply.

	After successfully changing our theme, we wanted to have different wallpapers setup on different virtual desktops. To do this, click “Settings” in the main menu then select “Wallpaper”. Click on the “advanced” button and select “This Desktop” under where to place the wallpaper and click apply. Next change to a different virtual desktop and repeat the same process but this time change the wallpaper to a different image. You can do this for all the virtual desktops that you have enabled!		After successfully changing our theme, we wanted to have different wallpapers setup on our different virtual desktops that we added earlier. To do this, click “Settings” in the main menu then select “Wallpaper”. Click on the “advanced” button and select “This Desktop” under where to place the wallpaper and click apply. Next change to a different virtual desktop and repeat the same process but this time change the wallpaper to a different image. You can do this for all the virtual desktops that you have enabled!

			‎[[File:Macpup_Custom_Desktops.PNG \|thumb\|right\|Macpup with JWM]]

	[[File:JWM_Screenshot.PNG\|thumb\|right\|Macpup with JWM]]		[[File:JWM_Screenshot.PNG\|thumb\|right\|Macpup with JWM]]

Kbyrd: /* 1. Enlightenment E17 */

2011-12-17T06:52:05Z

1. Enlightenment E17

← Older revision		Revision as of 06:52, 17 December 2011
Line 63:		Line 63:
	Macpup provides two window managers to choose from:		Macpup provides two window managers to choose from:
	=====1. Enlightenment E17=====		=====1. Enlightenment E17=====
	With Enlightenment being Macpups default Window Manager we decided to play around with a lot more of it's features compared to Joe's Window Manager (JWM). One of our favourite features was the ability to set Virtual Desktops. Virtual desktops allow you to create a grid of different workspaces which can easily be accessed through the ibar. ~~For more information on customizing Enlightenment you can checkout the guide~~		With Enlightenment being Macpups default Window Manager we decided to play around with a lot more of it's features compared to Joe's Window Manager (JWM). One of our favourite features was the ability to set Virtual Desktops. Virtual desktops allow you to create a grid of different workspaces which can easily be accessed through the ibar.


	[[File:Macpup_Custom_Theme2.PNG ‎\|thumb\|right\|Macpup with MPClub Theme Installed]]		[[File:Macpup_Custom_Theme2.PNG ‎\|thumb\|right\|Macpup with MPClub Theme Installed]]