Well, yes... The roadmap is a little deceiving. It correctly shows
that we've got most of the big features done, but there are quite a
few features which are only half done.
> According to the roadmap we have only headers/footers, dialogs,
> and bugs left.
That's pretty much true.
> I see lists and tables are 1.2ish. I assume borders (as in boxes around
> stuff) comes with tables?
I think they're implemented distinctly, but it might be logical to do
them at the same time.
> I'd like to see the Mac version working. I have Mac programming experience
> but no Mac at the moment. I can probably get one soon, at which point I'll
> start updating that portion of the tree, as well. To get it working
> anytime soon, however, I'll need help. Anyone?
The Mac portions of the tree are VERY out of date, AFAIK.
> OR, if there are still any wxWindows people here, would anyone be up to
> making a wx port of AbiWord? I've not used wx yet, but have wanted to. If
> some people would be willing to do that, instead of a direct Mac port,
> I'll help out some there.
I would still love to see this happen.
> Has anyone given this much thought yet? We need a cross-platform way to
> interact with OLE, Bonobo, OpenParts, and Be and Mac models (whatever
> those are).
> It really shouldn't be too difficult, as all we need is calls
> to: find and load component for data type A, give the component the data,
> get the data from the component, make the component show it, and something
> to get the necessary information to print it.
I suspect that designing a cross-platform API which will accomodate
OLE, Bonobo, and OpenParts will be quite a challenge.
However, the Bonobo guys are ready to go. Miguel has asked us to lay
some simple groundwork so that they can plug in Bonobo support more
easily. As soon as we provide them a class into which they can stick
their code, they'll be ready to do it.
> How big is this to users? I think a lot of people receive Word docs, but
> don't necessarily have to send Word docs. Of course, for those that do,
> this is extremely important. Anyway, this will take a good sized chunk of
> code in wv, but nothing really new or too complex, since we will always
> take the simplest approach (no fastsaves, no weird SPRMs to simplify
> SEP/PAP/CHP "compression", etc).
You're right -- for those that need it, this is a big deal. We've got
to have the feature sooner or later. I spoke with someone the other
day who wanted the feature very badly. They were wanting to deploy
AbiWord, and the absence of Word export was a showstopper for them.
-- Eric W. Sink, Software Craftsman SourceGear Corporation firstname.lastname@example.org