[Seaside][ShoreComponents] DatePicker discussion

[Pavel Krivanek]

>>>openTag: aString
>>>   TagNotification raiseRenderer: self tagName: aString.
>>>   self document openTag: aString attributes: self attributes.
>>>   attributeBuffer := nil.
>>>      
>>>
>>I'm concerned about the performance implications of signalling a
>>notification on every single openTag:.  At least in Squeak, I think
>>that will add a ton of overhead.
>>
>>If you give your elements ids, couldn't you do something like this?
>>(Not sure if my JS is correct here).
>>
>>html datePickerOn: #dateScheduled of: self.
>>html script: 'document.getElementById("someElement").onclick =
>>function() {....}'.
>>    
>>
>
>I don't like the idea either, basically because it violates the
>encapsulation of the date-picker component. What you should rather do,
>is to have an abstract superclass with template methods or
>pluggable-properties to generate different view-code.
>
>Lukas
>
I wanted to suggest it right now. We may have special wrapper classes 
for widgets like date picker. They will not be components and their 
instances will be created and deleted only during rendering phase.

-- Pavel