Hi
First of all thanks to the developers for this great framework.
I've been playing with it for about a month for use in a shopping mall
project, primarily modifying the admin functions while I wait for the
designers to finish the display templates.
The current implementation of attributes and variations seems to lend itself
more to programming flags than actual item attributes. For example this is a
great mechanism for implementing flags for items on special, high profile
items to display on department pages etc. The scope is global rather than at
the individual item level.
In order to implement variations such as color or size , which are item
specific and selected at the sku level, I added tables for options (you
hogged all the good terms). They are created and managed at the item level(I
did provide for global templates), included or excluded for display at the
sku level.
I choose to implement options as suffixes to the base sku (sm, med,lg..etc.)
rather than have each color/size combination generate a unique sku. This
will cause problems for inventory tracking and a few other areas. The proper
way would be using Javascript arrays to generate co-dependant select boxes
and the final sku based on the user's selections, much the way Leon's store
selector at Restoration Hardware works.
I am reluctant to use Javascript for something as critical as product
selection and would appreciate any comments from those with more practical
experiance.
Earl Wyllie
[EMAIL PROTECTED]
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Site: http://www.working-dogs.com/freetrade/
Problems?: [EMAIL PROTECTED]
