Saravanan666/pypi-org huggingface dataset:
Package: collective.folderlogo
collective.folderlogo changes logo images and their background under plone site or folders easily through the web.Currently tested withPlone-4.3 [taito]For older versions and python-2.6, use version 0.4.1.How ToAfter installing throughSite Setup–>Addons,
add Image with IDlogounder plone site or whatever folder you want to change logos.Changing ID of imagesGo toConfiguration registrypage fromSite Setup.UpdateLog ID,Background ColorandBackground Image IDfrom here.Background ColorNeeds to be available for CSS styling background-color like:transparent,#ffffff.Changelog1.2 (2013-05-06)Moved test packages to extras_require. [taito]Tested with Plone-4.3. [taito]Added testing integration to Travis CI. [taito]1.1 (2012-11-14)Tested with Plone-4.2.2. [taito]1.0 (2012-08-06)Configuration moved from properties to registry records. [taito]Dropped support for Python-2.6. [taito]0.4.1 (2011-04-21)Browser layer added. [taito]0.4.0 (2011-04-15)Background image and color configuration is added. [taito]0.3.1 (2011-03-29)Initial release. [taito]CreditsThe Finnish Association for Nature Conservation (Suomen Luonnonsuojeluliitto).
Package: collective.folderposition
Extended ordering controls for folder contents.InstallationPlone 4Add package to your instance’s eggs:[instance]
eggs +=
    collective.folderpositionPlone 3.xWithout z3c.autoinclude, you must add the package to both eggs and zcml:[instance]
eggs +=
    collective.folderposition
zcml +=
    collective.folderpositionChangelog1.0 - 2010-12-14Keep checked checkboxes checked across submissions.1.0b4 - 2010-12-14Recalculate the delta select box on focus incase kss updates the table.1.0b3 - 2010-12-13Return to previous page after submission.Fix error when moving Up/Down.1.0b2 - 2010-12-13Supply subset_ids to interact correctly with batching.1.0b1 - 2010-12-10Initial release.
Package: collective.forgetit
ContentsIntroductionContributorsChangelogIntroductioncollective.forgetit removes residue of Products that have been removed.
It will not delete your content objects. Use the ZMI for that.
It will not remove persistent utilities. Use wildcard.fixpersistentutilities for that.
collective.forgetit aims to remove traces in the other locations, one
of them being the catalog from zc.relation, where a removed interface
can create havoc.While collective.forgetit does not remove your content objects, it removes other information that might have been of value. Be sure that you really don’t want to reinstall the package/Product again to reuse your old content!Currently, collective.forgetit only handles residue in zc.relation catalogs.ContributorsPatrick Gerken, Original authoreChangelog0.0.1 (2012-09-21)Initial release
[do3cc]
Package: collective.formlib.link
OverviewThis package provides a schema field that combines an internal and
external link representation. It’s relatively low-tech.It provides a widget that lets users enter links on the format:``"Title":internal path or URI:"Description"``Both title and description are optional. If an internal path is given,
the field tries to resolve the object and stores only its UID.RequirementsZope 2.10.4+UsageInclude the ZCML-slug for the package to register the widget with
formlib.A schema definition for a field carrying a single link:>>> from collective.formlib.link.field import Link
>>> field = Link(title=u"Link")A list of link fields:>>> from zope import schema
>>> field = schema.List(
...     title=u"Links",
...     value_type=Link)To render the link from a page template:<a tal:attributes="href link/@@absolute_url;
                   title link/description"
   tal:content="link/pretty_title_or_uri" />Releases0.2 (2011-07-01)Fixed an issue with the link packing routine.
