Saravanan666/pypi-org huggingface dataset:
Package: quintagroup.pingtool
Introductionquintagroup.pingtool is a simple tool to enable pinging of external feed agregators for Plone 3.1.xDEPENDS onXMLRPCMethodINSTALLATIONsee docs/INSTALL.txt for instructions.Supported Plone versionsPlone 3.1InstallationTo install quintagroup.pingtool into the global Python environment (or a workingenv), using a traditional Zope 2 instance, you can do this:Copyquintagroupfolder to the/path/to/instance/lib/pythondirectory of your Zope instance.Create a file calledquintagroup.pingtool-configure.zcmlin the/path/to/instance/etc/package-includesdirectory of your Zope instance.
The file should only contain this:<include package="quintagroup.pingtool" />Restart the Zope server, for example with the following command in the terminal:$ ./bin/zopectl restartAlternatively, if you are using zc.buildout and
the plone.recipe.zope2instance recipe to manage your project, you can do this:Addquintagroup.pingtoolto the list of eggs to install.:[buildout]
...
eggs =
    ...
    quintagroup.pingtoolTell the plone.recipe.zope2instance recipe to install a ZCML slug:[instance]
recipe = plone.recipe.zope2instance
...
zcml =
    quintagroup.pingtoolRe-run buildout, e.g. with:$ ./bin/buildoutRestart the Zope server, e.g with the following command in the terminal:$ ./bin/instance restartInstall quintagroup.pingtool with quickinstaller in Plone.Plone Development by Quintagroup, 2004-2012Changelog1.1.3 (2009-03-05)Added adapters and utilitiesAdded uninstall configletAdded modified tests1.1.0 - 09-02-2009Added integration with Outbound Syndication (Vice)1.0.0Created package quintagroup.pingtool based on product qPingTool
