From Mageia wiki
Jump to: navigation, search


Summary

Having Xfce more Mageia compliant : look & use

Owner

  • Name: magnux77
  • Email: magnux77@laposte.net

Resources

List here people who will be implied in this feature (packagers, QA, doc, ...)

Current status

  • Targeted release: <software_release> (if needed), <Mageia release>
  • Last updated: 2018/12/13
  • Percentage of completion: <XX>%

Detailed Description

The goal is to have a Xfce installation more Mageia compliant. In the look aspect ( more like Plasma):

- Only 1 bottom panel like Plasma in place of 2 today (top & bottom)
- Windows : Compositing : active windows = 100%, inactive = 90%
- Windows : Compositing : active shadow for every window.

In the use aspect (more customized like Plasma):

- Thunderbird in place of Claws Mail
- Classic Menu in place of Whisker Menu less usable (bad display, more clics)
- gvfs-mtp natively installed for androïd systems cause they are usuals today
- Thunar : + Catfish , Edit Custom Actions "Search for files" catfish %f
- Volume Manager : to be configured (more precisions later if accepted)
- task-xfce-plugins natively installed for easier use by beginners


Why it would be good for Mageia to include it

A lot of reasons

- Different GUI should have a convergent look as they are delivered in the same distribution. Mageia will show better integration capacities.
- Xfce is far more simple than KDE to maintain and upgrade (It runs fine with no problem till april 2016 on Mageia 6 officially delivered on July 2017 : ready 15 monthes before Plasma !)
- Xfce could represent an alternative to Plasma for a lower Mageia development cost and prepares a possible escape way if Plasma complexity becomes too heavy 
- Xfce is more open and less hegemonic than Plasma : no Xfmail, no Xfonqueror and so on.
- Xfce upgrades are less difficult for users and complex for developpers.

Test case

Anything useful for QA and all testers to help debugging during all development cycle

Software / Packages Dependencies

List of packages to be implied

What could disrupt development of this new feature

Planning

Contingency

Release Notes

Documentation

Include here any needed information or link to documentation