I can't seem to find what I need, so I'm asking now.
I create HTML5 targets, which results in several folders - partly based on my source file structure, and partly generated by Flare.
Is there a way to make it so that all Help files are in a single folder after compiling the Help? If so, how can I do it?
Help target in a single folder
-
kwag_myers
- Propellus Maximus
- Posts: 810
- Joined: Wed Jul 25, 2012 11:36 am
- Location: Ann Arbor, MI
Re: Help target in a single folder
The General tab of the Target Editor has an Output Folder setting. If you want to output all your projects to a single folder, you must set up a subfolder for each project. Otherwise, the Output folder will be overwritten each time you build to that folder.
Another option is to use the Publish feature, where you can build a project locally (to your hard drive) and then copy the output to a single folder. This is usually the procedure when you are putting your files up on a server for the development team to include with their builds.
Another option is to use the Publish feature, where you can build a project locally (to your hard drive) and then copy the output to a single folder. This is usually the procedure when you are putting your files up on a server for the development team to include with their builds.
"I'm tryin' to think, but nothin' happens!" - Curly Joe Howard
Re: Help target in a single folder
Hmmm - maybe I should explain better.
For a single target, there usually are several folders based on the source folder structure and whatever Flare does.
So one target looks like:
So, no Resources, Skins, Data, or Content folder - everything just in one single folder - with no folder structure.
I could change how I work w/ the source files, but that is not desirable form my perspective.
For a single target, there usually are several folders based on the source folder structure and whatever Flare does.
So one target looks like:
- - Content folder
- Data folder
- Resources folder
- Skins folder
- csh.js
- Help.htm
- Help.mcwebhelp
- help_CSH.htm
So, no Resources, Skins, Data, or Content folder - everything just in one single folder - with no folder structure.
- - topic1.htm
- topic2.htm
- topic3.htm
- topic4.htm
- topic5.htm
- topic_xxx.htm
- csh.js
- Help.htm
- Help.mcwebhelp
- help_CSH.htm
I could change how I work w/ the source files, but that is not desirable form my perspective.
-
wclass
- Propellus Maximus
- Posts: 1238
- Joined: Mon Feb 27, 2006 5:56 am
- Location: Melbourne, Australia
Re: Help target in a single folder
I think the answer is No. Changing your source files will only affect the content of the Content folder - you'll still end up with the Data, Skins, and Resources folders on generation.devangee wrote: ...
I could change how I work w/ the source files, but that is not desirable form my perspective.
Just curious - why do your developers need a single folder?
Margaret Hassall - Melbourne
-
kwag_myers
- Propellus Maximus
- Posts: 810
- Joined: Wed Jul 25, 2012 11:36 am
- Location: Ann Arbor, MI
Re: Help target in a single folder
Plus, putting all files in one folder would require all links to images, snippets, etc., to be revised. I'm with Margaret, I don't understand why this would be necessary. All the developer needs to do is point the UI link to Help.htm.
"I'm tryin' to think, but nothin' happens!" - Curly Joe Howard
Re: Help target in a single folder
Because they wanted to know if we could make the end result of the Help the same as MS - MS has no folders for their web-based content for their web client applications.
So that's what they wanted me to look into.
It doesn't matter to me either way, as long as there was an easy way to do this. But since there isn't, I'm not going to change how I've organized my source files for that.
I'll let them know that it's not possible, and leave it at that.
So that's what they wanted me to look into.
It doesn't matter to me either way, as long as there was an easy way to do this. But since there isn't, I'm not going to change how I've organized my source files for that.
I'll let them know that it's not possible, and leave it at that.