Splitting up a project into multiple projects - Alias files

[straygoat]

Hello all,

For our help system (first run at using Flare for our help), we are importing our entire suite as a chm. We will then auto-generate an alias file for our context sensitive help (we don't need the header file as we handle CSH in a slightly different way). What I would like to know is - what happens to the alias file when we later use global project linking to divide the project into a suite of sub-projects?

As far as I can tell, the answer would be to only create new aliases (for new content) within the 'master' project as this would ensure that Flare assigned unique numbers to topics in all of the sub-topics.

Is that the best way forward? Or should we look at allocating a range of values to each sub-topic after the initial auto-gen? For example, if the auto-gen uses numbers in the range 100000-200000, would we then just assign 200001-300000 to one sub project, 300001-400000 to a different sub project and so on?

Thanks

[Nita Beck]

I like your idea of devising a unique range of numbers for each project, but I'd have the upper limit be x99999, so there'd be 100000-199999, 200000-299999, and so forth. That way, anything starting with a certain number (1, 2, and so forth) will be instantly recognizable as being maintained in one particular project.

[straygoat]

Thanks Nita...so the number range is the right way to go?

[Nita Beck]

I actually don't really know if it is or not. My point is to keep the numbers n00000 thru n99999 all withint the same range, so that the first digit can help an author to identify which project something is from. But otherwise, I don't know. I haven't before tried to take a large alias file and break it up into multiple alias files so have no practical advice for you. Sorry...