[quoted text, click to view] > Well, I must say I use prebuilt movieclips - like templates - and a xml file
that
> contains a seperate childNode that holds the path to the image.
That works really well, but the only problem is this project is basically a
HTML editor for users in an image-centric blog like system, with compose and
preview mode. So users might do anything with any combination of images and
HTML markup, there's not a predefined template.
That being said, I am seriously considering using a custom parser which checks
to see if an image is wide or wider than the textfield width, and if so then
dynamically end the current textfield, insert a movieclip with the image loaded
in it, then start a new textfield below it. But that would introduce all sorts
of things I don't want to deal with...
Concerning hspace, I'll probably toy with it some more because I don't fully
understand how it behaves, but the problems I encountered with it were:
1) It requires users to specify hspace, or additional AS to auto detect image
size after it loads and insert hspace tags
2) hspace is specific to Flash, and end deployment of the HTML would be in a
real HTML page, this means I'd need/want to strip it out before publishing, and
somehow add it back in when editing existing
3) It appeared to add space *above* the image, which I don't want
4) It didn't seem to help the problem/bug with text wrapping, as described in
my previous post.