deleting index entries

[doc_guy]

Also, being the Lone Writer here, I have no source control to deal with.

Source control can be *very* valuable to lone writers. I won't hijack this thread (too late, sorry), but from my view, source control is really more about controlling the source than it is about collaboration. It has some nice collaboration features, but the nuts and bolts of source control is backing up your content and being able to revert to any previous state at any time.

As for deleting index entries, I assume you are using Flare 4. Are your files local or on a network drive? What happens when you edit an index entry and then save the topic?

[KevinDAmery]

I agree, Paul.

Put it this way: have you ever encountered a lone programmer who didn't use source control of some type? (I sure haven't.) If the company can't afford to lose or mess up months worth of programming, why should losing or messing up months worth of documentation be acceptable?

[ccardimon]

Put it this way: have you ever encountered a lone programmer who didn't use source control of some type? (I sure haven't.) If the company can't afford to lose or mess up months worth of programming, why should losing or messing up months worth of documentation be acceptable?

So what is the Keep It Super Simple way of source control (backups) that a lone writer can implement on their own using Flare?

I am ready, willing, and able to learn.

[KevinDAmery]

In my case, I use the same VSS repository we use for application code. I manually check the files in and out as required outside of Flare (we've tried the integrated approach but for one reason or another Flare floods the network with packets when we do that, so my network admin won't let me use it). As a lone writer, it's relatively easy since you don't have to worry about other users checking things out, so you can check out the entire project when you need to make a change, then check everything back in when you're done.

As said, I'm using VSS here, but the same approach should work with any other source control system.

[ccardimon]

I guess Flare offers on-board source control that is easy?

[KevinDAmery]

No, you'd an external system like Visual Source Safe (VSS) Team Foundation Server (TFS) or something else. Flare will talk directly to those two, or to another one (who's name escapes me) through a plugin.

But as I mentioned before I'm not bothering with the direct interaction and am just managing the source control outside of Flare. The important thing is to make sure you have a system that allows for version control and backups of your docs. If you're working in a software development environment, it's almost assured the developers have a system for doing this with their source code: all that you would need to do is have the person responsible for that create an area in it for documentation and then add your files to it.

[doc_guy]

yes, and no.

Flare natively integrates with Team Foundation Server, a Microsoft product. There are plugins to work with other source control systems, but in most cases, I believe, you have to purchase the plugin.

You should probably use whatever source control system your development group is using. Just ask for a directory where you can store your stuff. Then get the plugin you need to work with it. The PushOK plugins that work with SVN and SCC are about 30 bucks, I believe.