[Q] Subclassing WAComponent or WACompound?

Hi,

I'm currently developing project manamgent application(simple, just for learning seaside and its canvas api) and want to create date selector widget(?) with
calendar support - I mean attaching small button toggling calendar to date input tag. I first tried and make it work with subclassing WAComponent which
has two subcomponent: date input and mini calendar. But this does break the style - original code can be written like this

html dateInput value: self project dueDate; callback: [ :v | self project dueDate: v ]

but modified code be written like this

html render: dueDateEditor

so, here comes the question, which is better case, subclassing WACompoent or create a new tag for new widget by subclassing WACompound?

Thanks in advance.
_______________________________________________
Seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside

S.J.Chun a écrit :

>so, here comes the question, which is better case, subclassing WACompoent or create a new tag for new widget by subclassing WACompound?
>
>  
>
WACompound subclasses were introduced to ease migration from the
"classic'" api
#dateInputWithValue:callback: and #timeInputWithValue:callback:
I suggest you subclass WAComponent.
HTH
Michel.
_______________________________________________
Seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside