This module is very similar to http://drupal.org/project/cck_autocomplete - could you please clarify your vision about further development: do you plan to go in a specific direction or can users expect merging with the other project? Very important for anyone choosing to rely on this module!

(A corresponding question has also been asked at the other project's support queue.)

Comments

markus_petrux’s picture

Status: Active » Fixed

I would like to mention I know there's another module, you haven't mentioned, which is the first one who implemented this feature, as far as I know:

http://drupal.org/project/textfield_autocomplete

But that module is for D5, and it's kind of just a first commit and forget module. No more commits, no support given by the author.

So when I was interested in this feature for the project I'm working on, which is D6 based. After researching a little, I found that project and I announced in the CCK issue I was going to contact the author of the textfield_autocomplete:

http://drupal.org/node/126595#comment-1185108
http://drupal.org/node/281885#comment-1185125

I even suggested it could be part of CCK itself. Curiously CCK already has an "option widgets" add-on, but it doesn't have "autocomplete widgets". :) ...but CCK maintainers seem to be too busy, specially with Fields in D7, so that idea was kind of lost...

This was January, 6, where I already had it almost working on my dev environment.

After trying to contact the author of textfield_autocomplete module without success (initially, because they contacted me after some time, but never knew about them when I replied), well you can see I also requested transfership of that module here:

http://drupal.org/node/367578

I was just able to wait for some time, not forever, so after unsuccessful attempts to not add clutter to the Drupal repositories, join efforts with others, etc., I decided to go ahead and create my own project.

I already started moving when I knew about the cck_autocomplete module (created in January, 25). Even when I already had code, and determination to find a working solution for our project, I looked at that project, but I found it was not following coding standards, etc. So I opted to continue on my own road.

Autocomplete Widgets module overlaps the features of other similar modules. In regards to quality, performance, et al... all I can say is we will be using it on a high traffic site (meristation.com is being ported to D6, which is ~2M pageviews a day) and I have plans to keep it as up to date and optimal as possible, and it will probably be ported to D7, or an upgrade path provided for Fields in D7, when the time comes.

Please, compare all modules that offer this functionally for yourself and choose the one that better fits your needs. Thanks :)

archard’s picture

Autocomplete Widgets and CCK Autocomplete seem to do the same thing, but Autocomplete Widgets looks a bit more ambitious. However, I wouldn't mind 'merging' modules at this point because I don't have much time these days to properly maintain CCK Autocomplete.

So, I would recommend going with Autocomplete Widgets. I will recommend to CCK Autocomplete users that they make the switch. Feel free to borrow any code you want from CCK Autocomplete, markus.

@markus - I'm curious why you think CCK Autocomplete doesn't follow coding standards. Can you elaborate?

markus_petrux’s picture

Oh, yes. It's basically the use if tab characters, indentation issues and whitespaces on empty lines all over the .module script. I didn't look much after that.

BTW, thanks for chiming in. I think this feature ought to be part of CCK itself, and I suggested that, but CCK maintainers are too busy, so... we have to live with these modules in D6, I'm afraid.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.

turadg’s picture

@archard, can you update the CCK Autocomplete project page to reflect your advice to users to use Autocomplete Widgets instead?

markus_petrux’s picture

@turadg: I think it would be better to request this in the issue that's still open in the CCK Autocomplete queue.

http://drupal.org/node/451068

It often happens that issues in status "closed" are missed from the eyes of most people.

archard’s picture

turadg: I've posted the message on CCK Autocomplete's project page.

Marko B’s picture

This module is very useful also in drupal 7, hope it will have drupal 8 version. Happy it never merged :)

OFF’s picture

Issue summary: View changes

D8 version desirable