Hello all!
I've continually run into this problem where ideally I'd like to add several hundreds of RichTextFields to vfm. But the instantiation times are prohibitive (is this app broken or are we still waiting?!?!).
Unfortunately, due to the nature of the application, it will be ideal to have the user think they have access to all of these fields in one vfm (this is an iPhone port). So my next thought was to device a lighter weight vfm that essentially swaps in and out instances of fields based on the direction the user is scrolling.
From my experience, this strategy becomes overly problematic when developing for touch screens. Admittedly, it's been a few months since I've looked at this problem. But I do recall a very vivid depiction of hell. So I'd much rather front load the question.
So, if my memory serves correctly, the wall I ran into was gathering the information that serves as the basis to programmatically understand which fields to swap in/out; at what rate; and identifying the callback that would continually provide feedback of the current state of the scrolling mechanism (for the touch screen).
I know I didn't give a much to work from. But I will appreciate any thoughts or experience.
Lub,
taco sauce
