In the example I discussed recently, about publishing poems online
using flex, I used images to hold the actual text of the poem. I
thought initially, not sure why, that I had to use that to ensure the
layout of the text. Obviously there are ways to use a '\n' to force a
newline.
However, let's say I kept the use of images to hold the poems. I used
Accordions that exist within a Panel component, where each Accordion
and Panel component held 5-6 poems or pages (some poems had to span
more than one page, or pane). Each of the Panels is a custom
component based on the Panel component (which holds an Accordion).
I also have an ApplicationControlBar at the top that selects between
different instancesAccordion instances. So, the ApplicationControlBar
has Poems 1 - 4 followed by Poems 5-8 and etc. like that, where each
selection, holds a different Panel that holds an Accordion. When you
are on a slower internet connection, this doesn't look too good. Each
time you click on a new pane of the Accordion you have to wait a bit
for the next pane to load, because the pane holds an image file.
I was thinking that if each custom component, each Panel, could embed
the images but load as an external component then there would be a
wait only when the different groups of poems load, in other words,
when you click on Poems 5-8 to go from reading Poems 1 - 4, the
application would load an external component, perhaps a swc, if I
understand things right. That reduces the time that the user has to
wait when going from poem 5 to 6 and 6 to 7, or page 2 of poem 6 from
page 1 of poem 6. Hopefully, I'm explaining this clearly.
How would I compile each custom component into a separate application,
or separate swc component? and then how do I include each of these
into the main application?
Thanks in advance for any help,
Please let me know if I'm unclear.
Bruce
--- In flexcoders@yahoogroups.com, "alinmircea_s" <alinmirce...@...>
wrote:
>
> Wow, first "If a different computer on the web could use a
> different font" you don t have to worry about that, font s are embeded
> into the app, not accessed on the user side.
>
>
> <mx:TextArea text="{'this'+ '\n' +'is'+ '\n' +'a'+ '\n' +'test'}"
> width="100%" height="100"/>
>
> "\n" = new line
>
> OR
>
> <mx:TextArea width="100%" height="100%" selectable="false"
> editable="false">
> <mx:htmlText>
> <
