Static Content Resize

[Colin]

Does the HTMLWrapper (or miniHTMLWrapper) re-flow/re-layout content if
container is resized? The demo includes hard-coded width and height in
the divs which is may not work for the use-case I'm investigating, and
removing the hard-coded width and height from the demo breaks layout.

Also, is the supported HTML set documented anywhere?


Thanks,
Colin

[Tyler Larson]

Both of them can do this the example for MiniHTML is setup to do this

https://github.com/talltyler/MiniHTML/blob/master/src/Main.as

I don't have an example of the newest version of HTMLWrapper but it should all be based on values that have percentages instead of pixel based values. Let me know if you can't get it working and need help. 

The best list of implemented tags to go from is what is provided in the code

For HTMLWrapper https://github.com/talltyler/HTMLWrapper/blob/master/TagsBase.as

Source for video and audio tags is written for HTMLWrapper but commented out, just uncomment them to enable these tags.

For MiniHTML only the Div tag and text (CDATA) elements are supported but code is written for images and title tags in the source but commented out. 

-Tyler

--
You received this message because you are subscribed to the Google Groups "htmlwrapper" group.
To post to this group, send email to htmlw...@googlegroups.com.
To unsubscribe from this group, send email to htmlwrapper...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/htmlwrapper?hl=en.

[Colin]

Thanks for the clarification on the capabilities. I think I'll first
try the full HTMLWrapper code. I would like to support as many HTML 4
tags as I can out of the box.

Here's the context:

I have a Flex (Flash Builder 4) project that is currently rendering
(poorly) some HTML in an extended mx:Text component using the HTMLText
attribute. I've been looking to replace this with something more
robust at parsing/rendering HTML and have tried out DENG
(abandonware), Groe.org's AS3 HTML Parser, and I'm looking into your
solution as well. Groe.org's solution looks okay, but doesn't easily
resize the content, so I'm glad it sounds like your code will handle
that.

Currently I'm slightly confused by your Flex example in as much as you
have the controller->navigator->window hierarchy which seems overly
robust if I'm not using the ASTRID framework, too. My current project
has multiple alternating boxes of mx:Text for the HTML content and
"form fields" which take text and image input. So I'm not sure that I
want multiple window components all over canvas. It's not clear from
the document.as file, but can I just use that as a "top-level" object
for rendering the HTML and embed multiple documents in a container?
I'm going to continue playing with the code, but would appreciate your
feedback.

Thanks,
Colin

[Tyler Larson]

Thanks for looking into it.
I would suggest trying to learn the whole ASTRID framework even if you are trying to do something simple.
The framework does lots of things for you if you keep it's structure.
You can try to get around using it but it will just be harder, the flex example was trying to get around parts of it which is why you see the code that is drilling into controller > navigator > window. If you use the whole framework you will have a render method that you can pass your renderer and data to.

Whatever you end up doing let me know if you get stuck on anything.

-Tyler