Saravanan666/pypi-org huggingface dataset:
Package: collective.pdfexport
README for collective.pdfexportA simple product which provides a XHTML2PDF Exporter.EnablingImplement collective.pdfexport.interfaces.IPDFExportCapable on the content
type and create xhtml2pdf_view for it. Loading download_pdf view on the content
will export xhtml2pdf_view as PDF.Changelog1.0a9 (2014-01-13)Nothing changed yet.1.0a8 (2013-12-16)Nothing changed yet.1.0a7 (2013-11-26)Nothing changed yet.1.0a6 (2013-11-13)Nothing changed yet.1.0a5 (2013-11-04)Nothing changed yet.1.0a4 (2013-11-04)Nothing changed yet.1.0a3 (2013-11-04)Nothing changed yet.1.0a2 (2013-11-03)Nothing changed yet.1.0a1 (2013-10-24)Initial package generated using inigo.templer
Package: collective.pdfjs
collective.pdfjs - Plone integration for Mozilla’s JavaScript PDF readerIntroductionThis product adds pdf.js support for Plone.Pdf.js is a JavaScript library for rendering PDF documents in the canvas,
without using external plugins; only JavaScript is needed.This product will make the JavaScript library available as a resource, and
add a new view for the File content type.Please note that pdf.js is still under heavy development; as such:a modern browser is required;not all PDFs may be rendered correctly, or at all;InstallationUsing zc.buildout addcollective.pdfjsto the list of eggs to install:[instance]
recipe = plone.recipe.zope2instance
...
eggs =
    ...
    collective.pdfjsRe-run buildout, e.g. with:$ ./bin/buildoutRestart your plone instance and install this addon.UsageIf the view detects a PDF file, it will attempt to render it inline using
pdf.js. If the user browser doesn’t have JavaScript enabled, it will embed
any available PDF reader plugin (Acrobat’s, Google Chrome native, etc) instead.Additional informationCurrently, the whole document is downloaded and each page rendered
incrementally inside the canvas. This means that big files on slow connections
will take a while before displaying; you might want to switch to the standard
view in this case.Source Code and ContributionsIf you want to help with the development (improvement, update, bug-fixing, …)
ofcollective.pdfjsthis is a great idea!The code is located in thegithub collective.You can clone it orget access to the github-collectiveand work directly on the project.ContributorsRigel Di Scala <zedr@zedr.com> <http://github.com/zedr>MarcelJens KleinBenjamin StefanerMaik Derstappen <md@derico.de> <http://github.com/MrTango>Changelog1.0.4 (2023-02-27)Add missing dependency on plone.app.upgrade
[MrTango]1.0.3 (2023-02-27)Depend only on Products.CMFPlone not on Plone package
[MrTango]1.0.2 (2022-11-04)Fix manifest file1.0.1 (2022-11-04)hide upgrade steps in quickinstaller
[MrTango]1.0 (2022-11-04)Overhaul to the most recent pdfjs release including its recent viewer.js
[jensens, benniboy]make it compatiple with Plone 6
[MrTango]0.4.2Tests: added a test on availableLayouts
This fails because the view is not present,
no idea why. Must recheck.Added human name for the view, after a suggestion by
Marcel0.4.0Tests: basic code coverageReasonably minified pdf.js0.3.6Minified pdf.min.jsTested on Chrome and Firefox0.2.2Renders the Tracemonkey PDF
Package: collective.pdftransform
IntroductionThe main goal of this product is to allow PDF into ImageFields in
Plone. It uses code written by David Brenneman for
collective.pdfpeek.InstallJust add the following lines in your buildout:collective.pdfpeek
collective.pdftransformYou must install pdftransform with the quick installer (no need to
install pdfpeek, but it must be in the buildout as we use its methods)Using pdftransform in your sitecollective.pdftransform adds apdf_to_imagetransform in Plone
portal_transform.
As transforms can not be used with FileField (or at least I did not
find how …) it also provides a method in utils called update_form.
You can use it in thepost_validatemethod of your Archetype
objects.Here is an example (from Products.plonehrm, the Employee Archetype
object):...
from collective.pdftransform.utils import update_form
...
class Employee(BaseFolder):
    ...

    security.declarePrivate('post_validate')
    def post_validate(self, REQUEST, errors):
        update_form(self, REQUEST)

    ...With this, all files submitted in the edit form, if they are PDF, are
