Before i start on tis issue i want to thank waltd for his significant assistance to explain how to import an excel file into a FW table.
However now i seem to have an issue, that is causing a serious problem when i come to edit the table to allow me to import changes to the Excel File.
The Excel spread sheet is exported as a CSV file, and then imported into FW as a CSV file into a table, issues start occurring with what i call “trailing cells or rows” that are imported into the FW table but these rows have no height and i cannot select them in order to delete them from the page. If i ignore them and then try to edit the table to re-introduce the edited Excel page (as waltd explained in a previous thread) then these trailing cells/rows increase in number creating an issue with the page overrunning …
How do i edit out these trailing rows/cells? from FW it seems that there is no way to limit the amount of rows/cells exported via the Save As operation in Excel.
Yes thanks i tried the option to select a cell above the " target rows" moving t down to the row and then tried to delete row and it did not work for me, not sure what i was doing wrong there? however went back and tried again so that worked. thx, but i have also now realised why i was getting these other “trailing rows” into the table, they had formula in them !.
Just another observation in regard to inserting CSV text into Tables, when i set the style based on the td tag, not all of the styling characteristics are visible until you Preview the page, is this correct? For instance within the style i have used the Extended tab to insert align-vertical with middle !important set (thanks waltd) but you do not see this effect until you preview.
Just another observation in regard to inserting CSV text into Tables, when i set the style based on the td tag, not all of the styling characteristics are visible until you Preview the page, is this correct?
This is expected behavior. Freeway’s internal design view is not HTML, and not CSS. It is a Desktop Publishing environment, with all the richness and precision that comes from a (distant) heritage in print design. When you publish or preview, you dumb down that model to whatever version of HTML/CSS you have chosen for your page in the Page Inspector. So Freeway does not read the CSS when showing you the design view, only the parts of its styles that you created with the normal styling tools.
That’s because Freeway Pro’s strength is as a code generator… when you
are in the layout window, FWP has not yet generated any code. While it will
dutifully include your Extended code in the final markup, it doesn’t
consider it yet when creating the working page’s display. Freeway Pro is
much better at rendering extended styling than it used to be, but in cases
like this you will need to develop a capacity for letting go of some of the
visual expectations of the working window.
–
Ernie Simpson
On Tue, May 29, 2012 at 5:12 AM, ejw email@hidden wrote:
Just another observation in regard to inserting CSV text into Tables, when
i set the style based on the td tag, not all of the styling characteristics
are visible until you Preview the page, is this correct? For instance
within the style i have used the Extended tab to insert align-vertical with
middle !important set (thanks waltd) but you do not see this effect until
you preview.
Thank you for your descriptive responses which helps me understand how the FW product generates the final product… suppose this is the real trade off between WYSIWYG and the more efficient code… hope i have understood this point!
The key thing here is to realize that Freeway is optimized for designer ease and speed first, and so putting off the generation of the HTML/CSS until publish time is a real time-saver, because you only have to run through that huge tree of elements once that way. Imagine if every time you made a change, you had to wait while Freeway re-generated the code and re-optimized all of the graphics. You can sort of visualize this effect by turning on View / Graphics Preview in the main menu. You’ll turn it right off, I’m sure.
Walter
On May 29, 2012, at 4:09 PM, ejw wrote:
Walter/Ernie,
Thank you for your descriptive responses which helps me understand how the FW product generates the final product… suppose this is the real trade off between WYSIWYG and the more efficient code… hope i have understood this point!