Okay, there’s a specific problem set i’m trying to solve (i have a really awful workaround at the moment), but it seems like an extension for this is (a) probably more generally useful, and (b) likely to be an easy or at least not terribly difficult extension to work you’ve already done.

The issue is this: i work on a couple of sites for real estate builders. A builder has x available houseplans. They have plats in some subdivisions Each subdivision can have some subset y of houseplans built in it—but the PRICE of any given plan is set PER SUBDIVISION; it’s not intrinsic to the house.

So, for example, we have three subdivisions: Hifalutin Estates, Snob Manor, and The Estates of Overconsumption.
We also have three houseplans available: the Moose, the Elephant, and the Whale.

Snob Manor can have the Moose built at a cost of $240,000 or the Whale at $250,000.
Hifalutin can have the Moose from $210,000 or the Elephant from $220,000.
Overconsumption: Moose, $215,000; Elephant, $222,000; Whale, $245,000.

So what i need, and what i suspect other people might need and want also, is something VERY like your multi-text plugin, but with a relationship available as one of the columns.

For me, each row would look like:
=========================
(dropdown—houseplans)  |  PRICE
=========================
(dropdown—houseplans)  |  PRICE
=========================

It seems to me that there are LOTS of other circumstances where you might want to associate an arbitrary number of RELATIONSHIP rows each with one or more free-text-entry fields.

So, a suggestion, if it’s not too hard to implement!

—Adrienne

Your asking for something similar to Ektron’s ability to create “field groups.”  What those are is a grouping of fields that are allowed to repeat as many times as needed.  So you could create a grouping of a relationship field and a text field, then in the publish section of Ektron it would allow you to duplicate that group and have as many rel+text pairs as you need.

I think a “grouping” approach would be the best way to go with EE also.  However, with the current extension hooks it may be a little difficult.  I’ll have to look into how the publish tab is built and see if there is some way to visually and programatically separate fields.

(BUMP)

Mark, any more ideas/progress on this? (I’m hoping!)

—Adrienne

alienne - 20 November 2006 10:16 AM

(BUMP)

Mark, any more ideas/progress on this? (I’m hoping!)

—Adrienne

x2

Happy New Years all!!!