Forum - Lets talk 2.0

« Lets talk 2.0 »

Welcome Guest. Please Login or Register.
Jun 17, 2013, 11:41pm

Return to or visit the SalineOS webpage

Forum :: General :: Testing and Development :: Lets talk 2.0

Page 1 of 8 » Jump to page Go

Author

Topic: Lets talk 2.0 (Read 2,533 times)

Anthony Nordquist
Administrator

member is offline

Joined: Dec 2010
Gender: Male

Posts: 1,343

Lets talk 2.0
« Thread Started on Jan 13, 2012, 9:25am »

There is roughly 5.5 to 6 months before the expected freeze of Debian Wheezy, which will signify the coming of early development builds of SalineOS 2.0. I would like to invite everyone to make suggestions and join the discussion on what will be coming in 2.0. This post will also serve as my own personal to do list and will be updated periodically.

These items will be done for 1.6:
I will be adding the custom actions I posted earlier here: http://salinelinux.proboards.com/index.c....ad=98&post=5189
I will be killing the P.S.E as I feel that I went about it the wrong way, I will be cutting up the scripts and doing something for 2.0 (See below).
Will be applying a fix to the X server wanting to blank the screen after 10 minutes.

To do and other info for 2.0:
The desktop background will be changed to another piece of photography, though I have one in mind if you know of some copyleft photography that is really good, feel free to make suggestions.

Determine the best theme to use.

The Icon theme is up in the air, if you have suggestions, please post under this thread. If anyone wants to fix up some of the icons that were included in SalineOS 1.x, they are public domain works (Except the terminal and desktop icons which I will be making from the desktop background), and can be changed freely. If you change any of them and post them here I will consider adding them for 2.0.

I will be moving to sudo for administrative tasks. Don't worry though, you can always open a root terminal through a Thunar custom action, as I will be updating it to work properly. I "may" add a launcher to the bottom panel as well.

I will be including Pulse Audio by default, the rational behind this is simple, every sound related issue posted on the forums for 1.x was fixed by installing Pulse Audio.

I am very likely going to replace Chromium with Midori. This decision has nothing to do with conserving system resources, I just feel Midori is the best available browser right now. Great strides have been made since version 2.4 that is available from the Squeeze repositories. As an added bonus, Midori uses less system resources

If feasible I will be including the Google Chrome repository and the Iceweasel backports repository.

Setup my own repository, this is likely to include packages for the user manual, salineos_utils, game packages built from upstream's pre-compiled binaries and packages pulled from Debian backports (When they start for Wheezy).

I will be moving to packagekit utilities for handling software updates and installation of packages. This means the removal of Synaptic.

Deluge will be replacing Transmission.

Xchat and baobab won't be included by default.

Firestarter firewall will be included.

Change desktop Icon size.

Change side pane icons in Thunar to "small".

Create Thunar launcher next to the Applications Menu.

I will be writing SalineOS System Utilities, a program using YAD with options to do various things such as, install proprietary drivers using magix-driver-installer, install-restricted-multimedia, change the system language and keyboard layout with localizesys, setup a lamp server, re-size the default SalineOS swap file, ease the installation and configuration of WINE, install XBMC and its extras, and whatever else I can come up with or good ideas that are suggested in this thread.

I am likely to replace Rhythmbox as the default music player, I am looking for input your favorite music players and why. I won't be using one that requires QT or Mono libraries so please only GTK based suggestions. -Exaile is currently the likely candidate.

Package Kit URL will be included, this script was developed and will continue to be developed in house. Put simply this is an apturl implementation built on the package kit command line utility pkcon. I have actually developed two implementations of this script, one that uses Zenity for a GUI which is only likely to work on Debian based systems and one that runs inside an xterm window. Packagekit URL is backwards compatible with Ubuntu's apturl implementation, for those keeping track yes this means that any distribution that has pkcon can use apturl links through packagekit url. My hope is that other distributions will take up using my convention of pkgkit://package-name/operation and these links will be supported by several distributions in the future (But, I will not be holding my breath). I do not and will never be supporting adding repositories as apturl does, packagekit URL simply strips this extra input out and installs the package using what is available from the repositories already enabled on the system. -Edit, This will be re-written in YAD.

The source for Package Kit URL is available here:
Zenity version: http://www.salineos.com/Scripts/packagekit-url
Xterm Version: http://www.salineos.com/Scripts/xterm/packagekit-url

To setup either version is fairly simple:

Put whatever version you intend to use in /usr/bin and mark it executable. Ensure you have pkcon installed, this is supplied by the package packagekit in Debian. For the Zenity version you obviously need Zenity installed.

Create a .desktop file in /usr/share/applications called packagekit-url.desktop and add this:

[Desktop Entry]
Version=1.0
Type=Application
Exec=gksudo "xterm -e /usr/bin/packagekit-url %u"
StartupNotify=false
Terminal=false

If using the zenity version change the Exec line to gksudo /usr/bin/packagekit-url %u

Now you need to add support to the various browsers:
For Midori you need to edit the $HOME/.local/share/applications/mimeapps.list (Possibly default.list in some distros?, I know this was the case for Debian Squeeze) of each user on the system and add these lines:
x-scheme-handler/pkgkit=packagekit-url.desktop
x-scheme-handler/apt=packagekit-url.desktop

Chrome/Chromium
Patch xdg-open (Located in /usr/bin on Debian) to include this:
For Xterm:

Code:
if [ "$(echo "$@" | grep "pkgkit://")" != "" ]; then
gksudo "xterm -e /usr/bin/packagekit-url $@"
elif [ "$(echo "$@" | grep "apt:")" != "" ]; then
gksudo "xterm -e /usr/bin/packagekit-url $@"
fi

For Zenity

Code:
if [ "$(echo "$@" | grep "pkgkit://")" != "" ]; then
gksudo /usr/bin/packagekit-url "$@"
elif [ "$(echo "$@" | grep "apt:")" != "" ]; then
gksudo /usr/bin/packagekit-url "$@"
fi

Firefox/Iceweasel:
Ran out of time, will add this later. Cheers.

Bugs that are affecting packagekit-url development at this time:
pkcon lacks a simulate option like apt has. Showing all the dependencies that will be pulled in with the package on the confirmation dialog would be nice, but without this switch it cannot be done cleanly. This bug was reported to packagekit upstream. https://bugs.freedesktop.org/show_bug.cgi?id=42602

Weird behavior from Midori when being redirected to an apturl, also reported to the upstream devs: https://bugs.launchpad.net/midori/+bug/916502

Migrate all the SalineOS utilities to YAD, this includes the installer, magix, localizesys and grub-doctor.

Re-write the installer mostly from scratch, using reusable functions. The installer will be setting all the options and showing a list of everything it will be doing and allowing you to go back and change any option individually.

Cleanup the menu by moving .desktop files to $HOME/.local/share/applications and modifying them with the line NoDisplay=true

Create $HOME/.config/menus/xfce-applications.menu and tweak it as needed.

Configure all hibernate options to divert to suspend (All of them I can).

Write a custom logout dialog without an option to hibernate, include a What's This button to explain Xfce4-Session. This what's this button should be able to remove itself from the dialog after being read.

Investigate reverting to the open source drivers for ATI and NVIDIA.

Ship all available printer drivers on the ISO images.

« Last Edit: Mar 9, 2012, 3:20am by Anthony Nordquist »