Posted by ray007 on June 16, 2007 at 7:45am
8 followers
Jump to:
| Project: | Drupal.org webmasters |
| Component: | Project ownership |
| Category: | support request |
| Priority: | normal |
| Assigned: | kiamlaluno |
| Status: | closed (fixed) |
Issue Summary
seems the last commits happened about 8 month ago ... is this project still active?
Comments
#1
Not actively active, no.
I have real-world work on, so it's all on the back-burner.
It can be retired, or opened up to anyone who wants to CVS, or indeed replace it with another approach.
I still have plenty of ideas for it, but no pressing need for my own dev on it.
#2
Hi, One year further..times flies..is there a drupal 5 version of this module?
If not, what is the best alternative approch?
Thanks for your reply in advance!
greetings,
Martijn
#3
Poke.
@dman: Are you thinking that this project is still worthwhile, overall, or do you think there are better ways of doing it? If the former, are you still interested in doing it, and just strapped for time, or are you no longer interested? Either way, could you post the latest versions so that others can take it up?
cheers
ned
#4
Most of what I did has been overtaken by the emerging RDF projects.
At the time this project was first released, there was no CCK, no nodereference, and no RDF.
I saw an RDF triplestore as a way of building the node-to-node references we needed. I built an RDF triplestore and predicates and UI for it, but got tied up in some of the scaling issues.
Nowadays, you are best to use CCK+nodereference, although even that isn't what I saw as the full solution, it is at least a workable one.
the RDF projects still haven't broken through their barrier of critical mass, or even turned out to be anything more than prrof-of-concept (that I've seen so far) so although I'll keep lookig towards that direction, a full answer is not in there yet.
#5
dman: so basically this project is more or less dead, unless it turns out that CCK can't handle it?
What do you think of something like this: #704712: Abitrary reference names for node reference? If we could get that to automatically map the arbitrary label to a semantic property, I think it would more or less cover this project (at least for nodereferences - not for external links)
#6
Seeing as I ceased work on it about three years ago, yeah it's dead.
I've not thought about doing it with nodereferences exactly, but I was thinking that way when I needed to to attribute-value pairs.
See http://drupal.org/project/attribute for a current incarnation to start from I guess.
I think there is also some widget that groups cck fields, so you can define a widget that contains a select box for relationship 'type' and a nodereference field on the same row. Can't recall what it's called or how stable it got.
I'm still holding out for a proper RDF version ... but I guess that won't work in with Views as well as nodereference currently does.
#7
See http://drupal.org/project/awesomerelationship
That module already works, although it's only very basic pre-alpha at the moment. Perhaps this module should be deprecated in favour of Awesome Relationships?
#8
Reference dman's comments above. dman is module owner.
This module has been effectively superseded by Awesome Relationships and References projects.
#9
Aren's comment is at odds with the fact Awesome Relationships is marked as Abandoned and has no releases.
#10
Sorry, Awesome Relationships got moved to Relation (http://drupal.org/project/relation), and that may someday supersede References.
References appears to just be a way to get D6 CCK's nodereference and userreference types into D7.
#11
I have marked the module as abandoned.
#12
Automatically closed -- issue fixed for 2 weeks with no activity.