| /plugin/pagemove/ |
| H A D | admin.php | 405 $files = scandir($pathToSearch);
406 if( !empty($files) ) {
407 foreach($files as $file) {
878 $files = array();
890 $files[] = $dir.'/'.$file;
893 sort($files);
903 foreach($files as $file) {
|
| /plugin/pagequery/ |
| H A D | deleted.files | 1 # This is a list of files that were present in previous plugin releases
3 # the files installed
|
| H A D | readme.md | 9 On the surface it may appear to fill a similar role to the really excellent [[plugin:indexmenu|IndexMenu]], however pagequery's aspirations are not as lofty or elaborate. IndexMenu focuses on displaying namespaces, and the pages within. allowing you to sort the namespaces and files by many options, and actively navigate and manipulate this index. Pagequery's purpose is __displaying lists of pages__: yes, you can sort by namespace if you wish, however the main goal is to search for and list pages in any order, and then neatly display them in groups (A-Z, by year, by month, etc...) and in addition in columns — to make best use of space. If you try both of them you'll quickly see that they //"scratch different itches."//
35 "http://pagequery.googlecode.com/files/pagequery%20screenshot.png"An example of a navigation page
76 E.g. Search for all pages in the "drafts" namespace, listing only files beginning with a number, sorted by name:
80 Or, all files in the "happy:go:lucky" namespace, sorted by year, then date created, in proper case, in 2 columns, and use the page title, not the name in the listing:
|
| /plugin/pagetitle/ |
| H A D | deleted.files | 1 # deleted.files : PageTitle plugin for DokuWiki
3 # This file contains a list of files that were present in previous
5 # An up-to-date plugin should not have any of the files installed.
|
| /plugin/passwordgrey/ |
| H A D | LICENSE | 95 a) You must cause the modified files to carry prominent notices
96 stating that you changed the files and the date of any change.
158 associated interface definition files, plus the scripts used to
|
| /plugin/pdb/classes/ |
| H A D | cache.php | 52 $files = array();
60 $files[$id] = $path;
64 return $files;
|
| /plugin/pdfjs/ |
| H A D | LICENSE | 6 of this software and associated documentation files (the "Software"), to deal
|
| H A D | plugin.info.txt | 6 desc Show pdf files using PDF.js
|
| /plugin/pdfjs/pdfjs/ |
| H A D | LICENSE | 29 source, and configuration files.
98 (b) You must cause any modified files to carry prominent notices
99 stating that You changed the files; and
|
| /plugin/pdfjs/pdfjs/build/ |
| H A D | pdf.js.map | 1 …files. Providing a custom factory is useful\n * for environments without `XMLHttpRequest` suppor…
|
| H A D | pdf.worker.js.map | 1 …files, which we thus attempt to support (utilizing `docBaseUrl`).\n /* falls through */\n…
|
| /plugin/pdfjs/pdfjs/web/ |
| H A D | viewer.js | 1829 var files = evt.target.files;
1831 if (!files || files.length === 0) {
1846 var files = evt.dataTransfer.files;
1848 if (!files || files.length === 0) {
2084 var file = evt.fileInput.files[0];
13513 database.files = [];
13515 while (database.files.length >= _this.cacheSize) {
13516 database.files.shift();
13523 var branch = database.files[i];
13532 index = database.files.push({
[all …]
|
| H A D | viewer.js.map | 1 …files","evt","webViewerOpenFileViaURL","xhr","pageIndex","pageView","Stats","mode","view","action"…
|
| /plugin/pdftools/ |
| H A D | LICENSE | 95 a) You must cause the modified files to carry prominent notices
96 stating that you changed the files and the date of any change.
158 associated interface definition files, plus the scripts used to
|
| H A D | README.md | 102 The template files must be placed in a directory, which must bei included in the zip-file. The file…
|
| /plugin/pdftools/tpl/checkliste/ |
| H A D | README.txt | 3 Templates define the design of the created PDF files and are a good way
11 The following files can be created and will be used to set headers and
34 If you reference image files, be sure to prefix them with the @TPLBASE@
40 footer files.
|
| /plugin/pdftools/tpl/checkliste2/ |
| H A D | README.txt | 3 Templates define the design of the created PDF files and are a good way
11 The following files can be created and will be used to set headers and
34 If you reference image files, be sure to prefix them with the @TPLBASE@
40 footer files.
|
| /plugin/pdftools/tpl/info/ |
| H A D | README.txt | 3 Templates define the design of the created PDF files and are a good way
11 The following files can be created and will be used to set headers and
34 If you reference image files, be sure to prefix them with the @TPLBASE@
40 footer files.
|
| /plugin/pdftools/tpl/kompakt/ |
| H A D | README.txt | 3 Templates define the design of the created PDF files and are a good way
11 The following files can be created and will be used to set headers and
34 If you reference image files, be sure to prefix them with the @TPLBASE@
40 footer files.
|
| /plugin/pdftools/tpl/minimal/ |
| H A D | README.txt | 3 Templates define the design of the created PDF files and are a good way
11 The following files can be created and will be used to set headers and
34 If you reference image files, be sure to prefix them with the @TPLBASE@
40 footer files.
|
| /plugin/pdftools/tpl/onlylogo/ |
| H A D | README.txt | 3 Templates define the design of the created PDF files and are a good way
11 The following files can be created and will be used to set headers and
34 If you reference image files, be sure to prefix them with the @TPLBASE@
40 footer files.
|
| /plugin/pdftools/tpl/standard/ |
| H A D | README.txt | 3 Templates define the design of the created PDF files and are a good way
11 The following files can be created and will be used to set headers and
34 If you reference image files, be sure to prefix them with the @TPLBASE@
40 footer files.
|
| /plugin/pglist/ |
| H A D | action.php | 40 'insert' => '{{pglist>selected_namespace files dirs me nostart fsort dsort}}'
|
| H A D | syntax.php | 73 'files' => 0,
97 if(preg_match('/\bfiles\b/i',$params)) $conf['files'] = 1;
135 if ($data['files'])
|
| /plugin/pgn4web/ |
| H A D | LICENSE | 141 includes interface definition files associated with source files for
399 must place, in the relevant source files, a statement of the
400 additional terms that apply to those files, or a notice indicating
|