[malthe]0.1 (2008-02-29)Initial public release.
Package: collective.formtoy
IntroductionThis package allows you to experiment with the Zope 2 publisher’s marshalling features, as described here:http://docs.zope.org/zope2/zdgbook/ObjectPublishing.html#marshalling-arguments-from-the-requestcollective.formtoy InstallationIf you are using zc.buildout and the plone.recipe.zope2instance
recipe to manage your project, you can do this:Addcollective.formtoyto the list of eggs to install, e.g:[instance]
...
eggs =
    ...
    collective.formtoyRe-run buildout, e.g. with:$ ./bin/buildoutChangelog1.0.0 - (2012-04-06)Clean up package
[aclark]0.2 - 07/13/2010Fix up docs0.1 - 07/13/2010Initial release
Package: collective.formwidget.mathjax
ContentsIntroductionTODOCREDITSContributorsChangelogIntroductionThis package adds a widget to z3cform widgets so you can have a textarea field with a TeX Preview div on the edit form.It also loads the MathJax on the registry so it’s not necessary to have collective.mathjaxTODOPulish the js on the edit formTestsLoad needed script.js only on edit of a type that has this kind of widgetCREDITSSponsored by Barcelona Tech University
Developed by Iskra Desenvolupament SCCL (Iskra.cat)ContributorsRamon Navarro, Original AuthorChangelog1.0-dev (unreleased)Initial import
[ramon]
Package: collective.formwidget.uberselect
OverviewThis package provides a query source compatible withz3c.formwidget.querywhich combines to an uberselection widget for
thez3c.formform generation framework.The native value type for the widget is Archetypes UID collections.Example:>>> from collective.formwidget.uberselect.archetypes import \
...     ArchetypesContentSourceBinder>>> class ISelection(interface.Interface):
...     items = schema.Set(
...         title=u"Selection",
...         description=u"Search for content.",
...         value_type=schema.Choice(
...             source=ArchetypesContentSourceBinder()
...         )
...     )Weak referencesA recipe to store references aspersistent.wref.WeakRefinstead of
UID is to use theuid2wrefadapter between the form and the
context.>>> from collective.formwidget.uberselect.wref import uid2wref>>> Factory = uid2wref(ISelection['items'])To store weak references instead of UIDs you would register such a
factory as a component adapting the context. The factory automatically
provides the interface which defines the field.
Package: collective.freeze
Tell me what your product doesFeaturesCan be bullet pointsExamplesThis add-on can be seen in action at the following sites:
- Is there a page on the internet where everybody can see the features?DocumentationFull documentation for end users can be found in the “docs” folder, and is also available online athttp://docs.plone.org/foo/barTranslationsThis product has been translated intoKlingon (thanks, K’Plai)InstallationInstall collective.freeze by adding it to your buildout:[buildout]

...

eggs =
    collective.freezeand then runningbin/buildoutContributeIssue Tracker:https://github.com/collective/collective.freeze/issuesSource Code:https://github.com/collective/collective.freezeDocumentation:https://docs.plone.org/foo/barSupportIf you are having issues, please let us know.
