[Pro] I've had better days…

Normally I don’t use something as pedantic as the Link to PDF action, but I am on a project with a lot of PDF’s to download and I sought a way to manage dozens of PDF files in a site with various levels of Resource folders…

So, taking this route, I’m disturbed to find what should be simple, elemental,

  <p><a>link</a></p>

becomes

   <p><span id="uselesscodestuff"><a>link</a></span><p>

While the span tag adds another opportunity for styling, I already have plenty with the two other existing tags. Further, the action adds the moronic position:relative to the css of an already contextually relative-positioned item.

With every version of Freeway Pro, I expect to see advancement. And I do… but there are always a dozen small details like this that never are addressed - and I am bloody sick of it. Sick of tripping over the small details because Softpress doesn’t think it worthy to address them or that it is the user’s job to silently bear them.


freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options

I think you may be seeing a regression in Freeway 6. Action items (elements created by inline Actions) generate an extra span tag that represents the Action itself. This is a bug, and has been reported as such. The issue starts in the FixInlineActionStyling() function in that Action, which incorrectly treats this “junk” span as something it should act upon. I’ve sent you a modified Action that comments out that function and deletes the span. You can override the built-in version by dropping this on your Actions folder. Once Softpress fixes this issue, you can remove it and run with the native version instead.

I feel your pain, brother!

Walter

On Jan 14, 2014, at 12:08 PM, The Big Erns wrote:

Normally I don’t use something as pedantic as the Link to PDF action, but I am on a project with a lot of PDF’s to download and I sought a way to manage dozens of PDF files in a site with various levels of Resource folders…

So, taking this route, I’m disturbed to find what should be simple, elemental,

 <p><a>link</a></p>

becomes

  <p><span id="uselesscodestuff"><a>link</a></span><p>

While the span tag adds another opportunity for styling, I already have plenty with the two other existing tags. Further, the action adds the moronic position:relative to the css of an already contextually relative-positioned item.

With every version of Freeway Pro, I expect to see advancement. And I do… but there are always a dozen small details like this that never are addressed - and I am bloody sick of it. Sick of tripping over the small details because Softpress doesn’t think it worthy to address them or that it is the user’s job to silently bear them.


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

Walter, as always you are my hero. :slight_smile:

On Tuesday, January 14, 2014, Walter Lee Davis email@hidden wrote:

I think you may be seeing a regression in Freeway 6. Action items
(elements created by inline Actions) generate an extra span tag that
represents the Action itself. This is a bug, and has been reported as such.
The issue starts in the FixInlineActionStyling() function in that Action,
which incorrectly treats this “junk” span as something it should act upon.
I’ve sent you a modified Action that comments out that function and deletes
the span. You can override the built-in version by dropping this on your
Actions folder. Once Softpress fixes this issue, you can remove it and run
with the native version instead.

I feel your pain, brother!

Walter


Ernie Simpson


freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options

And as a follow-up to my original irritated post - this is my point
exactly, that this small issue was fixable/patch-able in very short order.
Softpress should have someone at least some of the time tasked with fixing
or patching whatever they are not immediately addressing - whatever that
might be. While there are plans for generations of programmers and their
children to slowly evolve Freeway Pro’s feature-set, having somebody shore
up the already-existing workings would just be so bleeding brilliant.


Ernie Simpson


freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options

To be fair, Ernie, my patch was fairly crude, and disabled some existing functionality of the Action, which is designed to fix issues brought about by inserting this Action inline within text that has been already span-styled. Normal behavior for Freeway is to split the span, insert the link, and span the content of the link, leading to this lovely bit of bit-rot:

<span class="foo">Something </span>
<a href="path/tp/file.pdf"><span class="foo">to download</span></a>
<span class="foo"> here</span>

So the function that I disabled (in my quest to fixing the link up the way you prefer it) would have normalized that construction, leaving a single span around the entire run of text. I felt certain that sending you such a bastardized Action would have zero consequences, since you wouldn’t have the temerity to span-style some link text (or much of anything).

Walter

On Jan 14, 2014, at 1:05 PM, Ernie Simpson wrote:

And as a follow-up to my original irritated post - this is my point
exactly, that this small issue was fixable/patch-able in very short order.
Softpress should have someone at least some of the time tasked with fixing
or patching whatever they are not immediately addressing - whatever that
might be. While there are plans for generations of programmers and their
children to slowly evolve Freeway Pro’s feature-set, having somebody shore
up the already-existing workings would just be so bleeding brilliant.


Ernie Simpson


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

