Stay cool, stay calm, everyone, I just had to move that in as I am experimenting a little on the Ajax stuff. I basically took some of Werner's ideas, merged that with the prototype library, and tried to follow what Sean has laid out for his inputSuggest. But please wait until I get closer to my goal of getting used to AJAX, and we can then start off discussing about what to do with the components.
I will especially be experimenting what to do about the backend-integration. Right now, also after talking to Manfred and Thomas, there is still some fog in my mind which needs to clear, but I think I might basically let each Ajax request run through the faces request/response and stop dead at a phase listener which then decides what will be rendered out. Regard this only as a moving target right now! regards, Martin On 7/9/05, Bruno Aranda <[EMAIL PROTECTED]> wrote: > I am sure we will reach a consensus on this and get the best component > possible. I give you my opinion in both components, not knowing the > insights of any of them. > Regarding the name of the component, I like more the name > 'inputSuggest', because it is easy to remember and someone who do not > know what this component does will associate directly to Google's > suggest. I like more the suggestions scroll-box of the Matt-Sean > component as it seams cleaner, but I like the input box coloring of > Werner's component. Both of them are great so the result of the merge > would be even greater! > > Regards, > > Bruno > > - Suggestions display: I like more the scroll box of the > 2005/7/9, Werner Punz <[EMAIL PROTECTED]>: > > Werner Punz wrote: > > > > > > Actually just checked the sources I got in today from the svn sandbox, > > > there is nothing from me left anymore :-D > > > Command back, that suff is from someone else, but they placed the code > > > for the autocomplete on top of the prototype which is excellent > > > > > > > > Btw... another thing, I checked the code for the new autocomplete > > Javascripts, it is absolutely excellent. > > Unfortunately it has the same component leak problems like the effects. > > > > (I am not sure, but I think the guy who wrote this stuff, > > basically must be the same one I contacted yesterday, because of a > > component leak problem in the basic effects code) > > > > >
