File: README

package info (click to toggle)
caja-actions 1.8.1-1
  • links: PTS, VCS
  • area: main
  • in suites: stretch
  • size: 32,308 kB
  • sloc: ansic: 48,885; xml: 4,222; makefile: 1,073; sh: 339
file content (138 lines) | stat: -rw-r--r-- 3,612 bytes parent folder | download
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
2014-03-23 update to 1.7.1

changelog:
- improve help documents

2014-03-15 update to 1.7.0

changelog:
- port to yelp-tools

2014-03-14 update to 1.6.3

changelog:
- update to follow nautilus-action-3.2.3
- for details see git commits

2013-08-18 update to 1.6.2

changelog:
- fix Copying-DOCS issue,  wrong-file-end-of-line-encoding

2014-08-15 update to 1.6.1

changelog:
- improve debug usage

2012-11-29 update to 1.6.0

changelog:
- complete removal of mateconf usage, needed for distros with MATE 1.6
  without mateconf.
  
Mate Installation
==================
NOCONFIGURE=1 ./autogen.sh

./configure  \

    --with-gtk=2

    --enable-html-manuals

make

sudo make install


for Mate-1.4, you need 1.4.0 source

NOCONFIGURE=1 ./autogen.sh

./configure  \

	--disable-schemas-install \

	--with-gtk=2 \

    --enable-mateconf=yes \

    --disable-scrollkeeper \

    --enable-html-manuals \

    --with-default-io-provider=na-desktop

make

sudo make install
  

Description
==================  
Caja-Actions

  Caja-actions is an extension for Caja file manager which
  allows the user to add arbitrary program to be launched through the
  Caja file manager popup menu of selected files.

Caja-Actions components.

  Caja-Actions has three sort of components:

  - A user interface, caja-actions-config-tool (CACT), which let you
    manage your actions. With CACT, you are able to create, modify and
    delete actions, to define menus and submenus, to order and reorder
    items.
    Import/export functions are also managed via CACT.

  - Caja extensions as dynamically loadable plugins. These extensions
    are automatically loaded by Caja when it starts. For now, two
    extensions are provided:
    . libcaja-actions-menu.so is a plugin which takes care of displaying
      actions in Caja context menus;
    . libcaja-actions-tracker.so is a plugin which tracks the current
      Caja selection, and sends it in response to a DBus request. 

  - Command-line utilities:
    a) installed in PREFIX/bin:
       . caja-actions-new lets you create new actions from the command-line;
       . caja-actions-run lets you execute a predefined action, taking
         into account the current Caja selection via a DBus call to the
         libcaja-actions-tracker plugin;
    b) installed in PKGLIBEXECDIR:
       . na-print-schemas prints the full MateConf schemas on stdout;
       . na-delete-xmltree deletes a tree from a XML file;
       . na-mateconf2keys.sh migrates menus, actions and user preferences from
         MateConf to files.

Caja-Actions plugins.

  I/O Providers.

    Caja-Actions itself uses plugins to load menus and actions from
    the storage space. These plugins are installed in PKGLIBDIR, usually
    something as /usr/lib/caja-actions/.

    Starting with 1.5.0, the preferred default I/O provider is 'na-desktop',
    which means that newly created actions and menus will be stored on
    disk as .desktop files, in accordance with DES-EMA specification [1].

  Importers/Exporters.

    Caja-Actions also relies on plugins to import actions and menus,
    and to export them, in several formats.
    For now, Caja-Actions is able to import/export its items as:
    . MateConf schemas;
    . MateConf dump;
    . XML;
    . .desktop files.

Caja-Actions documentation.

  Documentation is provided in several formats:
  - developer documentation is provided as xml and html files, as generated
    by gtk-doc;
  - CACT user's manuals and general documentation is provided as xml, pdf
    and html files, as generated by mate-doc-utils, docbook-utils or dblatex
    tools.