Hi Ian and Everyone!
I have mixed feelings about this issue.
2 Situations I faced with this:
(1) I created web pages from OO.o v1.1.4 for a class I had that used
BlackBoard as the VLE. I had to do some code changes to get the pages
to display correctly using the HTML Editor in BlackBoard. The code was
a mess to decipher. :-( But, it was do-able.
(2) When I edited a web page in Microsoft Word, that I created from a
doc in OOo, the table code became all messed up and the tables did not
display properly. The cut and paste to correct this took a lot of work
when the original doc I created in OOo had a lot of tables in it. I
would have to type the document from scratch in MSWord and then convert
to HTML. :-(
Now, I do not know if anything can be done about it. Microsoft Word
documents when saved in HTML also has some messy code. That just may be
what one gets when converting DOC to HTML.
Does anyone know if this new "Open Doc" code will clean this up some?
I support much of what Ian is saying but I also see the other side of
this that T.J. is referring to. If the community was to take a vote I
think they would agree mostly with Ian but it would be nice to see some
incremental work done on the HTML conversion function and building
feature with subsequent releases even if a major change is not done all
at once.
A PDA port which is easy to configure and accomplish would also be nice.
:-P I think some work is being done with this. Someone who knows
more about it may see this thread and comment on it.
What does the community feel about that.
SC
Ian Lynch wrote:
On Mon, 2005-09-19 at 01:10 -0500, T. J. Brumfield wrote:
With 2.0 looming, has there been much thought of the future roadmap of OOO?
One thing I'd really like to see added to OOO is a fully featured HTML
editor. There are plenty of WYSIWYG open-source HTML editors out there. I
imagine you might be able to borrow perhaps from one of their codebases as a
starting point.
KOffice has plenty of applications such as KFormula, Kivio and KPlato. Has
there been any thought to convert these or add similiar functionality to
OOO?
I'd like to see the effort going into fundamentally improving the
efficiency of the code so that OOo is as compact and as fast as it can
possibly be, encouraging posrts to PDAs as they get cheaper and more
powerful hardware. Oh and proper support for SVG import. That is
fundamentally much more important than replicating things that are
easily available elsewhere.
--
How sweet it is!!! :)
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
