hpoe

Forum Replies Created

Viewing 2 replies - 16 through 17 (of 17 total)
  • Author
    Replies
  • in reply to: dynamic colModel #86761
    hpoe
    Participant

    Alan thanks, this would be a solution. I used another way to do it, because it would be too much to handle in a script.

    We have about 20000 different item configurations, each with up to 30 attributes and up to 1500 configs per item configurations and 3 languages.

    Example: http://ruegg.mediando.ch/images/bookmarks/mediando_web003.png

    one page is set up for one item, each row in the grid is a specific item with specific attributes plus price, which make up the row.

    Fix in the grid is only the item no on the left and the price on the right.

    My solution for this solution was to create a stored proc which created the select for the grid from basically 3 tables (items, item_attr and prices), the colModel and the colNames and the result of this procedure is stored in a table.

    At runtime I add the colmodel and colnames from this table to the javascript and I let again a stored proc execute the generated select in a coldfusion component.

    This performs quite wll, I just have a few formatting problems. e.g. the right most price column is cut off, but that's another story.

    in reply to: dynamic colModel #86501
    hpoe
    Participant

    OK, i try to ask differently.

    I have create a grid for products which have very different configurations eg size, power, weight. 1 product on one html page, one coModel per product. colNames depending on selected language. In the grid the different dimensions / configurations / prices have to be shown. Moreover filtering with selection lists to all columns is a must, an of course paging.

    I am not sure but I think my only option is to generate the javascript configuration the first time a product is called and save it language dependent in the database for later usage.

    Generating an xml configuration would be easier, but I don't know how to include the option lists and the configuration for the search toolbar. The existing example is very basic and the json_test.txt and xml_test.xml files are not in the distribution package 3.4.3

Viewing 2 replies - 16 through 17 (of 17 total)

Stay connected with us in your favorite flavor!