| Name | Summary | Document Type | Collections | Branch | Language | Last Modifier Login | Actions |
| .NET/C# implementation of the remote Java Daisy API | Daisy is a comprehensive content management application framework, consisting of basically : a standalone repository server accessible through either a local Java API, an HTTP/XML API, or a high-level remote Java API (based also on an HTTP/XML API), and an extensive browsing and editing DaisyWi... | SimpleDocument | daisywiki | main | en | cyberchand | show |
| 1.0.0 to 1.1.0 upgrade | Changes (compared to Daisy 1.0.0) Features Introduced separate ACL permission for changing the version state (publish/draft). Added permanent deletion of documents. Added deletion of part, field and document types (only possible when no longer in use). Notification mails: instead of receiving m... | SimpleDocument | daisydocs | daisydocs-1_2 | en | bruno | show |
| 1.0.0 to 1.1.0 upgrade | Changes (compared to Daisy 1.0.0) Features Introduced separate ACL permission for changing the version state (publish/draft). Added permanent deletion of documents. Added deletion of part, field and document types (only possible when no longer in use). Notification mails: instead of receiving m... | SimpleDocument | daisydocs | daisydocs-1_3 | en | bruno | show |
| 1.0.0 to 1.1.0 upgrade | Changes (compared to Daisy 1.0.0) Features Introduced separate ACL permission for changing the version state (publish/draft). Added permanent deletion of documents. Added deletion of part, field and document types (only possible when no longer in use). Notification mails: instead of receiving m... | SimpleDocument | daisydocs | daisydocs-1_4 | en | bruno | show |
| 1.1.0 to 1.2.0 upgrade | Changes (compared to Daisy 1.1.0) Features Graphical navigation tree editor that should enable non-technical users to edit the navigation tree (XML knowledge is no longer required). The tree editor works in both IE and Mozilla and doesn't require any server round tripping, it all works client s... | SimpleDocument | daisydocs | daisydocs-1_2 | en | bruno | show |
| 1.1.0 to 1.2.0 upgrade | Changes (compared to Daisy 1.1.0) Features Graphical navigation tree editor that should enable non-technical users to edit the navigation tree (XML knowledge is no longer required). The tree editor works in both IE and Mozilla and doesn't require any server round tripping, it all works client s... | SimpleDocument | daisydocs | daisydocs-1_3 | en | bruno | show |
| 1.1.0 to 1.2.0 upgrade | Changes (compared to Daisy 1.1.0) Features Graphical navigation tree editor that should enable non-technical users to edit the navigation tree (XML knowledge is no longer required). The tree editor works in both IE and Mozilla and doesn't require any server round tripping, it all works client s... | SimpleDocument | daisydocs | daisydocs-1_4 | en | bruno | show |
| 1.2 to 1.3 Milestone 1 upgrade | Changes (compared to Daisy 1.2) Features Document Variants: it is possible to have multiple variants of one document, which can be branch-variants or language-variants. These variants all share the same document ID, but are then distinguished by their branch and language. Document Tasks: these... | SimpleDocument | daisydocs | daisydocs-1_3 | en | bruno | show |
| 1.2 to 1.3 Milestone 1 upgrade | Changes (compared to Daisy 1.2) Features Document Variants: it is possible to have multiple variants of one document, which can be branch-variants or language-variants. These variants all share the same document ID, but are then distinguished by their branch and language. Document Tasks: these... | SimpleDocument | daisydocs | daisydocs-1_4 | en | bruno | show |
| 1.2 to 1.3 upgrade | These instructions are for upgrading from Daisy 1.2 to Daisy 1.3. If you are running a 1.3 milestone release, please see the documents describing the upgrade procedures for going from one milestone release to the next. If you are running an older milestone release then 1.3-M3, for example 1.3-M1... | SimpleDocument | daisydocs | daisydocs-1_3 | en | bruno | show |
| 1.2 to 1.3 upgrade | These instructions are for upgrading from Daisy 1.2 to Daisy 1.3. If you are running a 1.3 milestone release, please see the documents describing the upgrade procedures for going from one milestone release to the next. If you are running an older milestone release then 1.3-M3, for example 1.3-M1... | SimpleDocument | daisydocs | daisydocs-1_4 | en | bruno | show |
| 1.3-M1 to 1.3-M2 upgrade | Changes (compared to Daisy 1.3 Milestone 1) Features Authentication Schemes: this enables support for multiple external authentication mechanisms, an LDAP implementation is included with Daisy. The authentication scheme to use is configurable on a per-user level. It is also possible to auto-cre... | SimpleDocument | daisydocs | daisydocs-1_3 | en | bruno | show |
| 1.3-M1 to 1.3-M2 upgrade | Changes (compared to Daisy 1.3 Milestone 1) Features Authentication Schemes: this enables support for multiple external authentication mechanisms, an LDAP implementation is included with Daisy. The authentication scheme to use is configurable on a per-user level. It is also possible to auto-cre... | SimpleDocument | daisydocs | daisydocs-1_4 | en | bruno | show |
| 1.3-M2 to 1.3-M3 upgrade | Changes Various improvements to the skinning: the skinning now happens in two steps: first a page-specific stylesheet or template, and then a layout.xsl defining the general layout. The layout.xsl has a well-defined input. The common stylesheets have been dropped, instead a new fallback mechani... | SimpleDocument | daisydocs | daisydocs-1_3 | en | bruno | show |
| 1.3-M2 to 1.3-M3 upgrade | Changes Various improvements to the skinning: the skinning now happens in two steps: first a page-specific stylesheet or template, and then a layout.xsl defining the general layout. The layout.xsl has a well-defined input. The common stylesheets have been dropped, instead a new fallback mechani... | SimpleDocument | daisydocs | daisydocs-1_4 | en | bruno | show |
| 1.3-M3 compatibility notes | Skinning Daisy 1.3-M3 introduces an improved skinning system. Basically the XSLs are mostly the same, but the way they are applied is different. Skinning now happens in two steps: first a page-specific XSL (or template), and then the layout.xsl which does the general layout (on a well-defined in... | SimpleDocument | daisydocs | daisydocs-1_3 | en | bruno | show |
| 1.3-M3 compatibility notes | Skinning Daisy 1.3-M3 introduces an improved skinning system. Basically the XSLs are mostly the same, but the way they are applied is different. Skinning now happens in two steps: first a page-specific XSL (or template), and then the layout.xsl which does the general layout (on a well-defined in... | SimpleDocument | daisydocs | daisydocs-1_4 | en | bruno | show |
| 1.3-M3 to 1.3-RC upgrade | Changes language updates for Dutch, German, Polish and French. Upgrading Before starting Shutdown Daisy (the Repository Server, the Daisy Wiki, and the OpenJMS server) Make backups! More specifically: make a copy of the daisy data directory do a dump of the database: mysqldump daisyrepositor... | SimpleDocument | daisydocs | daisydocs-1_3 | en | bruno | show |
| 1.3-M3 to 1.3-RC upgrade | Changes language updates for Dutch, German, Polish and French. Upgrading Before starting Shutdown Daisy (the Repository Server, the Daisy Wiki, and the OpenJMS server) Make backups! More specifically: make a copy of the daisy data directory do a dump of the database: mysqldump daisyrepositor... | SimpleDocument | daisydocs | daisydocs-1_4 | en | bruno | show |
| 1.3-RC to 1.3 final upgrade | Changes Bug fixes Fixed bug in recursive include processing (reported by clint, kipkerplunk-daisy <at> yahoo <dot> com) Fixed problem with variantLastModified query identifier. Re-enabled Postgresql choice in installation program, upon request. Fix a bug in the navigation tree when the first do... | SimpleDocument | daisydocs | daisydocs-1_3 | en | bruno | show |
| 1.3-RC to 1.3 final upgrade | Changes Bug fixes Fixed bug in recursive include processing (reported by clint, kipkerplunk-daisy <at> yahoo <dot> com) Fixed problem with variantLastModified query identifier. Re-enabled Postgresql choice in installation program, upon request. Fix a bug in the navigation tree when the first do... | SimpleDocument | daisydocs | daisydocs-1_4 | en | bruno | show |
| 1.3 to 1.3.1 upgrade | What's new This release adds the ability to configure which external URL inclusions authors can do in documents. See Include Permissions and the email describing the related security issue. This is the only change in this release. After upgrading to this release, you will need to configure the ... | SimpleDocument | daisydocs | daisydocs-1_3 | en | bruno | show |
| 1.3 to 1.3.1 upgrade | What's new This release adds the ability to configure which external URL inclusions authors can do in documents. See Include Permissions and the email describing the related security issue. This is the only change in this release. After upgrading to this release, you will need to configure the ... | SimpleDocument | daisydocs | daisydocs-1_4 | en | bruno | show |
| 1.3 to 1.4-M1 upgrade | Changes New "Daisy Books" functionality for publishing books/manuals from Daisy documents. See the books documentation. Some features added as part of the Daisy Books implementation that are useful outside of books: full ID and fragment ID support in the editor: there is now a dialog for assig... | SimpleDocument | daisydocs | daisydocs-1_4 | en | bruno | show |
| 1.3 to 1.4 upgrade | Changes To get a full overview of all changes in Daisy 1.4, have a look at the notes of the various Milestone releases. Some highlights: "book" publication functionality (the major new feature of this release) A backup mechanism and accompanying backup tool Various improvements to the editor O... | SimpleDocument | daisydocs | daisydocs-1_4 | en | bruno | show |
| 1.4-M1 to 1.4-M2 upgrade | Changes Book related changes: The book definition editor now supports graphical editing of all its parts. This is the biggest change in this release (in terms of development effort). For book instances and publications within the book instance, there is now both a name and label (previously o... | SimpleDocument | daisydocs | daisydocs-1_4 | en | bruno | show |
| 1.4-M2 to 1.4-M3 upgrade | Changes Features Books: font size configurable through a publication property, changed the default value to 12pt (before it was 11pt) made logo alignment configurable through a publication property upgraded to Ibex 3.8.8 link extraction is now performed for the book-specific parts (see pluggab... | SimpleDocument | daisydocs | daisydocs-1_4 | en | bruno | show |
| 1.4-M3 to 1.4-final upgrade | Changes Bug fixes Misc improvements to the backup tool. Fix too strong validation on collection names when subscrbing on collections in the user settings. (DSY-228) Updated Polish, German and Russian translations (Dutch were already up to date, French is missing in this release). PosgreSQL jar ... | SimpleDocument | daisydocs | daisydocs-1_4 | en | bruno | show |
| 1.4 to 1.4.1 upgrade | Changes The Daisy 1.4 release shipped with incorrect character-decoding of request parameters and POST-bodies submitted from a web browser to the Daisy Wiki. This release fixes this problem. Next to that, the following small changes have been made: When creating a new document in Firefox 1.5, t... | SimpleDocument | daisydocs | daisydocs-1_4 | en | bruno | show |
| 1.4 to 1.5-M1 upgrade | Daisy 1.5-M1 was released on March 22, 2006. Changes Features Various query language improvements. See this mail and the updated query documentation. The content of the blobstore directory is now organised hierarchically. This should scale better on most file systems. A new field type, link, to... | SimpleDocument | daisydocs | daisydocs-1_5 | en | bruno | show |
| 1.4 to 1.5 upgrade | Daisy 1.5 was released on August 16, 2006. Read this document carefully, especially the upgrading instructions. Take your time to do the upgrade. This release contains various changes that will make future updates a lot easier. Changes Some important changes that affect deployment or compatibili... | SimpleDocument | daisydocs | daisydocs-1_5 | en | bruno | show |
| 1.5-M1 to 1.5-M2 upgrade | Daisy 1.5 Milestone 2 was released on June 21, 2006. Changes Important changes: read this section! Daisy Wiki: the configuration and data used by the Daisy Wiki is now stored in a separate wikidata directory, similar to the data directory of the repository server. The data directory contains th... | SimpleDocument | daisydocs | daisydocs-1_5 | en | bruno | show |
| 1.5-M2 to 1.5 final upgrade | Changes Only some small changes and bug fixes in this release: Updates to Dutch, German and Russian translations. Enable JMX for ActiveMQ, ActiveMQ's MBeans are browseable via Daisy's JMX console (HTTP on port 9264). Updated MX4J to version 3.0.1 daisy-wikidata-init: allow to specify empty dire... | SimpleDocument | daisydocs | daisydocs-1_5 | en | bruno | show |
| 1.5 to 1.5.1 upgrade | Changes If you are currently using Daisy 1.5.0, there is little reason to upgrade to this release. No changes have be done except for those listed below. Added characterEncoding=UTF-8 parameter to the MySQL JDBC URL, which is needed for correct UTF-8 support when UTF-8 is not the default charac... | SimpleDocument | daisydocs | daisydocs-1_5 | en | bruno | show |
| 1.5 to 2.0 changes | Core repository [important change] Daisy switched to namespaced document IDs. Before, document IDs where simply a sequence number, now they are the combination of a sequence number and a namespace suffix. For example "123-DSY". Namespaced document IDs allow export-import of documents between r... | SimpleDocument | daisydocs | daisydocs-2_0 | en | bruno | show |
| 1.5 to 2.0 compatibility | Change to namespaced document IDs Daisy Wiki compatibility URLs without a namespace still work as before, so installing this new Daisy version will not break all external links (and bookmarks, etc.). About the navigation: if you have navigation paths in which the node IDs are simply defined by t... | SimpleDocument | daisydocs | daisydocs-2_0 | en | bruno | show |
| 1.5 to 2.0 upgrade | These instructions now apply to Daisy 2.0.1. If you would still have a 2.0 download, we suggest you download 2.0.1 instead. Changes & compatibility Before upgrading you can skim over the changes. In case you've made any customization to Daisy (e.g. skins), or are using the Daisy APIs, have a loo... | SimpleDocument | daisydocs | daisydocs-2_0 | en | bruno | show |
| 2.0.1 to 2.0.2 upgrade | Plans for a 2.0.2 release have been discarded (unless some serious bug would pop up), instead we're going for a short-term 2.1 release. | SimpleDocument | daisydocs | daisydocs-2_0 | en | bruno | show |
| 2.0(.x) to 2.1. upgrade | These are the upgrade instructions for when you have currently Daisy 2.0 or 2.0.1 installed. If you have 2.1-RC installed, see here. Upgrading Daisy installation review In case you're not very familiar with Daisy, it is helpful to identify the main parts involved. The following picture illustrat... | SimpleDocument | daisydocs | daisydocs-2_1 | en | bruno | show |
| 2.0(.x) to 2.1 changes | Replaced Avalon Merlin by something new called the "Daisy Runtime" most users won't notice this the Daisy Runtime is basically some thin infrastructure around Spring. See docs. writing repository plugins (authentication schemes, extensions, ...) is now much better supported. Plugins can simply... | SimpleDocument | daisydocs | daisydocs-2_1 | en | bruno | show |
| 2.0(.x) to 2.1 compatibility | Skin compatibility There's a new layout-common.css, imported by layout.css and layout-mini.css The error.xsl changed a bit. There's a new plain.css, which needs to be linked by the layout.xsl. If you have a custom layout.xsl, then update it similar to the new default.xsl (just search in there ... | SimpleDocument | daisydocs | daisydocs-2_1 | en | bruno | show |
| 2.0-RC to 2.0 upgrade | Changes since 2.0-RC This is a list of all changes which happened since the 2.0-RC release (which is a bit more than expected). Further work on tanuki wrapper scripts. Updated external-include-rules.xml to handle the now-default case of not having "/daisy" in the mount point anymore. Some chang... | SimpleDocument | daisydocs | daisydocs-2_0 | en | bruno | show |
| 2.0 to 2.0.1 upgrade | Changes since 2.0 This is a list of all changes which happened since the 2.0 release. Navigation tree: in the query node, referencing values from outer queries using ${..} fails for some data types. See DSY-440. In the siteconf allow specification of the default collection using the collection ... | SimpleDocument | daisydocs | daisydocs-2_0 | en | mpo | show |
| 2.1-RC to 2.1 upgrade | Changes since 2.1-RC Further improvements to the HTML diff and the diff page in general. A direct link Actions -> Changes has been added to go to the diff without having to go via the versions page. Upgraded to FOP 0.94 (unfortunately, the footnotes-in-tables-and-lists bug is not yet fixed). Th... | SimpleDocument | daisydocs | daisydocs-2_1 | en | bruno | show |
| 2.1 to 2.2 changes | Changes Translation management + translation import/export We've added a bunch of translation management functionality. See also the documentation. New document model attributes to help keeping track of whether languages are in sync: on document: referenceLanguage on version: change type (majo... | SimpleDocument | daisydocs | daisydocs-2_2 | en | bruno | show |
| 2.1 to 2.2 compatibility | Access control (ACL) changes Read access details added, read-live permission removed IMPORTANT CHANGE! Anyone making use of access control should read this. The ACL model has been extended to allow to define detailed permissions when granting the read permission. We call this read access details... | SimpleDocument | daisydocs | daisydocs-2_2 | en | bruno | show |
| 2.1 to 2.2 upgrade | These are the upgrade instructions for when you have currently Daisy 2.1 installed. In case you have problems during the upgrade or notice errors or shortcomings in the instructions below, please let us know on the Daisy mailing list. Review compatibility notes Review the compatibility notes. As... | SimpleDocument | daisydocs | daisydocs-2_2 | en | bruno | show |
| 2.2-RC to 2.2 upgrade | Changes since 2.2-RC Misc fixes and translation updates. Upgrade instructions These are the upgrade instructions for when you have currently Daisy 2.2-RC installed. This release requires no special upgrade steps, besides putting the new Daisy distribution in place. In case you have problems duri... | SimpleDocument | daisydocs | daisydocs-2_2 | en | bruno | show |
| 2.2 to 2.3 changes | Changes Cross-document search and replace Daisy can now perform a search and replace across a set of documents. This feature is accessible via Tools -> Search & replace, or from the document basket or fulltext search results. Regular expression searching and sensible casing (keeping the case of ... | SimpleDocument | daisydocs | daisydocs-2_3 | en | karel | show |
| 2.2 to 2.3 compatibility | DocumentTaskManager Introduction To make it easier to add new types of document tasks some API changes were introduced. Deprecated / removed API TaskSpecifications are no longer created using the create[...]TaskSpecification methods on the DocumentTaskManager: createTaskSpecification(String de... | SimpleDocument | daisydocs | daisydocs-2_3 | en | karel | show |
| 2.2 to 2.3 upgrade | These are the upgrade instructions for when you have currently Daisy 2.2 installed. In case you have problems during the upgrade or notice errors or shortcomings in the instructions below, please let us know on the Daisy mailing list. Review compatibility notes Review the compatibility notes. Up... | SimpleDocument | daisydocs | daisydocs-2_3 | en | karel | show |
| About the knowledgebase | The knowledgebase itself runs on Daisy. It is an example of how something useful can be made with some simple customizations such as document information aggregation (a.k.a. publisher requests) and customized document styling. The implementation is part of the Daisy site sources which can be obt... | SimpleDocument | daisykb | main | en | bruno | show |
| Access annotations | When references to Daisy documents occur (in the output from Publisher prepared-document request), they are often annotated with information about the access rights the user has to the referenced document. More specificially, this happens for: links occurring in document content (attribute acce... | SimpleDocument | daisydocs | daisydocs-2_2 | en | bruno | show |
| Access annotations | When references to Daisy documents occur (in the output from Publisher prepared-document request), they are often annotated with information about the access rights the user has to the referenced document. More specificially, this happens for: links occurring in document content (attribute acce... | SimpleDocument | daisydocs | daisydocs-2_3 | en | bruno | show |
| Access Control | Introduction This document explains Daisy's features for access control: the authorisation of document read and write operations. In many systems, access control is configured by having access control lists (ACLs) attached to documents. These ACLs contain access control rules which tell for a ce... | SimpleDocument | daisydocs | daisydocs-1_2 | en | stevenn | show |
| Access Control | Introduction This document explains Daisy's features for access control: the authorisation of document operations such as read and write. While we usually talk about documents, technically the access control happens on the document variant level: a user is granted or denied access to a certain d... | SimpleDocument | daisydocs | daisydocs-1_3 | en | stevenn | show |
| Access Control | Introduction This document explains Daisy's features for access control: the authorisation of document operations such as read and write. While we usually talk about documents, technically the access control happens on the document variant level: a user is granted or denied access to a certain d... | SimpleDocument | daisydocs | daisydocs-1_4 | en | stevenn | show |
| Access Control | Introduction This document explains Daisy's features for access control: the authorisation of document operations such as read and write. While we usually talk about documents, technically the access control happens on the document variant level: a user is granted or denied access to a certain d... | SimpleDocument | daisydocs | daisydocs-1_5 | en | stevenn | show |
| Access Control | Introduction This document explains Daisy's features for access control: the authorisation of document operations such as read and write. While we usually talk about documents, technically the access control happens on the document variant level: a user is granted or denied access to a certain d... | SimpleDocument | daisydocs | daisydocs-2_0 | en | stevenn | show |
| Access Control | Introduction This document explains Daisy's features for access control: the authorisation of document operations such as read and write. While we usually talk about documents, technically the access control happens on the document variant level: a user is granted or denied access to a certain d... | SimpleDocument | daisydocs | daisydocs-2_1 | en | stevenn | show |
| Access Control | Introduction This section explains Daisy's document access control functionality. Access control concerns the authorization of document operations such as read and write. While we usually talk about documents, technically the access control happens on the document variant level: a user is grante... | SimpleDocument | daisydocs | daisydocs-2_2 | en | stevenn | show |
| Access Control | Introduction This section explains Daisy's document access control functionality. Access control concerns the authorization of document operations such as read and write. While we usually talk about documents, technically the access control happens on the document variant level: a user is grante... | SimpleDocument | daisydocs | daisydocs-2_3 | en | stevenn | show |
| ACL musings | Problems with the current ACL approach Our current access control system is quite interesting, in that we allow to select sets of documents using expressions and then specify the ACL rules that apply to those documents. Editing assistance The document-selection expressions can be of arbitrary co... | DaisyCommWikiDocument | daisywiki | main | en | bruno | show |
| ACL structure | | Image | daisydocs | daisydocs-1_2 | en | bruno | show |
| ACL structure | | Image | daisydocs | daisydocs-1_3 | en | bruno | show |
| ACL structure | | Image | daisydocs | daisydocs-1_4 | en | bruno | show |
| ACL structure | | Image | daisydocs | daisydocs-1_5 | en | bruno | show |
| ACL structure | | Image | daisydocs | daisydocs-2_0 | en | bruno | show |
| ACL structure | | Image | daisydocs | daisydocs-2_1 | en | bruno | show |
| ACL structure | | Image | daisydocs | daisydocs-2_2 | en | bruno | show |
| ACL structure | | Image | daisydocs | daisydocs-2_3 | en | bruno | show |
| Add a writing style to daisy-wiki | Overview The WYSIWYG editor component of Daisy 1.3 provides some constraints to the styles available for formatting text. While the available styles are sufficient for typical content, there are cases where additional styles are desirable. This document describes the steps necessary to add a new... | DaisyCommWikiDocument | daisywiki | main | en | cblin | show |
| Add your project to Eclipse | more info here. will be here soon. | SimpleDocument | handbook | main | en | hepabolu | show |
| Administration | This document describes a number of xReporter-administration related things. Creating users Creating a user is a matter of adding a record in a database table. The exact table and column names are configurable in the config.xml. By default it contains the following: <user-table table-name="user... | SimpleDocument | xreporter | main | en | stevenn | show |
| Aggregated documents | Description Create a new default document type (or part type) that defines a combination of multiple documents and/or queries Custom styling will then define how these items are layed out on the page. [todo] | DaisyCommWikiDocument | daisywiki | main | en | stevenn | show |
| Anpassung des Erscheinungsbilds für das Daisy Wiki | Das Erscheinungsbild des Daisy Wiki kann auf folgende Weise verändert werden: Anpassung eines bereits bestehenden Erscheinungsbild, dies geschieht mittels der Datei skinconf.xml, Erzeugung einer benutzerdefinierten Konfigurationsdatei, welche das Aussehen bestimmt. Der Name des standardmäßig ... | SimpleDocument | daisydocs | daisydocs-1_5 | de | bruno | show |
| Anpassung des Erscheinungsbilds für das Daisy Wiki | Das Erscheinungsbild des Daisy Wiki kann auf folgende Weise verändert werden: Anpassung eines bereits bestehenden Erscheinungsbild, dies geschieht mittels der Datei skinconf.xml, Erzeugung einer benutzerdefinierten Konfigurationsdatei, welche das Aussehen bestimmt. Der Name des standardmäßig ... | SimpleDocument | daisydocs | daisydocs-2_0 | de | bruno | show |
| Anpassung des Erscheinungsbilds für das Daisy Wiki | Das Erscheinungsbild des Daisy Wiki kann auf folgende Weise verändert werden: Anpassung eines bereits bestehenden Erscheinungsbild, dies geschieht mittels der Datei skinconf.xml, Erzeugung einer benutzerdefinierten Konfigurationsdatei, welche das Aussehen bestimmt. Der Name des standardmäßig ... | SimpleDocument | daisydocs | daisydocs-2_1 | de | bruno | show |
| Anpassung des Erscheinungsbilds für das Daisy Wiki | Das Erscheinungsbild des Daisy Wiki kann auf folgende Weise verändert werden: Anpassung eines bereits bestehenden Erscheinungsbild, dies geschieht mittels der Datei skinconf.xml, Erzeugung einer benutzerdefinierten Konfigurationsdatei, welche das Aussehen bestimmt. Der Name des standardmäßig ... | SimpleDocument | daisydocs | daisydocs-2_2 | de | bruno | show |
| Artifact | An artifact is a reference to a resource found in a repository. In Daisy, we use Maven for building the sources and hence use Maven-style repositories (the word repository here should not be confused with Daisy's own repository server). An artifact is identified by the tripple {groupId, artifact... | GlossaryEntry | daisydocs | daisydocs-2_1 | en | bruno | show |
| Artifact | An artifact is a reference to a resource found in a repository. In Daisy, we use Maven for building the sources and hence use Maven-style repositories (the word repository here should not be confused with Daisy's own repository server). An artifact is identified by the tripple {groupId, artifact... | GlossaryEntry | daisydocs | daisydocs-2_2 | en | bruno | show |
| Artifact | An artifact is a reference to a resource found in a repository. In Daisy, we use Maven for building the sources and hence use Maven-style repositories (the word repository here should not be confused with Daisy's own repository server). An artifact is identified by the tripple {groupId, artifact... | GlossaryEntry | daisydocs | daisydocs-2_3 | en | bruno | show |
| Artifacter tool | Introduction Daisy makes intensive use of the artifact concept. Both Maven and the Daisy Runtime make use of these artifacts. Since there are a lot of different Maven POMs and Daisy Runtime classloader definitions, it is useful to have some help in managing these. For example when you want to fi... | SimpleDocument | daisydocs | daisydocs-2_1 | en | bruno | show |
| Artifacter tool | Introduction Daisy makes intensive use of the artifact concept. Both Maven and the Daisy Runtime make use of these artifacts. Since there are a lot of different Maven POMs and Daisy Runtime classloader definitions, it is useful to have some help in managing these. For example when you want to fi... | SimpleDocument | daisydocs | daisydocs-2_2 | en | bruno | show |
| Artifacter tool | Introduction Daisy makes intensive use of the artifact concept. Both Maven and the Daisy Runtime make use of these artifacts. Since there are a lot of different Maven POMs and Daisy Runtime classloader definitions, it is useful to have some help in managing these. For example when you want to fi... | SimpleDocument | daisydocs | daisydocs-2_3 | en | bruno | show |
| Audit log | The Daisy repository server produces a JMS event for each (persistent) change that happens in the repository server. Examples include: creation/update/deletion of: documents, users, ACL, and any other entity. These JMS events are used for things like triggering update of the fulltext index, send... | DaisyCommWikiDocument | daisywiki | main | en | bruno | show |
| Auto Start/Stop Services on Mandriva Linux | Step 8 ? Automatic Start/Stop Mandriva/Mandrake 10.x Version française du document : http://www.apachefrance.com/Forums/index.php?showtopic=3606 Source Links : http://cocoondev.org/daisydocs-1_3/admin/193.html http://wrapper.tanukisoftware.org/doc/engl...troduction.html 1°-- Installl Java... | DaisyCommWikiDocument | daisywiki | main | en | patrick | show |
| Avalon Component | | Image | daisydocs | daisydocs-1_2 | en | bruno | show |
| Avalon Component | | Image | daisydocs | daisydocs-1_3 | en | bruno | show |
| Avalon Component | | Image | daisydocs | daisydocs-1_4 | en | bruno | show |
| Avalon Component | | Image | daisydocs | daisydocs-1_5 | en | bruno | show |
| Avalon Component | | Image | daisydocs | daisydocs-2_0 | en | bruno | show |
| Avalon Component | | Image | daisydocs | daisydocs-2_1 | en | bruno | show |
| Avalon Component | | Image | daisydocs | daisydocs-2_2 | en | bruno | show |
| Avalon Component | | Image | daisydocs | daisydocs-2_3 | en | bruno | show |
| Avalon Concerns | | Image | daisydocs | daisydocs-1_2 | en | bruno | show |
| Avalon Concerns | | Image | daisydocs | daisydocs-1_3 | en | bruno | show |
| Avalon Concerns | | Image | daisydocs | daisydocs-1_4 | en | bruno | show |
| Avalon Concerns | | Image | daisydocs | daisydocs-1_5 | en | bruno | show |
| Avalon Concerns | | Image | daisydocs | daisydocs-2_0 | en | bruno | show |
| Avalon Concerns | | Image | daisydocs | daisydocs-2_1 | en | bruno | show |
| Avalon Concerns | | Image | daisydocs | daisydocs-2_2 | en | bruno | show |
| Avalon Concerns | | Image | daisydocs | daisydocs-2_3 | en | bruno | show |
| Backgrounder FAQ | License Daisy is licensed using the Apache License 2.0, which is a BSD-style license. Basically, this license grants the user of Daisy the right to do anything he or she wants with the software, both in a commercial and non-commercial context. Daisy can be redistributed inside for-pay software, ... | SimpleDocument | daisy | main | en | stevenn | show |
| Backup locking | The practical side of making backups is explained in the section Making backups. Here we only describe the backup-lock mechanism, which is of use if you want to write your own backup tool. The repository server uses multiple storages: a relational database, the blobstore (a filesystem directory)... | SimpleDocument | daisydocs | daisydocs-1_4 | en | bruno | show |
| Backup locking | The practical side of making backups is explained in the section Making backups. Here we only describe the backup-lock mechanism, which is of use if you want to write your own backup tool. The repository server uses multiple storages: a relational database, the blobstore (a filesystem directory)... | SimpleDocument | daisydocs | daisydocs-1_5 | en | bruno | show |
| Backup locking | The practical side of making backups is explained in the section Making backups. Here we only describe the backup-lock mechanism, which is of use if you want to write your own backup tool. The repository server uses multiple storages: a relational database, the blobstore (a filesystem directory)... | SimpleDocument | daisydocs | daisydocs-2_0 | en | bruno | show |
| Backup locking | The practical side of making backups is explained in the section Making backups. Here we only describe the backup-lock mechanism, which is of use if you want to write your own backup tool. The repository server uses multiple storages: a relational database, the blobstore (a filesystem directory)... | SimpleDocument | daisydocs | daisydocs-2_1 | en | bruno | show |
| Backup locking | The practical side of making backups is explained in the section Making backups. Here we only describe the backup-lock mechanism, which is of use if you want to write your own backup tool. The repository server uses multiple storages: a relational database, the blobstore (a filesystem directory)... | SimpleDocument | daisydocs | daisydocs-2_2 | en | bruno | show |
| Backup locking | The practical side of making backups is explained in the section Making backups. Here we only describe the backup-lock mechanism, which is of use if you want to write your own backup tool. The repository server uses multiple storages: a relational database, the blobstore (a filesystem directory)... | SimpleDocument | daisydocs | daisydocs-2_3 | en | bruno | show |
| Basics | Where to put extensions Extensions can be site-specific or shared by all sites. Site-specific extensions are placed in a directory called cocoon in the directory of the site, thus: <webapp-directory>/daisy/sites/<sitename>/cocoon Cross-site extensions (shared by all sites) are placed in a direct... | SimpleDocument | daisydocs | daisydocs-1_3 | en | bruno | show |
| Basics | Where to put extensions Extensions can be site-specific or shared by all sites. Site-specific extensions are placed in a directory called cocoon in the directory of the site, thus: <webapp-directory>/daisy/sites/<sitename>/cocoon Cross-site extensions (shared by all sites) are placed in a direct... | SimpleDocument | daisydocs | daisydocs-1_4 | en | bruno | show |
| Basics | Where to put extensions Extensions can be site-specific or shared by all sites. Site-specific extensions are placed in a directory called cocoon in the directory of the site, thus: <wikidata directory>/sites/<sitename>/cocoon Cross-site extensions (shared by all sites) are placed in a directory ... | SimpleDocument | daisydocs | daisydocs-1_5 | en | bruno | show |
| Basics | Where to put extensions Extensions can be site-specific or shared by all sites. Site-specific extensions are placed in a directory called cocoon in the directory of the site, thus: <wikidata directory>/sites/<sitename>/cocoon Cross-site extensions (shared by all sites) are placed in a directory ... | SimpleDocument | daisydocs | daisydocs-2_0 | en | bruno | show |
| Basics | Where to put extensions Extensions can be site-specific or shared by all sites. Site-specific extensions are placed in a directory called cocoon in the directory of the site, thus: <wikidata directory>/sites/<sitename>/cocoon Cross-site extensions (shared by all sites) are placed in a directory ... | SimpleDocument | daisydocs | daisydocs-2_1 | en | bruno | show |
| Basics | Where to put extensions Extensions can be site-specific or shared by all sites. Site-specific extensions are placed in a directory called cocoon in the directory of the site, thus: <wikidata directory>/sites/<sitename>/cocoon Cross-site extensions (shared by all sites) are placed in a directory ... | SimpleDocument | daisydocs | daisydocs-2_2 | en | bruno | show |
| Basics | Where to put extensions Extensions can be site-specific or shared by all sites. Site-specific extensions are placed in a directory called cocoon in the directory of the site, thus: <wikidata directory>/sites/<sitename>/cocoon Cross-site extensions (shared by all sites) are placed in a directory ... | SimpleDocument | daisydocs | daisydocs-2_3 | en | bruno | show |
| Benutzer und Rollen | | Image | daisydocs | daisydocs-1_5 | de | bruno | show |
| Benutzer und Rollen | | Image | daisydocs | daisydocs-2_0 | de | bruno | show |
| Benutzer und Rollen | | Image | daisydocs | daisydocs-2_1 | de | bruno | show |
| Benutzer und Rollen | | Image | daisydocs | daisydocs-2_2 | de | bruno | show |
| Book Definition | This document describes the purpose and content of the various fields and parts of the BookDefinition document type. Fields BookPath Defines a hiearchical path (separated by slashes) for display of the book on overview pages. Parts BookDefinitionDescription The BookDefinitionDescription part def... | SimpleDocument | daisydocs | daisydocs-1_4 | en | bruno | show |
| Book Definition | This document describes the purpose and content of the various fields and parts of the BookDefinition document type. Fields BookPath Defines a hierarchical path (separated by slashes) for display of the book on overview pages. Parts BookDefinitionDescription The BookDefinitionDescription part de... | SimpleDocument | daisydocs | daisydocs-1_5 | en | bruno | show |
| Book Definition | This document describes the purpose and content of the various fields and parts of the BookDefinition document type. Fields BookPath Defines a hierarchical path (separated by slashes) for display of the book on overview pages. Parts BookDefinitionDescription The BookDefinitionDescription part de... | SimpleDocument | daisydocs | daisydocs-2_0 | en | bruno | show |
| Book Definition | This document describes the purpose and content of the various fields and parts of the BookDefinition document type. Fields BookPath Defines a hierarchical path (separated by slashes) for display of the book on overview pages. Parts BookDefinitionDescription The BookDefinitionDescription part de... | SimpleDocument | daisydocs | daisydocs-2_1 | en | bruno | show |
| Book Definition | This document describes the purpose and content of the various fields and parts of the BookDefinition document type. Fields BookPath Defines a hierarchical path (separated by slashes) for display of the book on overview pages. Parts BookDefinitionDescription The BookDefinitionDescription part de... | SimpleDocument | daisydocs | daisydocs-2_2 | en | bruno | show |
| Book Definition | This document describes the purpose and content of the various fields and parts of the BookDefinition document type. Fields BookPath Defines a hierarchical path (separated by slashes) for display of the book on overview pages. Parts BookDefinitionDescription The BookDefinitionDescription part de... | SimpleDocument | daisydocs | daisydocs-2_3 | en | bruno | show |
| book schema | | Image | daisydocs | daisydocs-1_4 | en | bruno | show |
| book schema | | Image | daisydocs | daisydocs-1_5 | en | bruno | show |
| book schema | | Image | daisydocs | daisydocs-2_0 | en | bruno | show |
| book schema | | Image | daisydocs | daisydocs-2_1 | en | bruno | show |
| book schema | | Image | daisydocs | daisydocs-2_2 | en | bruno | show |
| book schema | | Image | daisydocs | daisydocs-2_3 | en | bruno | show |
| Book Store | General The Book Store is responsible for the persistence of published books. It simply uses the filesystem as storage area. By default, the Book Store stores it files in the following directory: <daisy_home>/daisywiki/bookstore The location of this directory is however configurable in the coco... | SimpleDocument | daisydocs | daisydocs-1_4 | en | bruno | show |
| Book Store | General The Book Store is responsible for the persistence of published books. It simply uses the filesystem as storage area. By default, the Book Store stores it files in the following directory: <wikidata directory>/daisywiki/bookstore The location of this directory is however configurable in ... | SimpleDocument | daisydocs | daisydocs-1_5 | en | bruno | show |
| Book Store | General The Book Store is responsible for the persistence of published books. It simply uses the filesystem as storage area. By default, the Book Store stores it files in the following directory: <wikidata directory>/daisywiki/bookstore The location of this directory is however configurable in ... | SimpleDocument | daisydocs | daisydocs-2_0 | en | bruno | show |
| Book Store | General The Book Store is responsible for the persistence of published books. It simply uses the filesystem as storage area. By default, the Book Store stores it files in the following directory: <wikidata directory>/daisywiki/bookstore The location of this directory is however configurable in ... | SimpleDocument | daisydocs | daisydocs-2_1 | en | bruno | show |
| Book Store | General The Book Store is responsible for the persistence of published books. It simply uses the filesystem as storage area. By default, the Book Store stores it files in the following directory: <wikidata directory>/daisywiki/bookstore The location of this directory is however configurable in ... | SimpleDocument | daisydocs | daisydocs-2_2 | en | bruno | show |
| Book Store | General The Book Store is responsible for the persistence of published books. It simply uses the filesystem as storage area. By default, the Book Store stores it files in the following directory: <wikidata directory>/daisywiki/bookstore The location of this directory is however configurable in ... | SimpleDocument | daisydocs | daisydocs-2_3 | en | bruno | show |
| Branch variant | Each Daisy document can exist in multiple branch variants. Branch variants allow to maintain several different versions of the same content. A typical usage for branch variants is for software product documentation: with branch variants, you can start working on the content of the next version w... | GlossaryEntry | daisydocs | daisydocs-2_2 | en | bruno | show |
| Branch variant | Each Daisy document can exist in multiple branch variants. Branch variants allow to maintain several different versions of the same content. A typical usage for branch variants is for software product documentation: with branch variants, you can start working on the content of the next version w... | GlossaryEntry | daisydocs | daisydocs-2_3 | en | bruno | show |
| build-cocoon-targets | | Attachment | handbook | main | en | hepabolu | show |
| Calendar extension | Displaying a calendar in Daisy This tutorial will show you how to create a Daisy Wiki extension to display a calendar. Each date of the calendar will be associated with documents in the Daisy repository based on a date field in the documents. Create a field and document type For the purpose of t... | DaisyCommWikiDocument | daisywiki | main | en | bruno | show |
| calendar screenshot | | Image | daisywiki | main | en | bruno | show |
| Case Study | Objective: build a simple website using Cocoon and expand it as time/tutorial progresses. HealthyCocoon You are a web developer wanting to use Cocoon for the newly acquired project of a small company called HealthyCocoon. This company consists of 3 people and their primary business is selling qu... | SimpleDocument | handbook | main | en | hepabolu | show |
| Case Study - Step 1 | HealthyCocoon version 1 Talking about the requirements for the HealthyCocoon site resulted in the following: a home page with a short description of the website/company a contact page with the address and an email address a services page with the explanation of their products and services all p... | SimpleDocument | handbook | main | en | hepabolu | show |
| centr-screenshot | | Image | daisywiki | main | en | stevenn | show |
| Changes between Daisy 1.5.1 (rev. 3446) and Daisy 2.0 RC (rev. 3856) | Revision 3842 (Mar 16, 2007) Upgraded to final jBPM 3.2 release. Apparently the schema changed a bit, so drop the workflow tables by executing the following SQL on the daisyrepository database. Warning: this will remove all your workflow data. delete from daisy_system where propname = 'jbpm_sche... | DaisyCommWikiDocument | daisywiki | main | en | deining | show |
| Changes between Daisy 2.0.1 (=revision 3952) and Daisy 2.1 (=revision 4366) | Revision 4260 (July 30, 2007) Switching to Maven 1.1 as build tool. Just about everything stays the same, except that the manual installation of the maven plugins is not needed anymore. As you can see in the updated README.txt, the maven repository should now be http://repo1.maven.org/maven/ ins... | DaisyCommWikiDocument | daisywiki | main | en | deining | show |
| Changes between Daisy 2.0 RC (rev. 3856) and Daisy 2.0.1 (rev. 3952) | Revision 3872 (Mar 23, 2007) Upgraded to Lucene 2.1. Added a new field to the index to uniquely identify a document variant, which allows to exploit the new delete-via-writer functionality in this Lucene release (more details in commit mail). This requires a full rebuild of the fulltext index (f... | DaisyCommWikiDocument | daisywiki | main | en | deining | show |
| Changes between Daisy 2.1 (=revision 4366) and Daisy 2.2 (=revision 4657) | Revision 4573 (December 7, 2007) Fixed an error in the database schema, column locks.time_expires should allow null values. Login to MySQL and then execute (copy-paste): alter table locks change time_expires time_expires datetime; Revision 4546 (November 29, 2007) Changed behavior of ACL access ... | DaisyCommWikiDocument | daisywiki | main | en | deining | show |
| Changes since Daisy 2.2 (=revision 4657) | MySQL schema changes: alter table `daisydev_repository`.`document_tasks` change column `script` `action_type` varchar(100) NOT NULL; alter table `daisydev_repository`.`document_tasks` change column `script_language` `action_parameters` longtext; | DaisyCommWikiDocument | daisywiki | main | en | deining | show |
| Changing location (port or machine) of the different processes | This section details the changes to be done to run the different servers needed for Daisy on different machines or let them listen to different ports. The machine on which you want to run the Daisy Wiki only needs the DAISY_HOME/daisywiki subdirectory. The machine on which you want to run the r... | SimpleDocument | daisydocs | daisydocs-1_3 | en | bruno | show |
| Changing location (port or machine) of the different processes | This section details the changes to be done to run the different servers needed for Daisy on different machines or let them listen to different ports. The machine on which you want to run the Daisy Wiki only needs the DAISY_HOME/daisywiki subdirectory. The machine on which you want to run the r... | SimpleDocument | daisydocs | daisydocs-1_4 | en | bruno | show |
| Changing location (port or machine) of the different processes | This section details the changes to be done to run the different servers needed for Daisy on different machines or let them listen to different ports. The machine on which you want to run the Daisy Wiki only needs the DAISY_HOME/daisywiki subdirectory. The machine on which you want to run the r... | SimpleDocument | daisydocs | daisydocs-1_5 | en | bruno | show |
| Changing location (port or machine) of the different processes | This section details the changes to be done to run the different servers needed for Daisy on different machines or let them listen to different ports. The machine on which you want to run the Daisy Wiki only needs the DAISY_HOME/daisywiki subdirectory. The machine on which you want to run the r... | SimpleDocument | daisydocs | daisydocs-2_0 | en | bruno | show |
| Changing location (port or machine) of the different processes | This section details the changes to be done to run the different servers needed for Daisy on different machines or let them listen to different ports. The machine on which you want to run the Daisy Wiki only needs the DAISY_HOME/daisywiki subdirectory. The machine on which you want to run the r... | SimpleDocument | daisydocs | daisydocs-2_1 | en | bruno | show |
| Changing location (port or machine) of the different processes | This section details the changes to be done to run the different servers needed for Daisy on different machines or let them listen to different ports. The machine on which you want to run the Daisy Wiki only needs the DAISY_HOME/daisywiki subdirectory. The machine on which you want to run the r... | SimpleDocument | daisydocs | daisydocs-2_2 | en | bruno | show |
| Changing location (port or machine) of the different processes | This section details the changes to be done to run the different servers needed for Daisy on different machines or let them listen to different ports. The machine on which you want to run the Daisy Wiki only needs the DAISY_HOME/daisywiki subdirectory. The machine on which you want to run the r... | SimpleDocument | daisydocs | daisydocs-2_3 | en | bruno | show |
| Charts | Overview Since xReporter 1.3, a new output format is available: charts. While it is possible to dynamically get charts for any report, it is more interesting to define report-specific charts. Creating your first chart Overview Creating a chart is a matter of three simple steps: Create a format ... | SimpleDocument | xreporter | main | en | bruno | show |
| CHS | Introduction CHS is a showcase of the integration between Cocoon, Hibernate and Spring. This component is made available outside of the main Cocoon CVS repository because it relies on Hibernate which is LGPL licensed and as such cannot be added to Apache's CVS repository. Howto (for Cocoon 2.1... | SimpleDocument | main | main | en | ugo | show |
| class diagram | | Image | daisywiki | main | en | tim | show |
| classes diagram | | Image | daisywiki | main | en | sokol8 | show |
| Client-side Javascript todo list | This page is used to keep a list of things that can be improved in the client-side javascript area. Feel free to add/comment/update. there's now always a daisy object available with basic stuff like mountPoint and siteName (see layout.xsl). The document/naveditor specific things for these can ... | DaisyCommWikiDocument | daisywiki | main | en | bruno | show |
| cocoondev logo | | Image | main | main | en | stevenn | show |
| Cocoon GetTogether 2006 presentation | Presentation given by Bruno Dumon at the Cocoon GetTogether on October 4, 2006 about Daisy and document publishing in Daisy: presentation. Also check out Gustavo Nalle Fernandes' presentation on "Devware", a VMware image providing various development tools including Daisy. | DaisyCommWikiDocument | daisywiki | main | en | bruno | show |
| Cocoon GT presentation | | Attachment | daisywiki | main | en | bruno | show |
| Cocoon Handbook TOC | | Navigation | handbook | main | en | stevenn | show |
| Cocoon Integration | Concepts The xReporter server (which runs inside Phoenix) contains all logic related to the execution of reports. The output generated by xReporter however is always XML. That XML needs to be transformed one way or the other before displaying to the user. This is a job for the presentationlayer.... | SimpleDocument | xreporter | main | en | stevenn | show |
| cocoon screenshot | | Image | daisywiki | main | en | bruno | show |
| Coding style | Without getting religious about coding style guidelines, it is pleasant and productive if all code follows more or less the same style. Basically, just do the same as the current sources, and follow the standard Java conventions (ClassNamesLikeThis, static finals in uppercase, etc). Opening brac... | SimpleDocument | daisydocs | daisydocs-2_1 | en | bruno | show |
| Coding style | Without getting religious about coding style guidelines, it is pleasant and productive if all code follows more or less the same style. Basically, just do the same as the current sources, and follow the standard Java conventions (ClassNamesLikeThis, static finals in uppercase, etc). Opening brac... | SimpleDocument | daisydocs | daisydocs-2_2 | en | bruno | show |
| Coding style | Without getting religious about coding style guidelines, it is pleasant and productive if all code follows more or less the same style. Basically, just do the same as the current sources, and follow the standard Java conventions (ClassNamesLikeThis, static finals in uppercase, etc). Opening brac... | SimpleDocument | daisydocs | daisydocs-2_3 | en | bruno | show |
| Common | Various format types allow to alter their behaviour by: specifying a custom XSLT transformation to be used and/or by configuring the styling process by means of an XML configuration file (also called the "stylesheet parameterization files"). This is in fact what report-specific styling is all ... | SimpleDocument | xreporter | main | en | bruno | show |
| Common configuration files | As of Daisy 2.0, the tanuki wrapper scripts are integrated into the Daisy binary distribution. Therefore these manual instructions only apply if you want to integrate the wrapper scripts into an existing instance of Daisy 1.5. Alternatively, you can upgrade to Daisy 2.0 and use the scripts out o... | SimpleDocument | daisydocs | daisydocs-1_5 | en | deining | show |
| common xsl | | Image | xreporter | main | en | stevenn | show |
| Community | Getting involved Daisy is an open-source project with a very liberal license. This means a lot more than just giving the source code away for free, and you as a user sitting back and anxiously awaiting the next release. We welcome your participation, being it questions, comments, remarks, bug re... | SimpleDocument | daisy | main | en | stevenn | show |
| Component configuration | The API The current configuration system is an interim solution, mainly for backwards compatibility with our older runtime environment (Avalon Merlin). Nonetheless, it's not bad, though in the future we'll likely add more advanced features like runtime reloading and notification of configuration... | SimpleDocument | daisydocs | daisydocs-2_1 | en | bruno | show |
| Component configuration | The API The current configuration system is an interim solution, mainly for backwards compatibility with our older runtime environment (Avalon Merlin). Nonetheless, it's not bad, though in the future we'll likely add more advanced features like runtime reloading and notification of configuration... | SimpleDocument | daisydocs | daisydocs-2_2 | en | bruno | show |
| Component configuration | The API The current configuration system is an interim solution, mainly for backwards compatibility with our older runtime environment (Avalon Merlin). Nonetheless, it's not bad, though in the future we'll likely add more advanced features like runtime reloading and notification of configuration... | SimpleDocument | daisydocs | daisydocs-2_3 | en | bruno | show |
| Concept and general instructions | If you want to run Daisy as part of your operational environment, you might prefer to run the different Daisy components as services, which you can easily start, stop and restart, and which ideally run under a specific user (perhaps with restricted privileges). We recommend using "wrapper" for t... | SimpleDocument | daisydocs | daisydocs-2_0 | en | stevenn | show |
| Concept and general instructions | If you want to run Daisy as part of your operational environment, you might prefer to run the different Daisy components as services, which you can easily start, stop and restart, and which ideally run under a specific user (perhaps with restricted privileges). We recommend using "wrapper" for t... | SimpleDocument | daisydocs | daisydocs-2_1 | en | stevenn | show |
| Concept and general instructions | If you want to run Daisy as part of your operational environment, you might prefer to run the different Daisy components as services, which you can easily start, stop and restart, and which ideally run under a specific user (perhaps with restricted privileges). We recommend using "wrapper" for t... | SimpleDocument | daisydocs | daisydocs-2_2 | en | stevenn | show |
| Concept and general instructions | If you want to run Daisy as part of your operational environment, you might prefer to run the different Daisy components as services, which you can easily start, stop and restart, and which ideally run under a specific user (perhaps with restricted privileges). We recommend using "wrapper" for t... | SimpleDocument | daisydocs | daisydocs-2_3 | en | stevenn | show |
| config/build/deploy process | After installation, you may be wondering what all the directories are that were created, and what needs to be done if you change configuration files or add reports. This document should shine some light on this. This document applies to xReporter version 1.2 Overview of the different directorie... | SimpleDocument | xreporter | main | en | stevenn | show |
| Configuring upload limits | Daisy has no arbitrary limits on the size of the document parts, the eventual limits are the available disk space, file system limitations, and the java.lang.Long.MAX_VALUE value. However, the Daisy Wiki and the Daisy Repository Server have configurable limits of how much data one is allowed to ... | SimpleDocument | daisydocs | daisydocs-1_3 | en | bruno | show |
| Configuring upload limits | Daisy has no arbitrary limits on the size of the document parts, the eventual limits are the available disk space, file system limitations, and the java.lang.Long.MAX_VALUE value. However, the Daisy Wiki and the Daisy Repository Server have configurable limits of how much data one is allowed to ... | SimpleDocument | daisydocs | daisydocs-1_4 | en | bruno | show |
| Configuring upload limits | Daisy has no arbitrary limits on the size of the document parts, the eventual limits are the available disk space, file system limitations, and the java.lang.Long.MAX_VALUE value. However, the Daisy Wiki and the Daisy Repository Server have configurable limits of how much data one is allowed to ... | SimpleDocument | daisydocs | daisydocs-1_5 | en | bruno | show |
| Configuring upload limits | Daisy has no arbitrary limits on the size of the document parts, the eventual limits are the available disk space, file system limitations, and the java.lang.Long.MAX_VALUE value. However, the Daisy Wiki and the Daisy Repository Server have configurable limits of how much data one is allowed to ... | SimpleDocument | daisydocs | daisydocs-2_0 | en | bruno | show |
| Configuring upload limits | Daisy has no arbitrary limits on the size of the document parts, the eventual limits are the available disk space, file system limitations, and the java.lang.Long.MAX_VALUE value. However, the Daisy Wiki and the Daisy Repository Server have configurable limits of how much data one is allowed to ... | SimpleDocument | daisydocs | daisydocs-2_1 | en | bruno | show |
| Configuring upload limits | Daisy has no arbitrary limits on the size of the document parts, the eventual limits are the available disk space, file system limitations, and the java.lang.Long.MAX_VALUE value. However, the Daisy Wiki and the Daisy Repository Server have configurable limits of how much data one is allowed to ... | SimpleDocument | daisydocs | daisydocs-2_2 | en | bruno | show |
| Configuring upload limits | Daisy has no arbitrary limits on the size of the document parts, the eventual limits are the available disk space, file system limitations, and the java.lang.Long.MAX_VALUE value. However, the Daisy Wiki and the Daisy Repository Server have configurable limits of how much data one is allowed to ... | SimpleDocument | daisydocs | daisydocs-2_3 | en | bruno | show |
| Connecting to Jetty via mod_jk | The daisy installation comes bundled with Jetty as servlet engine. The daisywiki frontend runs as web application inside Jetty which listens on port 8888 by default. If you are interested in running the daisywiki frontend on port 80, you may put the Apache webserver in front of daisy. Doing so i... | DaisyCommWikiDocument | daisywiki | main | en | deining | show |
| Content Repository | | KnowledgeBaseCategory | daisykb | main | en | bruno | show |
| Content repository - customization and development | | FAQCategory | daisydocs | daisydocs-2_0 | en | bruno | show |
| Content repository - customization and development | | FAQCategory | daisydocs | daisydocs-2_1 | en | bruno | show |
| Content repository - customization and development | | FAQCategory | daisydocs | daisydocs-2_2 | en | bruno | show |
| Content repository - customization and development | | FAQCategory | daisydocs | daisydocs-2_3 | en | bruno | show |
| Content repository - general | | FAQCategory | daisydocs | daisydocs-2_0 | en | bruno | show |
| Content repository - general | | FAQCategory | daisydocs | daisydocs-2_1 | en | bruno | show |
| Content repository - general | | FAQCategory | daisydocs | daisydocs-2_2 | en | bruno | show |
| Content repository - general | | FAQCategory | daisydocs | daisydocs-2_3 | en | bruno | show |
| Contributor/Committer tips | Coding style Without getting religious about coding style guidelines, it is pleasant and productive if all code follows more or less the same style. Basically, just do the same as the current sources, and follow the standard Java conventions (ClassNamesLikeThis, static finals in uppercase, etc).... | SimpleDocument | daisydocs | daisydocs-1_5 | en | bruno | show |
| Contributor/Committer tips | Coding style Without getting religious about coding style guidelines, it is pleasant and productive if all code follows more or less the same style. Basically, just do the same as the current sources, and follow the standard Java conventions (ClassNamesLikeThis, static finals in uppercase, etc).... | SimpleDocument | daisydocs | daisydocs-2_0 | en | bruno | show |
| Contributor/Committer tips | This section contains information useful for people working on the Daisy source code. See also this related info in other places: Source code Repository implementation notes Daisy Wiki implementation notes | SimpleDocument | daisydocs | daisydocs-2_1 | en | bruno | show |
| Contributor/Committer tips | This section contains information useful for people working on the Daisy source code. See also this related info in other places: Source code Repository implementation notes Daisy Wiki implementation notes | SimpleDocument | daisydocs | daisydocs-2_2 | en | bruno | show |
| Contributor/Committer tips | This section contains information useful for people working on the Daisy source code. See also this related info in other places: Source code Repository implementation notes Daisy Wiki implementation notes | SimpleDocument | daisydocs | daisydocs-2_3 | en | bruno | show |
| CoUnit | Introduction CoUnit is a unit testing framework for Cocoon applications. It can be used to specify and execute unit tests for pipelines and stylesheets. CoUnit was developed by Nico Verwer and Jan Willem Boer, and is open source software (actually, it is in the public domain). CoUnit is not me... | SimpleDocument | main | main | en | nverwer | show |
| CoUnit code | | Attachment | main | main | en | nverwer | show |
| counit-html-output | | Image | main | main | en | nverwer | show |
| Creating a book | The only thing required to publish a book is a book definition. Usually, you will simply set up a Daisy Wiki site for the purpose of creating/editing the book content. However, instead of using a navigation tree definition, you will use a book definition. Creating a new book from scratch Assumin... | SimpleDocument | daisydocs | daisydocs-1_4 | en | bruno | show |
| Creating a book | The only thing required to publish a book is a book definition. Quickly trying it out To create (publish) a book based on existing content: Create a book definition document: create a document as usual but choose the "Book Definition" document type. Add some section nodes to it, or alternativel... | SimpleDocument | daisydocs | daisydocs-1_5 | en | bruno | show |
| Creating a book | The only thing required to publish a book is a book definition. Quickly trying it out To create (publish) a book based on existing content: Create a book definition document: create a document as usual but choose the "Book Definition" document type. Add some section nodes to it, or alternativel... | SimpleDocument | daisydocs | daisydocs-2_0 | en | bruno | show |
| Creating a book | The only thing required to publish a book is a book definition. Quickly trying it out To create (publish) a book based on existing content: Create a book definition document: create a document as usual but choose the "Book Definition" document type. Add some section nodes to it, or alternativel... | SimpleDocument | daisydocs | daisydocs-2_1 | en | bruno | show |
| Creating a book | The only thing required to publish a book is a book definition. Quickly trying it out To create (publish) a book based on existing content: Create a book definition document: create a document as usual but choose the "Book Definition" document type. Add some section nodes to it, or alternativel... | SimpleDocument | daisydocs | daisydocs-2_2 | en | bruno | show |
| Creating a book | The only thing required to publish a book is a book definition. Quickly trying it out To create (publish) a book based on existing content: Create a book definition document: create a document as usual but choose the "Book Definition" document type. Add some section nodes to it, or alternativel... | SimpleDocument | daisydocs | daisydocs-2_3 | en | bruno | show |
| Creating a multi role authentication scheme | This step by step instruction explains how to extend the Daisy CMS with your own authentication scheme that fits your needs. Assumption: You already set up daisy on a windows system and everything's working great. Your also doing the codeing and compiling on a separate system (a mac) because you... | DaisyCommWikiDocument | daisywiki | main | en | timmcd | show |
| Creating a skin | The anatomy of a skin A skin consists of a set of files: CSS file(s), images, XSLT stylesheets, and possibly others which are grouped below one directory. The directory containing the skins is located at: <DAISY_HOME>/daisywiki/webapp/daisy/resources/skins On a blank Daisy install, this contains... | SimpleDocument | daisydocs | daisydocs-1_3 | en | bruno | show |
| Creating a skin | The anatomy of a skin A skin consists of a set of files: CSS file(s), images, XSLT stylesheets, and possibly others which are grouped below one directory. The directory containing the skins is located at: <DAISY_HOME>/daisywiki/webapp/daisy/resources/skins On a blank Daisy install, this contains... | SimpleDocument | daisydocs | daisydocs-1_4 | en | bruno | show |
| Creating a skin | The anatomy of a skin A skin consists of a set of files: CSS file(s), images, XSLT stylesheets, and possibly others which are grouped below one directory. The directory containing the skins is located at: <wikidata directory>/resources/skins The name of the skin is the name of the directory belo... | SimpleDocument | daisydocs | daisydocs-1_5 | en | bruno | show |
| Creating a skin | The anatomy of a skin A skin consists of a set of files: CSS file(s), images, XSLT stylesheets, and possibly others which are grouped below one directory. The directory containing the skins is located at: <wikidata directory>/resources/skins The name of the skin is the name of the directory belo... | SimpleDocument | daisydocs | daisydocs-2_0 | en | bruno | show |
| Creating a skin | The anatomy of a skin A skin consists of a set of files: CSS file(s), images, XSLT stylesheets, and possibly others which are grouped below one directory. The directory containing the skins is located at: <wikidata directory>/resources/skins The name of the skin is the name of the directory belo... | SimpleDocument | daisydocs | daisydocs-2_1 | en | bruno | show |
| Creating a skin | The anatomy of a skin A skin consists of a set of files: CSS file(s), images, XSLT stylesheets, and possibly others which are grouped below one directory. The directory containing the skins is located at: <wikidata directory>/resources/skins The name of the skin is the name of the directory belo... | SimpleDocument | daisydocs | daisydocs-2_2 | en | bruno | show |
| Creating a skin | The anatomy of a skin A skin consists of a set of files: CSS file(s), images, XSLT stylesheets, and possibly others which are grouped below one directory. The directory containing the skins is located at: <wikidata directory>/resources/skins The name of the skin is the name of the directory belo... | SimpleDocument | daisydocs | daisydocs-2_3 | en | bruno | show |
| Creating your own authentication scheme | This step by step instruction explains how to extend the Daisy CMS with your own authentication scheme that fits your needs. Assumption: You already set up a unix system and created your users inside that system. Users will access your system via ssh. Task: You would like to use your existing us... | DaisyCommWikiDocument | daisywiki | main | en | deining | show |
| Custom document editors | General This design proposal is about letting wiki developers create completely custom document editors. TODO: add examples, more detailed description | DaisyCommWikiDocument | daisywiki | main | en | karel | show |
| Customization and development | | KnowledgeBaseCategory | daisykb | main | en | bruno | show |
| Custom workflow task screens | Why customizing the workflow screens There are two ways to customize the workflow screens, each with specific use cases. Editing Daisy documents Most workflow tasks require the user to open the document related to the workflow task in a new separate window, save the document, close the new windo... | SimpleDocument | daisydocs | daisydocs-2_3 | en | karel | show |
| CVSSource | Introduction CVSSource is a CVS 'source' (i.e. a new protocol) implementation for Cocoon, giving you read/write access to files stored in a CVS repository. This component is made available outside of the main Cocoon CVS repository because it relies on the CVS client package of JCVS which is LGPL... | SimpleDocument | main | main | en | stevenn | show |
| Daisy | Introduction Daisy is an open-source content management framework. It consists of a standalone repository server and a sample Cocoon web application to access and edit documents in the repository. The repository offers an XML/HTTP-based interface to the outside world, and its key distinguishing ... | SimpleDocument | main | main | en | stevenn | show |
| daisy_repo_clients | | Image | daisy | main | en | bruno | show |
| Daisy *DE*tachment client | People coming from classic office environments are easily lured into the benefits of centralized content management by the ease of use of the daisy wysiwyg editor. Without losing a recognisable content authoring environment they are happy to find: one centrally managed version of things allowi... | DaisyCommWikiDocument | daisywiki | main | en | bruno | show |
| daisy-2.2-docs-fop | | Attachment | daisywiki | main | en | karel | show |
| daisy-2.2-docs-fop0.95beta | | Attachment | daisywiki | main | en | karel | show |
| daisy-2.2-docs-ibex | | Attachment | daisywiki | main | en | karel | show |
| Daisy books enhancements | Daisy contains a book-publishing module, whose purpose is to publish nice "books" from Daisy documents in a variety of formats (currently HTML and PDF). The books are produced in batch, the result is a set of static files. A variety of enhancements can be done to this module: producing OpenOffi... | DaisyCommWikiDocument | daisywiki | main | en | bruno | show |
| Daisy Books Overview | Introduction The purpose of Daisy Books is to publish a set of aggregated Daisy documents as one whole, thus like a book or manual. Books can be published in various forms, including PDF and HTML (as one page or chunked into multiple pages). Technically, Daisy Books is part of (= integrated in) ... | SimpleDocument | daisydocs | daisydocs-1_4 | en | bruno | show |
| Daisy Books Overview | Introduction The purpose of Daisy Books is to publish a set of aggregated Daisy documents as one whole, thus like a book or manual. Books can be published in various forms, including PDF and HTML (as one page or chunked into multiple pages). Technically, Daisy Books is part of (= integrated in) ... | SimpleDocument | daisydocs | daisydocs-1_5 | en | bruno | show |
| Daisy Books Overview | Introduction The purpose of Daisy Books is to publish a set of aggregated Daisy documents as one whole, thus like a book or manual. Books can be published in various forms, including PDF and HTML (as one page or chunked into multiple pages). Technically, Daisy Books is part of (= integrated in) ... | SimpleDocument | daisydocs | daisydocs-2_0 | en | bruno | show |
| Daisy Books Overview | Introduction The purpose of Daisy Books is to publish a set of aggregated Daisy documents as one whole, thus like a book or manual. Books can be published in various forms, including PDF and HTML. The HTML can be published as as one big page or chunked into multiple pages, the chunks don't need ... | SimpleDocument | daisydocs | daisydocs-2_1 | en | bruno | show |
| Daisy Books Overview | Introduction The purpose of Daisy Books is to publish a set of aggregated Daisy documents as one whole, thus like a book or manual. Books can be published in various forms, including PDF and HTML. The HTML can be published as as one big page or chunked into multiple pages, the chunks don't need ... | SimpleDocument | daisydocs | daisydocs-2_2 | en | bruno | show |
| Daisy Books Overview | Introduction The purpose of Daisy Books is to publish a set of aggregated Daisy documents as one whole, thus like a book or manual. Books can be published in various forms, including PDF and HTML. The HTML can be published as as one big page or chunked into multiple pages, the chunks don't need ... | SimpleDocument | daisydocs | daisydocs-2_3 | en | bruno | show |
| Daisy Build System | The build system used by Daisy is Maven, an Apache project. Maven intro What follows is the very-very-quick Maven intro, for those not familiar with Maven. Unlike Ant, where you tell how your code should be build, in Maven you simply tell what directory contains your code, and what the dependenc... | SimpleDocument | daisydocs | daisydocs-1_2 | en | bruno | show |
| Daisy Build System | The build system used by Daisy is Maven, an Apache project. Maven intro What follows is the very-very-quick Maven intro, for those not familiar with Maven. Unlike Ant, where you tell how your code should be build, in Maven you simply tell what directory contains your code, and what the dependenc... | SimpleDocument | daisydocs | daisydocs-1_3 | en | bruno | show |
| Daisy Build System | The build system used by Daisy is Maven, an Apache project. Maven intro What follows is the very-very-quick Maven intro, for those not familiar with Maven. Unlike Ant, where you tell how your code should be build, in Maven you simply tell what directory contains your code, and what the dependenc... | SimpleDocument | daisydocs | daisydocs-1_4 | en | bruno | show |
| Daisy Build System | The build system used by Daisy is Maven, an Apache project. Maven intro What follows is the very-very-quick Maven intro, for those not familiar with Maven. Unlike Ant, where you tell how your code should be build, in Maven you simply tell what directory contains your code, and what the dependenc... | SimpleDocument | daisydocs | daisydocs-1_5 | en | bruno | show |
| Daisy Build System | The build system used by Daisy is Maven, an Apache project. Maven intro What follows is the very-very-quick Maven intro, for those not familiar with Maven. Unlike Ant, where you tell how your code should be build, in Maven you simply tell what directory contains your code, and what the dependenc... | SimpleDocument | daisydocs | daisydocs-2_0 | en | bruno | show |
| Daisy Build System | We should consider removing this document, Maven is common enough these days. The build system used by Daisy is Maven, an Apache project. Maven intro What follows is the very-very-quick Maven intro, for those not familiar with Maven. Unlike Ant, where you tell how your code should be build, in M... | SimpleDocument | daisydocs | daisydocs-2_1 | en | bruno | show |
| Daisy Build System | We should consider removing this document, Maven is common enough these days. The build system used by Daisy is Maven, an Apache project. Maven intro What follows is the very-very-quick Maven intro, for those not familiar with Maven. Unlike Ant, where you tell how your code should be build, in M... | SimpleDocument | daisydocs | daisydocs-2_2 | en | bruno | show |
| Daisy Build System | We should consider removing this document, Maven is common enough these days. The build system used by Daisy is Maven, an Apache project. Maven intro What follows is the very-very-quick Maven intro, for those not familiar with Maven. Unlike Ant, where you tell how your code should be build, in M... | SimpleDocument | daisydocs | daisydocs-2_3 | en | bruno | show |
| Daisy Client API | | Image | daisydocs | daisydocs-1_2 | en | bruno | show |
| Daisy Client API | | Image | daisydocs | daisydocs-1_3 | en | bruno | show |
| Daisy Client API | | Image | daisydocs | daisydocs-1_4 | en | bruno | show |
| Daisy Client API | | Image | daisydocs | daisydocs-1_5 | en | bruno | show |
| Daisy Client API | | Image | daisydocs | daisydocs-2_0 | en | bruno | show |
| Daisy Client API | | Image | daisydocs | daisydocs-2_1 | en | bruno | show |
| Daisy Client API | | Image | daisydocs | daisydocs-2_2 | en | bruno | show |
| Daisy Client API | | Image | daisydocs | daisydocs-2_3 | en | bruno | show |
| Daisy Community Wiki Home | Welcome to the Daisy community wiki. This is a place where everyone (yes, that includes you) can edit and contribute. To get edit access to this area, simply register and send a simple mail to the Daisy mailing list requesting editing access (include your Daisy login in the message). We will th... | DaisyCommWikiDocument | daisywiki | main | en | bruno | show |
| Daisy Database Schema | | Image | daisydocs | daisydocs-1_2 | en | bruno | show |
| Daisy Database Schema | | Image | daisydocs | daisydocs-1_3 | en | bruno | show |
| Daisy Database Schema | | Image | daisydocs | daisydocs-1_4 | en | bruno | show |
| Daisy Database Schema | | Image | daisydocs | daisydocs-1_5 | en | bruno | show |
| Daisy Database Schema | | Image | daisydocs | daisydocs-2_0 | en | bruno | show |
| Daisy Database Schema | | Image | daisydocs | daisydocs-2_1 | en | bruno | show |
| Daisy Database Schema | | Image | daisydocs | daisydocs-2_2 | en | bruno | show |
| Daisy Database Schema | | Image | daisydocs | daisydocs-2_3 | en | bruno | show |
| Daisy Demo Site | If you want to evaluate or explore daisy CMS without installing it on your own system, there is now a live demo site available at: http://demo.daisycms.org You may login with the following credentials: Administrator role: Username: admin Password: admin User role: Username: user Password: user ... | DaisyCommWikiDocument | daisywiki | main | en | deining | show |
| Daisy Deployment | | Image | daisydocs | daisydocs-1_2 | en | bruno | show |
| Daisy Deployment | | Image | daisydocs | daisydocs-1_3 | en | bruno | show |
| Daisy Deployment | | Image | daisydocs | daisydocs-1_4 | en | bruno | show |
| Daisy Deployment | | Image | daisydocs | daisydocs-1_5 | en | bruno | show |
| Daisy Deployment | | Image | daisydocs | daisydocs-1_5 | de | bruno | show |
| Daisy Deployment | | Image | daisydocs | daisydocs-2_0 | en | bruno | show |
| Daisy Deployment | | Image | daisydocs | daisydocs-2_0 | de | bruno | show |
| Daisy Deployment | | Image | daisydocs | daisydocs-2_1 | en | bruno | show |
| Daisy Deployment | | Image | daisydocs | daisydocs-2_1 | de | bruno | show |
| Daisy Deployment | | Image | daisydocs | daisydocs-2_2 | en | bruno | show |
| Daisy Deployment | | Image | daisydocs | daisydocs-2_2 | de | bruno | show |
| Daisy Deployment | | Image | daisydocs | daisydocs-2_3 | en | bruno | show |
| Daisy Detachment | Class diagrams Getting a detachment from the repository This shows the process of downloading a detachment from the repository. The actual task of conecting occurs in the constructor of DetachmentRepositoryTalker. Once the DetachmentManager has a Document from the repository, it creates a Det... | DaisyCommWikiDocument | daisywiki | main | en | tim | show |
| Daisy Docs Book | | BookDefinition | daisydocs | daisydocs-1_4 | en | bruno | show |
| Daisy Docs Book | | BookDefinition | daisydocs | daisydocs-1_5 | en | bruno | show |
| Daisy Docs Book | | BookDefinition | daisydocs | daisydocs-2_0 | en | bruno | show |
| Daisy Docs Book | | BookDefinition | daisydocs | daisydocs-2_1 | en | bruno | show |
| Daisy Docs Book | | BookDefinition | daisydocs | daisydocs-2_2 | en | bruno | show |
| Daisy Docs Book | | BookDefinition | daisydocs | daisydocs-2_3 | en | bruno | show |
| Daisy Docs Navigation | | Navigation | daisydocs | daisydocs-1_2 | en | bruno | show |
| Daisy Docs Navigation | | Navigation | | daisydocs-1_3 | en | bruno | show |
| Daisy Docs Navigation | | Navigation | | daisydocs-1_4 | en | bruno | show |
| Daisy Docs Navigation | | Navigation | daisydocs | daisydocs-1_5 | en | bruno | show |
| Daisy Docs Navigation | | Navigation | daisydocs | daisydocs-1_5 | de | bruno | show |
| Daisy Docs Navigation | | Navigation | daisydocs | daisydocs-2_0 | en | bruno | show |
| Daisy Docs Navigation | | Navigation | daisydocs | daisydocs-2_0 | de | bruno | show |
| Daisy Docs Navigation | | Navigation | daisydocs | daisydocs-2_1 | en | bruno | show |
| Daisy Docs Navigation | | Navigation | daisydocs | daisydocs-2_1 | de | bruno | show |
| Daisy Docs Navigation | | Navigation | daisydocs | daisydocs-2_2 | en | bruno | show |
| Daisy Docs Navigation | | Navigation | daisydocs | daisydocs-2_2 | de | bruno | show |
| Daisy Docs Navigation | | Navigation | daisydocs | daisydocs-2_3 | en | bruno | show |
| Daisy Enterprise | This is just a quick Moleskine-style scribble page to start thinking about various "enterprise" features. Daisy for ASPs ASP = Application Service Provider. I'm an ISP and I want to offer self-managed Wikis or websites to my customers, using Daisy. I want to run several Daisies on a single mach... | DaisyCommWikiDocument | daisywiki | main | en | stevenn | show |
| Daisy features overview | Introduction A content management system (CMS), as the name implies, is concerned with managing content (information). This includes things like basic storage and retrieval, authoring, browsing and searching content, versioning, access control, workflow and publishing. Daisy makes content manage... | SimpleDocument | daisy | main | en | bruno | show |
| Daisy Google Goodies | create a Google Sitemap extension | DaisyCommWikiDocument | daisywiki | main | en | bruno | show |
| Daisy Implementation Intro | This section of the documentation is intended to guide you on your first trip through the deep and inner workings of Daisy. It is intended to show how it all fits together, which might not always be obvious by looking at individual source files. This information is intended for people who want t... | SimpleDocument | daisydocs | daisydocs-1_2 | en | bruno | show |
| Daisy Implementation Intro | This section of the documentation is intended to guide you on your first trip through the deep and inner workings of Daisy. It is intended to show how it all fits together, which might not always be obvious by looking at individual source files. This information is intended for people who want t... | SimpleDocument | daisydocs | daisydocs-1_3 | en | bruno | show |
| Daisy Implementation Intro | This section of the documentation is intended to guide you on your first trip through the deep and inner workings of Daisy. It is intended to show how it all fits together, which might not always be obvious by looking at individual source files. This information is intended for people who want t... | SimpleDocument | daisydocs | daisydocs-1_4 | en | bruno | show |
| Daisy Implementation Intro | This section of the documentation is intended to guide you on your first trip through the deep and inner workings of Daisy. It is intended to show how it all fits together, which might not always be obvious by looking at individual source files. This information is intended for people who want t... | SimpleDocument | daisydocs | daisydocs-1_5 | en | bruno | show |
| Daisy Implementation Intro | This section of the documentation is intended to guide you on your first trip through the deep and inner workings of Daisy. It is intended to show how it all fits together, which might not always be obvious by looking at individual source files. This information is intended for people who want t... | SimpleDocument | daisydocs | daisydocs-2_0 | en | bruno | show |
| Daisy Implementation Module View | | Image | daisydocs | daisydocs-1_2 | en | bruno | show |
| Daisy Implementation Module View | | Image | daisydocs | daisydocs-1_3 | en | bruno | show |
| Daisy Implementation Module View | | Image | daisydocs | daisydocs-1_4 | en | bruno | show |
| Daisy Implementation Module View | | Image | daisydocs | daisydocs-1_5 | en | bruno | show |
| Daisy Implementation Module View | | Image | daisydocs | daisydocs-2_0 | en | bruno | show |
| Daisy Implementation Module View | | Image | daisydocs | daisydocs-2_1 | en | bruno | show |
| Daisy Implementation Module View | | Image | daisydocs | daisydocs-2_2 | en | bruno | show |
| Daisy Implementation Module View | | Image | daisydocs | daisydocs-2_3 | en | bruno | show |
| Daisy import/export | | Image | daisydocs | daisydocs-2_0 | en | bruno | show |
| Daisy import/export | | Image | daisydocs | daisydocs-2_1 | en | bruno | show |
| Daisy import/export | | Image | daisydocs | daisydocs-2_2 | en | bruno | show |
| Daisy import/export | | Image | daisydocs | daisydocs-2_3 | en | bruno | show |
| Daisy Import/Export | | Image | daisydocs | daisydocs-2_0 | de | bruno | show |
| Daisy Import/Export | | Image | daisydocs | daisydocs-2_1 | de | bruno | show |
| Daisy Import/Export | | Image | daisydocs | daisydocs-2_2 | de | bruno | show |
| Daisy installed on OS X, the repository server crashes when uploading an image? | When uploading an image on OS X 10.4.6 (Java build 1.5.0_06-112), the repository server exits with the following message: 2006-06-22 12:34:41.016 java[18896] CFLog (0): CFMessagePort: bootstrap_register(): failed 1100 (0x44c), port = 0x45703, name = 'Processes-2.18896' See /usr/include/servers/b... | FAQ | daisydocs | daisydocs-1_5 | en | bruno | show |
| Daisy installed on OS X, the repository server crashes when uploading an image? | When uploading an image on OS X 10.4.6 (Java build 1.5.0_06-112), the repository server exits with the following message: 2006-06-22 12:34:41.016 java[18896] CFLog (0): CFMessagePort: bootstrap_register(): failed 1100 (0x44c), port = 0x45703, name = 'Processes-2.18896' See /usr/include/servers/b... | FAQ | daisydocs | daisydocs-2_0 | en | bruno | show |
| Daisy installed on OS X, the repository server crashes when uploading an image? | When uploading an image on OS X 10.4.6 (Java build 1.5.0_06-112), the repository server exits with the following message: 2006-06-22 12:34:41.016 java[18896] CFLog (0): CFMessagePort: bootstrap_register(): failed 1100 (0x44c), port = 0x45703, name = 'Processes-2.18896' See /usr/include/servers/b... | KnowledgeBaseArticle | daisykb | main | en | bruno | show |
| Daisy Java Adapter | This documentation refers to an alpha version of the Daisy Java Adapter. This means that any interfaces or contracts can change without a preceding deprecation period. The Daisy Java Adapter requires a Daisy 1.5.1 repository. It won't work with any higher or lower version. The main goal of the D... | DaisyCommWikiDocument | daisywiki | main | en | reinhard | show |
| Daisy Knowledgebase Home | What is this? Daisy has a lot of documentation: 250+ dense pages in book form, however a lot of that material is reference documentation for Daisy implementors. Through a collection of bite-sized articles, this knowledge base aims to be a reading guide for that reference documentation. The knowl... | SimpleDocument | daisykb | main | en | bruno | show |
| Daisy Knowledge Base Navigation | | Navigation | daisykb | main | en | bruno | show |
| Daisy License | Daisy is licensed under the Apache License, Version 2.0 and is Copyright 2004 by Outerthought bvba and Schaubroeck nv. Apache License Version 2.0, January 2004 http://www.apache.org/licenses/ TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION 1. Definitions. "License" shall mean the t... | SimpleDocument | daisy | main | en | bruno | show |
| Daisy logo | | Image | daisydocs | daisydocs-1_4 | en | bruno | show |
| Daisy logo | | Image | daisydocs | daisydocs-1_5 | en | bruno | show |
| Daisy logo | | Image | daisydocs | daisydocs-2_0 | en | bruno | show |
| Daisy logo | | Image | daisydocs | daisydocs-2_1 | en | bruno | show |
| Daisy logo | | Image | daisydocs | daisydocs-2_2 | en | bruno | show |
| Daisy logo | | Image | daisydocs | daisydocs-2_3 | en | bruno | show |
| Daisy Maven Plugin | This documentation refers to an alpha version of the Daisy Java Adapter. This means that any interfaces or contracts can change without a preceding deprecation period. The Daisy Maven Plugin requires a Daisy 1.5.1 repository. It won't work with any higher or lower version. The Daisy Maven Plugin... | DaisyCommWikiDocument | daisywiki | main | en | reinhard | show |
| Daisy Namensräume | | Image | daisydocs | daisydocs-2_0 | de | bruno | show |
| Daisy Namensräume | | Image | daisydocs | daisydocs-2_1 | de | bruno | show |
| Daisy Namensräume | | Image | daisydocs | daisydocs-2_2 | de | bruno | show |
| Daisy namespaces | | Image | daisydocs | daisydocs-2_0 | en | bruno | show |
| Daisy namespaces | | Image | daisydocs | daisydocs-2_1 | en | bruno | show |
| Daisy namespaces | | Image | daisydocs | daisydocs-2_2 | en | bruno | show |
| Daisy namespaces | | Image | daisydocs | daisydocs-2_3 | en | bruno | show |
| Daisy presentation to the Java Users Group in Melbourne, Australia | Interested in one person's perspective on Daisy ... or need to borrow some raw materials for your own presentation ? http://geekscape.org/daisy/geekscape/g2/159.html -- Andy: 2005-12-06 | DaisyCommWikiDocument | daisywiki | main | en | geekscape | show |
| daisy-process-meta.xml reference | Overview The daisy-process-meta.xml contains the Daisy process metadata. This file is entirely optional, but will often be required to make meaningful usage of a workflow process in Daisy. See process authoring overview for a general discussion on the role of the process metadata, this section o... | SimpleDocument | daisydocs | daisydocs-2_0 | en | bruno | show |
| daisy-process-meta.xml reference | Overview The daisy-process-meta.xml contains the Daisy process metadata. This file is entirely optional, but will often be required to make meaningful usage of a workflow process in Daisy. See process authoring overview for a general discussion on the role of the process metadata, this section o... | SimpleDocument | daisydocs | daisydocs-2_1 | en | bruno | show |
| daisy-process-meta.xml reference | Overview The daisy-process-meta.xml contains the Daisy process metadata. This file is entirely optional, but will often be required to make meaningful usage of a workflow process in Daisy. See process authoring overview for a general discussion on the role of the process metadata, this section o... | SimpleDocument | daisydocs | daisydocs-2_2 | en | bruno | show |
| daisy-process-meta.xml reference | Overview The daisy-process-meta.xml contains the Daisy process metadata. This file is entirely optional, but will often be required to make meaningful usage of a workflow process in Daisy. See process authoring overview for a general discussion on the role of the process metadata, this section o... | SimpleDocument | daisydocs | daisydocs-2_3 | en | bruno | show |
| Daisy publishing setup scenarios | Below a number of publishing/usage scenarios for Daisy are mentioned, and how each of them can scale to larger usage loads. Note that these are theoretical options, currently not implemented. At the time of this writing, there is only the Daisy Wiki (without caching). Daisy Wiki scalability op... | DaisyCommWikiDocument | daisywiki | main | en | bruno | show |
| Daisy Repository PHP framework | Preliminary report Obtaining the code The code of the framework could be obtained from SVN using the following URL: http://svn.cocoondev.org/repos/daisy/contrib/gsoc2006/kostiantyn/DaisyLib/ You should use the latest version of PHP5. Particularly you should use a version that already supports t... | DaisyCommWikiDocument | daisywiki | main | en | sokol8 | show |
| Daisy Runtime | What is it? The Daisy Runtime is the platform upon which the repository server runs. Basically, it consists of a set of isolated Spring bean containers, with some infrastructure for setting up classloaders and for sharing services between the Spring containers. It's really just a thin layer arou... | SimpleDocument | daisydocs | daisydocs-2_1 | en | bruno | show |
| Daisy Runtime | What is it? The Daisy Runtime is the platform upon which the repository server runs. Basically, it consists of a set of isolated Spring bean containers, with some infrastructure for setting up classloaders and for sharing services between the Spring containers. It's really just a thin layer arou... | SimpleDocument | daisydocs | daisydocs-2_2 | en | bruno | show |
| Daisy Runtime | What is it? The Daisy Runtime is the platform upon which the repository server runs. Basically, it consists of a set of isolated Spring bean containers, with some infrastructure for setting up classloaders and for sharing services between the Spring containers. It's really just a thin layer arou... | SimpleDocument | daisydocs | daisydocs-2_3 | en | bruno | show |
| Daisy Seminar 2005-04-21 | | Attachment | daisy | main | en | stevenn | show |
| daisyskin | | Image | daisydocs | daisydocs-1_5 | en | bruno | show |
| daisyskin | | Image | daisydocs | daisydocs-2_0 | en | bruno | show |
| daisyskin | | Image | daisydocs | daisydocs-2_1 | en | bruno | show |
| daisyskin | | Image | daisydocs | daisydocs-2_2 | en | bruno | show |
| daisyskin | | Image | daisydocs | daisydocs-2_3 | en | bruno | show |
| Daisy Skinning | | Image | daisydocs | daisydocs-1_5 | de | bruno | show |
| Daisy Skinning | | Image | daisydocs | daisydocs-2_0 | de | bruno | show |
| Daisy Skinning | | Image | daisydocs | daisydocs-2_1 | de | bruno | show |
| Daisy Skinning | | Image | daisydocs | daisydocs-2_2 | de | bruno | show |
| Daisyskin source reference | Introduction The daisyskin source is a Cocoon (Excalibur/Avalon) source. Sources in Cocoon are additional schemes you can use in URLs, for the daisyskin source this means you can use URLs of the form "daisyskin:something". Compared to normal file URLs, the daisyskin source has "fallback" behavio... | SimpleDocument | daisydocs | daisydocs-1_3 | en | bruno | show |
| Daisyskin source reference | Introduction The daisyskin source is a Cocoon (Excalibur/Avalon) source. Sources in Cocoon are additional schemes you can use in URLs, for the daisyskin source this means you can use URLs of the form "daisyskin:something". Compared to normal file URLs, the daisyskin source has "fallback" behavio... | SimpleDocument | daisydocs | daisydocs-1_4 | en | bruno | show |
| DaisyUser class | | Image | daisywiki | main | en | sokol8 | show |
| daisy-util.js API reference | To make the Daisy Wiki context and functionality easily available from flowscript (javascript), a small integration library called daisy-util.js is available. Importing To use it, add the following on top of the javascript file: cocoon.load("resource://org/outerj/daisy/frontend/util/daisy-util.j... | SimpleDocument | daisydocs | daisydocs-1_3 | en | bruno | show |
| daisy-util.js API reference | To make the Daisy Wiki context and functionality easily available from flowscript (javascript), a small integration library called daisy-util.js is available. Importing To use it, add the following on top of the javascript file: cocoon.load("resource://org/outerj/daisy/frontend/util/daisy-util.j... | SimpleDocument | daisydocs | daisydocs-1_4 | en | bruno | show |
| daisy-util.js API reference | To make the Daisy Wiki context and functionality easily available from flowscript (javascript), a small integration library called daisy-util.js is available. Importing To use it, add the following on top of the javascript file: cocoon.load("resource://org/outerj/daisy/frontend/util/daisy-util.j... | SimpleDocument | daisydocs | daisydocs-1_5 | en | bruno | show |
| daisy-util.js API reference | To make the Daisy Wiki context and functionality easily available from flowscript (javascript), a small integration library called daisy-util.js is available. Importing To use it, add the following on top of the javascript file: cocoon.load("resource://org/outerj/daisy/frontend/util/daisy-util.j... | SimpleDocument | daisydocs | daisydocs-2_0 | en | bruno | show |
| daisy-util.js API reference | To make the Daisy Wiki context and functionality easily available from flowscript (javascript), a small integration library called daisy-util.js is available. Importing To use it, add the following on top of the javascript file: cocoon.load("resource://org/outerj/daisy/frontend/util/daisy-util.j... | SimpleDocument | daisydocs | daisydocs-2_1 | en | bruno | show |
| daisy-util.js API reference | To make the Daisy Wiki context and functionality easily available from flowscript (javascript), a small integration library called daisy-util.js is available. Importing To use it, add the following on top of the javascript file: cocoon.load("resource://org/outerj/daisy/frontend/util/daisy-util.j... | SimpleDocument | daisydocs | daisydocs-2_2 | en | bruno | show |
| daisy-util.js API reference | To make the Daisy Wiki context and functionality easily available from flowscript (javascript), a small integration library called daisy-util.js is available. Importing To use it, add the following on top of the javascript file: cocoon.load("resource://org/outerj/daisy/frontend/util/daisy-util.j... | SimpleDocument | daisydocs | daisydocs-2_3 | en | bruno | show |
| Daisy Wiki | The Daisy Wiki is a generic web-based frontend to the repository server. It provides both publishing and editing/management features. Please see the feature overview page for a comprehensive introduction. | SimpleDocument | daisydocs | daisydocs-2_0 | en | bruno | show |
| Daisy Wiki | The Daisy Wiki is a generic web-based frontend to the repository server. It provides both publishing and editing/management features. Please see the feature overview page for a comprehensive introduction. | SimpleDocument | daisydocs | daisydocs-2_1 | en | bruno | show |
| Daisy Wiki | The Daisy Wiki is a generic web-based frontend to the repository server. It provides both publishing and editing/management features. Please see the feature overview page for a comprehensive introduction. | SimpleDocument | daisydocs | daisydocs-2_2 | en | bruno | show |
| Daisy Wiki | The Daisy Wiki is a generic web-based frontend to the repository server. It provides both publishing and editing/management features. Please see the feature overview page for a comprehensive introduction. | SimpleDocument | daisydocs | daisydocs-2_3 | en | bruno | show |
| Daisy Wiki | | KnowledgeBaseCategory | daisykb | main | en | bruno | show |
| Daisy Wiki - customization and development | | FAQCategory | daisydocs | daisydocs-2_0 | en | bruno | show |
| Daisy Wiki - customization and development | | FAQCategory | daisydocs | daisydocs-2_1 | en | bruno | show |
| Daisy Wiki - customization and development | | FAQCategory | daisydocs | daisydocs-2_2 | en | bruno | show |
| Daisy Wiki - customization and development | | FAQCategory | daisydocs | daisydocs-2_3 | en | bruno | show |
| Daisy Wiki data directory | The Daisy Wiki data directory is where all the configuration and data used by the Wiki is stored. It is unrelated to the repository data directory. The Daisy Wiki data directory contains among other things the configuration for the sites, skins, frontend extensions, and the bookstore where the g... | GlossaryEntry | daisydocs | daisydocs-2_2 | en | bruno | show |
| Daisy Wiki data directory | The Daisy Wiki data directory is where all the configuration and data used by the Wiki is stored. It is unrelated to the repository data directory. The Daisy Wiki data directory contains among other things the configuration for the sites, skins, frontend extensions, and the bookstore where the g... | GlossaryEntry | daisydocs | daisydocs-2_3 | en | bruno | show |
| Daisywiki Document Type Specific Styling | Introduction This document describes how to create custom XSLT stylesheets to render documents differently depending on their document type. The Input XML The input of the stylesheets is an XML document which has a structure as shown below. This is not an extensive schema containing every other ... | SimpleDocument | daisydocs | daisydocs-1_2 | en | bruno | show |
| Daisy Wiki Document Type Specific Styling | Introduction This document describes how to create custom XSLT stylesheets to render documents differently depending on their document type. The Input XML The input of the stylesheets is an XML document which has a structure as shown below. This is not an extensive schema containing every other ... | SimpleDocument | daisydocs | daisydocs-1_3 | en | bruno | show |
| Daisy Wiki Document Type Specific Styling | Introduction This document describes how to create custom XSLT stylesheets to render documents differently depending on their document type. The Input XML The input of the stylesheets is an XML document which has a structure as shown below. This is not an extensive schema containing every other ... | SimpleDocument | daisydocs | daisydocs-1_4 | en | bruno | show |
| Daisy Wiki Document Type Specific Styling | Introduction Here we have a look at how to create custom XSLT stylesheets to render documents differently depending on their document type. The Input XML The input of the stylesheets is an XML document which has a structure as shown below. This is not an extensive schema containing every other e... | SimpleDocument | daisydocs | daisydocs-1_5 | en | bruno | show |
| Daisy Wiki Document Type Specific Styling | Introduction Here we have a look at how to create custom XSLT stylesheets to render documents differently depending on their document type. The Input XML The input of the stylesheets is an XML document which has a structure as shown below. This is not an extensive schema containing every other e... | SimpleDocument | daisydocs | daisydocs-2_0 | en | bruno | show |
| Daisywiki Editor Usage Notes | Introduction This document describes the editor used to modify pages stored in the document repository. The editor features wysiwyg editing. Where do I find the editor? The editor can be reached by either editing an existing document or creating a new document. To edit an existing document, use ... | SimpleDocument | daisydocs | daisydocs-1_2 | en | bruno | show |
| Daisy Wiki Editor Usage Notes | Introduction This document describes the editor used to modify pages stored in the document repository. The editor features wysiwyg editing. Where do I find the editor? The editor can be reached by either editing an existing document or creating a new document. To edit an existing document, use ... | SimpleDocument | daisydocs | daisydocs-1_3 | en | bruno | show |
| Daisy Wiki Editor Usage Notes | Introduction This document describes the editor used to modify pages stored in the document repository. The editor features wysiwyg editing. Where do I find the editor? The editor can be reached by either editing an existing document or creating a new document. To edit an existing document, use ... | SimpleDocument | daisydocs | daisydocs-1_4 | en | bruno | show |
| Daisy Wiki Editor Usage Notes | Introduction This document describes the editor used to modify pages stored in the document repository. The editor features wysiwyg editing. Where do I find the editor? The editor can be reached by either editing an existing document or creating a new document. To edit an existing document, use ... | SimpleDocument | daisydocs | daisydocs-1_5 | en | bruno | show |
| Daisy Wiki Editor Usage Notes | Introduction This document describes the editor used to modify pages stored in the document repository. The editor features wysiwyg editing. Where do I find the editor? The editor can be reached by either editing an existing document or creating a new document. To edit an existing document, use ... | SimpleDocument | daisydocs | daisydocs-2_0 | en | bruno | show |
| Daisy Wiki Editor Usage Notes | Introduction This document describes the editor used to modify pages stored in the document repository. The editor features wysiwyg editing. Where do I find the editor? The editor can be reached by either editing an existing document or creating a new document. To edit an existing document, use ... | SimpleDocument | daisydocs | daisydocs-2_1 | en | bruno | show |
| Daisy Wiki Editor Usage Notes | Introduction This document describes the editor used to modify pages stored in the document repository. The editor features wysiwyg editing. Where do I find the editor? The editor can be reached by either editing an existing document or creating a new document. To edit an existing document, use ... | SimpleDocument | daisydocs | daisydocs-2_2 | en | bruno | show |
| Daisy Wiki Editor Usage Notes | Introduction This document describes the editor used to modify pages stored in the document repository. The editor features wysiwyg editing. Where do I find the editor? The editor can be reached by either editing an existing document or creating a new document. To edit an existing document, use ... | SimpleDocument | daisydocs | daisydocs-2_3 | en | bruno | show |
| Daisy Wiki Extensions | Introduction This document explains how the Daisy Wiki can be extended with custom functionality. It assumes some knowledge of Cocoon concepts such as the sitemap. The Daisy Wiki makes it possible to add your own functionality on a per-site level, in the form of a site-specific sitemap that get... | SimpleDocument | daisydocs | daisydocs-1_2 | en | bruno | show |
| Daisy Wiki Extensions | All information about extensions provided on this and subsequent pages applies to Daisy releases after (not including) 1.3-M2. See the Daisy 1.2 docs for extensions in earlier releases. Introduction The Daisy Wiki has some hooks to add your own functionality. You build extensions by building on ... | SimpleDocument | daisydocs | daisydocs-1_3 | en | bruno | show |
| Daisy Wiki Extensions | Introduction The Daisy Wiki has some hooks to add your own functionality. You build extensions by building on top of Cocoon and making use of the available Daisy repository API (plus extension components such as the navigation manager and the publisher). To develop extensions, you don't need a J... | SimpleDocument | daisydocs | daisydocs-1_4 | en | bruno | show |
| Daisy Wiki Extensions | Introduction The Daisy Wiki has some hooks to add your own functionality. You build extensions by building on top of Cocoon and making use of the available Daisy repository API (plus extension components such as the navigation manager and the publisher). To develop extensions, you don't need a J... | SimpleDocument | daisydocs | daisydocs-1_5 | en | bruno | show |
| Daisy Wiki Extensions | Introduction The Daisy Wiki has some hooks to add your own functionality. You build extensions by building on top of Cocoon and making use of the available Daisy repository API (plus extension components such as the navigation manager and the publisher). To develop extensions, you don't need a J... | SimpleDocument | daisydocs | daisydocs-2_0 | en | bruno | show |
| Daisy Wiki Extensions | Introduction The Daisy Wiki has some hooks to add your own functionality. You build extensions by building on top of Cocoon and making use of the available Daisy repository API (plus extension components such as the navigation manager and the publisher). To develop extensions, you don't need a J... | SimpleDocument | daisydocs | daisydocs-2_1 | en | bruno | show |
| Daisy Wiki Extensions | Introduction The Daisy Wiki has some hooks to add your own functionality. You build extensions by building on top of Cocoon and making use of the available Daisy repository API (plus extension components such as the navigation manager and the publisher). To develop extensions, you don't need a J... | SimpleDocument | daisydocs | daisydocs-2_2 | en | bruno | show |
| Daisy Wiki Extensions | Introduction The Daisy Wiki has some hooks to add your own functionality. You build extensions by building on top of Cocoon and making use of the available Daisy repository API (plus extension components such as the navigation manager and the publisher). To develop extensions, you don't need a J... | SimpleDocument | daisydocs | daisydocs-2_3 | en | bruno | show |
| Daisy Wiki extension sample: guestbook | This sample illustrates using a form to collect data (based on Cocoon's form framework, CForms) and creating a document in the repository using the collected data. The theme of the sample is a "guestbook", though we don't want to publicise this as the correct way of building a guestbook. This sa... | SimpleDocument | daisydocs | daisydocs-1_3 | en | bruno | show |
| Daisy Wiki extension sample: guestbook | This sample illustrates using a form to collect data (based on Cocoon's form framework, CForms) and creating a document in the repository using the collected data. The theme of the sample is a "guestbook", though we don't want to publicise this as the correct way of building a guestbook. This sa... | SimpleDocument | daisydocs | daisydocs-1_4 | en | bruno | show |
| Daisy Wiki extension sample: guestbook | This sample illustrates using a form to collect data (based on Cocoon's form framework, CForms) and creating a document in the repository using the collected data. The theme of the sample is a "guestbook", though we don't want to publicise this as the correct way of building a guestbook. This sa... | SimpleDocument | daisydocs | daisydocs-1_5 | en | bruno | show |
| Daisy Wiki extension sample: guestbook | This sample illustrates using a form to collect data (based on Cocoon's form framework, CForms) and creating a document in the repository using the collected data. The theme of the sample is a "guestbook", though we don't want to publicise this as the correct way of building a guestbook. This sa... | SimpleDocument | daisydocs | daisydocs-2_0 | en | bruno | show |
| Daisy Wiki extension sample: guestbook | This sample illustrates using a form to collect data (based on Cocoon's form framework, CForms) and creating a document in the repository using the collected data. The theme of the sample is a "guestbook", though we don't want to publicise this as the correct way of building a guestbook. This sa... | SimpleDocument | daisydocs | daisydocs-2_1 | en | bruno | show |
| Daisy Wiki extension sample: guestbook | This sample illustrates using a form to collect data (based on Cocoon's form framework, CForms) and creating a document in the repository using the collected data. The theme of the sample is a "guestbook", though we don't want to publicise this as the correct way of building a guestbook. This sa... | SimpleDocument | daisydocs | daisydocs-2_2 | en | bruno | show |
| Daisy Wiki extension sample: guestbook | This sample illustrates using a form to collect data (based on Cocoon's form framework, CForms) and creating a document in the repository using the collected data. The theme of the sample is a "guestbook", though we don't want to publicise this as the correct way of building a guestbook. This sa... | SimpleDocument | daisydocs | daisydocs-2_3 | en | bruno | show |
| Daisy Wiki extension sample: navigation aggregation | This example creates a page composed of all documents occuring in a navigation tree, in the order in which they occur in the navigation tree. It is also possible to limit the result to a certain subsection of the navigation tree. To use, call an URL like: http://localhost:8888/daisy/<sitename>/e... | SimpleDocument | daisydocs | daisydocs-1_3 | en | bruno | show |
| Daisy Wiki extension sample: navigation aggregation | This example creates a page composed of all documents occuring in a navigation tree, in the order in which they occur in the navigation tree. It is also possible to limit the result to a certain subsection of the navigation tree. To use, call an URL like: http://localhost:8888/daisy/<sitename>/e... | SimpleDocument | daisydocs | daisydocs-1_4 | en | bruno | show |
| Daisy Wiki extension sample: navigation aggregation | This example creates a page composed of all documents occurring in a navigation tree, in the order in which they occur in the navigation tree. It is also possible to limit the result to a certain subsection of the navigation tree. To use, call an URL like: http://localhost:8888/daisy/<sitename>/... | SimpleDocument | daisydocs | daisydocs-1_5 | en | bruno | show |
| Daisy Wiki extension sample: navigation aggregation | This example creates a page composed of all documents occurring in a navigation tree, in the order in which they occur in the navigation tree. It is also possible to limit the result to a certain subsection of the navigation tree. To use, call an URL like: http://localhost:8888/daisy/<sitename>/... | SimpleDocument | daisydocs | daisydocs-2_0 | en | bruno | show |
| Daisy Wiki extension sample: navigation aggregation | This example creates a page composed of all documents occurring in a navigation tree, in the order in which they occur in the navigation tree. It is also possible to limit the result to a certain subsection of the navigation tree. To use, call an URL like: http://localhost:8888/daisy/<sitename>/... | SimpleDocument | daisydocs | daisydocs-2_1 | en | bruno | show |
| Daisy Wiki extension sample: navigation aggregation | This example creates a page composed of all documents occurring in a navigation tree, in the order in which they occur in the navigation tree. It is also possible to limit the result to a certain subsection of the navigation tree. To use, call an URL like: http://localhost:8888/daisy/<sitename>/... | SimpleDocument | daisydocs | daisydocs-2_2 | en | bruno | show |
| Daisy Wiki extension sample: navigation aggregation | This example creates a page composed of all documents occurring in a navigation tree, in the order in which they occur in the navigation tree. It is also possible to limit the result to a certain subsection of the navigation tree. To use, call an URL like: http://localhost:8888/daisy/<sitename>/... | SimpleDocument | daisydocs | daisydocs-2_3 | en | bruno | show |
| Daisy Wiki extension sample: publish document | This sample shows how to publish just one document. To use, just surf to an URL like: http://localhost:8888/daisy/<sitename>/ext/publishdoc/<documentId> in which you need to replace <sitename> with the name of your site and <documentId> with the ID of a document. This simple example can be usef... | SimpleDocument | daisydocs | daisydocs-1_3 | en | bruno | show |
| Daisy Wiki extension sample: publish document | This sample shows how to publish just one document. To use, just surf to an URL like: http://localhost:8888/daisy/<sitename>/ext/publishdoc/<documentId> in which you need to replace <sitename> with the name of your site and <documentId> with the ID of a document. This simple example can be usef... | SimpleDocument | daisydocs | daisydocs-1_4 | en | bruno | show |
| Daisy Wiki extension sample: publish document | This sample shows how to publish just one document. To use, just surf to an URL like: http://localhost:8888/daisy/<sitename>/ext/publishdoc/<documentId> in which you need to replace <sitename> with the name of your site and <documentId> with the ID of a document. This simple example can be usef... | SimpleDocument | daisydocs | daisydocs-1_5 | en | bruno | show |
| Daisy Wiki extension sample: publish document | This sample shows how to publish just one document. To use, just surf to an URL like: http://localhost:8888/daisy/<sitename>/ext/publishdoc/<documentId> in which you need to replace <sitename> with the name of your site and <documentId> with the ID of a document. This simple example can be usef... | SimpleDocument | daisydocs | daisydocs-2_0 | en | bruno | show |
| Daisy Wiki extension sample: publish document | This sample shows how to publish just one document. To use, just surf to an URL like: http://localhost:8888/daisy/<sitename>/ext/publishdoc/<documentId> in which you need to replace <sitename> with the name of your site and <documentId> with the ID of a document. This simple example can be usef... | SimpleDocument | daisydocs | daisydocs-2_1 | en | bruno | show |
| Daisy Wiki extension sample: publish document | This sample shows how to publish just one document. To use, just surf to an URL like: http://localhost:8888/daisy/<sitename>/ext/publishdoc/<documentId> in which you need to replace <sitename> with the name of your site and <documentId> with the ID of a document. This simple example can be usef... | SimpleDocument | daisydocs | daisydocs-2_2 | en | bruno | show |
| Daisy Wiki extension sample: publish document | This sample shows how to publish just one document. To use, just surf to an URL like: http://localhost:8888/daisy/<sitename>/ext/publishdoc/<documentId> in which you need to replace <sitename> with the name of your site and <documentId> with the ID of a document. This simple example can be usef... | SimpleDocument | daisydocs | daisydocs-2_3 | en | bruno | show |
| Daisy Wiki extension sample: RSS include | This sample shows you how to include a live import of an Atom/RSS feed into a document. Quite often, such feeds include escaped HTML (i.e. with < and > encoded as < and >), so we need some way to reparse that HTML into proper XML which can be passed through the Daisy publishing pipelines. ... | SimpleDocument | daisydocs | daisydocs-1_3 | en | stevenn | show |
| Daisy Wiki extension sample: RSS include | This sample shows you how to include a live import of an Atom/RSS feed into a document. Quite often, such feeds include escaped HTML (i.e. with < and > encoded as < and >), so we need some way to reparse that HTML into proper XML which can be passed through the Daisy publishing pipelines. ... | SimpleDocument | daisydocs | daisydocs-1_4 | en | stevenn | show |
| Daisy Wiki extension sample: RSS include | This sample shows you how to include a live import of an Atom/RSS feed into a document. Quite often, such feeds include escaped HTML (i.e. with < and > encoded as < and >), so we need some way to reparse that HTML into proper XML which can be passed through the Daisy publishing pipelines. ... | SimpleDocument | daisydocs | daisydocs-1_5 | en | stevenn | show |
| Daisy Wiki extension sample: RSS include | This sample shows you how to include a live import of an Atom/RSS feed into a document. Quite often, such feeds include escaped HTML (i.e. with < and > encoded as < and >), so we need some way to reparse that HTML into proper XML which can be passed through the Daisy publishing pipelines. ... | SimpleDocument | daisydocs | daisydocs-2_0 | en | stevenn | show |
| Daisy Wiki extension sample: RSS include | This sample shows you how to include a live import of an Atom/RSS feed into a document. Quite often, such feeds include escaped HTML (i.e. with < and > encoded as < and >), so we need some way to reparse that HTML into proper XML which can be passed through the Daisy publishing pipelines. ... | SimpleDocument | daisydocs | daisydocs-2_1 | en | stevenn | show |
| Daisy Wiki extension sample: RSS include | This sample shows you how to include a live import of an Atom/RSS feed into a document. Quite often, such feeds include escaped HTML (i.e. with < and > encoded as < and >), so we need some way to reparse that HTML into proper XML which can be passed through the Daisy publishing pipelines. ... | SimpleDocument | daisydocs | daisydocs-2_2 | en | stevenn | show |
| Daisy Wiki extension sample: RSS include | This sample shows you how to include a live import of an Atom/RSS feed into a document. Quite often, such feeds include escaped HTML (i.e. with < and > encoded as < and >), so we need some way to reparse that HTML into proper XML which can be passed through the Daisy publishing pipelines. ... | SimpleDocument | daisydocs | daisydocs-2_3 | en | stevenn | show |
| Daisy Wiki extension sitemap diagram | | Image | daisydocs | daisydocs-1_2 | en | bruno | show |
| Daisy Wiki extension sitemap diagram | | Image | daisydocs | daisydocs-1_3 | en | bruno | show |
| Daisy Wiki extension sitemap diagram | | Image | daisydocs | daisydocs-1_4 | en | bruno | show |
| Daisy Wiki extension sitemap diagram | | Image | daisydocs | daisydocs-1_5 | en | bruno | show |
| Daisy Wiki extension sitemap diagram | | Image | daisydocs | daisydocs-2_0 | en | bruno | show |
| Daisy Wiki extension sitemap diagram | | Image | daisydocs | daisydocs-2_1 | en | bruno | show |
| Daisy Wiki extension sitemap diagram | | Image | daisydocs | daisydocs-2_2 | en | bruno | show |
| Daisy Wiki extension sitemap diagram | | Image | daisydocs | daisydocs-2_3 | en | bruno | show |
| Daisy Wiki - general | | FAQCategory | daisydocs | daisydocs-2_0 | en | bruno | show |
| Daisy Wiki - general | | FAQCategory | daisydocs | daisydocs-2_1 | en | bruno | show |
| Daisy Wiki - general | | FAQCategory | daisydocs | daisydocs-2_2 | en | bruno | show |
| Daisy Wiki - general | | FAQCategory | daisydocs | daisydocs-2_3 | en | bruno | show |
| Daisy Wiki Implementation | The Daisy Wiki is build on top of the Apache Cocoon framework. Cocoon is historically strong in XML-based webpublishing, which is very useful when implementing a CMS frontend. Next to that, Cocoon also gained powerful webapp development support, in the form of innovative flow-control solutions a... | SimpleDocument | daisydocs | daisydocs-1_2 | en | bruno | show |
| Daisy Wiki Implementation | The Daisy Wiki is build on top of the Apache Cocoon framework. Cocoon is historically strong in XML-based webpublishing, which is very useful when implementing a CMS frontend. Next to that, Cocoon also gained powerful webapp development support, in the form of innovative flow-control solutions a... | SimpleDocument | daisydocs | daisydocs-1_3 | en | bruno | show |
| Daisy Wiki Implementation | The Daisy Wiki is build on top of the Apache Cocoon framework. Cocoon is historically strong in XML-based webpublishing, which is very useful when implementing a CMS frontend. Next to that, Cocoon also gained powerful webapp development support, in the form of innovative flow-control solutions a... | SimpleDocument | daisydocs | daisydocs-1_4 | en | bruno | show |
| Daisy Wiki Implementation | The Daisy Wiki is build on top of the Apache Cocoon framework. Cocoon is historically strong in XML-based web publishing, which is very useful when implementing a CMS frontend. Next to that, Cocoon also gained powerful webapp development support, in the form of innovative flow-control solutions ... | SimpleDocument | daisydocs | daisydocs-1_5 | en | bruno | show |
| Daisy Wiki Implementation | The Daisy Wiki is build on top of the Apache Cocoon framework. Cocoon is historically strong in XML-based web publishing, which is very useful when implementing a CMS frontend. Next to that, Cocoon also gained powerful webapp development support, in the form of innovative flow-control solutions ... | SimpleDocument | daisydocs | daisydocs-2_0 | en | bruno | show |
| Daisy Wiki Implementation | The Daisy Wiki is build on top of the Apache Cocoon framework. Cocoon is historically strong in XML-based web publishing, which is very useful when implementing a CMS frontend. Next to that, Cocoon also gained powerful webapp development support, in the form of innovative flow-control solutions ... | SimpleDocument | daisydocs | daisydocs-2_1 | en | bruno | show |
| Daisy Wiki Implementation | The Daisy Wiki is build on top of the Apache Cocoon framework. Cocoon is historically strong in XML-based web publishing, which is very useful when implementing a CMS frontend. Next to that, Cocoon also gained powerful webapp development support, in the form of innovative flow-control solutions ... | SimpleDocument | daisydocs | daisydocs-2_2 | en | bruno | show |
| Daisy Wiki Implementation | The Daisy Wiki is build on top of the Apache Cocoon framework. Cocoon is historically strong in XML-based web publishing, which is very useful when implementing a CMS frontend. Next to that, Cocoon also gained powerful webapp development support, in the form of innovative flow-control solutions ... | SimpleDocument | daisydocs | daisydocs-2_3 | en | bruno | show |
| Daisy Wiki Overview | An overview of the functionality of the Daisy Wiki can be found in the feature overview. | SimpleDocument | daisydocs | daisydocs-1_2 | en | bruno | show |
| Daisy Wiki Overview | An overview of the functionality of the Daisy Wiki can be found in the feature overview. | SimpleDocument | daisydocs | daisydocs-1_3 | en | bruno | show |
| Daisy Wiki Overview | An overview of the functionality of the Daisy Wiki can be found in the feature overview. | SimpleDocument | daisydocs | daisydocs-1_4 | en | bruno | show |
| Daisy Wiki Overview | An overview of the functionality of the Daisy Wiki can be found in the feature overview. | SimpleDocument | daisydocs | daisydocs-1_5 | en | bruno | show |
| Daisywiki PDF Notes | Introduction Daisy generates PDFs by feeding XSL-FO (a vocabulary for specifying formatting semantics) to Apache FOP (and XSL-FO processor). The PDFs are generated on the fly when a user requests them. Images FOP caches images, normally indefinitely. Daisy clears FOPs' image cache from time to t... | SimpleDocument | daisydocs | daisydocs-1_2 | en | bruno | show |
| Daisy Wiki PDF Notes | Introduction Daisy generates PDFs by feeding XSL-FO (a vocabulary for specifying formatting semantics) to Apache FOP (and XSL-FO processor). The PDFs are generated on the fly when a user requests them. Images FOP caches images, normally indefinitely. Daisy clears FOPs' image cache from time to t... | SimpleDocument | daisydocs | daisydocs-1_3 | en | bruno | show |
| Daisy Wiki PDF Notes | Introduction Daisy generates PDFs by feeding XSL-FO (a vocabulary for specifying formatting semantics) to Apache FOP (and XSL-FO processor). The PDFs are generated on the fly when a user requests them. Images FOP caches images, normally indefinitely. Daisy clears FOPs' image cache from time to t... | SimpleDocument | daisydocs | daisydocs-1_4 | en | bruno | show |
| Daisy Wiki PDF Notes | Introduction Daisy generates PDFs by feeding XSL-FO (a vocabulary for specifying formatting semantics) to Apache FOP (and XSL-FO processor). The PDFs are generated on the fly when a user requests them. Images FOP caches images, normally indefinitely. Daisy clears FOPs' image cache from time to t... | SimpleDocument | daisydocs | daisydocs-1_5 | en | bruno | show |
| Daisy Wiki PDF Notes | Introduction Daisy generates PDFs by feeding XSL-FO (a vocabulary for specifying formatting semantics) to Apache FOP (and XSL-FO processor). The PDFs are generated on the fly when a user requests them. Images FOP caches images, normally indefinitely. Daisy clears FOPs' image cache from time to t... | SimpleDocument | daisydocs | daisydocs-2_0 | en | bruno | show |
| Daisy Wiki PDF Notes | Introduction Daisy generates PDFs by feeding XSL-FO (a vocabulary for specifying formatting semantics) to Apache FOP (and XSL-FO processor). The PDFs are generated on the fly when a user requests them. Images FOP caches images, normally indefinitely. Daisy clears FOPs' image cache from time to t... | SimpleDocument | daisydocs | daisydocs-2_1 | en | bruno | show |
| Daisy Wiki PDF Notes | Introduction Daisy generates PDFs by feeding XSL-FO (a vocabulary for specifying formatting semantics) to Apache FOP (and XSL-FO processor). The PDFs are generated on the fly when a user requests them. Images FOP caches images, normally indefinitely. Daisy clears FOPs' image cache from time to t... | SimpleDocument | daisydocs | daisydocs-2_2 | en | bruno | show |
| Daisy Wiki PDF Notes | Introduction Daisy generates PDFs by feeding XSL-FO (a vocabulary for specifying formatting semantics) to Apache FOP (an XSL-FO processor). The PDFs are generated on the fly when a user requests them. Images FOP caches images, normally indefinitely. Daisy clears FOPs' image cache from time to ti... | SimpleDocument | daisydocs | daisydocs-2_3 | en | bruno | show |
| Daisy Wiki Screen List | This is an attempt to create a list of all pages (screens) in the Daisy Wiki. At the time of this writing, it was created after the release of Daisy 1.3-M2, with the purpose of being able to systematically verify correct display after some frontend refactorings. Page Notes Site Index P... | SimpleDocument | daisydocs | daisydocs-1_3 | en | bruno | show |
| Daisy Wiki Screen List | This is an attempt to create a list of all pages (screens) in the Daisy Wiki. At the time of this writing, it was created after the release of Daisy 1.3-M2, with the purpose of being able to systematically verify correct display after some frontend refactorings. Page Notes Site Index P... | SimpleDocument | daisydocs | daisydocs-1_4 | en | bruno | show |
| Daisy Wiki Screen List | This is an attempt to create a list of all pages (screens) in the Daisy Wiki. At the time of this writing, it was created after the release of Daisy 1.3-M2, with the purpose of being able to systematically verify correct display after some frontend refactorings. Page Notes Site Index P... | SimpleDocument | daisydocs | daisydocs-1_5 | en | bruno | show |
| Daisy Wiki Screen List | This is an attempt to create a list of all pages (screens) in the Daisy Wiki. At the time of this writing, it was created after the release of Daisy 1.3-M2, with the purpose of being able to systematically verify correct display after some frontend refactorings. Page Notes Site Index P... | SimpleDocument | daisydocs | daisydocs-2_0 | en | bruno | show |
| Daisy Wiki Screen List | This is an attempt to create a list of all pages (screens) in the Daisy Wiki. At the time of this writing, it was created after the release of Daisy 1.3-M2, with the purpose of being able to systematically verify correct display after some frontend refactorings. Page Notes Site Index P... | SimpleDocument | daisydocs | daisydocs-2_1 | en | bruno | show |
| Daisy Wiki Screen List | This is an attempt to create a list of all pages (screens) in the Daisy Wiki. At the time of this writing, it was created after the release of Daisy 1.3-M2, with the purpose of being able to systematically verify correct display after some frontend refactorings. Page Notes Site Index P... | SimpleDocument | daisydocs | daisydocs-2_2 | en | bruno | show |
| Daisy Wiki Screen List | This is an attempt to create a list of all pages (screens) in the Daisy Wiki. At the time of this writing, it was created after the release of Daisy 1.3-M2, with the purpose of being able to systematically verify correct display after some frontend refactorings. Page Notes Site Index P... | SimpleDocument | daisydocs | daisydocs-2_3 | en | bruno | show |
| Daisy Wiki Sites | What is a Daisy Wiki "site"? A Daisy Wiki site allows to have a specific view on a Daisy Repository. A site is configured with a default collection (the concept of document collections is explained on the documents page). Full text searches and recent changes are automatically limited to only sh... | SimpleDocument | daisydocs | daisydocs-1_2 | en | bruno | show |
| Daisy Wiki Sites | What is a Daisy Wiki "site"? A Daisy Wiki site is a specific view on a Daisy Repository. A site is configured with a default collection (the concept of document collections is explained on the documents page). Full text searches and recent changes are automatically limited to only show documents... | SimpleDocument | daisydocs | daisydocs-1_3 | en | bruno | show |
| Daisy Wiki Sites | What is a Daisy Wiki "site"? A Daisy Wiki site is a specific view on a Daisy Repository. A site is configured with a default collection (the concept of document collections is explained on the documents page). Full text searches and recent changes are automatically limited to only show documents... | SimpleDocument | daisydocs | daisydocs-1_4 | en | bruno | show |
| Daisy Wiki Sites | What is a Daisy Wiki "site"? A Daisy Wiki site is a specific view on a Daisy Repository. A site is configured with a default collection (the concept of document collections is explained on the documents page). Full text searches and recent changes are automatically limited to only show documents... | SimpleDocument | daisydocs | daisydocs-1_5 | en | bruno | show |
| Daisy Wiki Sites | What is a Daisy Wiki "site"? A Daisy Wiki site is a specific view on a Daisy Repository. A site is configured with a default collection (the concept of document collections is explained on the documents page). Full text searches and recent changes are automatically limited to only show documents... | SimpleDocument | daisydocs | daisydocs-2_0 | en | bruno | show |
| Daisy Wiki Sites | What is a Daisy Wiki "site"? A Daisy Wiki site is a specific view on a Daisy Repository. A site is configured with a default collection (the concept of document collections is explained on the documents page). Full text searches and recent changes are automatically limited to only show documents... | SimpleDocument | daisydocs | daisydocs-2_1 | en | bruno | show |
| Daisy Wiki Sites | What is a Daisy Wiki "site"? A Daisy Wiki site is a specific view on a Daisy Repository. A site is configured with a default collection (the concept of document collections is explained on the documents page). Full text searches and recent changes are automatically limited to only show documents... | SimpleDocument | daisydocs | daisydocs-2_2 | en | bruno | show |
| Daisy Wiki Sites | What is a Daisy Wiki "site"? A Daisy Wiki site is a specific view on a Daisy Repository. A site is configured with a default collection (the concept of document collections is explained on the documents page). Full text searches and recent changes are automatically limited to only show documents... | SimpleDocument | daisydocs | daisydocs-2_3 | en | bruno | show |
| Daisy Wiki Skinning | All Daisy pages are build up by XSLT "stylesheets" (transformations of XML data). Building a custom look for the site could thus be done by creating your own variant of these XSLTs. However, maintaining these and keeping them in sync with new developments and bugfixes happening in Daisy would be... | SimpleDocument | daisydocs | daisydocs-1_2 | en | bruno | show |
| Daisy Wiki Skinning | All information about skinning provided on this and subsequent pages applies to Daisy releases after (not including) 1.3-M2. See the Daisy 1.2 docs for skinning in earlier releases. Customising the look and feel of the Daisy Wiki is possible through: configuration of an existing skin, via the s... | SimpleDocument | daisydocs | daisydocs-1_3 | en | bruno | show |
| Daisy Wiki Skinning | Customising the look and feel of the Daisy Wiki is possible through: configuration of an existing skin, via the skinconf.xml creation of a custom skin Daisy ships with one skin called default. The skin to use is configurable on the level of a site in the siteconf.xml file. Thus different sites... | SimpleDocument | daisydocs | daisydocs-1_4 | en | bruno | show |
| Daisy Wiki Skinning | Customising the look and feel of the Daisy Wiki is possible through: configuration of an existing skin, via the skinconf.xml creation of a custom skin Daisy ships with one skin called default. The skin to use is configurable on the level of a site in the siteconf.xml file. Thus different sites... | SimpleDocument | daisydocs | daisydocs-1_5 | en | bruno | show |
| Daisy Wiki Skinning | Customising the look and feel of the Daisy Wiki is possible through: configuration of an existing skin, via the skinconf.xml creation of a custom skin Daisy ships with one skin called default. The skin to use is configurable on the level of a site in the siteconf.xml file. Thus different sites... | SimpleDocument | daisydocs | daisydocs-2_0 | en | bruno | show |
| Daisy Wiki Skinning | Customising the look and feel of the Daisy Wiki is possible through: configuration of an existing skin, via the skinconf.xml creation of a custom skin Daisy ships with one skin called default. The skin to use is configurable on the level of a site in the siteconf.xml file. Thus different sites... | SimpleDocument | daisydocs | daisydocs-2_1 | en | bruno | show |
| Daisy Wiki Skinning | Customising the look and feel of the Daisy Wiki is possible through: configuration of an existing skin, via the skinconf.xml creation of a custom skin Daisy ships with one skin called default. The skin to use is configurable on the level of a site in the siteconf.xml file. Thus different sites... | SimpleDocument | daisydocs | daisydocs-2_2 | en | bruno | show |
| Daisy Wiki Skinning | Customising the look and feel of the Daisy Wiki is possible through: configuration of an existing skin, via the skinconf.xml creation of a custom skin Daisy ships with one skin called default. The skin to use is configurable on the level of a site in the siteconf.xml file. Thus different sites... | SimpleDocument | daisydocs | daisydocs-2_3 | en | bruno | show |
| Database schema | The image below shows the database schema of the daisy repository. The actual content of parts is stored in files on the hard disk, the blob_id column in the parts table contains the filename (or more correctly, the id used by the BlobStore component to retrieve the data, but this is currently t... | SimpleDocument | daisydocs | daisydocs-1_2 | en | bruno | show |
| Database schema | The image below shows the database schema of the daisy repository. The actual content of parts is stored in files on the hard disk, the blob_id column in the parts table contains the filename (or more correctly, the id used by the BlobStore component to retrieve the data, but this is currently t... | SimpleDocument | daisydocs | daisydocs-1_3 | en | bruno | show |
| Database schema | The image below shows the database schema of the daisy repository. The actual content of parts is stored in files on the hard disk, the blob_id column in the parts table contains the filename (or more correctly, the id used by the BlobStore component to retrieve the data, but this is currently t... | SimpleDocument | daisydocs | daisydocs-1_4 | en | bruno | show |
| Database schema | The image below shows the database schema of the daisy repository. The actual content of parts is stored in files on the hard disk, the blob_id column in the parts table contains the filename (or more correctly, the id used by the BlobStore component to retrieve the data, but this is currently t... | SimpleDocument | daisydocs | daisydocs-1_5 | en | bruno | show |
| Database schema | The image below shows the database schema of the daisy repository. The actual content of parts is stored in files on the hard disk, the blob_id column in the parts table contains the filename (or more correctly, the id used by the BlobStore component to retrieve the data, but this is currently t... | SimpleDocument | daisydocs | daisydocs-2_0 | en | bruno | show |
| Database schema | The image below shows the database schema of the daisy repository. The actual content of parts is stored in files on the hard disk, the blob_id column in the parts table contains the filename (or more correctly, the id used by the BlobStore component to retrieve the data, but this is currently t... | SimpleDocument | daisydocs | daisydocs-2_1 | en | bruno | show |
| Database schema | The image below shows the database schema of the daisy repository. The actual content of parts is stored in files on the hard disk, the blob_id column in the parts table contains the filename (or more correctly, the id used by the BlobStore component to retrieve the data, but this is currently t... | SimpleDocument | daisydocs | daisydocs-2_2 | en | bruno | show |
| Database schema | The image below shows the database schema of the daisy repository. The actual content of parts is stored in files on the hard disk, the blob_id column in the parts table contains the filename (or more correctly, the id used by the BlobStore component to retrieve the data, but this is currently t... | SimpleDocument | daisydocs | daisydocs-2_3 | en | bruno | show |
| data source authorisation | | Image | xreporter | main | en | stevenn | show |
| datasource icon | | Image | xreporter | main | en | mpo | show |
| Data Sources | Concepts A data source in xReporter describes both the connection parameters and some metadata concerning the database such as a name and description. (The word " data source" in xReporter thus covers somewhat more than a Java data source). Multiple data sources can be defined. xReporter can ha... | SimpleDocument | xreporter | main | en | stevenn | show |
| datasource types | | Image | xreporter | main | en | stevenn | show |
| Datatypes | Datatypes play an important role in xReporter. For each parameter that is asked to the user, or for each value that is retrieved from a resultset, a datatype is required. It is possible to create a catalog of datatypes. The datatypes defined in the catalog can then be reused across report defini... | SimpleDocument | xreporter | main | en | stevenn | show |
| ddi-wireframe-main | | Image | daisywiki | main | en | karel | show |
| ddi-wireframe-main | | Image | daisywiki | main | en | karel | show |
| ddi-wireframe-main | | Image | daisywiki | main | en | karel | show |
| default skin | | Image | xreporter | main | en | stevenn | show |
| Deploying on Tomcat | The Daisy webapp can be freely moved out of the DAISY_HOME/daisywiki directory and deployed on another servlet container. It has no external dependencies: it needs no other stuff from DAISY_HOME, nor does it need access to the daisy data directory. Here is how you can deploy Daisy on Tomcat (thi... | SimpleDocument | daisydocs | daisydocs-1_3 | en | bruno | show |
| Deploying on Tomcat | The Daisy webapp can be freely moved out of the DAISY_HOME/daisywiki directory and deployed on another servlet container. It has no external dependencies: it needs no other stuff from DAISY_HOME, nor does it need access to the daisy data directory. Here is how you can deploy Daisy on Tomcat (thi... | SimpleDocument | daisydocs | daisydocs-1_4 | en | bruno | show |
| Deploying on Tomcat | The Daisy webapp can be freely moved out of the DAISY_HOME/daisywiki directory and deployed on another servlet container. It has no dependencies on the other stuff from DAISY_HOME, but it does need access to the daisywiki data directory (not the repository data directory). It does not need acces... | SimpleDocument | daisydocs | daisydocs-1_5 | en | bruno | show |
| Deploying on Tomcat | The Daisy webapp can be freely moved out of the DAISY_HOME/daisywiki directory and deployed on another servlet container. It has no dependencies on the other stuff from DAISY_HOME, but it does need access to the daisywiki data directory (not the repository data directory). It does not need acces... | SimpleDocument | daisydocs | daisydocs-2_0 | en | bruno | show |
| Deploying on Tomcat | The Daisy webapp can be freely moved out of the DAISY_HOME/daisywiki directory and deployed on another servlet container. It has no dependencies on the other stuff from DAISY_HOME, but it does need access to the daisywiki data directory (not the repository data directory). It does not need acces... | SimpleDocument | daisydocs | daisydocs-2_1 | en | bruno | show |
| Deploying on Tomcat | The Daisy webapp can be freely moved out of the DAISY_HOME/daisywiki directory and deployed on another servlet container. It has no dependencies on the other stuff from DAISY_HOME, but it does need access to the daisywiki data directory (not the repository data directory). It does not need acces... | SimpleDocument | daisydocs | daisydocs-2_2 | en | bruno | show |
| Deploying on Tomcat | The Daisy webapp can be freely moved out of the DAISY_HOME/daisywiki directory and deployed on another servlet container. It has no dependencies on the other stuff from DAISY_HOME, but it does need access to the daisywiki data directory (not the repository data directory). It does not need acces... | SimpleDocument | daisydocs | daisydocs-2_3 | en | bruno | show |
| Deploying plugins | As explained earlier, a plugin should be packaged as a container jar. The Daisy Runtime configuration for the repository server will automatically include container jars put in the following directories: <daisy data dir>/plugins/load-before-repository <daisy data dir>/plugins/load-after-reposito... | SimpleDocument | daisydocs | daisydocs-2_1 | en | bruno | show |
| Deploying plugins | As explained earlier, a plugin should be packaged as a container jar. The Daisy Runtime configuration for the repository server will automatically include container jars put in the following directories: <daisy data dir>/plugins/load-before-repository <daisy data dir>/plugins/load-after-reposito... | SimpleDocument | daisydocs | daisydocs-2_2 | en | bruno | show |
| Deploying plugins | As explained earlier, a plugin should be packaged as a container jar. The Daisy Runtime configuration for the repository server will automatically include container jars put in the following directories: <daisy data dir>/plugins/load-before-repository <daisy data dir>/plugins/load-after-reposito... | SimpleDocument | daisydocs | daisydocs-2_3 | en | bruno | show |
| Desktop integration | A lot of useful feedback on this document can be found in this mailing list thread: http://thread.gmane.org/gmane.comp.java.daisy.general/7617 The initial idea was to merge the information of this thread with this document, but it would not be productive to do so. Please view the thread for a ... | DaisyCommWikiDocument | daisywiki | main | en | karel | show |
| Diff Example | a b c aa bb cc aaa bbb ccc aaaa bbbb cccc | SimpleDocument | daisywiki | main | en | guyvdb | show |
| directory layout | | Image | main | main | en | nverwer | show |
| dirlayout | | Image | handbook | main | en | hepabolu | show |
| Display images in a query using query-styling | Objective This article is about displaying a query-based table of images within a daisy installation for the visual selection of pictures. Background Once daisy is accepted by those working with it (in our case a company using it for background info and end-user documentation), a lot of pictures... | DaisyCommWikiDocument | daisywiki | main | en | kevin_walsh | show |
| Displaying Full Size Images | Overview Images embedded into a Daisy Page display full size in editing, but when they are saved, the display as a preview, with a link "Click to enlarge". The default Daisy installation only displays full size images if the width is under a default value (at time of writing this was 650px). ... | DaisyCommWikiDocument | daisywiki | main | en | twells | show |
| DITA Support | Overview Should Daisy support DITA? Why? If so, how? This document describes the basics of the DITA standard for topic-based XML authoring, why the standard is of potential interest to Daisy users, and some possible ways that Daisy might be extended to support use of DITA. This is a discussion d... | DaisyCommWikiDocument | daisywiki | main | en | peterdykstra | show |
| docbrowser-mockup | | Image | daisywiki | main | en | karel | show |
| docbrowser search aspects | | Image | daisywiki | main | en | karel | show |
| Documentation | Introduction Installation and download: Installing xReporter version 1.2 Installing xReporter version 1.2.1 (unreleased) How and when to (re)deploy Datasources Datatypes Report definitions Resource bundles Administration Logging HTTP interface Expression language Customising the presentati... | SimpleDocument | xreporter | main | en | stevenn | show |
| Documentation for each release | Here you find links to the documentation of various Daisy releases. Current release: Daisy 2.2 Future releases: Daisy 2.3 Past releases: Daisy 1.2 Daisy 1.3 Daisy 1.4 Daisy 1.5 Daisy 2.0 Daisy 2.1 | SimpleDocument | daisy | main | en | bruno | show |
| Documentation Home | These pages contain the Daisy 1.3 documentation. The main Daisy site can be found here. In continuous development for the past 6 months, Daisy packs many new features while providing improvements and bugfixes to ensure easier implementation and integration. Most notable new features in this rele... | SimpleDocument | daisydocs | daisydocs-1_3 | en | bruno | show |
| Documentation Home | These pages contain the documentation for Daisy 1.4. The main Daisy site can be found here. The documentation is also available published as a Daisy-book. | SimpleDocument | daisydocs | daisydocs-1_4 | en | bruno | show |
| Documentation Home | These pages contain the Daisy documentation of the Daisy 1.5 release. The main Daisy site can be found here. The documentation is also available published as a Daisy-book. For an end-user introduction to Daisy, have a look at the video tutorials. | SimpleDocument | daisydocs | daisydocs-1_5 | en | bruno | show |
| Documentation Home | These pages contain the documentation of the Daisy 2.0 release. See also: main Daisy site documentation of other releases The documentation is also available published as a Daisy-book. For an end-user introduction to Daisy, have a look at the video tutorials. | SimpleDocument | daisydocs | daisydocs-2_0 | en | bruno | show |
| Documentation Home | These pages contain the documentation of the Daisy 2.1 release. See also: main Daisy site documentation of other releases The documentation is also available published as a Daisy-book. For an end-user introduction to Daisy, have a look at the video tutorials. | SimpleDocument | daisydocs | daisydocs-2_1 | en | bruno | show |
| Documentation Home | These pages contain the documentation of the Daisy 2.2 release - browse the navigation on the left. See also: main Daisy site documentation of other releases The documentation is also available published as a Daisy-book. For an end-user introduction to Daisy, have a look at the video tutor... | SimpleDocument | daisydocs | daisydocs-2_2 | en | bruno | show |
| Documentation Home | These pages contain the documentation of the Daisy 2.3 release - browse the navigation on the left. See also: main Daisy site documentation of other releases The documentation is also available published as a Daisy-book. For an end-user introduction to Daisy, have a look at the video tutor... | SimpleDocument | daisydocs | daisydocs-2_3 | en | bruno | show |
| Document browser | Introduction The document browser is used to let the user search for a document to link to. The document browser is used in various locations: in the HTML editor, in the navigation editor, for link fields, in the workflow interaction screens, ... The document browser can be customized by means ... | SimpleDocument | daisydocs | daisydocs-2_3 | en | freya | show |
| Document Comments | This document is about document comments: comments that can be added to Daisy documents. Comment features The current Daisy comments system is rather simple (text-only comments, no editing after creation, no threading) but nonetheless very useful. Comment visibility Each comment has a certain vi... | SimpleDocument | daisydocs | daisydocs-1_2 | en | bruno | show |
| Document Comments | This document is about document comments: comments that can be added to Daisy documents. More precisely, they are actually added to document variants, thus each document variant has its own comments. Comment features The current Daisy comments system is rather simple (text-only comments, no edit... | SimpleDocument | daisydocs | daisydocs-1_3 | en | bruno | show |
| Document Comments | This section is about document comments: comments that can be added to Daisy documents. More precisely, they are actually added to document variants, thus each variant of a document has its own comments. Comment features The current Daisy comments system is rather simple (text-only comments, no ... | SimpleDocument | daisydocs | daisydocs-1_4 | en | bruno | show |
| Document Comments | This section is about document comments: comments that can be added to Daisy documents. More precisely, they are actually added to document variants, thus each variant of a document has its own comments. Comment features The current Daisy comments system is rather simple (text-only comments, no ... | SimpleDocument | daisydocs | daisydocs-1_5 | en | bruno | show |
| Document Comments | This section is about document comments: comments that can be added to Daisy documents. More precisely, they are actually added to document variants, thus each variant of a document has its own comments. Comment features The current Daisy comments system is rather simple (text-only comments, no ... | SimpleDocument | daisydocs | daisydocs-2_0 | en | bruno | show |
| Document Comments | This section is about document comments: comments that can be added to Daisy documents. More precisely, they are actually added to document variants, thus each variant of a document has its own comments. Comment features The current Daisy comments system is rather simple (text-only comments, no ... | SimpleDocument | daisydocs | daisydocs-2_1 | en | bruno | show |
| Document Comments | This section is about document comments: comments that can be added to Daisy documents. More precisely, they are actually added to document variants, thus each variant of a document has its own comments. Comment features The current Daisy comments system is rather simple (text-only comments, no ... | SimpleDocument | daisydocs | daisydocs-2_2 | en | bruno | show |
| Document Comments | This section is about document comments: comments that can be added to Daisy documents. More precisely, they are actually added to document variants, thus each variant of a document has its own comments. Comment features The current Daisy comments system is rather simple (text-only comments, no ... | SimpleDocument | daisydocs | daisydocs-2_3 | en | bruno | show |
| Document editor initialisation | Introduction Usually users create new documents by choosing a document type on the "New document" page. Sometimes it can be useful to create documents from other places, or to have the editor initialised with certain content (e.g. a field with a value already assigned or so). Here we have a look... | SimpleDocument | daisydocs | daisydocs-1_5 | en | bruno | show |
| Document editor initialisation | Introduction Usually users create new documents by choosing a document type on the "New document" page. Sometimes it can be useful to create documents from other places, or to have the editor initialised with certain content (e.g. a field with a value already assigned or so). Here we have a look... | SimpleDocument | daisydocs | daisydocs-2_0 | en | bruno | show |
| Document editor initialisation | Introduction Usually users create new documents by choosing a document type on the "New document" page. Sometimes it can be useful to create documents from other places, or to have the editor initialised with certain content (e.g. a field with a value already assigned or so). Here we have a look... | SimpleDocument | daisydocs | daisydocs-2_1 | en | bruno | show |
| Document editor initialisation | Introduction Usually users create new documents by choosing a document type on the "New document" page. Sometimes it can be useful to create documents from other places, or to have the editor initialised with certain content (e.g. a field with a value already assigned or so). Here we have a look... | SimpleDocument | daisydocs | daisydocs-2_2 | en | bruno | show |
| Document editor initialisation | Introduction Usually users create new documents by choosing a document type on the "New document" page. Sometimes it can be useful to create documents from other places, or to have the editor initialised with certain content (e.g. a field with a value already assigned or so). Here we have a look... | SimpleDocument | daisydocs | daisydocs-2_3 | en | bruno | show |
| Document information aggregation | Introduction When a document is published in the Wiki, the Wiki will retrieve the document using a publisher request, and style it using a document-type specific stylesheet (or fall back to a default stylesheet). The information available to this stylesheet is basically just the document with it... | SimpleDocument | daisydocs | daisydocs-1_5 | en | bruno | show |
| Document information aggregation | Introduction When a document is published in the Wiki, the Wiki will retrieve the document using a publisher request, and style it using a document-type specific stylesheet (or fall back to a default stylesheet). The information available to this stylesheet is basically just the document with it... | SimpleDocument | daisydocs | daisydocs-2_0 | en | bruno | show |
| Document information aggregation | Introduction When a document is published in the Wiki, the Wiki will retrieve the document using a publisher request, and style it using a document-type specific stylesheet (or fall back to a default stylesheet). The information available to this stylesheet is basically just the document with it... | SimpleDocument | daisydocs | daisydocs-2_1 | en | bruno | show |
| Document information aggregation | Introduction When a document is published in the Wiki, the Wiki will retrieve the document using a publisher request, and style it using a document-type specific stylesheet (or fall back to a default stylesheet). The information available to this stylesheet is basically just the document with it... | SimpleDocument | daisydocs | daisydocs-2_2 | en | bruno | show |
| Document information aggregation | Introduction When a document is published in the Wiki, the Wiki will retrieve the document using a publisher request, and style it using a document-type specific stylesheet (or fall back to a default stylesheet). The information available to this stylesheet is basically just the document with it... | SimpleDocument | daisydocs | daisydocs-2_3 | en | bruno | show |
| Document model changes | What new attributes to introduce in the document model to support translation management? Since this about adding core system attributes, we should carefully consider them before adding, but without being too scared either ;-) on version: a 'synced_with' (in sync with, corresponds to, matc... | DaisyCommWikiDocument | daisywiki | main | en | bruno | show |
| Document Publishing | This document wil describe the process of how a document gets published by Daisy. What follows below are some first rough notes. The publishing process is split between a "Publisher" extension component running in the repository server and the frontend running on Cocoon. The goal of the Publishe... | SimpleDocument | daisydocs | daisydocs-1_2 | en | bruno | show |
| Document Publishing | This document wil describe the process of how a document gets published by Daisy. What follows below are some first rough notes. The publishing process is split between a "Publisher" extension component running in the repository server and the frontend running on Cocoon. The goal of the Publishe... | SimpleDocument | daisydocs | daisydocs-1_3 | en | bruno | show |
| Document Publishing | This document wil describe the process of how a document gets published by Daisy. What follows below are some first rough notes. The publishing process is split between a "Publisher" extension component running in the repository server and the frontend running on Cocoon. The goal of the Publishe... | SimpleDocument | daisydocs | daisydocs-1_4 | en | bruno | show |
| Document Publishing | This document will describe the process of how a document gets published by Daisy. What follows below are some first rough notes. See also the Cocoon GT presentation on this subject. The publishing process is split between a "Publisher" extension component running in the repository server and th... | SimpleDocument | daisydocs | daisydocs-1_5 | en | bruno | show |
| Document publishing internals | Here we will eventually add a complete description of how the process of getting a document published in the Daisy Wiki works behind the curtains. For now, please see the Cocoon GT presentation on this subject. | SimpleDocument | daisydocs | daisydocs-2_0 | en | bruno | show |
| Document publishing internals | Here we will eventually add a complete description of how the process of getting a document published in the Daisy Wiki works behind the curtains. For now, please see the Cocoon GT presentation on this subject. | SimpleDocument | daisydocs | daisydocs-2_1 | en | bruno | show |
| Document publishing internals | Here we will eventually add a complete description of how the process of getting a document published in the Daisy Wiki works behind the curtains. For now, please see the Cocoon GT presentation on this subject. | SimpleDocument | daisydocs | daisydocs-2_2 | en | bruno | show |
| Document publishing internals | Here we will eventually add a complete description of how the process of getting a document published in the Daisy Wiki works behind the curtains. For now, please see the Cocoon GT presentation on this subject. | SimpleDocument | daisydocs | daisydocs-2_3 | en | bruno | show |
| Documents | Introduction The purpose of the Daisy Repository Server is managing documents. This document will describe the structure (or features) of such documents. The diagram below gives an overview of the document structure, this will be further explained in the rest of this document. Document Types, T... | SimpleDocument | daisydocs | daisydocs-1_2 | en | stevenn | show |
| Documents | Introduction The purpose of the Daisy Repository Server is managing documents. This document will describe the structure (or features) of such documents. The diagram below gives an overview of the document structure, this will be further explained in the remainder of this document. Documents & ... | SimpleDocument | daisydocs | daisydocs-1_3 | en | stevenn | show |
| Documents | Introduction The purpose of the Daisy Repository Server is managing documents. This document will describe the structure (or features) of such documents. The diagram below gives an overview of the document structure, this will be further explained in the remainder of this document. Documents & ... | SimpleDocument | daisydocs | daisydocs-1_4 | en | stevenn | show |
| Documents | Introduction The purpose of the Daisy Repository Server is managing documents. This document will describe the structure (or features) of such documents. The diagram below gives an overview of the document structure, this will be further explained in the remainder of this document. Documents & ... | SimpleDocument | daisydocs | daisydocs-1_5 | en | stevenn | show |
| Documents | Introduction The purpose of the Daisy Repository Server is managing documents. The main content of a document is contained in its so-called parts and fields. Parts contain arbitrary binary data (e.g. an XML document, a PDF file, an image). Fields contain simple information of a certain data type... | SimpleDocument | daisydocs | daisydocs-2_0 | en | stevenn | show |
| Documents | Introduction The purpose of the Daisy Repository Server is managing documents. The main content of a document is contained in its so-called parts and fields. Parts contain arbitrary binary data (e.g. an XML document, a PDF file, an image). Fields contain simple information of a certain data type... | SimpleDocument | daisydocs | daisydocs-2_1 | en | stevenn | show |
| Documents | Introduction The purpose of the Daisy Repository Server is managing documents. The main content of a document is contained in its so-called parts and fields. Parts contain arbitrary binary data (e.g. an XML document, a PDF file, an image). Fields contain simple information of a certain data type... | SimpleDocument | daisydocs | daisydocs-2_2 | en | stevenn | show |
| Documents | Introduction The purpose of the Daisy Repository Server is managing documents. The main content of a document is contained in its so-called parts and fields. Parts contain arbitrary binary data (e.g. an XML document, a PDF file, an image). Fields contain simple information of a certain data type... | SimpleDocument | daisydocs | daisydocs-2_3 | en | stevenn | show |
| Documents do not appear in my query in the navigation tree, but they do appear when executing the query through the query search screen. What's wrong? | Navigation trees can be associated with one or more collections. Queries appearing in the navigation tree are then automatically limited to these collections. This feature avoids that you have to add the 'InCollection' condition to every query in the navigation tree. There is no way to disable i... | FAQ | daisydocs | daisydocs-1_5 | en | bruno | show |
| Documents do not appear in my query in the navigation tree, but they do appear when executing the query through the query search screen. What's wrong? | Navigation trees can be associated with one or more collections. Queries appearing in the navigation tree are then automatically limited to these collections. This feature avoids that you have to add the 'InCollection' condition to every query in the navigation tree. There is no way to disable i... | FAQ | daisydocs | daisydocs-2_0 | en | bruno | show |
| Documents do not appear in my query in the navigation tree, but they do appear when executing the query through the query search screen. What's wrong? | Navigation trees can be associated with one or more collections. Queries appearing in the navigation tree are then automatically limited to these collections. This feature avoids that you have to add the 'InCollection' condition to every query in the navigation tree. There is no way to disable i... | KnowledgeBaseArticle | daisykb | main | en | bruno | show |
| Document Structure | | Image | daisydocs | daisydocs-1_2 | en | bruno | show |
| Document Structure | | Image | daisydocs | daisydocs-1_3 | en | bruno | show |
| Document Structure | | Image | daisydocs | daisydocs-1_4 | en | bruno | show |
| Document Structure | | Image | daisydocs | daisydocs-1_5 | en | bruno | show |
| Document Structure | | Image | daisydocs | daisydocs-2_0 | en | bruno | show |
| Document Structure | | Image | daisydocs | daisydocs-2_1 | en | bruno | show |
| Document Structure | | Image | daisydocs | daisydocs-2_2 | en | bruno | show |
| Document Structure | | Image | daisydocs | daisydocs-2_3 | en | bruno | show |
| Document styling | Introduction The Daisy Wiki allows to customize the styling of documents by mean of an XSLT. This custom styling is typically performed depending on the document type. The Input XML The input of the stylesheets is an XML document which has a structure as shown below. This is not an extensive sc... | SimpleDocument | daisydocs | daisydocs-2_1 | en | bruno | show |
| Document styling | Introduction The Daisy Wiki allows to customize the styling of documents by mean of an XSLT. This custom styling is typically performed depending on the document type. The Input XML The input of the stylesheets is an XML document which has a structure as shown below. This is not an extensive sc... | SimpleDocument | daisydocs | daisydocs-2_2 | en | bruno | show |
| Document styling | Introduction The Daisy Wiki allows to customize the styling of documents by mean of an XSLT. This custom styling is typically performed depending on the document type. The Input XML The input of the stylesheets is an XML document which has a structure as shown below. This is not an extensive sc... | SimpleDocument | daisydocs | daisydocs-2_3 | en | bruno | show |
| Document summary | A summary stored as part of the document (thus it is quick to retrieve). The summary contains the first few hundred words from the live version of the document. | GlossaryEntry | daisydocs | daisydocs-2_2 | en | bruno | show |
| Document summary | A summary stored as part of the document (thus it is quick to retrieve). The summary contains the first few hundred words from the live version of the document. | GlossaryEntry | daisydocs | daisydocs-2_3 | en | bruno | show |
| Document Task Manager | The purpose of the Document Task Manager (DTM) is to perform a certain task across a set of documents. The DTM is an optional component running inside the Daisy Repository Server. Some of its features are: Tasks are executed in the background, inside the repository server. Thus the user (a perso... | SimpleDocument | daisydocs | daisydocs-1_3 | en | bruno | show |
| Document Task Manager | The purpose of the Document Task Manager (DTM) is to perform a certain task across a set of documents. The DTM is an optional component running inside the Daisy Repository Server. Some of its features are: Tasks are executed in the background, inside the repository server. Thus the user (a perso... | SimpleDocument | daisydocs | daisydocs-1_4 | en | bruno | show |
| Document Task Manager | The purpose of the Document Task Manager (DTM) is to perform a certain task across a set of documents. The DTM is an optional component running inside the Daisy Repository Server. Some of its features are: Tasks are executed in the background, inside the repository server. Thus the user (a perso... | SimpleDocument | daisydocs | daisydocs-1_5 | en | bruno | show |
| Document Task Manager | The purpose of the Document Task Manager (DTM) is to perform a certain task across a set of documents. The DTM is an optional component running inside the Daisy Repository Server. Some of its features are: Tasks are executed in the background, inside the repository server. Thus the user (a perso... | SimpleDocument | daisydocs | daisydocs-2_0 | en | bruno | show |
| Document Task Manager | The purpose of the Document Task Manager (DTM) is to perform a certain task across a set of documents. The DTM is an optional component running inside the Daisy Repository Server. Some of its features are: Tasks are executed in the background, inside the repository server. Thus the user (a perso... | SimpleDocument | daisydocs | daisydocs-2_1 | en | bruno | show |
| Document Task Manager | The purpose of the Document Task Manager (DTM) is to perform a certain task across a set of documents. The DTM is an optional component running inside the Daisy Repository Server. Some of its features are: Tasks are executed in the background, inside the repository server. Thus the user (a perso... | SimpleDocument | daisydocs | daisydocs-2_2 | en | bruno | show |
| Document Task Manager | The purpose of the Document Task Manager (DTM) is to perform a certain task across a set of documents. The DTM is an optional component running inside the Daisy Repository Server. Some of its features are: Tasks are executed in the background, inside the repository server. Thus the user (a perso... | SimpleDocument | daisydocs | daisydocs-2_3 | en | bruno | show |
| Dokumentation für jede der veröffentlichten Versionen | Hier finden Sie die Dokumentation zu den einzelnen Versionen, die von Daisy bisher veröffentlicht wurden. Ältere Versionen: Daisy 1.2 Daisy 1.3 Daisy 1.4 Aktuelle Version: Daisy 1.5 Zukünftige Version: Daisy 2.0 | SimpleDocument | daisy | main | de | bruno | show |
| Dokumentation - Startseite | Diese Seiten umfassen die Dokumentation für Version 1.5 des Daisy Content-Management Systems. Die Startseite für das Daisy System finden Sie hier. Diese Dokumentation ist auch in Form eines Buches erhältlich, diese Buch wurde mit Hilfe des Daisy CMS publiziert. Endanwender sollten als Einführung... | SimpleDocument | daisydocs | daisydocs-1_5 | de | bruno | show |
| Dokumentation - Startseite | Diese Seiten umfassen die Dokumentation für die zukünftige Version 2.0 des Daisy Content-Management Systems. Die Startseite für das Daisy System finden Sie hier. Diese Dokumentation ist auch in Form eines Buches erhältlich, diese Buch wurde mit Hilfe des Daisy CMS publiziert. Endanwender sollten... | SimpleDocument | daisydocs | daisydocs-2_0 | de | bruno | show |
| Dokumentation - Startseite | Diese Seiten umfassen die Dokumentation für die zukünftige Version 2.0 des Daisy Content-Management Systems. Die Startseite für das Daisy System finden Sie hier. Diese Dokumentation ist auch in Form eines Buches erhältlich, diese Buch wurde mit Hilfe des Daisy CMS publiziert. Endanwender sollten... | SimpleDocument | daisydocs | daisydocs-2_1 | de | bruno | show |
| Dokumentation - Startseite | Diese Seiten umfassen die Dokumentation für die zukünftige Version 2.0 des Daisy Content-Management Systems. Die Startseite für das Daisy System finden Sie hier. Diese Dokumentation ist auch in Form eines Buches erhältlich, diese Buch wurde mit Hilfe des Daisy CMS publiziert. Endanwender sollten... | SimpleDocument | daisydocs | daisydocs-2_2 | de | bruno | show |
| Dokumentenstruktur | | Image | daisydocs | daisydocs-1_5 | de | bruno | show |
| Dokumentenstruktur | | Image | daisydocs | daisydocs-2_0 | de | bruno | show |
| Dokumentenstruktur | | Image | daisydocs | daisydocs-2_1 | de | bruno | show |
| Dokumentenstruktur | | Image | daisydocs | daisydocs-2_2 | de | bruno | show |
| dotech logo | | Image | xreporter | main | en | stevenn | show |
| duurzame_mobiliteit | | Image | daisywiki | main | en | bruno | show |
| eclipse-perspective | | Image | handbook | main | en | hepabolu | show |
| eclipse-restart | | Image | handbook | main | en | hepabolu | show |
| edit detachment sequence diagram | | Image | daisywiki | main | en | tim | show |
| Editing documents | | KnowledgeBaseCategory | daisykb | main | en | bruno | show |
| Einbindung von Multimedia-Objekten | Einführung Mittels des Dokumententyps "MultiMediaObject" ist es möglich, eine Flash-Animation, eine Filmsequenz oder eine Audiodatei einzubinden. Gebrauchsanweisung Erzeugen Sie ein neues Dokument, wählen Sie als Dokumenttyp "MultiMediaObject" und laden Sie Ihr Objekt. Von diesem Dokumententyp w... | SimpleDocument | daisydocs | daisydocs-1_5 | de | bruno | show |
| Einbindung von Multimedia-Objekten | Einführung Mittels des Dokumententyps "MultiMediaObject" ist es möglich, eine Flash-Animation, eine Filmsequenz oder eine Audiodatei einzubinden. Gebrauchsanweisung Erzeugen Sie ein neues Dokument, wählen Sie als Dokumenttyp "MultiMediaObject" und laden Sie Ihr Objekt. Von diesem Dokumententyp w... | SimpleDocument | daisydocs | daisydocs-2_0 | de | bruno | show |
| Einbindung von Multimedia-Objekten | Einführung Mittels des Dokumententyps "MultiMediaObject" ist es möglich, eine Flash-Animation, eine Filmsequenz oder eine Audiodatei einzubinden. Gebrauchsanweisung Erzeugen Sie ein neues Dokument, wählen Sie als Dokumenttyp "MultiMediaObject" und laden Sie Ihr Objekt. Von diesem Dokumententyp w... | SimpleDocument | daisydocs | daisydocs-2_1 | de | bruno | show |
| Einbindung von Multimedia-Objekten | Einführung Mittels des Dokumententyps "MultiMediaObject" ist es möglich, eine Flash-Animation, eine Filmsequenz oder eine Audiodatei einzubinden. Gebrauchsanweisung Erzeugen Sie ein neues Dokument, wählen Sie als Dokumenttyp "MultiMediaObject" und laden Sie Ihr Objekt. Von diesem Dokumententyp w... | SimpleDocument | daisydocs | daisydocs-2_2 | de | bruno | show |
| Emailer Notes | When Daisy sends emails (currently only the email notifier does this), the emails are first queued in a database table. The purpose of this is to decouple the component that sends email from the actual sending of the emails. The database table used for this is called email_queue, and has the fol... | SimpleDocument | daisydocs | daisydocs-1_2 | en | bruno | show |
| Emailer Notes | When Daisy sends emails (currently only the email notifier does this), the emails are first queued in a database table. The purpose of this is to decouple the component that sends email from the actual sending of the emails. The database table used for this is called email_queue, and has the fol... | SimpleDocument | daisydocs | daisydocs-1_3 | en | bruno | show |
| Emailer Notes | When Daisy sends emails (currently only the email notifier does this), the emails are first queued in a database table. The purpose of this is to decouple the component that sends email from the actual sending of the emails. The database table used for this is called email_queue, and has the fol... | SimpleDocument | daisydocs | daisydocs-1_4 | en | bruno | show |
| Emailer Notes | When Daisy sends emails (currently only the email notifier does this), the emails are first queued in a database table. The purpose of this is to decouple the component that sends email from the actual sending of the emails. The database table used for this is called email_queue, and has the fol... | SimpleDocument | daisydocs | daisydocs-1_5 | en | bruno | show |
| Emailer Notes | When Daisy sends emails (currently only the email notifier does this), the emails are first queued in a database table. The purpose of this is to decouple the component that sends email from the actual sending of the emails. The database table used for this is called email_queue, and has the fol... | SimpleDocument | daisydocs | daisydocs-2_0 | en | bruno | show |
| Emailer Notes | When Daisy sends emails (this is e.g. done by the email notifier, the user self-registration component, the workflow task notifiactions), the emails are first queued in a database table. The purpose of this is to decouple the component that sends email from the actual sending of the emails. The ... | SimpleDocument | daisydocs | daisydocs-2_1 | en | bruno | show |
| Emailer Notes | When Daisy sends emails (this is e.g. done by the email notifier, the user self-registration component, the workflow task notifications), the emails are first queued in a database table. The purpose of this is to decouple the component that sends email from the actual sending of the emails. The ... | SimpleDocument | daisydocs | daisydocs-2_2 | en | bruno | show |
| Emailer Notes | When Daisy sends emails (this is e.g. done by the email notifier, the user self-registration component, the workflow task notifiactions), the emails are first queued in a database table. The purpose of this is to decouple the component that sends email from the actual sending of the emails. The ... | SimpleDocument | daisydocs | daisydocs-2_3 | en | bruno | show |
| Email Notifier | General Daisy can send out emails when changes are made to documents. To make use of this the SMTP host must be correctly configured as described in the installation instructions. In the Daisy Wiki, individual users can subscribe to get notifications by selecting the "User Settings" link, making... | SimpleDocument | daisydocs | daisydocs-1_2 | en | bruno | show |
| Email Notifier | General Daisy can send out emails when changes are made to documents. To make use of this the SMTP host must be correctly configured, which is usually done as part of the installation, but can be changed afterwards (see below). In the Daisy Wiki, individual users can subscribe to get notificatio... | SimpleDocument | daisydocs | daisydocs-1_3 | en | bruno | show |
| Email Notifier | General Daisy can send out emails when changes are made to documents. To make use of this the SMTP host must be correctly configured, which is usually done as part of the installation, but can be changed afterwards (see below). In the Daisy Wiki, individual users can subscribe to get notificatio... | SimpleDocument | daisydocs | daisydocs-1_4 | en | bruno | show |
| Email Notifier | General Daisy can send out emails when changes are made to documents. To make use of this the SMTP host must be correctly configured, which is usually done as part of the installation, but can be changed afterwards (see below). In the Daisy Wiki, individual users can subscribe to get notificatio... | SimpleDocument | daisydocs | daisydocs-1_5 | en | bruno | show |
| Email Notifier | General Daisy can send out emails when changes are made to documents. To make use of this the SMTP host must be correctly configured, which is usually done as part of the installation, but can be changed afterwards (see below). In the Daisy Wiki, individual users can subscribe to get notificatio... | SimpleDocument | daisydocs | daisydocs-2_0 | en | bruno | show |
| Email Notifier | General Daisy can send out emails when changes are made to documents. To make use of this the SMTP host must be correctly configured, which is usually done as part of the installation, but can be changed afterwards (see below). In the Daisy Wiki, individual users can subscribe to get notificatio... | SimpleDocument | daisydocs | daisydocs-2_1 | en | bruno | show |
| Email Notifier | General Daisy can send out emails when changes are made to documents. To make use of this the SMTP host must be correctly configured, which is usually done as part of the installation, but can be changed afterwards (see below). In the Daisy Wiki, individual users can subscribe to get notificatio... | SimpleDocument | daisydocs | daisydocs-2_2 | en | bruno | show |
| Email Notifier | General Daisy can send out emails when changes are made to documents. To make use of this the SMTP host must be correctly configured, which is usually done as part of the installation, but can be changed afterwards (see below). In the Daisy Wiki, individual users can subscribe to get notificatio... | SimpleDocument | daisydocs | daisydocs-2_3 | en | bruno | show |
| Embedding a Java Applet inside a Daisy document | When your Daisy powered web site needs a more sophisticated user interface or more interactivity than can be provided by HTML / DHTML, etc ... then why not consider using a Java Applet ? The trick is to get things just right, so that the CLASSPATH, etc are properly served by Apache / Daisy ... ... | DaisyCommWikiDocument | daisywiki | main | en | geekscape | show |
| Embedding multimedia | Introduction It is possible to embed a flash animation, a movie or a sound fragment using the MultiMediaObject document type. Usage Create a new document, choose the document type MultiMediaObject, and upload the item. There are some fields available to control various options (like height, widt... | SimpleDocument | daisydocs | daisydocs-1_4 | en | bruno | show |
| Embedding multimedia | Introduction It is possible to embed a flash animation, a movie or a sound fragment using the MultiMediaObject document type. Usage Create a new document, choose the document type MultiMediaObject, and upload the item. There are some fields available to control various options (like height, widt... | SimpleDocument | daisydocs | daisydocs-1_5 | en | bruno | show |
| Embedding multimedia | Introduction It is possible to embed a flash animation, a movie or a sound fragment using the MultiMediaObject document type. Usage Create a new document, choose the document type MultiMediaObject, and upload the item. There are some fields available to control various options (like height, widt... | SimpleDocument | daisydocs | daisydocs-2_0 | en | bruno | show |
| Embedding multimedia and literal HTML | Introduction Daisy includes some default document types for easily embedding multi media and literal HTML. There are no special tricks involved in their implementation, you could easily create them yourself, but they are included for convenience. Embedding multi media This explains how you can ... | SimpleDocument | daisydocs | daisydocs-2_1 | en | bruno | show |
| Embedding multimedia and literal HTML | Introduction Daisy includes some default document types for easily embedding multi media and literal HTML. There are no special tricks involved in their implementation, you could easily create them yourself, but they are included for convenience. Embedding multi media This explains how you can ... | SimpleDocument | daisydocs | daisydocs-2_2 | en | bruno | show |
| Embedding multimedia and literal HTML | Introduction Daisy includes some default document types for easily embedding multi media and literal HTML. There are no special tricks involved in their implementation, you could easily create them yourself, but they are included for convenience. Embedding multi media This explains how you can ... | SimpleDocument | daisydocs | daisydocs-2_3 | en | bruno | show |
| eSignature extension | Abstract This document describes an eSignature extension for Daisy. It requires (at least) Daisy version 2.1. eSignature? Reference: pages 36-38 of http://www.fda.gov/ora/compliance_ref/part11/FRs/background/pt11finr.pdf For certain applications (life sciences), users are required to sign that ... | DaisyCommWikiDocument | daisywiki | main | en | bruno | show |
| Example code and tests | | Attachment | main | main | en | nverwer | show |
| Expanding the administration section | In Daisy's administration section it is currently possible to administrer collections, users, document types, ACLs and so forth. However the web based administration is far from complete. Sites A Daisy instance can have any number of sites. These sites typically have a homepage, navigation, skin... | DaisyCommWikiDocument | daisywiki | main | en | bruno | show |
| Export tool | The export tools exports data from a Daisy repository to a directory or zip file conforming to the Daisy import/export format. For a basic usage scenario, see the introduction. Specifying the set of documents to export The documents to export are specified in an XML file which is passed to the... | SimpleDocument | daisydocs | daisydocs-2_0 | en | bruno | show |
| Export tool | The export tools exports data from a Daisy repository to a directory or zip file conforming to the Daisy import/export format. For a basic usage scenario, see the introduction. Specifying the set of documents to export The documents to export are specified in an XML file which is passed to the... | SimpleDocument | daisydocs | daisydocs-2_1 | en | bruno | show |
| Export tool | The export tools exports data from a Daisy repository to a directory or zip file conforming to the Daisy import/export format. For a basic usage scenario, see the introduction. Specifying the set of documents to export The documents to export are specified in an XML file which is passed to the... | SimpleDocument | daisydocs | daisydocs-2_2 | en | bruno | show |
| Export tool | The export tools exports data from a Daisy repository to a directory or zip file conforming to the Daisy import/export format. For a basic usage scenario, see the introduction. Specifying the set of documents to export The documents to export are specified in an XML file which is passed to the... | SimpleDocument | daisydocs | daisydocs-2_3 | en | bruno | show |
| Expression Language | Intro Expressions are used in various places in xReporter: to calculate default values, to do validation, to insert calculated values inside SQL statements, ... The expressions are very similar to those found in spreadsheets. Basics In expressions there are four basic types: strings, numbers, d... | SimpleDocument | xreporter | main | en | stevenn | show |
| Extending the repository | This section contains information for people who want to plug in custom Java-based components in the repository server. | SimpleDocument | daisydocs | daisydocs-2_1 | en | bruno | show |
| Extending the repository | This section contains information for people who want to plug in custom Java-based components in the repository server. | SimpleDocument | daisydocs | daisydocs-2_2 | en | bruno | show |
| Extending the repository | This section contains information for people who want to plug in custom Java-based components in the repository server. | SimpleDocument | daisydocs | daisydocs-2_3 | en | bruno | show |
| Faceted Browser | Introduction The Daisy Wiki includes a faceted browser which allows for faceted navigation through the repository. The faceted browser shows the distinct values for selected properties (facets) of the documents in the repository, and allows to search for documents by selecting values for these f... | SimpleDocument | daisydocs | daisydocs-1_3 | en | bruno | show |
| Faceted Browser | Introduction The Daisy Wiki includes a faceted browser which allows for faceted navigation through the repository. The faceted browser shows the distinct values for selected properties (facets) of the documents in the repository, and allows to search for documents by selecting values for these f... | SimpleDocument | daisydocs | daisydocs-1_4 | en | bruno | show |
| Faceted Browser | Introduction The Daisy Wiki includes a faceted browser which allows for faceted navigation through the repository. The faceted browser shows the distinct values for selected properties (facets) of the documents in the repository, and allows to search for documents by selecting values for these f... | SimpleDocument | daisydocs | daisydocs-1_5 | en | bruno | show |
| Faceted Browser | Introduction The Daisy Wiki includes a faceted browser which allows for faceted navigation through the repository. The faceted browser shows the distinct values for selected properties (facets) of the documents in the repository, and allows to search for documents by selecting values for these f... | SimpleDocument | daisydocs | daisydocs-2_0 | en | bruno | show |
| Faceted Browser | Introduction The Daisy Wiki includes a faceted browser which allows for faceted navigation through the repository. The faceted browser shows the distinct values for selected properties (facets) of the documents in the repository, and allows to search for documents by selecting values for these f... | SimpleDocument | daisydocs | daisydocs-2_1 | en | bruno | show |
| Faceted Browser | Introduction The Daisy Wiki includes a faceted browser which allows for faceted navigation through the repository. The faceted browser shows the distinct values for selected properties (facets) of the documents in the repository, and allows to search for documents by selecting values for these f... | SimpleDocument | daisydocs | daisydocs-2_2 | en | bruno | show |
| Faceted Browser | Introduction The Daisy Wiki includes a faceted browser which allows for faceted navigation through the repository. The faceted browser shows the distinct values for selected properties (facets) of the documents in the repository, and allows to search for documents by selecting values for these f... | SimpleDocument | daisydocs | daisydocs-2_3 | en | bruno | show |
| FAQ | Frequently Asked Questions select name, summary where InCollection('daisydocs') and documentType = 'FAQ' and branch = ContextDoc(branch) and language = ContextDoc(language) order by creationTime option style_hint = 'daisyfaq' | SimpleDocument | daisydocs | daisydocs-1_5 | en | bruno | show |
| FAQ | Frequently Asked Questions select $FAQCategory=>name, name where InCollection('daisydocs') and documentType = 'FAQ' and branch = ContextDoc(branch) and language = ContextDoc(language) order by $FAQCategory, creationTime option style_hint = 'faq-index' | SimpleDocument | daisydocs | daisydocs-2_0 | en | bruno | show |
| FAQ | See the knowledgebase for FAQs. | SimpleDocument | daisydocs | daisydocs-2_1 | en | bruno | show |
| FAQ | See the knowledgebase for FAQs. | SimpleDocument | daisydocs | daisydocs-2_2 | en | bruno | show |
| FAQ | See the knowledgebase for FAQs. | SimpleDocument | daisydocs | daisydocs-2_3 | en | bruno | show |
| Field editors | Configuration Detection of the field editors is done when the document editor is started. Each field on the document is checked to see if an editor is available. If no editor is configured the default field editor will be used. This editor is configured based on which field type it is handeling.... | SimpleDocument | daisydocs | daisydocs-2_2 | en | paul | show |
| Field editors | Configuration Detection of the field editors is done when the document editor is started. Each field on the document is checked to see if an editor is available. If no editor is configured the default field editor will be used. This editor is configured based on which field type it is handeling.... | SimpleDocument | daisydocs | daisydocs-2_3 | en | paul | show |
| Field synchronization between language variants | This is about the problem of fields which should always have the same value in all language variants, thus are in fact not language dependent. There are a couple of possible approaches: do it manually have some process which does it for us (the approach is the same as the manual one, except ... | DaisyCommWikiDocument | daisywiki | main | en | bruno | show |
| Fins | Introduction Fins is the refactored and expanded (JFree)ChartTransformer, a charting library wrapped as a Cocoon component. Website Fins 1.0.0 documentation (works only with Cocoon 2.2 and JFreeChart 1.0.5) is available from http://www.lucamorandini.it/fins/index.html Fins 0.1.2 documentation (... | SimpleDocument | main | main | en | stevenn | show |
| First Steps | The first step to take is the installation of Java and Eclipse. Cocoon is written in Java and is therefore platform-independent. However, we have experience with Windows XP, so some instructions might be windows-only and need some changes for other operating systems. Any feedback on this is much... | SimpleDocument | handbook | main | en | hepabolu | show |
| flanderslogistics | | Image | daisywiki | main | en | bruno | show |
| Format i18n | Various user-visible labels defined in the format and format index files can be internationalized. For this we used Cocoon's "i18n transformer" system. To have something translated, you basically use an <i18n:text> tag and define the corresonding label in a resource bundle. Let's look at an exam... | SimpleDocument | xreporter | main | en | bruno | show |
| Format type config reference | Next to the standard <f:info> element in the format file, you can add more configuration for the format type. The available configuration is dependent on the format type, the following sections provide information on what's available. | SimpleDocument | xreporter | main | en | bruno | show |
| Front-end changes | The front-end (= Daisy Wiki) changes mainly fall into two categories: adding support for working with the new attributes, and adding translation management specific pages. The below are very preliminary ideas. It is however quite important to think about how the user will be confronted with, and... | DaisyCommWikiDocument | daisywiki | main | en | bruno | show |
| Full Text Indexer | Full text indexing in Daisy happens automatically when documents are updated, so you don't need to worry about updating the index yourself. More precisely, the full text indexer has a durable subscription on the JMS events generated by the repository, and it are these events which trigger the in... | SimpleDocument | daisydocs | daisydocs-1_2 | en | bruno | show |
| Full Text Indexer | Full text indexing in Daisy happens automatically when document variants are updated, so you do not need to worry about updating the index yourself. Technically, the full text indexer has a durable subscription on the JMS events generated by the repository, and it are these events which trigger ... | SimpleDocument | daisydocs | daisydocs-1_3 | en | bruno | show |
| Full Text Indexer | Full text indexing in Daisy happens automatically when document variants are updated, so you do not need to worry about updating the index yourself. Technically, the full text indexer has a durable subscription on the JMS events generated by the repository, and it are these events which trigger ... | SimpleDocument | daisydocs | daisydocs-1_4 | en | bruno | show |
| Full Text Indexer | Full text indexing in Daisy happens automatically when document variants are updated, so you do not need to worry about updating the index yourself. Technically, the full text indexer has a durable subscription on the JMS events generated by the repository, and it are these events which trigger ... | SimpleDocument | daisydocs | daisydocs-1_5 | en | bruno | show |
| Full Text Indexer | Full text indexing in Daisy happens automatically when document variants are updated, so you do not need to worry about updating the index yourself. Technically, the full text indexer has a durable subscription on the JMS events generated by the repository, and it are these events which trigger ... | SimpleDocument | daisydocs | daisydocs-2_0 | en | bruno | show |
| Full Text Indexer | Full text indexing in Daisy happens automatically when document variants are updated, so you do not need to worry about updating the index yourself. Technically, the full text indexer has a durable subscription on the JMS events generated by the repository, and it are these events which trigger ... | SimpleDocument | daisydocs | daisydocs-2_1 | en | bruno | show |
| Full Text Indexer | Full text indexing in Daisy happens automatically when document variants are updated, so you do not need to worry about updating the index yourself. Technically, the full text indexer has a durable subscription on the JMS events generated by the repository, and it are these events which trigger ... | SimpleDocument | daisydocs | daisydocs-2_2 | en | bruno | show |
| Full Text Indexer | Full text indexing in Daisy happens automatically when document variants are updated, so you do not need to worry about updating the index yourself. Technically, the full text indexer has a durable subscription on the JMS events generated by the repository, and it are these events which trigger ... | SimpleDocument | daisydocs | daisydocs-2_3 | en | bruno | show |
| Full text search | The full-text search screen can be customised: In the <wikidata> directory, look for a file named conf/search-fulltext.xml <?xml version="1.0"?> <searchconf> <!-- <documentName show="true" autoWildcards="false"/> --> <fullText show="true" required="true"/> <collections show="true" useSiteCollect... | SimpleDocument | daisydocs | daisydocs-2_3 | en | karel | show |
| General | | KnowledgeBaseCategory | daisykb | main | en | bruno | show |
| General | | KnowledgeBaseCategory | daisykb | main | en | bruno | show |
| General concept | If you want to run Daisy as part of your operational environment, you might prefer to run the different Daisy components as services, which you can easily start, stop and restart, and which ideally run under a specific user (perhaps with restricted privileges). We recommend using "wrapper" for t... | SimpleDocument | daisydocs | daisydocs-1_5 | en | stevenn | show |
| GeoID | Introduction Connectors between Apache Cocoon and geographic information services. Website Geoid 1.0.0 documentation is available from http://www.lucamorandini.it/geoid/index.html Project resources Contact: lmorandini -at- ieee - dot- org SVN: http://svn.cocoondev.org/repos/geoid/ | SimpleDocument | main | main | en | stevenn | show |
| get_detachment | | Image | daisywiki | main | en | tim | show |
| Get Cocoon | You can get Cocoon as a release version, or you can get the bleeding edge and pull it straight from the SVN. We'll describe both methods. For this tutorial we assume you use a recent release version. At the time of writing this tutorial it is 2.1.7. Get the release version Download the release v... | SimpleDocument | handbook | main | en | hepabolu | show |
| get detachment sequence diagram | | Image | daisywiki | main | en | tim | show |
| get detachment sequence diagram (violet) | | Attachment | daisywiki | main | en | tim | show |
| Getting involved | xReporter is an open-source project with a very liberal license. This means a lot more than just giving the source code away for free, and you as a user sitting back and anxiously awaiting the next release. We welcome your participation, being it questions, comments, remarks, bug reports, docume... | SimpleDocument | xreporter | main | en | mpo | show |
| Getting started | Creating your first extension Here we show how to create a very simple and mostly useless "hello world" extension, just to illustrate some basics. We will create a Cocoon pipeline which generates a blurb of HTML showing "Hello world" and then show how to include that in a Daisy document. Create ... | SimpleDocument | daisydocs | daisydocs-1_3 | en | bruno | show |
| Getting started | Creating your first extension Here we show how to create a very simple and mostly useless "hello world" extension, just to illustrate some basics. We will create a Cocoon pipeline which generates a blurb of HTML showing "Hello world" and then show how to include that in a Daisy document. Create ... | SimpleDocument | daisydocs | daisydocs-1_4 | en | bruno | show |
| Getting started | Creating your first extension Here we show how to create a very simple and mostly useless "hello world" extension, just to illustrate some basics. We will create a Cocoon pipeline which generates a blurb of HTML showing "Hello world" and then show how to include that in a Daisy document. Create ... | SimpleDocument | daisydocs | daisydocs-1_5 | en | bruno | show |
| Getting started | Creating your first extension Here we show how to create a very simple and mostly useless "hello world" extension, just to illustrate some basics. We will create a Cocoon pipeline which generates a blurb of HTML showing "Hello world" and then show how to include that in a Daisy document. Create ... | SimpleDocument | daisydocs | daisydocs-2_0 | en | bruno | show |
| Getting started | Creating your first extension Here we show how to create a very simple and mostly useless "hello world" extension, just to illustrate some basics. We will create a Cocoon pipeline which generates a blurb of HTML showing "Hello world" and then show how to include that in a Daisy document. Create ... | SimpleDocument | daisydocs | daisydocs-2_1 | en | bruno | show |
| Getting started | Creating your first extension Here we show how to create a very simple and mostly useless "hello world" extension, just to illustrate some basics. We will create a Cocoon pipeline which generates a blurb of HTML showing "Hello world" and then show how to include that in a Daisy document. Create ... | SimpleDocument | daisydocs | daisydocs-2_2 | en | bruno | show |
| Getting started | Creating your first extension Here we show how to create a very simple and mostly useless "hello world" extension, just to illustrate some basics. We will create a Cocoon pipeline which generates a blurb of HTML showing "Hello world" and then show how to include that in a Daisy document. Create ... | SimpleDocument | daisydocs | daisydocs-2_3 | en | bruno | show |
| Glossary | Definitions in the glossary: | SimpleDocument | daisydocs | daisydocs-2_1 | en | bruno | show |
| Glossary | Definitions in the glossary: | SimpleDocument | daisydocs | daisydocs-2_2 | en | bruno | show |
| Glossary | Definitions in the glossary: | SimpleDocument | daisydocs | daisydocs-2_3 | en | bruno | show |
| Glossary Example | | Image | daisywiki | main | en | kevin_walsh | show |
| Going live | This section contains items that might be worthwhile to check when putting a Daisy instance into production. Change the "testuser" account When configuring the repository server using the "daisy-repository-init" script, you are prompted for an initial bootstrap user account to be able to connect... | SimpleDocument | daisydocs | daisydocs-2_1 | en | bruno | show |
| Going live | This section contains items that might be worthwhile to check when putting a Daisy instance into production. Change the "testuser" account When configuring the repository server using the "daisy-repository-init" script, you are prompted for an initial bootstrap user account to be able to connect... | SimpleDocument | daisydocs | daisydocs-2_2 | en | bruno | show |
| Going live | This section contains items that might be worthwhile to check when putting a Daisy instance into production. Change the "testuser" account When configuring the repository server using the "daisy-repository-init" script, you are prompted for an initial bootstrap user account to be able to connect... | SimpleDocument | daisydocs | daisydocs-2_3 | en | bruno | show |
| GoogleMap FieldEditor | | Image | daisywiki | main | en | paul | show |
| Google Maps Field Editor | Lets assume you have a document and you want to attach a location to that document. For the sake of an example we'll pick landmarks. Thie Landmark document type will have parts : SimpleDocumentContent : for a little description of what we are looking at (we'll just recycle this part) Image : fo... | DaisyCommWikiDocument | daisywiki | main | en | paul | show |
| Google Summer of Code 2007 | Google is hosting a Summer of Code again! What does that mean? Well, if you are a student, and your proposal qualifies, and your contribution is considered worthwhile, then you can get paid to contribute to open source projects such as Daisy: 4500 US$, no less! You'll find much more information ... | DaisyCommWikiDocument | daisywiki | main | en | stevenn | show |
| GovCamp presentation September 2006 | Presentation about using Facet Browsing to deal with semantic tags. Given at the "GovCamp" conference in Brussels, September 2006 : presentation. | DaisyCommWikiDocument | daisywiki | main | en | mpo | show |
| GovCamp Presentation September 2006 Brussels | | Attachment | daisywiki | main | en | mpo | show |
| grouping transformer output | | Image | xreporter | main | en | stevenn | show |
| grouping transformer pipelines | | Image | xreporter | main | en | stevenn | show |
| Guided tour | This section gives you a guided tour of Daisy's translation management features to give an idea of what can be done. Completely fictional example Alice wants to create two sites about cookies. They will have the same content, but one will be in English, the other will be in French. Because her n... | SimpleDocument | daisydocs | daisydocs-2_2 | en | karel | show |
| Guided tour | This section gives you a guided tour of Daisy's translation management features to give an idea of what can be done. Completely fictional example Alice wants to create two sites about cookies. They will have the same content, but one will be in English, the other will be in French. Because her n... | SimpleDocument | daisydocs | daisydocs-2_3 | en | karel | show |
| GUI diagram | | Image | daisywiki | main | en | tim | show |
| gui-screenshot | | Image | daisywiki | main | en | tim | show |
| Guy's application | HTML DIFF PROJECT: (the original idea) PROJECT DESCRIPTION: The goal of the "HTML diff" project is to provide a Java library that compares XML files. The minimum inputs are 2 XML files, and the minimum output file is a Java representation of the basic operations that turned the first data struct... | DaisyCommWikiDocument | daisywiki | main | en | guyvdb | show |
| Guy's Test Document | Image test | DaisyCommWikiDocument | daisywiki | main | en | guyvdb | show |
| Handbook Home | This site is intended as a work-in-progress for a Cocoon tutorial that goes beyond the usual "Hello World" level. If it grows into a full-fledged Cocoon Handbook so much the better, but I have no intention of competing with other projects to upgrade and extend the Cocoon documentation. I'd rathe... | SimpleDocument | handbook | main | en | stevenn | show |
| Help, I deleted the navigation tree document!? | You accidently deleted your navigation tree document, and now you can't access your site anymore. See this mailing list message for help. | KnowledgeBaseArticle | daisykb | main | en | bruno | show |
| Hinweise zum Gebrauch des Editors im Daisy Wiki | Einleitung Dieses Dokument beschreibt den Editor der dazu genutzt wird, diejenigen Seiten zu verändern, die im Dokumentenrepository gespeichert sind. Der Editor erlaubt das Editieren im sog. WYSIWYG-Modus. Wo finde ich den Editor? Der Editor wird immer dann aufgerufen, wenn Sie entweder ein bere... | SimpleDocument | daisydocs | daisydocs-1_5 | de | bruno | show |
| Hinweise zum Gebrauch des Editors im Daisy Wiki | Einleitung Dieses Dokument beschreibt den Editor der dazu genutzt wird, diejenigen Seiten zu verändern, die im Dokumentenrepository gespeichert sind. Der Editor erlaubt das Editieren im sog. WYSIWYG-Modus. Wo finde ich den Editor? Der Editor wird immer dann aufgerufen, wenn Sie entweder ein bere... | SimpleDocument | daisydocs | daisydocs-2_0 | de | bruno | show |
| Hinweise zum Gebrauch des Editors im Daisy Wiki | Einleitung Dieses Dokument beschreibt den Editor der dazu genutzt wird, diejenigen Seiten zu verändern, die im Dokumentenrepository gespeichert sind. Der Editor erlaubt das Editieren im sog. WYSIWYG-Modus. Wo finde ich den Editor? Der Editor wird immer dann aufgerufen, wenn Sie entweder ein bere... | SimpleDocument | daisydocs | daisydocs-2_1 | de | bruno | show |
| Hinweise zum Gebrauch des Editors im Daisy Wiki | Einleitung Dieses Dokument beschreibt den Editor der dazu genutzt wird, diejenigen Seiten zu verändern, die im Dokumentenrepository gespeichert sind. Der Editor erlaubt das Editieren im sog. WYSIWYG-Modus. Wo finde ich den Editor? Der Editor wird immer dann aufgerufen, wenn Sie entweder ein bere... | SimpleDocument | daisydocs | daisydocs-2_2 | de | bruno | show |
| History | While xReporter is still very young and we prefer to talk about its future rather than its history, some of its background might be nice to know. This document has been written at the time of the second release (1.1) of xReporter in March 2003. xReporter development started in the summer of 2002... | SimpleDocument | xreporter | main | en | stevenn | show |
| Home | Welcome to Daisy - the open source CMS Downloads (dailies) Latest release (2.2) Mailing lists Commercial support What is Daisy? Daisy is a content management system that offers rich out-of-the-box functionality combined with solid foundations for extensibility and integration. Dai... | SimpleDocument | daisy | main | en | stevenn | show |
| Home | Welcome to the cocoondev.org website. cocoondev.org supports Cocoon-related, non-ASF open source projects by providing Subversion for source code management mailing lists for (inter)project communication Jira for issue tracking a project web presence through Daisy or static HTML a shared bloggi... | SimpleDocument | main | main | en | stevenn | show |
| How can I edit a document when it fails to display? | In some rare circumstances, there might be something in a document that causes its rendering to fail. For example, the document contains a "query-and-include" instruction which selects so many documents that there is not enough memory to render them. In such cases, the page actions menu will not... | FAQ | daisydocs | daisydocs-2_0 | en | bruno | show |
| How can I edit a document when it fails to display? | In some rare circumstances, there might be something in a document that causes its rendering to fail. For example, the document contains a "query-and-include" instruction which selects so many documents that there is not enough memory to render them. In such cases, the page actions menu will not... | KnowledgeBaseArticle | daisykb | main | en | bruno | show |
| How do I change the daisyrepository database to UTF-8? | For newer Daisy versions (1.5, 2.0, ...) the installation instructions create databases using the UTF-8 character set by default. The following information is mainly for people how have been using Daisy since older releases. Overview Two steps are involved: Changing the MySQL database to UTF-8 ... | FAQ | daisydocs | daisydocs-2_0 | en | bruno | show |
| How do I change the daisyrepository database to UTF-8? | For newer Daisy versions (1.5, 2.0, ...) the installation instructions create databases using the UTF-8 character set by default. The following information is mainly for people how have been using Daisy since older releases. Overview Two steps are involved: Changing the MySQL database to UTF-8 ... | KnowledgeBaseArticle | daisykb | main | en | bruno | show |
| How do I change the document type of a set of documents? | Suppose you start out with the "Simple Document" document type, but after a while decide you want to switch to your own document type with custom fields and/or parts. You can easily migrate your existing documents to the new document type using a document task. A document task is some task that ... | FAQ | daisydocs | daisydocs-1_5 | en | bruno | show |
| How do I change the document type of a set of documents? | Suppose you start out with the "Simple Document" document type, but after a while decide you want to switch to your own document type with custom fields and/or parts. You can easily migrate your existing documents to the new document type using a document task. A document task is some task that ... | FAQ | daisydocs | daisydocs-2_0 | en | bruno | show |
| How do I change the document type of a set of documents? | Suppose you start out with the "Simple Document" document type, but after a while decide you want to switch to your own document type with custom fields and/or parts. You can easily migrate your existing documents to the new document type using a document task. A document task is some task that ... | KnowledgeBaseArticle | daisykb | main | en | bruno | show |
| How do I enable the collapse/expand behaviour of the navigation tree? | By default after setting up Daisy and creating a site with the daisy-wiki-add-site tool, the navigation tree of the site will always be displayed fully. To enable the expand/collapse behaviour, you need to set the contextualizedTree property in the siteconf.xml. This is done by opening the sitec... | FAQ | daisydocs | daisydocs-1_5 | en | bruno | show |
| How do I enable the collapse/expand behaviour of the navigation tree? | By default after setting up Daisy and creating a site with the daisy-wiki-add-site tool, the navigation tree of the site will always be displayed fully. To enable the expand/collapse behaviour, you need to set the contextualizedTree property in the siteconf.xml. This is done by opening the sitec... | FAQ | daisydocs | daisydocs-2_0 | en | bruno | show |
| How do I enable the collapse/expand behaviour of the navigation tree? | By default after setting up Daisy and creating a site with the daisy-wiki-add-site tool, the navigation tree of the site will always be displayed fully. To enable the expand/collapse behaviour, you need to set the contextualizedTree property in the siteconf.xml. This is done by opening the sitec... | KnowledgeBaseArticle | daisykb | main | en | bruno | show |
| How do I set the reference language for an existing set of documents? | If you have an existing set of documents for which you want to initialize the reference language, you don't need to do this manually. You can use a document task for this. Here is how to do it: Make sure you are logged in as Administrator. Choose Tools -> Document Tasks. Select "Create a new doc... | KnowledgeBaseArticle | daisykb | main | en | bruno | show |
| How do I solve "Lock obtain timed out: SimpleFSLock@/.../indexstore/write.lock" at repository startup? | If you get this error when starting up the repository server, there are two possible situations: Daisy is already/still running (though in that case you'll likely get errors about ports being in use before you see this one) Daisy didn't shut down cleanly the last time it was stopped In the sec... | FAQ | daisydocs | daisydocs-2_0 | en | bruno | show |
| How do I solve "Lock obtain timed out: SimpleFSLock@/.../indexstore/write.lock" at repository startup? | If you get this error when starting up the repository server, there are two possible situations: Daisy is already/still running (though in that case you'll likely get errors about ports being in use before you see this one) Daisy didn't shut down cleanly the last time it was stopped In the sec... | KnowledgeBaseArticle | daisykb | main | en | bruno | show |
| How do I use my own favicon.ico or robots.txt? | The default favicon.ico and robots.txt files of Daisy can be found at <DAISY_HOME>/daisywiki/webapp/daisy/resources/ If you want to modify them, do not overwrite these files, as these changes will be lost when upgrading Daisy. Rather, put your own files in: <wiki data directory>/resources/ If t... | KnowledgeBaseArticle | daisykb | main | en | bruno | show |
| How to build a Glossary in daisy | Providing a Glossary in daisy Introduction This document explains how to setup a glossary. It is based on a real example. When using daisy as a company documentation system, it may be necessary to have a glossary that explains terminology and give examples. Each term should be a single document ... | DaisyCommWikiDocument | daisywiki | main | en | kevin_walsh | show |
| How-to Install/Config on Mandriva Linux | Daisy install on Mandriva Linux : System configuration = Mandriva 10.x server 2005LE - Apache 2.0xx avec Virtual Hosts - Java 1.5x - Tomcat 5.x - mod-jk 1.2x Version française du document : http://www.apachefrance.com/Forums/index.php?showtopic=3606 Step 1 - Create Databases & Users - (syntax i... | DaisyCommWikiDocument | daisywiki | main | en | patrick | show |
| How to solve this error when running daisy-wiki-init: "Data truncation: Data too long for column 'value' at row 1"? | The reason is daisy-wiki-init tries too load schema types with descriptions in various languages which sometimes use special glyphs, and MySQL fails over this. The solution is simple: change your database to UTF-8. | FAQ | daisydocs | daisydocs-2_0 | en | bruno | show |
| How to solve this error when running daisy-wiki-init: "Data truncation: Data too long for column 'value' at row 1"? | The reason is daisy-wiki-init tries too load schema types with descriptions in various languages which sometimes use special glyphs, and MySQL fails over this. The solution is simple: change your database to UTF-8. | KnowledgeBaseArticle | daisykb | main | en | bruno | show |
| HTML diff (compare) component | This project is a research-level project for an ambitious student. Background The main content type used for textual content in Daisy is a subset of HTML which is also well-formed XML (technically, it's not XHTML since it's not in the XHTML namespace). Much like a source code version control sys... | DaisyCommWikiDocument | daisywiki | main | en | bruno | show |
| HTTP API | Introduction Daisy contains a HTTP+XML interface, which is an interface to talk to the repository server by exchanging XML messages over the HTTP protocol. This interface offers full access to all functionality of the repository. The HTTP protocol is a protocol that allows to perform a limited n... | SimpleDocument | daisydocs | daisydocs-1_2 | en | bruno | show |
| HTTP API | Introduction Daisy contains a HTTP+XML interface, which is an interface to talk to the repository server by exchanging XML messages over the HTTP protocol. This interface offers full access to all functionality of the repository. The HTTP protocol is a protocol that allows to perform a limited n... | SimpleDocument | daisydocs | daisydocs-1_3 | en | bruno | show |
| HTTP API | Introduction Daisy contains a HTTP+XML interface, which is an interface to talk to the repository server by exchanging XML messages over the HTTP protocol. This interface offers full access to all functionality of the repository. The HTTP protocol is a protocol that allows to perform a limited n... | SimpleDocument | daisydocs | daisydocs-1_4 | en | bruno | show |
| HTTP API | Introduction Daisy contains a HTTP+XML interface, which is an interface to talk to the repository server by exchanging XML messages over the HTTP protocol. This interface offers full access to all functionality of the repository. The HTTP protocol is a protocol that allows to perform a limited n... | SimpleDocument | daisydocs | daisydocs-1_5 | en | bruno | show |
| HTTP API | Introduction Daisy contains a HTTP+XML interface, which is an interface to talk to the repository server by exchanging XML messages over the HTTP protocol. This interface offers full access to all functionality of the repository. The HTTP protocol is a protocol that allows to perform a limited n... | SimpleDocument | daisydocs | daisydocs-2_0 | en | bruno | show |
| HTTP API | Introduction Daisy contains a HTTP+XML interface, which is an interface to talk to the repository server by exchanging XML messages over the HTTP protocol. This interface offers full access to all functionality of the repository. The HTTP protocol is a protocol that allows to perform a limited n... | SimpleDocument | daisydocs | daisydocs-2_1 | en | bruno | show |
| HTTP API | Introduction Daisy contains a HTTP+XML interface, which is an interface to talk to the repository server by exchanging XML messages over the HTTP protocol. This interface offers full access to all functionality of the repository. The HTTP protocol is a protocol that allows to perform a limited n... | SimpleDocument | daisydocs | daisydocs-2_2 | en | bruno | show |
| HTTP API | Introduction Daisy contains a HTTP+XML interface, which is an interface to talk to the repository server by exchanging XML messages over the HTTP protocol. This interface offers full access to all functionality of the repository. The HTTP protocol is a protocol that allows to perform a limited n... | SimpleDocument | daisydocs | daisydocs-2_3 | en | bruno | show |
| HTTPClient class | | Image | daisywiki | main | en | sokol8 | show |
| HTTP Interface | Introduction The xReporter server is a standalone application. To communicate with the server a HTTP interface is available, which will be described in this document. This HTTP interface will be used by other applications, and not by end-users in their web browser. The HTTP interface for the web... | SimpleDocument | xreporter | main | en | bruynb | show |
| I'm learning to fly | | Image | daisy | main | en | stevenn | show |
| Ideas for a new skin | Some grab of first ideas on what a new Daisy skin should provide: (This list started off as a resume of email discussions, feel free to add more stuff here) Organization/principles Very rough idea: separate display organisation from content organisation. The text below should be verified against... | DaisyCommWikiDocument | daisywiki | main | en | mpo | show |
| IIS and Daisy | To set IIS as a proxy for Daisy you should do the following. Configure Daisy Add an AJP listener to Daisy. This can be done in the <WIKIDATA>/jetty-daisywiki.xml. This will override the standard daisy jetty configuration. If you are using service scripts then you should edit the configuration so... | SimpleDocument | daisydocs | daisydocs-2_3 | en | paul | show |
| Image thumbnails and metadata extraction | The repository server contains an (optional) component that can perform image thumbnailing and extraction of metadata (width, height and, for jpeg, arbitrary EXIF fields). This component is registered as a "pre-save-hook", this is a component which gets called before a document is saved, and whi... | SimpleDocument | daisydocs | daisydocs-1_5 | en | bruno | show |
| Image thumbnails and metadata extraction | The repository server contains an (optional) component that can perform image thumbnailing, extraction of metadata (width, height and, for JPEG, arbitrary Exif fields), and automatic rotation of JPEG images as indicated in the Exif data. This component is registered as a "pre-save-hook", this is... | SimpleDocument | daisydocs | daisydocs-2_0 | en | bruno | show |
| Image thumbnails and metadata extraction | The repository server contains an (optional) component that can perform image thumbnailing, extraction of metadata (width, height and, for JPEG, arbitrary Exif fields), and automatic rotation of JPEG images as indicated in the Exif data. This component is registered as a "pre-save-hook", this is... | SimpleDocument | daisydocs | daisydocs-2_1 | en | bruno | show |
| Image thumbnails and metadata extraction | The repository server contains an (optional) component that can perform image thumbnailing, extraction of metadata (width, height and, for JPEG, arbitrary Exif fields), and automatic rotation of JPEG images as indicated in the Exif data. This component is registered as a "pre-save-hook", this is... | SimpleDocument | daisydocs | daisydocs-2_2 | en | bruno | show |
| Image thumbnails and metadata extraction | The repository server contains an (optional) component that can perform image thumbnailing, extraction of metadata (width, height and, for JPEG, arbitrary Exif fields), and automatic rotation of JPEG images as indicated in the Exif data. This component is registered as a "pre-save-hook", this is... | SimpleDocument | daisydocs | daisydocs-2_3 | en | bruno | show |
| Implementation notes | Below is a collection of implementation details and why we chose to do something this or that way. They are collected here (a) to prevent us from raising the same issues multiple times, (b) to group them in one place and (c) to be able to organise them into groups of related issues. Setting / c... | DaisyCommWikiDocument | daisywiki | main | en | karel | show |
| Import/export format | This section describes the import/export format. This is the format produced by the export tool, and expected by the import tool. The format consists of a directory structure containing files (XML files and binary data files). This directory structure can optionally be zipped, though this is not... | SimpleDocument | daisydocs | daisydocs-2_0 | en | bruno | show |
| Import/export format | This section describes the import/export format. This is the format produced by the export tool, and expected by the import tool. The format consists of a directory structure containing files (XML files and binary data files). This directory structure can optionally be zipped, though this is not... | SimpleDocument | daisydocs | daisydocs-2_1 | en | bruno | show |
| Import/export format | This section describes the import/export format. This is the format produced by the export tool, and expected by the import tool. The format consists of a directory structure containing files (XML files and binary data files). This directory structure can optionally be zipped, though this is not... | SimpleDocument | daisydocs | daisydocs-2_2 | en | bruno | show |
| Import/export format | This section describes the import/export format. This is the format produced by the export tool, and expected by the import tool. The format consists of a directory structure containing files (XML files and binary data files). This directory structure can optionally be zipped, though this is not... | SimpleDocument | daisydocs | daisydocs-2_3 | en | bruno | show |
| Import/export introduction | The export and import tools allow to copy (synchronize, replicate) documents between Daisy repositories that have different namespaces. It is required that the repositories have different namespaces in order to keep the identity of the documents. For one-time transfer of documents from one repos... | SimpleDocument | daisydocs | daisydocs-2_0 | en | bruno | show |
| Import/export introduction | The export and import tools allow to copy (synchronize, replicate) documents between Daisy repositories that have different namespaces. It is required that the repositories have different namespaces in order to keep the identity of the documents. For one-time transfer of documents from one repos... | SimpleDocument | daisydocs | daisydocs-2_1 | en | bruno | show |
| Import/export introduction | The export and import tools allow to copy (synchronize, replicate) documents between Daisy repositories that have different namespaces. It is required that the repositories have different namespaces in order to keep the identity of the documents. For one-time transfer of documents from one repos... | SimpleDocument | daisydocs | daisydocs-2_2 | en | bruno | show |
| Import/export introduction | The export and import tools allow to copy (synchronize, replicate) documents between Daisy repositories that have different namespaces. It is required that the repositories have different namespaces in order to keep the identity of the documents. For one-time transfer of documents from one repos... | SimpleDocument | daisydocs | daisydocs-2_3 | en | bruno | show |
| Import tool | The import tool imports data conforming to the Daisy import/export format into a Daisy repository. This data will usually be created with the export tool, but this is not a requirement, the data simply needs to conform to the required format and might hence be produced manually or by custom tool... | SimpleDocument | daisydocs | daisydocs-2_0 | en | bruno | show |
| Import tool | The import tool imports data conforming to the Daisy import/export format into a Daisy repository. This data will usually be created with the export tool, but this is not a requirement, the data simply needs to conform to the required format and might hence be produced manually or by custom tool... | SimpleDocument | daisydocs | daisydocs-2_1 | en | bruno | show |
| Import tool | The import tool imports data conforming to the Daisy import/export format into a Daisy repository. This data will usually be created with the export tool, but this is not a requirement, the data simply needs to conform to the required format and might hence be produced manually or by custom tool... | SimpleDocument | daisydocs | daisydocs-2_2 | en | bruno | show |
| Import tool | The import tool imports data conforming to the Daisy import/export format into a Daisy repository. This data will usually be created with the export tool, but this is not a requirement, the data simply needs to conform to the required format and might hence be produced manually or by custom tool... | SimpleDocument | daisydocs | daisydocs-2_3 | en | bruno | show |
| Include Permissions | Daisy allows to do inclusions in documents. This can be either other Daisy documents (through the "daisy:" syntax) or when published through the Daisy Wiki, any URL resolvable by Cocoon (the framework on which the Daisy Wiki is implemented). However, allowing document authors to include any arbi... | SimpleDocument | daisydocs | daisydocs-1_3 | en | bruno | show |
| Include Permissions | Daisy allows to do inclusions in documents. This can be either other Daisy documents (through the "daisy:" syntax) or when published through the Daisy Wiki, any URL resolvable by Cocoon (the framework on which the Daisy Wiki is implemented). However, allowing document authors to include any arbi... | SimpleDocument | daisydocs | daisydocs-1_4 | en | bruno | show |
| Include Permissions | Daisy allows to do inclusions in documents. This can be either other Daisy documents (through the "daisy:" syntax) or when published through the Daisy Wiki, any URL resolvable by Cocoon (the framework on which the Daisy Wiki is implemented). However, allowing document authors to include any arbi... | SimpleDocument | daisydocs | daisydocs-1_5 | en | bruno | show |
| Include Permissions | Daisy allows to do inclusions in documents. This can be either other Daisy documents (through the "daisy:" syntax) or when published through the Daisy Wiki, any URL resolvable by Cocoon (the framework on which the Daisy Wiki is implemented). However, allowing document authors to include any arbi... | SimpleDocument | daisydocs | daisydocs-2_0 | en | bruno | show |
| Include Permissions | Daisy allows to do inclusions in documents. This can be either other Daisy documents (through the "daisy:" syntax) or when published through the Daisy Wiki, any URL resolvable by Cocoon (the framework on which the Daisy Wiki is implemented). However, allowing document authors to include any arbi... | SimpleDocument | daisydocs | daisydocs-2_1 | en | bruno | show |
| Include Permissions | Daisy allows to do inclusions in documents. This can be either other Daisy documents (through the "daisy:" syntax) or when published through the Daisy Wiki, any URL resolvable by Cocoon (the framework on which the Daisy Wiki is implemented). However, allowing document authors to include any arbi... | SimpleDocument | daisydocs | daisydocs-2_2 | en | bruno | show |
| Include Permissions | Daisy allows to do inclusions in documents. This can be either other Daisy documents (through the "daisy:" syntax) or when published through the Daisy Wiki, any URL resolvable by Cocoon (the framework on which the Daisy Wiki is implemented). However, allowing document authors to include any arbi... | SimpleDocument | daisydocs | daisydocs-2_3 | en | bruno | show |
| Inline editing | Document styling allows you to show a document's parts, fields and metadata in a visually appealing way. The inline editing feature allows you to edit your documents while using the same layout. Usage The inline editing feature is always on. To use it, you have to add some attributes to your d... | SimpleDocument | daisydocs | daisydocs-2_3 | en | karel | show |
| Install and Config Notes | Changing location (port or machine) of the different processes This section details the changes to be done to run the different servers needed for Daisy on different machines or let them listen to different ports. The machine on which you want to run the Daisy Wiki only needs the DAISY_HOME/dai... | SimpleDocument | daisydocs | daisydocs-1_2 | en | bruno | show |
| Installation | These instructions only apply to Daisy 1.2. For Daisy 1.3, see here. Downloading Daisy Packaged versions of Daisy, which include Cocoon, OpenJMS and Merlin can be found in the distribution area. Daisy also requires a recent installation of the MySQL database server (>= version 4.0.20). Daisy has... | SimpleDocument | daisydocs | daisydocs-1_2 | en | bruno | show |
| Installation | Downloading Daisy Packaged versions of Daisy can be found in the distribution area. This includes everything required to run Daisy, except for: a Java Virtual Machine (JVM): version 1.4.2, version 5 (= 1.5) or higher required a MySQL database: version 4.0.20 or higher, or version 4.1.7 or highe... | SimpleDocument | daisydocs | daisydocs-1_3 | en | bruno | show |
| Installation | Downloading Daisy Packaged versions of Daisy can be found in the distribution area. This includes everything required to run Daisy, except for: a Java Virtual Machine (JVM): version 1.4.2, version 5 (= 1.5) or higher required a MySQL database: version 4.0.20 or higher, or version 4.1.7 or highe... | SimpleDocument | daisydocs | daisydocs-1_4 | en | bruno | show |
| Installation | Downloading Daisy Packaged versions of Daisy can be found in the distribution area (Sourceforge). This includes everything required to run Daisy, except for: a Java Virtual Machine (JVM): version 1.4.2, version 5 (= 1.5), or higher required a MySQL database: version 4.1.7 or higher required (5 ... | SimpleDocument | daisydocs | daisydocs-1_5 | en | bruno | show |
| Installation | These installation instructions are being updated for Daisy 1.5-M2. To install Daisy 1.5-M1, please follow the instructions for Daisy 1.4, which are the same Daisy herunterladen Packaged versions of Daisy can be found in the distribution area (Sourceforge). This includes everything required to r... | SimpleDocument | daisydocs | daisydocs-1_5 | de | bruno | show |
| Installation | Downloading Daisy Packaged versions of Daisy can be found in the distribution area (Sourceforge). This includes everything required to run Daisy, except for: a Java Virtual Machine (JVM): Java 1.5 or higher required a MySQL database: version 4.1.7 or higher required (5 also fine) If you don't ... | SimpleDocument | daisydocs | daisydocs-2_0 | en | bruno | show |
| Installation | Downloading Daisy Packaged versions of Daisy can be found in the distribution area (Sourceforge). This includes everything required to run Daisy, except for: a Java Virtual Machine (JVM): version 1.4.2, version 5 (= 1.5), or higher required a MySQL database: version 4.1.7 or higher required (5 ... | SimpleDocument | daisydocs | daisydocs-2_0 | de | bruno | show |
| Installation | Downloading Daisy Packaged versions of Daisy can be found in the distribution area (Sourceforge). This includes everything required to run Daisy, except for: a Java Virtual Machine (JVM): Java 1.5 or higher required a MySQL database: version 4.1.7 or higher required (5 also fine) If you don't ... | SimpleDocument | daisydocs | daisydocs-2_1 | en | bruno | show |
| Installation | Downloading Daisy Packaged versions of Daisy can be found in the distribution area (Sourceforge). This includes everything required to run Daisy, except for: a Java Virtual Machine (JVM): version 1.4.2, version 5 (= 1.5), or higher required a MySQL database: version 4.1.7 or higher required (5 ... | SimpleDocument | daisydocs | daisydocs-2_1 | de | bruno | show |
| Installation | Downloading Daisy Packaged versions of Daisy can be found in the distribution area (Sourceforge). This includes everything required to run Daisy, except for: a Java Virtual Machine (JVM): Java 1.5 or higher required a MySQL database: version 4.1.7 or higher required (5 also fine) If you don't ... | SimpleDocument | daisydocs | daisydocs-2_2 | en | bruno | show |
| Installation | Downloading Daisy Packaged versions of Daisy can be found in the distribution area (Sourceforge). This includes everything required to run Daisy, except for: a Java Virtual Machine (JVM): version 1.4.2, version 5 (= 1.5), or higher required a MySQL database: version 4.1.7 or higher required (5 ... | SimpleDocument | daisydocs | daisydocs-2_2 | de | bruno | show |
| Installation | Downloading Daisy Packaged versions of Daisy can be found in the distribution area (Sourceforge). This includes everything required to run Daisy, except for: a Java Virtual Machine (JVM): Java 1.5 or higher required a MySQL database: version 4.1.7 or higher required (5 also fine) If you don't ... | SimpleDocument | daisydocs | daisydocs-2_3 | en | bruno | show |
| Installation and update | | FAQCategory | daisydocs | daisydocs-2_0 | en | bruno | show |
| Installation and update | | FAQCategory | daisydocs | daisydocs-2_1 | en | bruno | show |
| Installation and update | | FAQCategory | daisydocs | daisydocs-2_2 | en | bruno | show |
| Installation and update | | FAQCategory | daisydocs | daisydocs-2_3 | en | bruno | show |
| Installation and update | | KnowledgeBaseCategory | daisykb | main | en | bruno | show |
| Integrating DaisyWiki and JAAS | This is a draft version. It is not meant to be complete and may contain mistakes, errors. Your comments are welcome. Introduction Initially, Daisy Wiki has no support for JAAS based security. The lack of JAAS security support prohibits integrating of Daisy Wiki with other web applications. Lucki... | DaisyCommWikiDocument | daisywiki | main | en | bobbie | show |
| Integration of Daisy in non-Java environments. | In GSOC 2006 we had a student that created a PHP library. Daisy has a language-neutral HTTP/XML-based API to access its stand-alone repository server. Daisy has also (of course) a native Java API wich can work in-JVM or remotely (transparently communicating over the HTTP/XML API), as illustrated... | DaisyCommWikiDocument | daisywiki | main | en | bruno | show |
| intergator screenshot | | Image | daisywiki | main | en | bruno | show |
| Internationalisation | Introduction (i18n is new in Daisy 1.1) We welcome translations to new languages, or improvements to the currently available languages. Send translations to the mailing list, or attach them to an issue in Jira. Make sure you use UTF-8 encoding in your files (except for the .property files -- see... | SimpleDocument | daisydocs | daisydocs-1_2 | en | bruno | show |
| Internationalisation | Introduction We welcome translations to new languages, or improvements to the currently available languages. Send translations to the mailing list, or attach them to an issue in Jira. Make sure you use UTF-8 encoding in your files (except for the .property files -- see below). Also, check on the... | SimpleDocument | daisydocs | daisydocs-1_3 | en | bruno | show |
| Internationalisation | Introduction We welcome translations to new languages, or improvements to the currently available languages. Send translations to the mailing list, or attach them to an issue in Jira. Make sure you use UTF-8 encoding in your files (except for the .property files -- see below). Also, check on the... | SimpleDocument | daisydocs | daisydocs-1_4 | en | bruno | show |
| Internationalisation | Introduction We welcome translations to new languages, or improvements to the currently available languages. Send translations to the mailing list, or attach them to an issue in Jira. Make sure you use UTF-8 encoding in your files (except for the .properties files -- see below). Also, check on t... | SimpleDocument | daisydocs | daisydocs-1_5 | en | bruno | show |
| Internationalisation | Introduction We welcome translations to new languages, or improvements to the currently available languages. Send translations to the mailing list, or attach them to an issue in Jira. Make sure you use UTF-8 encoding in your files (except for the .properties files -- see below). Also, check on t... | SimpleDocument | daisydocs | daisydocs-2_0 | en | bruno | show |
| Internationalisation | Introduction We welcome translations to new languages, or improvements to the currently available languages. Send translations to the mailing list, or attach them to an issue in Jira. Make sure you use UTF-8 encoding in your files (except for the .properties files -- see below). Also, check on t... | SimpleDocument | daisydocs | daisydocs-2_1 | en | bruno | show |
| Internationalisation | Introduction We welcome translations to new languages, or improvements to the currently available languages. Send translations to the mailing list, or attach them to an issue in Jira. Make sure you use UTF-8 encoding in your files (except for the .properties files -- see below). Also, check on t... | SimpleDocument | daisydocs | daisydocs-2_2 | en | bruno | show |
| Internationalisation | Introduction We welcome translations to new languages, or improvements to the currently available languages. Send translations to the mailing list, or attach them to an issue in Jira. Make sure you use UTF-8 encoding in your files (except for the .properties files -- see below). Also, check on t... | SimpleDocument | daisydocs | daisydocs-2_3 | en | bruno | show |
| Introduction | The GroupingTransformer is a transformer for use within Apache Cocoon. It can group table-like data and calculate summaries for each group. It is based on the grouping and expression language code from xReporter, though it does not require xReporter to be used (and vice versa: if you're using xR... | SimpleDocument | xreporter | main | en | stevenn | show |
| Issue tracking | Jira usage guidelines I spent some time in the xReporter Jira and found that the issues were all sort of lumped together, and that I was unable to use it to answer some of the questions I had about what had been entered previously. Specifically, it didn't seem as if we were using the workflow / ... | SimpleDocument | xreporter | main | en | bruynb | show |
| Is there a spell checker? | Daisy's HTML editor doesn't include a spell checker (itself). This is mostly due to the lack of available open-source Java-based spell check solutions. Also, server-based spell checking solutions are not as comfortable as client-side solutions. The good news is that Firefox 2.0 includes a spell ... | FAQ | daisydocs | daisydocs-2_0 | en | bruno | show |
| Is there a spell checker? | Daisy's HTML editor doesn't include a spell checker (itself). This is mostly due to the lack of available open-source Java-based spell check solutions. Also, server-based spell checking solutions are not as comfortable as client-side solutions. The good news is that Firefox 2.0 includes a spell ... | KnowledgeBaseArticle | daisykb | main | en | bruno | show |
| jars snippet | | Attachment | main | main | en | ugo | show |
| Java API | Introduction Daisy is written in Java and thus its native interface is a Java API. This Java API is packaged separately, and consists of two jars: daisy-repository-api-<version>.jar daisy-repository-xmlschema-bindings-<version>.jar The second jar, the xmlschema-bindings, are Java classes generat... | SimpleDocument | daisydocs | daisydocs-1_2 | en | bruno | show |
| Java API | Introduction Daisy is written in Java and thus its native interface is a Java API. This Java API is packaged separately, and consists of two jars: daisy-repository-api-<version>.jar daisy-repository-xmlschema-bindings-<version>.jar The second jar, the xmlschema-bindings, are Java classes generat... | SimpleDocument | daisydocs | daisydocs-1_3 | en | bruno | show |
| Java API | Introduction Daisy is written in Java and thus its native interface is a Java API. This Java API is packaged separately, and consists of two jars: daisy-repository-api-<version>.jar daisy-repository-xmlschema-bindings-<version>.jar The second jar, the xmlschema-bindings, are Java classes generat... | SimpleDocument | daisydocs | daisydocs-1_4 | en | bruno | show |
| Java API | Introduction Daisy is written in Java and thus its native interface is a Java API. This Java API is packaged separately, and consists of two jars: daisy-repository-api-<version>.jar daisy-repository-xmlschema-bindings-<version>.jar The second jar, the xmlschema-bindings, are Java classes generat... | SimpleDocument | daisydocs | daisydocs-1_5 | en | bruno | show |
| Java API | Introduction Daisy is written in Java and thus its native interface is a Java API. This Java API is packaged separately, and consists of two jars: daisy-repository-api-<version>.jar daisy-repository-xmlschema-bindings-<version>.jar The second jar, the xmlschema-bindings, are Java classes generat... | SimpleDocument | daisydocs | daisydocs-2_0 | en | bruno | show |
| Java API | Introduction Daisy is written in Java and thus its native interface is a Java API. This Java API is packaged separately, and consists of two jars: daisy-repository-api-<version>.jar daisy-repository-xmlschema-bindings-<version>.jar The second jar, the xmlschema-bindings, are Java classes generat... | SimpleDocument | daisydocs | daisydocs-2_1 | en | bruno | show |
| Java API | Introduction Daisy is written in Java and thus its native interface is a Java API. This Java API is packaged separately, and consists of two jars: daisy-repository-api-<version>.jar daisy-repository-xmlschema-bindings-<version>.jar The second jar, the xmlschema-bindings, are Java classes generat... | SimpleDocument | daisydocs | daisydocs-2_2 | en | bruno | show |
| Java API | Introduction Daisy is written in Java and thus its native interface is a Java API. This Java API is packaged separately, and consists of two jars: daisy-repository-api-<version>.jar daisy-repository-xmlschema-bindings-<version>.jar The second jar, the xmlschema-bindings, are Java classes generat... | SimpleDocument | daisydocs | daisydocs-2_3 | en | bruno | show |
| Java API Documentation | The Daisy API for the latest version of the Daisy CMS ? as of this writing version 2.0 ? can be found at http://cocoondev.org/javadoc/daisy/2.0/ Everyone who seriously wants to extend or modify daisy in some way or the other, using the Java programming language needs access to the Daisy's javad... | DaisyCommWikiDocument | daisywiki | main | en | deining | show |
| JMS | | KnowledgeBaseCategory | daisykb | main | en | bruno | show |
| JMS Cache Invalidation Sample | | CodeSample | daisydocs | daisydocs-1_3 | en | bruno | show |
| JMS Cache Invalidation Sample | | CodeSample | daisydocs | daisydocs-1_4 | en | bruno | show |
| JMS Cache Invalidation Sample | | CodeSample | daisydocs | daisydocs-1_5 | en | bruno | show |
| JMS Cache Invalidation Sample | | CodeSample | daisydocs | daisydocs-2_0 | en | bruno | show |
| JMS Cache Invalidation Sample | | CodeSample | daisydocs | daisydocs-2_1 | en | bruno | show |
| JMS Cache Invalidation Sample | | CodeSample | daisydocs | daisydocs-2_2 | en | bruno | show |
| JMS Cache Invalidation Sample | | CodeSample | daisydocs | daisydocs-2_3 | en | bruno | show |
| JMX console | The Daisy repository server offers a JMX (Java Management Extensions) console through which certain things can be monitored or certain settings can be changed at runtime. In JMX, the components that provide this management access are called MBeans. The MBeans of the embedded ActiveMQ server are ... | SimpleDocument | daisydocs | daisydocs-2_0 | en | bruno | show |
| JMX console | The Daisy repository server offers a JMX (Java Management Extensions) console through which certain things can be monitored or certain settings can be changed at runtime. In JMX, the components that provide this management access are called MBeans. The MBeans of the embedded ActiveMQ server are ... | SimpleDocument | daisydocs | daisydocs-2_1 | en | bruno | show |
| JMX console | The Daisy repository server offers a JMX (Java Management Extensions) console through which certain things can be monitored or certain settings can be changed at runtime. In JMX, the components that provide this management access are called MBeans. The MBeans of the embedded ActiveMQ server are ... | SimpleDocument | daisydocs | daisydocs-2_2 | en | bruno | show |
| JMX console | The Daisy repository server offers a JMX (Java Management Extensions) console through which certain things can be monitored or certain settings can be changed at runtime. In JMX, the components that provide this management access are called MBeans. The MBeans of the embedded ActiveMQ server are ... | SimpleDocument | daisydocs | daisydocs-2_3 | en | bruno | show |
| KB Category navigation tree | | Navigation | daisykb | main | en | bruno | show |
| KB full index navigation tree | | Navigation | daisykb | main | en | bruno | show |
| Keeping track of SVN trunk changes | On this page we keep track of SVN revisions that introduce changes to the database schema, the myconfig.xml, or other things which require some upgrade action when working on SVN trunk. This initiative has been started on November 13, 2006. Newest entries should be put on top. <daisy-src> is use... | DaisyCommWikiDocument | daisywiki | main | en | bruno | show |
| key icon | | Image | xreporter | main | en | mpo | show |
| Kommentare zu Dokumenten | Dieser Abschnitt behandelt Kommentare zu Dokumenten: Kommentare können zu Daisy Dokumenten hinzugefügt werden. Genauer gesagt werden sie tatsächlich zu einer bestimmten Variante eines Dokuments hinzugefügt. Von daher besitzt auch jede Variante eines Dokuments ihre eigenen Kommentare. Eigenschaft... | SimpleDocument | daisydocs | daisydocs-1_5 | de | bruno | show |
| Kommentare zu Dokumenten | Dieser Abschnitt behandelt Kommentare zu Dokumenten: Kommentare können zu Daisy Dokumenten hinzugefügt werden. Genauer gesagt werden sie tatsächlich zu einer bestimmten Variante eines Dokuments hinzugefügt. Von daher besitzt auch jede Variante eines Dokuments ihre eigenen Kommentare. Eigenschaft... | SimpleDocument | daisydocs | daisydocs-2_0 | de | bruno | show |
| Kommentare zu Dokumenten | Dieser Abschnitt behandelt Kommentare zu Dokumenten: Kommentare können zu Daisy Dokumenten hinzugefügt werden. Genauer gesagt werden sie tatsächlich zu einer bestimmten Variante eines Dokuments hinzugefügt. Von daher besitzt auch jede Variante eines Dokuments ihre eigenen Kommentare. Eigenschaft... | SimpleDocument | daisydocs | daisydocs-2_1 | de | bruno | show |
| Kommentare zu Dokumenten | Dieser Abschnitt behandelt Kommentare zu Dokumenten: Kommentare können zu Daisy Dokumenten hinzugefügt werden. Genauer gesagt werden sie tatsächlich zu einer bestimmten Variante eines Dokuments hinzugefügt. Von daher besitzt auch jede Variante eines Dokuments ihre eigenen Kommentare. Eigenschaft... | SimpleDocument | daisydocs | daisydocs-2_2 | de | bruno | show |
| Language-independent content | Keywords: language-independent content (fields, parts), cross-language fields, language-variant-scoped fields This document is about the problem of how to take care of document content (mostly fields, but could be parts) that need to be the same for all language variants. Writing down the proble... | DaisyCommWikiDocument | daisywiki | main | en | bruno | show |
| Language variant | Each Daisy document can exist in multiple language variants. Each variant typically contains the same content, but in a different language. The various language variants of a document are all identified by the same document ID. See variants. | GlossaryEntry | daisydocs | daisydocs-2_2 | en | bruno | show |
| Language variant | Each Daisy document can exist in multiple language variants. Each variant typically contains the same content, but in a different language. The various language variants of a document are all identified by the same document ID. See variants. | GlossaryEntry | daisydocs | daisydocs-2_3 | en | bruno | show |
| Large repositories | If you have more than 10 000 documents in your Daisy repository, it is recommended to enlarge the document cache size in order to keep good performance. Ideally, the cache should be as large as the number of documents (or the set of frequently accessed documents thereof) . To configure the docum... | SimpleDocument | daisydocs | daisydocs-2_1 | en | bruno | show |
| Large repositories | If you have more than 10 000 documents in your Daisy repository, it is recommended to enlarge the document cache size in order to keep good performance. Ideally, the cache should be as large as the number of documents (or the set of frequently accessed documents thereof) . To configure the docum... | SimpleDocument | daisydocs | daisydocs-2_2 | en | bruno | show |
| Large repositories | If you have more than 10 000 documents in your Daisy repository, it is recommended to enlarge the document cache size in order to keep good performance. Ideally, the cache should be as large as the number of documents (or the set of frequently accessed documents thereof) . To configure the docum... | SimpleDocument | daisydocs | daisydocs-2_3 | en | bruno | show |
| Launcher | The purpose of the launcher is to easily start the repository server without the need to add all the required implementation jars to the classpath of your project. When using the launcher, you only need the launcher jar on the classpath, and the launcher will then construct a classloader contain... | SimpleDocument | daisydocs | daisydocs-2_1 | en | bruno | show |
| Launcher | The purpose of the launcher is to easily start the repository server without the need to add all the required implementation jars to the classpath of your project. When using the launcher, you only need the launcher jar on the classpath, and the launcher will then construct a classloader contain... | SimpleDocument | daisydocs | daisydocs-2_2 | en | bruno | show |
| Launcher | The purpose of the launcher is to easily start the repository server without the need to add all the required implementation jars to the classpath of your project. When using the launcher, you only need the launcher jar on the classpath, and the launcher will then construct a classloader contain... | SimpleDocument | daisydocs | daisydocs-2_3 | en | bruno | show |
| layout.xsl input XML specification | This is the layout.xsl input contract. <page> <!-- The context element is usually produced by the PageContext class (but the layout.xsl doesn't care about this of course) --> <context> <!-- The mountPoint is everything of the URI path that comes before the part matched by the Daisy sitemap. By d... | SimpleDocument | daisydocs | daisydocs-1_3 | en | bruno | show |
| layout.xsl input XML specification | This is the layout.xsl input contract. <page> <!-- The context element is usually produced by the PageContext class (but the layout.xsl doesn't care about this of course) --> <context> <!-- The mountPoint is everything of the URI path that comes before the part matched by the Daisy sitemap. By d... | SimpleDocument | daisydocs | daisydocs-1_4 | en | bruno | show |
| layout.xsl input XML specification | This is the layout.xsl input contract. <page> <!-- The context element is usually produced by the PageContext class (but the layout.xsl doesn't care about this of course) --> <context> <!-- Information about the Daisy Wiki version --> <versionInfo version="..." buildHostName="..." buildDateTime=... | SimpleDocument | daisydocs | daisydocs-1_5 | en | bruno | show |
| layout.xsl input XML specification | This is the layout.xsl input contract. <page> <!-- The context element is usually produced by the PageContext class (but the layout.xsl doesn't care about this of course) --> <context> <!-- Information about the Daisy Wiki version --> <versionInfo version="..." buildHostName="..." buildDateTime=... | SimpleDocument | daisydocs | daisydocs-2_0 | en | bruno | show |
| layout.xsl input XML specification | This is the layout.xsl input contract. <page> <!-- The context element is usually produced by the PageContext class (but the layout.xsl doesn't care about this of course) --> <context> <!-- Information about the Daisy Wiki version --> <versionInfo version="..." buildHostName="..." buildDateTime=... | SimpleDocument | daisydocs | daisydocs-2_1 | en | bruno | show |
| layout.xsl input XML specification | This is the layout.xsl input contract. <page> <!-- The context element is usually produced by the PageContext class (but the layout.xsl doesn't care about this of course) --> <context> <!-- Information about the Daisy Wiki version --> <versionInfo version="..." buildHostName="..." buildDateTime=... | SimpleDocument | daisydocs | daisydocs-2_2 | en | bruno | show |
| layout.xsl input XML specification | This is the layout.xsl input contract. <page> <!-- The context element is usually produced by the PageContext class (but the layout.xsl doesn't care about this of course) --> <context> <!-- Information about the Daisy Wiki version --> <versionInfo version="..." buildHostName="..." buildDateTime=... | SimpleDocument | daisydocs | daisydocs-2_3 | en | bruno | show |
| License | The xReporter License, based on the Apache Software License 1.1 Copyright (C) 2002 Outerthought bvba and Schaubroeck nv. All rights reserved. Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: 1. Redistr... | SimpleDocument | xreporter | main | en | stevenn | show |
| License | The GroupingTransformer License, based on the Apache Software License 1.1 Copyright (C) 2003 Outerthought bvba. All rights reserved. Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: 1. Redistributions o... | SimpleDocument | xreporter | main | en | stevenn | show |
| Link rewriter | The problem For linking to some kinds of resources, it would be nice if we had a shortcut mechanism so that we don't have to use the full URL. An example will help understand what I mean. Suppose you want to link to issues in Daisy's issue database. You could do this by using the full URL to the... | DaisyCommWikiDocument | daisywiki | main | en | bruno | show |
| Link transformation | This section is about the transformation of links in the Daisy Wiki from "daisy:" to the public URL space. Format of the links It might be good to review the format of the links first. The structure of a Daisy link is: daisy:docid@branch:language:version#fragmentid The branch, language and versi... | SimpleDocument | daisydocs | daisydocs-1_5 | en | bruno | show |
| Link transformation | This section is about the transformation of links in the Daisy Wiki from "daisy:" to the public URL space. Format of the links It might be good to review the format of the links first. The structure of a Daisy link is: daisy:docid@branch:language:version#fragmentid The branch, language and versi... | SimpleDocument | daisydocs | daisydocs-2_0 | en | bruno | show |
| Link transformation | This section is about the transformation of links in the Daisy Wiki from "daisy:" to the public URL space. Format of the links It might be good to review the format of the links first. The structure of a Daisy link is: daisy:docid@branch:language:version#fragmentid The branch, language and versi... | SimpleDocument | daisydocs | daisydocs-2_1 | en | bruno | show |
| Link transformation | This section is about the transformation of links in the Daisy Wiki from "daisy:" to the public URL space. Format of the links It might be good to review the format of the links first. The structure of a Daisy link is: daisy:docid@branch:language:version#fragmentid The branch, language and versi... | SimpleDocument | daisydocs | daisydocs-2_2 | en | bruno | show |
| Link transformation | This section is about the transformation of links in the Daisy Wiki from "daisy:" to the public URL space. Format of the links It might be good to review the format of the links first. The structure of a Daisy link is: daisy:docid@branch:language:version#fragmentid The branch, language and versi... | SimpleDocument | daisydocs | daisydocs-2_3 | en | bruno | show |
| Live and staging view | By default, the Daisy Wiki shows the live version of each document, if you want to see other versions you need to explicitly go look at them. The live/staging switch allows to make that the last version of each document is displayed by default. Or from another point of view, it shows how the Wik... | SimpleDocument | daisydocs | daisydocs-1_5 | en | bruno | show |
| Live and staging view | By default, the Daisy Wiki shows the live version of each document, if you want to see other versions you need to explicitly go look at them. The live/staging switch allows to make that the last version of each document is displayed by default. Or from another point of view, it shows how the Wik... | SimpleDocument | daisydocs | daisydocs-2_0 | en | bruno | show |
| Live and staging view | By default, the Daisy Wiki shows the live version of each document, if you want to see other versions you need to explicitly go look at them. The live/staging switch allows to make that the last version of each document is displayed by default. Or from another point of view, it shows how the Wik... | SimpleDocument | daisydocs | daisydocs-2_1 | en | bruno | show |
| Live and staging view | By default, the Daisy Wiki shows the live version of each document, if you want to see other versions you need to explicitly go look at them. The live/staging switch allows to make that the last version of each document is displayed by default. Or from another point of view, it shows how the Wik... | SimpleDocument | daisydocs | daisydocs-2_2 | en | bruno | show |
| Live and staging view | By default, the Daisy Wiki shows the live version of each document, if you want to see other versions you need to explicitly go look at them. The live/staging switch allows to make that the last version of each document is displayed by default. Or from another point of view, it shows how the Wik... | SimpleDocument | daisydocs | daisydocs-2_3 | en | bruno | show |
| Live sites | Daisy's own website runs on a live Daisy instance. Daisy is in use by many companies and organisations, often as an internal knowledge management tool. Below some cases are listed of public sites that we are aware of. Screenshot Info Intergator A website using Daisy on the backend, ... | DaisyCommWikiDocument | daisywiki | main | en | bruno | show |
| Live version | The live version of a document is its most recent version whose version state is publish. | GlossaryEntry | daisydocs | daisydocs-2_2 | en | bruno | show |
| Live version | The live version of a document is its most recent version whose version state is publish. | GlossaryEntry | daisydocs | daisydocs-2_3 | en | bruno | show |
| Log files | The log files of daisy are by default created in the following directory: $DATADIR/logs The log files rol over daily. You will probably want to regularly delete old log files, for example using a cron job. The logging configuration can be adjusted in the following file: $DATADIR/conf/logkit.xml... | SimpleDocument | daisydocs | daisydocs-1_2 | en | bruno | show |
| Log files | The log files of daisy are by default created in the following directory: $DATADIR/logs The log files rol over daily. You will probably want to regularly delete old log files, for example using a cron job. The logging configuration can be adjusted in the following file: $DATADIR/conf/logkit.xml... | SimpleDocument | daisydocs | daisydocs-1_3 | en | bruno | show |
| Log files | The log files of daisy are by default created in the following directory: $DATADIR/logs The log files rol over daily. You will probably want to regularly delete old log files, for example using a cron job. The logging configuration can be adjusted in the following file: $DATADIR/conf/logkit.xml... | SimpleDocument | daisydocs | daisydocs-1_4 | en | bruno | show |
| Log files | Repository server The log files of the repository server are by default created in the following directory: <daisydata directory>/logs The log files rol over daily. You will probably want to regularly delete old log files, for example using a cron job. The logging configuration can be adjusted ... | SimpleDocument | daisydocs | daisydocs-1_5 | en | bruno | show |
| Log files | Repository server The log files of the repository server are by default created in the following directory: <daisydata directory>/logs The log files rol over daily. You will probably want to regularly delete old log files, for example using a cron job. The logging configuration can be adjusted ... | SimpleDocument | daisydocs | daisydocs-2_0 | en | bruno | show |
| Log files | Repository server The log files of the repository server are by default created in the following directory: <daisydata directory>/logs The log files rol over daily. You will probably want to regularly delete old log files, for example using a cron job. The logging configuration can be adjusted i... | SimpleDocument | daisydocs | daisydocs-2_1 | en | bruno | show |
| Log files | Repository server The log files of the repository server are by default created in the following directory: <daisydata directory>/logs The log files rol over daily. You will probably want to regularly delete old log files, for example using a cron job. The logging configuration can be adjusted i... | SimpleDocument | daisydocs | daisydocs-2_2 | en | bruno | show |
| Log files | Repository server The log files of the repository server are by default created in the following directory: <daisydata directory>/logs The log files rol over daily. You will probably want to regularly delete old log files, for example using a cron job. The logging configuration can be adjusted i... | SimpleDocument | daisydocs | daisydocs-2_3 | en | bruno | show |
| Logging | This document provides information about the xReporter log files. The logfiles can be found in the directory phoenix/apps/xreporter/logs. The names of the logfiles consist of a basename followed by a date, followed by the extension ".log". In this document we will refer to the filenames only by ... | SimpleDocument | xreporter | main | en | stevenn | show |
| Logging | Logging API In the repository server all logging is performed using the commons-logging API. It is then up to the environment in which the repository server is started to set up a concrete logging implementation. In the Daisy Runtime CLI we replaced the commons-logging API by its clone jcl-over... | SimpleDocument | daisydocs | daisydocs-2_1 | en | bruno | show |
| Logging | Logging API In the repository server all logging is performed using the commons-logging API. It is then up to the environment in which the repository server is started to set up a concrete logging implementation. In the Daisy Runtime CLI we replaced the commons-logging API by its clone jcl-over... | SimpleDocument | daisydocs | daisydocs-2_2 | en | bruno | show |
| Logging | Logging API In the repository server all logging is performed using the commons-logging API. It is then up to the environment in which the repository server is started to set up a concrete logging implementation. In the Daisy Runtime CLI we replaced the commons-logging API by its clone jcl-over... | SimpleDocument | daisydocs | daisydocs-2_3 | en | bruno | show |
| logo outerthought | | Image | daisy | main | en | stevenn | show |
| logo schaubroeck | | Image | daisy | main | en | stevenn | show |
| Maintaining change logs | (for committers) When committing a feature change, make sure to mention it on the changes page for the current release (which is part of the documentation of that release). Same holds for commits which involve backwards incompatible changes or changes that require special action when updating. W... | SimpleDocument | daisydocs | daisydocs-2_1 | en | bruno | show |
| Maintaining change logs | (for committers) When committing a feature change, make sure to mention it on the changes page for the current release (which is part of the documentation of that release). Same holds for commits which involve backwards incompatible changes or changes that require special action when updating. W... | SimpleDocument | daisydocs | daisydocs-2_2 | en | bruno | show |
| Maintaining change logs | (for committers) When committing a feature change, make sure to mention it on the changes page for the current release (which is part of the documentation of that release). Same holds for commits which involve backwards incompatible changes or changes that require special action when updating. W... | SimpleDocument | daisydocs | daisydocs-2_3 | en | bruno | show |
| Making backups | Introduction For backing up Daisy there is an application which will help you create and restore backups. You can find it in <DAISY_HOME>/bin/daisy-backup-tool This tool in its current form can backup : daisy-repository repository database blobstore indexstore configuration openjms database... | SimpleDocument | daisydocs | daisydocs-1_4 | en | bruno | show |
| Making backups | Introduction For backing up Daisy there is an application which will help you create and restore backups. You can find it in <DAISY_HOME>/bin/daisy-backup-tool This tool in its current form can backup : daisy-repository repository database blobstore indexstore configuration activemq database... | SimpleDocument | daisydocs | daisydocs-1_5 | en | bruno | show |
| Making backups | Introduction For backing up Daisy there is an application which will help you create and restore backups. You can find it in <DAISY_HOME>/bin/daisy-backup-tool This tool in its current form can backup : daisy-repository repository database blobstore indexstore configuration activemq database... | SimpleDocument | daisydocs | daisydocs-2_0 | en | bruno | show |
| Making backups | Introduction For backing up Daisy there is an application which will help you create and restore backups. You can find it in <DAISY_HOME>/bin/daisy-backup-tool This tool in its current form can backup : daisy-repository repository database blobstore indexstore configuration activemq database ... | SimpleDocument | daisydocs | daisydocs-2_1 | en | bruno | show |
| Making backups | Introduction For backing up Daisy there is an application which will help you create and restore backups. You can find it in <DAISY_HOME>/bin/daisy-backup-tool This tool in its current form can backup : daisy-repository repository database blobstore indexstore configuration activemq database ... | SimpleDocument | daisydocs | daisydocs-2_2 | en | bruno | show |
| Making backups | Introduction For backing up Daisy there is an application which will help you create and restore backups. You can find it in <DAISY_HOME>/bin/daisy-backup-tool This tool in its current form can backup : daisy-repository repository database blobstore indexstore configuration activemq database ... | SimpleDocument | daisydocs | daisydocs-2_3 | en | bruno | show |
| Memory configuration | xReporter runs in a Java Virtual Machine (JVM). The JVM has a limit to the amount of memory it can allocate. The default limit can be too low when working with large result sets in xReporter. Here is how you can change these limits. xReporter server (Phoenix) Before starting Phoenix, set the PH... | SimpleDocument | xreporter | main | en | bruno | show |
| Merlin | Our look at the repository should start with mentioning Merlin. Merlin is the component runtime platform that hosts the repository server. Merlin is an inversion of control (IoC) style container, which means that the container gives components everything they need (configuration, handles to othe... | SimpleDocument | daisydocs | daisydocs-1_2 | en | bruno | show |
| Merlin | Our look at the repository should start with mentioning Merlin. Merlin is the component runtime platform that hosts the repository server. Merlin is an inversion of control (IoC) style container, which means that the container gives components everything they need (configuration, handles to othe... | SimpleDocument | daisydocs | daisydocs-1_3 | en | bruno | show |
| Merlin | Our look at the repository should start with mentioning Merlin. Merlin is the component runtime platform that hosts the repository server. Merlin is an inversion of control (IoC) style container, which means that the container gives components everything they need (configuration, handles to othe... | SimpleDocument | daisydocs | daisydocs-1_4 | en | bruno | show |
| Merlin | Our look at the repository should start with mentioning Merlin. Merlin is the component runtime platform that hosts the repository server. Merlin is an inversion of control (IoC) style container, which means that the container gives components everything they need (configuration, handles to othe... | SimpleDocument | daisydocs | daisydocs-1_5 | en | bruno | show |
| Merlin | Our look at the repository should start with mentioning Merlin. Merlin is the component runtime platform that hosts the repository server. Merlin is an inversion of control (IoC) style container, which means that the container gives components everything they need (configuration, handles to othe... | SimpleDocument | daisydocs | daisydocs-2_0 | en | bruno | show |
| Miscellaneous | | KnowledgeBaseCategory | daisykb | main | en | bruno | show |
| Miscellaneous ideas | Ajax enhanced authoring environment (should be more then just graphical effects though) possibly evolving into a pure browser direct repository-client (which would involve bypassing much of the cocoon-side logic) Spellchecker support (on client and maybe even on server: JMS process listening to... | DaisyCommWikiDocument | daisywiki | main | en | bruno | show |
| Mounting sites at arbitrary URL paths | Description and goals Allows sites to be mapped at arbitrary URL paths instead of the current fixed structure (/sitename), e.g. just "/" or "/abc/def/ghi". Details There will be a configuration file which defines the mapping The current "*/**" matcher in the sitemap will be replaced by somethin... | DaisyCommWikiDocument | daisywiki | main | en | stevenn | show |
| Moving a Daisy install from one computer to another | This document primarily addresses older versions of daisy. As of daisy release 1.5-M2, the need to have absolute paths in the myconfig.xml by was removed through the introduction property substitutions, such as ${daisy.datadir} and ${daisy.home}. The repository initialisation script now generate... | DaisyCommWikiDocument | daisywiki | main | en | tom | show |
| Multi-language setup | Introduction Here we will describe the recommended approach for setting up Daisy when making use of language variants. If you are setting up an initial system, you can use the quick setup using daisy-wiki-add-site. If you like to do things yourself or you have an existing document collection in ... | SimpleDocument | daisydocs | daisydocs-2_2 | en | bruno | show |
| Multi-language setup | Introduction Here we will describe the recommended approach for setting up Daisy when making use of language variants. If you are setting up an initial system, you can use the quick setup using daisy-wiki-add-site. If you like to do things yourself or you have an existing document collection in ... | SimpleDocument | daisydocs | daisydocs-2_3 | en | bruno | show |
| Multi-language support | Introduction Documents in Daisy can exist in multiple variants. There are two types of variants: branches and languages. Different document variants are technically pretty much like different documents, but they are identified by the same document ID, thus giving a logical grouping. While on a b... | DaisyCommWikiDocument | daisywiki | main | en | bruno | show |
| Multi-language support | Introduction This section of the documentation is intended to provide an introduction to the Daisy features for managing multi-lingual content, both of the repository and the front-end. Multi-lingual content can take many forms. Two major categories are: you have a set of documents, some of wh... | SimpleDocument | daisydocs | daisydocs-2_2 | en | bruno | show |
| Multi-language support | Introduction This section of the documentation is intended to provide an introduction to the Daisy features for managing multi-lingual content, both of the repository and the front-end. Multi-lingual content can take many forms. Two major categories are: you have a set of documents, some of wh... | SimpleDocument | daisydocs | daisydocs-2_3 | en | bruno | show |
| Multiple namespace management | Concept Let one repository manage multiple namespaces. Tasks Instead of only one, allow multiple repository-managed namespaces = namespaces for which the repository manages the document ID counter. Let administrators decide per documentType what the default namespace is. Configuration is done ... | DaisyCommWikiDocument | daisywiki | main | en | karel | show |
| multivalue-widget | | Image | daisywiki | main | en | karel | show |
| multivalue-widget | | Image | daisywiki | main | en | karel | show |
| multivalue-widget | | Image | daisywiki | main | en | karel | show |
| myconfig.xml | The configuration file of the repository server. The file can be found in the repository data directory at conf/myconfig.xml. The programmer's explanation can be found in Component configuration. | GlossaryEntry | daisydocs | daisydocs-2_1 | en | bruno | show |
| myconfig.xml | The configuration file of the repository server. The file can be found in the repository data directory at conf/myconfig.xml. The programmer's explanation can be found in Component configuration. | GlossaryEntry | daisydocs | daisydocs-2_2 | en | bruno | show |
| myconfig.xml | The configuration file of the repository server. The file can be found in the repository data directory at conf/myconfig.xml. The programmer's explanation can be found in Component configuration. | GlossaryEntry | daisydocs | daisydocs-2_3 | en | bruno | show |
| Navigation | Overview Daisy allows to create hierarchical navigation trees for your site. Some of the features and possibilities: navigation trees are dynamically generated for the current user and the current document. Documents for which the user has no read access are removed from the navigation tree, as... | SimpleDocument | daisy | daisydocs-1_2 | en | bruno | show |
| Navigation | Overview Daisy allows to create hierarchical navigation trees for your site. Some of the features and possibilities: navigation trees are dynamically generated for the current user and the current document. Documents for which the user has no read access are removed from the navigation tree, as... | SimpleDocument | daisydocs | daisydocs-1_3 | en | bruno | show |
| Navigation | Overview Daisy allows to create hierarchical navigation trees for your site. Some of the features and possibilities: navigation trees are dynamically generated for the current user and the current document. Documents for which the user has no read access are removed from the navigation tree, as... | SimpleDocument | daisydocs | daisydocs-1_4 | en | bruno | show |
| Navigation | Overview Daisy allows to create hierarchical navigation trees for your site. Some of the features and possibilities: navigation trees are dynamically generated for the current user and the current document. Documents for which the user has no "read live" access are removed from the navigation t... | SimpleDocument | daisydocs | daisydocs-1_5 | en | bruno | show |
| Navigation | Overview Daisy allows to create hierarchical navigation trees for your site. Some of the features and possibilities: navigation trees are dynamically generated for the current user and the current document. Documents for which the user has no "read live" access are removed from the navigation ... | SimpleDocument | daisydocs | daisydocs-2_0 | en | bruno | show |
| Navigation | Overview Daisy allows to create hierarchical navigation trees for your site. Some of the features and possibilities: navigation trees are dynamically generated for the current user and the current document. Documents for which the user has no "read live" access are removed from the navigation ... | SimpleDocument | daisydocs | daisydocs-2_1 | en | bruno | show |
| Navigation | Overview Daisy allows to create hierarchical navigation trees for your site. Some of the features and possibilities: navigation trees are dynamically generated for the current user and the current document. Documents for which the user has no read permission are removed from the navigation tre... | SimpleDocument | daisydocs | daisydocs-2_2 | en | bruno | show |
| Navigation | Overview Daisy allows to create hierarchical navigation trees for your site. Some of the features and possibilities: navigation trees are dynamically generated for the current user and the current document. Documents for which the user has no read permission are removed from the navigation tre... | SimpleDocument | daisydocs | daisydocs-2_3 | en | bruno | show |
| Navigation definition to book definition XSLT | | Attachment | daisydocs | daisydocs-1_4 | en | bruno | show |
| Navigation definition to book definition XSLT | | Attachment | daisydocs | daisydocs-1_5 | en | bruno | show |
| Navigation definition to book definition XSLT | | Attachment | daisydocs | daisydocs-2_0 | en | bruno | show |
| Navigation definition to book definition XSLT | | Attachment | daisydocs | daisydocs-2_1 | en | bruno | show |
| Navigation definition to book definition XSLT | | Attachment | daisydocs | daisydocs-2_2 | en | bruno | show |
| Navigation definition to book definition XSLT | | Attachment | daisydocs | daisydocs-2_3 | en | bruno | show |
| Navigation for daisy | | Navigation | | main | en | stevenn | show |
| Navigation for main | | Navigation | | main | en | stevenn | show |
| Navigation Tree for xReporter website | | Navigation | xreporter | main | en | mpo | show |
| navtree editor | | Image | daisy | main | en | stevenn | show |
| New commenting system | Daisy currently includes a very simple system to add comments to documents. There is lot of room for enhancement here. Some ideas: allow to associate/attach comments with parts of the documents (e.g. individual paragraphs or headers). For a nice example, see here. allow threaded comments allow ... | DaisyCommWikiDocument | daisywiki | main | en | bruno | show |
| New document browser | Concept A rewrite(?) of the existing document browser with some new features: chunking sorting more search possiblities: facet browsing predefined filters lookup of related WFs and possible transitions in the various tasks (?) multi-document-selection (useful for making multi-value daisy-link... | DaisyCommWikiDocument | daisywiki | main | en | karel | show |
| News | Releases Version Release date Changes Announcements 2.2 2008-03-09 changes 2.1 2007-08-31 changes press release 2.0.1 2007-04-12 changes 2.0 2007-04-03 changes 1.5.1 2006-09-22 changes 1.5 2006-08-16 changes press release 1.4.1 2006-02-17 ... | SimpleDocument | daisy | main | en | stevenn | show |
| nexusalpha screenshot | | Image | daisywiki | main | en | bruno | show |
| non-rendered svg document | | Image | daisywiki | main | en | bruno | show |
| Notes on Content Management Systems, particularly Daisy | General notes about Content Management Systems, with a few reasons to choose Daisy out of the myriad of CMS choices. http://geekscape.org/daisy/geekscape/110.html -- Andy: 2005-12-06 | DaisyCommWikiDocument | daisywiki | main | en | geekscape | show |
| Notes on JPDL authoring | Special considerations for workflows to be deployed in Daisy Process definition verification When deploying a process definition in Daisy, Daisy applies some stricter checking on the process definition than jBPM does, more specifically: it checks the process definition has a name it checks t... | SimpleDocument | daisydocs | daisydocs-2_0 | en | bruno | show |
| Notes on JPDL authoring | Special considerations for workflows to be deployed in Daisy Process definition verification When deploying a process definition in Daisy, Daisy applies some stricter checking on the process definition than jBPM does, more specifically: it checks the process definition has a name it checks t... | SimpleDocument | daisydocs | daisydocs-2_1 | en | bruno | show |
| Notes on JPDL authoring | Special considerations for workflows to be deployed in Daisy Process definition verification When deploying a process definition in Daisy, Daisy applies some stricter checking on the process definition than jBPM does, more specifically: it checks the process definition has a name it checks t... | SimpleDocument | daisydocs | daisydocs-2_2 | en | bruno | show |
| Notes on JPDL authoring | Special considerations for workflows to be deployed in Daisy Process definition verification When deploying a process definition in Daisy, Daisy applies some stricter checking on the process definition than jBPM does, more specifically: it checks the process definition has a name it checks t... | SimpleDocument | daisydocs | daisydocs-2_3 | en | bruno | show |
| ntlm-group-auth | | Attachment | daisywiki | main | en | timmcd | show |
| oaais | | Image | daisywiki | main | en | bruno | show |
| ODF Integration | The Open Document Format is gaining much attention and a growing momentum in the (non Microsoft part of the) industry. Of course, by virtue of the integrated Apache Lucene, we are already properly indexing these files, but more could be done. With the 2.x release of OpenOffice as the de facto ... | DaisyCommWikiDocument | daisywiki | main | en | bruno | show |
| open_detachment | | Image | daisywiki | main | en | tim | show |
| Othello | Introduction Template based web site. Website An old version is live at http://othello.osmosis.gr Live sites Cafe bar KYVERNEIO (http://www.kyverneio.gr) DAIHATSU Agent (http://www.karanikolaou.gr) Milk Industry of Xanthi S.A "RODOPI (http://www.rodopi-sa.gr) Project resources Mailing list: h... | SimpleDocument | main | main | en | stevenn | show |
| Other | | FAQCategory | daisydocs | daisydocs-2_0 | en | bruno | show |
| Other | | FAQCategory | daisydocs | daisydocs-2_1 | en | bruno | show |
| Other | | FAQCategory | daisydocs | daisydocs-2_2 | en | bruno | show |
| Other | | FAQCategory | daisydocs | daisydocs-2_3 | en | bruno | show |
| outerthought skin | | Image | xreporter | main | en | stevenn | show |
| Overview | Certain functionality of xReporter is reusable outside the context of the xReporter server itself. This page will contain those as subprojects. Feedback about any of the projects listed below is welcome on the xReporter mailing list. GroupingTransformer A Cocoon transformer that can perform grou... | SimpleDocument | xreporter | main | en | stevenn | show |
| Overview | This document provides a quick overview of the main facts about xReporter. Purpose The goal of xReporter is web-based, read-only consultation of databases. The user can choose from a set of predefined reports. Reports can be created without any programming (though you'll need SQL knowledge). An... | SimpleDocument | xreporter | main | en | stevenn | show |
| Overview | History Up to xReporter 1.2.1, a report had a fixed number of output formats: HTML, XML, PDF, CSV and Excel. These output formats were customizable through report-specific styling. It was not possible to add new formats or multiple variations of the same format. Since xReporter 1.3, a system is ... | SimpleDocument | xreporter | main | en | bruno | show |
| p:aclInfo | Returns the result of evaluating the current context document against the ACL. Request This request requires no attributes, so its syntax is simply: <p:aclInfo/> Response The response is a d:aclResultInfo element. | PublisherRequest | daisydocs | daisydocs-2_1 | en | bruno | show |
| p:aclInfo | Returns the result of evaluating the current context document against the ACL. Request This request requires no attributes, so its syntax is simply: <p:aclInfo/> Response The response is a d:aclResultInfo element. | PublisherRequest | daisydocs | daisydocs-2_2 | en | bruno | show |
| p:aclInfo | Returns the result of evaluating the current context document against the ACL. Request This request requires no attributes, so its syntax is simply: <p:aclInfo/> Response The response is a d:aclResultInfo element. | PublisherRequest | daisydocs | daisydocs-2_3 | en | bruno | show |
| p:annotatedDocument | Returns the XML representation of the current document with some annotations. The annotations include things like the name and label of the document type, display names for users, branch and language name (for all these things, otherwise only the numeric IDs would be present), and annotations to... | PublisherRequest | daisydocs | daisydocs-2_1 | en | bruno | show |
| p:annotatedDocument | Returns the XML representation of the current document with some annotations. The annotations include things like the name and label of the document type, display names for users, branch and language name (for all these things, otherwise only the numeric IDs would be present), and annotations to... | PublisherRequest | daisydocs | daisydocs-2_2 | en | bruno | show |
| p:annotatedDocument | Returns the XML representation of the current document with some annotations. The annotations include things like the name and label of the document type, display names for users, branch and language name (for all these things, otherwise only the numeric IDs would be present), and annotations to... | PublisherRequest | daisydocs | daisydocs-2_3 | en | bruno | show |
| p:annotatedVersionList | Returns a list of all versions of the document, with some annotations on top of the default XML representation of a version list. Request Syntax: <p:annotatedVersionList/> Response A d:versions element. | PublisherRequest | daisydocs | daisydocs-2_1 | en | bruno | show |
| p:annotatedVersionList | Returns a list of all versions of the document, with some annotations on top of the default XML representation of a version list. Request Syntax: <p:annotatedVersionList/> Response A d:versions element. | PublisherRequest | daisydocs | daisydocs-2_2 | en | bruno | show |
| p:annotatedVersionList | Returns a list of all versions of the document, with some annotations on top of the default XML representation of a version list. Request Syntax: <p:annotatedVersionList/> Response A d:versions element. | PublisherRequest | daisydocs | daisydocs-2_3 | en | bruno | show |
| p:availableVariants | Returns the available variants for the current context document. Request Syntax: <p:availableVariants/> Response A d:availableVariants element. | PublisherRequest | daisydocs | daisydocs-2_1 | en | bruno | show |
| p:availableVariants | Returns the available variants for the current context document. Request Syntax: <p:availableVariants/> Response A d:availableVariants element. | PublisherRequest | daisydocs | daisydocs-2_2 | en | bruno | show |
| p:availableVariants | Returns the available variants for the current context document. Request Syntax: <p:availableVariants/> Response A d:availableVariants element. | PublisherRequest | daisydocs | daisydocs-2_3 | en | bruno | show |
| p:choose | Allows to execute one among of a number of possible alternatives. Request Syntax: <p:choose> <p:when test="..."> [... any publisher instruction ...] </p:when> [... more p:when's ...] <p:otherwise> [... any publisher instruction ...] </p:otherwise> </p:choose> There should be at least one p:when,... | PublisherRequest | daisydocs | daisydocs-2_1 | en | bruno | show |
| p:choose | Allows to execute one among of a number of possible alternatives. Request Syntax: <p:choose> <p:when test="..."> [... any publisher instruction ...] </p:when> [... more p:when's ...] <p:otherwise> [... any publisher instruction ...] </p:otherwise> </p:choose> There should be at least one p:when,... | PublisherRequest | daisydocs | daisydocs-2_2 | en | bruno | show |
| p:choose | Allows to execute one among of a number of possible alternatives. Request Syntax: <p:choose> <p:when test="..."> [... any publisher instruction ...] </p:when> [... more p:when's ...] <p:otherwise> [... any publisher instruction ...] </p:otherwise> </p:choose> There should be at least one p:when,... | PublisherRequest | daisydocs | daisydocs-2_3 | en | bruno | show |
| p:comments | Returns the comments for the current context document. Request Syntax: <p:comments/> Response A d:comments element. The newlines in the comments will be replaced with <br/> tags. | PublisherRequest | daisydocs | daisydocs-2_1 | en | bruno | show |
| p:comments | Returns the comments for the current context document. Request Syntax: <p:comments/> Response A d:comments element. The newlines in the comments will be replaced with <br/> tags. | PublisherRequest | daisydocs | daisydocs-2_2 | en | bruno | show |
| p:comments | Returns the comments for the current context document. Request Syntax: <p:comments/> Response A d:comments element. The newlines in the comments will be replaced with <br/> tags. | PublisherRequest | daisydocs | daisydocs-2_3 | en | bruno | show |
| p:diff | Returns a diff of the current context document/version with another version of this document or another document. Request Syntax: <p:diff contentDiffType="text|html|htmlsource"> <p:otherDocument id="expr" branch="expr" language="expr" version="expr"/> </p:diff> If no p:otherDocument element is s... | PublisherRequest | daisydocs | daisydocs-2_1 | en | bruno | show |
| p:diff | Returns a diff of the current context document/version with another version of this document or another document. Request Syntax: <p:diff contentDiffType="text|html|htmlsource"> <p:otherDocument id="expr" branch="expr" language="expr" version="expr"/> </p:diff> If no p:otherDocument element is s... | PublisherRequest | daisydocs | daisydocs-2_2 | en | bruno | show |
| p:diff | Returns a diff of the current context document/version with another version of this document or another document. Request Syntax: <p:diff contentDiffType="text|html|htmlsource"> <p:otherDocument id="expr" branch="expr" language="expr" version="expr"/> </p:diff> If no p:otherDocument element is s... | PublisherRequest | daisydocs | daisydocs-2_3 | en | bruno | show |
| p:document | A p:document request is push a document on the context document stack, and thus to change the currently active context document. The context document is the document on which the document related requests apply. Request Any publisher request element can be nested within p:document. The p:documen... | PublisherRequest | daisydocs | daisydocs-2_1 | en | bruno | show |
| p:document | A p:document request is push a document on the context document stack, and thus to change the currently active context document. The context document is the document on which the document related requests apply. Request Any publisher request element can be nested within p:document. The p:documen... | PublisherRequest | daisydocs | daisydocs-2_2 | en | bruno | show |
| p:document | A p:document request is push a document on the context document stack, and thus to change the currently active context document. The context document is the document on which the document related requests apply. Request Any publisher request element can be nested within p:document. The p:documen... | PublisherRequest | daisydocs | daisydocs-2_3 | en | bruno | show |
| p:documentType | Returns the documentType of the current context document. Request This request requires no attributes, so its syntax is simply: <p:documentType/> Response The response is a d:documentType element. | PublisherRequest | daisydocs | daisydocs-2_3 | en | karel | show |
| p:forEach | Executes publisher instructions for each document in a list of documents. The list of documents on which to operate can either result from a query or an expression. Request Query Syntax: <p:forEach useLastVersion="true|false"> <p:query>select ... where ... order by ...</p:query> <p:document> [ .... | PublisherRequest | daisydocs | daisydocs-2_1 | en | bruno | show |
| p:forEach | Executes publisher instructions for each document in a list of documents. The list of documents on which to operate can either result from a query or an expression. Request Query Syntax: <p:forEach useLastVersion="true|false"> <p:query>select ... where ... order by ...</p:query> <p:document> [ .... | PublisherRequest | daisydocs | daisydocs-2_2 | en | bruno | show |
| p:forEach | Executes publisher instructions for each document in a list of documents. The list of documents on which to operate can either result from a query or an expression. Request Query Syntax: <p:forEach useLastVersion="true|false"> <p:query>select ... where ... order by ...</p:query> <p:document> [ .... | PublisherRequest | daisydocs | daisydocs-2_3 | en | bruno | show |
| p:group | The p:group element acts as a container for other instructions. It allows to distinguish between e.g. different queries or navigation tree results if you would have more than one of them. Request Syntax: <p:group id="expr" catchErrors="true|false"> [... child instructions ...] </p:group> The id ... | PublisherRequest | daisydocs | daisydocs-2_1 | en | bruno | show |
| p:group | The p:group element acts as a container for other instructions. It allows to distinguish between e.g. different queries or navigation tree results if you would have more than one of them. Request Syntax: <p:group id="expr" catchErrors="true|false"> [... child instructions ...] </p:group> The id ... | PublisherRequest | daisydocs | daisydocs-2_2 | en | bruno | show |
| p:group | The p:group element acts as a container for other instructions. It allows to distinguish between e.g. different queries or navigation tree results if you would have more than one of them. Request Syntax: <p:group id="expr" catchErrors="true|false"> [... child instructions ...] </p:group> The id ... | PublisherRequest | daisydocs | daisydocs-2_3 | en | bruno | show |
| p:ids | Returns the list of all values of the id attributes occurring in the Daisy-HTML parts of the current context document. This can be useful in editors to show the user a list of possible fragment identifier values. Request Syntax: <p:ids/> Response <p:ids> [ zero or more child p:id elements ] <p:i... | PublisherRequest | daisydocs | daisydocs-2_1 | en | bruno | show |
| p:ids | Returns the list of all values of the id attributes occurring in the Daisy-HTML parts of the current context document. This can be useful in editors to show the user a list of possible fragment identifier values. Request Syntax: <p:ids/> Response <p:ids> [ zero or more child p:id elements ] <p:i... | PublisherRequest | daisydocs | daisydocs-2_2 | en | bruno | show |
| p:ids | Returns the list of all values of the id attributes occurring in the Daisy-HTML parts of the current context document. This can be useful in editors to show the user a list of possible fragment identifier values. Request Syntax: <p:ids/> Response <p:ids> [ zero or more child p:id elements ] <p:i... | PublisherRequest | daisydocs | daisydocs-2_3 | en | bruno | show |
| p:if | Allows to execute a part of the publisher request only if a certain test is satisfied. Request Syntax: <p:if test="..."> [... child instructions ...] </p:if> The test attribute specifies a conditional expression (an expression evaluating to true or false) in the same format as used in the Daisy ... | PublisherRequest | daisydocs | daisydocs-2_1 | en | bruno | show |
| p:if | Allows to execute a part of the publisher request only if a certain test is satisfied. Request Syntax: <p:if test="..."> [... child instructions ...] </p:if> The test attribute specifies a conditional expression (an expression evaluating to true or false) in the same format as used in the Daisy ... | PublisherRequest | daisydocs | daisydocs-2_2 | en | bruno | show |
| p:if | Allows to execute a part of the publisher request only if a certain test is satisfied. Request Syntax: <p:if test="..."> [... child instructions ...] </p:if> The test attribute specifies a conditional expression (an expression evaluating to true or false) in the same format as used in the Daisy ... | PublisherRequest | daisydocs | daisydocs-2_3 | en | bruno | show |
| p:myComments | Returns a list of all private comments of the user. Request Syntax: <p:myComments/> Response Same as for p:comments. | PublisherRequest | daisydocs | daisydocs-2_1 | en | bruno | show |
| p:myComments | Returns a list of all private comments of the user. Request Syntax: <p:myComments/> Response Same as for p:comments. | PublisherRequest | daisydocs | daisydocs-2_2 | en | bruno | show |
| p:myComments | Returns a list of all private comments of the user. Request Syntax: <p:myComments/> Response Same as for p:comments. | PublisherRequest | daisydocs | daisydocs-2_3 | en | bruno | show |
| p:navigationTree | Request a navigation tree from the Navigation Manager. Request The full form of this request is: <p:navigationTree> <p:navigationDocument id="expr" branch="expr" language="expr"/> <p:activeDocument id="expr" branch="expr" language="expr"/> <p:activePath>expr</p:activePath> <p:contextualized>true... | PublisherRequest | daisydocs | daisydocs-2_1 | en | bruno | show |
| p:navigationTree | Request a navigation tree from the Navigation Manager. Request The full form of this request is: <p:navigationTree> <p:navigationDocument id="expr" branch="expr" language="expr"/> <p:activeDocument id="expr" branch="expr" language="expr"/> <p:activePath>expr</p:activePath> <p:contextualized>true... | PublisherRequest | daisydocs | daisydocs-2_2 | en | bruno | show |
| p:navigationTree | Request a navigation tree from the Navigation Manager. Request The full form of this request is: <p:navigationTree> <p:navigationDocument id="expr" branch="expr" language="expr"/> <p:activeDocument id="expr" branch="expr" language="expr"/> <p:activePath>expr</p:activePath> <p:contextualized>true... | PublisherRequest | daisydocs | daisydocs-2_3 | en | bruno | show |
| p:performFacetedQuery | Returns the result of executing a query. Request Syntax: <p:performFacetedQuery> <p:options> <p:additionalSelects> <p:expression>name</p:expression> <p:expression>summary</p:expression> </p:additionalSelects> <p:defaultConditions>documentType='SimpleDocument'</p:defaultConditions> <p:defaultSor... | PublisherRequest | daisydocs | daisydocs-2_1 | en | paul | show |
| p:performFacetedQuery | Returns the result of executing a query. Request Syntax: <p:performFacetedQuery> <p:options> <p:additionalSelects> <p:expression>name</p:expression> <p:expression>summary</p:expression> </p:additionalSelects> <p:defaultConditions>documentType='SimpleDocument'</p:defaultConditions> <p:defaultSor... | PublisherRequest | daisydocs | daisydocs-2_2 | en | paul | show |
| p:performFacetedQuery | Returns the result of executing a query. Request Syntax: <p:performFacetedQuery> <p:options> <p:additionalSelects> <p:expression>name</p:expression> <p:expression>summary</p:expression> </p:additionalSelects> <p:defaultConditions>documentType='SimpleDocument'</p:defaultConditions> <p:defaultSor... | PublisherRequest | daisydocs | daisydocs-2_3 | en | paul | show |
| p:performQuery | Returns the result of executing a query. Request Syntax: <p:performQuery> <p:query>select ... where ... order by ...</p:query> [ optional elements: ] <p:extraConditions>...</p:extraConditions> <p:document>...</p:document> </p:performQuery> If there is a context document available (i.e. if this ... | PublisherRequest | daisydocs | daisydocs-2_1 | en | bruno | show |
| p:performQuery | Returns the result of executing a query. Request Syntax: <p:performQuery> <p:query>select ... where ... order by ...</p:query> [ optional elements: ] <p:extraConditions>...</p:extraConditions> <p:document>...</p:document> </p:performQuery> If there is a context document available (i.e. if this ... | PublisherRequest | daisydocs | daisydocs-2_2 | en | bruno | show |
| p:performQuery | Returns the result of executing a query. Request Syntax: <p:performQuery> <p:query>select ... where ... order by ...</p:query> [ optional elements: ] <p:extraConditions>...</p:extraConditions> <p:document>...</p:document> </p:performQuery> If there is a context document available (i.e. if this ... | PublisherRequest | daisydocs | daisydocs-2_3 | en | bruno | show |
| p:performWorkflowQuery | Returns the result of a query on the workflow manager. These results can be process, task or timer instances. Request The syntax is much like a typical workflow query. Here is just a quick overview for a detailed list of options have a look at the workflow query syntax. <p:performWorkflowQuery t... | PublisherRequest | daisydocs | daisydocs-2_3 | en | paul | show |
| p:preparedDocuments (& p:prepareDocument) | p:preparedDocuments is the most powerful of all publisher requests. It returns the content of the document prepared for publishing. The preparation consists of all sorts of things such as: inlining the content of Daisy-HTML parts in the document XML. executing queries and query-includes embedde... | PublisherRequest | daisydocs | daisydocs-2_1 | en | bruno | show |
| p:preparedDocuments (& p:prepareDocument) | p:preparedDocuments is the most powerful of all publisher requests. It returns the content of the document prepared for publishing. The preparation consists of all sorts of things such as: inlining the content of Daisy-HTML parts in the document XML. executing queries and query-includes embedde... | PublisherRequest | daisydocs | daisydocs-2_2 | en | bruno | show |
| p:preparedDocuments (& p:prepareDocument) | p:preparedDocuments is the most powerful of all publisher requests. It returns the content of the document prepared for publishing. The preparation consists of all sorts of things such as: inlining the content of Daisy-HTML parts in the document XML. executing queries and query-includes embedde... | PublisherRequest | daisydocs | daisydocs-2_3 | en | bruno | show |
| p:publisherRequest | p:publisherRequest is the root element of a publisher request document. A basic, empty publisher request is structured as follows: <p:publisherRequest xmlns:p="http://outerx.org/daisy/1.0#publisher" locale="en-US" versionMode="live" exceptions="throw"> [... various publisher requests ...] </p:p... | PublisherRequest | daisydocs | daisydocs-2_1 | en | bruno | show |
| p:publisherRequest | p:publisherRequest is the root element of a publisher request document. A basic, empty publisher request is structured as follows: <p:publisherRequest xmlns:p="http://outerx.org/daisy/1.0#publisher" locale="en-US" versionMode="live" exceptions="throw"> [... various publisher requests ...] </p:p... | PublisherRequest | daisydocs | daisydocs-2_2 | en | bruno | show |
| p:publisherRequest | p:publisherRequest is the root element of a publisher request document. A basic, empty publisher request is structured as follows: <p:publisherRequest xmlns:p="http://outerx.org/daisy/1.0#publisher" locale="en-US" versionMode="live" exceptions="throw"> [... various publisher requests ...] </p:p... | PublisherRequest | daisydocs | daisydocs-2_3 | en | bruno | show |
| p:resolveDocumentIds | This element allows to retrieve the names of a set of documents of which you have only the ID. The advantage compared to using simply the repository API is that this only requires one remote call for as many documents as you need (assuming you are using the remote API, otherwise it does not make... | PublisherRequest | daisydocs | daisydocs-2_1 | en | bruno | show |
| p:resolveDocumentIds | This element allows to retrieve the names of a set of documents of which you have only the ID. The advantage compared to using simply the repository API is that this only requires one remote call for as many documents as you need (assuming you are using the remote API, otherwise it does not make... | PublisherRequest | daisydocs | daisydocs-2_2 | en | bruno | show |
| p:resolveDocumentIds | This element allows to retrieve the names of a set of documents of which you have only the ID. The advantage compared to using simply the repository API is that this only requires one remote call for as many documents as you need (assuming you are using the remote API, otherwise it does not make... | PublisherRequest | daisydocs | daisydocs-2_3 | en | bruno | show |
| p:resolveVariables | Resolves variables in the specified text strings. Request <p:resolveVariables> <p:text>...</p:text> ... more p:text elements ... </p:resolveVariables> Variables should be embedded in the text using ${varname} syntax ($$ is used to escape $). Response <p:resolvedVariables> <p:text>...</p:text> ..... | PublisherRequest | daisydocs | daisydocs-2_1 | en | bruno | show |
| p:resolveVariables | Resolves variables in the specified text strings. Request <p:resolveVariables> <p:text>...</p:text> ... more p:text elements ... </p:resolveVariables> Variables should be embedded in the text using ${varname} syntax ($$ is used to escape $). Response <p:resolvedVariables> <p:text>...</p:text> ..... | PublisherRequest | daisydocs | daisydocs-2_2 | en | bruno | show |
| p:resolveVariables | Resolves variables in the specified text strings. Request <p:resolveVariables> <p:text>...</p:text> ... more p:text elements ... </p:resolveVariables> Variables should be embedded in the text using ${varname} syntax ($$ is used to escape $). Response <p:resolvedVariables> <p:text>...</p:text> ..... | PublisherRequest | daisydocs | daisydocs-2_3 | en | bruno | show |
| p:selectionList | This instruction allows to retrieve the selection list of a field type. Request Syntax: <p:selectionList fieldType="..." branch="expr" language="expr"/> The fieldType attribute can contain either the name or ID of the field type. The branch and language attributes are optional, if not present t... | PublisherRequest | daisydocs | daisydocs-2_1 | en | bruno | show |
| p:selectionList | This instruction allows to retrieve the selection list of a field type. Request Syntax: <p:selectionList fieldType="..." branch="expr" language="expr"/> The fieldType attribute can contain either the name or ID of the field type. The branch and language attributes are optional, if not present t... | PublisherRequest | daisydocs | daisydocs-2_2 | en | bruno | show |
| p:selectionList | This instruction allows to retrieve the selection list of a field type. Request Syntax: <p:selectionList fieldType="..." branch="expr" language="expr"/> The fieldType attribute can contain either the name or ID of the field type. The branch and language attributes are optional, if not present t... | PublisherRequest | daisydocs | daisydocs-2_3 | en | bruno | show |
| p:shallowAnnotatedVersion | Returns the shallow version XML, this the version XML without field and part information in it. Request Syntax: <p:shallowAnnotatedVersion/> Response. A d:version element. If you requested the live version of the document, but the document does not have a live version, there will simply be no d:... | PublisherRequest | daisydocs | daisydocs-2_1 | en | bruno | show |
| p:shallowAnnotatedVersion | Returns the shallow version XML, this is the version XML without field and part information in it. Request Syntax: <p:shallowAnnotatedVersion/> Response. A d:version element. If you requested the live version of the document, but the document does not have a live version, there will simply be no... | PublisherRequest | daisydocs | daisydocs-2_2 | en | bruno | show |
| p:shallowAnnotatedVersion | Returns the shallow version XML, this the version XML without field and part information in it. Request Syntax: <p:shallowAnnotatedVersion/> Response. A d:version element. If you requested the live version of the document, but the document does not have a live version, there will simply be no d:... | PublisherRequest | daisydocs | daisydocs-2_3 | en | bruno | show |
| p:subscriptionInfo | Returns whether the user is subscribed for email notifications on the current context document. Request Syntax: <p:subscriptionInfo/> Response The response is the same element with the actual subscription status added: <p:subscriptionInfo subscribed="true|false"/> | PublisherRequest | daisydocs | daisydocs-2_1 | en | bruno | show |
| p:subscriptionInfo | Returns whether the user is subscribed for email notifications on the current context document. Request Syntax: <p:subscriptionInfo/> Response The response is the same element with the actual subscription status added: <p:subscriptionInfo subscribed="true|false"/> | PublisherRequest | daisydocs | daisydocs-2_2 | en | bruno | show |
| p:subscriptionInfo | Returns whether the user is subscribed for email notifications on the current context document. Request Syntax: <p:subscriptionInfo/> Response The response is the same element with the actual subscription status added: <p:subscriptionInfo subscribed="true|false"/> | PublisherRequest | daisydocs | daisydocs-2_3 | en | bruno | show |
| p:variablesConfig | This is not a publisher instruction, but rather configuration information for the variable resolution. With "variables" we mean the variables that can be embedded in Daisy-HTML parts and document names. See [todo] for more information on this topic. The p:variablesConfig element can only occur a... | PublisherRequest | daisydocs | daisydocs-2_1 | en | bruno | show |
| p:variablesConfig | This is not a publisher instruction, but rather configuration information for the variable resolution. With "variables" we mean the variables that can be embedded in Daisy-HTML parts and document names. See [todo] for more information on this topic. The p:variablesConfig element can only occur a... | PublisherRequest | daisydocs | daisydocs-2_2 | en | bruno | show |
| p:variablesConfig | This is not a publisher instruction, but rather configuration information for the variable resolution. With "variables" we mean the variables that can be embedded in Daisy-HTML parts and document names. See [todo] for more information on this topic. The p:variablesConfig element can only occur a... | PublisherRequest | daisydocs | daisydocs-2_3 | en | bruno | show |
| p:variablesList | Returns a list of all defined variables, according to the active p:variableConfig of the current publisher request. This is mostly useful to let editors pick variables from the list of available variables. Request This request requires no attributes, so its syntax is simply: <p:variablesList/> R... | PublisherRequest | daisydocs | daisydocs-2_1 | en | bruno | show |
| p:variablesList | Returns a list of all defined variables, according to the active p:variableConfig of the current publisher request. This is mostly useful to let editors pick variables from the list of available variables. Request This request requires no attributes, so its syntax is simply: <p:variablesList/> R... | PublisherRequest | daisydocs | daisydocs-2_2 | en | bruno | show |
| p:variablesList | Returns a list of all defined variables, according to the active p:variableConfig of the current publisher request. This is mostly useful to let editors pick variables from the list of available variables. Request This request requires no attributes, so its syntax is simply: <p:variablesList/> R... | PublisherRequest | daisydocs | daisydocs-2_3 | en | bruno | show |
| Part Editors | Introduction Starting with Daisy 1.4, the document editor has been changed to make it easy to insert custom editors for parts. Configuration The rules for detecting which part editor to use are as follows: if there is part specific editor configured, use that if the "Daisy HTML" flag of the par... | SimpleDocument | daisydocs | daisydocs-1_4 | en | bruno | show |
| Part Editors | Introduction Starting with Daisy 1.4, the document editor has been changed to make it easy to insert custom editors for parts. Configuration The rules for detecting which part editor to use are as follows: if there is part specific editor configured, use that if the "Daisy HTML" flag of the par... | SimpleDocument | daisydocs | daisydocs-1_5 | en | bruno | show |
| Part Editors | Introduction Starting with Daisy 1.4, the document editor has been changed to make it easy to insert custom editors for parts. Configuration The rules for detecting which part editor to use are as follows: if there is part specific editor configured, use that if the "Daisy HTML" flag of the par... | SimpleDocument | daisydocs | daisydocs-2_0 | en | bruno | show |
| Part Editors | Introduction Starting with Daisy 1.4, the document editor has been changed to make it easy to insert custom editors for parts. Configuration The rules for detecting which part editor to use are as follows: if there is part specific editor configured, use that if the "Daisy HTML" flag of the par... | SimpleDocument | daisydocs | daisydocs-2_1 | en | bruno | show |
| Part Editors | Introduction Starting with Daisy 1.4, the document editor has been changed to make it easy to insert custom editors for parts. Configuration The rules for detecting which part editor to use are as follows: if there is part specific editor configured, use that if the "Daisy HTML" flag of the par... | SimpleDocument | daisydocs | daisydocs-2_2 | en | bruno | show |
| Part Editors | Introduction Starting with Daisy 1.4, the document editor has been changed to make it easy to insert custom editors for parts. Configuration The rules for detecting which part editor to use are as follows: if there is part specific editor configured, use that if the "Daisy HTML" flag of the par... | SimpleDocument | daisydocs | daisydocs-2_3 | en | bruno | show |
| Partial Write Access | General This feature needs no introduction, but the design here will address several subtle aspects. Note: the ACL is always checked against the *previous* version of the document. e.g. ACL: if $Foo='foo' then no write access to $Bar When a document starts with $Foo='foo', then the user can o... | DaisyCommWikiDocument | daisywiki | main | en | karel | show |
| Paste this into lib/jars.xml | | Attachment | main | main | en | ugo | show |
| PDF renderer unification | IBEX -> FOP 0.94 Currently (up to version 2.2) the Daisy wiki uses Apache FOP for rendering single-document pdfs (when you replace .html with .pdf while browsing documents). For rendering books, IBEX is used. This distinction was introduced because at the time, FOP had several issues with the r... | DaisyCommWikiDocument | daisywiki | main | en | karel | show |
| Persistent login | See http://issues.cocoondev.org/browse/DSY-148 Being able to "save" your login on a computer. Think GMail, Flickr, Wordpress, etc. Introduces obvious security challenges, however all the cool kids are doing it anyway. Priority: medium. Feasibility: OK, with some caveats. Work involved: UI work... | DaisyCommWikiDocument | daisywiki | main | en | karel | show |
| Persistent URL | Introduction The "persistent URL" (or "bookmark URL") feature provides an URL containing all report configuration state, which can be bookmarked or mailed to other users to execute the same report. Specifying a non-default output format By adding some parameters to this URL, it is also possible ... | SimpleDocument | xreporter | main | en | bruno | show |
| Plugin registry | To make plugins available, you need to register them with a service called the PluginRegistry. When registering a plugin, you need to specify the following: The plugin type interface, specified as a Java Class object A name for the plugin, which should be unique within a particular type of plug... | SimpleDocument | daisydocs | daisydocs-2_1 | en | bruno | show |
| Plugin registry | To make plugins available, you need to register them with a service called the PluginRegistry. When registering a plugin, you need to specify the following: The plugin type interface, specified as a Java Class object A name for the plugin, which should be unique within a particular type of plug... | SimpleDocument | daisydocs | daisydocs-2_2 | en | bruno | show |
| Plugin registry | To make plugins available, you need to register them with a service called the PluginRegistry. When registering a plugin, you need to specify the following: The plugin type interface, specified as a Java Class object A name for the plugin, which should be unique within a particular type of plug... | SimpleDocument | daisydocs | daisydocs-2_3 | en | bruno | show |
| Policy | License There are no specific license requirements for projects wanting to join cocoondev.org, except that they are kindly requested to follow the guidelines of the OSI open source definition. While it is in everyone's interest to use AL 2.0-compatible licenses, it is at the project's sole discr... | SimpleDocument | main | main | en | stevenn | show |
| PostgreSQL installation | TODO | DaisyCommWikiDocument | daisywiki | main | en | bruno | show |
| PostgreSQL Installation Notes | Daisy Installation - PostgreSQL Thanks to Olivier Lange for http://lists.cocoondev.org/pipermail/daisy/2005-January/000740.html Instructions also purloined from: http://news.gmane.org/gmane.comp.java.openjms.user 31 May 2005 16:22 Tim Anderson http://lists.cocoondev.org/pipermail/daisy/2004-... | DaisyCommWikiDocument | daisywiki | main | en | thomasn | show |
| Powered by Daisy Logo | | Image | main | main | en | stevenn | show |
| Powered by Daisy Logo - small | | Image | main | main | en | stevenn | show |
| Process authoring overview | Introduction This section will get you started creating your own workflow process definitions. The process definitions are normal jBPM process definitions. In jBPM, a process definition is an XML file. This XML file can be deployed as-is, or can be put in a process archive (a zip file). The proc... | SimpleDocument | daisydocs | daisydocs-2_0 | en | bruno | show |
| Process authoring overview | Introduction This section will get you started creating your own workflow process definitions. The process definitions are normal jBPM process definitions. In jBPM, a process definition is an XML file. This XML file can be deployed as-is, or can be put in a process archive (a zip file). The proc... | SimpleDocument | daisydocs | daisydocs-2_1 | en | bruno | show |
| Process authoring overview | Introduction This section will get you started creating your own workflow process definitions. The process definitions are normal jBPM process definitions. In jBPM, a process definition is an XML file. This XML file can be deployed as-is, or can be put in a process archive (a zip file). The proc... | SimpleDocument | daisydocs | daisydocs-2_2 | en | bruno | show |
| Process authoring overview | Introduction This section will get you started creating your own workflow process definitions. The process definitions are normal jBPM process definitions. In jBPM, a process definition is an XML file. This XML file can be deployed as-is, or can be put in a process archive (a zip file). The proc... | SimpleDocument | daisydocs | daisydocs-2_3 | en | bruno | show |
| Programming interfaces | The native API of the Daisy repository server is its Java interface. To allow other processes (on the same or another computer) to talk to the repository server, a HTTP+XML based interface is available. Lastly, the Java API of the Daisy repository server is also implemented in a "remote" variant... | SimpleDocument | daisydocs | daisydocs-2_0 | en | bruno | show |
| Programming interfaces | The native API of the Daisy repository server is its Java interface. To allow other processes (on the same or another computer) to talk to the repository server, a HTTP+XML based interface is available. Lastly, the Java API of the Daisy repository server is also implemented in a "remote" variant... | SimpleDocument | daisydocs | daisydocs-2_1 | en | bruno | show |
| Programming interfaces | The native API of the Daisy repository server is its Java interface. To allow other processes (on the same or another computer) to talk to the repository server, a HTTP+XML based interface is available. Lastly, the Java API of the Daisy repository server is also implemented in a "remote" variant... | SimpleDocument | daisydocs | daisydocs-2_2 | en | bruno | show |
| Programming interfaces | The native API of the Daisy repository server is its Java interface. To allow other processes (on the same or another computer) to talk to the repository server, a HTTP+XML based interface is available. Lastly, the Java API of the Daisy repository server is also implemented in a "remote" variant... | SimpleDocument | daisydocs | daisydocs-2_3 | en | bruno | show |
| Project History | cocoon:/ext/xrp-status | SimpleDocument | xreporter | main | en | mpo | show |
| Projects overview | CHS CoUnit CVSSource Daisy Fins GeoID Othello Rhino+cont xReporter | SimpleDocument | main | main | en | stevenn | show |
| Publication Process Tasks Reference | General All publication tasks read and write their files in the book instance that is currently being processed. Thus all input and output paths specified on the individual publication tasks are relative paths within a book instance, and are prefixed with the directory of the current publication... | SimpleDocument | daisydocs | daisydocs-1_4 | en | bruno | show |
| Publication Process Tasks Reference | General All publication tasks read and write their files in the book instance that is currently being processed. Thus all input and output paths specified on the individual publication tasks are relative paths within a book instance, and are prefixed with the directory of the current publication... | SimpleDocument | daisydocs | daisydocs-1_5 | en | bruno | show |
| Publication Process Tasks Reference | General All publication tasks read and write their files in the book instance that is currently being processed. Thus all input and output paths specified on the individual publication tasks are relative paths within a book instance, and are prefixed with the directory of the current publication... | SimpleDocument | daisydocs | daisydocs-2_0 | en | bruno | show |
| Publication Process Tasks Reference | General All publication tasks read and write their files in the book instance that is currently being processed. Thus all input and output paths specified on the individual publication tasks are relative paths within a book instance, and are prefixed with the directory of the current publication... | SimpleDocument | daisydocs | daisydocs-2_1 | en | bruno | show |
| Publication Process Tasks Reference | General All publication tasks read and write their files in the book instance that is currently being processed. Thus all input and output paths specified on the individual publication tasks are relative paths within a book instance, and are prefixed with the directory of the current publication... | SimpleDocument | daisydocs | daisydocs-2_2 | en | bruno | show |
| Publication Process Tasks Reference | General All publication tasks read and write their files in the book instance that is currently being processed. Thus all input and output paths specified on the individual publication tasks are relative paths within a book instance, and are prefixed with the directory of the current publication... | SimpleDocument | daisydocs | daisydocs-2_3 | en | bruno | show |
| Publication Type Definition | Introduction As already mentioned in the overview, a publication type describes how a book is published. If you want to customize this process (most often to change the look of the published books) then you can do this by creating new publication types (do not modify the built-in publication typ... | SimpleDocument | daisydocs | daisydocs-1_4 | en | bruno | show |
| Publication Type Definition | Introduction As already mentioned in the overview, a publication type describes how a book is published. If you want to customize this process (most often to change the look of the published books) then you can do this by creating new publication types (do not modify the built-in publication typ... | SimpleDocument | daisydocs | daisydocs-1_5 | en | bruno | show |
| Publication Type Definition | Introduction As already mentioned in the overview, a publication type describes how a book is published. If you want to customize this process (most often to change the look of the published books) then you can do this by creating new publication types (do not modify the built-in publication typ... | SimpleDocument | daisydocs | daisydocs-2_0 | en | bruno | show |
| Publication Type Definition | Introduction As already mentioned in the overview, a publication type describes how a book is published. If you want to customize this process (most often to change the look of the published books) then you can do this by creating new publication types (do not modify the built-in publication typ... | SimpleDocument | daisydocs | daisydocs-2_1 | en | bruno | show |
| Publication Type Definition | Introduction As already mentioned in the overview, a publication type describes how a book is published. If you want to customize this process (most often to change the look of the published books) then you can do this by creating new publication types (do not modify the built-in publication typ... | SimpleDocument | daisydocs | daisydocs-2_2 | en | bruno | show |
| Publication Type Definition | Introduction As already mentioned in the overview, a publication type describes how a book is published. If you want to customize this process (most often to change the look of the published books) then you can do this by creating new publication types (do not modify the built-in publication typ... | SimpleDocument | daisydocs | daisydocs-2_3 | en | bruno | show |
| Publisher | Introduction The publisher is an optional component that runs inside the repository server. Its goal is to retrieve in one remote call the information you want to display on a page. The result is returned as an XML document. The requestable information consists of more then just XML dumps of rep... | SimpleDocument | daisydocs | daisydocs-1_3 | en | bruno | show |
| Publisher | Introduction The publisher is an optional component that runs inside the repository server. Its goal is to retrieve in one remote call the information you want to display on a page. The result is returned as an XML document. The requestable information consists of more then just XML dumps of rep... | SimpleDocument | daisydocs | daisydocs-1_4 | en | bruno | show |
| Publisher | Introduction The publisher is an optional component that runs inside the repository server. Its goal is to retrieve in one remote call the information you want to display on a page. The result is returned as an XML document. The requestable information consists of more than just XML dumps of rep... | SimpleDocument | daisydocs | daisydocs-1_5 | en | bruno | show |
| Publisher | Introduction The publisher is an optional component that runs inside the repository server. Its goal is to retrieve in one remote call the information you want to display on a page. The result is returned as an XML document. The requestable information consists of more than just XML dumps of rep... | SimpleDocument | daisydocs | daisydocs-2_0 | en | bruno | show |
| Publisher | Introduction The publisher is an extension component running in the content repository server. Its original goal was to retrieve in one remote call the information you need to display on a page. The result is returned as an XML document. However, the information that can be requested from the pu... | SimpleDocument | daisydocs | daisydocs-2_1 | en | bruno | show |
| Publisher | Introduction The publisher is an extension component running in the content repository server. Its original goal was to retrieve in one remote call the information you need to display on a page. The result is returned as an XML document. However, the information that can be requested from the pu... | SimpleDocument | daisydocs | daisydocs-2_2 | en | bruno | show |
| Publisher | Introduction The publisher is an extension component running in the content repository server. Its original goal was to retrieve in one remote call the information you need to display on a page. The result is returned as an XML document. However, the information that can be requested from the pu... | SimpleDocument | daisydocs | daisydocs-2_3 | en | bruno | show |
| PublisherDocument class | | Image | daisywiki | main | en | sokol8 | show |
| PublisherRequest class | | Image | daisywiki | main | en | sokol8 | show |
| Publishing: roadmap | Positioning and goals Daisy has been developed from the beginning to support a broad range of content management needs. Based upon the core repository server, many front ends and publishing systems are possible. Currently we have: the Wiki. Through the extension mechanism and publisher request... | DaisyCommWikiDocument | daisywiki | main | en | stevenn | show |
| Publishing based on a repository export | Introduction Here we consider a semi-static publishing scenario. It works disconnected from the repository server, based on an "export" of the (relevant) repository data. There can be as many of these publishing frontends (with corresponding exports) as you want. +------------+ |repo server |..... | DaisyCommWikiDocument | daisywiki | main | en | bruno | show |
| Publish-only library | This should provide a solution for people who want to build a website with Daisy, separate from the Daisy Wiki, with high flexibility for customisations, but without having to write all publishing logic from scratch. The goal is to split of the core document publishing functionality from the Dai... | DaisyCommWikiDocument | daisywiki | main | en | bruno | show |
| publish-only notes | (very draft) Concept "publish-only" is the name we give to all activities related to supporting the creation of publishing applications, i.e. applications concerned with using/publishing content available in a Daisy repository. This is in contrast with Daisy's default frontend application, the D... | SimpleDocument | daisydocs | daisydocs-1_3 | en | bruno | show |
| publish-only notes | (very draft) Concept "publish-only" is the name we give to all activities related to supporting the creation of publishing applications, i.e. applications concerned with using/publishing content available in a Daisy repository. This is in contrast with Daisy's default frontend application, the D... | SimpleDocument | daisydocs | daisydocs-1_4 | en | bruno | show |
| pubreqoverview | | Image | daisydocs | daisydocs-2_1 | en | bruno | show |
| pubreqoverview | | Image | daisydocs | daisydocs-2_2 | en | bruno | show |
| pubreqoverview | | Image | daisydocs | daisydocs-2_3 | en | bruno | show |
| Quelltext | Der Quelltext kann mittels SVN erhalten werden. Anweisungen dazu, wie eine Daisy-Entwicklunsgumgebung aufgesetzt wird (dies unterscheidet sich geringfügig von der Vorgehensweise die anzuwenden ist, falls sie eine gepackte Version benutzen) ist in verschiedenen Dateien namens README.txt im Quellc... | SimpleDocument | daisydocs | daisydocs-1_5 | de | bruno | show |
| Quelltext | Der Quelltext kann mittels SVN erhalten werden. Anweisungen dazu, wie eine Daisy-Entwicklunsgumgebung aufgesetzt wird (dies unterscheidet sich geringfügig von der Vorgehensweise die anzuwenden ist, falls sie eine gepackte Version benutzen) ist in verschiedenen Dateien namens README.txt im Quellc... | SimpleDocument | daisydocs | daisydocs-2_0 | de | bruno | show |
| Quelltext | Der Quelltext kann mittels SVN erhalten werden. Anweisungen dazu, wie eine Daisy-Entwicklunsgumgebung aufgesetzt wird (dies unterscheidet sich geringfügig von der Vorgehensweise die anzuwenden ist, falls sie eine gepackte Version benutzen) ist in verschiedenen Dateien namens README.txt im Quellc... | SimpleDocument | daisydocs | daisydocs-2_1 | de | bruno | show |
| Quelltext | Der Quelltext kann mittels SVN erhalten werden. Anweisungen dazu, wie eine Daisy-Entwicklunsgumgebung aufgesetzt wird (dies unterscheidet sich geringfügig von der Vorgehensweise die anzuwenden ist, falls sie eine gepackte Version benutzen) ist in verschiedenen Dateien namens README.txt im Quellc... | SimpleDocument | daisydocs | daisydocs-2_2 | de | bruno | show |
| Query documents linked to the current document | Overview Proiding a list of linked documents is a useful addition to many Daisy pages. ( For example, documenting a server and having links to all the applications running on that server. ) There are multiple ways of accomplishing this, and some confusion on the easiest way to create linked d... | DaisyCommWikiDocument | daisywiki | main | en | twells | show |
| Query Language | Introduction The Daisy Query Language can be used to search for documents. Queries can be used in various places: explicitely via the "Query Search" page embedded inside documents embedded inside navigation trees The implementation of various daisy features is also based on queries, such as th... | SimpleDocument | daisydocs | daisydocs-1_2 | en | stevenn | show |
| Query Language | Introduction The Daisy Query Language can be used to search for documents (more precisely, document variants). Queries can be used in various places: explicitely via the "Query Search" page embedded inside documents embedded inside navigation trees The implementation of various Daisy features ... | SimpleDocument | daisydocs | daisydocs-1_3 | en | stevenn | show |
| Query Language | Introduction The Daisy Query Language can be used to search for documents (more precisely, document variants). In the Daisy Wiki, queries can be used in various places: explicitely via the "Query Search" page embedded inside documents embedded inside navigation trees The implementation of var... | SimpleDocument | daisydocs | daisydocs-1_4 | en | stevenn | show |
| Query Language | Introduction The Daisy Query Language can be used to search for documents (more precisely, document variants). In the Daisy Wiki, queries can be used in various places: explicitly via the "Query Search" page embedded inside documents embedded inside navigation trees The implementation of vari... | SimpleDocument | daisydocs | daisydocs-1_5 | en | stevenn | show |
| Query Language | Introduction The Daisy Query Language can be used to search for documents (more precisely, document variants). In the Daisy Wiki, queries can be used in various places: explicitly via the "Query Search" page embedded inside documents embedded inside navigation trees The implementation of vari... | SimpleDocument | daisydocs | daisydocs-2_0 | en | stevenn | show |
| Query Language | Introduction The Daisy Query Language can be used to search for documents (more precisely, document variants). In the Daisy Wiki, queries can be used in various places: explicitly via the "Query Search" page embedded inside documents embedded inside navigation trees The implementation of vari... | SimpleDocument | daisydocs | daisydocs-2_1 | en | stevenn | show |
| Query Language | Introduction The Daisy Query Language can be used to search for documents (more precisely, document variants). In the Daisy Wiki, queries can be used in various places: explicitly via the "Query Search" page embedded inside documents embedded inside navigation trees The implementation of vari... | SimpleDocument | daisydocs | daisydocs-2_2 | en | stevenn | show |
| Query Language | Introduction The Daisy Query Language can be used to search for documents (more precisely, document variants). In the Daisy Wiki, queries can be used in various places: explicitly via the "Query Search" page embedded inside documents embedded inside navigation trees The implementation of vari... | SimpleDocument | daisydocs | daisydocs-2_3 | en | stevenn | show |
| Query language changes | What sort of things do we want to be able to search for? Documents for which translated variants are not up to date or are missing (and the inverse: are up to date and exist) With the new attributes, we can do this. Suppose a reference variant EN and translated variant FR, than searching for out... | DaisyCommWikiDocument | daisywiki | main | en | bruno | show |
| Query Styling | (This feature is new in Daisy 1.1) By default, query results are rendered as a table. It is however possible to customize the styling of these query results. This is done by supplying a style_hint option in the query, for example: select name where true option style_hint = 'bullets' The style h... | SimpleDocument | daisydocs | daisydocs-1_2 | en | bruno | show |
| Query Styling | By default, query results are rendered as a table. It is however possible to customize the styling of these query results. This is done by supplying a style_hint option in the query, for example: select name where true option style_hint = 'bullets' The style hint 'bullets' is included as a samp... | SimpleDocument | daisydocs | daisydocs-1_3 | en | bruno | show |
| Query Styling | By default, query results are rendered as a table. It is however possible to customize the styling of these query results. This is done by supplying a style_hint option in the query, for example: select name where true option style_hint = 'bullets' The style hint 'bullets' is included as a samp... | SimpleDocument | daisydocs | daisydocs-1_4 | en | bruno | show |
| Query Styling | Overview By default, query results are rendered as a table. It is however possible to customize the styling of the query results. This is done by supplying a style_hint option in the query, for example: select name where true option style_hint = 'bullets' The style hint 'bullets' is included as ... | SimpleDocument | daisydocs | daisydocs-1_5 | en | bruno | show |
| Query Styling | Overview By default, query results are rendered as a table. It is however possible to customize the styling of the query results. This is done by supplying a style_hint option in the query, for example: select name where true option style_hint = 'bullets' The style hint 'bullets' is included as ... | SimpleDocument | daisydocs | daisydocs-2_0 | en | bruno | show |
| Query Styling | Overview By default, query results are rendered as a table. It is however possible to customize the styling of the query results. This is done by supplying a style_hint option in the query, for example: select name where true option style_hint = 'bullets' The style hint 'bullets' is included as ... | SimpleDocument | daisydocs | daisydocs-2_1 | en | bruno | show |
| Query Styling | Overview By default, query results are rendered as a table. It is however possible to customize the styling of the query results. This is done by supplying a style_hint option in the query, for example: select name where true option style_hint = 'bullets' The style hint 'bullets' is included as ... | SimpleDocument | daisydocs | daisydocs-2_2 | en | bruno | show |
| Query Styling | Overview By default, query results are rendered as a table. It is however possible to customize the styling of the query results. This is done by supplying a style_hint option in the query, for example: select name where true option style_hint = 'bullets' The style hint 'bullets' is included as ... | SimpleDocument | daisydocs | daisydocs-2_3 | en | bruno | show |
| RDaisy | RDaisy: A Ruby Library for Accessing a Daisy Repository The Daisy repository server library for Ruby provides a layer of abstraction to allow Ruby developers to easily access content stored in a Daisy repository for use in Ruby applications, in particular, Ruby on Rails based web applications. ... | DaisyCommWikiDocument | daisywiki | main | en | christopher.haines | show |
| Reference language | The reference language for a document is the language variant in which the content is originally authored, and on which the translation into other languages is based. The reference language is a document property and allows to perform translation management. | GlossaryEntry | daisydocs | daisydocs-2_2 | en | bruno | show |
| Reference language | The reference language for a document is the language variant in which the content is originally authored, and on which the translation into other languages is based. The reference language is a document property and allows to perform translation management. | GlossaryEntry | daisydocs | daisydocs-2_3 | en | bruno | show |
| repo_wiki | | Image | daisy | main | en | bruno | show |
| Report format index | Introduction The report format index is a file describing the various output formats available for a specific report. Based on this file, the menu with the various choices will be generated. In case no specific configuration is present, a default menu is shown. The format index file also allows ... | SimpleDocument | xreporter | main | en | bruno | show |
| Report formats | Introduction A format defines a way of how the report output should be rendered. A format is defined by creating an XML file. A format consists of a pointer to a format type, which is the actual implementation of the output rendering, and configuration information for that format type. To make t... | SimpleDocument | xreporter | main | en | bruno | show |
| Report format types | Introduction A report format type implements a specific way of rendering the report output. The principle of creating a report format type is quite simple: it is a just a directory containing a Cocoon sitemap.xmap file. The sitemap.xmap should contain at least one pipeline for rendering the outp... | SimpleDocument | xreporter | main | en | bruno | show |
| report icon | | Image | xreporter | main | en | mpo | show |
| Reports | This document describes the format of the report definition files. Report definitions are described in XML files, which should be placed in a specific directory. The directory location is configurable in the config.xml. The name of a report definition file should always end in ".xml". All exampl... | SimpleDocument | xreporter | main | en | bruynb | show |
| Report-specific Styling | This document applies to xReporter 1.1 and above. By default, xReporter will show the output of a report in a standard table. This can be further customised either by parameterizing the default output.xsl stylesheets (which does not require knowledge of XSL), or by providing report-specific XSL'... | SimpleDocument | xreporter | main | en | stevenn | show |
| repository_functionalities | | Image | daisydocs | daisydocs-2_0 | en | bruno | show |
| repository_functionalities | | Image | daisydocs | daisydocs-2_1 | en | bruno | show |
| repository_functionalities | | Image | daisydocs | daisydocs-2_2 | en | bruno | show |
| repository_functionalities | | Image | daisydocs | daisydocs-2_3 | en | bruno | show |
| Repository Administration | Administrative actions for the Daisy Repository Server include: managing users managing document collections managing document, part and field types (ie, the repository schema) managing access control All these operations should be performed through the Daisy Repository Server, never directly ... | SimpleDocument | daisydocs | daisydocs-1_2 | en | bruno | show |
| Repository Administration | Administrative actions for the Daisy Repository Server include: managing users managing document collections managing document, part and field types (ie, the repository schema) managing access control All these operations should be performed through the Daisy Repository Server, never directly ... | SimpleDocument | daisydocs | daisydocs-1_3 | en | bruno | show |
| Repository Administration | Administrative actions for the Daisy Repository Server include: managing users managing document collections managing document, part and field types (ie, the repository schema) managing access control All these operations should be performed through the Daisy Repository Server, never directly ... | SimpleDocument | daisydocs | daisydocs-1_4 | en | bruno | show |
| Repository Administration | Administrative actions for the Daisy Repository Server include: managing users managing document collections managing document, part and field types (ie, the repository schema) managing access control All these operations should be performed through the Daisy Repository Server, never directly ... | SimpleDocument | daisydocs | daisydocs-1_5 | en | bruno | show |
| Repository Administration | Administrative actions for the Daisy Repository Server include: managing users managing document collections managing document, part and field types (ie, the repository schema) managing access control All these operations should be performed through the Daisy Repository Server, never directly ... | SimpleDocument | daisydocs | daisydocs-2_0 | en | bruno | show |
| Repository Administration | Administrative actions for the Daisy Repository Server include: managing users managing document collections managing document, part and field types (ie, the repository schema) managing access control All these operations should be performed through the Daisy Repository Server, never directly ... | SimpleDocument | daisydocs | daisydocs-2_1 | en | bruno | show |
| Repository Administration | Administrative actions for the Daisy Repository Server include: managing users managing document collections managing document, part and field types (ie, the repository schema) managing access control All these operations should be performed through the Daisy Repository Server, never directly ... | SimpleDocument | daisydocs | daisydocs-2_2 | en | bruno | show |
| Repository Administration | Administrative actions for the Daisy Repository Server include: managing users managing document collections managing document, part and field types (ie, the repository schema) managing access control All these operations should be performed through the Daisy Repository Server, never directly ... | SimpleDocument | daisydocs | daisydocs-2_3 | en | bruno | show |
| Repository data directory | The directory where, in a typical setup, all configuration information, data and log files for the repository are stored, except for the data which is stored in the SQL database. The location of the repository data directory is specified as a parameter when starting the repository server. | GlossaryEntry | daisydocs | daisydocs-2_1 | en | bruno | show |
| Repository data directory | The directory where, in a typical setup, all configuration information, data and log files for the repository are stored, except for the data which is stored in the SQL database. The location of the repository data directory is specified as a parameter when starting the repository server. | GlossaryEntry | daisydocs | daisydocs-2_2 | en | bruno | show |
| Repository data directory | The directory where, in a typical setup, all configuration information, data and log files for the repository are stored, except for the data which is stored in the SQL database. The location of the repository data directory is specified as a parameter when starting the repository server. | GlossaryEntry | daisydocs | daisydocs-2_3 | en | bruno | show |
| Repository Extensions | The Daisy Repository has the concept of extensions, which is additional functionality that is separate from the core repository. Extensions are accessed in the repository API as follows: Repository repository = repositoryManager.getRepository(new Credentials("user", "password")); MyExtension myE... | SimpleDocument | daisydocs | daisydocs-1_2 | en | bruno | show |
| Repository Extensions | The Daisy Repository has the concept of extensions, which is additional functionality that is separate from the core repository. Extensions are accessed in the repository API as follows: Repository repository = repositoryManager.getRepository(new Credentials("user", "password")); MyExtension myE... | SimpleDocument | daisydocs | daisydocs-1_3 | en | bruno | show |
| Repository Extensions | The Daisy Repository has the concept of extensions, which is additional functionality that is separate from the core repository. Extensions are accessed in the repository API as follows: Repository repository = repositoryManager.getRepository(new Credentials("user", "password")); MyExtension myE... | SimpleDocument | daisydocs | daisydocs-1_4 | en | bruno | show |
| Repository Extensions | The Daisy Repository has the concept of extensions, which is additional functionality that is separate from the core repository. Extensions are accessed in the repository API as follows: Repository repository = repositoryManager.getRepository(new Credentials("user", "password")); MyExtension myE... | SimpleDocument | daisydocs | daisydocs-1_5 | en | bruno | show |
| Repository Extensions | The Daisy Repository has the concept of extensions, which is additional functionality that is separate from the core repository. Extensions are accessed in the repository API as follows: Repository repository = repositoryManager.getRepository(new Credentials("user", "password")); MyExtension myE... | SimpleDocument | daisydocs | daisydocs-2_0 | en | bruno | show |
| Repository Extensions | Repository Extensions are a particular type of plugins that add extra functionality to the repository. An Extension is usually related to the repository, e.g. because it needs access to information in the repository. The extension code has no special privileges, it simply makes use of the reposi... | SimpleDocument | daisydocs | daisydocs-2_1 | en | bruno | show |
| Repository Extensions | Repository Extensions are a particular type of plugins that add extra functionality to the repository. An Extension is usually related to the repository, e.g. because it needs access to information in the repository. The extension code has no special privileges, it simply makes use of the reposi... | SimpleDocument | daisydocs | daisydocs-2_2 | en | bruno | show |
| Repository Extensions | Repository Extensions are a particular type of plugins that add extra functionality to the repository. An Extension is usually related to the repository, e.g. because it needs access to information in the repository. The extension code has no special privileges, it simply makes use of the reposi... | SimpleDocument | daisydocs | daisydocs-2_3 | en | bruno | show |
| Repository Implementation | This section contains some information on internals of the repository server. It is mostly only relevant for people who want to hack on Daisy itself. | SimpleDocument | daisydocs | daisydocs-2_1 | en | bruno | show |
| Repository Implementation | This section contains some information on internals of the repository server. It is mostly only relevant for people who want to hack on Daisy itself. | SimpleDocument | daisydocs | daisydocs-2_2 | en | bruno | show |
| Repository Implementation | This section contains some information on internals of the repository server. It is mostly only relevant for people who want to hack on Daisy itself. | SimpleDocument | daisydocs | daisydocs-2_3 | en | bruno | show |
| Repository Implementation | We have mentioned before that there are two implementations of the repository API: one we call local (the one in the repository server) and one we call remote. In this document we're going to look into how the repository objects are implemented to support both local and remote implementations. R... | SimpleDocument | daisydocs | daisydocs-1_2 | en | bruno | show |
| Repository Implementation | We have mentioned before that there are two implementations of the repository API: one we call local (the one in the repository server) and one we call remote. In this document we're going to look into how the repository objects are implemented to support both local and remote implementations. R... | SimpleDocument | daisydocs | daisydocs-1_3 | en | bruno | show |
| Repository Implementation | We have mentioned before that there are two implementations of the repository API: one we call local (the one in the repository server) and one we call remote. In this document we're going to look into how the repository objects are implemented to support both local and remote implementations. R... | SimpleDocument | daisydocs | daisydocs-1_4 | en | bruno | show |
| Repository Implementation | We have mentioned before that there are two implementations of the repository API: one we call local (the one in the repository server) and one we call remote. In this document we're going to look into how the repository objects are implemented to support both local and remote implementations. R... | SimpleDocument | daisydocs | daisydocs-1_5 | en | bruno | show |
| Repository Implementation | We have mentioned before that there are two implementations of the repository API: one we call local (the one in the repository server) and one we call remote. In this document we're going to look into how the repository objects are implemented to support both local and remote implementations. R... | SimpleDocument | daisydocs | daisydocs-2_0 | en | bruno | show |
| Repository Implementation | We have mentioned before that there are two implementations of the repository API: one we call local (the one in the repository server) and one we call remote. In this document we're going to look into how the repository objects are implemented to support both local and remote implementations. R... | SimpleDocument | daisydocs | daisydocs-2_1 | en | bruno | show |
| Repository Implementation | We have mentioned before that there are two implementations of the repository API: one we call local (the one in the repository server) and one we call remote. In this document we're going to look into how the repository objects are implemented to support both local and remote implementations. R... | SimpleDocument | daisydocs | daisydocs-2_2 | en | bruno | show |
| Repository Implementation | We have mentioned before that there are two implementations of the repository API: one we call local (the one in the repository server) and one we call remote. In this document we're going to look into how the repository objects are implemented to support both local and remote implementations. R... | SimpleDocument | daisydocs | daisydocs-2_3 | en | bruno | show |
| Repository Implementation Intro | The repository server is a standalone process that concerns itself with tasks such as storing and retrieving documents, indexing them and performing searches, manage access control to these documents, and all that. Remote clients talk to the repository using a HTTP+XML interface. The repository ... | SimpleDocument | daisydocs | daisydocs-1_2 | en | bruno | show |
| Repository Implementation Intro | The repository server is a standalone process that concerns itself with tasks such as storing and retrieving documents, indexing them and performing searches, manage access control to these documents, and all that. Remote clients talk to the repository using a HTTP+XML interface. The repository ... | SimpleDocument | daisydocs | daisydocs-1_3 | en | bruno | show |
| Repository Implementation Intro | The repository server is a standalone process that concerns itself with tasks such as storing and retrieving documents, indexing them and performing searches, manage access control to these documents, and all that. Remote clients talk to the repository using a HTTP+XML interface. The repository ... | SimpleDocument | daisydocs | daisydocs-1_4 | en | bruno | show |
| Repository Implementation Intro | The repository server is a standalone process that concerns itself with tasks such as storing and retrieving documents, indexing them and performing searches, manage access control to these documents, and all that. Remote clients talk to the repository using a HTTP+XML interface. The repository ... | SimpleDocument | daisydocs | daisydocs-1_5 | en | bruno | show |
| Repository Implementation Intro | The repository server is a standalone process that concerns itself with tasks such as storing and retrieving documents, indexing them and performing searches, manage access control to these documents, and all that. Remote clients talk to the repository using a HTTP+XML interface. The repository ... | SimpleDocument | daisydocs | daisydocs-2_0 | en | bruno | show |
| Repository Implementation Runtime View | | Image | daisydocs | daisydocs-1_2 | en | bruno | show |
| Repository Implementation Runtime View | | Image | daisydocs | daisydocs-1_3 | en | bruno | show |
| Repository Implementation Runtime View | | Image | daisydocs | daisydocs-1_4 | en | bruno | show |
| Repository Implementation Runtime View | | Image | daisydocs | daisydocs-1_5 | en | bruno | show |
| Repository Implementation Runtime View | | Image | daisydocs | daisydocs-2_0 | en | bruno | show |
| Repository Implementation Runtime View | | Image | daisydocs | daisydocs-2_1 | en | bruno | show |
| Repository Implementation Runtime View | | Image | daisydocs | daisydocs-2_2 | en | bruno | show |
| Repository Implementation Runtime View | | Image | daisydocs | daisydocs-2_3 | en | bruno | show |
| Repository namespaces | Each Daisy repository (since Daisy 2.0) has a namespace. The documents created in that repository will by default belong to that namespace. The ID of a document is the combination of a numeric sequence and the namespace, for example: 2583-AWAN Each repository server is responsible for maintainin... | SimpleDocument | daisydocs | daisydocs-2_0 | en | bruno | show |
| Repository namespaces | Each Daisy repository (since Daisy 2.0) has a namespace. The documents created in that repository will by default belong to that namespace. The ID of a document is the combination of a numeric sequence and the namespace, for example: 2583-AWAN Each repository server is responsible for maintainin... | SimpleDocument | daisydocs | daisydocs-2_1 | en | bruno | show |
| Repository namespaces | Each Daisy repository (since Daisy 2.0) has a namespace. The documents created in that repository will by default belong to that namespace. The ID of a document is the combination of a numeric sequence and the namespace, for example: 2583-AWAN Each repository server is responsible for maintainin... | SimpleDocument | daisydocs | daisydocs-2_2 | en | bruno | show |
| Repository namespaces | Each Daisy repository (since Daisy 2.0) has at least one namespace. The documents created in that repository will by default belong to one of those namespaces based on the configuration. The ID of a document is the combination of a numeric sequence and the namespace, for example: 2583-AWAN Each ... | SimpleDocument | daisydocs | daisydocs-2_3 | en | bruno | show |
| Repository plugins | Daisy provides a number of interfaces through which the repository functionality can be extended or customized. The components that do this are called plugins. Anatomy of a plugin A plugin is basically an implementation of a certain plugin interface. The various plugin interfaces are listed furt... | SimpleDocument | daisydocs | daisydocs-2_1 | en | bruno | show |
| Repository plugins | Daisy provides a number of interfaces through which the repository functionality can be extended or customized. The components that do this are called plugins. Anatomy of a plugin A plugin is basically an implementation of a certain plugin interface. The various plugin interfaces are listed furt... | SimpleDocument | daisydocs | daisydocs-2_2 | en | bruno | show |
| Repository plugins | Daisy provides a number of interfaces through which the repository functionality can be extended or customized. The components that do this are called plugins. Anatomy of a plugin A plugin is basically an implementation of a certain plugin interface. The various plugin interfaces are listed furt... | SimpleDocument | daisydocs | daisydocs-2_3 | en | bruno | show |
| Repository schema | Overview The repository schema controls the structure of documents. The repository schema defines part types, field types and document types. A document type is a combination of zero or more part types and zero or more field types. Part and field types are defined as independent entities, meanin... | SimpleDocument | daisydocs | daisydocs-2_0 | en | bruno | show |
| Repository schema | Overview The repository schema controls the structure of documents. The repository schema defines part types, field types and document types. A document type is a combination of zero or more part types and zero or more field types. Part and field types are defined as independent entities, meanin... | SimpleDocument | daisydocs | daisydocs-2_1 | en | bruno | show |
| Repository schema | Overview The repository schema controls the structure of documents. The repository schema defines part types, field types and document types. A document type is a combination of zero or more part types and zero or more field types. Part and field types are defined as independent entities, meanin... | SimpleDocument | daisydocs | daisydocs-2_2 | en | bruno | show |
| Repository schema | Overview The repository schema controls the structure of documents. The repository schema defines part types, field types and document types. A document type is a combination of zero or more part types and zero or more field types. Part and field types are defined as independent entities, meanin... | SimpleDocument | daisydocs | daisydocs-2_3 | en | bruno | show |
| Repository Schema Structure | | Image | daisydocs | daisydocs-1_2 | en | bruno | show |
| Repository Schema Structure | | Image | daisydocs | daisydocs-1_3 | en | bruno | show |
| Repository Schema Structure | | Image | daisydocs | daisydocs-1_4 | en | bruno | show |
| Repository Schema Structure | | Image | daisydocs | daisydocs-1_5 | en | bruno | show |
| Repository Schema Structure | | Image | daisydocs | daisydocs-2_0 | en | bruno | show |
| Repository Schema Structure | | Image | daisydocs | daisydocs-2_1 | en | bruno | show |
| Repository Schema Structure | | Image | daisydocs | daisydocs-2_2 | en | bruno | show |
| Repository Schema Structure | | Image | daisydocs | daisydocs-2_3 | en | bruno | show |
| Repository server | The repository server is the core of Daisy. It provides the pure content management functionality without GUI (graphical user interface). The main purpose of the repository is managing documents. The repository server consists of a core and some non-essential extension components that add additi... | SimpleDocument | daisydocs | daisydocs-2_0 | en | bruno | show |
| Repository server | The repository server is the core of Daisy. It provides the pure content management functionality without GUI (graphical user interface). The main purpose of the repository is managing documents. The repository server consists of a core and some non-essential extension components that add additi... | SimpleDocument | daisydocs | daisydocs-2_1 | en | bruno | show |
| Repository server | The repository server is the core of Daisy. It provides the pure content management functionality wi |