Hi,
I have several projects, each of which have a skin that uses an image in the Logo to show a project description/name on the published pages.
When I merge these projects using the Merging Flare Projects using Targets, I get the desired result, with one exception - I lose the display of the project description/name on the top of the pages, because the new project uses it's own skin....
Could someone suggest a good way to identify the original project description/name on the top of the topic pages after merging?
Jim P.
Merging Projects Skin(s) Question
Re: Merging Projects Skin(s) Question
Hi Jim. I could be misunderstanding your question/issue and if that is case please accept my apologies in advance. 
I take your inquiry to refer to the browser header (skin related).
When you merge projects, that should not result in a new project. Instead, the result should be new output. For instance, if you have project A and project B and merge them, you will still be left with both project A and B, and will not produce project C. Either project A or B can serve as the "master" project. Assume you choose project A as master. When you select project B in the TOC editor as wanting to merge that project file into project A, the only option you can further specify is the target - belonging to project B, however, also in project A - that you want to merge. Assume you select HTML5 as an example target. "HTML5" must reside in both project A and B, however, the SKIN logo and other options (such as synonyms file, etc.) is determined by the setting in the HTML5 target from project A, not B.
Perhaps merging the other way around, where you choose project B as the master, could resolve your issue.
I hope this makes things clearer for you rather than more nebulous
I take your inquiry to refer to the browser header (skin related).When you merge projects, that should not result in a new project. Instead, the result should be new output. For instance, if you have project A and project B and merge them, you will still be left with both project A and B, and will not produce project C. Either project A or B can serve as the "master" project. Assume you choose project A as master. When you select project B in the TOC editor as wanting to merge that project file into project A, the only option you can further specify is the target - belonging to project B, however, also in project A - that you want to merge. Assume you select HTML5 as an example target. "HTML5" must reside in both project A and B, however, the SKIN logo and other options (such as synonyms file, etc.) is determined by the setting in the HTML5 target from project A, not B.
Perhaps merging the other way around, where you choose project B as the master, could resolve your issue.
I hope this makes things clearer for you rather than more nebulous
Re: Merging Projects Skin(s) Question
Thanks for the quick response.
Maybe I approached this a little wrong.
What I did is I created a new ("parent") project. In the TOC of the "parent", associated the existing projects, each to a TOC entry.
When I did this, the pages displayed, all take on the "parent" skin.
Jim P.
Maybe I approached this a little wrong.
What I did is I created a new ("parent") project. In the TOC of the "parent", associated the existing projects, each to a TOC entry.
When I did this, the pages displayed, all take on the "parent" skin.
Jim P.
Re: Merging Projects Skin(s) Question
You're welcome Jim.
The way you approached this certainly could work. If you already created a new project with a new TOC and then linked items in the new TOC to the projects you want to merge, that's fine. Then in this case your new project also needs a new target that matches the target type of the projects you are merging. Your new target in your new project would also need a new skin and other options set. You probably should just import the skin you ultimately want into your new project and then select that skin in your new target. I think the bottom line here is that the skin which contains the project description/name that you mention you've lost needs to be the skin used in your master merge project.
The way you approached this certainly could work. If you already created a new project with a new TOC and then linked items in the new TOC to the projects you want to merge, that's fine. Then in this case your new project also needs a new target that matches the target type of the projects you are merging. Your new target in your new project would also need a new skin and other options set. You probably should just import the skin you ultimately want into your new project and then select that skin in your new target. I think the bottom line here is that the skin which contains the project description/name that you mention you've lost needs to be the skin used in your master merge project.