Search results

redis-7.2.3-1.lbn36.x86_64

Redis is an advanced key-value store. It is often referred to as a data structure server since keys can contain strings, hashes, lists, sets and sorted sets. You can run atomic operations on these types, like appending to a string; incrementing the value in a hash; pushing to a list; computing set intersection, union and difference; or getting the member with highest ranking in a sorted set. In order to achieve its outstanding performance, Redis works with an in-memory dataset. Depending on your use case, you can persist it either by dumping the dataset to disk every once in a while, or by appending each command to a log. Redis also supports trivial-to-setup master-slave replication, with very fast non-blocking first synchronization, auto-reconnection on net split and so forth. Other features include Transactions, Pub/Sub, Lua scripting, Keys with a limited time-to-live, and configuration settings to make Redis behave like a cache. You can use Redis from most programming languages also.

redis-devel-7.2.3-1.lbn36.x86_64

Header file required for building loadable Redis modules. Detailed API documentation is available in the redis-doc package.

redland-1.0.10-4.lbn13.x86_64

Redland is a library that provides a high-level interface for RDF (Resource Description Framework) implemented in an object-based API. It is modular and supports different RDF/XML parsers, storage mechanisms and other elements. Redland is designed for applications developers to provide RDF support in their applications as well as for RDF developers to experiment with the technology.

redland-1.0.15-2.fc18.1.armv6hl

Redland is a library that provides a high-level interface for RDF (Resource Description Framework) implemented in an object-based API. It is modular and supports different RDF/XML parsers, storage mechanisms and other elements. Redland is designed for applications developers to provide RDF support in their applications as well as for RDF developers to experiment with the technology.

redland-1.0.16-2.fc19.x86_64

Redland is a library that provides a high-level interface for RDF (Resource Description Framework) implemented in an object-based API. It is modular and supports different RDF/XML parsers, storage mechanisms and other elements. Redland is designed for applications developers to provide RDF support in their applications as well as for RDF developers to experiment with the technology.

redland-1.0.16-3.fc19.armv6hl

Redland is a library that provides a high-level interface for RDF (Resource Description Framework) implemented in an object-based API. It is modular and supports different RDF/XML parsers, storage mechanisms and other elements. Redland is designed for applications developers to provide RDF support in their applications as well as for RDF developers to experiment with the technology.

redland-1.0.17-8.lbn25.x86_64

Redland is a library that provides a high-level interface for RDF (Resource Description Framework) implemented in an object-based API. It is modular and supports different RDF/XML parsers, storage mechanisms and other elements. Redland is designed for applications developers to provide RDF support in their applications as well as for RDF developers to experiment with the technology.

redland-1.0.17-35.lbn36.x86_64

Redland is a library that provides a high-level interface for RDF (Resource Description Framework) implemented in an object-based API. It is modular and supports different RDF/XML parsers, storage mechanisms and other elements. Redland is designed for applications developers to provide RDF support in their applications as well as for RDF developers to experiment with the technology.

redomino.advancedkeyword-1.4-1.lbn19.noarch

