We are happy to announce the new stable release of Nautilus-Actions.
What is it ?
Nautilus-Actions is an extension for Nautilus file manager which allows to add arbitrary items to the Nautilus context menus.
What is new in this release ?
User is now able to freely enable/disable an action.
A disabled action will never appear in the Nautilus context menu.
#325519 asked by Frederic Ruaudel (enabled property) #590398 reported by Pierre Wieser (install doc) #590399 reported by Pierre Wieser (gtk_image_menu_item_set_image)
2009-08-11 Pierre Wieser
* src/nact/nact-icommand-tab.c: * src/nact/nautilus-actions-config-tool.ui: Cleanup code. * src/nact/nact-iaction-tab.c: * src/nact/nact-icommand-tab.c: * src/nact/nautilus-actions-config-tool.ui: Set a mnemonic for all entry fields. 2009-08-10 Pierre Wieser * data/nautilus-actions.schemas.in: Add schema description for 'enabled' action property. * src/common/na-action.c: * src/common/na-action.h: Define 'enabled' new action property. * src/common/na-gconf-keys.h: * src/common/na-xml-names.h:
We are very happy to announce the new development release of Nautilus-Actions.
Probably the most exciting feature in this version is the right through new user interface.
Take a look at it.
Packagers, your users will want it !
Nautilus-Actions 1.11.2 is available for download at
I'm very proud to announce today the release of the version 1.10.1 of Nautilus-actions.
It includes many small bugfixes, and updated translations.
In particular, bug #574919, which prevented nautilus-actions to execute under Gnome 2.26 has been fixed with the help of Bruce van der Kooij.
Detailed ChangedLog can be found here.
For now, the tarball is made available at ftp://pwi.dyndns.biz/tarballs/nautilus-actions/nautilus-actions-1.10.1.tar.gz
Bug reports are welcome at http://bugzilla.gnome.org/browser.cgi?product=nautilus-actions
I didn't want see nautilus-actions fall back in the obscurity. As many of you, I use this so practical extension on an every day basis, and I was upset to no more find any upgrade nor maintenance.
Frederic has created this project, led it during many years and really made a great work. I'd wish thanks him for all of that. But time has passed, Frederic has wished reorientate his time differently, and he was searching for a successor for more than one year now.
I so asked Frederic the permission to take back his project. With his agreement, nautilus-actions has now a brand-new project manager.
As you probably have noticed, the development pace of Nautilus-actions has been decreased since 1 year and it is due to a lack of time and motivation from me.
But as I see that there is still lots of people interested in this project, and wanting some of the new features promised, I've decided to make things clear about my plans on the subject.
So, it's time to turn to someone else with better motivation than I have right now in order to allow Nautilus-actions to keep make its user base happy about it.
If you are interrested in taking this on, please contact me at grumz _AT_ grumz .DOT. net and I would give you all the means and help to get on this great project !
Thanks in advance !
Nautilus-actions version 1.4.1 is out !
This is a minor bug fix and translation update release. Three new languages has been added : Dzongkha, English (British) and Arabic.
You can check for the changes details here.
The new release can be found in the Download section. All the packages for your favourite distribution will hopefully be available very soon !
If you need to fill a bug/feature report, please follow this link.
Following my last blog post about the future plans for Nautilus actions, I would like to share with you once again some of my ideas about the next major 2.x version.
This time, it is about the future conditions that will be available in the options of each actions config. Indeed, as the main benefits of Nautilus actions, towards its concurrent the Nautilus-scripts, is the fact that the actions are displayed only when it's contextually needed, to me it is important that the possibilities to achieve this should be the best possible.
So I plan to add as much options as possible and as long as it makes sense of course, to reach this goal.
Here is the current list of conditions I plan to make available for the next 2.x releases :
- Filename pattern (basic and regexp) + case sensitiveness option
- It will consist of two options : the basic one which represents the current option available with simple joker (* and ?) and the regexp one which will be used for regular expression matching.
- Folder name pattern (basic and regexp) + case sensitiveness option
- Same as above, but for matching the folder in which the selected elements are. (eg, if you select /home/foobar/file.txt, it will match the /home/foobar part)
- Mime types pattern (basic and regexp)
- Same as above but for mime types matching (image/jpeg, video/mpeg, text/plain, etc.)
- Element type (folder, file, link, etc...)
- This will be a "probably" extended condition based of the current "Appears if selection contains" which will provide more kind of file types like symlinks for example. But I have to see if it make sense or not...
- Number of selected elements (1, 2, 3, unlimited) (Bug #325523)
- This one is an extended version of "Appears if selection has multiple files or folders" option. It will be useful for actions like "diff" which need exactly 2 files for example.
- Schemes of the selected elements (file, sftp, smb, dav, etc...)
- No change here, it is the one already available since the beginning.
- Content of the selected folders (hold music files, hold a .svn folder, etc.)
- This one is about checking the files available in a selected folder. For example, if you want to define a SVN set of actions, you will search for a folder with a .svn folder in it, or if you want to enqueue a full folder of music file, you will search for audio files. This options must be tested to see if it doesn't reduce the performance of Nautilus too much.
- Condition script (run a script which return true if conditions are ok) (Bug #330610)
- This one is a possibility to set a script/program that would be launched and activate the defined action if it returns TRUE. The performance counterparts have to be tested too.
All these conditions have to be tested to know if they really have an acceptable performance/added value ratio. Now, I would really appreciate if you could give me your thoughts about all this and if you have any awesome ideas which are not in this list to reach the goal given above !
Exactly one year ago, the 28th of August 2005, I was releasing the first public release of Nautilus-actions, the V0.3, on this site.
Since then, a lots of improvements has been done, mainly thanks to Rodrigo Moya who helped me a lot in the transition to GConf, which improves a lot Nautilus-actions' performance. There was also a lots of works done by the Gnome Translation Project with now 28 languages supported !
Finally, the success of Nautilus-actions wouldn't have occured without the help of all its users who spreads the word in the many forums and blogs all over the net, and after seeing a lot of them starting to create full threads dedicated to the possible configurations that can be created with it, I decided to create an official Actions Repository which has so far 40 configs submitted since its creation four months ago !
Now, it is time to think of the future of Nautilus-actions and I will now start the 2.x series which aims is to be even more integrated with the Gnome Desktop and ideally be accepted as a part of it in one of the next main release (2.18 ?). The 2.x releases will probably use the last Gnome features and so will not be compatible with Gnome < 2.16 and GTK+ < 2.10. I will try to keep the configurations as compatible as possible. Anyway, the 1.x series will stay in maintenance mode and some patches could be applied to support a part of the new configurations if necessary.
To come back to the 2.x series new features, here is a non exhaustive list of the things I want to add :
- Support for submenus in Nautilus. Thanks to the integration of the submenu support in Nautilus 2.16, I will now be able to add the possibility to group actions together in a submenu, to make coherent groups of actions (eg, CVS support) or to avoid bloating the main menu (Bug #325528).
- Add some options to make the needs for most scripts useless. For example, when you want to run a command once for each selected files, you have to create a script to loop on each files and send them to the command, because Nautilus-actions run the command once with all the selected files as parameter. Now you will be able to choose between the two possibilities (or ideally, Nautilus-actions will be able to guess which one is better depending of the other options you choose). If you have any propositions/suggestions about this, feel free to leave a comment !
- Creation of a new config in a wizard mode. Now that the wizard/assistant widgets have been integrated in GTK+, I would like to use them to make the configuration creation easier for new users. Maybe a preference settings will give the possibility to choose between wizard mode or normal mode. As I want to add more options, I don't want to fear new users with a too complicated interface, so I think that the wizard mode is a good compromise because it allows to easily add some help in each steps.
- Possibility to disable any configs without deleting them (Bug #325519). If you have some useful configs that you don't use often, you can disable them to avoid cluttering your menu during the time you don't need them. And it will be useful if more apps add some support for Nautilus-actions because when you install an actions as root, it is not possible to delete it as a normal user.
- Many other nifty features I didn't have thought about yet...
So now, one more thing I have to find to implement all this... Time ! :oP
If you have any suggestions to make, any features to propose, any great ideas to implement all of this in a clean way, don't hesitate to leave a comment here or to submit a feature request on Bugzilla.
Thanks for your attention and support !
Nautilus-actions version 1.4 is out !
This is a major bug fix release. The most important one concerns a patch created for Nautilus to support a menu cache update feature for its extensions. As you probably noticed with the previous version of Nautilus-actions, there are some case where the actions are not available right after you edit them with Nact. Now if you have this patch applied (will be available upstream in Nautilus 2.16), you will not have to restart Nautilus or your Gnome session to be able to use your new actions.
Another important change concerns a better error handling of mainly the import/export features. Now an error dialog will be displayed to explain why some config file can't be imported or exported, etc.
The full list of changes is available here.
The new release can be found in the Download section. All the packagers are working hard to deliver Nautilus-actions on the different supported distributions and those still missing will be made available very soon !
If you need to fill a bug/feature report, please follow this link.