Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionLast revisionBoth sides next revision | ||
projects:gsoc_2022:start [2024/01/23 08:27] – sefsef alexxcons | projects:gsoc_2022:start [2024/01/24 14:46] – alexxcons | ||
---|---|---|---|
Line 1: | Line 1: | ||
~~NOTOC~~ | ~~NOTOC~~ | ||
- | ====== Xfce - Google Summer of Code 2022 ====== | + | ====== Xfce - Google Summer of Code 2021 ====== |
* **[[# | * **[[# | ||
* **[[# | * **[[# | ||
- | * **[[#thunar|thunar]]** | + | * **[[#Create Sample/ |
- | * **[[#xfce4-terminal|xfce4-terminal]]** | + | * **[[#Improve Thunar|Improve Thunar]]** |
- | * **[[#xfce4-screenshooter|xfce4-screenshooter]]** | + | * **[[#Wayland Support|Wayland Support]]** |
- | * **[[#xfce4-panel|xfce4-panel]]** | + | * **[[#Create StatusNotifierItem Skeleton / example|Create StatusNotifierItem Skeleton / example]]** |
- | * **[[#all components|all components]]** | + | * **[[#Add Calendar Capabilities to Clock|Add Calendar Capabilities to Clock]]** |
- | * **[[# | + | |
* **[[#GSoC Participants Blogs|GSoC Participants Blogs]]** | * **[[#GSoC Participants Blogs|GSoC Participants Blogs]]** | ||
Line 16: | Line 15: | ||
[[https:// | [[https:// | ||
- | [[https:// | + | [[https:// |
+ | |||
+ | The Xfce project was accepted as [[https:// | ||
If you are a developer who would like to get involved with the Xfce project, please see [[https:// | If you are a developer who would like to get involved with the Xfce project, please see [[https:// | ||
- | **Note**: Due to bot protection you need to request permission on the #xfce-dev IRC channel to be able to fork Xfce proejcts and to open merge requests. | ||
---- | ---- | ||
Line 26: | Line 26: | ||
====== Communication ====== | ====== Communication ====== | ||
- | Participants | + | Students |
- | * The [[https:// | + | * [[https:// |
- | * The [[https:// | + | * [[https:// |
If you use a [[https:// | If you use a [[https:// | ||
Line 35: | Line 35: | ||
Alternatively you can use [[https:// | Alternatively you can use [[https:// | ||
- | If you are connecting via Matrix, please dont use Matrix specific things like ' | + | In order to coordinate projects, students should add their names to [[https:// |
---- | ---- | ||
[[|Back To Top]] | [[|Back To Top]] | ||
Line 41: | Line 42: | ||
====== Project Ideas ====== | ====== Project Ideas ====== | ||
- | Feel free to package a number of issues to a GSoC project, for which you think, you can solve them in the given timeframe (175h or 350h). Note that the issues you pick don't need to share the same mentor or be entirely from one project (some projects are pretty small and simple | + | * **[[#Create Sample/ |
+ | * **[[# | ||
+ | * **[[# | ||
+ | * **[[# | ||
+ | * **[[#Create StatusNotifierItem Skeleton / example]]** | ||
+ | * **[[#Add Calendar Capabilities | ||
- | Note: Fixing some smaller issues already now (E.g. to show your programming skills) as well would be very welcome. | + | ---- |
- | Here are some suggestions to pick from, where mentors already confirmed to support them as part of a GSoC project. You can as well check our [[https:// | + | ===== Create Sample/Skeleton plugins in all GOI supported languages ===== |
- | * **[[# | + | As we already have sample/ |
- | * **[[#xfce4-terminal|xfce4-terminal]]** | + | |
- | * **[[#xfce4-screenshooter|xfce4-screenshooter]]** | + | |
- | * **[[#xfce4-panel|xfce4-panel]]** | + | |
- | * **[[#all components|all components]]** | + | |
- | ---- | + | |
- | ===== thunar ===== | + | |
- | Thunar is Xfce' | + | that make it' |
- | * [[https://gitlab.xfce.org/ | + | * **[Language: |
- | * **[Difficulty: easy] [Required Skills: C, Glib] [Possible | + | * **Python:** Create Sample/ |
- | * **[Estimate time: 15h (Could be part of a 175h/350h project)]** | + | * **JavaScript:** Create Sample/ |
- | * To ease the editing of accels.scm | + | * **Vala:** Create Sample/ |
- | * The linked bug contains an old WIP patch. | + | |
- | * [[https:// | + | **[Difficulty: |
- | * **[Difficulty: | + | |
- | * **[Estimate time: 20h (Could be part of a 175h/350h project)]** | + | |
- | * Bulk rename supports find-and-replace, | + | |
- | * Fix RegEx find-and-replace to replace all occurrences. | + | |
- | * Additional task: Add an option to replace only the first occurrence | + | |
- | * **[Difficulty: | + | |
- | * **[Estimated time: 20h (Could be part of a 175h/350h project)]** | + | |
- | * Add a checkbox to enable replace-all. | + | |
- | * Open an Issue first to work with this problem. | + | |
- | * [[https:// | + | ---- |
- | * **[Difficulty: medium] | + | [[|Back To Top]] |
- | * **[Estimate time: 40h (Could be part of a 175h/350h project)]** | + | |
- | * So that the side panel icons are more consistent and less distracting | + | |
- | * There is already a [[https:// | + | |
- | * [[https:// | + | ===== Improve Thunar ===== |
- | * **[Difficulty: | + | |
- | * **[Estimate time: 60h (Could be part of a 175h/350h project)]** | + | |
- | * Implement a strategy that can handle when a resulting name of one file conflicts with the original name of the other. | + | |
- | * [[https:// | + | Thunar is Xfce's file manager and one of its core components. There are many new features pending |
- | * **[Difficulty: | + | |
- | * **[Estimate time: 60h (Could | + | |
- | * Unlike UNIX systems, Windows | + | |
- | * Figure out how to check filesystem case-insensitivity ([[https:// | + | |
- | * Implement a renaming scheme to fit case-sensitive names to case-insensitive filesystems. | + | |
- | * Additional task: Warn user about case-insensitive systems | + | |
- | * **[Difficulty: | + | |
- | * **[Estimated time: 20h + dialog discussion (Could be part of a 175h/350h project)]** | + | |
- | * Open an Issue first to work with this problem. | + | |
- | * Dialog like " | + | |
- | * Check if the filesystem is case-insensitive and/or the overwriten file only differs by case. | + | |
- | * Figure out a way to inform the user about the problem without explaining too many technical details. | + | |
- | * [[https:// | + | * <del>[[https:// |
+ | * **[Difficulty: | ||
+ | * Often when searching something in trash, the latest trashed items are of interest. | ||
+ | * The mission here would be, to add another sorting category " | ||
+ | * Check [[https:// | ||
+ | * Most likely it will be required to bundle multiple [[https:// | ||
+ | * < | ||
+ | * **[Difficulty: | ||
+ | * Currently setting a default application is a bit hidden in thunar. And if not set, the last used application always will be used as default, which is bad UX (see issue description). | ||
+ | * The idea is, to automatically select an application as default for a specific mime-type on the first open, if no default application was defined so far for that mime type. | ||
+ | * Additionally the "open with" context menu should get an additional entry labeled "set default application" | ||
+ | * The application chooser should highlight the current default application in some way. | ||
+ | * Note that most likely this issue alone will not be sufficient for a 175 hour Project, you will need to bundle multiple issues. | ||
+ | * < | ||
+ | * **[Difficulty: | ||
+ | * The location " | ||
+ | * It would be nice to fix these flaws, and show the " | ||
+ | * Note that most likely this issue alone will not be sufficient for a 175 hour Project, you will need to bundle multiple issues. | ||
+ | * < | ||
* **[Difficulty: | * **[Difficulty: | ||
- | * **[Estimate time: 60h (Could be part of a 175h/350h project)]** | + | * Currently zoom levels are the same for each directory. However since thunar 4.16.x, several settings, like view-type and sorting order can be saved per directory. As well for the zoom level that would make a lot of sense. |
- | * Like for Mac, it would be nice to have the possibility to set custom colors | + | * The commits for the existing " |
- | * The chosen color could be saved as gvfs-metadata value, like done for e.g. emblems. | + | * In addition it could be interesting to select in detail which settings should be shown "per directory" |
- | * The property dialog | + | |
* [[https:// | * [[https:// | ||
* **[Difficulty: | * **[Difficulty: | ||
- | * **[Estimate time: 60h (Could be part of a 175h/350h project)]** | ||
* Currently the only thunar custom action which is provided by thunar is "open terminal here". (Xubuntu adds some more). To add additional custom actions from [[https:// | * Currently the only thunar custom action which is provided by thunar is "open terminal here". (Xubuntu adds some more). To add additional custom actions from [[https:// | ||
* Like that we would have the possibility to provide translations for all of these UCA's | * Like that we would have the possibility to provide translations for all of these UCA's | ||
- | * We would need the possibility | + | * We would need the possibility enable/ |
- | * One job here would be to modify the UCA-management dialog in order to show disabled UCA's grayed out. A checkbox inside UCA config dialog could be used to enable/ | + | * One job here would be to modify the UCA-management dialog in order to show disabled UCA's grayed out. A checkbox inside UCA config dialog could be used to enable/ |
* In a second step, default UCA's could be added from the [[https:// | * In a second step, default UCA's could be added from the [[https:// | ||
* Code in Xfdesktop, the desktop manager, would also need to be modified to handle disabled UCA's. | * Code in Xfdesktop, the desktop manager, would also need to be modified to handle disabled UCA's. | ||
+ | * < | ||
+ | * **[Difficulty: | ||
+ | * In the past we had alot of bugs related to tree-view (sidepane) letting CPU run at 100%. The reason is, that building the file-tree is a complex procedure which has a lot of corner cases, embedded in an recursive call. Errors | ||
+ | * It looks like for now we found all problematic corner cases, though in order to make the related code more failsafe for further changes, it still would be nice to have a rate-limiting mechanism, using '' | ||
+ | * [[https:// | ||
+ | * **[Difficulty: | ||
+ | * Currently there is only a single file which stores all the user-specific custom actions | ||
+ | * It would be much more " | ||
+ | * The user would need to be able to overwrite and disable system-defined UCA's. (See as well [[https:// | ||
+ | * Optionally the project could be extended by changing the format from " | ||
+ | * < | ||
+ | * **[Difficulty: | ||
+ | * There is a couple of open issues related to file search. According to your skill-level we could make a GSoC project out of multiple of these bugs. | ||
+ | * E.g. the possibility to access a file-search tool, like catfish via toolbar (Possibly by using a DBus call?) | ||
+ | * < | ||
+ | * **[Difficulty: | ||
+ | * Currently on restart only the latest used path is restored. | ||
+ | * Like web browsers, thunar could restore all paths from the last session instead. | ||
+ | * [[https:// | ||
+ | * **[Difficulty: | ||
+ | * There are a number of issues filed on the thunar bulk renamer which could be packed as a GSoC project dependent on your skill-level | ||
+ | * E.g. it is needed to properly highlight renaming conflicts, and several smaller enhancements | ||
+ | * < | ||
+ | * **[Difficulty: | ||
+ | * The execute flag currently is used to mark a launcher as " | ||
+ | * The idea is to use a " | ||
+ | * [[https:// | ||
+ | * **[Difficulty: | ||
+ | * Like for Mac, it would be nice to have the possibility to set custom colors for file and folder names. | ||
+ | * The chosen color could be saved as gvfs-metadata value, like done for e.g. emblems. | ||
+ | * The property dialog of files/ | ||
+ | * < | ||
+ | * **[Difficulty: | ||
+ | * Currently in thunar it is possible to specify custom keyboard shortcuts via the accels.xml file. That is not user-friendly. | ||
+ | * Instead, it would be nice to have a dialog which provides an overview on all thunar shortcuts and the possibility to change them. | ||
+ | * That dialog should be implemented in libxfce4ui in a way that allows other Xfce components to reuse it. | ||
+ | * < | ||
+ | * **[Difficulty: | ||
+ | * The freedesktop thumbnail spec described how to store and retrieve thumbnails. Thunar impements only part of the spec. The " | ||
+ | * To implement the spec fully, the following things needs to be changed: | ||
+ | * Thunar needs to check .sh_thumbnails and display thumbnails there before requesting new thumbnails to be created by tumbler | ||
+ | * Tumbler needs only to create thumbnails if they are not already in .sh_thumbnails | ||
+ | * For remote drives, thumbnails should also be displayed if they are in .sh_thumbnails, | ||
* [[https:// | * [[https:// | ||
- | * **[Difficulty: | + | * **[Difficulty: |
- | * **[Estimate time: 80h (Could be part of a 175h/350h project)]** | + | * While it would be good to know how many files are inside a folder, that can be very resource-consuming, |
- | * While it would be good to know how many files are inside a folder, that can be very resource-consuming, | + | |
* The linked bug contains an old WIP patch, which already worked for local files. | * The linked bug contains an old WIP patch, which already worked for local files. | ||
* The mission would be, to port that patch to thunar master and make it usable for remote location / figure out how to best do so. | * The mission would be, to port that patch to thunar master and make it usable for remote location / figure out how to best do so. | ||
- | * It is likely that a good solution requires running this functionality in a separate thread so experience with multi-threading could prove useful. | ||
* If that is not challenging enough for you, there is an [[https:// | * If that is not challenging enough for you, there is an [[https:// | ||
- | |||
* [[https:// | * [[https:// | ||
* **[Difficulty: | * **[Difficulty: | ||
- | | + | * Several thunar plugins, like rabbit-vcs, the thunar-vcs-plugin and thunar-dropbox would profit from the possibility to set emblems on files. Though currently plugins are not able to do so. |
- | | + | |
* Nautilus already seems to provide such a service. Most likely the nautilus code can be used as inspiration. | * Nautilus already seems to provide such a service. Most likely the nautilus code can be used as inspiration. | ||
* It would be required to extend the thunarx API (API used by thunar plugin) in order to support custom emblems. | * It would be required to extend the thunarx API (API used by thunar plugin) in order to support custom emblems. | ||
+ | * Move resources which can be shared between thunar and xfdesktop into libxfce4util/ | ||
+ | * **[Difficulty: | ||
+ | * Both components need to do file operations, mounting and provide context menus. The related code currently is duplicated. | ||
+ | * The idea is to move that code and it's dependencies to a shared library in order to reduce duplication, | ||
+ | * There is no issue yet for that project ...feel free to open one | ||
+ | * [[https:// | ||
+ | * **[Difficulty: | ||
+ | * So that all applications which want to pick a file, will see the thunar dialog, instead of the foreign GtkFileChooserDialog | ||
+ | * Possible required to implement a service '' | ||
+ | * Creation of the related DBUS Service in thunar | ||
+ | * Dialog to pick specific file(s) and hit " | ||
+ | * [[https:// | ||
+ | * **[Difficulty: | ||
+ | * So that the side panel icons are more consistent and less distracting | ||
+ | * There is already a [[https:// | ||
+ | |||
+ | ---- | ||
+ | [[|Back To Top]] | ||
+ | |||
+ | ===== Wayland Support ===== | ||
+ | |||
+ | The X11 windowing system is currently in maintenance mode, as it is an aging system, and the Linux desktop ecosystem is transitioning to the Wayland display server protocol. In order to speedup the transition of Xfce's components to Wayland, they need to be tested and bugs need to be filed and fixed. [[https:// | ||
+ | |||
+ | ---- | ||
+ | |||
+ | ===== Improve Accessibility ===== | ||
+ | |||
+ | Investigate all Xfce applications to ensure that they are 100% accessible to screen reader and keyboard users, including making the [[https:// | ||
+ | |||
+ | ---- | ||
+ | |||
+ | ===== Create StatusNotifierItem Skeleton / example ===== | ||
+ | |||
+ | We already provide a way to show [[https:// | ||
+ | |||
+ | ---- | ||
+ | [[|Back To Top]] | ||
+ | |||
+ | ===== Add Calendar Capabilities to Clock ===== | ||
+ | |||
+ | The Gtk2-based [[https:// | ||
+ | **[Required Skills: C, Gtk, Glib]** | ||
+ | |||
+ | ---- | ||
+ | |||
+ | ===== GSoC Participants Blogs ==== | ||
+ | |||
+ | * **[[http:// | ||
+ | * **[[https:// | ||
+ | * **[[https:// | ||
+ | |||
+ | ---- | ||
+ | [[|Back to Top]] | ||
- | * [[https://gitlab.xfce.org/xfce/thunar/ | + | [[https://docs.xfce.org/contribute/start|Back to main Xfce Contribute page]] |
- | * **[Difficulty: | + | |
- | * **[Estimate time: 80h (Could be part of a 175h/350h project)]** | + | |
- | * The goal of this project is to implement ' | + | |
- | * Examples of such operations are: " | + | |
- | * A possible solution would be to create a Stack where information about file operations is kept. To undo Thunar would get the top element of the Stack and execute the reverse operation. | + | |
- | * For example, if the top element of the Stack says that a FileA was moved from DirA to DirB Thunar would need to move FileA from DirB to DirA to undo. | + |