Hi, For my GSoC project, I will be working on caja, the file manager for the MATE desktop. My primary goal is to extend its extensions functionality to allow runtime (de-)activation of individual plugins, and to create an extension management system to allow more complex extensions. Now that my exams are over, I could finally devote myself to my GSoC project. At the beginning of this week, I continued work on my example extensions. I now have a full set of extensions that demonstrate most if not all of the functionality made possible through libcaja-extension. Now that I understand the process better myself, I have also begun writing much-needed documentation on this subject for future extension developers. In the later part of the week, I have begun with the changes required to caja for the main goal of my project. I hope to finish implementing the following five steps in the coming days: 1. Extend the default gsettings schemas to create a subcategory for extensions -modify libcaja-private/org.mate.caja.gschema.xml 2. Make the load_module_dir() procedure keep track of extensions found in CAJA_EXTENSIONDIR. Add new modules to the config (gsettings), and load known modules depending on their enabled/disabled status in said config. -modify libcaja-private/caja-module.c 3. Create new GUI tab in "File Management Preferences" to list available extensions and allow changing of their enabled/disabled status. -modify caja-file-management-properties.[c|ui] 4. Modify load module procedure to allow loading/unloading extensions during runtime. -modify libcaja-private/caja-module.c -modify individual gui elements insertion functions (caja-window-menus.c and such) 5. Allow extensions to expose a proper name, so we don't have to identify them by their module filename ('example.so') in the GUI. With kind regards, Alexander van der Meij alexandervdm @ freenode -- To unsubscribe, e-mail: opensuse-project+unsubscribe@opensuse.org To contact the owner, email: opensuse-project+owner@opensuse.org