Suggestions for enhancing the porteus 2.1 Wizard

[brokenman]

How about adding a feature - when you hover over a browser logo it would pop up its version, for example Firefox 23.
This could be added (Hamza?) but again, it introduces more maintenance.

You can download other browsers here:
http://dl.porteus.org/i486/testing/Port ... 2/modules/

Updated browsers can usually be found in the modules section as they are released. I can also provide a pBuild that would automatically build the latest browser on your own machine.

[Saman]

Dear Lukas,

You can get updated version of browsers from porteus ppm (porteus package manager), meanwhile I think that porteus developers always put the latest version of browsers in wizard

[Hamza]

This could be added (Hamza?) but again, it introduces more maintenance.

If I can make it automatic then we may implement it otherwise there is no way to implement it.

I can also provide a pBuild that would automatically build the latest browser on your own machine.

Firefox pBuild?

[brokenman]

I havn't made a firefox pBuild but I have scripts for opera and chrome that can pull the latest version and build automatically. Keep in mind that any firefox pBuild must now copy the firefox.desktop file to /usr/share/applications/browser.desktop as we use this file now to call the current available browser.

[tome]

Maybe other office suites like Kingsoft Office (WPS) and OpenOffice (these are more compatible with Microsoft Office and OpenOffice 4.0 will have new feature from Lotus Symphony)
WPS is 32-bit but it works good on 64-bit. No distro (marketplace) offers these as default so Porteus can be first.
You can find something about WPS here http://mosayanvala.wordpress.com/2013/0 ... pressions/

[Hamza]

Adding too many software to wizard will make it too much complicated.

[francois]

Right keep it simple and see how good it works.

[tome]

My suggestion is to choose system locale

Code: Select all

/etc/profile.d/lang.sh

from Wizard.

@Saman
AbiWord and Gnumeric You can find in 0091-xfce-apps.xzm, try this as root (if you use x86_64, similar fo i486)

Code: Select all

httpfs2 http://ponce.cc/porteus/x86_64/archive/Porteus-v2.0-x86_64/Porteus-XFCE-v2.0-x86_64.iso /media

go to /media and open .iso with this:
/opt/porteus-scripts/context-menu/mount-iso (or /opt/porteus-scripts/context-menu/mount-module)
and copy 0091-xfce-apps.xzm wherever you want.
@brokenman
Why

Keep in mind that any firefox pBuild must now copy the firefox.desktop file to /usr/share/applications/browser.desktop as we use this file now to call the current available browser.

It can be mozilla-firefox.desktop and browser.desktop with

Code: Select all

NoDisplay=true

This would be simpler if someone use more than one browser-module.

[Gooplusplus]

What is really lacking in USB Porteus vs USB Puppy is an easy path to "persistence" file creation.

In Puppy-Racy, upon first exit the user is prompted whether to create a persistence file, what size, etc.

This "USB persistence option on first exit", IMO, would be the most useful addition to the Porteus Wizard.

[brokenman]

Hi Gooplusplus,

While you can easily setup where your changes will be saved using the Porteus Settings Centre, perhaps having a prompt upon exit could be useful. Since this resides in the Porteus 'core', perhaps Fanthom can take a look at implementing the backend and if it is feasible I can write a front end for it. Thanks for your valuable input.

[donald]

^
I don't want a OS which is talking to me, before I ask. (with a command)
KISS
no 2nd Puppy please.

[fanthom]

agree with donald - i'm always fresh user and would hate to click on a prompt every time i do a shutdown. perhaps we could sniff /proc/cmdline for 'changes=' string, then check /var/log/porteus-livedbg if changes are saved in memory and display prompt only when both conditions are true. it would still not be right if user opened 'save file manager' and created save file prior to reboot as this popup would be not necessary then.

[Gooplusplus]

^
I don't want a OS which is talking to me, before I ask. (with a command)
KISS
no 2nd Puppy please.

That is why I would make it a build "option" via the Wizard.

Along with Puppy, every known Ubuntu derivative has a USB persistence option built-in. However, unlike Puppy, the Ubuntu casper-rw persistence file should be created before usage, commonly with a simple tool like:

http://www.pendrivelinux.com/casper-rw- ... m-windows/

I will be making an "RW" series of USB multiboot collections, with one main Linux distro and one secondary Linux distro (+XBMC, etc.). Porteus KDE would have been chosen as the secondary distro in each case except that it lacks preconfigured persistence.

http://www.gooplusplus.com/multiboot-collections/ .................. example:

[donald]

@ Gooplusplus

What is really lacking in USB Porteus vs USB Puppy is an easy path to "persistence" file creation.

As brokenman said
"you can easily setup where your changes will be saved using the Porteus Settings Centre"
so I think there is no need to write and implement extra code,
just to have a big balloon telling me somewhat, before shutdown.

[Gooplusplus]

"you can easily setup where your changes will be saved using the Porteus Settings Centre"

That would be post-install and post-first-run. A distributed USB multiboot collection might be used by hundreds of people or more. Each person would have his or her own settings, wi-fi setup, etc. I don't want "my" own personal post-first-run settings saved when they may be entirely different and inappropriate for others.

An OPTION for pre-install persistence (preferably as a Build Wizard selection) would not affect anyone not adding that option. For those installing with the persistence option, a "persistence creation setup on exit" popup would be a one-time occurrence, just as it is with Puppy-Racy.