Saravanan666/pypi-org huggingface dataset:
Package: collective.tiles.discussion
Tile for showing most recent discussion items.Features“Latest comments” tile with several fields to determine which discussion items to show.Inspiration was taken fromcollective.portlet.discussion.InstallationInstall collective.tiles.discussion by adding it to your buildout:[buildout]

...

eggs =
    collective.tiles.discussionand then runningbin/buildout.You probably want to add a tile management package as well, for exampleplone.app.mosaic.UsageCreate a Classic UI Plone Site.In the Discussion control panel globally enable comments.In the Content Settings control panel enable comments on Page, or any content type that you want.Add one or more comments.Go to the Add-ons control panel.Activateplone.app.mosaicor some other tile management package.Activatecollective.tiles.discussion.Create a page.Set its display tolayout_viewfor Mosaic.Edit the page.  The layout view should be active now.Insert a “Latest comments” tile, configure it, and save the page.Now the tile should show a list with the latests comments.Note that there is also a “Discussions” tile inplone.app.standardtiles.
This shows the comments of the current page, plus an add-form for a new comment.Filter on review statesIn the tile you can filter on review state if you want.
By default Discussion Items have only one state: published.  In this case a filter is not needed.In the Discussion control panel you can enable comment moderation.
This enables a workflow with more states.
Comments start in the pending state, and can be published, rejected, or marked as spam.Currently, in Plone 6.0.6, without filter, an anonymous user will see Discussion Items from the states published, rejected, and spam.
So you may want to explicitly filter on the published state in the tile, and possibly pending.ContributeIf you are having issues, or want to contribute a bugfix or feature, please let us know.Issue Tracker:https://github.com/collective/collective.tiles.discussion/issuesSource Code:https://github.com/collective/collective.tiles.discussionLicenseThe project is licensed under the GPLv2.ContributorsMaurits van Rees,maurits@vanrees.orgChangelog1.0.0a1 (2023-08-31)Initial release.
[mauritsvanrees]
Package: collective.tiles.githubgist
collective.tiles.githubgistThis Plone Add-On adds a tile forPloneWebsites to show GitHub Gists.Mostly HarmlessFeaturesAdds a new tile to embed GitHub Gists into a Plone website.Registers the tile forMosaic, if it is installed.InstallationInstall collective.tiles.githubgist by adding it to your buildout:[buildout]

...

eggs =
    collective.tiles.githubgistand then runningbin/buildoutContributeIssue Tracker:https://github.com/it-spirit/collective.tiles.githubgist/issuesSource Code:https://github.com/it-spirit/collective.tiles.githubgistDocumentation:https://collectivetilesgithubgist.readthedocs.ioSupportIf you are having issues, please let us know.
We have a issue tracker located at:https://github.com/it-spirit/collective.tiles.githubgist/issuesLicenseThe project is licensed under the GPLv2.ContributorsThomas Massmann,thomas.massmann@it-spir.itChangelog0.2.1 (2017-07-28)Fix pygments related imports.0.2 (2017-07-28)Add tile option to specify filename of a multifile gist.Render gist code in noscript tag.Add option to specify title level (h1 to h6)Allow inline rendering of gists using pygments syntax highlighter.0.1 (2017-06-04)Initial release.
Package: collective.tiles.iframembed
A tile which embeds external url inside an iframeFeaturesdomains validationInstallationInstall collective.tiles.iframembed by adding it to your buildout:[buildout]

...

eggs =
    collective.tiles.iframembedand then runningbin/buildoutCompatibilityPlone >= 5.2 and Python3 from version 1.0.0.For previous Plone versions, use < 1.0.0ContributeIssue Tracker:https://github.com/collective/collective.tiles.iframembed/issuesSource Code:https://github.com/collective/collective.tiles.iframembedLicenseThe project is licensed under the GPLv2.ContributorsRedTurtle Technology,sviluppoplone@redturtle.itChangelog1.0.0 (2022-11-23)Major refactoring for python 3.8 and plone 5.2
[axaroth]0.1.5 (2020-09-09)Added default domains when installing the productFixed registry.xml and upgrade process
[daniele]0.1.4 (2018-11-15)Stripped trailing slash from iframe url
[daniele]0.1.3 (2018-08-21)Fix document outline [nzambello]0.1.2 (2018-03-14)Fix dependencies
[cekk]0.1.1 (2018-02-15)Added check on query string.
[daniele]0.1.0 (2017-09-13)Initial release.
[]
Package: collective.tiles.rssmixer
This product provides a tile that can fetch RSS feeds from multiple sources and show them together.UsageThe tile has a set of parameters that allows to configure source feeds and how to render them.
You can set a list of RSS feed urls. Results will be mixed and sorted by date.TranslationsThis product has been translated intoItalianInstallationInstall collective.tiles.rssmixer by adding it to your buildout:[buildout]

