I’m resurrecting this thread because now I have had time to replicate the
issue and think I understand it better.
See this first - http://cssway.thebigerns.com/workbench/freeway-limits/
I’ve had a couple of major websites with this issue now. Both have serial
content which explosively grew beyond their original scope. Ideally, I
should have fallen back (pushed forward?) to a managed content system - but
before y’all start battering me with those comments, can we just focus on
the FWP issue?
This example (as my other actual sites) are all inline or inflow
construction (“box model construction” to some of you). Within my main
content element, I would have serialized product containers (HTML5
articles). They served as templates for items that were added. Items that
are deleted are simply select and delete. So when the business activity for
these clients began growing, so did the number of available products. My
FWP pages got longer and longer, and as they did I began encountering
Problem #1 - the “garbled screen” problem
The closer a FWP workspace “page” gets to 19,999 px, the screen begins
doing strange things. Scrolling after some point down the workspace results
in a garbled screen. On a long enough page it is unavoidable, inevitable.
If you open my FWP document and use the Site pane as a shortcut to the page
bottom, say, selecting the 14th article item – and then try any scrolling
method to continue down, the screen bunches up. Check it out.
Problem #2 - the “hidden selection” problem
On longer pages, after some point individual items no longer display
selection “handles” - the only way I can tell if an item is selected is by
the visual feedback of the Site/Item pane. Worse, longer documents will
also stop showing the text-selection highlight so there’s no way to know
where your insert cursor is, what text you’ve selected, and so forth. Not
impossible to do, and almost as fun as having an icepick repeatedly jabbed
into your eye sockets. Go to the article15 item and try selecting any child
box or item.
Problem #3 - the “auto-growth” problem
As I duplicate or add more items to my FWP construction, Freeway Pro will
grow the workspace page length to accommodate the new content. UNTIL the
page reaches 19,999px in length. Exceeding this dimension will cause your
inline construction to collapse - get used to X’s in the Site/Item pane. At
This point, FWP will no longer grow the page length for you - you must
manually expand the workspace yourself - from 19,999px to 32,767px
(Freeway’s self-imposed maximum length).
I can only assume the previous silence on this issue has been because of
inexperience with it. Yippee, I’m a pioneer! What I would really like to
hear from Softpress about this is A) Yes, we know about this… and B) This
is what we plan to do or not do about it.
And of course from any Freewayers who’ve had similar issues, or who have
played with my files and come up with solutions – like, for example, that
the whole screen-garble thing can be held at bay by NOT placing the
serialized items into a single big container… Yes, while I cannot say how
long a container can get without causing problems, I’ve found that a
temporary solution was to break up long containers into smaller ones. This
seems to have gotten me past much of the garbled screen issue, but not the
hidden selection problem.
On Wed, Jun 26, 2013 at 4:51 AM, Ernie Simpson email@hidden wrote:
Sorry I couldn’t be more helpful.
Thanks for even looking Kelly… you speak of strange widths, but let me be
clear that I am speaking only in the vertical dimension. Specifically,
inline or inflow containers that approach or exceed 19999px in the working
area or working “page” areas that exceed that neighborhood. That this has
happened to me and 1 other user that I know of indicates that it is a
repeatable issue, just not yet a predictable one.
I’d love to do more testing to chase down all the particulars, but my
Softpress R&D budget is already overdrawn.
freewaytalk mailing list
Update your subscriptions at: