David Bovill wrote/ schreef:
> Sjoerd wrote:
>> Stil waiting for this option, again: Who wants to work together to make a
>> nice script/ external for this?
> Possibly. Thinking of it mores as linked fields, with text flowing from one
> to another (as in Quark Express). Did this in HyperCard ages ago, and it
> would be *much* easier in Metacard.
> 
> I haven't played with the formattedHeight/width etc properties yet, so I am
> sure there is someone on the list who knows how to do this much better than
> me...
> 
> I think a starting place would be to create a function which can take a
> field of any dimensions, a nice big chunk of text, and figure out where to
> cut the text so as the maximum number of words fits into the field. Even
> better would be to have the keeplinestogether, or similar options, but for
> now...

I don't quite understand your script below, but I think I have the same idea
as you in mind. I would think of a script and a layout like this:

Layout:
------------------------¬
|  Field "t1"           |
|                       |
------------------------¬
|  Image 1  | Field "t2"|
|           |           |
|           |-----------¬
|           |  Image 2  |
------------------------¬
|Field "t3"| Img. |Fld. |
|          | 3    |"t4" |
-------------------------
  -- And there is also an invisible field "MeanText" with the whole text
  -- in it.

We would need the following handlers:
- createFields -- creates the fields in the right order and maybe according
                  to the props of images and players. Ran every time the
                  place and/or the size and/or the existence of images and/
                  or players changes.
- distributeText -- distributes the MeanText over all (already existing)
                    fields. Ran every time the text changes.
  + getTextBack  -- gets the fields back (into MeanText)
  + refillFields -- puts the whole MeanText into field "t1", and cuts the
                    not-fitting text, and puts that into field "t2", and so
                    on.

I think that the createFields handler is the most difficult one to make.
Also a demo-stack has to be made. Volunteers for any of these?
> function wordNumOfOverflow fldObject, someText
> ...
> return wordNum
> end wordNumOfOverflow
> 
> Also not sure about the implications/possibility of using styled/htmlText...
> anyway I think this is the key function?

Hoping for any volunteers,
Sjoerd


Archives: http://www.mail-archive.com/[email protected]/
Info: http://www.xworlds.com/metacard/mailinglist.htm
Please send bug reports to <[EMAIL PROTECTED]>, not this list.

Reply via email to