right, John... now how do we get those two suggestions together?
inputSuggestRemote inputSuggestAjax inputSuggestAjx inputSuggestAx I wouldn't separate out the components to their own taglib - the name should clearly state what the component is about by itself, this shouldn't be dependent on the taglib prefix. regards, Martin On 7/15/05, John Fallows <[EMAIL PROTECTED]> wrote: > On 7/14/05, Sean Schofield <[EMAIL PROTECTED]> wrote: > > Since we are going to have two components for the forseeable future > > (at least in the sandbox) can I *suggest* that we call the ajax one > > "ajaxSuggest"? > > > > IMO ajaxInputSuggest is a little too wordy and easy to confuse with > > inputSuggest. > > The lower case first letter makes this appear to be a suggestion for > the tag name. > > The standard naming convention for tags with a behavioral superclass > of UIInput is input*, and ajaxSuggest does not follow that convention. > > You should pick a tag name that begins with input, such as > inputAjaxSuggest, to help users understand both the behavioral > contract and the interactive presentation contract for this component. > > Kind Regards, > John Fallows. >