...

eggs =
    collective.tiles.rssmixerand then runningbin/buildoutContributeIssue Tracker:https://github.com/collective/collective.tiles.rssmixer/issuesSource Code:https://github.com/collective/collective.tiles.rssmixerSupportIf you are having issues, please let us know.
We have a mailing list located at:project@example.comLicenseThe project is licensed under the GPLv2.ContributorsRedTurtle Technology,sviluppoplone@redturtle.itChangelog0.1.1 (2019-03-28)Added support for pat-slider [nzambello]0.1.0 (2019-03-14)Initial release.
[cekk]
Package: collective.tiles.sliders
This Plone Add-On adds a collection of slider tiles forPloneWebsites.FeaturesAdds new tiles to show slideshows in a Plone website.Registers the tiles forMosaic, if it is installed.DocumentationFull documentation for end users can be found in the “docs” folder, and is also available online athttps://collectivetilessliders.readthedocs.ioTranslationsThis product has been translated intoEnglish (source language)InstallationInstall collective.tiles.sliders by adding it to your buildout:[buildout]

...

eggs =
    collective.tiles.slidersor pull in mosaic:eggs =
    collective.tiles.sliders[mosaic]and then runningbin/buildoutContributeIssue Tracker:https://github.com/it-spirit/collective.tiles.sliders/issuesSource Code:https://github.com/it-spirit/collective.tiles.slidersDocumentation:https://collectivetilessliders.readthedocs.ioSupportIf you are having issues, please let us know.
