| Port details | 
	| 
 py-laces Django components that know how to render themselves
 0.1.2 www  =2          0.1.2Version of this port present on the latest quarterly branch.Maintainer: sunpoet@FreeBSD.org Port Added: 2024-03-09 14:12:39Last Update: 2025-02-03 15:51:35Commit Hash: c13b133People watching this port, also watch:: jdictionary, py311-Automat, py311-python-gdsii, py311-PyOpenGL, p5-SaneAlso Listed In: pythonLicense: BSD3CLAUSEWWW: https://github.com/tbrlpld/lacesDescription:Laces components provide a simple way to combine data (in the form of Python
objects) with the Django templates that are meant to render that data. The
components can then be simply rendered in any other template using the {%
component %} template tag. That parent template does not need to know anything
about the component's template or data. No need to receive, filter, restructure
or pass any data to the component's template. Just let the component render
itself.
Template and data are tied together in the component, and they can be passed
around together. This becomes especially useful when components are nested -- it
allows us to avoid building the same nested structure twice (once in the data
and again in the templates).
Working with objects that know how to render themselves as HTML elements is a
common pattern found in complex Django applications, such as the Wagtail admin
interface. The Wagtail admin is also where the APIs provided in this package
have previously been discovered, developed and solidified. The purpose of this
package is to make these tools available to other Django projects outside the
Wagtail ecosystem.   ¦  ¦  ¦  ¦ 
 Manual pages:FreshPorts has no man page information for this port.pkg-plist: as obtained via: make generate-plistThere is no configure plist information for this port.USE_RC_SUBR (Service Scripts)
no SUBR information found for this portDependency lines:
${PYTHON_PKGNAMEPREFIX}laces>0:www/py-laces@${PY_FLAVOR}
To install the port: cd /usr/ports/www/py-laces/ && make install cleanTo add the package, run one of these commands:NOTE: If this package has multiple flavors (see below), then use one of them instead of the name specified above.pkg install www/py-lacespkg install py311-laces
 NOTE: This is a Python port. Instead of py311-laces listed in the above command, you can pick from the names under the Packages section.
PKGNAME: py311-lacesPackage flavors (<flavor>: <package>)distinfo:TIMESTAMP = 1738089166
SHA256 (laces-0.1.2.tar.gz) = 3218e09c1889ae5cf3fc7a82f5bb63ec0c7879889b6a9760bfc42323c694b84d
SIZE (laces-0.1.2.tar.gz) = 29264 
Packages (timestamps in pop-ups are UTC):
 
DependenciesNOTE: FreshPorts displays only information on required and default dependencies.  Optional dependencies are not covered.Build dependencies:
py311-django42>=3.2 : www/py-django42@py311py311-flit-core>=3.2<4 : devel/py-flit-core@py311python3.11 : lang/python311py311-build>=0 : devel/py-build@py311py311-installer>=0 : devel/py-installer@py311
Test dependencies:
python3.11 : lang/python311
Runtime dependencies:
py311-django42>=3.2 : www/py-django42@py311python3.11 : lang/python311
This port is required by:for Run
					            
www/py-wagtail
Configuration Options:
     No options to configureOptions name:www_py-lacesUSES:pythonFreshPorts was unable to extract/find any pkg message
Master Sites: | 
| Commit History - (may be incomplete: for full details, see links to repositories near top of page) | 
| Commit | Credits | Log message | 
|---|
| 0.1.2 03 Feb 2025 15:51:35
 
       | Po-Chuan Hsieh (sunpoet)  | www/py-laces: Update to 0.1.2
Changes:	https://github.com/tbrlpld/laces/releases | 
| 0.1.1 09 Mar 2024 14:05:16
 
       | Po-Chuan Hsieh (sunpoet)  | www/py-laces: Add py-laces 0.1.1
Laces components provide a simple way to combine data (in the form of Python
objects) with the Django templates that are meant to render that data. The
components can then be simply rendered in any other template using the {%
component %} template tag. That parent template does not need to know anything
about the component's template or data. No need to receive, filter, restructure
or pass any data to the component's template. Just let the component render
itself.
Template and data are tied together in the component, and they can be passed
around together. This becomes especially useful when components are nested -- it
allows us to avoid building the same nested structure twice (once in the data
and again in the templates).
Working with objects that know how to render themselves as HTML elements is a
common pattern found in complex Django applications, such as the Wagtail admin
interface. The Wagtail admin is also where the APIs provided in this package
have previously been discovered, developed and solidified. The purpose of this
package is to make these tools available to other Django projects outside the
Wagtail ecosystem. |