I am blanking here… does anyone have an idea for adding a second class to a list?
I’m trying to produce the following…
<ul class="liststyle class2">
<li>list item</li>
<li>another list item</li>
<li>etcetera, and so forth</li>
</ul>
All ideas welcome.
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
I don’t think you can do it easily Ernie. You can use an Action, insert the list as a markup item or edit the code after the page has loaded. Unfortunately the application doesn’t provide the same hooks to extend elements like lists, rules etc as it does for tables (for example) where you can inset code at various locations as well as add attributes to the table or cell.
Regards,
Tim.
On 1 Oct 2014, at 18:05, The Big Erns wrote:
I am blanking here… does anyone have an idea for adding a second class to a list?
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
I tweaked the AddSelector action to include some more Tags so it may well be tweakable to include UL as well. It allows you to add IDs and Classes.
Would that be useful?
David
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
I may try that Dave - I’ve used that action before to add selectors to some
hard-to-reach items. Is it hard to tweak for this?
I tweaked the AddSelector action to include some more Tags so it may well
be tweakable to include UL as well. It allows you to add IDs and Classes.
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
On 1 Oct 2014, 7:05 pm, Tim Plumb wrote:
I don’t think you can do it easily Ernie. You can use an Action, insert the list as a markup item …
all disappointing honestly (to avoid “it sucks”)
Basically I’m pretty sure to know what Ernie is after. So I’m trying to give a go here:
Assumed we have the following construction:
A parent DIV. In this DIV we have couple of things (other DIVs, Graphic items whatsoever).
The two parted action:
Applied to the parent it removes the DIV, substituting it by
Applied to each child item, it removes the DIV substituting it by
Pretty similar as HTML5 action works.
All the rest is coming from external CSS properties and the “what ever library you’d like to use - function”.
It would enable us to use a bunch of stuff out there (such as shown on codrops and others).
Let’s call it “extended use(er) beta” action.
Cheers
Thomas
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
Is it hard to tweak for this?
Shouldn’t think so - I will have a look later tonight.
D
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
This is a very quick hack but should do what you need;
http://www.freewayactions.com/code/?f=Add+classes.fwaction
Apply the Action to a parent object and give it the class to hunt for. Once located it will append the other defined class(es) to the object(s).
I do wish Freeway had nuts and bolts access to items like lists as they remain frustratingly out of reach without Actions like this.
Regards,
Tim.
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
Thanks for the attention guys - adding classes works well with some items,
but there are still quite a few ordinary bits that the Extended interface
doesn’t touch. I could make duplicate styles to cover the different style
combos but that seems so un-clever.
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
This is a very quick hack but should do what you need;
http://www.freewayactions.com/code/?f=Add+classes.fwaction
Tim, that does work for me… and is very flexible for other items. Thanks!
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
On 1 Oct 2014, 9:10 pm, Tim Plumb wrote:
I do wish Freeway had nuts and bolts access to items like lists as they remain frustratingly out of reach without Actions like this.
I usually end up making an inline Action (which goes into one of the LIs), and then reaching upward for the UL in the Action. It becomes unsightly to look at while designing, but does give you the access you need in the Action.
Walter
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
Hi Walter,
I agree. Other than pushing the design view around an inline Action would work well here.
I had thought that a generic Action that looked at the styles on the page and attempted to place classes in the HTML would work really well but I stopped when I realised that it would take me far longer than I had. The basic idea is that you could have two styles like this;
.mycolor { color:#cccccc; }
.mydiv ul { color:#cccccc; }
the first one being a Freeway produced style (a name style) and the second a user generated one (a tag style). When the Action runs it would have to look for the second nested style, locate a matching class for the style (mycolor in this example) and then locate the UL on the page to apply the mycolor class to. Finally it would need to clean up the styles once it was done.
In essence it would dumb down the CSS and simply apply the base styles to the HTML.
Needless to say I found this Action I wrote a lot easier than trying to tackle this! Maybe if I get time I’ll try and look into how this would work.
Regards,
Tim.
On 2 Oct 2014, at 13:06, waltd wrote:
I usually end up making an inline Action (which goes into one of the LIs), and then reaching upward for the UL in the Action. It becomes unsightly to look at while designing, but does give you the access you need in the Action.
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options