My site exists to publish content.
I would like to implement stretchtext, as you can see here:
http://fagerjord.no/stretchfilm/pages/stretchf/simpledi.html
The stretched area may want to contain effects as well.
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
Try using Transition FX, built in to Freeway 5, and see if that works for you.
Walter
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
Thanks, Walt.
I am now just trying to implement this in a serious way. The Transition FX is very easy and cool. I can readily do one instance of the additional text rolling down. I just put the appearing text in an HTML item inside an HTML item that has the static text. Clicking the outer frame makes the inner frame windowshade down, growing the outer box to accommodate. This is exactly what I want.
The problem is that I want ten such items on a page. Ideally, the items under the rolldown on the page would push down, and return up when collapsed. I’ll refer you to the example:
http://fagerjord.no/stretchfilm/pages/stretchf/simpledi.html
Using the effect the way I am, I cannot link HTML items so that they “push down.” Instead, the rolled down text just writes on top of the text under.
Ideas? If I could get separate HTML items to reflow, all would be well, but they have to be separate because I need many “triggers.”
Thanks for all you do.
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
Insert all of the items inline within another, larger HTML box, and
they will push each other around. Simply select all of them, cut to
the clipboard, draw an HTML box where they used to be, double-click
inside it so you have a text cursor, and paste. Your layout should
look the same way it was but the items will all be peers in the same
parent element, so they will have equal standing and will push each
other out of the way when needed.
Walter
On Dec 9, 2010, at 10:32 PM, tedg wrote:
Using the effect the way I am, I cannot link HTML items so that they
“push down.” Instead, the rolled down text just writes on top of the
text under.
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
Walt, this method is not yet working for me. The sections still overlap. There must be some setting I am getting wrong.
I’ve tried all combinations. The defaults are:
overflow is “visible”
float is “none”
clear is “none”
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
I guess more information would be useful.
What I am making is a template for a CMS. At the moment, I have each of those individual html elements with a code that will place content of different lengths.
Under normal circumstances, all these code substitutions would be in a single html unit, flowing properly. I am going the separate html unit route in order to use the TransitionFX action that makes certain html elements show and hide.
However, even before the action is applied, my html elements do not reflow.
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
Hi,
what Walter meant is, that your construction needs to be “inline”.
If it should be something like this (I never tried transitionFX for this):
http://www.kimmich-dm.de/hblocher/schume/slidingtext.html
it maybe help this image:
So draw an html-item, inclick in it (cursor) add some text, insert html-item (trigger), insert html-item (sliding-text) …
The key is inline content to manage unexpected hight (anyway in CMS).
Best regards
Thomas
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
Thomas —
Thank you for the work. I guess I am not making myself clear.
I can easily do what you did by determining ahead of time the size of each html box. But this is a template that will import text of different lengths, so I cannot know how big any of the boxes will be.
The content gets added after the Freeway documents is published.
What happens for me is that each box grows as it needs to to accommodate the imported text, but as it grows, the bottom of an html box does not push down the top of the box below.
I believe I simply have some setting wrong, perhaps the “overflow” setting, perhaps the html document type. Perhaps the CSS setting?
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
Freeway (the way I have it set) produces a div specification that sets the height. I guess my question is how to I prevent that?
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
In the Inspector, click on the up/down arrow icon left of the Height
field. The height field and its value will “gray back” and the
parameter will no longer be published at all. SInce this is height,
the natural reaction from the browser will be to shrink-wrap the box
around its content. If there is no content, then it will collapse to
the minimum height permitted by its padding.
Walter
On Dec 10, 2010, at 10:16 AM, tedg wrote:
Freeway (the way I have it set) produces a div specification that
sets the height. I guess my question is how to I prevent that?
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
Well it really might be that I misunderstand you, but the key to me is a “full inline box model”.
Each html element needs to have un undefined height so the box will stretch with the amount of content it’s filled in regardless if you add content within freeway or within your CMS.
To do this, mark your html element and “grey-out” the height by clicking the small arrow up and down box in the inspectors first tab.
Keep in mind, that boxes below (footer) needs to be set in relationship to your expanding box as well and so on …
I set up somewhere a small example using RPL-Action to do, but this is only recommended by having a quite thight layout.
The example is here:
http://www.kimmich-dm.de/ripple/ripple-test.php
As you can see in the added screenshot, the boxes in freeway are set to undefined height, growing by filling with content in browser (in my case WebYep).
Am I closer to your needs now?
Thomas
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
Here’s a fun little JavaScript snippet to test your in-flow layouts
for overflow. Apply Protaculous to the page, click on the top Function
Body button, and paste in the following code:
$('PageDiv').observe('click', function(evt){
this.select('p').each(function(elm){
elm.update(elm.innerHTML + elm.innerHTML);
});
});
With this script in the page, any click will cause all of the P
(paragraph) tags to double their contents. Repeated clicks will double
each time, so your page can get quite enormous. If you want to test
only a single element on the page, then substitute its Title (which is
really the ID) from the Inspector’s left-most tab for the ID PageDiv
value above. This will focus the effect on only one element on the
page, so you can see how a dynamic area will react to longer copy in a
way that merely enlarging the fonts in your browser will fail to do.
Walter
On Dec 10, 2010, at 10:08 AM, tedg wrote:
Thomas —
Thank you for the work. I guess I am not making myself clear.
I can easily do what you did by determining ahead of time the size
of each html box. But this is a template that will import text of
different lengths, so I cannot know how big any of the boxes will be.The content gets added after the Freeway documents is published.
What happens for me is that each box grows as it needs to to
accommodate the imported text, but as it grows, the bottom of an
html box does not push down the top of the box below.I believe I simply have some setting wrong, perhaps the “overflow”
setting, perhaps the html document type. Perhaps the CSS setting?
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
On 10 Dec 2010, 2:32 pm, waltd wrote:
In the Inspector, click on the up/down arrow icon left of the Height
field. The height field and its value will “gray back” and the
parameter will no longer be published at all.
Wow, this is just what I needed. You guys are lifesavers. This is such an esoteric UI convention, I never would have found it.
Thank you.
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
IT is quite an improvement over the versions previous to 5 (I think,
maybe it was 4) where the only way to get this was to delete whatever
was there (making it empty, not zero). Talk about a difficult concept
to wrap your head around.
Walter
On Dec 10, 2010, at 3:13 PM, tedg wrote:
On 10 Dec 2010, 2:32 pm, waltd wrote:
In the Inspector, click on the up/down arrow icon left of the Height
field. The height field and its value will “gray back” and the
parameter will no longer be published at all.Wow, this is just what I needed. You guys are lifesavers. This is
such an esoteric UI convention, I never would have found it.Thank you.
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options