Kai Diefenbach wrote:
Hi Martin, hi all
Martin Aspeli <[EMAIL PROTECTED]> wrote:
Yes. nested comments are on the top of my todo list.
You may be able to re-use the Ploneboard interfaces directly, or model
something closely on them. A lot of thought have gone into them. :)
As you mentioned th
Martin Aspeli <[EMAIL PROTECTED]> wrote:
> Kai Diefenbach wrote:
> > Hi Martin, hi all
> >
> > Martin Aspeli <[EMAIL PROTECTED]> wrote:
> >>> Yes. nested comments are on the top of my todo list.
> >> You may be able to re-use the Ploneboard interfaces directly, or model
> >> something closely on
On Thu, 2006-21-09 at 21:55 +0100, Martin Aspeli wrote:
> > For an add-on product this means there is no way to unregister a
> > particular menu and menus added this way are available without
> > installation as they are global adapters and utilities.
>
> Well, a third party product can of course
Hi all,
First off I have to admit that I welcome any sort of increased
flexibility when it comes to portlets.
I will add the following goals of of any sort of plip to handle this
(loosely based on the motivation factors mentioned in the plip writeup):
1. Increase ability to customize
2. Impr
Hi Rocky & co,
Thanks for the review :)
I followed the bundle notes to discover how to actually activate the
portlets (in my plone site by default there weren't really any working
portlets but I assume this was intentional and of course will not be the
case in the final implementation). Once th
Martin Aspeli wrote:
> Hi Hanno,
>
>> 1. Global configuration:
>>
>> Currently menus (Actions menu, Workflow menu, ...) are configured in
>> ZCML and thus immediately available without any installation step.
>>
>> For an add-on product this means there is no way to unregister a
>> particular menu
Hi.
Martin Aspeli wrote:
>
>> #4: Prevent over-complication
>> This goal unfortunately hasn't been met very well. In my opinion the
>> new mechanics of integrating Zope 3 CA techniques used in this plip have
>> increased the complication of setting up portlets by several magnitudes.
>> Of cour
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 TextFiel
Hi Hanno,
The other thing is that the browser:menuItem and browser:menu directives
do all kinds of non-fun magic in the ZCML registration that we'd have to
replicate, and I don't know how hard this would be.
Mmh, but this means we don't know how easy this is to accomplish and we
leave the pro
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 bun
Hanno Schlichting wrote:
In this case I would love to see a short tutorial on how to write a new
simple portlet in the Plone developer reference.
I most definitely intend to make one if/when this is adopted.
Having a simple example people can copy as a base for their own products
would help
On Sat, 2006-23-09 at 22:10 +0100, Martin Aspeli wrote:
> > #4: Prevent over-complication
> > This goal unfortunately hasn't been met very well. In my opinion the
> > new mechanics of integrating Zope 3 CA techniques used in this plip have
> > increased the complication of setting up portlets by
12 matches
Mail list logo