We have a mailing list located at:project@example.comLicenseThe project is licensed under the GPLv2.ContributorsJian Aijun,jianaijun@gmail.comChangelog1.0a1 (unreleased)Initial release.
[]
Package: collective.fullcalendar
collective.fullcalendarcollective.fullcalendar is an implementation ofhttps://fullcalendar.io/into classic UI Plone.FeaturesFolderish content items and Collections can be turned into calendarsTranslationsThis product has been translated intoGermanEnglishNorwegianContributeIssue Tracker:https://github.com/collective/collective.fullcalendar/issuesSource Code:https://github.com/collective/collective.fullcalendarContributorsWerkbank GmbH,mail@werkbank.deKatja Süss,k.suess@rohberg.chPhilip Bauer,bauer@starzel.deChangelog1.2 (2023-07-04)Remove invalid python_requires.
[pbauer]Add norwegian translation.
[espenmn]Add CSS class for publication class. CSS class will be ‘state-published’, etc..
[espenmn]Fix: have get_events return recurring events.
[witch]1.0b2 (2021-12-11)Fix support for folders.
[pbauer]Support custom collection-types.
[pbauer]Ignore limit and batching in collections.
[pbauer]Do not calculate events twice.
[pbauer]1.0b1 (2021-11-22)Make own form for adding new events
[wkbkhard]Fix add-link location
[pbauer]Add setting: custom event type
[ksuess]Fix whole day events
[ksuess]Use default-settings from schema.
[pbauer]Switch view on enable and disable
[pbauer]Remove german phrases
[wkbkhard]1.0a3Enhance installation profiles and resources
[wkbkhard, ksuess]Add fullcalendar to collections
[wkbkhard]Adding events over calendar with normal AddForm possible
[wkbkhard]1.0a2Changing programming of configuration
[wkbkhard]Disable fullcalendar behavior (still there, but not directly installed)
[wkbkhard]Add fullcalendar interface with AnnotationAdapter with possibility to enable/disable calendar by action
[wkbkhard]1.0a1Initial release.
[wkbkhard]
Package: collective.fullview
IntroductionThis package provides an alternative full view for Plone with support for
BrowserViews. BrowserViews weren’t fully supported in the skin layer based
folder_full_view Page Template. This package provides a @@full_view view.This package fixes: “Error when view folder with folder_full_view view”http://code.google.com/p/dexterity/issues/detail?id=172AuthorJohannes Raggam, BlueDynamics Alliance <raggam-nl [at] adm [dot] at>Changes1.3 (2013-11-23)Register “en” and “de” translations.
[thet]1.2 (2013-02-06)Allow recursive expansion of full_view views.
[thet]1.1.1 (2013-01-18)Fix pfg_prefix for PloneFormGen forms to really return a unique prefix per
form in a full_view.
[thet]1.1 (2013-01-16)Render PloneFormGen FormFolder not via the content-core macro but via an
@@embedded view.
[thet]1.0 (unreleased)Initial release.
Package: collective.funkbot
IntroductionThis package has been done start duringsprint@ploneconf2009. The goal is first
to provide nighly load tests to Plone. The other goal is to be able to do the same
on any other Plone project fast.Using buildbot and funkload together, allow you to have feedbacks about
performance impact done by your last code modifications every day in mail or ttw.ContentsIntroductionCreditsHow to use itWhere things areTODOChangelogCreditsPlanet Makina CorpusContact usHow to use itFirst the process:Create a new funkbot project (projectname, vcs type, vcs address of the buildout)Go inside, init the buildout (buildout init or python bootstrap.py)launch the buildout will install buildbot and funkloadlaunch master and slave daemonsConnect your webbrowser tohttp://localhost:9080Ask a force rebuild will launch the build of your project.Now the command line:paster create -t funkbot plone4virtualenv plone4cd plone4source bin/activateeasy_install zc.buildoutbuildoutmaster start && mycomputer startfirefoxhttp://localhost:9080Where things areThe main things to understand is that you are creating a buildbot. So the first buildout doesn’t build
the project. It build the buildbot that will build the project (sic).TODOadd static for serving funkload reports ttw (in progress)send mail at the end of tests with funkload reports insideChangelog1.0 - 2009-11-01Initial release [toutpt]Paste template to create a buildbot that trigger funkload [toutpt]
Package: collective.futures
collective.futuresThis is a collective package for providing yet another
way to do asynchronous (non-blocking) processing on Plone.This time we speak in terms of promises and futures:
promises are asynchronously run functions, which provide
their results as requested futures for add-on your code.A major differences for any other alternatives is that this
does not require any additional services, but requires only
Plone running on top of a Zope instance.A major limitation is that the asynchronously executed
code cannot access the database in any way (or you may
face unexpected consequences). Also, this brings no benefits
with HAProxy and fixed amount current requests per instance.ExamplefromProducts.Five.browserimportBrowserViewfromcollectiveimportfuturesdefmy_async_task(*args):# a lot of time consuming async processingreturnu'my asynchronously computed value'classMyView(BrowserView):def__call__(self,*args):try:returnfutures.result('my_unique_key')exceptfutures.FutureNotSubmittedError:futures.submit('my_unique_key',my_async_task,*args)returnu'just a placeholder value'orfromProducts.Five.browserimportBrowserViewfromcollectiveimportfuturesdefmy_async_task(*args):# a lot of time consuming async processingreturnu'my asynchronously computed value'classMyView(BrowserView):def__call__(self,*args):returnfutures.resultOrSubmit('my_unique_key',u'placeholder value',my_async_task,*args)ExplanationThis package uses approach, which kind of splits a single
request into two separate passes:Whenever some add-on code
requires a value to be computed asynchronously, it
tries to request for a named future result at first and only then
submits a promise function to compute result for that future.If any futures are submitted, the initial response is never
published, but instead the current transaction is aborted
and the submitted promise functions are executed in
parallel threads separate from the default Zope threads
(or even in parallel processes) and
their return values are collected
(see also the documentation ofconcurrent.futuresin Python).When all promise functions have been resolved, the original request
is cloned, resolved values are set as futures and a new
internal request is dispatched.After this second pass, the add-on code can use
the now available futures, not submit more futures, and
finally, the response is published all the way to
the browser.For more background information:http://datakurre.pandala.org/2014/05/asynchronous-stream-iterators-and.htmlChangelog0.9.3 (2018-09-05)Fix issue where plone.protect tried to parse PromiseWorkerStreamIterator as
xml
[datakurre]0.9.2 (2018-06-29)Add to log exceptions within futures to get full exception stacktraces
[datakurre]0.9.1 (2016-05-25)Fix issue where resolved futures were not passed for nested requests
[datakurre]0.9.0 (2014-10-23)First release.
Package: collective.gacontext
Author:ramonskiDate:2008-03-20Revision:60988AbstractAdd Google Analytics context dependent to your Plone SiteIntroductionGoogle Analytics can cope with different URLs of a site, e.g. withhttp://plone.organdhttp://plone.org/products. So if you have a hierarchical
structure of your site and you want to analyze it with Google Analytics, you
need different ga-code-snippets per URL. With this package you can handle it.UsageThere is a formlib form registered on the interfacecollective.gacontext.interfaces.IGAContextMarker. Each context which is
marked with that Interface becomesGoogle Analyticsaware. A new object
tab is displayed where you can edit a ga-code-snippet.A viewlet, registered for PortalFooter, will find the responsible code snippet
for it. It calls a utility which walks the acquisition chain up for the next
object which provides the IGAContextMarker Interface and returns its code
snippet (if there is one set).Example:http://plone.orgis  marked withIGAContextMarkerand has the following ga code:<script src="http://www.google-analytics.com/urchin.js" type="text/javascript">
</script>
<script type="text/javascript">
_uacct = "UA-00000-0";
urchinTracker();
</script>http://plone.org/eventswill find the same code snippet:<script src="http://www.google-analytics.com/urchin.js" type="text/javascript">
</script>
<script type="text/javascript">
_uacct = "UA-00000-0";
urchinTracker();
</script>Ifhttp://plone.org/events/conferencesis marked with aIGAContextMarkerand
has the following ga code:<script src="http://www.google-analytics.com/urchin.js" type="text/javascript">
</script>
<script type="text/javascript">
_uacct = "UA-99999-9";
urchinTracker();
</script>Thenhttp://plone.org/events/conferences/2008-location-tbdwill find the code
snippet fromhttp://plone.org/events/conferences:<script src="http://www.google-analytics.com/urchin.js" type="text/javascript">
</script>
<script type="text/javascript">
_uacct = "UA-99999-9";
urchinTracker();
</script>vim: set ft=rst tw=75 nocin nosi ai sw=4 ts=4 expandtab spell spelllang=en:
Package: collective.galleriffic
IntroductionThis addon is an integration ofgallerifficin Plone usinggallery.
It provides a Galleriffic view for Folder, Collection and Link content types.This addon can manage thousands of photos in the same albums without any
performance issues. This is not common in the world of gallery/slideshow
jquery plugins.Dependenciescollective.gallerycollective.js.gallerifficcollective.configviewsHow to installThis addon is a Plone add on so please follow the official documentation athttp://plone.org/documentation/kb/add-ons/installingExposed configurationThe Galleriffic view expose some of the configuration of Galleriffic using the
configure view link provided by collective.configviews addon.
Options are translated.Delay in millisecondsNumber of thubnails to show per pagePreloadEnable top pagerEnable bottom pagerMax pages to showRender SS controls (Play & Pause)Render navigation controls (Previous & Next)Enable history (you will need to install collective.jqhistory for this option)Enable Keyboard navigationAutostartSync transitionsdefault transition durationCreditsCompaniesPlanet Makina CorpusContact usAuthorsJeanMichel FRANCOIS aka toutpt <toutpt@gmail.com>Changelog1.1.6 (2013-08-07)improvement responsive.1.1.5 (2013-07-25)fix width image in IE9 & IE10.1.1.4 (2013-07-22)changing the css menu control.modified view with thumbnail.modified display of display_mode_2 for easy customization.1.1.3 (2013-07-15)Modified MANIFEST.1.1.2 (2013-07-15)adding galleriffic view with thumbnails in the Display menu.1.1.1 (2013-07-05)Nothing changed yet.1.1 (2013-07-02)Register view with thumbnails.
[smoussiaux]1.0 (2012-02-28)Initial release
Package: collective.gelf
collective.pygelfProvidesZConfig-compatible logger handler factories forGraylog Extended Log Format.Usage withplone.recipe.zope2instance:[instance]...event-log-custom=%import collective.gelf<gelfudp>host 127.0.0.1port 9401custom app_name=Zope buildout=example.com</gelfudp>Available GELF hander types aregelfudp,gelftcpandgelftls.  Seepygelf-documentation for available configuration options.Custom fields with static values can be defined withcustomoption,
which accepts space separated list offieldname=staticvaluepairs.Changelog0.9.2 (2016-04-05)Update README
[datakurre]
Package: collective.generic.devmode
IntroductionThis provide a scriptcg.devmodewhich can do some actions on a zope instance.The main use is when you grab the production datafs, you ‘ll need to sanitize the content a little.
The sanitization include changing all passwords and all emails at once.Another use is for running scripts without any security (we just give us all rights ;))ContentsIntroductionCreditsActions & usageChanging all email for all users:Changing all passwordsChanging the administrator passwordRunning a script with all security stuff removedModifiersRunning with debugGiving an alternative zope configuration fileSpecifying the plone site idSpecifying the admin usercollective.generic.devmode InstallationChangelogSvn :http://svn.plone.org/svn/collective/collective.generic.devmode/trunk/Developement supported by :Makina CorpusCreditsPlanet Makina CorpusContact usActions & usageChanging all email for all users:./bin/cg.devmode -m --mail=some@mail.fooChanging all passwords./bin/cg.devmode -p  --password=secretChanging the administrator password./bin/cg.devmode -a  --password=secretRunning a script with all security stuff removed./bin/cg.devmode -r --script=</path/to/file.py>  [--script-args="String"] # equivalent of ./bin/instance run toto.py String except for securityModifiersRunning with debug./bin/cg.devmode -v [ARGS]Giving an alternative zope configuration file./bin/cg.devmode -c <CONFIGGILE>Specifying the plone site id./bin/cg.devmode -l <PLONE_SITE_ID>Specifying the admin user./bin/cg.devmode --user <ADMIN_USER>collective.generic.devmode InstallationTo install collective.generic.devmode into the global Python environment (or a workingenv),
using a traditional Zope 2 instance, you can do this:When you’re reading this you have probably already run``easy_install collective.generic.devmode``.Find out how to install setuptools (and EasyInstall) here:http://peak.telecommunity.com/DevCenter/EasyInstallIf you are using Zope 2.9 (not 2.10), getpythonproductsand install it
via:python setup.py install --home /path/to/instanceinto your Zope instance.Alternatively, if you are using zc.buildout and the plone.recipe.zope2instance
recipe to manage your project, you can do this:Addcollective.generic.devmodeto the list of eggs to install, e.g.:[buildout]
parts=
    ...
    cg.devmode
