How about saving to html files first? (If you only want partial content,
then that can be done too, btw.) Then. Use an editor that has a Project
Manager feature, together with an inline browser view display. Import
your saved html files into the editor's Project file
Here's something fairly straightforward for this use:
Bonfire Studio
http://nzworks.com/bonfire/screenshots/thumb_browserview.gif
For cleanliness for this purpose, uncheck the "output view" lower pane.
Your Project pane, I like it docked vertically on the left. Import
new docs intor your project -- singly or in groups -- through the menu
or by dragging from the explorer.
In theProject pane, you get hierarchical layout: nested subfolders, etc.
You can create a tree, drag documents around, move them between subfolders
and so forth.
In the document display, there is one loaded doc at a time. That loaded
doc has three available tabs: source, xml, or browser view.
If you like, you can configure Bonfire to always show only one tab for
html files. You could choose strictly browser view, as the one tab.
You can also have image files as part of a project file. Those would use
the Browser Control too, for automatic display.
Your project file is a special .xpr document, for Bonfire Studio to
load. Basically telling it just a file list to load as a particular
group, together with the layout. Source view on an .xpr says XML type.
As to the files that get loaded, those are html files on disk. So the
good thing is you don't have to worry about import/export concerns.
Also can change those html files with any editor, if you desire.
http://nzworks.com/bonfire/index.asp
_______________________________
Footnotes. I initially liked Bonfire, but had two things that bothered
me. One was common problem: the lack of wordwrap view.
The other is that it makes copies of the files you configure to be part
of a project, and puts them in a new folder. Then in .xpr file you see
(1) the filename, relative path since its a file now in the same folder as
the .xpr file. Plus (2) the original absolute path on disk.
Having two copies was something I did not want, for my purposes. Yet for
other purposes, say those similar to the OP's, where there is not a lot
of editing going on, might be fine.
I should note. I did not take time to investigate what goes on when you
edit one of the files that are part of a Bonfire project, in the various
scenarios: Bonfire interface; or original location or new location, with
external program; etc. Short sum, it's an area of confusion for me, the
file copies, and I haven't gone through and investigated the specifics of
its behaviors in this matter.