transformed into jpg files.
You can specify an extra argument in update_form which is the list of
fields, for example, if we had written this:security.declarePrivate('post_validate')
def post_validate(self, REQUEST, errors):
    update_form(self, REQUEST,
                ['portrait_file', 'idScan_file'])only the files submitted in the portrait and idScan fields would have
been transformed.You can also use the validator calledisValidImageOrPDFin your
Image fields.Changelog0.5 (2015-08-27)Code cleanup.
[maurits]0.4 (2013-06-04)Do not explicitly require collective.pdfpeek 1.2, but make that a
minimum.
[maurits]0.3 (2012-10-30)Patched pdfpeek to use the default 1.2 release. [vincent]Allow setting PDF resolution in update_form. [vincent]0.2 (2010-06-21)Bugfix in utils/is_transformable_pdf. [vincent]0.1 (2010-05-19)added translations for french and dutch. [vincent]updated the validator to return an error if the PDF file can not be
transformed. [vincent]added is_transformable_pdf in utils, tells if the PDF file uploaded
can be transformed with pdf_to_image. [vincent]added validator called ‘isValidImageOrPDF’ that checks that the
submitted if is a PDF or an image (except BMP images as it can cause
problems). [vincent]added update_form in utils, that can be used in
the post_validate method of your Archetype objects. [vincent]Added transform to the portal_transform. [vincent]
Package: collective.periodcriterion
Table of contentsIntroductionHow to useRequirementsTODOCreditsAuthorsChangelog0.2.0 (2012-12-20)0.1.0 (2011-02-16)IntroductionThis product add a two new criteria for dates inside Plone, someway similar to the “Today” ones.What you can’t do with the default Plone relative criteria is configure a Collection that:show all news published this monthshow all file modified this year… and so on.As default Plone “today” criteria, the “this month” and “this year” values are taken automatically.How to useThe new criteria displays a simple selection between:This yearThis monthNew criteria added on CollectionAlso, this product will backport the “Today” criteria added on new style collection content type to the old
Archetypes based ones.New criteria added on old-style CollectionRequirementsTested withPlone 4.2andPlone 4.3.TODOFix tests (the few there are GMT+1 specific)Right now the calculation of dates is sometimes crappy.CreditsDeveloped with the support ofAzienda USL Ferrara; Azienda USL Ferrara supports thePloneGov initiative.AuthorsThis product was developed by RedTurtle Technology team.Changelog0.2.0 (2012-12-20)Plone 4.2 compatibility for old and new Collection content type
[keul]More pythoninc dates generation, using DateTime native methods
[keul]Added a proper uninstall profile (it works only partially, and only on Plone 4.3)
[keul]Support for “Site Administrator” role
[keul]0.1.0 (2011-02-16)first release
Package: collective.permalink
collective.permalinkThis adds apermalinkto every supported Plone content. A permalink is a link to the content
that should never change even if you rename or move it.FeaturesPermalink as object action or as document actionjavascript copy to clipboard on click eventTranslationsThis addon has been translated intoEnglishDevelopment setupAssuming you have a clean python 2.7 with virtualenv and pip:cd <your sandbox dir>
git clone https://github.com/collective/collective.permalink.git
cd collective.permalink
<virtualenv2.7> .
source ./bin/activate
pip install -Ur requirements.txt
buildoutRunning instance:instance fgRunning code-analysis:code-analysisRunning tests:./bin/test -s collective.permalinkUsage in other projectUse as egg via buildoutInstall collective.permalink by adding it to your buildout.cfg:[instance]
recipe = plone.recipe.zope2instance
...
eggs =
  ...
  collective.permalink
  ...Use as egg via setup.pyInstall collective.permalink by adding it to your setup.py:install_requires=[
    ...
    'collective.permalink',
    ...
]Use as source via buildoutInstall collective.permalink by adding it to your buildout.cfgmr.developeris needed!:[sources]
collective.permalink = git https://github.com/collective/collective.permalink.git
...and then runningbuildoutHow to useThe default implementation is based on the Ploneresolveuidfeature.
This will not work (and shows anything) for contents without theplone.uuidsupport. You can however
customize and develop additional adapters for providing permalink for yours types (or customize
the default one).The new resource will be added to thedocument actionssection.CreditsDeveloped with the support ofAzienda USL Ferrara; Azienda USL Ferrara supports thePloneGov initiative.AuthorsThis product was developed by RedTurtle Technology team.Plone5 upgrade and improvements by the development dept. (gogo&iham) of theacademy of fine arts vienna.ContributeIssue Tracker:https://github.com/collective/collective.permalink.git/issuesSource Code:https://github.com/collective/collective.permalink.gitLicenseThe project is licensed under the GPLv2.ContributorsRed TurtleMarkus Hilbert,markus.hilbert@iham.atSven Strack,sven@so36.netChangelog1.0.5 (2018-03-22)fix js error.
[iham]1.0.4 (2018-03-21)pypi version confusion… nevermind.
v 1.0.3 was removed.
[iham]1.0.3 (2018-03-21)fixed resource registration to make it work with plone-resource-compile.
[iham]1.0.2 (2017-09-06)fixed Broken “Permalink (to Clipboard)” functionality #4
[enkidulan]update url in setup.py, plone.org/products is gone
[svx]remove node_modules from repository and add .gitignore file
[cekk]1.0.1 (2017-08-09)fixed permission for view.
[iham]1.0.0 (2017-06-28)Dropped Plone 4 compatibility.upgrade to Plone5clean up code using flake8 conventionsadded testsadded controlpaneladded javascript “copy to clipboard” on click
[iham]0.2.1 (2016-01-20)make permalink respect typesUseViewActionInListings
[pbauer]0.2.0 (2013-04-11)Dropped Plone 3 compatibilityFixing import for Plone 4.2
[keul]Now based onplone.uuidto this should work also
for dexterity based contents
[keul]0.1.0 (2010-07-07)initial release
Package: collective.person
Person content type for PloneFeaturescollective.personprovides a content type representing a Person.Content TypesPerson: A content type representing a personBehaviorsnametitledescriptioncollective.person.personPerson BehaviorFields with basic person informationcollective.person.userLink Person to Plone UserAdapts a Person to link it to a Plone Usercollective.person.namefromusernameName from usernameUse the username field as name (basis for the id)PermissionsidtitleUsagecollective.person.person.addcollective.person: Add PersonControl the creation of a new Person content itemCatalog IndexesThis package adds Indexes and Metadata to Portal Catalog.Content AttributeIndex TypeMetadataCommentrolesKeywordIndex✅--usernameFieldIndex✅Used whencollective.person.userbehavior is enabledSee it in actionThis package is being used by the following sites:TODODocumentationInstallationAddcollective.personas a dependency on your package'ssetup.pyinstall_requires=["collective.person","Plone","plone.restapi","setuptools",],Also, addcollective.personto your package'sconfigure.zcml(ordependencies.zcml):<includepackage="collective.person"/>Generic SetupTo automatically enable this package when your add-on is installed, add the following line inside the package'sprofiles/default/metadata.xmldependencieselement:<dependency>profile-collective.person:default</dependency>Source Code and ContributionsWe welcome contributions tocollective.person.You can create an issue in the issue tracker, or contact a maintainer.Issue TrackerSource CodeDevelopment setupYou need a working Python environment version 3.8 or later.Then install the dependencies and a development instance using:makeinstallBy default, we use the latest Plone version in the 6.x series.Update translationsmakei18nFormat codebasemakeformatRun testsmaketestLicenseThe project is licensed under GPLv2.Changelog1.0.0a2 (2023-06-21)New features:ImplementPersoncontent type @ericof personAdd pt_BR translation @ericof pt_BRImplementcollective.person.userbehavior @ericof user-behavior1.0.0 (unreleased)
Package: collective.personaltags
IntroductionLicence: GNU General Public LicenseThis module provides a tagging tool for plone 4. The idea is that logged-in
users can tag items that they are interested in, and find them again later.RequirementsPlone 4A browser with javascript supportjquery 1.4.3 or laterInstallationAdd collective.personaltags to your buildout eggs.:eggs=\
    ...
    collective.personaltagsRun buildout, restart plone.Go to “Site Setup -> Add-ons”.Install the product “Track content using personal tags”.ConfigurationThe tool comes with an implementation of the back-end storage called demo. This
