Search results
203 results
Sort by:
Volto Efforts and Issues
Postings, bug reports, and feature requests from my efforts to use Plone 6 + Volto as it was being released.
Playing With Blocks
Exhibit some addon stuff (including this page description with formatted text , situated in multiple places including complex containers, with some footnotes )
Software and Systems
I'm a software and systems developer interested in making simple and effective tools. I'm particularly interested in how to make it easy to organize information to support comprehension and collaboration.
Software Craft
Notes about software work I've done.
Organizing Connections
Potential for unlimited cooperation in the progressive development of stories depends on being able to share the process of organizing details and not just the ability to share the details that are being organized. That is, ability to share the process of establishing and changing connections between details and not just the details.
My Weblog
I use this weblog for transient topics. (Essays on the rest of the site are for stuff that I've been developing gradually.)
An Automatically Populated Nested Volto Navigation Menubar
Many websites need an automatically populated nested navigation menu, and the new Plone 6 frontend, Volto, did not provide one. I've implemented a fully functional version. It's a little rough but quite sufficient for my purposes.
Zope Plone
I work with and have contributed to the development of a web application server, Zope, and a content management platform built on Zope named Plone.
Plone6 Volto
The new platform on which I've implemented my website, manually migrating from Plone 4 for the original version. I like the implementation of a block structured framework, based on React Semantic UI, by members of the Plone community has implemented.
Plone4 WSGI
The Web Services Gateway Interface is a specification for communications between and among web servers and web applications. It is officially stated in PEP 333 (a Python Enhancement Proposal), and it is a powerful basis for synthesizing web applications through the interconnection of components, over the web. It is complex, as are implementations of the specification in Plone. Around March, 2010 I attempted to get a handle on it and needed better guides than I found, so started to develop my own. I didn't go very far.
Contact Improvisation
I love playing this dance/movement game. Partners mutually follow points of contact, coordinating in a way that can approach the immediacy and depth of moving on one's own, sharing presence.
Learning Contact Improvisation
Explaining how to do CI is like explaining how to walk or swim or surf or ride a bike – these kinds of things are learned by doing. However, we can find guidance about how to participate – to tune in and engage – in a way that invites what the practice teaches.
Musings and Amusements
Design, philosophy, stories, and silliness.
Work / CV
My work history and goals.
Site
Info about the site implementation and tips for getting around.
About Plone with WSGI
Notes from exploring integration of Plone with WSGI, around March 2010, including an attempt to clearly describe WSGI.
WSGI Deliverance Synopsis
A cheat sheet describing the WSGI deliverance_ filter, by which thematic layouts are imposed on pages from WSGI-aware python applications.
WSGI Plone Paste Config
Notes about the python Paste configuration for the devel build of Plone with WSGI using Martin Aspelli's Plone 3.x Uber-Buildout
Plone4 Blobs
At several points from November, 2007 through March 2009 I worked with preliminary versions of Andi Ziedler's Plone/Zope integrations of binary large objects (blobs) in Plone 3, so my clients and I could include rich media - video, audio, formatted documents like pdf - on our sites without bloating ZODB file storage. In the process I got more familiar with zc.buildout , the Python automated build machinery used by Plone, in order to work out ZEO integration and other issues. This is an account that changed as the situation developed, and conveys many useful details involving building plone/zc.buildout, operation of blobs, and related things.
startcluster.sh
my version of a cluster startup script, circa 2009. the main differences from the standard scripts is that these custom versions didn't have their locations hard coded, and they called each other, reducing code duplication and drift.
restartcluster.sh
my version of the cluster restart script, circa 2009. the main differences from the standard scripts is that these custom versions didn't have their locations hard coded, and they called each other, reducing code duplication and drift.
shutdowncluster.sh
my version of the cluster shutdown script, circa 2009. the main differences from the standard scripts is that these custom versions didn't have their locations hard coded, and they called each other, reducing code duplication and drift.
clientXctl.sh
my version of the cluster startup script, circa 2009. the main differences from the standard scripts is that these custom versions didn't have their locations hard coded, and they called each other, reducing code duplication and drift.
ploneoutblobs_base.cfg
my scheme migrated away from using this base.cfg configuration file.
ploneoutblobs_buildout.cfg
my version of a cluster configuration script, circa 2009, this one was supplanted buildout.cfg - see related files.