No, although you can identify a header with an Action. Try the AddSelector Action to do this. Insert the Action inline anywhere within your header text, and add the desired ID or classname. (I haven’t tested this in Freeway 6 yet, though, so you may end up reporting a bug for me.)
All HTML boxes and Graphic boxes that are layered or inline will get an ID in Freeway 5 or 6, you adjust this in the Name/ID field (6) or Title field (5 or less) of the Inspector.
Walter
On Apr 10, 2013, at 1:09 PM, atelier wrote:
I recently came across this in the source of a page
Freeway doesn’t expose controls to add an ID within the style palette, it would have to do that in the Inspector. But the interface doesn’t allow you to select an H tag directly. (Which is what it would need to do.) An H tag is a full block-level tag, equivalent in seniority to a DIV or P tag. HTML allows you to apply an ID to it, but Freeway treats an H1 as if it was a style, which is most certainly is not.
Walter
On Apr 10, 2013, at 1:37 PM, atelier wrote:
Cool. But I was thinking, how it would be if one could add the id in the stylepallet.
Do you need to use IDs? Why not use a class?
You can easily add a class to a named tag like an H1 by entering a name in the Edit styles dialog alongside the tag field;
Tag: H1
Name: myclassname
which will give you something like this;
Blah, blah, blah...
Regards,
Tim.
On 10 Apr 2013, at 18:37, atelier wrote:
Cool. But I was thinking, how it would be if one could add the id in the stylepallet.
…this makes me also think how FW doesn’t make it very easy for a novice to learn HTML the proper way.
I think Softpress would say Freeway Pro isn’t meant to facilitate anyone learning HTML or CSS at all, even though it’s had the opposite effect for many of us. I would have thought it to be a fine legacy for Freeway Pro to have been more transformative for its users.
No problem. I wasn’t sure why you wanted to use an ID rather than a class. If you want to control items with a script on your page then an ID is slightly easier to code for but as Freeway makes adding an ID to an h tag (for example) near impossible then classes it has to be!
Regards,
Tim.
On 10 Apr 2013, at 19:43, atelier wrote:
I have no answer to your question, Tim! I asked here because I discovered something I was not familiar with.
still in my early learning days
One more thing, (I take advantage of the fact that some of the Bosses from this list following this little discussion I found this interesting, never heard of it either:
I’ve never discovered the child selector option in FW, so I was not aware of its existance. Reading the article made me slowly slowly understand why I had such a problem adapting the FW CSS menu afterwards. Outside FW. The client wanted small changes to the site, and I got unpredictable results, nearly uncontrollable. Exactly as described in the article.
It’s the depth at which a particular rule set impacts the elements around it. For example, a style like #nav li a, when given an HTML structure that includes our menus, has a depth of 5: from the ul to the li to the ul to the li to the a.
The deeper the level of applicability, the more impact the styles can have on the HTML and the more tightly coupled the HTML is to the CSS.
The goal of more manageable CSS — especially in larger projects — is to limit the depth of applicability. In other words, write CSS to affect only the elements that we want them to affect.
That’s a good rule to follow. The reason that Freeway’s CSS Menu Action uses this tortured CSS is because it has to work at one remove. Even though it adds an ID to the parent menu, the child elements in the menu are known only by their offset from the top-level item, so you do get some very strong selectors that are difficult to overpower.
Walter
On Apr 10, 2013, at 3:50 PM, atelier wrote:
The goal of more manageable CSS — especially in larger projects — is to limit the depth of applicability. In other words, write CSS to affect only the elements that we want them to affect.