Wow, that’s awful. What a wreck. That’s (FW) normal?

Todd

Normal behavior for Freeway is to split the span, insert the link, and span the content of the link, leading to this lovely bit of bit-rot:

Something
to download
here


freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options

You are fair, Walter - and probably cooler-tempered than I am capable of.
And maybe I do underestimate the complexity in these little details that
have irritated me over the years.

In any event, your “crude patch” is greatly appreciated :slight_smile:

On Tuesday, January 14, 2014, Walter Lee Davis email@hidden wrote:

To be fair, Ernie, my patch was fairly crude, and disabled some existing
functionality of the Action, which is designed to fix issues brought about
by inserting this Action inline within text that has been already
span-styled. Normal behavior for Freeway is to split the span, insert the
link, and span the content of the link, leading to this lovely bit of
bit-rot:

    <span class="foo">Something </span>
    <a href="path/tp/file.pdf"><span class="foo">to

download

    <span class="foo"> here</span>

So the function that I disabled (in my quest to fixing the link up the
way you prefer it) would have normalized that construction, leaving a
single span around the entire run of text. I felt certain that sending you
such a bastardized Action would have zero consequences, since you wouldn’t
have the temerity to span-style some link text (or much of anything).

Walter

On Jan 14, 2014, at 1:05 PM, Ernie Simpson wrote:

And as a follow-up to my original irritated post - this is my point
exactly, that this small issue was fixable/patch-able in very short
order.

Softpress should have someone at least some of the time tasked with
fixing

or patching whatever they are not immediately addressing - whatever that
might be. While there are plans for generations of programmers and their
children to slowly evolve Freeway Pro’s feature-set, having somebody
shore

up the already-existing workings would just be so bleeding brilliant.


Ernie Simpson


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


Ernie Simpson


freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options

That’s what an inline Action without Softpress’s clever code will do.

If I had spent some more time on the problem, I’m sure I could have figured out a way to remove the Freeway 6-bug-generated extra span from the mix without disabling that code. If I had, I probably would have sent it to Softpress and posted it to the Forge until there’s a patch to Freeway proper.

Walter

On Jan 14, 2014, at 1:27 PM, Todd wrote:

Wow, that’s awful. What a wreck. That’s (FW) normal?

Todd
http://xiiro.com

Normal behavior for Freeway is to split the span, insert the link, and span the content of the link, leading to this lovely bit of bit-rot:

Something
to download
here


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

It’ll be good to find a rock solid library solution for this. I patched the LI Styler Action for David Owen last week simply by checking for FW6 and the presence of the span (plus I have my fingers crossed);
http://www.freewayactions.com/code/?f=List+Item+Styler.fwaction
I suspect this is far from a fool-proof solution.
Regards,
Tim.

On 14 Jan 2014, at 18:39, Walter Lee Davis wrote:

If I had spent some more time on the problem, I’m sure I could have figured out a way to remove the Freeway 6-bug-generated extra span from the mix without disabling that code. If I had, I probably would have sent it to Softpress and posted it to the Forge until there’s a patch to Freeway proper.


freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options

Tim,

I re-named the action just for this job so it did not overwrite the old in case of problems with it. It’s OK so far.

David Owen

http://www.printlineadvertising.co.uk

On 14 Jan 2014, at 19:20, Tim Plumb email@hidden wrote:

I patched the LI Styler Action for David Owen last


freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options

On 14 Jan 2014, 5:34 pm, The Big Erns wrote:

You are fair, Walter - and probably cooler-tempered than I am capable of.

Well Ernie - Somehow I really do believe we’re soul mates.

Cheers

Thomas


freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options

Ernie, anyway you can post a link to the page you’re working on? I’m curious to see what the issue was and how this bit of code fixed it.


freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options

Ernie, anyway you can post a link to the page you’re working on? I’m
curious to see what the issue was and how this bit of code fixed it.

I’m sorry Kelly - the project isn’t yet complete and even when it is, this
is all material that lies beyond their paywall. However, I took a few
minutes to cobble a quick example here -
http://cssway.thebigerns.com/workbench/unwanted-span/


Ernie Simpson


freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options

Wow! Thanks. I hope you didn’t do all of that for my benefit. :slight_smile:

By the way, I’ve never used the Link to PDF action, but I have successfully used the Force Download action and it works very well. http://actionsforge.com/projects/view/109-force-download-php

You can sample the code on this page:
http://www.williamsburgmemorialpark.com/needs/immediate.html


freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options

LOL. I just saw your code comments. Thanks for explaining everything Ernie.


freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options

