Re: Suggested extension for WASelectTag
Philippe Marschall <[email protected]>
| Newsgroups | gmane.comp.lang.smalltalk.squeak.seaside |
|---|---|
| Message-ID | <CA+LFMPiffn8Kkys+syXW_Xkkvw3ZuJ=nO4YYYxJo_Bt9khpE_A@mail.gmail.com> |
On Sat, Jul 1, 2017 at 7:24 AM, [email protected] <[email protected]> wrote: > ... > > Was this available already and did I overlook it? Not that I know of. > Does this sound reasonable? Worth adding to Seaside? I have some issues with the API: - Config is an abbreviation, we don't usually use abbreviations - we don't usually use the Block suffix for methods that accept blocks, e.g.. #callback: not #callbackBlock:, see also #titles: (WAIframeTag >> #rootBlock is a bad example) I don't really have a good proposal, maybe #optionRenderer: but the renderer wouldn't render the whole option, only customize it. As Paul has noted if you want full control you may be better off rendering the the options yourself as done in WAInputElementContainer>>#renderSingleSelectionCustomOn [1] [1] https://github.com/SeasideSt/Seaside/blob/master/repository/Seaside-Tests-Functional.package/WAInputElementContainer.class/instance/renderSingleSelectionCustomOn..st Cheers Philippe _______________________________________________ seaside mailing list [email protected] http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside