I’m getting ready to redesign a client’s website and they have asked about letting the viewers resize text. So I set up a rough test page in FW 6 with 3 buttons to change text size (I got the idea from posts on this forum, thank you and that seems to work. Unfortunately, it also makes a mess of the page layout.
So I thought maybe I could improve things by adding Read More… actions to hide the text mess. I added one to the left column and it worked. Then I added another to the column next to the right. But for some reason, instead of appearing a few lines from the top of the text block (where I inserted it), it appears at the end of the text bock.
I’ve done some more experimenting with Read More… action. It seems to need both a carriage return and a line feed following the insertion point in the text in order to work correctly.
Otherwise, the action will be invoked at the next CR+LF. If there is none, the action is not invoked until the end of the text block.
In my test page, I had a list of items (each on a single line ending with a shift CR). The lack of a line feed caused the action to be invoked at the end of text block.
This is not a problem, but it is worth being aware of when using this action with lists.
There seems to be a problem when my test page (containing the Read More action) is viewed on phone.
Normally when the Read More button is clicked, a white pop-up window appears surrounded by semi transparent black area. It works this way on phone only if phone is held in vertical position.
If the phone is held in horizontal position, the white pop-up window seems to cut off at the bottom and merge with the page below (instead of being surrounded by dark area). This would visually confuse a user.
I tried it on an android phone (and a tablet) and it didn’t work right when held in vertical position. The pop-up window merges with the background and does not scroll.
Would you mind trying it on your phone and telling me if it works for you :-? The URL is listed in my first post above.
I will also try your suggestion to us an accordion to reveal more text.
Reading some of the old posts, it sounds like there are real problems with suiteFX and mootools. So should I use ScriptyAccordion? Are there issue I need to know about?
suiteFX and mootools. So should I use ScriptyAccordion?
These use different Core javascript libraries to those used ‘natively’ in FW (which uses Script/Protaculous predominantly)
Also there has been no development of suiteFX and mootools within FW since Weaver departed these shores many years back. And as you probably appreciate constant development is required to keep up with Browser advances.
So while they may work there may be javascript conflicys with other FW actions and if something breaks then it isn’t going to be fixed.
The one major difference (leaving out compatibility with other Actions and modern browsers) is that ScriptyAccordion does not follow the same design modality as the other two. Where SuiteFX and Moo Accordions use a separate Action to mark each header and each disclosed element, ScriptyAccordion relies on you to follow a disciplined assembly technique, and then apply and configure a single Action to the parent element (the outer HTML box) containing all of the headers and disclosed elements.
While this requires you to think a little more clearly about the content you are presenting (rather than to just use a click-click-draw style) the benefit is that you don’t have to click and configure each element in your assembly, and when you come back to edit it later, you don’t have to fiddle with any Actions. Any amount of properly-constructed content will behave exactly the same way.
Walter
On Dec 30, 2013, at 3:40 AM, DeltaDave wrote:
suiteFX and mootools. So should I use ScriptyAccordion?
These use different Core javascript libraries to those used ‘natively’ in FW (which uses Script/Protaculous predominantly)
Also there has been no development of suiteFX and mootools within FW since Weaver departed these shores many years back. And as you probably appreciate constant development is required to keep up with Browser advances.
So while they may work there may be javascript conflicys with other FW actions and if something breaks then it isn’t going to be fixed.
and that seems to work. Unfortunately, it also makes a mess of the page layout.