TopNav skin and linked projects
-
- Jr. Propeller Head
- Posts: 2
- Joined: Fri Mar 27, 2015 6:23 am
TopNav skin and linked projects
I'm trying to adapt an existing HTML5 project to use the TopNav skin. My TOC is mostly links to other Subsystems projects, and none of those show up in the top nav menu when I generate. Is there a setting I am missing, or is this not supported by the skin.
Thanks much!!
Thanks much!!
-
- Senior Propellus Maximus
- Posts: 3667
- Joined: Thu Feb 02, 2006 9:57 am
- Location: Pittsford, NY
Re: TopNav skin and linked projects
Welcome to the forums. Unfortunately, I think you are out of luck.
I assume that you are using runtime merging and that your TOC entries are pointing to the Flare projects (by linking to their .flprj files) where those subsystems are managed and built.
Per the Flare 11 help (here: http://webhelp.madcapsoftware.com/flare ... Output.htm), "Merging projects is not supported in Top Navigation output at all."
I assume that you are using runtime merging and that your TOC entries are pointing to the Flare projects (by linking to their .flprj files) where those subsystems are managed and built.
Per the Flare 11 help (here: http://webhelp.madcapsoftware.com/flare ... Output.htm), "Merging projects is not supported in Top Navigation output at all."
Nita
RETIRED, but still fond of all the Flare friends I've made. See you around now and then!
RETIRED, but still fond of all the Flare friends I've made. See you around now and then!
-
- Jr. Propeller Head
- Posts: 2
- Joined: Fri Mar 27, 2015 6:23 am
Re: TopNav skin and linked projects
Ahh, too bad. Thanks for the quick reply!!
Re: TopNav skin and linked projects
Oh, that's unfortunate. I like the TopNav look, but we're married to the run-time merge for the one project where we could use it.
Anyone else who would like to use this combination of features, please log a feature request:
https://www.madcapsoftware.com/feedback ... quest.aspx
Thanks,
Kristen
Anyone else who would like to use this combination of features, please log a feature request:
https://www.madcapsoftware.com/feedback ... quest.aspx
Thanks,
Kristen
Kristen Kelleher
Director of Tech Pubs, TIBCO Jaspersoft
Director of Tech Pubs, TIBCO Jaspersoft
Re: TopNav skin and linked projects
I'm green behind the ears (aka, newbie in these posts). And it's been quite a journey familiarizing myself with Flare, learning the right terminology, and refining my searches so that I could finally arrive here at this particular string. It's not the diagnosis I wanted to hear. But at least I feel some relief from not knowing. Thanks to all who participated here. I will learn to love Tri-pane a while longer. Those of us who have projects merged in our TOCs can't be that small a minority. Or are we? You would think we're a a highly unusual bunch when you consider the one line note that alerts users to this circumstance stuffed way at the bottom of documentation. In any case, I've learned a great appreciation for these Forums. A wealth of information. It works.
-
- Senior Propellus Maximus
- Posts: 2630
- Joined: Wed Apr 14, 2010 8:01 am
- Location: Surrey, UK
Re: TopNav skin and linked projects
Could you use global project linking rather than runtime merging? And would that work with topnav?
Started as a newbie with Flare 6.1, now using Flare 2023.
Report bugs at http://www.madcapsoftware.com/bugs/submit.aspx.
Request features at https://www.madcapsoftware.com/feedback ... quest.aspx
Report bugs at http://www.madcapsoftware.com/bugs/submit.aspx.
Request features at https://www.madcapsoftware.com/feedback ... quest.aspx
Re: TopNav skin and linked projects
Hi ChoccieMuffin,
Thanks for the response and suggestion. I don't see any notes in the documentation warning against using Global Project Linking and Top Navigation. But I don't think it would work for us, as I understand things. We have a number of software modules that live independently from our main software platform version update schedules. We want to keep documentation for everything in one menu. But we want to be able to build and re-publish on the fly, irregularly, for one or two projects now and then. We want to avoid having to build and re-publish en masse, which I understand takes a long time. Keeping our various projects in subsystems and linking in the main TOC via runtime merging I guess allows for this.
Global Project Linking, on the other hand, appears to link information in one central place, which happens to be a master project. We just want to point all of our projects to a master TOC, and leave the content separate and independently available for manipulation and re-publishing.
I don't want to abandon the idea of converting to Top Navigation. But I suspect it will require flexibility on our side rather than Flare's side. And I need to understand our methodology and project structure better before bending to those requirements. But I appreciate the suggestion. And I'm always eager to hear more about possibilities and potential workarounds.
Thanks for the response and suggestion. I don't see any notes in the documentation warning against using Global Project Linking and Top Navigation. But I don't think it would work for us, as I understand things. We have a number of software modules that live independently from our main software platform version update schedules. We want to keep documentation for everything in one menu. But we want to be able to build and re-publish on the fly, irregularly, for one or two projects now and then. We want to avoid having to build and re-publish en masse, which I understand takes a long time. Keeping our various projects in subsystems and linking in the main TOC via runtime merging I guess allows for this.
Global Project Linking, on the other hand, appears to link information in one central place, which happens to be a master project. We just want to point all of our projects to a master TOC, and leave the content separate and independently available for manipulation and re-publishing.
I don't want to abandon the idea of converting to Top Navigation. But I suspect it will require flexibility on our side rather than Flare's side. And I need to understand our methodology and project structure better before bending to those requirements. But I appreciate the suggestion. And I'm always eager to hear more about possibilities and potential workarounds.
-
- Propellus Maximus
- Posts: 608
- Joined: Wed Feb 01, 2006 6:21 am
- Location: Off in the dark....
Re: TopNav skin and linked projects
It appears that it is top nav still does not support project merging.
http://help.madcapsoftware.com/flare201 ... Output.htm
IMHO, I think this will prevent many doc teams with large projects from converting to the cool frameless output. I was kind of looking forward to playing with topnav, but merging projects is kind of high on our list.
http://help.madcapsoftware.com/flare201 ... Output.htm
IMHO, I think this will prevent many doc teams with large projects from converting to the cool frameless output. I was kind of looking forward to playing with topnav, but merging projects is kind of high on our list.
Trent.
Certifiable.
umm...
I meant MAD Certified.
Official Propeller Beanie Owner
Are you on Flare's Slack channels? PM me for an invitation!
Certifiable.
umm...
I meant MAD Certified.
Official Propeller Beanie Owner
Are you on Flare's Slack channels? PM me for an invitation!
Re: TopNav skin and linked projects
Good to see that my team still isn't alone in the world with merged projects and still ineligible for TopNav frameless HTML5 output. Has anyone heard any gossip about the new "side navigation"? I suspect it suffers from the same limitations. But thought I'd check the pulse in case something has changed with project merging and new fangled output. Lots of new looks, but same restrictions.
Makes sense from a marketing perspective: If you already have Flare, and you already have your projects merged into one TOC, you're water under the bridge. Not much sense adding new floors to a building made out of brick and mortar.
Makes sense from a marketing perspective: If you already have Flare, and you already have your projects merged into one TOC, you're water under the bridge. Not much sense adding new floors to a building made out of brick and mortar.
Re: TopNav skin and linked projects
I believe sidenav is just top nav on the side, so the same limitations.
I've also been doing some thinking about it, and it might make sense that merging isn't supported. I'm not a developer, but I'm trying to think how the combined TOC could be developed without frames (one of the key points of top nav). Just some random Friday musings.
I've also been doing some thinking about it, and it might make sense that merging isn't supported. I'm not a developer, but I'm trying to think how the combined TOC could be developed without frames (one of the key points of top nav). Just some random Friday musings.
-
- Propellus Maximus
- Posts: 1238
- Joined: Mon Feb 27, 2006 5:56 am
- Location: Melbourne, Australia
Re: TopNav skin and linked projects
We are looking into this as well - that is, linking many projects. SideNav has the same limitations (but looks nice).
Our next trial is to try and incorporate ElasticSearch, but the powers that be have said this will cost us in licence fees.
Will do some testing over the next few weeks anyway - cause if it works we might then work on a business case for the licence.
Other ways to experiment - we are going to test just having one big project. So far, I have set up our apps all as separate projects (which is easier to maintain), and then created a master project that uses global project linking to import all the sub projects. Only tried on a small sample so far and that works. At the same time we are testing some automatic build tools with TFS so that the giant build can happen overnight.
Has anyone incorporated Google Search across multiple projects? We have used CSH to link between separate projects in the past.
Will let you know how we go - might take a few weeks to complete at this point (other priorities).
Our next trial is to try and incorporate ElasticSearch, but the powers that be have said this will cost us in licence fees.
Will do some testing over the next few weeks anyway - cause if it works we might then work on a business case for the licence.
Other ways to experiment - we are going to test just having one big project. So far, I have set up our apps all as separate projects (which is easier to maintain), and then created a master project that uses global project linking to import all the sub projects. Only tried on a small sample so far and that works. At the same time we are testing some automatic build tools with TFS so that the giant build can happen overnight.
Has anyone incorporated Google Search across multiple projects? We have used CSH to link between separate projects in the past.
Will let you know how we go - might take a few weeks to complete at this point (other priorities).
Margaret Hassall - Melbourne