cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Giacomo Pati <giac...@apache.org>
Subject RE: [VOTE] Status of Portal blocks
Date Thu, 26 Aug 2004 14:14:24 GMT
On Thu, 26 Aug 2004, Carsten Ziegeler wrote:

> Giacomo Pati wrote:
>>>
>>> a) mark portal-fw as deprecated
>>
>> Hmm.. deprecated mean "Hey man, go change you portal as it
>> will be removed in the future" is this you want to signal?
>>
> Yes :( The portal-fw is a nice portal framework, but the code
> is very very ugly (I know it 'cause I wrote it). The new
> portal block is (apart from tools) a 100% replacement which
> is even faster and consumes less memory.
> Deperecating does not mean removing and deprecating means that
> it is still supported. So if any bugs occur, we will fix
> them - but if you start a new project, you should use
> the new portal block; that's why I think we should deprecate
> the old one.

If one deprecates something it suggests a replacement. IIRC the new portal 
lacks some administration tools which the old one has (user admin, etc.), 
right?

So, what is your suggestion instead of using the old portal block than?

-- 
Giacomo Pati
Otego AG, Switzerland - http://www.otego.com
Orixo, the XML business alliance - http://www.orixo.com

Mime
View raw message