...
[cg.devmode]
recipe=minitage.recipe.scripts
eggs=${instance:eggs}
    collective.generic.devmode
scripts=cg.devmode
extra-paths = ${instance:extra-paths}
# in an oldschool zope2 install, zope2home/lib/python must be in extra-paths!Re-run buildout, e.g. with:$ ./bin/buildoutChangelog1.0 - 2010-04-12Initial release [kiorky]
Package: collective.geo.bundle
Overviewcollective.geo allows to geo-reference Plone content types and to display this information over a map.The core of collective geo is composed by the following packages:collective.geo.geographerprovides geo annotation for Plone.(repository)collective.geo.openlayersenables openlayers machinery into Plone.(repository)collective.geo.settingsprovides some utilities where settings of collective.geo packages can be stored(repository)collective.geo.mapwidgetprovides some handy page macros and adapters to easily manage multiple maps on one page.(repository)collective.z3cform.mapwidgetprovides a mapwidget for z3c.form framework.(repository)collective.geo.contentlocationsprovides a GUI for collective.geo.geographer. It provides some simple forms to add geographical coordinates to Plone content types.(repository)collective.geo.kmlprovides KML views for georeferenced objects, allowing Plone content types to be visualized in Google Earth.(repository)To display the maps,collective.geotakes advantage ofOpenlayers, a JavaScript library for displaying map data in web browsers, with no server-side dependencies.As a default map source we can selectOpenStreetMap,Google MapsorBing Maps.RequirementsBeautifulSoup (geopy)geopy >=0.98Plone >= 4.2collective.geo.contentlocations>= 3.1collective.geo.kml>= 3.2collective.z3cform.colorpicker>= 1.2collective.geo.behaviour>= 1.2InstallationThis addon can be installed has any other addons, please follow officialdocumentation.UpgradeTo upgrade collective.geo go to in the Plone Site Setup > Addon.When an upgrade is available a button will appear
next to Plone Maps (collective.geo) product.
Click the button to upgrade.DocumentationThe package is documented atcollectivegeo.readthedocs.org.
The sourcecode for this documentation resides in the docs folder of this
package, please contribute.ContributorsGiorgio Borelli - gborelliSilvio Tomatis - silviotGerhard Weis - gweisDavid Beitey - davidjbAdam Tang - adam139Christian Ledermann - clederLeonardo J. Caballero G. - macaguaMetricsChangelog2.3 (2015-05-02)Update requirements
[gborelli]Remove c.geo.behavior as extra requires and include it as default
[gborelli]2.2 (2014-08-16)Updated c.geo.mapwidget to 2.1.3
[gborelli]Updated version and year of collective.geo docs
[macagua]Added documentation about collective.geo.usersmap
[macagua]Added documentation about collective.geo.flexitopic
[macagua]2.1 (2014-02-26)Moved robot test from c.geo.behaviour
[gborelli]2.0 (2013-10-29)Added robotframework tests [gborelli]Added Sphinx documentation [gborelli]Added travis-ci configuration [gborelli]Added extras_requires in setup.py to use g.ceo with Dexterity
[gborelli]Added buildout configurationRefacrtorized package structure
[giacomos]0.1 (2011-03-06)First release