Re: Nautilus-actions, Nautilus-scripts and Nautilus Extensions



Hi there,

 For those who doesn't know, I'm the main author of Nautilus-actions :)

John Stowers wrote:

[snip] I am prepared to implement these suggestions I would like peoples feedback on what is the better approach. I have two current ideas. Option 1) Add an additional tab in the Nautilus preferencs. This tab contains a listbox listing the installed nautilus extensions AND scripts (but making no visual distinction between the two). Each extension/script can be enabled via a checkbox. There is also Add, Remove, and Configure buttons. The configure button is enabled for all extensions that implement the (new) NautilusConfigureExtension interface and provides a way to prevent nautilus extensions needing their own seperate configuration tool like nautilus-actions currenlty does.

This is a great news that I'm happy to learn. In which version of nautilus was it implemented ? 2.14 ?

I don't have a lot of time to give to Nautilus-actions at the moment, but I would be glad to help you implement this in n-a.

The Add and Remove buttons allow better discoverability of the extensions(and scripts) functionality to users and provide a simple way to install and remove scripts and extensions. Option 2) Create a NautilusPreferencePage interface to allow individual nautilus extensions to host their configuration pages in the nautlus preferences dialog. What are peoples thoughts on this? I will create some visual mockups based upon feeback if you like.

For my part, both options is ok for me. The most it is integrated, the best is it for the final users.

Best regards,

Fred
--
http://www.grumz.net/
begin:vcard
fn:Frederic RUAUDEL
n:RUAUDEL;Frederic
org:EMBL Grenoble Outstation;Computer & Network Team
email;internet:ruaudel embl fr
title:System Administrator
x-mozilla-html:FALSE
version:2.1
end:vcard



[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]