Hi,
I'm currently working on a print out function.
What I need help with is how to place the icon in the right place.
This is a draft from the designer:
As you can see the icon is to be placed at bottom of the main content area.
Becouse of that most pages have more than one content div and those are placed on the right hand side at the page the printout icon will be placed after those. This is when I place the code for the icon in the design parse file direct after the main content area.
How can I solve this?
Hi Daniel,
I'm not too sure what the problem is - do you want to place the print icon after the last div, to the bottom right?
Would a float:right and a margin (in the parse file) do it?
Hi Matt!
The icon is to be placed as you can see in the picture.
But if I put it after the content divs in the design it will be placed either after content div 2 or content div 1 depending on if a specific page has 2 divs.
Check this examples:
2 Divvs
2 Divvs
If I would place the icon after the body area in the design it would be placed on different places depending how many divvs im using.
Maybe I could place it within the footer, but that would be quite har to get the light blue line on the right to follow thrue all the way.
I have no idea if this works or how it works, but I think I remember someone saying that you can position links or icons using backgrounds??
If you give the first DIV in a page a specific class, you might be able to format that one a little different and print that icon at the bottom right.
Like I said, I have no idea what I'm talking about, but it sounds like somewhere I would start investigating from.
Hmm… if that was possible it might work.
Bottomline is it not that good that you cant specify specific divs/areas which should hold editable content.
In that case it would be easy to just say that content div 1 & 2 are editable. And in between I could place whatever I want.
Today all the divs with editable content has to come directly after each other to be handled by Matrix.
You could achive this with nested content - if one of the two divs were likely to have the same content throughout a lot of pages. Though I gather that this is not what you want?
Otherwise, I still think you should be able to achieve what you want by floating the print-icon in the parsefile - the width of the content divs appears to be set so that shouldn't be a problem.
We have used contextual asset lists to deal with this. It means we can have multiple editable content on a page split by fixed content in the parse file
We have a couple of custom assets derived from standard_page, one for left context and one for right context.
In the parse file we have nested content whcih is an asset listing the list items of type right_context with the root node set to current asset. Any time we want extra content in the right hand area we just add a right context page under the root of that page.
This has the advanage that we can link the same bit of content to different places, rather than have it repeated on many pages (and the problems with keeping all those bits in sync).
Marcus set this up for us, and I think I've described it correctly.
cheers,
Richard
This sounds very interesting.
I was thinking on asset listing as a solution, but didn't manage to find a implementation that would be easy to handle.
Just to clear out.
- You have nested content areas in the design.
- Every area are "pointing" to an asset listing page.
- This asset listing page are listing the page content from children called "right_context" or "left_context". (Depending on nested area)
Have I missed anything?
What parts have been customized for you?
BTW: I solved my problem with placing the icon in a div and gave that an absolute position. In other words some CSS hacks. But for me it seems like a quick-hack solution.
[quote]1. You have nested content areas in the design.
2. Every area are “pointing” to an asset listing page.
3. This asset listing page are listing the page content from children called “right_context” or “left_context”. (Depending on nested area)
[right][post=“9251”]<{POST_SNAPBACK}>[/post][/right][/quote]
Yes, you have it in one (or 3). The root node to list is set down the bottom of the details page (set to current asset id).
This is an example of what we’ve done. That page is an asset listing, and to avoid the nested list (from the Parse file) also listing all the assets that are the root of the page we use those two custom assets. The list of highlights on the right is nested in the right_contextual and elsewhere, whever we want to use it.
The left one is used on This and elsewhere to give the daily archive listing on the left.
We use a customisation to turn off the contextual listing on pages that it’s not needed BUT with the new No Results content area for Asset listings in 3.8 we won’t have to do this anymore - we’ll just put no code in that bodycopy. This will then only put code in the page when there is content to put in the right (or left) areas.
There are probably other ways of targeting what content to list (I’d be keen to hear of any).
We’d originally wanted two editable areas (like you do) but the source order was important for us (we try to have a semantic page for acccessibility reasons).
This solution has actually turned out to be much faster than the way I thought it would be done, as I just drop a contextual item under the root of where I want it, and it appears where I want it. And I can link the content to one master listing too, making it a bit more manageable.
cheers,
Richard
And while I think of it, you could avoid the whole print thing by using a CSS print style sheet to remove (or add) whatever styles you want!
R.
Hi,
thanks for your response!
I would be very interested in looking into that custom assets. I wounder how I can get a copy of it.
Regarding the icon. It's something the client and designer has decided to have. I'm just the implementor. 
You'd have to speak directly to Richard about that – the custom assets belong to Radio New Zealand.
Have contacted him now.
Btw: I really would like this feature to be included in the standard asset. Do you know anything about it?
The assets were created specifically for RNZ. I doubt very much if they'll go into the core, because they're designed for a particular layout style. Though, the concept of having multiple content areas is possibly something we can consider for MySource v4.0.
I've posted it to the bug system. Just want to check if you might know something i didn't in this case… 