[Grok-dev] Viewlets: Check for availability

[Christian Klinger]

Hi JW,

i am ok with the change. It's fine not to use the filter method of the
BaseClass from ViewletManagerBase right? We lost then the filter for
canAccess.

So i am +1 for the change and releasing ;)

Christian


> On 6/15/11 14:44 , Sylvain Viollon wrote:
>> On Wed, 15 Jun 2011 13:10:20 +0200
>> Jan-Wijbrand Kolman<janwijbrand at gmail.com>  wrote:
>>> On 6/15/11 08:08 , Christian Klinger wrote:
>>>> i think there were some discussions lately about this topic on a
>>>> sprint. I don't know to which conclusions we come...
>>>>
>>>> For me i want to add a +1 for it.
>>>
>>> I think to remember we explicitly decided not to add this feature,
>>> somewhere along the line of "different applications have different
>>> needs in this regards, and it is easy to add yourself".
>>>
>>> Not sure anymore though.
>>>
>>> You suggestion apearts to be reasonable "safe" to add though. Thinking
>>> about it now, I'd not be against it.
>>>
>>> BTW, I'm about to work on grokcore.view and grokcore.viewlet soon
>>> anyway for content providers. I could try to include this suggestion
>>> too.
>>
>>    Honestly I use it at few places, and my customer needs it as well (on
>>    plain viewlets).
>>
>>    An available method on a Viewlet and check it in the filter of the
>>    ViewletManager would be great.
>>
>>    +1 from my part, and +1 from the part of my customer so that makes
>>    +2, and it is justified.
>
> Checkin on the grokcore.viewlet trunk. I think the change is backwards
> compatible. If you guys agree, I could create a release quickly.
>
> regards, jw