--- Jonathon -- Improov <[EMAIL PROTECTED]> wrote:
Chris,
Is this how OFBiz is currently doing things? I can
see your point.
This is NOT how OFBiz currently does things. And
without a community effort to modularize the
components, (IMO) will likely never be the way OFBiz
does things. The product component and the
manufacturing components feature sets are simply,
individually too rich. You can't introduce this
concept into the product component without breaking
the manufacturing component (or at least severely
convoluting the conceptualizations as I understand
it). The value of the manufacturing component is just
too high compared to this benefit for this to be
feasible. If you were able to offer an alternative
product component, then a manufacturing component for
that new product component could be created without
the disruption to the current components.
But currently, I have a limiting/crippling "time to
market" constraint. When building for flexibility, there can be no
end to the quest.
Exactly. I can propose "what ifs" and "ponder this"
all day long as I have the luxury of never having to
satisfy your boss/client's actual need to sell
something :-) . This is the benefit and bane of open
source software. The lure to create a better
mousetrap when the only mice you have, you keep as
pets.
Whatever you said of Product IDs, the same may be said of
ProductFeature IDs or any other IDs in
OFBiz.
It's been a while since I've played with
ProductFeature IDs, so I may be off a bit on the
concept, but I don't think the same is true because
those IDs remain internal to your organization, don't
they?
Usually, I'm forced to deliver the application first, see how things
run with
prototype, then figure out where to go next after getting a better
view. I usually can't decide
whether to construct a skyscraper on small plateau or sprawling
shopping mall on large plateau when I
haven't even climbed up the plateau to see what size it really is.
Hindsight is cheaper to buy than
foresight.
Still, back to your discussion with Product IDs. Can
I use fields like "Internal Name" and "Description" for my
storefront? I know the
storefront currently displays Product ID. This is a real problem. I'd
like a bit, even if just a tiny
amount, of discussion or ideas thrown in at this moment for this topic.
This is largely simply what you're choosing to show
the user of the site through the UI (except where
there are textbox inputs) your link information can
have the Product.productId to send to your services
but have the words that show up on the screen be
Product.internalName.
(To Boss: Any chance you'll be changing your Product
IDs like Chris said?)
Jonathon
Regards,
Chris
