fanthom wrote:kdialog is good looking and functional but i would vote for console as more universal solution. LXDE users are growing in strength and we should also think about other desktops like XFCE.
About XFCe...
I know, late reply is late... and I wrote the same already in the slax forum...
My idea/Suggestion: tweaking a standard Porteus into a Porteus with no KDE but XFCe instead means also include all the non KDE programs from the console, like cdrecord, mkisofs and more like that (and manfiles and readmes and setup files), and create that module for each and every Porteus version anew. Same is when someone wants to create a Gnome-Only Porteus.
And technically spoken the users need to download that extra module, although all these programs and manfiles and readmes and setup files are just the same as in the original Porteus ISO...
005-kdeapps.lzm
006-koffice.lzm
can be ommited. Same with
003-lxde.lzm
BUT the non-KDE programs from 004-kde.lzm are needed for any non-KDE porteus as well...
Therefore my idea: to me it sounds easier when we would split the
004-kde.lzm for each any every generic Porteus version - like into:
003-lxde.lzm
004-konsole.lzm (or maybe: 004-programs or any other neat name) [here goes cdrecord, mkisofs and whatnot]
005-kde.lzm (the rest of the original 004-kde.lzm from Porteus 0.9 to 1.0a - but this time really only the KDE stuff)
and the rest of the modules with the according number.
And I think it would be possible to write a script that auto-splits the module... Simply based on a listfile that lists all the path and filenames to be removed from the
original 004-kde.lzm
What do you folks think of that idea?
I hope I was able to explain it in an understandable way, since I sometimes have issues doing so in English...
, but please keep FFx in its own module.
