> How does Abi store the graphic file in relation to the document that
>it is embeded in?
> In terms of HTML we would have the graphic be a separate file (as far
>as the local viewer is concerned) but then integrated into the file when it
>is sent to the browser. Thus objects in different formats are stored on disk
>as separate files. But most Word Processors I've used stored the graphics as
>part of the document file itself? This is obviously optimal from a user's
>point of view because when they want to share the file they only have to copy
>one file. But it doesn't exactly make sense from the program's point of
>view.
Another example from FrameMaker -- you can import graphics either by
embedding or by reference. The latter is fantastic when you're maintaining
a large body of documentation with an extensive artwork library -- if you
use a particular graphic in several manuals (or even several times in a
single manual), updating the artwork file automatically updates every
instance of that graphic in every manual.
But it's a pain in the rear when you're moving stuff around -- or like
you said, when you email a doc somewhere else.
I guess it comes down to the uses AbiWord is intended for. If it's going
to be the church secretary's tool of choice, or mostly for short documents,
embedded-only and limited choices are probably preferable (keeping confusion
potential to a minimum).
If AbiWord is going to play in the tech writer's arena, it will need to
support many different complex features... then again, seeing how many
tech writers use MS Word, maybe not. :-) I'm thinking about large document
production here, the high-end where FrameMaker reigns.
Finally, there's a very large middle ground where engineers write specs,
marketroids build web sites and write proposals, tech writers create
release notes and other short documents, everyday people write sloppy
love letters, and Stephen King cranks out his next huge (but simply-
formatted) novel. From what I've seen so far, AbiWord will be a natural
in this arena. Very few people need a FrameMaker, but most people will
be doing more than a weekly church bulletin, whether at work or at home.
A few extra choices, that can be easily hidden from the most casual users,
would make a big difference.
Larry