Is there a maximum number of TVs that can be used on a template?

I designed a site, and more specifically a menu for a restaurant using a combination of Foundation 3 & Modx. I developed the menu using tables which has worked out very well indeed. My menu tables are merely items and pricing—very simple—and are set up in a chunk. So far so good. I want my client to be able to modify pricing on his own, and was hoping he would not have to hunt and peck amongst the table code in my chunk. Tedious as it might be I thought I would just migrate the menu page to it's own template and then set up a TV for each item's price and label it with an obvious name so the client could easily go in a find for example "Large Combo Pizza Price" and update the price.

At this point, there are 56 price items between all of the small medium large, single topping, combo, etc. etc.

I just didn't want to undertake the task of setting up the TVs if in the end it would result in some kind of problem.

The foundation 3 table structure is really working great, and with the addition of their responsive table js & css, longer tables pin the 1st column and allow the user to scroll the remaining table items on iphone, ipad and android. Some of the styling and the ugly default blue scoller that appears on mac at least, I could do without, but at some point there needs to be function over form.

Just in case anyone is interested, link to the responsive info for foundation 3 tables is: http://zurb.com/playground/responsive-tables

As far as I know, there is no limit. You might find MIGx to be useful here; you can have an entire grid of nested form fields. Very useful for variable numbers of items in any kind of structured output, such as tables or lists.

Thanks Susan: I am familiar with the MIGx and that's about the extent of it. At this juncture, I'm under a tight timeline, and need to go with what I know. I'll give the TV method a try and see how it goes. I am curious about the MIGx though and plan to learn more.

Your MIGx TV would be for "Items", then an editable list of Items, each of which would have fields for "description", "price", "image", etc. No need for a separate TV for each item.

This way your client can add his own Items; as it is, every time he adds or removes an item from his menu he'd have to add or remove a TV.

+1 for MIGX for this task. Without it, as Susan noted there'd need to be a TV for each item, and a new call in the template for each as well.

You wouldn't even necessarily need the table for the menu items either. You'd make one chunk with the html for the menu items display, and MIGX will use it for each item automatically. Essentially, your table becomes the MIGX grid TV (from a usability standpoint).

This would be a perfect application to figure out how to show and hide items from MIGX (which I want for one client's site, but haven't yet figured entirely). Specials, and temporarily unavailable menu items could be turned on and off at will.

Thanks for the wealth of feedback. The menu I'm working with is pretty static. If the owner does have a new item, I would add that content. But in the meantime, the menu items really don't change. Only the prices from time to time to absorb the rising cost of ingredients. The table structure in this scenario works perfect, and everything fell right into place. I have been curious about MIGx but just have not had the time to learn more about it.

Wow! Just spent a bit time last night playing with MIGx using a tutorial by Mark Hamstra. This MIGx is very cool!

Right? It does make quick work of anything that you might want to use multiple times. The @FIELD:tpl property is also quite powerful. Make a few tpl chunks, a selectable TV for each, and stick it in MIGX. Now you can tpl each item separately. Nice.

Have fun!