We have a issue tracker located at:https://github.com/it-spirit/collective.tiles.sliders/issuesLicenseThe project is licensed under the GPLv2.ContributorsThomas Massmann,thomas.massmann@it-spir.itMarkus Hilbert,markus.hilbert@iham.atChangelog1.0.0 (2019-02-07)changed to version 1.0.0 as this release is no more backwards compatible.
[iham]fixed robot tests for Plone 5.1.x
[iham]removed css hacks as the break css validation and ie6/7 are of no importants anymore.
[iham]made responsive slides a pattern itself.
[iham]refactored responsive slides to become resource & bundle
[iham]refactored dynamic form resources and bundling.
[iham]add and setup extra[mosaic]to pull in mosaic in one go.
[jensens]Fixed dependency chain inmetadata.xmland reinstall of mosaic and other dependency-roundtrips.
[iham, jensens]On uninstall remove values from registry.
[jensens]Minimal contained buildout overhaul.
[jensens]Compile Resources in order to make it work with Plone 5.1.4.
[jensens]0.4 (2017-12-01)Only return link for related items, not the image (like) object itself.
[tmassman]Add link (if available) to responsiveslides.js slider.
[tmassman]Add styling for captions on responsiveslides.js slider.
[tmassman]0.3 (2017-12-01)Add custom widget for content selection.
[tmassman]Register JS resources (pattern) and bundle.
[tmassman]0.2 (2017-11-27)Remove allow_fullscreen setting.
[tmassman]0.1 (2017-11-27)Initial release.
[tmassman]Added responsiveslides.js based slider.
[tmassman]
Package: collective.tiles.unitegallery
.. This README is meant for consumption by humans and pypi. Pypi can render rst files so please do not use Sphinx features.If you want to learn more about writing documentation, please check out: http://docs.plone.org/about/documentation_styleguide.htmlThis text does not appear on pypi or github. It is a comment.==============================================================================collective.tiles.unitegallery==============================================================================Implements Unite Gallery as tile for Mosaic in PloneFeatures--------- Adds a new tile name Unite Gallery that can display a collection of images as tiles or galleryTodo----- When tiles settings will be able to display form fieldsets, add all gallery optionsInstallation------------Install collective.tiles.unitegallery by adding it to your buildout::[buildout]...eggs =collective.tiles.unitegalleryand then running ``bin/buildout``Contribute----------- Issue Tracker: https://github.com/collective/collective.tiles.unitegallery/issues- Source Code: https://github.com/collective/collective.tiles.unitegallerySupport-------If you are having issues, please let us know.License-------The project is licensed under the GPLv2.Contributors============- Martronic-SA, martronic@martronic.chChangelog=========1.0b1 (unreleased)------ Allow to set custom options (useful to introduce javascript in options like gallery_height:$(window).height()1.0a7------ Change .off('touchstart') position after gallery initialisation1.0a6------ Reuse requirejs- Add gallery.off('touchstart') to fix scroll on mobiles1.0a5-----Fix wrong requirejsDepends on collective.js.unitegallery1.0a4-----Fix break on load if folder content is not only images1.0a3-----Added some options1.0a2-----1.0a1------------------- Initial release.[Martronic-SA]
Package: collective.tinymceplugins.codemagic
IntroductionThis package adds the CodeMagic TinyMCE plugin to Plone.InstallationAdd the collective.tinymceplugins.codemagic egg to your buildout.cfg and install
using the QuickInstaller.ContributorsRichard Mitchell [mitchellrj]Changelog1.1 (2012-03-09)Fixed egg. Now includes .zcml and .xml files.1.0 (2012-03-09)Initial release.
Package: collective.tinymceplugins.embedly
IntroductionThis package adds the Embedly TinyMCE plugin to Plone.Currently based on version 2.0.9 of the source available in theWordPress.org subversion repository.This product was developed byNetsight Internet Solutions Limited. Its official repository and bug tracker
is athttp://github.com/collective/collective.tinymceplugins.embedly.InstallationAdd the collective.tinymceplugins.embedly egg to your buildout.cfg and
install using the QuickInstaller.ConfigurationTo use the Embedly plugin on your site, you need to provide an API key
(available fromembed.ly). You can set the API
key by going to Site Setup -> Configuration Registry and setting the
api_key value.UsageA video example of this product’s usage in Plone can be foundon
Vimeo.AlternativesThis product can be used alongsidecollective.embedlyandcollective.oembed.
This is the only Plone add-on product of the 3 to include full TinyMCE
integration.Dependenciescollective.tinymceplugins.embedly currently depends on version 1.3dev
or higher ofProducts.TinyMCE. This is because the
embed.ly TinyMCE plugin designed for WordPress is aimed at TinyMCE
version 3.4.5 or higher.ContributorsRichard Mitchell [mitchellrj]David Glick [davisagli]Changelog1.0.2 (2016-11-05)Fix jquery script tag to match the current protocol, to avoid mixed content when served via HTTPS.1.0.1 (2012-04-18)Fixed skin registration to be recursive.1.0.0 (2012-04-18)Initial release.Licensecollective.tinymceplugins.embedly Copyright 2012, Netsight Internet
Solutions LimitedThe embed.ly TinyMCE plugin Copyright 2010  Embedly (email:developer@embed.ly)This program is free software; you can redistribute it and/or modify
it under the terms of the GNU General Public License as published by
the Free Software Foundation; either version 2 of the License, or
(at your option) any later version.This program is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
GNU General Public License for more details.You should have received a copy of the GNU General Public License
along with this program; if not, write to the Free Software
Foundation, Inc., 59 Temple Place, Suite 330, Boston,
MA 02111-1307 USA.
Package: collective.tinymceplugins.imagebrowser
IntroductionThis is a plugin for theTinyMCEeditor for Plone.It replaces the defaultploneimageplugin in order to provide image thumbnail
browsing and a ressource library (preselected folders).How this looks likeTo add entries to the ressource library go to the tinymce controlpanel and click on the library tab.DependenciesThis product has been tested with Plone 4.1.2 and TinyMCE 1.2.8.
The supported Webbrowsers are: Chrome 10, Konqueror, Firefox 3.6/4, Safari, IE 8/9.TODOA good uninstall GS step.AuthorsJoscha Krutzki (joka)CreditsCreated on behalf of 4teamwork GmbH (http://www.4teamwork.ch)Changelog1.0b6 (2012-02-28)Fixed include path of Javascript files for compatibility with TinyMCE 1.2.9.
[Julian Infanger]1.0b5 (2011-12-21)Fixed: do not delete existing img classes
[joka]Fixed wording
[joka]1.0b4 (2011-11-24)Added english translation files
[joka]Changed message ids, default translations
[joka]Upgrade step to migrate to plone.registry
[joka]Use plone.registry instead of TinyMCE object to store image resource entries
[joka]Fixed wording
[joka]List all folders first, then all images, float only images.
[joka]Merged in Products.TinyMCE image plugin 1.2.8 (Plone 4.1).
[joka]1.0b3 (2011-06-24)Do not load TinyMCE profile as it’s applied by Plone anyway and it would
reset various settings.
[buchi]Added upgrade step to fix the category of the imaging controlpanel which was
wrongly set by previous versions loading the TinyMCE profile.
[buchi]1.0b2 (2011-06-08)Fix broken release by also including non-Python files.
[buchi]1.0b1Initial release
Package: collective.tinymceportlets
IntroductionThis product allows you to add portlets within TinyMCE.It adds a button to tiny mce to allow you to choose portlets from the normal
plone right and left columns(or any extra portlet managers available).It works by using plone.transformchain to add the portlets into the document
after it has been rendered.Only tested on Plone 4.1 but could work on other versions.On Plone 4.1, you’ll have to pin plone.formwidget.contenttree:[versions]
...
plone.formwidget.contenttree = 1.0.4
...Changelog1.0a2 (2011-10-04)Add refresh button to get the list of
portlets since I can’t know when the context
is changed with the contenttree widget always.1.0a1 (2011-10-04)Initial release
Package: collective.tinymcetemplates
Introductioncollective.tinymcetemplatesis a Plone 3 add-on that provides a TinyMCE
plugin that allows authors to inserttemplatesandsnippetsinto the page.InstallationAddcollective.tinymcetemplatesto your buildout in theeggslist, or
as a dependency in theinstall_requireslist in thesetup.pyfile
for a product that is already installed in your build. The package’s
configuration is loaded automatically by Plone.You must also install the product in Plone’s Add-on control panel.UsageContent authors can use the new Template button to insert templates into
the page.Templates are created and managed as standard Plone Pages:The Page title is used as the template titleThe Page description is used as the template description.The Page body is used as the the template content.Hint:If you don’t want templates to show up in search results, remember
that they need only be accessible to content authors at edit time. You can
thus put them in a workflow state that gives content authors access. You can
also restrict access to templates in this way: an author will not see a
template built from a Page he does not have the permission to see.To create some templates, the quickest option is to create a Folder with the
id “templates” in the root of the site and put one or more Pages in this
folder.Hint:You can tick the “exclude from navigation” button on the templates
folder to make sure it doesn’t show up in the portal tabs or navigation tree.It’s possible to set a different path for templates, and to list multiple
folders. In the configuration registry, as managed byplone.app.registry,
the template paths are listed under the keycollective.tinymcetemplates.templateLocations. This contains a tuple of
paths to pages or folders of pages, relative to the portal root. You can
also use GenericSetup to manipulate this list. Seeplone.app.registryfor
details.Working with the user’s selectionYou can insert the user’s current editor selection into your template. To do
this, you need to add a placeholder div or span with the classselcontent.
For example:<p>
You said: <span class="selcontent">(your content here)</span>
<br />
We think this is wrong!
</p>Hint:To insert this class, you can either add it as a paragraph or
character style in the TinyMCE control panel, or insert it into the markup
manually via the HTML view.When the user now inserts this template into the page, their current selection
will replace the “(your content here)” placeholder.Changelog1.0b3 - 2010-07-31Fix another release issue. Not my day with distribute/PyPI.1.0b2 - 2010-07-30Fix a slightly broken release1.0b1 - 2010-07-30Initial release
Package: collective.trajectory
Introduction============This product provides URL routing capability to Plone content. Powered by theawesome traject library by Martijn Faassen and based on a similar library calledmegrok.traject.Note: this is still a proof of concept, need more testing.What It Does=============Basically, this project allow your content to be a routing based app. For example,with this product, you can have something like:* site/folder/myApp - a traject enabled content, resolved through graphtraversal* site/folder/myApp/models/1 - returns a SQLalchemy model object, resolvedthrough url routingEnabling routing for content type==================================Hook this into ZCML::<adapter factory="collective.trajectory.components.Traverser"for="myproduct.content.mycontent.MyContentzope.publisher.interfaces.IRequest"/>where `myproduct.content.mycontent.MyContent` is the class of the contenttype which will be the root of the URL routing.Registering route patterns===========================Registering patterns is pretty much like how its supposed to be done innormal traject. However, the model class will need to be inherited from`collective.trajectory.components.Model`from collective.trajectory.components import Modelfrom myproduct.content.mycontent import MyContentimport trajectclass MyModel(Model):def __init__(self, item_id):self.item_id = item_iddef factory(item_id):return MyModel(item_id)def arguments(obj):return {'item_id': obj.item_id}pattern = u'models/:item_id'traject.register(MyContent, pattern, factory)traject.register_inverse(MyContent, MyModel, pattern, arguments)Additional Info================* The returned models acquire attributess from your MyApp object throughAcquisition, so that templates behave as it should, and portal toolsavailable through current context.* Views are simply the standard plone browserviews, nothing fancy.Changelog=========0.1 (2011-10-03)----------------- Initial release
Package: collective.transcode.recipe
A zc.buildout recipe that configures a collective.transcode.daemon instanceFor more info check outhttp://pypi.python.org/pypi/collective.transcode.daemonhttp://pypi.python.org/pypi/collective.transcode.starSupported optionsThe recipe supports the following options:listen_host
    hostname to listen

listen_port
    port to use

videofolder
    relative path of folder where transcoded videos are stored

secret
    a secret shared key used for authentication and encryption

profiles
    a python list of dicts specifying the supported transcoded
    profiles. The dict should contain
        i) the id of the profile,
        ii) the command to be executed with the first parameter to be the input and the second the output file
        iii) the list of supported mime types for this profile
    e.g. profiles = [ {'id':'low', 'cmd':'scripts/lowQualityTranscode %s %s', 'supported_mime_types': ['video/mpeg', 'video/3gpp'] } ]ContributorsDimitris Moraitis, unweb.meMike Muzurakis, unweb.meMarkos Gogoulos, unweb.meVictor Rajewski, engagemedia.orgChristos Psaltis, unweb.meChange history0.2 (2010-07-22)Release for collective.transcode.daemon 0.2
