Piers, I thank you kindly. In fact, I fall humbly to my knees and offer you my first-born goat. A rough draft of your idea can be seen here: http://snipurl.com/2azzy-meep
There was a concern regarding large chunks of (non-editable) text dropping to the next line, so I've temporarily gotten around it by putting each non-editable word into its own textfield. Is that overkill? Will there be problems with drawing hundreds of textfields onChange? Next hurdle: working out how to deal with reeeally long text entry. ie, when the input textfield width exceeds line space remaining. Creating a new, symbiotic input textfield for user input to flow into strikes me as a massive headache, especially when it comes evaluating the user data later. I spose we can but try. I'll keep posting improvements as (or if) they happen. Thanks again! On Tue, May 27, 2008 at 8:21 PM, Piers Cowburn <[EMAIL PROTECTED]> wrote: > Here's a solution (in English rather than code though): > > Create an array of your two different types of fields (editable and > non-editable). > > Create a render function (triggered once at the start, and then > subsequently by the Change event of any of the editable fields) which loops > through this array making labels / input fields for each one accordingly. > > Each time you create a new label, check to see if the width of it will > exceed the width of the page, and if so, split it into two fields, with the > second being on a new line. > > > I think that should work. > > Piers > > > > > On 27 May 2008, at 10:52, Paul Andrews wrote: > > ----- Original Message ----- From: <[EMAIL PROTECTED]> >> To: <[email protected]> >> Sent: Tuesday, May 27, 2008 5:29 AM >> Subject: [Flashcoders] Ideas for a "Fill in the gaps" activity >> >> >> Hello Flashcoders, >>> >>> I have a "Fill in the gaps" activity, done in HTML and Javascript (very >>> quickly). It can be seen here: http://snipurl.com/2askk-meep. >>> >>> I have to make something like this in Flash, and it's leaving me stumped. >>> It >>> seems like I'd need all the text (plus "growable gaps") to be within one >>> text field, to retain the flow of the words in the paragraph. However, >>> said >>> text field can't just be an input text field because that would make all >>> the >>> text editable. >>> >>> Any ideas very welcome. Even a very small idea > 0 idea, which is what I >>> have at the moment. Thanks! >>> >> >> I have done this for a commercial product using drag and drop. All the >> gaps were just drop zones, suitably sized to accept the (largest possible) >> draggable answer. The non editable text was just labels. The layout was >> fixed with text flow done by hand. It was a multiple choicedrag and drop >> thing though - in your case you can just substitute the drop zone for input >> fields. >> >> It is messy, so I'm looking forward to some clever solutions.. >> >> Paul >> _______________________________________________ >> Flashcoders mailing list >> [email protected] >> http://chattyfig.figleaf.com/mailman/listinfo/flashcoders >> > > [EMAIL PROTECTED] > 0207 631 3278 > > > > _______________________________________________ > Flashcoders mailing list > [email protected] > http://chattyfig.figleaf.com/mailman/listinfo/flashcoders > _______________________________________________ Flashcoders mailing list [email protected] http://chattyfig.figleaf.com/mailman/listinfo/flashcoders
