On Wed, Nov 03, 2004 at 07:05:49PM +0100, Sylvain Wallez wrote:
> Tim Larson wrote:
> >On Wed, Nov 03, 2004 at 06:29:46PM +0100, Sylvain Wallez wrote:
> >>Tim Larson wrote:
> >>>On Tue, Nov 02, 2004 at 11:29:28AM +0100, Sylvain Wallez wrote:
> >>I had a bug while writing widget states because Repea
Tim Larson wrote:
On Wed, Nov 03, 2004 at 06:29:46PM +0100, Sylvain Wallez wrote:
Tim Larson wrote:
On Tue, Nov 02, 2004 at 11:29:28AM +0100, Sylvain Wallez wrote:
I am working on the port now and have it almost finished,
Buhooo... I missed your post and am also almost finished :-(((
On Wed, Nov 03, 2004 at 06:29:46PM +0100, Sylvain Wallez wrote:
> Tim Larson wrote:
> >On Tue, Nov 02, 2004 at 11:29:28AM +0100, Sylvain Wallez wrote:
> >I am working on the port now and have it almost finished,
>
> Buhooo... I missed your post and am also almost finished :-(((
:(
> >but I have
Tim Larson wrote:
On Tue, Nov 02, 2004 at 11:29:28AM +0100, Sylvain Wallez wrote:
Unusual for me, but time for a rant: I wrote the new CForms widget state
feature in 2.1 and tried to port it to 2.2.
WHAT A PITA!
There are a number or *bug fixes* or minor new features that only exist
in 2.2. W
On Tue, Nov 02, 2004 at 09:12:28PM +, Tim Larson wrote:
> I am working on the port now and have it almost finished,
> but I have a few questions about some recent changes that
> the commit comments did not make clear to me:
>
> AbstractWidget.java
> From: public Widget getParent()
>
On Tue, Nov 02, 2004 at 11:29:28AM +0100, Sylvain Wallez wrote:
> Unusual for me, but time for a rant: I wrote the new CForms widget state
> feature in 2.1 and tried to port it to 2.2.
>
> WHAT A PITA!
>
> There are a number or *bug fixes* or minor new features that only exist
> in 2.2. Why are
Sylvain Wallez dijo:
> Carsten Ziegeler wrote:
>
>>Sylvain Wallez wrote:
>>
>>
There are other changes as well - internal processing etc. But the good
news is: you can use the ExtendedComponentSelector in the
configuration, although the class doesn't exist. ECM++ will
automatical
Carsten Ziegeler wrote:
Sylvain Wallez wrote:
There are other changes as well - internal processing etc. But the good news is: you can use the ExtendedComponentSelector in the configuration, although the class doesn't exist. ECM++ will automatically use the CocoonServiceSelector. This is for com
Sylvain Wallez wrote:
> >>
> >There are other changes as well - internal processing etc.
> But the good
> >news is: you can use the ExtendedComponentSelector in the
> >configuration, although the class doesn't exist. ECM++ will
> >automatically use the CocoonServiceSelector. This is for
> comp
Carsten Ziegeler wrote:
Sylvain Wallez wrote:
I remember a time where 2.2 contained only the Cocoon core
and no blocks. Is it no more possible? Ah no: the cforms
xconf files now reference ECM++ selectors. G... What
about reinstalling in 2.2 an ExtendedComponentSelector that
would simply be
Carsten Ziegeler wrote:
Sylvain Wallez wrote:
I remember a time where 2.2 contained only the Cocoon core
and no blocks. Is it no more possible? Ah no: the cforms
xconf files now reference ECM++ selectors. G... What
about reinstalling in 2.2 an ExtendedComponentSelector that
would simply
Sylvain Wallez wrote:
>
> I remember a time where 2.2 contained only the Cocoon core
> and no blocks. Is it no more possible? Ah no: the cforms
> xconf files now reference ECM++ selectors. G... What
> about reinstalling in 2.2 an ExtendedComponentSelector that
> would simply be a subclass
Unusual for me, but time for a rant: I wrote the new CForms widget state
feature in 2.1 and tried to port it to 2.2.
WHAT A PITA!
There are a number or *bug fixes* or minor new features that only exist
in 2.2. Why aren't they ported also to 2.1?
Please, please, consider upgrading both branches
13 matches
Mail list logo
