[jQuery] Re: Release: autocomplete 1.0 alpha
Shelane, Ok, I tried the width thing by initially putting "300px" and nothing happened. Then I entered 300 and it worked fine. Can you place in the documentation the expected value type (an integer value). Or maybe allow people to set measurement types if you detect it's not an integer. Fixed! The value is just passed through to jQuery's css method as the width property, but so far only allowed numbers. Now it also accepts strings, so you can set px or em or whatever you like. -- Jörn Zaefferer http://bassistance.de
[jQuery] Re: Release: autocomplete 1.0 alpha
Yes, I had a malformed style :-(
I fixed it. I should have checked with firebug. That's for the extra pair
of eyes.
On 4/30/07 4:11 PM, "Dan G. Switzer, II" <[EMAIL PROTECTED]> wrote:
>
> Shelane,
>
>> That's why I did this:
>> .ac_loading {
>>background: ('/resources/images/indicator.gif') right center no-repeat;
>> }
>
> Firefox is reporting the .ac_loading class as:
>
> .ac_loading {
> }
>
> I'm looking at: http://education.llnl.gov/jQuery/ajax.html
>
> -Dan
>
>
>
[jQuery] Re: Release: autocomplete 1.0 alpha
Shelane,
>That's why I did this:
>.ac_loading {
>background: ('/resources/images/indicator.gif') right center no-repeat;
>}
Firefox is reporting the .ac_loading class as:
.ac_loading {
}
I'm looking at: http://education.llnl.gov/jQuery/ajax.html
-Dan
[jQuery] Re: Release: autocomplete 1.0 alpha
That's why I did this:
.ac_loading {
background: ('/resources/images/indicator.gif') right center no-repeat;
}
On 4/30/07 3:42 PM, "Dan G. Switzer, II" <[EMAIL PROTECTED]> wrote:
>
> Shelane,
>
>> I don't notice my little indicator when it's doing the lookup. The file
>> that I have in my css file is there. Maybe my results are coming back too
>> fast :-)
>
> The odds are you the path you have in your CSS to the indicator icon is
> wrong. Remember the image path is relative from the CSS file, not the html
> page the CSS page is called from.
>
> I'd double check your CSS.
>
> -Dan
>
>
>
[jQuery] Re: Release: autocomplete 1.0 alpha
Shelane, >I don't notice my little indicator when it's doing the lookup. The file >that I have in my css file is there. Maybe my results are coming back too >fast :-) The odds are you the path you have in your CSS to the indicator icon is wrong. Remember the image path is relative from the CSS file, not the html page the CSS page is called from. I'd double check your CSS. -Dan
[jQuery] Re: Release: autocomplete 1.0 alpha
Ok, I tried the width thing by initially putting "300px" and nothing
happened. Then I entered 300 and it worked fine. Can you place in the
documentation the expected value type (an integer value). Or maybe allow
people to set measurement types if you detect it's not an integer.
I don't notice my little indicator when it's doing the lookup. The file
that I have in my css file is there. Maybe my results are coming back too
fast :-)
Just want to make the comment that I'm glad you're working on this. I can't
wait to fully abandon my script.aculo.us implementation and not ever have to
worry about the competing libraries again :-) or the super bloated prototype
just to have one silly little piece of functionality.
On 4/30/07 2:55 PM, "Jörn Zaefferer" <[EMAIL PROTECTED]> wrote:
>
> Shelane,
>
> thanks for your reports! That helps a lot. In detail:
>> I believe I found a bug in the new autocompleter. Line 157 has:
>> var $input = $(input).attr("autocomplete",
>> "off").addClass(options.inputClass);
>>
> Good catch, fixed.
>> If the default caching is set at 10 and matcheSubset default is true, why is
>> it making a second call to the server when I add a new letter.
>>
>> First input: cap
>> Additional letter: i
>>
>> Then a new query goes out to the server:
>> http://education.llnl.gov/jQuery/pages/lookup.lasso?q=capi&limit=50
>>
> That isn't supposed to happen, I'll need to check that.
>> Second question: is there a way I can do max all? It seems counter
>> intuitive if caching is used. Unless it's set so that if caching is used,
>> only the final output is limited.
>>
>> Third question: I have seen a few examples out there including these params:
>> highlight: false,
>> highlight: function(value) {
>> //alert(value);
>> return value;
>> },
>>
>> But I don't see anything documenting these (in your documentation online).
>>
> I haven't made a new release yet. To keep up-to-date with the latest
> revision you can get it directly from the repository:
> http://dev.jquery.com/browser/trunk/plugins/autocomplete/jquery.autocomplete.j
> s?format=txt
> The updated documentation is already there, but not very readable.
>> Forgot to add my example link:
>>
>> http://education.llnl.gov/jQuery/ajax.html
>>
>> Click auto complete (unknown if this is working at all in IE right now).
>> Definitely in FF. Your plugin is the second example.
> You may want to set the width of the displayed select box via the width
> option. That should help to avoid line breaks within one item.
>
> Let me know if you notice anything else!
[jQuery] Re: Release: autocomplete 1.0 alpha
Shelane,
thanks for your reports! That helps a lot. In detail:
I believe I found a bug in the new autocompleter. Line 157 has:
var $input = $(input).attr("autocomplete",
"off").addClass(options.inputClass);
Good catch, fixed.
If the default caching is set at 10 and matcheSubset default is true, why is
it making a second call to the server when I add a new letter.
First input: cap
Additional letter: i
Then a new query goes out to the server:
http://education.llnl.gov/jQuery/pages/lookup.lasso?q=capi&limit=50
That isn't supposed to happen, I'll need to check that.
Second question: is there a way I can do max all? It seems counter
intuitive if caching is used. Unless it's set so that if caching is used,
only the final output is limited.
Third question: I have seen a few examples out there including these params:
highlight: false,
highlight: function(value) {
//alert(value);
return value;
},
But I don't see anything documenting these (in your documentation online).
I haven't made a new release yet. To keep up-to-date with the latest
revision you can get it directly from the repository:
http://dev.jquery.com/browser/trunk/plugins/autocomplete/jquery.autocomplete.js?format=txt
The updated documentation is already there, but not very readable.
Forgot to add my example link:
http://education.llnl.gov/jQuery/ajax.html
Click auto complete (unknown if this is working at all in IE right now).
Definitely in FF. Your plugin is the second example.
You may want to set the width of the displayed select box via the width
option. That should help to avoid line breaks within one item.
Let me know if you notice anything else!
--
Jörn Zaefferer
http://bassistance.de
[jQuery] Re: Release: autocomplete 1.0 alpha
Forgot to add my example link:
http://education.llnl.gov/jQuery/ajax.html
Click auto complete (unknown if this is working at all in IE right now).
Definitely in FF. Your plugin is the second example.
On 4/30/07 2:35 PM, "Shelane Enos" <[EMAIL PROTECTED]> wrote:
>
> Also, a few other issues.
>
> If the default caching is set at 10 and matcheSubset default is true, why is
> it making a second call to the server when I add a new letter.
>
> First input: cap
> Additional letter: i
>
> Then a new query goes out to the server:
> http://education.llnl.gov/jQuery/pages/lookup.lasso?q=capi&limit=50
>
> Second question: is there a way I can do max all? It seems counter
> intuitive if caching is used. Unless it's set so that if caching is used,
> only the final output is limited.
>
> Third question: I have seen a few examples out there including these params:
> highlight: false,
> highlight: function(value) {
> //alert(value);
> return value;
> },
>
> But I don't see anything documenting these (in your documentation online).
>
> Thanks.
>
> On 4/30/07 2:05 PM, "Shelane" <[EMAIL PROTECTED]> wrote:
>
>>
>> Jörn,
>>
>> I believe I found a bug in the new autocompleter. Line 157 has:
>> var $input = $(input).attr("autocomplete",
>> "off").addClass(options.inputClass);
>>
>> This throws a javascript error if jQuery.noConflict() has been called:
>> $(input).attr is not a function
>>
>> changing it to var $input = jQuery(input).attr("autocomplete",
>> "off").addClass(options.inputClass);
>>
>> fixes the problem
>>
>> On Apr 19, 11:08 am, Jörn Zaefferer <[EMAIL PROTECTED]> wrote:
>>> Dan G. Switzer, II schrieb:>> What would be passed to the function? The
>>> containing li? a jQuery object
> containing the containing li? The HTML text?
>>>
The source is available here:
http://dev.jquery.com/browser/trunk/plugins/autocomplete/jquery.autoc...
.js
>>>
[...]
>>>
At the moment it runs against li.innerHTML.
>>>
>>> So far it was internal only, I'd pass the formatted string as the first
>>> argument and the other stuff in addition.
>>> Formatting would be very flexible then. Default takes a simple string
>>> and adds simple highlighting. Then you can replace that simple string
>>> with some custom formatting and default highlighting. Or you use
>>> formatting and include highlighting and switch off default
>>> highlighting... I hope we really need that degree.
>>>
>>> Ah, and thanks Dan for the regex and the link, I'll test that.
>>>
>>> --
>>> Jörn Zaefferer
>>>
>>> http://bassistance.de
>>
>>
>>
>
>
[jQuery] Re: Release: autocomplete 1.0 alpha
Also, a few other issues.
If the default caching is set at 10 and matcheSubset default is true, why is
it making a second call to the server when I add a new letter.
First input: cap
Additional letter: i
Then a new query goes out to the server:
http://education.llnl.gov/jQuery/pages/lookup.lasso?q=capi&limit=50
Second question: is there a way I can do max all? It seems counter
intuitive if caching is used. Unless it's set so that if caching is used,
only the final output is limited.
Third question: I have seen a few examples out there including these params:
highlight: false,
highlight: function(value) {
//alert(value);
return value;
},
But I don't see anything documenting these (in your documentation online).
Thanks.
On 4/30/07 2:05 PM, "Shelane" <[EMAIL PROTECTED]> wrote:
>
> Jörn,
>
> I believe I found a bug in the new autocompleter. Line 157 has:
> var $input = $(input).attr("autocomplete",
> "off").addClass(options.inputClass);
>
> This throws a javascript error if jQuery.noConflict() has been called:
> $(input).attr is not a function
>
> changing it to var $input = jQuery(input).attr("autocomplete",
> "off").addClass(options.inputClass);
>
> fixes the problem
>
> On Apr 19, 11:08 am, Jörn Zaefferer <[EMAIL PROTECTED]> wrote:
>> Dan G. Switzer, II schrieb:>> What would be passed to the function? The
>> containing li? a jQuery object
containing the containing li? The HTML text?
>>
>>> The source is available here:
>>> http://dev.jquery.com/browser/trunk/plugins/autocomplete/jquery.autoc...
>>> .js
>>
>>> [...]
>>
>>> At the moment it runs against li.innerHTML.
>>
>> So far it was internal only, I'd pass the formatted string as the first
>> argument and the other stuff in addition.
>> Formatting would be very flexible then. Default takes a simple string
>> and adds simple highlighting. Then you can replace that simple string
>> with some custom formatting and default highlighting. Or you use
>> formatting and include highlighting and switch off default
>> highlighting... I hope we really need that degree.
>>
>> Ah, and thanks Dan for the regex and the link, I'll test that.
>>
>> --
>> Jörn Zaefferer
>>
>> http://bassistance.de
>
>
>
[jQuery] Re: Release: autocomplete 1.0 alpha
Jörn,
I believe I found a bug in the new autocompleter. Line 157 has:
var $input = $(input).attr("autocomplete",
"off").addClass(options.inputClass);
This throws a javascript error if jQuery.noConflict() has been called:
$(input).attr is not a function
changing it to var $input = jQuery(input).attr("autocomplete",
"off").addClass(options.inputClass);
fixes the problem
On Apr 19, 11:08 am, Jörn Zaefferer <[EMAIL PROTECTED]> wrote:
> Dan G. Switzer, II schrieb:>> What would be passed to the function? The
> containing li? a jQuery object
> >> containing the containing li? The HTML text?
>
> > The source is available here:
> >http://dev.jquery.com/browser/trunk/plugins/autocomplete/jquery.autoc...
> > .js
>
> > [...]
>
> > At the moment it runs against li.innerHTML.
>
> So far it was internal only, I'd pass the formatted string as the first
> argument and the other stuff in addition.
> Formatting would be very flexible then. Default takes a simple string
> and adds simple highlighting. Then you can replace that simple string
> with some custom formatting and default highlighting. Or you use
> formatting and include highlighting and switch off default
> highlighting... I hope we really need that degree.
>
> Ah, and thanks Dan for the regex and the link, I'll test that.
>
> --
> Jörn Zaefferer
>
> http://bassistance.de
[jQuery] Re: Release: autocomplete 1.0 alpha
Yes. This is possible and it is the situation I described. Thank you for your patience. I must say that support on this list is just awesome in relation to other projects. Yoyo
[jQuery] Re: Release: autocomplete 1.0 alpha
Dan G. Switzer, II schrieb: What would be passed to the function? The containing li? a jQuery object containing the containing li? The HTML text? The source is available here: http://dev.jquery.com/browser/trunk/plugins/autocomplete/jquery.autocomplete .js [...] At the moment it runs against li.innerHTML. So far it was internal only, I'd pass the formatted string as the first argument and the other stuff in addition. Formatting would be very flexible then. Default takes a simple string and adds simple highlighting. Then you can replace that simple string with some custom formatting and default highlighting. Or you use formatting and include highlighting and switch off default highlighting... I hope we really need that degree. Ah, and thanks Dan for the regex and the link, I'll test that. -- Jörn Zaefferer http://bassistance.de
[jQuery] Re: Release: autocomplete 1.0 alpha
Brian,
>What would be passed to the function? The containing li? a jQuery object
>containing the containing li? The HTML text?
The source is available here:
http://dev.jquery.com/browser/trunk/plugins/autocomplete/jquery.autocomplete
.js
581 function dataToDom() {
582 var num = limitNumberOfItems(data.length);
583 for (var i=0; i < num; i++) {
584 if (!data[i])
585 continue;
586 function highlight(value) {
587 return value.replace(new RegExp("(" + term + ")",
"gi"), "$1");
588 }
589 jQuery("").html( options.formatItem
590 ? highlight(options.formatItem(data[i].data,
i+1, num))
591 : highlight(data[i].value) ).appendTo(list);
592 }
593 listItems = list.find("li");
594 if ( options.selectFirst ) {
595 listItems.eq(0).addClass(CLASSES.ACTIVE);
596 active = 0;
597 }
598 }
At the moment it runs against li.innerHTML.
-Dan
[jQuery] Re: Release: autocomplete 1.0 alpha
> Dan G. Switzer, II schrieb:
>> Jörn,
>>
>>
>>> Fully agreed, I'll make that optional. I've got another request for an
>>> even more sophicistacted highlighting, seems like a good idea to
>>> implement it not only as a boolean option.
>>>
>>
>> You could also just define that highlight function as the default option
>> for
>> an onHighlight setting. That way someone could just overwrite the
>> default
>> behavior.
>>
>> I'd like to see both a highlight: true/false and onHighligh:
>> function(){}
>> option. That would provide tons of flexibility.
>>
> How about this:
> @option Boolean|Function highlight Whether and how to highlight matches
> in the select box. Set to false to disable. Set to a function to
> customize. Default: Wraps the search term in a element
Jörn,
What would be passed to the function? The containing li? a jQuery object
containing the containing li? The HTML text?
- Brian
[jQuery] Re: Release: autocomplete 1.0 alpha
Jörn,
>> I'd like to see both a highlight: true/false and onHighligh: function(){}
>> option. That would provide tons of flexibility.
>>
>How about this:
>@option Boolean|Function highlight Whether and how to highlight matches
>in the select box. Set to false to disable. Set to a function to
>customize. Default: Wraps the search term in a element
That would work. My nature is to break the 2 into separate options--only
because I think it's confusing to novice users. But that definitely would
work.
Also, I think maybe you could fix the HTML issue by changing your function
to:
function highlight(value) {
return value.replace(new RegExp("(?]*)(" + term + ")", "gi"),
"$1$2");
}
I did not test this yet. You might want to throw it at some HTML. And test
it.
There's also some other suggestions here:
http://regexadvice.com/forums/thread/24779.aspx
-Dan
[jQuery] Re: Release: autocomplete 1.0 alpha
Dan G. Switzer, II schrieb:
Jörn,
Fully agreed, I'll make that optional. I've got another request for an
even more sophicistacted highlighting, seems like a good idea to
implement it not only as a boolean option.
You could also just define that highlight function as the default option for
an onHighlight setting. That way someone could just overwrite the default
behavior.
I'd like to see both a highlight: true/false and onHighligh: function(){}
option. That would provide tons of flexibility.
How about this:
@option Boolean|Function highlight Whether and how to highlight matches
in the select box. Set to false to disable. Set to a function to
customize. Default: Wraps the search term in a element
--
Jörn Zaefferer
http://bassistance.de
[jQuery] Re: Release: autocomplete 1.0 alpha
Jörn,
>Fully agreed, I'll make that optional. I've got another request for an
>even more sophicistacted highlighting, seems like a good idea to
>implement it not only as a boolean option.
You could also just define that highlight function as the default option for
an onHighlight setting. That way someone could just overwrite the default
behavior.
I'd like to see both a highlight: true/false and onHighligh: function(){}
option. That would provide tons of flexibility.
-Dan
[jQuery] Re: Release: autocomplete 1.0 alpha
Dan G. Switzer, II schrieb:
Jörn,
The highlight code you're using code break HTML.
Could you detail that?
function formatItem(d){
return "" + d[1] + "";
}
If the user would try searching for the word "str", your highlight code
would try to wrap strong tags inside my strong tags.
Ok, so I need to exclude html from the search?
Besides, someone may not actually want the highlight behavior. It's
definitely not a behavior I want every time.
Fully agreed, I'll make that optional. I've got another request for an
even more sophicistacted highlighting, seems like a good idea to
implement it not only as a boolean option.
--
Jörn Zaefferer
http://bassistance.de
[jQuery] Re: Release: autocomplete 1.0 alpha
Yoyo, >I was thinking about using multiple autocomplete field to allow typing >tags, >this way one can easly add free tags anytime along with autocompletion if >particular tag was enetered before. Like I said like in del.icio.us. > >Is this possible with this plugin? Yes. This is possible and it is the situation I described. -Dan
[jQuery] Re: Release: autocomplete 1.0 alpha
The first piece of code I implemented into was a "City" field for an application. So once a particular city is entered in the free-form text field, it will show up in the autocomplete the next time a user hits the page. So next time it is not possible to add another city in autocomplete box? I was thinking about using multiple autocomplete field to allow typing tags, this way one can easly add free tags anytime along with autocompletion if particular tag was enetered before. Like I said like in del.icio.us. Is this possible with this plugin?
[jQuery] Re: Release: autocomplete 1.0 alpha
Yoyo, >Well, my English is not so good so I don't know If I understand it >properly. >What I mean was something like tag autocompleting in del.icio.us posting >page. Yes, all the autocomplete field is a text field. You can enter whatever text you want. The first piece of code I implemented into was a "City" field for an application. So once a particular city is entered in the free-form text field, it will show up in the autocomplete the next time a user hits the page. -Dan
[jQuery] Re: Release: autocomplete 1.0 alpha
I like the second option, or Dan's method as described in a later post, where you allow the developer to pass an expression which determines whether the row should be displayed or not. I have hacked together a demo for our users using Dan's autocomplete script, which populates a select menu and uses your third option (disallowing the already selected option to be selected again), and while it works great, the users all commented they would rather not see the option displayed once again, once it has been selected. Jeff On Apr 18, 1:28 pm, Jörn Zaefferer <[EMAIL PROTECTED]> wrote: > Jeff Fleitz schrieb:> One thing that I think would be useful to add (I pinged > Dan about this > > the other day), is an option to restrict the multiple option to > > distinct values, so that duplicate selections are prevented. > > That is an interesting point. > > I see three ways to handle this: > - Let the user enter whatever he wants, using the autocomplete only as a > helper. > - Remove anything that was already entered from the proposed elements > - Disallow/remove a selected value if it was already entered > > What would be the better solution? > > -- > Jörn Zaefferer > > http://bassistance.de
[jQuery] Re: Release: autocomplete 1.0 alpha
Dan G. Switzer, II schrieb: Yoyo, Is it possible to insert custom values in multiple input? If for example I try to write "Cracow" I got "Creola" If you want freeform text to be entered, then you can't try to map the text to another value (like a primary key.) So, you could use the multiple as a text only input field in online e-mail application to type in address to send a message to without a problem. What Dan said. Does that answer your question? Well, my English is not so good so I don't know If I understand it properly. What I mean was something like tag autocompleting in del.icio.us posting page.
[jQuery] Re: Release: autocomplete 1.0 alpha
Jörn,
>> The highlight code you're using code break HTML.
>>
>Could you detail that?
function formatItem(d){
return "" + d[1] + "";
}
If the user would try searching for the word "str", your highlight code
would try to wrap strong tags inside my strong tags.
Besides, someone may not actually want the highlight behavior. It's
definitely not a behavior I want every time.
-Dan
[jQuery] Re: Release: autocomplete 1.0 alpha
Dan G. Switzer, II schrieb: Jörn, Could we hijack the current result event for this? Currenlty nothing is returned. If the user doesn't want the result, he could return false or whatever to prevent it. Switching the order in which the result is set to the input and the callback is executed shouldn't be a problem. What I was thinking was something like this: [...] Now, if the user defines an onProccessRow function, they can control whether or not to display the current item. I see, that makes more sense. On a side note, I think maybe the "highlight" function should be optional. I could see where that would be that could be problematically if you're using the formatItem() function. Ok. The highlight code you're using code break HTML. Could you detail that? -- Jörn Zaefferer http://bassistance.de
[jQuery] Re: Release: autocomplete 1.0 alpha
Jörn,
>Could we hijack the current result event for this? Currenlty nothing is
>returned. If the user doesn't want the result, he could return false or
>whatever to prevent it. Switching the order in which the result is set
>to the input and the callback is executed shouldn't be a problem.
What I was thinking was something like this:
function dataToDom() {
var num = limitNumberOfItems(data.length);
for (var i=0; i < num; i++) {
var bProcessRow = options.onProcessRow ?
options.onProcessRow(data[i]) : true;
if (!data[i] || !bProcessRow )
continue;
function highlight(value) {
return value.replace(new RegExp("(" + term + ")",
"gi"), "$1");
}
jQuery("").html( options.formatItem
? highlight(options.formatItem(data[i].data, i+1,
num))
: highlight(data[i].value) ).appendTo(list);
}
listItems = list.find("li");
if ( options.selectFirst ) {
listItems.eq(0).addClass(CLASSES.ACTIVE);
active = 0;
}
}
Now, if the user defines an onProccessRow function, they can control whether
or not to display the current item.
On a side note, I think maybe the "highlight" function should be optional. I
could see where that would be that could be problematically if you're using
the formatItem() function.
The highlight code you're using code break HTML.
-Dan
[jQuery] Re: Release: autocomplete 1.0 alpha
Dan G. Switzer, II schrieb: Jörn, I see three ways to handle this: - Let the user enter whatever he wants, using the autocomplete only as a helper. - Remove anything that was already entered from the proposed elements - Disallow/remove a selected value if it was already entered What would be the better solution? I actually sent you a note offlist about this the other day. I would think the best method would be to provide another event hook that when looking to see if the current row should be added as a element. If the event hook exists, and returns false, you don't add it to the output. If true or null, you add it. That way the developer can code his logic to see if he wants the item to be displayed or not. Could we hijack the current result event for this? Currenlty nothing is returned. If the user doesn't want the result, he could return false or whatever to prevent it. Switching the order in which the result is set to the input and the callback is executed shouldn't be a problem. -- Jörn Zaefferer http://bassistance.de
[jQuery] Re: Release: autocomplete 1.0 alpha
On 4/18/07, Jörn Zaefferer <[EMAIL PROTECTED]> wrote: What about the links on the wiki plugin page? Replace both? Point to the better versions, no need to point to my page. I'm not that vain, and I'm nicely mentioned in the current version of the plugin :-)
[jQuery] Re: Release: autocomplete 1.0 alpha
Jörn, >I see three ways to handle this: >- Let the user enter whatever he wants, using the autocomplete only as a >helper. >- Remove anything that was already entered from the proposed elements >- Disallow/remove a selected value if it was already entered > >What would be the better solution? I actually sent you a note offlist about this the other day. I would think the best method would be to provide another event hook that when looking to see if the current row should be added as a element. If the event hook exists, and returns false, you don't add it to the output. If true or null, you add it. That way the developer can code his logic to see if he wants the item to be displayed or not. -Dan
[jQuery] Re: Release: autocomplete 1.0 alpha
Jörn/Dylan, >>> > I'm glad to release the first version of the rewritten autocomplete >>> > plugin, based on the work by ... >>> > There is now a page with a download, link to the demo and >>> documentation: >>> > http://bassistance.de/jquery-plugins/jquery-plugin-autocomplete/ >>> >>> Great! >> >> Really nice work Jorn, you took what was there and made it better. I >> think I'm going to take my initial autocomplete page down, and refer >> to the improved work. It seems logical that we point jQuery users (new >> and current) to the best version. > >What about the links on the wiki plugin page? Replace both? I wouldn't replace anything until the bugs are all fixed. -Dan
[jQuery] Re: Release: autocomplete 1.0 alpha
Dan G. Switzer, II schrieb: Yoyo, Is it possible to insert custom values in multiple input? If for example I try to write "Cracow" I got "Creola" If you want freeform text to be entered, then you can't try to map the text to another value (like a primary key.) So, you could use the multiple as a text only input field in online e-mail application to type in address to send a message to without a problem. What Dan said. Does that answer your question? -- Jörn Zaefferer http://bassistance.de
[jQuery] Re: Release: autocomplete 1.0 alpha
Dylan Verheul schrieb: On 4/18/07, Mika Tuupola <[EMAIL PROTECTED]> wrote: On Apr 18, 2007, at 2:35 PM, Fil wrote: >> http://bassistance.de/jquery-plugins/jquery-plugin-autocomplete/ > > Great work :) Dylan seems to be source of many great plugins ;) I'll take that as a compliment :-) You should. Btw. four of six of my plugins are based on other plugins... -- Jörn Zaefferer http://bassistance.de
[jQuery] Re: Release: autocomplete 1.0 alpha
Fil schrieb: http://bassistance.de/jquery-plugins/jquery-plugin-autocomplete/ Great work :) You have a bug at Thanks Fil, gonna fix that. -- Jörn Zaefferer http://bassistance.de
[jQuery] Re: Release: autocomplete 1.0 alpha
Dylan Verheul schrieb: On 4/18/07, Dylan Verheul <[EMAIL PROTECTED]> wrote: On 4/17/07, Jörn Zaefferer <[EMAIL PROTECTED]> wrote: > I'm glad to release the first version of the rewritten autocomplete > plugin, based on the work by ... > There is now a page with a download, link to the demo and documentation: > http://bassistance.de/jquery-plugins/jquery-plugin-autocomplete/ Great! Really nice work Jorn, you took what was there and made it better. I think I'm going to take my initial autocomplete page down, and refer to the improved work. It seems logical that we point jQuery users (new and current) to the best version. What about the links on the wiki plugin page? Replace both? -- Jörn Zaefferer http://bassistance.de
[jQuery] Re: Release: autocomplete 1.0 alpha
Dan G. Switzer, II schrieb: Geoffrey, Instead of hiding the box, perhaps there could be an option to display a message in the box that there are no matches to the users current input. In situations where the user must select from the list (the input will have to pass validation later) this could be helpful. You can add this functionality by hooking in to the result() method. It allows you to assign a function which is run when the user finalizes their value (by selecting a value or blur from the field.) Yeah, that is quite easy to implement. As long as you don't want to display that message inside the select box. -- Jörn Zaefferer http://bassistance.de
[jQuery] Re: Release: autocomplete 1.0 alpha
Jeff Fleitz schrieb: One thing that I think would be useful to add (I pinged Dan about this the other day), is an option to restrict the multiple option to distinct values, so that duplicate selections are prevented. That is an interesting point. I see three ways to handle this: - Let the user enter whatever he wants, using the autocomplete only as a helper. - Remove anything that was already entered from the proposed elements - Disallow/remove a selected value if it was already entered What would be the better solution? -- Jörn Zaefferer http://bassistance.de
[jQuery] Re: Release: autocomplete 1.0 alpha
amircx schrieb: found a problem: when im typing and select the matched value, and using form vaildiation plugin, if i set the MinLen in the validation plugin, its not accept the new value and change the state ie if i got field the min len required is 3 chars, and i typed "abrah" and selected it (it was in the array), its still marks me the field as "please fill min 3 chars in this field" This is a problem specific to integration of autocomplete with validation, and I haven't done any testing for that yet. Could you detail what type of validation you are using when the problem occurs? also, i wonder, is there a way to force user to type things only from the array? cause now if i got lets say, country textfield that user should input there his country, if he writes "germannyyy" its allows him. i need to force him to choose only things that inside the array. In that case you need a plain select, don't you? -- Jörn Zaefferer http://bassistance.de
[jQuery] Re: Release: autocomplete 1.0 alpha
On 4/18/07, Mika Tuupola <[EMAIL PROTECTED]> wrote: On Apr 18, 2007, at 2:35 PM, Fil wrote: >> http://bassistance.de/jquery-plugins/jquery-plugin-autocomplete/ > > Great work :) Dylan seems to be source of many great plugins ;) I'll take that as a compliment :-)
[jQuery] Re: Release: autocomplete 1.0 alpha
Geoffrey, >Instead of hiding the box, perhaps there could be an option to display a >message in the box that there are no matches to the users current input. In >situations where the user must select from the list (the input will have to >pass validation later) this could be helpful. You can add this functionality by hooking in to the result() method. It allows you to assign a function which is run when the user finalizes their value (by selecting a value or blur from the field.) -Dan
[jQuery] Re: Release: autocomplete 1.0 alpha
Instead of hiding the box, perhaps there could be an option to display a message in the box that there are no matches to the users current input. In situations where the user must select from the list (the input will have to pass validation later) this could be helpful. -Original Message- From: jquery-en@googlegroups.com [mailto:[EMAIL PROTECTED] On Behalf Of Chris W. Parker Sent: Tuesday, April 17, 2007 3:09 PM To: jquery-en@googlegroups.com Subject: [jQuery] Re: Release: autocomplete 1.0 alpha On Tuesday, April 17, 2007 2:04 PM Jörn Zaefferer <> said: > There is now a page with a download, link to the demo and > documentation: > http://bassistance.de/jquery-plugins/jquery-plugin-autocomplete/ > > The documentation lacks better examples, so until that is improved, > please try out the demo and take a look at it's page source. Sweet. Comment: When I type and am no longer matching anything in the available list the box should disappear. I think. Chris.
[jQuery] Re: Release: autocomplete 1.0 alpha
>found a problem: >when im typing and select the matched value, and using form vaildiation >plugin, if i set the MinLen in the validation plugin, its not accept the >new >value and change the state > >ie >if i got field the min len required is 3 chars, and i typed "abrah" and >selected it (it was in the array), its still marks me the field as "please >fill min 3 chars in this field" Are you sure you're not validating against a hidden form field? I can't see why the validation routine would not correctly read the value from an Autocomplete field--since it's just a text value in a field. >also, i wonder, is there a way to force user to type things only from the >array? cause now if i got lets say, country textfield that user should >input >there his country, if he writes "germannyyy" its allows him. i need to >force >him to choose only things that inside the array. You can use the result() method to update a hidden field w/the selected value. If the value isn't in the array, just leave the hidden field empty. Then you can validate against the hidden field to see if a "valid" entry was entered. -Dan
[jQuery] Re: Release: autocomplete 1.0 alpha
On Apr 18, 2007, at 2:35 PM, Fil wrote: http://bassistance.de/jquery-plugins/jquery-plugin-autocomplete/ Great work :) Dylan seems to be source of many great plugins ;) -- Mika Tuupola http://www.appelsiini.net/~tuupola/
[jQuery] Re: Release: autocomplete 1.0 alpha
Yoyo, >Is it possible to insert custom values in multiple input? > >If for example I try to write "Cracow" I got "Creola" If you want freeform text to be entered, then you can't try to map the text to another value (like a primary key.) So, you could use the multiple as a text only input field in online e-mail application to type in address to send a message to without a problem. -Dan
[jQuery] Re: Release: autocomplete 1.0 alpha
Is it possible to insert custom values in multiple input? If for example I try to write "Cracow" I got "Creola" /Yoyo
[jQuery] Re: Release: autocomplete 1.0 alpha
http://bassistance.de/jquery-plugins/jquery-plugin-autocomplete/ Great work :) You have a bug at
[jQuery] Re: Release: autocomplete 1.0 alpha
found a problem: when im typing and select the matched value, and using form vaildiation plugin, if i set the MinLen in the validation plugin, its not accept the new value and change the state ie if i got field the min len required is 3 chars, and i typed "abrah" and selected it (it was in the array), its still marks me the field as "please fill min 3 chars in this field" also, i wonder, is there a way to force user to type things only from the array? cause now if i got lets say, country textfield that user should input there his country, if he writes "germannyyy" its allows him. i need to force him to choose only things that inside the array. Dan G. Switzer, II wrote: > > > Jörn, > >>I'm glad to release the first version of the rewritten autocomplete >>plugin, based on the work by ... >>There is now a page with a download, link to the demo and documentation: >>http://bassistance.de/jquery-plugins/jquery-plugin-autocomplete/ > > Looking good! Glad to see you got the findValue() working for multiple > selects! Very nice! > > -Dan > > > -- View this message in context: http://www.nabble.com/Release%3A-autocomplete-1.0-alpha-tf3597557s15494.html#a10055112 Sent from the JQuery mailing list archive at Nabble.com.
[jQuery] Re: Release: autocomplete 1.0 alpha
On 4/18/07, Dylan Verheul <[EMAIL PROTECTED]> wrote: On 4/17/07, Jörn Zaefferer <[EMAIL PROTECTED]> wrote: > I'm glad to release the first version of the rewritten autocomplete > plugin, based on the work by ... > There is now a page with a download, link to the demo and documentation: > http://bassistance.de/jquery-plugins/jquery-plugin-autocomplete/ Great! Really nice work Jorn, you took what was there and made it better. I think I'm going to take my initial autocomplete page down, and refer to the improved work. It seems logical that we point jQuery users (new and current) to the best version.
[jQuery] Re: Release: autocomplete 1.0 alpha
On 4/17/07, Jörn Zaefferer <[EMAIL PROTECTED]> wrote: I'm glad to release the first version of the rewritten autocomplete plugin, based on the work by ... There is now a page with a download, link to the demo and documentation: http://bassistance.de/jquery-plugins/jquery-plugin-autocomplete/ Great!
[jQuery] Re: Release: autocomplete 1.0 alpha
Dude... This plugin freaking rocks. It's so far ahead of what it was before. Great job you guys! -Original Message- From: jquery-en@googlegroups.com [mailto:[EMAIL PROTECTED] On Behalf Of Chris W. Parker Sent: Tuesday, April 17, 2007 5:09 PM To: jquery-en@googlegroups.com Subject: [jQuery] Re: Release: autocomplete 1.0 alpha On Tuesday, April 17, 2007 2:04 PM Jörn Zaefferer <> said: > There is now a page with a download, link to the demo and > documentation: > http://bassistance.de/jquery-plugins/jquery-plugin-autocomplete/ > > The documentation lacks better examples, so until that is improved, > please try out the demo and take a look at it's page source. Sweet. Comment: When I type and am no longer matching anything in the available list the box should disappear. I think. Chris.
[jQuery] Re: Release: autocomplete 1.0 alpha
On Tuesday, April 17, 2007 3:25 PM Dan G. Switzer, II <> said: > Chris, > >> Comment: When I type and am no longer matching anything in the >> available list the box should disappear. I think. > > It's already known and listed in the "Known Issues" under "mustMatch > option is broken." ;) Then it's agreed. :)
[jQuery] Re: Release: autocomplete 1.0 alpha
Chris, >Comment: When I type and am no longer matching anything in the available >list the box should disappear. I think. It's already known and listed in the "Known Issues" under "mustMatch option is broken." ;) -Dan
[jQuery] Re: Release: autocomplete 1.0 alpha
On Tuesday, April 17, 2007 2:04 PM Jörn Zaefferer <> said: > There is now a page with a download, link to the demo and > documentation: > http://bassistance.de/jquery-plugins/jquery-plugin-autocomplete/ > > The documentation lacks better examples, so until that is improved, > please try out the demo and take a look at it's page source. Sweet. Comment: When I type and am no longer matching anything in the available list the box should disappear. I think. Chris.
[jQuery] Re: Release: autocomplete 1.0 alpha
Nice job! The multiple option is the bomb. One thing that I think would be useful to add (I pinged Dan about this the other day), is an option to restrict the multiple option to distinct values, so that duplicate selections are prevented. Jeff On Apr 17, 5:04 pm, Jörn Zaefferer <[EMAIL PROTECTED]> wrote: > Hi folks, > > I'm glad to release the first version of the rewritten autocomplete > plugin, based on the work by ... > There is now a page with a download, link to the demo and > documentation:http://bassistance.de/jquery-plugins/jquery-plugin-autocomplete/ > > The documentation lacks better examples, so until that is improved, > please try out the demo and take a look at it's page source. > > Have fun! > > -- > Jörn Zaefferer > > http://bassistance.de
[jQuery] Re: Release: autocomplete 1.0 alpha
Jörn, >I'm glad to release the first version of the rewritten autocomplete >plugin, based on the work by ... >There is now a page with a download, link to the demo and documentation: >http://bassistance.de/jquery-plugins/jquery-plugin-autocomplete/ Looking good! Glad to see you got the findValue() working for multiple selects! Very nice! -Dan
[jQuery] Re: Release: autocomplete 1.0 alpha
Jörn Zaefferer schrieb: Hi folks, I'm glad to release the first version of the rewritten autocomplete plugin, based on the work by ... Sorry, wanted to insert a few names there: Dylan Verheul, Dan G. Switzer and Anjesh Tuladhar -- Jörn Zaefferer http://bassistance.de