Ernie, I haven’t seen this syntax used before:

/* STRUCTURAL STYLES */
div, 
header, 
article, 
section, 
footer

header > div,
article > div, 
section > div, 

Where can I find out more about Structural Styles?

BTW, nice use of the rem unit of measure.


freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options

Ernie, anyway you can post a link to download the FWP file for the page you setup? I’d like to see where you’re inserting the code. Thanks!


freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options

These examples target all child div elements inside each header, article, section element.

Just wait ’til you learn about all the pseudo classes (eg, nth-child(3n+3)), adjacent sibling selectors (+) and so much more. Oh the fun you’ll have.

Todd

header > div,
article > div,
section > div


freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options

Yeah, my head is about to explode with the little bit of CSS knowledge I’ve already acquired. LOL


freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options

I don’t think that I ever responded to this… and though I’m sure Kelly
figured it out, I thought that I’d make some comments for anyone else
interested.

When I hand-code html and css, I try to group my CSS code so that I can
easily find and edit relevant elements - so I try to put basic Structural
Items together, basic Text items together, Menu items, List items, and so
forth. Keeping in mind, of course, that the the order in which my styles
appear affect the CSS Cascade. Structural Items to me represent those
logical HTML sectioning elements that are physically used to build a
document structure - so divs, headers, footers, etc.

I think Kelly was also intrigued by the selectors that I used for my
styles… Freeway employs a basic selector set, but in CSS there is an
abundance of very creative and useful selector types for making powerful
and elegant code. For example, the first selector is an example of a
grouped selector, where a single style definition can be applied to a
group of selectors.

For review, here’s an example of CSS code syntax -
http://cssway.thebigerns.com/Resources/diag-css-syntax.png

Group selectors are separated by commas. Freeway Pro writes what I call
“structural” code redundantly, item by item, and by id attribute. As a
human coder, I think it’s more efficient to write some things just once, as
a general rule, then worry about the exceptions later. So, since I know
that my layout is relative, I take those sectioning items used to make the
general layout and position them relatively in one swoop…

div, header, article, section, footer { position: relative; }

Another way to write this so it is easier to read is to add a
carriage-return after the comma…

div,
header,
article,
section,
footer { position: relative; }

but t’s still the same thing.

My sites are built like layer cakes with these sectioning elements. The
top-parent element (PageDiv) is unaligned with an undefined flexible width,
so the section containers (invisibly) extend the width of the browser
window. Into these I put content containers which are centered and given
max-widths… which then keep the contents quite visibly in a page-like area.
Again, these content-containers have common styles that are easier to
affect globally. So my second example, while again an example of a group
selector, is actually an example of a group of Child selectors…

header > div, article > div, section > div, footer > div { margin: 0 auto;
max-width: 1200px; }

Child selectors target elements that are directly children of a parent
element – and no further. Descendant selectors continue down the family
tree… so that header div will affect every div element within the
header element. Child selectors limit that influence to the first
children of that line. Since that is how my structure is designed, it makes
it perfect for this use.

<section element>
    <div container><!-- direct child of the section element -->
        <div><!-- child of container element, therefore only indirectly
child of the section -->

Using this kind of logic with code makes it easier to affect elements by
their structural position, instead of by name or class – which are all
valid ways to write styling code. Just this way uses less effort to get the
same results. Editing is more direct when you can affect similar items with
a single edit.

Of course, this way of thinking doesn’t always apply well in Freeway Pro…
firstly, the goddam Tag field in the Style Editor isn’t resizable or big
enough to see squat. I have to use a text editor to write the selector the
copy-paste into the Tag field. :stuck_out_tongue: However - once you numb yourself to that
reality, Freeway accepts and reliably writes these special selector styles.
Then I can use something like the Anonymous action to disconnect the
element from the id selector it writes for that element so my custom style
kicks in.

It’s important to note, though, that Freeway still writes the style code
for such items… though it no longer applies it – which is somewhat bad,
aesthetically. Also, FWP has its own logic for the order in which styles
are written. This makes it harder to group styles logically or to benefit
the Cascade order.

A couple of my favorite learning resources for CSS style selectors-

http://css.maxdesign.com.au/selectutorial/index.htm


Ernie Simpson

On Wed, Jan 15, 2014 at 12:49 AM, RavenManiac email@hidden
wrote:

Ernie, I haven’t seen this syntax used before:
thebigerns.com

/* STRUCTURAL STYLES */
div,
header,
article,
section,
footer

header > div,
article > div,
section > div,

Where can I find out more about Structural Styles?


freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options