Richard MacLemale wrote: > What is a reasonable maximum number of fields you should put on a single > card in MetaCard? Could you, for example, have a stack with 50 cards, and > each card have 2,000 fields on it? What are some (if any) of the > disadvantages of putting 2,000 fields on a card? If there are problems with > this approach I can work around it, but I'm working on a project which would > really benefit from having 2000 fields, grouped together with scrollbars on > the group. Any input would be appreciated.
2000? It's hard to imagine a UI that needs that many editable text regions. What are you making? The downsides to high object counts are RAM and hit testing. And of course depending on what's in those fields it may take a while to redraw. Can't say I've ever put 2000 fields on a card, so I can't say for sure how gracefully MC would handle it. It seems easy enough to test with a repeat loop creating new fields in a test stack. Please let us know how that comes out. Offhand my first hunch would be to think of a solution which would allow a lower object count if possible.... -- Richard Gaskin Fourth World Media Corporation Custom Software and Web Development for All Major Platforms Developer of WebMerge 2.0: Publish any Database on Any Site ___________________________________________________________ [EMAIL PROTECTED] http://www.FourthWorld.com Tel: 323-225-3717 AIM: FourthWorldInc _______________________________________________ metacard mailing list [EMAIL PROTECTED] http://lists.runrev.com/mailman/listinfo/metacard
