Introduction
Collective.ZodbBrowser is a web application to browse, inspect and introspect Zope’s zodb objects. It is inspired on smalltalk’s class browser and zodbbrowsers for zope3.
There is a demo video available at YouTube’s menttes channel.
Using ZodbBrowser with your buildout
If you already have a buildout for Plone3 or Plone4 running, edit buildout.cfg to add collective.zodbbrowser to eggs and zcml sections at buildout and instance parts respectively.
[buildout] ... eggs = collective.zodbbrowser ...
Autoinclude is automatically configured to work in Plone but if you are using any other systems, make sure to add a zcml slug:
... [instance] ... zcml = collective.zodbbrowser
Then run bin/buildout to make the changes effective.
Changelog
collective.zodbbrowser 0.1
Changed namespace to avoid conflicts on windows plataforms. Thanks to Laurence Rowe.
Added Smartfilter for Plone folders. Thanks to Elizabeth Leddy and
Added annotations list
Switch from View to ViewManagementScreens Permissions. Thanks to Elizabeth Leddy.
Added alternate view that starts to filter out objects that are unlikely. to be navigated. Thanks to Elizabeth Leddy.
Rename views to not conflict with certain built in items. Thanks to Elizabeth Leddy.
Render sites with broken interfaces. Thanks to Elizabeth Leddy.
Bumped the jquery dynatree version, fixed missing dependencies for jq libs. Thanks to Elizabeth Leddy.
Fix setup.py so that autoinclude works with plone without zcml. Thanks to Elizabeth Leddy.
Make all browser views extend DoomedBrowserView, which makes sure the utility can’t accidentally commit a transaction. Thanks to David Glick.
Remove unused five:registerPackage directive and initialize method. Thanks to David Glick.
zope2.zodbbrowser 0.2 experimental version
Added ui.layout for better layout and resizable panels. Thanks to Quimera.
Updated jquery from 1.4.2 to 1.4.4.
Added Pretty printing format to show propertie’s values. Thanks to Laurence Rowe and Emanuel Sartor.
Added support for older pythons 2.4 , 2.5. Thanks to Laurence Rowe.
Included module and file path for source code. Thanks to davidjb.
Added z3c.autoinclude.plugin support to remove the zcml entry on buildout. Thanks to aclark.
zope2.zodbbrowser 0.1 experimental version
Initial release includes: Class and Ancestors, Properties, Callables and Interfaces provided.
Support for Zope 2.13.x
Support for Firefox 3.6 and Chrome 5.0. No support Internet Explorer yet.
1 maintainer
Metadata
1 maintainer
Release files for collective.zodbbrowser 0.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| collective.zodbbrowser-0.1.tar.gz | 80.0 kB | Without provenance | Details for collective.zodbbrowser-0.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| collective.zodbbrowser-0.1-py2.6.egg | Legacy Egg format | - | - | Details for collective.zodbbrowser-0.1-py2.6.egg |
Total release size: 162.3 kB
Release files / collective.zodbbrowser-0.1.tar.gz
| Download URL | collective.zodbbrowser-0.1.tar.gz |
|---|---|
| Size | 80.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
c61c76fd5cb41814e1e0193929496927c460d5f500b92455a22db8250b0ad6c4
|
|
BLAKE2b-256 checksum How to use checksums |
12ac051aafbdaa000e4a1b3ead9b2af5c5c1849cc23cde129ca79f96e1a9bbfc
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Release files / collective.zodbbrowser-0.1-py2.6.egg
| Download URL | collective.zodbbrowser-0.1-py2.6.egg |
|---|---|
| Size | 82.3 kB |
| Tags | Egg |
|
SHA-256 checksum How to use checksums |
01f193004a4f337d34a4a35fbff94f8f10d9eb25de7fbfd4172f83007a97e54b
|
|
BLAKE2b-256 checksum How to use checksums |
08caebd5f4c3ddbcc627e9dc52c9f428b28a7eeb536feca0be921a3807f35ae2
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for collective.zodbbrowser 0.1
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