is chosen by default.You can select the portal_types to limit the tool to via an “Add-on Configuration”
screen (configlet).You can configure system wide standard tag names.Add a ‘Personal Tags’ portlet to the site so that the user can see their tags.You can configure the number of tags to display. The rest are hidden.UsageThe tool provides a tag selector bar on each page. Enter the tags you want.
Tags are delimited by spaces.JQuery auto-complete will hint with names of existing tags.RemovalThe tool does not un-install the storage. You should do this manually if you
are completely uninstalling the tool.It is in the site-root and called “personaltags”.Limits of the Demo ManagerThe demo manager was build to demonstrate the tool in Plone. My usage is
with an SQLAlchemy backend, so the work on the demo storage is incomplete.There is no recognition of events such as zope.app.container.interfaces.IObjectRemovedEvent.Changelog1.0devdev (unreleased)Initial release
Package: collective.pfg.creditcardfields
IntroductionThis package is meant to contain any useful field for credit card payment
using PloneFormGen.It contains for now a “Credit Card Expiration Date” field.You need to add the egg in your buildout and then import the profile.Changelog1.3 (unreleased)Fix template to include widget label for compatibility with Archetypes>=1.7.7
[davisagli]1.2 (2010-05-19)Don’t use the uniqueItemIndex, which is no longer present in Plone 4.
[davisagli]1.1 (2009-03-03)changed name of the skin path [lucielejard]updated the field so that it doesn’t change the date to localize
time automatically [lucielejard]1.0 (2009-02-02)added a hidden “day” field, so that when the field is required, we have
all the fields set upadded all the code needed to have a credit card expiration date fieldcreating the initial structure of the trunk [lucielejard]
Package: collective.pfg.norobots
Table of ContentsOverviewRequirementsScreenshotInstallationGetting the moduleEnabling the moduleQuickly test ?CreditsSource codeHow to contribute and submit a patch ?ContributorsChangelog1.2 (2016-07-21)1.1 (2015-04-13)1.0 (2012-10-03)Overviewcollective.pfg.norobotsis aPloneFormGenfield usingcollective.z3cform.norobots.collective.z3cform.norobotsprovides a “human” captcha widget based on a list of
question/answer(s).This captcha can be used :as a PloneFormGen field withcollective.pfg.norobotsas aplone.app.discussion(Plone Discussions) captcha pluginas az3c formfieldas a macro in a custom formRequirementsI have tested this release with :Plone 5.0.5 & PloneFormGen 1.8.1 & collective.z3cform.norobots 1.4.4Plone 4.3.10 & PloneFormGen 1.7.19 & collective.z3cform.norobots 1.4.4ScreenshotInstallationGetting the moduleAddcollective.pfg.norobotsto yourplone.recipe.zope2instancebuildout section e.g.:[instance]
...
eggs =
    Plone
    ...
    collective.pfg.norobotsOr, you can add it as a dependency on your own productsetup.py:install_requires=[
    ...
    'collective.pfg.norobots',
],Enabling the moduleInstall PloneFormGen (if not already done) then collective.pfg.norobots from the Add-ons control panel. That’s it!Quickly test ?Downloadcollective.pfg.norobotsand usevirtualenvandbuildoutto test the module:easy_install virtualenv
cd collective.pfg.norobots
virtualenv .
source bin/activate
(collective.pfg.norobots) easy_install zc.buildout
!!! check the buildout config file ``test-plone-base.cfg`` before running !!!
(collective.pfg.norobots) ln -s test-plone-5.0.x.cfg buildout.cfg
(collective.pfg.norobots) python bootstrap.py
(collective.pfg.norobots) bin/buildout
[...] be patient... [...]
(collective.pfg.norobots) ./bin/instance fgGo tohttp://localhost:8080, add a new Plone Site and install collective.pfg.norobots.Launch tests:(collective.pfg.norobots) pip install unittest2
    (collective.pfg.norobots) ./bin/test -s collective.pfg.norobotsLaunch code coverage:(collective.pfg.norobots) bin/coverage
