Port to 5.0?
rry - January 29, 2007 - 00:26
| Project: | Relationship |
| Version: | HEAD |
| Component: | Code |
| Category: | feature request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | active |
Jump to:
Description
Any chance of this being ported to version 5.0 anytime soon?
Thanks.

#1
I love this great module too!
I am learning and trying to organize my nodes into a topic map. Category module with freetagging is a good and simple solution but is lack of relationship among the categories.
#2
OK, I'm starting on this.
Looks pretty painless so far, But I'm doing a code review of everything to see how much I can strip out to an accessable lite core API vs my complicated layers of logic and RDF-ness.
While I'm on it, can anyone suggest where in the new admin layout the 'Relationships' section should go?
Under " Content management" alongside categories or in 'build' with the structural bits?
#3
I think it would defintely be Content Management.
#4
Any progress or updates on this?
It seems like there are a number of people here who would be happy to help with testing, etc.
#5
These modules look fantastic.. if you want any help testing/debugging a 5.1 version let me know.
#6
What will be approximat competion of this module, It's really good
#7
Any updates on the port? I'd love to use this module!
#8
I really apologise for my inability to commit to getting progress on this.
I've been doing real jobs and getting paid real money instead :-}
What happened was after my 4.6/4.7 proof-of concept work, migrating it to 5.0 (which is sorta done in HEAD) threw up which bits were over-complex and inefficient - after being worked over so many times even I couldn't be sure of the dependancies any more.
This stems from my misguided attempt to use the RDF logic/syntax to describe the internal rules themselves. It is theoretically possible, but also highly recursive. So I ended up with strange loops when bootstrapping - then messy work-arounds for them.
This (and other discussions over in the Relationship groups discussions) all told me that I needed a re-write to strip down to a minimal API so that other folk would be able to join in. That's just not happened in the last few months.
I'm torn between the need to start-from-scratch and the uncomfortable desire not to throw out the lessons I learnt and features I added in the first few iterations.
... and of course simple time/money constraints.
:(
#9
Subscribing...
I'm glad you're still trying to work on this when you can.
If you get a break from paid work and could do some paid work on this Agaric may be interested in sponsoring – no promise yet, we'd have to look into it more – but if you do have a break coming up contact Agaric. Thanks!