<div>Hi!<br> </div>
<div>During my trial to create a generic WABrush seaside editor</div>
<div>i have found some questionable namings in WABrush and all subclasses!</div>
<div>Ill hope that some of these could be addressed with Seaside 2.9!</div>
<div>Here is the result after checking mostly all classes:</div>
<div><br>- WASelectTag<br> - #enabled: aBlock <-> #disabled: Boolean .. Its a little bit confusing to use enabled: in that case</div>
<div>
<p>- WATimeInput<br> - public api -> public<br> - initialize-release -> initialization<br><br>- WAAnchorTag <br> - conveniance -> convenience<br> - #tag -> category accessing<br><br>- WAHeadingTag<br> - #tag -> category accessing<br>
<br>- WATagBrush<br> -#tag -> category accessing<br><br>- WAImageTag<br> -#tag -> category accessing<br><br>- WADivTag<br> - public api -> public<br><br>- WAFormInputTag: .. why is it necessary to set also the class ?<br>
with: aBlock<br> self type isNil ifFalse: [<br> self attributes at: 'type' ifAbsentPut: [ self type ].<br> self class: self type ].<br> super with: aBlock<br><br>WATagBrush, WACheckboxTag, WARAdionButtonTag, WASubmitButtonTag <br>
- #canHaveShortcut -> testing<br><br>- WACheckboxTag<br> #submitFormNamed: -> conveniance (see WAAnchorTag)<br><br>- WAButtonTag<br> - initialize-release -> initialization<br><br>- WAImageButtonTag<br> - callback: -> callbacks<br>
<br>- WAFormTag<br> - initialize-release -> initialization<br><br>- WAGenericTag<br> - initialize-release -> initialization<br><br>- WAHeadingTag <br> - conveniance -> convenience<br> - #tag -> accessing<br>
<br>- WAImageTag<br> - initialize-release -> initialization<br> - #tag -> accessing<br></p></div>
<div>Cheers </div>
<div>Gerhard</div>
<div> </div>