The ``redomino.advancedkeyword`` plugin aims to improve the keyword mechanism provided by Plone introducing *hierarchy* among keywords. All the customizations introduced by redomino.advancedkeyword are made with backward compatibility in mind. You can also use this plugin without pain when you need to migrate your contents: redomino.advancedkeyword still uses the standard ``subject`` field and the main work was made at frontend level using javascript. Note: having your javascript enabled is not required to use redomino.advancedkeyword. What are the main problems of the old keyword management? --------------------------------------------------------- Here is a list of problems: * all the keywords are listed as a long, long plain list * keywords are not semantically grouped Here you can see the standard keyword widget how it is prompted to : .. figure:: https://github.com/redomino/redomino.advancedkeyword/raw/master/docs/resources/keywordold.png :align: center Old keywords widgets. As you can imagine the above edit widget is hard to use and difficult to manage. How can AdvancedKeyword help you -------------------------------- And now the advanced keyword widget with hierarchical management: .. figure:: https://github.com/redomino/redomino.advancedkeyword/raw/master/docs/resources/keywordtree.png :align: center Keywords widget powered by redomino.advancedkeyword The above image lets the keyword editor collapse/expand semantic groups of keywords, which makes it more suitable to manage large sets of keywords as you can find in a large intranet. You can also search for existing keywords through the existing tags. How does it work? ================= Hierarchy is introduced using the ``.`` (dot) character: it will be used as a keyword separator. Why are we using the dot character and not another one? Because it is little used in keywords and it is easy to type. Edit view --------- If you use correctly the . separator, you will be able to create a keyword tree similar to the following one: :: [+] what [v] [+] what.doors [v] [+] what.doors.flat [+] what.doors.profiled [+] what.furniture [-] technology [v] ... Clicking on the collapse or expand controls you can open or close keyword nodes. If you click on a keyword that is a leaf, all its parents will be selected automatically; if you unselect a node, all the sub-keywords selected are automatically deselected. So by the keyword editor you will be able to select single leafs or internal nodes. You can add new keywords using the standard Plone control: nothing has changed. If you want to add one or more keywords then type something similar to the following example: * what.furniture.outdoor * etc How keywords are shown on tagged contents ----------------------------------------- If you choose the following keywords on a particular object: * what.doors.flat * technology.combined systems the customized keywords viewlet will prompt the following links: * what (clicking on this item you will be able to see all the products) * what.doors (clicking on this item you will be able to see all the door related products) * what.doors.flat (clicking on this item you will be able all the flat doors related products) * technology * technology.combined systems This works because we provide a customized catalog indexer for keywords. In the next release a new mechanism will be provided for changing the displayed keywords. For instance, if you don't like how "technology.combinened systems" looks like, you'll be able to edit it. How to use AdvancedKeyword on an existing site ---------------------------------------------- At first you will see the javascript plugin with a plain keywords list, you should add the hierarchy level grouping keywords separated by dots characters: the Plone plugin named KeywordManager is your friend! Other features ============== Keyword map ----------- Thanks to the keywords map you 're able to see the website's arguments structure. How to see the arguments map of the site: * portal_url/@@keywordsmap Keywords portlet ---------------- This product also adds a new portlet: Keyword Portlet. In order to assign a new instance of this portlet you will have to choose a "supertag" (or a namespace tag). This supertag will be used to browse a list of all tags that are "first child" of this tag. For ex. if your portal has these two contents:: >>> doc1.Subjects() ['supertag','supertag1','supertag.subtag1','supertag1.subtag2'] >>> doc2.Subjects() ['supertag','supertag1','supertag.subtag3','supertag1.subtag4'] and if you choose 'supertag1' as parent tag, the results list will show this: * subtag2 * subtag4 These are links to the search page with a search parameter set to 'supertag.subtagX'. Here you can see the keyword portlet: .. figure:: https://github.com/redomino/redomino.advancedkeyword/raw/master/docs/resources/keywordportlet.png :align: center Keywords portlet powered by redomino.advancedkeyword (it shows a subset of existing keywords)

redomino.breadcrumbsbrain-0.4-1.lbn19.noarch

%redomino.breadcrumbsbrain is a new plugin for Plone CMS that will make it much easier to search for specific objects in a Plone-based portal or intranet by showing the breadcrumbs paths along with Titles and Descriptions in the search results. We all know that common users do not provide objects with proper titles and descriptions (sometimes they just do not provide them at all), which makes it hard to figure out if what you found is actually what you were looking for. Then you open every link in the search results to find it out, which may take you quite a time. What you actually need in a situation like this is CONTEXT. And context is what you get! redomino.breadcrumbsbrain displays the breadcrumbs of each object in the search results, helping you in figuring out what those objects are about: are they from 2010 or 2011? are they in the 'Notices' archive or in the 'News' archive? and so on. BE CAREFUL! This is not a standalone package. If you want you can call the breadcrumbs_renderer view provided by this package (for example you can insert this code into the search.pt template):: <tal:block tal:replace="structure result/@@breadcrumbs_renderer|nothing" /> This way you will be able to display where your search results items are placed.