(http://svn.quintagroup.com/products/qPingTool/trunk).ConvertedExtension/Install.pyinto a complete GenericSetup profile.Updated tests to run with Plone 3.x.General code cleanup and modernization.Added form for setup links of feed.0.3Pingtool migrated to ATCTAdded adapter for operating with canonicalURL property
in Plone root and added ‘overview’ tab to portal_pingtool
for operation with mentioned propertyInstallation correctedfixed some issues0.2   05-05-2005reviewed ping specsadded default sites to be pingedqPingTool works only with SimpleBlog currently0.1initial release
Package: quintagroup.ploneformgen.readonlystringfield
IntroductionReadonly FormGen String Field (quintagroup.ploneformgen.readonlystringfield) is
a Plone product that allows to add Readonly String Field to the form, created
with PloneFormGen product.UsageAdd Readonly String Field as a usual String Field to PloneFormGen form.Insert ‘Default Value’ or ‘Default Expression’ expression, that will be
evaluated when the form is displayed to get the field default value.That value will be displayed on every form submission as a default value,
but will not be editable.If under some circumstances you need to make readonly field editable, then
set appropriate condition in Edit Mode field.Supported Plone versions3.xDependenciesPloneFormGenAuthorsVitaliy Podoba -piv@quintagroup.comPython development by Quintagroup, 2004-2012Changelog0.2 - March 24, 2009Updated documentation accordingly to changes in readonly field functionality.
[piv]Added tests.
[piv]Added uninstall procedure.
[piv]Removed editable mode from read only field for anonymous user, made this
functionality as optional feature by means of edit mode tal expression field.
[piv]Added Products.PloneFormGen as egg requirement and as installation
dependency.
[piv]Formatted documentation as reStructuredText.
[piv]0.1 - October 31, 2008Initial release.
[piv]
Package: quintagroup.portlet.cumulus
quintagroup.portlet.cumulusis a Plone product that allows you to add tag cloud
portlets to your Plone site. Your site’s tags (content categories are used as
tags) are displayed using a Flash movie that rotates them in 3D. It works just
like a regular tags cloud, but is more visually exciting. This is the WordPress
WP-Cumulus plugin ported to Plone as a portlet.When you add this portlet anywhere in the site it will display all site’s tags.
If you have installed QuillsEnabled product this portlet will display only blog’s
tags when rendered inside blog.Plone Development by Quintagroup, 2004-2012LinksHome pageRepositoryDocumentation and examplesUsageOn the page you want to add such portlet go to portlet management area and select
‘Tag Cloud (cumulus) portlet from Add portlet… drop-down menuProvide your own values for portlet configurationSave changesThe portlet will now display a cloud of keywords/tags used on your Plone site.Cumulus Portlet optionsIt is possible to set cumulus portlet options so that it fits your site design, color
scheme etc. When you create cumulus portlet you can specify:Width and height of the flash tag cloud portletSmallest and largest tag sizeMain and optionally second color of the tags for creating multi-colored tag cloudOptional highlight color when mouse is over it and background portlet colorTransparent or compatibility modeRotation speedSupported Plone versionsPlone 4.1Plone 4.0Plone 3.xInstallationAddquintagroup.portlet.cumulusto the list of eggs to install, e.g.:[buildout]
...
eggs =
    ...
    quintagroup.portlet.cumulusTell the plone.recipe.zope2instance recipe to install a ZCML slug:[instance]
recipe = plone.recipe.zope2instance
...
zcml =
    quintagroup.portlet.cumulusRe-run buildout, e.g. with:$ ./bin/buildoutRestart instance, e.g. with:$ ./bin/instance restartInstall Tag cloud (cumulus) portlet with Quickinstaller in Plone.Changelog1.2 (2012-02-24)Implemented max. number of tags to be displayed (Suresh V)1.1.1 (2011-10-28)Compatibility with Plone 4.1 added1.1.0 (2011-01-04)Fresh tagcloud.swf added, with proper unicode support1.0 (2009-04-24)Initial release
Package: quintagroup.portletmanager.footer
IntroductionThis package adds portlet manager in the page footer.Supported Plone version3.xAuthorBohdan KovalPlone Development by Quintagroup, 2004-2012support@quintagroup.com* quintessence of modern businessInstallationTo install quintagroup.portletmanager.footer into the global Python environment (or a workingenv),
using a traditional Zope 2 instance, you can do this:Copyquintagroupfolder to the/path/to/instance/lib/pythondirectory.Create a file calledquintagroup.portletmanager.footer-configure.zcmlin the/path/to/instance/etc/package-includesdirectory. The file should only contain this:<include package="quintagroup.portletmanager.footer" />Restart the Zope server, for example, with the following command in the terminal:$ ./bin/zopectl restartInstall this products with QuickInstaller in PloneAlternatively, if you are using zc.buildout and the plone.recipe.zope2instance
recipe to manage your project, you can do this:Addquintagroup.portletmanager.footerto the list of eggs to install, e.g.:[buildout]
...
eggs =
    ...
    quintagroup.portletmanager.footerTell the plone.recipe.zope2instance recipe to install a ZCML slug:[instance]
recipe = plone.recipe.zope2instance
...
zcml =
    quintagroup.portletmanager.footerRe-run buildout, e.g. with:$ ./bin/buildoutRestart the Zope server, for example, with the following command in the terminal:$ ./bin/instance restartInstall this products with QuickInstaller in PloneChangelog0.1 (2009-10-06)Initial release
Package: quintagroup.portlet.static
quintagroup.portlet.staticquintagroup.portlet.static is a Plone product that allows you to add stylished
static text portlets to your Plone site. Static Stylish Text portlets are
usual Plone Static Text portlets with certain HTML classes assigned.Static Stylish Text portlets can be used in those cases when you need to have
several static text portlets be displayed in different ways. For this,
go to Site Setup -> Add-on Products Configuration -> Static Stylish portlet
(www.yoursite/@@staticstylishportlet-controlpanel). In Static Stylish portlet
settings area create HTML classes and specify CSS styles for those HTML
classes in the corresponding CSS file. These classes will be available for
you in a Portlet style drop down menu on static stylish text portlet add/edit form.UsageSelect Static Stylish text portlet from Add portlet drop-down menuProvide content to be displayed on the portlet [as you would do for
usual Plone static text portletsChoose a portlet style for the portlet from the list of available HTML
classes.Save changesSupported Plone versionPlone 4.xPlone 3ContributorsVitaliy PodobaRoman KozlovskyiMalthe BorchVolodymyr MaksymivCopyright (c) “Quintagroup”:http://quintagroup.com, 2011InstallationIn buildout.cfg file of your instance:Addquintagroup.portlet.staticto the list of eggs to install, e.g.:[buildout]
...
eggs =
    ...
    quintagroup.portlet.staticTell the plone.recipe.zope2instance recipe to install a ZCML slug:[instance]
...
zcml =
    quintagroup.portlet.staticRe-run buildout, e.g. with:$ ./bin/buildoutRestart the Zope server, for example, with the following command in the terminal:$ ./bin/instance restartInstall ‘Static Stylish Portlet’ via Site Setup -> Add-onsChangelog0.7 - March 29, 2012Added z3c.autoinclude directives.
[potar]0.6 - January 05, 2012Changed option to display portlet for anonymous users only to
instead two settings respectively requiring and excluding users with
a given role (from a set of roles), e.g. “Member”.0.5 - September 26, 2011Added option to display portlet for anonymous users only.0.4 - August 31, 2011Plone 4.1 compatibility added0.3 - September 03, 2010Fixed support with plone.portlet.static 2.0 [kroman0]0.2 - June 04, 2010Fixed MANIFEST.in [kroman0]0.1 - February 25, 2009Initial release
Package: quintagroup.robotframework.utils
Quintagroup robotframework utilsData file parserDatafile library provides more convenient way to save some of your test
data than robotframework variables tables do.For example you have a file ‘users.rst’ where you save users accounts information:**Accounts on site**

=========  ====  ========  =================
users      id    password  email
=========  ====  ========  =================
admin      Eric  passwr    eric@example.com
manager    Jonh  passwr    jonh@example.com
publisher  Olga  passwr    olga@example.com
reader     Jane  passwr    _table_:
\                          work; jane@work.com|
\                          pesonal; jane@pesonal.com
=========  ====  ========  =================and in test case you can parse this file and access its data in the following manner:*** Settings ***
Library         quintagroup.robotframework.datafile.rst

*** Test Cases ***
Attribute alike access
    ${users}=  Read tables from file  ${CURDIR}/users.rst
    Should Be Equal  ${users.admin.id}  Eric
    Should Be Equal  ${users.manager.email}  jonh@example.com
    Should Be Equal  ${users.reader.id}  Jane
    Should Be Equal As String  ${users.reader.email}  [['work', 'jane@work.com'], ['pesonal', 'jane@pesonal.com']]
    Should Be Equal As String  ${users.reader.email}[0]  ['work', 'jane@work.com']Changelog1.0 (2013-12-16)Initial release
Package: quintagroup.slidertemplates
Quintagroup.slidertemplates===========================Enhanced Responsive Views for NG Collection Portlet (Carousel, Shelf, Tabs).. figure:: http://quintagroup.com/services/plone-development/products/quintagroup.slidertemplates/quintagroup.slidertemplates-logo.pngIntroduction------------The product can be used to add new responsive views for NG Collection Portlet. quintagroup.slidertemplates adds several templates: Carousel, Shelf, Vertical and Horizontal Tabs, qgCarousel, and contentSlider that can customize portlet display. Now you do not need to involve developer to use several custom views with collective.portlet.ngcollection. Just assign different view for each newly created portlet via it's Edit form.Usage-----quintagroup.slidertemplates is simple in usage, just follow the steps:* Go to /@@manage-portlets link on the desired page.* Choose NG Collection Portlet from the "Add portlet..." drop-down menu.* Add any previously created collection.* Choose one of the offered templates: carousel, shelf, vertical or horizontal tabs.* Save portlet.Find more information at http://quintagroup.com/services/plone-development/products/quintagroup.slidertemplates.Supported Plone versions:-------------------------PLone 5.0Changelog=========1.5 August 20, 2015--------------------- Fixed resource registation and fixed js files for plone 5 [roman.ischiv]1.4 August 20, 2015--------------------- Initial release for Plone 5 [roman.ischiv]1.3.2 May 12, 2015--------------------- Fixed script for contentCarousel [roman.ischiv]1.3.1 March 27, 2015--------------------- Fixed script for qgCarousel, added var 'gap' for item [roman.ischiv]1.3 March 18, 2015-------------------- Fixed script for qg carousel [roman.ischiv]1.2 January 29, 2015-------------------- Fixed templates for horizontal and vertical tabs [roman.ischiv]1.1 January 26, 2015-------------------- Added qgCarousel and contentSlider template [roman.ischiv]1.0dev (unreleased)-------------------- Initial release
Package: quintagroup.substyle
IntroductionStyles for site subsections.Changelog1.3 (Nov 21, 2013)Added support all portal types [kroman0]1.2.1 (Apr 24, 2013)fixed documentation [kroman0]1.2 (Apr 24, 2013)set style for all ATContentTypes [kroman0]added substylestemplate property [kroman0]added tests [kroman0]1.1.1 (Dec 16, 2011)typo fixed1.1 (Dec 15, 2011)Fixed variables namespep8 test passed1.0 (Aug 11, 2011)Initial release
Package: quintagroup.sunrain.policy
SunRain Policy is a theme extension forSunRain diazo Plone themeby Quintagroup.FeaturesAdds four actions for subscription: ‘Share on Twitter’, ‘Share on Facebook’, ‘Send this’ and ‘Subscribe to RSS’.
Their links can be edited via ZMI portal_actions -> subscribe.InstallationSee docs/INSTALL.txt file for detailed installation instructions.WARNINGBe careful when doing product reinstall. In case you need to reinstall SunRain Policy for any reasons - note that your custom actions will disappear and demo actions will appear instead.AuthorsTaras PeretiatkoQuintagroup:http://quintagroup.com, 2006-2012Installationquintagroup.sunrain.policy can be installed in any of the following ways.Installation via buildoutIn the buildout.cfg file of your instance:Addquintagroup.sunrain.policyto the list of eggs to install, e.g.:[buildout]
...
eggs =
    ...
    quintagroup.sunrain.policyRe-run buildout:$ ./bin/buildoutRestart the Zope server:$ ./bin/instance restartThen activate ‘SunRain Policy’ in Plone (Site Setup -> Add-ons).Installation: development modeIf you want to customize SunRain Policy please use the following installation instructions:downloadquintagroup.sunrain.policy-version.ziparchive fromhttp://pypi.python.org/pypi/quintagroup.sunrain.policyextract product archive to getquintagroup.sunrain.policy-versionfolder. Remove version from
folder name to havequintagroup.sunrain.policyfolderputquintagroup.sunrain.policyfolder intosrcdirectory of your buildoutin buildout.cfg file of your buildout addquintagroup.sunrain.policyto the list of eggs you are developing and  to the list of eggs to install:[buildout]
...
develop = src/quintagroup.sunrain.policy
...
eggs =
    ...
    quintagroup.sunrain.policyRe-run buildout:$ ./bin/buildoutStart instance in development mode:$ ./bin/instance fgInstallSunRain Policyin Plone (Site Setup -> Add-ons).Now you can customize SunRain Policy by modifyingquintagroup.sunrain.policypackage insrcdirectory
of your buildout.Changelog1.0 - May 18, 2012Initial release [naivok]1.0dev (unreleased)
Package: quintagroup.theme.lite
Lite Plone ThemeLite is a free diazo theme for Plone 4.FeaturesReplaceable logo as in default Plone: customize portal_skins -> sunburst_images -> logo.pngEditable footer as in default Plone: customize portal_view_customizations -> plone.footerImproved thumbnail display view (switch to Thumbnail view)Additional FeaturesFeatures, that are supported and can be activated by additional packages installation:quintagroup.dropdownmenu. Adds custom-style dropdown menuProducts.Carousel. Adds rotating Carousel banner featureProducts.LinguaPlone. Adds multilingual functionality. Custom-style language selectors.Products.PloneFormGen. Adds TTW Form Generator feature.Products.ContentWellPortlets. Allows adding portlets in the header, footer and content areaRecommendedTheme was tested with:Plone 4.1plone.app.theming 1.0b9quintagroup.dropdownmenu 1.2.5Products.LinguaPlone 4.1.1Products.Carousel 2.1Products.PloneFormGen 1.7.0Products.ContentWellPortlets 4.1.0Dependenciesplone.app.themingHome Directoryhttp://skins.quintagroup.com/liteAuthorsTaras PeretiatkoYuriy HvozdovychVolodymyr RudnytskyyPlone Themes by Quintagroup, 2006-2012Installationquintagroup.theme.lite can be installed in any of the following ways.Installation via diazo panelDownload zip file athttp://plone.org/products/lite-plone-skin/releases/6.0.4/lite.zipImport the theme at the ‘Diazo theme’ control panelInstallation via buildoutIn the buildout.cfg file of your buildout:Addquintagroup.theme.liteto the list of eggs to install:[buildout]
...
eggs =
    ...
    quintagroup.theme.liteRe-run buildout, e.g. with:$ ./bin/buildoutRestart the Zope server, e.g with the following command in the terminal:$ ./bin/instance restartOn your Plone site go to Site Setup -> Add-ons and activateLite Theme.Installation in development modeIf you want to customize Lite theme please use the following installation instructions:downloadquintagroup.theme.lite-version.ziparchive fromhttp://pypi.python.org/pypi/quintagroup.theme.liteextract theme archive to getquintagroup.theme.lite-versionfolder. Remove version from
folder name to havequintagroup.theme.litefolderputquintagroup.theme.litefolder intosrcdirectory of your buildoutin buildout.cfg file of your buildout addquintagroup.theme.liteto the list of eggs you are developing and to the list of eggs to install:[buildout]
...
develop = src/quintagroup.theme.lite
...
eggs =
    ...
    quintagroup.theme.liteRe-run buildout:$ ./bin/buildoutStart instance in development mode:$ ./bin/instance fgInstallLite Themein Plone (Site Setup -> Add-ons).Now you can customize Lite Theme by modifyingquintagroup.theme.litepackage insrcdirectory
of your buildout.Changelog6.0.4 - January 20, 2012Products.PloneFormGen compatibility added6.0.3 - December 29, 2011removed plone.app.themingpluging dependency6.0.2 - November 22, 2011unnecessary css dropped6.0.1 - November 02, 2011added base tagportal-top source URL fixed6.0 - October 24, 2011theme package converted into diazo theme4.0.2 - July 29, 2011compatibility with Plone 4.1 added4.0.1 - June 8, 2011added dependency for plonetheme.classicbullets source URL fixed4.0 - Mar 31, 2011theme updated to Plone 4
Package: quintagroup.theme.pythonreel
SeeREADME.rston github.Installationquintagroup.theme.pythonreel can be installed in any of the following ways.Installation via diazo panelDownload zip file athttp://plone.org/products/pythonreel-plone-theme/releases/1.1/pythonreel.zipImport the theme at the ‘Diazo theme’ control panelInstallation via buildoutIn the buildout.cfg file of your instance:Addquintagroup.theme.pythonreelto the list of eggs to install:[buildout]
...
eggs =
    ...
    quintagroup.theme.pythonreelRe-run buildout:$ ./bin/buildoutRestart the Zope server:$ ./bin/instance restartThen activate ‘Python Reel Theme’ in Plone (Site Setup -> Add-ons).Installation: development modeIf you want to customize Python Reel Theme please use the following installation instructions:downloadquintagroup.theme.pythonreel-version.ziparchive fromhttp://pypi.python.org/pypi/quintagroup.theme.pythonreelextract theme archive to getquintagroup.theme.pythonreel-versionfolder. Remove version from
folder name to havequintagroup.theme.pythonreelfolderputquintagroup.theme.pythonreelfolder intosrcdirectory of your buildoutin buildout.cfg file of your buildout addquintagroup.theme.pythonreelto the list of eggs you are developing and  to the list of eggs to install:[buildout]
...
develop = src/quintagroup.theme.pythonreel
...
eggs =
    ...
    quintagroup.theme.pythonreelRe-run buildout:$ ./bin/buildoutStart instance in development mode:$ ./bin/instance fgInstallPython Reel Themein Plone (Site Setup -> Add-ons).Now you can customize Python Reel Theme by modifyingquintagroup.theme.pythonreelpackage insrcdirectory
of your buildout.Changelog1.5.4 August 21, 2015Fixed diazo rules for favicons [roman.ischiv]1.5.3 June 05, 2015Fixed styled for navigation on mobile screen [roman.ischiv]1.5.2 May 26, 2015updated styles for new versions[1.3.1] of quintagroup.dropdownmenu product [roman.ischiv]1.5.1 April 21, 2014Fixed styles for new versions of quintagroup.slidertemplates and quintagroup.megamenu products [roman.ischiv]1.5 December 29, 2014Fixed rules for panels in portal-top [roman.ischiv]1.4 December 12, 2014Added style for megamenu and slidertemplates products [roman.ischiv]Remove “_” from name in scss file in theme in order to avoid errors when copy and modifying theme [roman.ischiv]1.1 March 18, 2013Plone 4.3rc1 compatibility added [naivok]Update portlet navigation style [naivok]1.0.1 January 22, 2013added fixes for Plone 4.2.3 [naivok]added pythonreel_expanded.css [serg]1.0 December 21, 2012Initial release [naivok]
Package: quintagroup.transmogrifier
Export/import transmogrifier blueprintsThis package contains blueprints for collective.transmogrifier
pipelines, that may be used to export/import Plone site content.
It also overrides GenericSetupContentstep so this package
can be used out-the-box to migrate site content.LinksDocumentation and examples:http://projects.quintagroup.com/products/wiki/quintagroup.transmogrifierCreditsDesign and developmentBohdan KovalAndriy MylenkyyTaras MelnychukVitaliy StepanovVitaliy PodobaVolodymyr CherepanyakMyroslav OpyrTom LazarMaurits Van ReesLaurence RoweMikko OhtamaaTom GrossChangelog0.5 (23-08-2013)Fixed export of Blobs
[tom_gross]Allow exporting of Plone sites not in ZODB root
[tom_gross]Port xml.minidom to lxml
[tom_gross]Plone 4.3 compatibiltyApply patch which fixes import of tarballs not available in Plone 4.2
[tom_gross]Be more failsafe in pathological situations
[tom_gross]Use regex to similarize xml in tesrs on Python 2.6 and 2.7
[tom_gross]0.4 (21-04-2011)Multiple path export support added to sitewalker
[chervol]Collection criteria export added for catalog source
[chervol]Simple transformation fallback added for straight forward type substitution
scenario, correspondent test updated
[chervol, kroman0]cmfns cleanup, local_roles override due to unicode errors
[chervol]Allowed types acquisition case switch added
[chervol]Yield items in manifest order from manifest importer section.
[elro]Add an OrderedDict implementation.
[elro]Walk the folder structure breadth first (sort of) in reader section.
[elro]Set import context as an annotation on transmogrifier.
[elro]In the marshaller sections, make sure the path is a string, as it
fails on unicode (and paths should be ascii strings).
Fixeshttp://plone.org/products/quintagroup.transmogrifier/issues/1[maurits]If you only want to export a part of the site, you can specify a
start-path in the sitewalker section; use ‘folder’ to only export
‘/plonesite/folder’.
[maurits]Only patch Generic Setup when Python is < 2.6. [elro]Add the _export_context to the item always so other section may use it even
if there is no _files key. [elro]Add content type sniffing to the WriterSection. [elro]Added z3c.autoinclude entry point so that zcml slug is no longer needed.
Unfortunately I have no permissions to update documentation regarding this [miohtama]Fix issue of using path index with catalogsource [miohtama]0.3 (2010-09-07)Plone4 compatibility [tomster, csenger]updated tests for Plone4 and Plone3 [fenix, liebster]added sections for export/import of portlet assignments [koval]0.2 (2010-01-04)the “quintagroup.transmogrifier” namespace removed [koval]added interface import/export steps [mylan]merged plone21 branch [piv]various fixes [piv, mylan, koval]history update, release [chervol]0.1 (2009-11-19)Initial release