Split project into API an UI modules
| Project: | Drupal Contact List Importer |
| Version: | 6.x-1.x-dev |
| Component: | Code |
| Category: | feature request |
| Priority: | normal |
| Assigned: | hadsie |
| Status: | closed |
Jump to:
I built a module for a project that requires an array of contacts from a contact list. Thanks for building this module. It really helped me :)
I do have a feature request though. Would it be possible to split this project into 2 different modules?
1) an API for grabbing contacts
2) a user interface
In my module, I only make a call to dcl_importer_get_contacts to gather the contacts. The UI and menu items from DCL are not needed for the website I'm working on.
Advantages to you? I'm willing to help work on the DCL API by submitting patches wherever possible. Otherwise, if this won't work for you, I'd have to rip out what I need from DCL and have to maintain it on my own. It's definitely not an optimal solution for either of us (or others that may want to do what I'm doing).
Let me know your thoughts.
#1
That would be great actually :-), my problem is that i don't really have much time to enhance the module, there is a lot in the TODO list regarding dcl_importer but as i said i can barely find sometime for my self to do things that i really love to do like Drupal!
if you started this then that would definitely encourage me and give me a push since that would be a team work rather than a solo player :), ohh, and of course its an open invitation so every body can join the party :-), so, again my answer is yes :-) but you have to show me something so i can start working on that with you and with the others if any :-)
#2
That is great news!
*update*: removed my patch for a newer better one coming soon.
#3
I'll be tightening up this patch. A bit more work has to go into it.
#4
I'm interested in co-maintaining this module. Because I think it should get a stable release ....
#5
The company I work for decided to go with another solution. Unfortunately I won't be able to do the split for this module. Hopefully R.Muilwijk and others can and will continue the work on this issue.
#6
@R.Muilwijk, your help is so much appreciated and yes, i believe it should get into a stable release but lets give it a lil while to make sure that everything is working fine, i am planning to add more sources to the list of providers that this module is supporting, let me add them and wait for a while so we can release a stable package.
Regards, soosa
#7
#8
Hi! I'm proposing a GSoC project to integrate contact APIs to Drupal so we could support functionalities such as previous friend finding. My goals are to develop a common base for different external APIs (Google Data, Windows Live, etc) and provide an exposed API to be used by other modules.
Maybe I could do this work as an DCL Importer extension (in fact this issue is one of the things I'd had to solve). Do you think it's a good idea? Using APIs as the external contact source would require major changes on this module?
Please take a look on my preliminary proposal at http://groups.drupal.org/node/10161. I didn't know DCL before, so my proposal doesn't mention it, but I plan to review it if your answers are positive.
#9
I already supplied some patches and some tips for fixing stuff.. why don't you just apply them or atleast review them when you appreciate my help?
#10
IS this module maintained or not? What are the plans of maintainer?
#11
The D5 module is no longer maintained. I won't be splitting the module into two modules for API + UI just yet as there's very few API calls that would be useful. I will be designing it in such a way that it will be easy to use it as just an API, however.
#12
Upon further thought I think it does make sense to split this into an API and a UI modules. Re-opening
#13
The module has now been broken down into it's core dcl_importer functions and had the invite code stripped out into another module. On it's on, the dcl_importer provides little more than an api and a form + hooks that can be used by other connector modules. Marking this as fixed, though more api work is still needed so that it can handle multiple retrieval libraries.
#14
Automatically closed -- issue fixed for 2 weeks with no activity.