Greetings Everyone -- I am implementing a satchmo store, and I could use some feedback regarding one of my requirements.
Essentially, I need to be able to handle diagrams. A perfect example would be something like this: http://www.mamotorworks.com/corvette-1-0-9532.html As you can see, a diagram is simply an image of a 'whole' that has been 'blown-apart' and its constituent parts labeled. The labeled parts on the diagram correspond to the labeled parts (by 'key') available for sale down below. When you think about it, a diagram is essentially a grouping mechanism, and therefore very similar to a category. However, it is different from a category in a couple ways. First there is the 'call-out' or 'key' attribute. This attribute needs to exist on the relationship between the diagram and product (and not on the diagram or product itself, that is) because one product may exist in many diagrams. Secondly, I may want to display a diagram quite differently than a category. There are likely to be other subtle differences as yet unidentified by me. This train of thought brings me to the conclusion that, while I might be able to accommodate diagrams using satchmo categories, it could get ugly and burdensome rather quickly. So, I am considering introducing diagrams into my satchmo application as a first-class concept (i.e. creating a Diagram model, giving it a URL mapping at "/diagram/<diagram-slug>", etc.). Does anyone have any feedback for me? Is this a good idea? Does this make sense? Am I missing a better/easier way? Has this feature ever been requested/needed before? Thanks in advance! --Stuart
-- You received this message because you are subscribed to the Google Groups "Satchmo users" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/satchmo-users?hl=en.
