Re: [drupal-devel] New weblinks module.
Bèr Kessels <[email protected]> Thu, 16 Oct 2003 22:22:22 +0200
| Newsgroups | gmane.comp.php.drupal.user,gmane.comp.php.drupal.devel |
|---|---|
| Message-ID | <[email protected]> |
Hi, This module seems to become a really nice module now! Throwing in some ideas here: I think all (web)links and URI's on the drupal site should use the weblinks table to store its weblinks. This will centralize the whole weblinks management. A lot of modules now store weblinks in different tables all over the installtion. IMO this is bad from usability point of view. I'm all for centralizing all URI management. I'm currently aware of the following modules using weblinks in some way: * profile.module * drupal.module * import.module * filestore.module * reviews.module There are probably more, but i'm not aware of them. I think we should try to store all weblinks in a central place. An API should be provided by weblinks.module to allow this in an easy way. I'm no good programmer, so i give some ideas here, maybe others will have better ideas. 1) An api to save all weblinks as a node. The body of the node can contain some human and machine readable text about the purpose of the node (eg 'this is a xml-feed. Please see http://blabla/import/12 for more info') 2) A cron nodegenerator to mirror all weblinks as nodes. EG a new feed will be provided as a node too) 3) Admin screens from where all weblinks can be edited. Eg the whole import admin screen will move into the weblinks section. As you might guess I think option 1) is the best. option 2) makes no sense from usability point of view. It will, however, not require current modules to be edited. Option 3 might look good, but will only work if ever the weblinks.module is included in the main distribution. -- [ Drupal user list | http://list.drupal.org/ ] [ http://lists.drupal.org/options/drupal-user/gcpdu-drupal-user%40gmane.org ]