hi martin, et. al.
On Sep 24, 2006, at 1:25 AM, Martin Aspeli wrote:
o Markup and Textile support requires additional Python modules to
be installed. They should probably not be available for selection
unless these modules are installed.
that's a matter of specification, i guess. here,
On Sep 24, 2006, at 1:41 PM, Tom Lazar wrote:
On Sep 24, 2006, at 1:25 AM, Martin Aspeli wrote:
o Looking at http://dev.plone.org/archetypes/changeset/6957, it's
not clear to me why we need to set the field's allowable content
types from the site property that holds the default values as
Hi Tom,
o Markup and Textile support requires additional Python modules to be
installed. They should probably not be available for selection unless
these modules are installed.
that's a matter of specification, i guess. here, like with most
decisions (i.e. using portal properties, not using
Hi guys,
Below is the review for PLIP 149 - Improved Markup Support
http://plone.org/products/plone/roadmap/149
What is it?
---
- A way of registering additional transformations to support different
text transforms more easily, without requiring the content type (i.e.
the AT
o It's unclear to me whether/how this corresponds to the work on Wicked
should be orthogonal to wicked (just as stx, reST, html etc is). wicked
is not format sensitive(another reason why it keeps it's syntactical
scope limited).
speaking of wicked, got it all running with the plone-3.0