[dimo]0.1 (2010-02-18)Initial release
[dimo]Download
Package: collective.transform.creole
IntroductionThis package gives Plone users the ability to use creole wiki syntax in their Plone site.  Creole aims to be a common wiki format across all wiki engines.  Now you can use it in Plone!To see some examples of Creole wiki text take a look at the cheat sheet:http://www.wikicreole.org/wiki/CheatSheetInstallTo install collective.transform.creole with buildout do the following:[instance]
eggs = collective.transform.creole
zcml = collective.transform.creoleOnce the package is installed you can do the following:Run the ‘Creole Transform Install’ profileGo to Site setup -> markupMake sure the text/wiki+creole transform is enabledSet your default editor to ‘Plain Text’Write some wiki text!To uninstall, run the ‘Creole Transform Uninstall’ profile and remove the package from your buildout.Changelog1.1 - (2008-11-12)Handle unicode properly
[claytron]1.0 - (2008-11-08)Initial release
[claytron]
Package: collective.transform.kml
Introduction============Transform KML to HTML. It extracts the name and descrition fromthe placemarks and constructs a simple html document from this.Installation============Add ``collective.transform.kml`` to the list of eggs to install, e.g.:::[buildout]...eggs =...collective.transform.kmlRe-run buildout, e.g. with:::$ ./bin/buildoutChangelog=========0.1 (2012/06/13)-------------------- Initial release
Package: collective.transform.multimarkdown
IntroductionThis package allows Plone users to include MultiMarkdown syntax in their Plone sites. MultiMarkdown is a derivative of John Gruber’s original Markdown project.To see the improved MultiMarkdown syntax, check out theSyntax Guide.InstallTo install collective.transform.multimarkdown with buildout do the following:[instance]
eggs = collective.transform.multimarkdown
zcml = collective.transform.multimarkdownOnce the package is installed you can do the following:Run theMultiMarkdown TransformprofileGo toSite Setup->MarkupMake sure thetext/x-multimarkdowntransform is enabledSet your default editor toPlain TextWrite some MultiMarkdown!To uninstall, run theMultiMarkdown Transform Uninstallprofile and remove the package from your buildout.LimitationsThis packages makes use of the MultiMardown perl scripts to do the actual transform. If you have a copy of MultiMarkdown.pl and want to use it instead of the script included in this package, make sure it is in your PATH, and the package will find and use it.Since this packages uses perl scripts, you must have perl installed and in your PATH for the transform to work correctly. This package has only been tested on *nix and should work on most flavors of Linux and BSD. Use of this package on a Windows machine could cause errors.Changelog0.2 (2009-08-19)Fixed a few typos in license0.1 (2009-08-19) (Unreleased)Initial release
Package: collective.transform.ppt-xl
Introduction============Powerpoint and Excel to HTML transformationIt uses ppthtml and xlhtml which can be installed with e.g:::apt-get install ppthtml xlhtmlor you can obtain the sourcecode fromhttp://sourceforge.net/projects/chicago/Installation============Add ``collective.transform.ppt_xl`` to the list of eggs to install, e.g.:::[buildout]...eggs =...collective.transform.ppt_xlRe-run buildout, e.g. with:::$ ./bin/buildoutChangelog=========0.1  (2012/06/13)-------------------- Initial release