Table would look something like this.
NavNodeID1 NewsObjecteId43 NavNodeID2 NewsObjecteId56 NavNodeID3 NewsObjecteId32 NavNodeID4 NewsObjecteId18 NavNodeID5 NewsObjecteId21
In other words I know that you can assign a navNode to point to a specific page somewhere else in the tree, but if I wanted to make this process dynamic but in reverse. Instead of creating a node and assigning it to point to an existing page, they would be creating the page as a news type and assign it to an existing navnode.
You may be trying to make it more difficult than it has to be.
There are a few ways to do this. I am assuming that the Nav nodes already exist and you just want new dmNews objects to point to them.
If this is the case you can use the built-in feature called "Categories". This will also allow you to relate the news item to multiple nav nodes if you wish.
Otherwise you could extend the dmNews object. Add a PLP step that allows you to do whatever you want. Like maybe create a field (say "relatedNavID") and allow the user to choose from a populated list of existing nav nodes. There are probably a hundred other ways you can get Farcry to do what you intend by extending the dmNews object.
If neither of these seem to be your solution perhaps you could give an excplicit example of what you're trying to do. (i.e. I am assuming you want the person to create a dmNews object and assign / relate it to a single (or multiple) dmNavigation object. I would consider using the already built-in "Categories" feature.) However, I'm still not sure "exactly" what you're trying to do. The good thing is that most custom things (beyond what exists in dmNews) should be able to be accomplished by extending the dmNews object.
-Jeff C.
--- You are currently subscribed to farcry-dev as: [email protected] To unsubscribe send a blank email to [EMAIL PROTECTED] Aussie Macromedia Developers: http://lists.daemon.com.au/
