Postponed
Project:
Link to content
Version:
6.x-2.x-dev
Component:
User interface
Priority:
Normal
Category:
Task
Assigned:
Reporter:
Created:
9 Mar 2008 at 17:50 UTC
Updated:
15 Sep 2008 at 20:21 UTC
I find the approach of the easylink module (http://drupal.org/project/easylinks) quite clever. It allows the admin to specify a view that produces the list of nodes to display. Because views allow exposed filters, this does essentially the same as your module. However your module is more actively developed and also has a nicer javascript window. Perhaps the approach of easylinks could be adopted for your module?
Comments
Comment #1
gustav commentedSorry, the link in my post was incorrect. The correct link is http://drupal.org/project/easylink
Comment #2
stborchertHi,
I already thought of that but stopped further development on this because I couldn't find a solution to display a filtered list of nodes *and* terms with views.
Maybe I'll find a quick solution and am able to include this.
thanks,
Stefan
Comment #3
gustav commentedWhat do you mean by "a filtered list of nodes and terms?". For linking to nodes you only need a list of nodes filtered by terms and that is the kind of thing views is good for.
Personally however I am would want to filter by different things than terms. For example I would like to list the nodes a user has recently visited or the nodes the user has recently contributed to. Views gives a lot of possibilities there.
Comment #4
stborchertNot really. If you select page, story and term on linktonode's settings page you will receive a list with nodes (stories, pages) and terms filtered by the selected term.
True. But this would also break the term selection fields.
There are many possibilities views would open, but on the other hand there a some major features views would break.
I have to do some testing before I can say "ok, lets do it", so don't bother.
greetings,
Stefan
Comment #5
stborchertWell, I've thought about it and played around with some code.
Result: views will be used from now on (5.x-2.x) to list the nodes. However, I have to make some major changes to the module: terms and nodes want be displayed together in one list anymore (because I didn't found any way to do this), so there will be an extra "plugin" for displaying terms.
The major problem still is to output the views results as json (but fortunately bdragon has made views_json so this shouldn't be this big).
Comment #6
stborchertSmall status update.
The plugins (linktocontent_node, linktocontent_menu, etc.) will be removed because they will be unnecessary.
Instead of these old "fixed" plugins, the user (admin or someone else with specific access rights) will be able to create a new "plugin". This "plugin" consists of two views: the first one to create the browsing selection (e.g. list of terms or menu structure or organic groups, ...) and the second one will create the listing (nodes, terms, menu items, users, ...).
To achieve this linktocontent will define some views (escpecially for the browsing part).
Don't know now when a first dev-version will be online, but I'm coding as fast as possible ;-)
Comment #7
sunThis will depend on #252938: Port LinktoContent to 6.x