The Cinnamon desktop client in action
An introduction to the Cinnamon desktop client with screenshots
This overview uses images of the German version of Cinnamon. Cinnamon is currently available in English and German, but can be translated into the language of your choice quite easily. The client supports resource bundles for other languages, and the server also allows you to define UI-languages, so for example a custom object type is displayed as "Black/White image" in English and "Schwarz/Weiß-Bild" in German.
[Click on the images to view a larger version]
Repository view
Upon start the client connects to the servers specified in the file config/CinnamonDesktopClient.config.xml in the element <servers> and lists the existing repositories.
<servers>
<server name="Cinnamon">http://127.0.0.1:8080/cinnamon/cinnamon</server>
</servers>
Open a repository
After login, you can open the repository navigation window, which consists of a tree view of the repository and an area where objects and other content is displayed.
Note that you may create several connections to a repository at the same time with the same or different users.
The repository view
The repository view shows the user's home folder in the current repository, his previously defined search objects and offers access to a list of objects this user has checked out.
Folders and objects have several default fields like name, owner, type and ACL. Depending on the type, other, more specialized sub-windows are shownin the lower right area.
Object relations
An object may have any number of relations to other objects. For example, a document may be linked to images which are contained inside and which have to be present for the publishing process. Via the relations tab, you can always see which objects depend on the selected one - and upon which objects it is dependent. Cinnamon protects related objects as needed, so you cannot accidentally delete an image which is required by one or more documents.
Objects and relations are version dependent - version 1 of a document may be related to version 3 of an image, but version 2 of the document may be linked to a different version. Relations may define deep dependencies (for example, an image which must be present in the document) or flat (for example the PDF version of a DITA document - the PDF is not necessarily dependent on the source document).
Object permissions
An object is always connected to an ACL which determines which operations a user may perform on the object. This allows fine grained control of browsing, reading and writing of both the object's metadata and its content.
Object context menu
Objects may be checked out, in which case they are protected from being overwritten or changed by other users. You can also create new versions or copy & paste objects.
Search editor
The search editor allows you to create complex queries with "and" or "or" groups of criteria. The index is based upon Lucene and you can define your own semantic index fields - for example, in an XML document all <title> element may be added to the new index field "document_title", while the content of <body> is added to "document_content". Those fields can be specified in the search dialog and so you may search for a document which contains certain words in the title or the content.
Once defined, you can save search definitions and execute them later on. This is useful to create searches for publication sets, so you can always get a list of "all documents and images used in the 1.2 version of our French operating manual".
Search result
The objects found by a search are listed along with their path. You can export them as a CSV-list or use them directly for further actions.









