That is another option, yes, I had not thought about it, I imagine because of the name. If we do it this way, to DateField we would have to change the variables to lowercase and menubutton to button. This change would only affect users who have extended DateFieldView.
Does anyone see any other considerations? @yishay, What if we were to rename the interface to ... IInputAndButtonView (to make it more generic)? Hiedra -----Mensaje original----- De: Yishay Weiss <yishayj...@hotmail.com> Enviado el: martes, 17 de mayo de 2022 12:13 Para: dev@royale.apache.org Asunto: RE: New Interface Jewel Looks like textInput and button are all the bead requires and both are defined in IComboBoxView. Personally, I think it's ok for DateFieldView to implement IComboBoxView. From: Maria Jose Esteve<mailto:mjest...@iest.com> Sent: Monday, May 16, 2022 11:36 AM To: dev@royale.apache.org<mailto:dev@royale.apache.org> Subject: RE: New Interface Jewel I stand by my question... > What name would you give to an iBeadView that defines a TextInput and a Button (ComboBoxView, DateFieldView,...)? > ÂżIViewTextButton? My purpose is to unify beads of type "ComboBoxDisabled", "DateFieldDisabled", ..., into one (they share all the code except for the reference to the view) Hiedra -----Mensaje original----- De: Maria Jose Esteve <mjest...@iest.com> Enviado el: lunes, 16 de mayo de 2022 9:51 Para: dev@royale.apache.org Asunto: RE: New Interface Jewel There is a similar "IComboBoxView". Sorry Hiedra -----Mensaje original----- De: Maria Jose Esteve <mjest...@iest.com> Enviado el: lunes, 16 de mayo de 2022 9:38 Para: dev@royale.apache.org Asunto: New Interface Jewel Hi guys, What name would you give to an iBeadView that defines a TextInput and a Button (ComboBoxView, DateFieldView,...)? ÂżIViewTextButton? Hiedra