(collective.pfg.norobots) bin/report
And open with a browser htmlcov/index.htmlCreditsSylvain Boureliou [sylvainb] -GitHub-WebsiteMakina CorpusMakina CorpusSource codeSource codeis hosted on Github.How to contribute and submit a patch ?Source codeand anissue trackeris hosted on Github.ContributorsSylvain Boureliou [sylvainb]Kim Chee Leong [kcleong]Pawel Lewicki [lewicki]Changelog1.2 (2016-07-21)Unified widget with the other PFG widgets to make it work with QuickEdit.
[lewicki]1.1 (2015-04-13)Added Dutch translation.
[kcleong]1.0 (2012-10-03)Initial release
[sylvainb]
Package: collective.pfgpreview
IntroductionTo use PloneFormGen preview page:
set ‘preview’ in “Custom Form Action” field of FormFolderChangelog1.1 (2015-07-20)Plone 4.3.x compatibility
[Armin Stross-Radschinski]Replaced history.back() with better implementation which
does not propagate old validation errors to user.
[naro]1.0 - 2012-04-19Initial releaseContributorsRoman Kozlovskyi [kroman0]
Sune Broendum Woeller [sunew]
Radim Novotny [naro]
Package: collective.pfg.showrequest
Introductioncollective.pfg.showrequest shows field labels and values on the next form generated by PloneFormGen.Currently tested withPlone-4.3Products.PloneFormGen-1.7.8Python-2.7.xSometimes, you might need to chain forms to create wizard like forms where
you want to show field input results from the previous form.
This package serves for this need by simply registering viewlet to plone.app.layout.viewlets.interfaces.IAboveContentBody interface.How ToOnce you have quickinstalled collective.pfg.showrequest,
go to the Form Folder (Form2) where you want to show the field results.There isShow Requestbutton under Actions, so click it.
Input field ids from the previous form (Form1) and save it.The order will effect the resulting order.Copy the field types from theForm1to theForm2with default values and overrides empty.To show the field result correctly, you need to have the same field in both Form1 and Form2 for the showing fields.You will see previous form results above the content body now like it is
on thanks page.Changelog0.6 (2013-05-06)Moved test packages to extras_require. [taito]Tested with Plone-4.3. [taito]0.5.1 (2013-03-23)Updated to work with Products.PloneFormGen-1.7.7. [taito]Tested with Plone-4.2.5. [taito]0.5 (2013-01-06)Tested with Plone-4.2.3 and Products.PloneFormGen-1.7.6. [taito]Added testing integration to Travis CI. [taito]0.4 (2012-11-14)Tested with Plone-4.2.2 and Products.PloneFormGen-1.7.4. [taito]0.3 (2012-09-17)Tested with Plone-4.2.1. [taito]0.2.0 (2011-04-22)Added control on showing field results.0.1.0 (2011-04-21)Initial releaseInstallationIf you are using zc.buildout and the plone.recipe.zope2instance
recipe to manage your project, you can do this:Addcollective.pfg.showrequestto the list of eggs to install, e.g.:[buildout]
...
eggs =
    ...
    collective.pfg.showrequestRe-run buildout, e.g. with:$ ./bin/buildoutCreditsFinnish Association for Nature Conservation (Suomen Luonnonsuojeluliitto) who uses this package in their site:http://www.sll.fi
Package: collective.pfg.soup
Soup Storage for PloneFormGen Form DataThis PloneFormGen Storage Adapter saves and index form-data in so calledsoup. A soup is an unstructured flat storage containing records with
attributes (form-data). Attributes are indexed in anrepoze.catalog. Thus
complex queries on the data are possible.It ships with an full-featured table view based onjquery.datatables.
Datatables server-side processing enables to have large datasets processed.
It provides a search over all columns and by single columns. Each column
can be sorted.Additional to the form data userid and timestamp of creations is logged.A row can be edited. After save modification-timestamp, userid and changed
fields are logged.CSV-Export of all data is possible, including creators userid, creation- and
last-modified-timestamp if selected.InstallationJust depend in your buildout on the eggcollective.pfg.soup. ZCML is
loaded automagically with z3c.autoinclude.InstallSoup Adapter for PloneFormGenas an addon in Plone control-panel or
portal_setup.This package is written for Plone 4.2 or later.Source Code and ContributionsIf you want to help with the development (improvement, update, bug-fixing, …)
ofcollective.pfg.soupthis is a great idea!The code is located in thegithub collective.You can clone it orget access to the github-collectiveand work directly on the project.Maintainer is Jens Klein and the BlueDynamics Alliance developer team. We
appreciate any contribution and if a release is needed to be done on pypi,
please just contact one of usdev@bluedynamics dot comContributorsJens W. Klein <jens@bluedynamics.com>Benjamin StefanerPeter HolzerLicense GPL 2Todosonly indexed fields are sortable - reflect this in UIcreate indexadapters for all field typesbinary handlingHistory1.5.1prevent re-edit javscript from fetching cached requests. fixes #7
[jensens, 2014-03-07]allow shared soup storage based on soup_name
[agitator, 2014-12-16]added json response headers
[agitator, 2014-12-16]1.5deal with Rating Scale Field. fixes #6.
[jensens, 2013-12-19]1.4workaround in order to fix #5 On copy soup is not copied.
[jensens, 2013-12-19]1.3fixes #4 Export with non-ascii in labels fails.
[jensens, 2013-12-16]1.2fixes some problems in form re-edit mechanism. Before this change a form
lost its data if a user clicked on view tab with edit cookie set already.
Also re-edit resulted in double entries in some cases. With this change also
issue #1 was fixed, which was in fact a side effect of the above.
[jensens, 2013-09-16]1.1.1fixes broken release because of some git confusion
[jensens, 2013-09-11]1.1broken release, tries to: fix a bug while showing history.
[jensens, 2013-08-26]1.0added feature: delete rows
[jensens, 2013-03-07]1.0-beta31.6 (2014-12-16)[jensens, 2013-02-24]1.0-beta2bugfix: subscriber raised AttributeError: get_soup [jensens, 2012-09-07]1.0-betamake it work [jensens, 2012-07-03]
Package: collective.pfg.sqladapter
Introductioncollective.pfg.sqladapteradds a form action adapter to PloneFormGen that
saves form input data in a SQL database using SQLAlchemy.SetupTo installcollective.pfg.sqladapteradd it to the list of eggs in your buildout.To configure the database, use z3c.saconfig and define a named scoped session
“collective.pfg.sqladapter” in your configure.zcml or in the “zcml-additional”
parameter of your buildout.Example:<configure xmlns="http://namespaces.zope.org/db">
    <engine name="collective.pfg.sqladapter" url="mysql://user:password@localhost/database" />
    <session name="collective.pfg.sqladapter" engine="collective.pfg.sqladapter" />
</configure>Run buildout and restart your instance. Then install the product using Quickinstaller.UsageTo save form input data in your SQL database add a “SQLAdapter” in your Form Folder
and enter the name of the table where the input data should be stored.If a table with the given name does not exist in your database, it will be
created with columns corresponding to the fields in your form. Thus the “SQLAdapter”
should be added after all fields were added.Changelog1.0 (2012-02-20)Initial release